Method for transmitting uplink channel in wireless communication system and apparatus therefor

Abstract

To provide a method for transmitting an uplink channel in a wireless communication system and apparatus therefor.SOLUTION: The method performed by a terminal in the method for transmitting an uplink channel in a wireless communication system comprises the steps of: receiving a system information block 1 (SIB1) from a base station; transmitting a preamble for a random access procedure to the base station; receiving a random access response (RAR) to the preamble from the base station; and transmitting a PUSCH to the base station on the basis of the random access response.SELECTED DRAWING: Figure 30

Description

[Technical Field]

[0001] The present disclosure relates to a wireless communication system, and to a method and apparatus for transmitting an uplink channel. [Background technology]

[0002] After the commercialization of the fourth-generation (4G) communication system, efforts are underway to develop a new fifth-generation (5G) communication system to meet the increasing demand for wireless data traffic. 5G communication systems are also called post-4G network communication systems, post-LTE systems, or new radio (NR) systems. To achieve high data rates, 5G communication systems include systems that operate using millimeter wave (mmWave) bands above 6 GHz, and also include communication systems that operate using frequency bands below 6 GHz to ensure coverage. As a result, implementation forms for base stations and terminals are under consideration.

[0003] This increases efficiency and allows communication providers to offer more data and voice services over a given bandwidth. Therefore, the 3GPP® NR system is designed to meet the demand for high-speed data and media transmission in addition to supporting large amounts of voice. The advantages of the NR system are higher throughput and lower latency on the same platform, support for frequency division duplexing (FDD) and time division duplexing (TDD), and low operating costs with an enhanced end-user environment and simple architecture. For more efficient data processing, the dynamic TDD of the NR system may use a method to change the number of orthogonal frequency division multiplexing (OFDM) symbols that can be used in the uplink and downlink according to the data traffic direction of a cell user. For example, when the downlink traffic of a cell is larger than the uplink traffic, the base station may allocate more downlink OFDM symbols to a slot (or subframe). Information about the slot configuration should be transmitted to the terminal.

[0004] To mitigate the path loss of radio waves in the ultra-high frequency band and increase the transmission distance of radio waves, technologies being discussed for 5G communication systems include beamforming, massive multiple input / output (massive MIMO), full dimension multiple input / output (FD-MIMO), array antenna, analog beamforming, hybrid beamforming that combines analog beamforming and digital beamforming, and large scale antenna technologies. In addition, to improve the system network, technological developments are being carried out for the 5G communication system in areas such as advanced small cells, improved small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device to device communication (D2D), vehicle to everything communication (V2X), wireless backhaul, non-terrestrial network communication (NTN), moving networks, cooperative communication, coordinated multi-points (CoMP), and interference cancellation.Other advanced coding modulation (ACM) methods being developed for 5G systems include hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC), as well as advanced access technologies such as filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA).

[0005] Meanwhile, in a human-centered connected network where humans generate and consume information, the Internet is evolving into the Internet of Things (IoT) network, which exchanges information among distributed components such as objects. Internet of Everything (IoE) technology is also emerging, combining IoT technology with big data processing technology through connections to cloud servers. Implementing IoT requires technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology. As a result, in recent years, technologies such as sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) have been considered for connecting objects. In an IoT environment, intelligent Internet technology (IT) services can be provided that collect and analyze data generated by connected objects to create new value in human life. Through the integration and blending of existing information technology (IT) with various industries, IoT can be applied to areas such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, health management, 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 (M2M) communication, and machine-type communication (MTC) are implemented using techniques such as beamforming, MIMO, and array antennas. The application of Cloud RAN as a big data processing technology described above is an example of the fusion of 5G technology and IoT technology. Generally, mobile communication systems are being developed to provide voice services while guaranteeing user activity.

[0007] However, mobile communication systems have gradually expanded beyond voice services to include data services, and have now been developed to the extent that they provide high-speed data services. However, due to the resource shortage phenomenon in currently available mobile communication systems and users' demand for high-speed services, more advanced mobile communication systems are needed. Summary of the Invention [Problem to be solved by the invention]

[0008] The present specification aims to provide a method and apparatus for transmitting an uplink channel in a wireless communication system. [Means for solving the problem]

[0009] The present specification provides a method and apparatus for transmitting an uplink channel in a wireless communication system.

[0010] In more detail, in a step of transmitting an uplink channel in a wireless communication system, the terminal includes a step of receiving a System Information Block 1 (SIB1) from a base station, a step of transmitting a preamble for a random access procedure to the base station, a step of receiving a Random Access Response (RAR) from the base station in response to the preamble, the random access response including information for scheduling a Physical Uplink Shared Channel (PUSCH) to be transmitted by the terminal to the base station, and a step of transmitting the PUSCH to the base station based on the Random Access Response, wherein the SIB1 includes information on a repetition transmission count candidate set including values ​​for one or more repetition transmission counts for performing repeated transmission of the PUSCH, the random access response includes information indicating one of the values ​​for the one or more repetition transmission counts included in the repetition transmission count candidate set, and the PUSCH is repeatedly transmitted by the one or more values.

[0011] The terminal may further include the steps of receiving downlink control information (DCI) from a base station, the downlink control information (DCI) including information for scheduling a retransmission PUSCH, and repeatedly transmitting the retransmission PUSCH to the base station based on the DCI, wherein the information for scheduling the retransmission PUSCH includes information regarding the number of repetitions of the retransmission PUSCH, the information regarding the number of repetitions of the retransmission PUSCH is included in a HARQ process number field of the DCI, the retransmission PUSCH is the same as the PUSCH, and the DCI is transmitted by the base station if the base station fails to receive the PUSCH transmitted by the terminal.

[0012] a processor for controlling the transceiver; and a system information block (SIB) for transmitting an uplink channel in a wireless communication system, the processor receiving a system information block (SIB) from a base station, transmitting a preamble for a random access procedure to the base station, and receiving a random access response (RAR) from the base station in response to the preamble, the random access response including information for scheduling a physical uplink shared channel (PUSCH) to be transmitted by the terminal to the base station, and transmitting the PUSCH from the base station based on the random access response, the SIB including information on a repetition transmission count candidate set including values ​​for one or more repetition transmission counts for performing repeated transmission of the PUSCH, the random access response including information indicating one of the values ​​for the one or more repetition transmission counts included in the repetition transmission count candidate set, and the PUSCH being repeatedly transmitted by the one or more values.

[0013] The processor receives downlink control information (DCI) including information for scheduling a PUSCH from a base station, and repeatedly transmits the retransmission PUSCH to the base station based on the DCI, wherein the information for scheduling the retransmission PUSCH includes information regarding the number of repetitions of the retransmission PUSCH, the information regarding the number of repetitions of the retransmission PUSCH is included in a HARQ process number field of the DCI, the retransmission PUSCH is the same as the PUSCH, and the DCI is transmitted by the base station if the base station fails to receive the PUSCH transmitted by the terminal.

[0014] The random access response is a Physical Downlink Shared Channel (PDSCH) including an Uplink (UL) grant.

[0015] The information indicating any one of the values ​​is included in at least one of a Time Domain Resource Assignment (TDRA) field, a Modulation Coding Scheme (MCS) field, and a Transmission Power Control (TPC) field of the random access response.

[0016] If the information indicating any one of the values ​​is included in the MCS field, the any one of the values ​​is indicated by one or more Most Significant Bits (MSBs) of the bits of the MCS field.

[0017] If the information indicating any one of the values ​​is included in the TPC field, the any one of the values ​​is indicated by one or more least significant bits (LSBs) of the bits of the TPC field.

[0018] The SIB1 includes at least one of information about the preamble and a RACH occasion, and the PUSCH is transmitted on a resource determined based on at least one of the information about the preamble and the RACH occasion.

[0019] The DCI is scrambled with the TC-RNTI, and the format of the DCI is DCI format 0_0.

[0020] Each of the one or more values ​​for the number of repeated transmissions is a power of two.

[0021] The values ​​for the one or more repeated transmission times are 1, 2, 4, and 8, respectively.

[0022] The random access response includes a frequency hopping flag indicating whether the PUSCH is frequency hopping, and the PUSCH is characterized by performing intra-slot frequency hopping or inter-slot frequency hopping based on one of the values ​​and the frequency hopping flag.

[0023] When any one of the values ​​is 1, if the value of the frequency hopping flag indicates that the PUSCH is frequency hopping, the PUSCH is frequency hopped within a slot, and if the value of the frequency hopping flag indicates that the PUSCH is not frequency hopping, the PUSCH is not frequency hopped.

[0024] When any one of the values ​​is greater than 1, if the value of the frequency hopping flag indicates that the PUSCH is frequency hopping, the PUSCH is frequency hopped between slots, and if the value of the frequency hopping flag indicates that the PUSCH is not frequency hopping, the PUSCH is not frequency hopped.

[0025] The random access response further includes information regarding a resource on which the first repeated transmission of the PUSCH is performed, the information regarding the resource on which the first repeated transmission of the PUSCH is performed being a slot offset value between the resource on which the random access response is received and the resource on which the first repeated transmission of the PUSCH is performed; the SIB1 further includes information regarding a TDD configuration, the information regarding the TDD configuration being information regarding a type of symbol constituting a slot, the type of symbol being any one of a downlink symbol set to be usable for downlink transmission, an uplink symbol set to be usable for uplink transmission, and a flexible symbol not set to the downlink symbol or the uplink symbol; the PUSCH is repeatedly transmitted in slot units; and the resource on which the first repeated transmission of the PUSCH is performed is a resource that is separated from the resource on which the random access response is received by the slot offset value.

[0026] The resource in which the first repeat transmission of the PUSCH is performed is a flexible slot, and repeat transmissions after the first repeat transmission of the PUSCH are performed on uplink slots, the flexible slot is configured to include at least one of the flexible symbols, and all of the uplink slots are configured with the uplink symbols.

[0027] In a method for receiving an uplink channel in a wireless communication system, the method, performed by a base station, includes the steps of: transmitting a system information block 1 (SIB1) to a terminal; receiving a preamble for a random access procedure from the terminal; transmitting a random access response (RAR) to the terminal in response to the preamble; the random access response including information for scheduling a physical uplink shared channel (PUSCH) to be transmitted by the terminal to the base station; and receiving the PUSCH based on the random access response from the terminal, wherein the SIB1 includes information on a repetition transmission count candidate set including values ​​for one or more repetition transmission counts for performing repeated transmission of the PUSCH, the random access response including information indicating one of the values ​​for the one or more repetition transmission counts included in the repetition transmission count candidate set, and the PUSCH is repeatedly transmitted by the one or more values. [Effects of the Invention]

[0028] An object of the present specification is to provide a method for repeatedly transmitting an Msg3 PUSCH in a random access procedure.

[0029] The present specification aims to provide a method for inter-slot frequency hopping of a repeatedly transmitted Msg3 PUSCH.

[0030] The present specification aims to provide a method for determining resources for repeatedly transmitting Msg3 PUSCH.

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

[0032] [Figure 1]FIG. 1 illustrates an example of a wireless frame structure used in a wireless communication system. [Figure 2] FIG. 1 illustrates an example of a downlink (DL) / uplink (UL) slot structure in a wireless communication system. [Figure 3] 1 is a diagram illustrating physical channels used in a 3GPP system and a typical signal transmission method using the physical channels. [Figure 4a] FIG. 1 illustrates an SS / PBCH block for initial cell access in a 3GPP NR system. [Figure 4b] FIG. 1 illustrates an SS / PBCH block for initial cell access in a 3GPP NR system. [Figure 5a] FIG. 1 illustrates a procedure for transmitting control information and control channels in a 3GPP NR system. [Figure 5b] FIG. 1 illustrates a procedure for transmitting control information and control channels in a 3GPP NR system. [Figure 6] FIG. 1 illustrates a control resource set (CORESET) in which a physical downlink control channel (PDCCH) may be transmitted in a 3GPP NR system. [Figure 7] FIG. 1 illustrates a method for configuring a PDCCH search space in a 3GPP NR system. [Figure 8] FIG. 1 is a conceptual diagram illustrating carrier aggregation. [Figure 9] FIG. 1 is a diagram for explaining single-carrier communication and multi-carrier communication. [Figure 10] A diagram showing an example in which a cross-carrier scheduling technique is applied. [Figure 11] 2A and 2B are block diagrams showing the configurations of a terminal and a base station according to an embodiment of the present invention. [Figure 12]1 illustrates a method for scheduling a physical uplink shared channel in the time domain according to an embodiment of the present invention. [Figure 13] 1 illustrates a method for scheduling a physical uplink shared channel in the frequency domain according to an embodiment of the present invention. [Figure 14] 1 illustrates repeated transmission of a physical uplink shared channel according to an embodiment of the present invention. [Figure 15] 1 illustrates a method for scheduling a physical uplink control channel according to an embodiment of the present invention. [Figure 16] 1 illustrates repeated transmission of a physical uplink control channel according to an embodiment of the present invention. [Figure 17] FIG. 10 is a diagram illustrating repeated transmission of Msg3 PUSCH according to one embodiment of the present invention. [Figure 18] FIG. 10 is a diagram illustrating repeated transmission of Msg3 PUSCH using three DMRSs according to one embodiment of the present invention. [Figure 19] FIG. 10 is a diagram illustrating a method for transmitting an Msg3 PUSCH using two DMRSs according to one embodiment of the present invention. [Figure 20] FIG. 10 is a diagram illustrating a method for transmitting an Msg3 PUSCH using two DMRSs according to one embodiment of the present invention. [Figure 21] FIG. 10 is a diagram illustrating a method for transmitting an Msg3 PUSCH using two DMRSs according to one embodiment of the present invention. [Figure 22] FIG. 10 is a diagram illustrating a method for determining the number of modulation symbols for multiplexing uplink control information included in an Msg3 PUSCH according to an embodiment of the present invention. [Figure 23] FIG. 10 is a diagram illustrating a method for determining the number of modulation symbols for multiplexing uplink control information included in an Msg3 PUSCH according to an embodiment of the present invention. [Figure 24] FIG. 10 is a diagram illustrating a method for determining the number of modulation symbols for multiplexing uplink control information included in an Msg3 PUSCH according to an embodiment of the present invention. [Figure 25]FIG. 10 is a diagram illustrating a method for determining the number of modulation symbols for multiplexing uplink control information included in an Msg3 PUSCH according to an embodiment of the present invention. [Figure 26] FIG. 10 is a diagram illustrating a method for determining the number of modulation symbols for multiplexing uplink control information included in an Msg3 PUSCH according to an embodiment of the present invention. [Figure 27] FIG. 10 is a diagram illustrating resources available for repeated transmission of Msg3 PUSCH according to one embodiment of the present invention. [Figure 28] FIG. 10 is a diagram illustrating resources available for repeated transmission of Msg3 PUSCH according to one embodiment of the present invention. [Figure 29] 10 illustrates a method for determining a frequency hopping method according to the number of repeated transmissions of a PUSCH according to an embodiment of the present invention. [Figure 30] 10 is a flowchart illustrating a method for a terminal to transmit an Msg3 PUSCH according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0033] The terms used in this specification are currently widely used and general terms that are possible based on the functions of the present invention. However, the terms may be changed according to the intentions, practices, and the emergence of new technologies of those skilled in the art. In addition, in certain cases, there are terms arbitrarily selected by the applicant, and in this case, their meanings will be explained in the corresponding description of the present specification. Therefore, it is intended to be clear that the terms used in this specification should be analyzed based not only on the names of the terms but also on the substantial meaning of the terms and content throughout this specification.

[0034] Throughout this specification and the claims that follow, when an element is described as being "connected" to another element, the element may be "directly connected" to the other element or may be "electrically connected" to the other element through a third element. Furthermore, unless expressly stated to the contrary, the word "comprising" is understood to imply the inclusion of the stated elements and not the exclusion of any other elements unless otherwise specified. Moreover, limitations such as "equivalent to" or "equivalent to" based on a particular threshold value may be appropriately substituted with "greater than" or "less than," respectively, in some exemplary embodiments.

[0035] The following technologies may be used in various wireless access systems, such as Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), and Single-Carrier FDMA (SC-FDMA). CDMA may be implemented by wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be implemented by wireless technologies such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA may be implemented by wireless technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of Evolved UMTS (EUMTS) that uses Evolved UMTS Terrestrial Radio Access (E-UTRA), and LTE-Advanced (A) is an evolved version of 3GPP LTE. 3GPP New Radio (NR) is a system designed separately from LTE / LTE-A to support enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC), and massive machine type communication (mMTC) services, which are requirements of IMT-2020. For clarity, 3GPP NR will be mainly described, but the technical idea of ​​the present invention is not limited thereto.

[0036] Unless otherwise specified herein, a base station may refer to a next-generation Node B (gNB) as defined in 3GPP NR. Furthermore, unless otherwise specified, a terminal may refer to a user equipment (UE). Hereinafter, for ease of understanding, each content will be described separately as an embodiment, but the embodiments may be used in combination with each other. In this disclosure, a configuration of a terminal may refer to a configuration by a base station. Specifically, a base station may transmit a channel or a signal to a terminal and configure parameter values ​​used in the operation of the terminal or the wireless communication system.

[0037] FIG. 1 illustrates an example of a wireless frame structure used in a wireless communication system.

[0038] Referring to FIG. 1, a wireless frame (or radio frame) used in a 3GPP NR system has a length of 10 ms (Δf max N f / 100)*T c ) In addition, a wireless frame includes 10 subframes (SF) of equal size. max =480*10 3 Hz, N f =4096, T c =1 / (Δf ref *N f,ref ), Δf ref =15*10 3 Hz and N f,ref = 2048. The 10 subframes in one wireless frame may be assigned numbers from 0 to 9. Each subframe has a length of 1 ms and may include one or more slots according to the subcarrier spacing. More specifically, in a 3GPP NR system, the subcarrier spacing that may be used is 15*2 μkHz, and μ can have values ​​of μ=0, 1, 2, 3, 4 as the subcarrier spacing configuration. That is, 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz can be used for the subcarrier spacing. One subframe with a length of 1 ms is 2 μ slots, each of which may be 2 -μ ms. 2 in one subframe μ slots, 0 to 2 each μ In addition, slots in one wireless frame may be assigned numbers from 0 to 10*2. μ The allocated numbers may range from -1 to -1. The time resources may be distinguished by at least one of a wireless frame number (also referred to as a wireless frame index), a subframe number (also referred to as a subframe index), and a slot number (or slot index).

[0039] 2 illustrates an example of a downlink (DL) / uplink (UL) slot structure in a wireless communication system. In particular, FIG. 2 illustrates a resource grid structure for a 3GPP NR system.

[0040] Specifically, Figure 2 shows the structure of a resource grid in a 3GPP NR system. There is one resource grid per antenna port. Referring to Figure 2, a slot includes multiple Orthogonal Frequency Division Multiplexing (OFDM) symbols in the time domain and multiple Resource Blocks (RBs) in the frequency domain. An OFDM symbol also refers to one symbol section. Unless otherwise specified, an OFDM symbol may simply be referred to as a symbol. One RB includes 12 consecutive subcarriers in the frequency domain. Referring to Figure 2, the signal transmitted from each slot is divided into N size,μ grid,x *N RB sc Book subcarrier and N slot symbmay be represented by a resource grid containing N OFDM symbols, where x=DL if the signal is a DL signal and x=UL if the signal is a UL signal. size,μ grid,x represents the number of resource blocks (RBs) according to the subcarrier spacing, which is a component of μ (x is DL or UL), and N slot symb represents the number of OFDM symbols in a slot. RB sc is the number of subcarriers that make up one RB, and N RB sc = 12. Depending on the multiple access scheme, OFDM symbols may be called cyclic shift OFDM (CP-OFDM) symbols or discrete Fourier transform spread OFDM (DFT-s-OFDM) symbols.

[0041] The number of OFDM symbols included in one slot may vary according to the length of the cyclic prefix (CP). For example, in the case of a normal CP, one slot may include 14 OFDM symbols, while in the case of an extended CP, one slot may include 12 OFDM symbols. In a particular embodiment, the extended CP may be used only with 60 kHz subcarrier spacing. For convenience of explanation, in FIG. 2, one slot is configured using 14 OFDM symbols as an example, but the embodiments of the present disclosure may be similarly applied to slots having a different number of OFDM symbols. Referring to FIG. 2, each OFDM symbol is N size,μ grid,x *N RB sc The carrier frequency includes four subcarriers. The subcarrier types can be divided into data subcarriers for data transmission, reference signal subcarriers for transmitting reference signals, and guard bands. The carrier frequency is also called the center frequency (fc).

[0042] One RB is N RB sc A resource may be defined by (e.g., 12) consecutive subcarriers. For reference, a resource configured using one OFDM symbol and one subcarrier may be referred to as a resource element (RE) or tone. Thus, one RB may be defined by N slot symb *N RB sc Each resource element in the resource grid can be uniquely defined within one slot by a pair of indices (k, l), where k ranges from 0 to N in the frequency domain. size,μ grid,x *N RB sc l may be an index ranging from 0 to N in the time domain. slot symb It may be an index that scales down to -1.

[0043] In order for a UE to receive signals from or transmit signals to a base station, the time / frequency of the UE may be synchronized to the time / frequency of the base station, since when the base station and the UE are synchronized, the UE can determine the time and frequency parameters necessary to demodulate DL signals and transmit UL signals at the appropriate times.

[0044] Each symbol of a radio frame used in time division duplex (TDD), i.e., unpaired spectrum, may be configured with at least one of DL symbols, UL symbols, and flexible symbols. In frequency division duplex (FDD), i.e., paired spectrum, a radio frame used as a DL carrier may be configured with DL symbols or flexible symbols, and a radio frame used as a UL carrier may be configured with UL symbols or flexible symbols. DL symbols allow DL transmission but not UL transmission. UL symbols allow UL transmission but not DL transmission. Flexible symbols may be determined to be used as DL or UL according to the signal.

[0045] Information about each symbol type, i.e., information indicating any one of DL symbols, UL symbols, and flexible symbols, can be configured using cell-specific or common radio resource control (RRC) signals. In addition, information about each symbol type can be additionally configured using UE-specific or dedicated RRC signals. The base station notifies i) the duration of the cell-specific slot configuration, ii) the number of slots with only DL symbols from the beginning of the cell-specific slot configuration period, iii) the number of DL symbols from the first symbol of the slot immediately following the slot with only DL symbols, iv) the number of slots with only UL symbols from the end of the cell-specific slot configuration period, and v) the number of UL symbols from the last symbol of the slot immediately preceding the slot with only UL symbols by using cell-specific RRC signals. Here, a symbol that is not configured using either UL symbols or DL ​​symbols is a flexible symbol.

[0046] When information about symbol type is configured using UE-specific RRC signals, the base station can signal whether a flexible symbol is a DL symbol or a UL symbol in the cell-specific RRC signal. In this case, the UE-specific RRC signal cannot change a DL symbol or a UL symbol configured using the cell-specific RRC signal to another symbol type. The UE-specific RRC signal signals the number of DL symbols among the N slot symb symbols of the corresponding slot for each slot, and the number of UL symbols among the N slot symb symbols of the corresponding slot. In this case, the DL symbols of a slot can be continuously configured using the first symbol to the i-th symbol of the slot. In addition, the UL symbols of a slot can be continuously configured using the j-th symbol to the last symbol of the slot (where i < j). Among the slots, a symbol that is not configured using either UL symbols or DL symbols is a flexible symbol.

[0047] The symbol type consisting of the RRC signals as described above is referred to as a semi-static DL / UL configuration. In the semi-static DL / UL configuration consisting of the RRC signals described above, a flexible symbol is indicated as a downlink symbol, an uplink symbol, or a flexible symbol via dynamic SFI (slot format information) transmitted on the physical downlink control channel (PDCCH). At this time, a downlink symbol or an uplink symbol consisting of an RRC signal is not changed to another symbol type. Table 1 illustrates the dynamic SFI indicated by the base station to the terminal.

[0048]

Table 1

[0049] In Table 1, D denotes a downlink symbol, U denotes an uplink symbol, and X denotes a flexible symbol. As shown in Table 1, up to two DL / UL switchings are allowed in one slot.

[0050] FIG. 3 is a diagram illustrating physical channels used in a 3GPP system (e.g., NR) and a general signal transmission method using the physical channels.

[0051] When a UE is powered on or camps on a new cell, the UE performs an initial cell search (S101). Specifically, the UE may synchronize with a BS during the initial cell search. To this end, the UE may receive a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from a base station to synchronize with the base station and obtain information such as a cell ID. The UE may then receive a physical broadcast channel from the base station and obtain broadcast information in the cell.

[0052] Upon completion of the initial cell search, the UE receives a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information in the PDCCH, so that the UE can acquire system information that is more specific than the system information acquired through the initial cell search (S102). Here, the system information acquired by the UE is cell-common system information for the UE to operate correctly at the physical layer in Radio Resource Control (RRC), and is also referred to as remaining system information or system information block (SIB) 1.

[0053] When a terminal first accesses a base station or there are no radio resources for signal transmission (if the terminal is in RRC_IDLE mode), the terminal performs a random access procedure with the base station (S103 to S106). First, the terminal transmits a preamble over a physical random access channel (PRACH) (S103) and receives a random access response (RAR) message for the preamble from the base station over a PDCCH and a corresponding PDSCH (S104). At this time, the preamble in S103 and S104 is described as message 1 (Msg1), and the random access response is described as a response message or message 2 (Msg2). If the terminal receives a valid random access response, the terminal transmits data including its own identifier, etc. to the base station over a physical uplink shared channel (PUSCH) indicated in an uplink grant transmitted from the base station over the PDCCH or PDSCH (S105). At this time, the data including its own identifier, etc. in S105 and the PUSCH including the data are described as message 3 (Msg3). In addition, the PUSCH containing the data is described in message 3 PUSCH (Msg3 PUSCH). Next, the terminal waits to receive a PDCCH as an instruction from the base station to resolve collisions. If the terminal successfully receives the PDCCH via its own identifier and receives the corresponding PDSCH, the random access procedure is terminated in S106. At this time, the PDCCH and PDSCH in S106 are described in message 4 (Msg4). During the random access procedure, the terminal acquires a terminal-specific system required for the terminal to operate correctly in the physical layer in the RRC layer. Once the terminal acquires terminal-specific system information from the RRC layer, the terminal enters RRC_CONNECTED mode.

[0054] The RRC layer is used to generate and manage messages for control between a terminal and a wireless access network (RAN). More specifically, the base station and terminal can perform storage management including broadcasting cell system information required for all terminals in the cell, transmission management of paging messages, mobility management and handover, terminal measurement reporting and control thereof, terminal capability management, and device management at the RRC layer. Generally, the update of signals transmitted at the RRC layer (hereinafter referred to as RRC signals) is longer than the transmission / reception period (i.e., transmission time interval, TTI) at the physical layer, so that RRC signals can be maintained unchanged for a long period.

[0055] After the above-described procedure, the UE receives the PDCCH / PDSCH (S107) and transmits the physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) as a general UL / DL signal transmission procedure (S108). Specifically, the UE may receive downlink control information (DCI) through the PDCCH. The DCI may include control information such as resource allocation information for the UE. The format of the DCI may vary depending on the intended use. The uplink control information (UCI) transmitted by the UE to the base station through the UL includes a DL / UL ACK / NACK signal, a channel quality indicator (CQI), a precoding matrix index (PMI), a rank indicator (RI), etc. Here, the CQI, PMI, and RI may be included in channel state information (CSI). In a 3GPP NR system, a UE may transmit control information, such as the HARQ-ACK and CSI described above, over the PUSCH and / or PUCCH.

[0056] 4a and 4b show SS / PBCH blocks for initial cell access in a 3GPP NR system.

[0057] When powered on or wanting to access a new cell, the UE may acquire time and frequency synchronization with the cell and perform an initial cell search procedure. The UE may acquire the physical cell identity N of the cell during the cell search procedure. cell ID To this end, the UE may receive synchronization signals, such as a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), from the base station and synchronize to the base station. In this case, the UE may obtain information such as a cell identity (ID).

[0058] Referring to Figure 4a, the synchronization signal (SS) will be described in more detail. The synchronization signal can be classified into a PSS and an SSS. The PSS can be used to obtain time-domain and / or frequency-domain synchronization, such as OFDM symbol synchronization and slot synchronization. The SSS can be used to obtain frame synchronization and a cell group ID. Referring to Figure 4a and Table 2, an SS / PBCH block can be configured using 20 consecutive RBs (=240 subcarriers) in the frequency domain and 4 consecutive OFDM symbols in the time domain. In this case, within the SS / PBCH block, the PSS is transmitted in the first OFDM symbol, and the SSS is transmitted in the third OFDM symbol through subcarriers 56 to 182. Here, the lowest subcarrier index of the SS / PBCH block is numbered starting from 0. In the first OFDM symbol in which the PSS is transmitted, the base station does not transmit signals through the remaining subcarriers, i.e., subcarriers 0 to 55 and 183 to 239. In addition, in the third OFDM symbol in which the SSS is transmitted, the base station does not transmit signals through subcarriers 48 to 55 and 183 to 191. The base station transmits a physical broadcast channel (PBCH) through the remaining REs in the SS / PBCH block excluding the above signals.

[0059] [Table 2]

[0060] The SS allows a total of 1008 unique physical layer cell IDs to be grouped into 336 physical layer cell identifier groups, each group specifically including three unique identifiers through the combination of three PSSs and SSSs such that each physical layer cell ID is only part of one physical layer cell identifier group. Thus, the physical layer cell IDs N cellID =3N (1) ID +N (2) ID is an index N ranging from 0 to 335 indicating a physical layer cell identifier group (1) ID and an index N ranging from 0 to 2 indicating a physical layer identifier within the physical layer cell identifier group. (2) ID The UE may detect the PSS and identify one of three unique physical layer identifiers. In addition, the UE may detect the SSS and identify one of 336 physical layer cell IDs associated with the physical layer identifier. In this case, the sequence d of the PSS PSS (n) is as follows:

[0061]

number

[0062] Furthermore, the SSS series d SSS (n) is as follows:

number

[0063] A 10-ms radio frame may be divided into two 5-ms half-frames. Referring to Figure 4b, the slots in which the SS / PBCH blocks are transmitted within each half-frame are described. The slots in which the SS / PBCH blocks are transmitted may be any one of Cases A, B, C, D, and E. In Case A, the subcarrier spacing is 15 kHz, and the start of the SS / PBCH block is the ({2, 8} + 14*n)th symbol. In this case, n = 0 or 1 for carrier frequencies below 3 GHz. Additionally, n = 0, 1, 2, or 3 may be used for carrier frequencies above 3 GHz and below 6 GHz. In Case B, the subcarrier spacing is 30 kHz, and the start of the SS / PBCH block is {4, 8, 16, 20} + 28*n. In this case, n = 0 for carrier frequencies below 3 GHz. Additionally, n = 0 or 1 may be used for carrier frequencies above 3 GHz and below 6 GHz. In Case C, the subcarrier spacing is 30 kHz and the start of the SS / PBCH block is the ({2,8}+14*n)th symbol. In this case, n=0 or 1 for carrier frequencies below 3 GHz. Additionally, n=0, 1, 2, or 3 for carrier frequencies above 3 GHz and below 6 GHz. In Case D, the subcarrier spacing is 120 kHz and the start of the SS / PBCH block is the ({4,8,16,20}+28*n)th symbol. In this case, n=0, 1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, or 18 for carrier frequencies above 6 GHz. In Case E, the subcarrier spacing is 240 kHz and the start of the SS / PBCH block is the ({8,12,16,20,32,36,40,44}+56*n)th symbol. In this case, n=0, 1, 2, 3, 5, 6, 7, 8 for carrier frequencies above 6 GHz.

[0064] 5a and 5b show a procedure for transmitting control information and control channels in a 3GPP NR system. Referring to FIG. 5a, a base station may add a cyclic redundancy check (CRC) masked (e.g., XORed) with a radio network temporary identifier (RNTI) to control information (e.g., downlink control information (DCI)) (S202). The base station may scramble the CRC using an RNTI value determined according to the purpose / target of each control information. The common RNTI used by one or more UEs may include at least one of a system information RNTI (SI-RNTI), a paging RNTI (P-RNTI), a random access RNTI (RA-RNTI), and a transmit power control RNTI (TPC-RNTI). In addition, a UE-specific RNTI may include at least one of a cell temporary RNTI (C-RNTI) and a CS-RNTI. The base station may then perform channel coding (e.g., polar coding) (S204) and then perform rate matching according to the amount of resources used for PDCCH transmission (S206). The base station may then multiplex DCI based on a control channel element (CCE)-based PDCCH structure (S208). Additionally, the base station may apply additional processes, such as scrambling, modulation (e.g., QPSK), and interleaving, to the multiplexed DCI (S210), and then map the DCI to resources to be transmitted. A CCE is a basic resource unit for the PDCCH, and one CCE may include multiple (e.g., 6) resource element groups (REGs). One REG may be configured with multiple (e.g., 12) REs. The number of CCEs used for one PDCCH may be defined as an aggregation level.In a 3GPP NR system, aggregation levels of 1, 2, 4, 8, or 16 may be used. Figure 5b is a diagram relating to CCE aggregation levels and PDCCH multiplexing, showing the type of CCE aggregation level used for one PDCCH and the CCEs transmitted in the control area accordingly.

[0065] FIG. 6 illustrates a control resource set (core set) in which a physical downlink control channel (PDCCH) may be transmitted in a 3GPP NR system.

[0066] A core set is a time-frequency resource within which the PDCCH, i.e., a control signal for the UE, is transmitted. In addition, a search space, which will be described later, may be mapped to a core set. Thus, rather than monitoring all frequency bands for PDCCH reception, the UE may monitor a time-frequency region designated as a core set and decode the PDCCH mapped to the core set. A base station may configure one or more core sets for a UE per cell. A core set may be configured using up to three consecutive symbols on the time axis. Additionally, a core set may be configured in units of six consecutive PRBs on the frequency axis. In the embodiment of FIG. 6, core set #1 is configured using consecutive PRBs, and core sets #2 and #3 are configured using non-consecutive PRBs. A core set may be positioned within any symbol within a slot. For example, in the embodiment of FIG. 6, core set #1 starts in the first symbol of the slot, core set #2 starts in the fifth symbol of the slot, and core set #9 starts in the ninth symbol of the slot.

[0067] FIG. 7 illustrates a method for configuring a PUCCH search space in a 3GPP NR system.

[0068] To transmit a PDCCH to a UE, each core set may have at least one search space. In an embodiment of the present disclosure, a search space is a set of all time-frequency resources (hereinafter referred to as PDCCH candidates) through which the UE's PDCCH can be transmitted. The search space may include a common search space that 3GPP NR UEs are required to search in common, and a terminal-specific or UE-specific search space that a specific UE is required to search. In the common search space, a UE may monitor a PDCCH that all UEs in a cell belonging to the same base station are configured to search in common. In addition, a UE-specific search space may be configured for each UE so that the UE monitors the PDCCH allocated to each UE at different search space positions according to the UE. In the case of a UE-specific search space, the search spaces between UEs may be partially overlapped due to the limited control areas in which the PDCCHs are allocated. Monitoring the PDCCH includes blind decoding to find PDCCH candidates within the search space. When blind decoding is successful, it may be expressed that the PDCCH is (successfully) detected / received, and when blind decoding fails, it may be expressed that the PDCCH is not detected / received or is not successfully detected / received.

[0069] For ease of description, a PDCCH scrambled with a group common (GC) RNTI previously known to one or more UEs to transmit DL control information to one or more UEs is referred to as a group common (GC) PDCCH or a common PDCCH. In addition, a PDCCH scrambled with a terminal-specific RNTI already known by a specific UE to transmit UL or DL ​​scheduling information to that UE is referred to as a UE-specific PDCCH. A common PDCCH may be included in a common search space, and a UE-specific PDCCH may be included in a common search space or a UE-specific PDCCH.

[0070] A base station may signal information related to resource allocation of the transmission channels paging channel (PCH) and downlink shared channel (DL-SCH) (i.e., DL grants) or information related to resource allocation of the uplink shared channel (UL-SCH) and hybrid automatic repeat request (HARQ) (i.e., UL grants) to each UE or a group of UEs via the PDCCH. The base station may transmit PCH transport blocks and DL-SCH transport blocks via the PDSCH. The base station may transmit data excluding specific control information or specific service data via the PDSCH. In addition, a UE may receive data excluding specific control information or specific service data via the PDSCH.

[0071] A base station may transmit a PDCCH to a UE (one or more UEs) including information about where PDSCH data is to be transmitted and how the PDSCH data will be received and decoded by the corresponding UE. For example, assume that the DCI transmitted on a specific PDCCH is CRC masked using an RNTI of "A," and the DCI indicates that the PDSCH is allocated to a radio resource (e.g., a frequency location) of "B," and indicates transmission format information (e.g., transport block size, modulation scheme, coding information, etc.) of "C." The UE monitors the PDCCH using the RNTI information that the UE has. In this case, if a UE performs blind decoding of the PDCCH using the RNTI of "A," the UE receives the PDCCH and, through the received PDCCH information, receives the PDSCH indicated by "B" and "C."

[0072] Table 3 illustrates one embodiment of a physical uplink control channel (PUCCH) used in a wireless communication system.

[0073] [Table 3]

[0074] The PUCCH may be used to transmit the following UL control information (UCI):

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

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

[0077] - Channel State Information (CSI): Feedback information on the DL channel. The UE generates it based on the CSI reference signal (RS) transmitted by the base station. Multiple-input multiple-output (MIMO)-related feedback information includes a rank indicator (RI) and a precoding matrix indicator (PMI). The CSI may be divided into CSI part 1 and CSI part 2 according to the information indicated by the CSI.

[0078] In a 3GPP NR system, five PUCCH formats may be used to support different service scenarios, different channel environments, and frame structures.

[0079] PUCCH format 0 is a format capable of transmitting 1-bit or 2-bit HARQ-ACK information or SR. PUCCH format 0 can be transmitted over one or two OFDM symbols on the time axis and one RB on the frequency axis. When PUCCH format 0 is transmitted in two OFDM symbols, the same sequence on the two symbols may be transmitted over different RBs. In this case, the sequence may be a cyclic shift (CS) sequence of a base sequence used for PUCCH format 0. This allows the UE to obtain frequency diversity gain. Specifically, the terminal bit Bit UCI(M bit =1 or 2) to determine the cyclic shift (CS) value m cs Also, the length 12 basic sequence can be determined by the given CS value m cs Based on this, the cyclically shifted sequence can be mapped to 12 REs of one OFDM symbol and one RB and transmitted. bit = 1, one bit UCI 0 and 1 can be mapped to two cyclic shifted sequences, respectively, with a difference in cyclic shift value of 6. bit = 2, the 2-bit UCI 00, 01, 11, 10 can be mapped to four cyclic shifted sequences with a cyclic shift value difference of 3, respectively.

[0080] PUCCH format 1 carries 1-bit or 2-bit HARQ-ACK information or SR. PUCCH format 1 is transmitted using consecutive 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, bit The UCI with M = 1 is modulated by BPSK. bitThe UCI, where d(0) = 2, is modulated using quadrature phase shift keying (QPSK). The modulated complex-valued symbol d(0) is multiplied by a sequence of length 12 to obtain a signal. The terminal spreads the obtained signal using a time-domain orthogonal cover code (OCC) on even-numbered OFDM symbols assigned to PUCCH format 1 and transmits it. In PUCCH format 1, the maximum number of different terminals that can be multiplexed in the same RB is determined according to the length of the OCC used. In odd-numbered OFDM symbols of PUCCH format 1, a demodulation reference signal (DMRS) is spread using OCC and mapped.

[0081] PUCCH format 2 can deliver UCI exceeding two bits. PUCCH format 2 can be transmitted over one or two OFDM symbols on the time axis and one or more RBs on the frequency axis. When PUCCH format 2 is transmitted in two OFDM symbols, the sequences transmitted in different RBs over the two OFDM symbols may be identical to each other. Here, the sequence is a sequence of modulated complex-valued symbols d(0),...,d(M symbol -1), where M symbol is M bit / 2. Through this, the UE may obtain frequency diversity gain. More specifically, M bit Bit UCI(M bit >2) is bit-level scrambled, QPSK modulated, and mapped to RBs of one or two OFDM symbols, where the number of RBs may be one of 1 to 16. PUCCH format 3 or PUCCH format 4 may deliver UCI exceeding 2 bits. PUCCH format 3 or PUCCH format 4 may be transmitted over consecutive 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 may be one of 4 to 14. Specifically, the UE may transmit M-ary PUCCH using π / 2-2 phase shift keying (BPSK) or QPSK. bit The complex-valued symbols d(0) to d(M symb -1) where, when π / 2-BPSK is used, M symb =M bit and when using QPSK, M symb =M bit / 2. The UE does not need to apply block-wise spreading to PUCCH format 3. However, the UE may apply block-wise spreading to one RB (i.e., 12 subcarriers) using PreDFT-OCC of length 12, such that PUCCH format 4 may have a multiplexing capacity of 2 or 4. The UE performs transmit precoding (or DFT precoding) on ​​the spread signal, maps it to each RE, and transmits the spread signal.

[0082] In this case, the number of RBs occupied by PUCCH format 2, PUCCH format 3, or PUCCH format 4 may be determined according to the length and maximum code rate of the UCI transmitted by the UE. When the UE uses PUCCH format 2, the UE may transmit HARQ-ACK information and CSI information together over the PUCCH. When the number of RBs that the UE can transmit is greater than the maximum number of RBs that PUCCH format 2, PUCCH format 3, or PUCCH format 4 can use, the UE may transmit only the remaining UCI information without transmitting some of the UCI information according to the priority of the UCI information.

[0083] PUCCH Format 1, PUCCH Format 3, or PUCCH Format 4 may be configured through RRC signaling to indicate frequency hopping within a slot. When frequency hopping is configured, the index of the RB to be frequency hopped may be configured using RRC signaling. When PUCCH Format 1, PUCCH Format 3, or PUCCH Format 4 is transmitted over N OFDM symbols on the time axis, the first hop may have floor(N / 2) OFDM symbols, and the second hop may have ceil(N / 2) OFDM symbols.

[0084] PUCCH Format 1, PUCCH Format 3, or PUCCH Format 4 may be configured to be repeatedly transmitted in multiple slots. In this case, the number K of slots in which the PUCCH is repeatedly transmitted may be configured by RRC signaling. The repeatedly transmitted PUCCH must start at a fixed OFDM symbol in each slot and must have a constant length. When one of the OFDM symbols of a slot in which the UE should transmit the PUCCH is indicated as a DL symbol by RRC signaling, the UE may not transmit the PUCCH in the corresponding slot and may delay transmission of the PUCCH until the next slot for transmitting the PUCCH.

[0085] Meanwhile, in a 3GPP NR system, a terminal can transmit and receive using a bandwidth smaller than or equal to the bandwidth of a carrier (or cell). To this end, the terminal may be configured with a bandwidth part (BWP) consisting of a contiguous portion of the carrier's bandwidth. A terminal operating according to TDD or using an unpaired spectrum may be configured with up to four DL / UL BWP pairs per carrier (or cell). The terminal can also activate one DL / UL BWP pair. A terminal operating according to FDD or using a paired spectrum may be configured with up to four DL BWPs per downlink carrier (or cell) and up to four UL BWPs per uplink carrier (or cell). The terminal can activate one DL BWP and one UL BWP per carrier (or cell). The terminal does not need to receive or transmit on time-frequency resources other than the activated BWPs. An activated BWP can be referred to as an active BWP.

[0086] A base station can indicate to a terminal which BWPs among configured BWPs are activated using downlink control information (DCI). The BWP indicated in the DCI is activated, and other configured BWPs are deactivated. In a carrier (or cell) operating in TDD, the base station can include a bandwidth part indicator (BPI) indicating the activated BWP in the DCI scheduling a PDSCH or a PUSCH to change the DL / UL BWP pair of the terminal. The terminal can receive the DCI scheduling a PDSCH or a PUSCH and identify the activated DL / UL BWP pair based on the BPI. In a downlink carrier (or cell) operating in FDD, the base station can include a BPI indicating the activated BWP in the DCI scheduling a PDSCH to change the DL BWP of the terminal. In an uplink carrier (or cell) operating in FDD, the base station can include a BPI indicating the activated BWP in the DCI scheduling a PDSCH to change the UL BWP of the terminal.

[0087] FIG. 8 is a conceptual diagram illustrating carrier aggregation.

[0088] In this method, a UE uses multiple frequency blocks or cells (in a logical sense) configured using UL resources (or component carriers) and / or DL ​​resources (or component carriers) as one large logical frequency band to achieve this. One component carrier may also be referred to as a primary cell (PCell) or a secondary cell (SCell), or a primary SCell (PScell). However, hereinafter, the term "component carrier" will be used for convenience of explanation.

[0089] Referring to Figure 8, as an example of a 3GPP NR system, the overall system band may include up to 16 component carriers, and each component carrier may have a bandwidth of up to 400 MHz. A component carrier may include one or more physically contiguous subcarriers. Although Figure 8 shows each of the component carriers having the same bandwidth, this is merely an example, and each component carrier may have a different bandwidth. Also, although the component carriers are shown as being adjacent to each other on the frequency axis, the drawing is shown in a logical concept, and the component carriers may be physically adjacent to each other or spaced apart.

[0090] A different center frequency may be used for each component carrier. Also, one common center frequency may be used for physically adjacent component carriers. In the embodiment of Figure 8, assuming that all component carriers are physically adjacent, center frequency A may be used for all component carriers. Furthermore, assuming that the respective component carriers are not physically adjacent to each other, center frequency A and center frequency B may be used for each of the component carriers.

[0091] When the overall system band is expanded by carrier aggregation, the frequency band used for communication with each UE may be specified in component carrier units. UE A may use the overall system band of 100 MHz and perform communication using all five component carriers. UEs B1 to B5 may use only a 20 MHz bandwidth and perform communication using one component carrier. UEs C1 and C2 may use a 40 MHz bandwidth and each perform communication using two component carriers. The example in FIG. 8 shows a case where UE C1 uses two non-adjacent component carriers and UE C2 uses two adjacent component carriers.

[0092] 9A and 9B are diagrams for explaining single-carrier communication and multi-carrier communication. Specifically, FIG. 9A shows a single-carrier subframe structure, and FIG. 9B shows a multi-carrier subframe structure.

[0093] Referring to FIG. 9(a), in FDD mode, a typical wireless communication system may transmit or receive data through one DL band and one UL band corresponding thereto. In another specific embodiment, in TDD mode, the wireless communication system may divide a radio frame into UL time units and DL time units in the time domain and transmit or receive data through the UL / DL time units. Referring to FIG. 9(b), three 20 MHz component carriers (CCs) may be aggregated into UL and DL so that a 60 MHz bandwidth can be supported. The CCs may or may not be adjacent to each other in the frequency domain. Although FIG. 9(b) illustrates a case where the bandwidth of the UL CC and the bandwidth of the DL CC are identical and symmetrical, the bandwidth of each CC may be determined independently. In addition, asymmetric carrier aggregation, in which the number of UL CCs and DL CCs differs, is possible. The DL / UL CC allocated / configured to a specific UE through RRC may be referred to as the serving DL / UL CC of the specific UE.

[0094] A base station may communicate with a UE by activating some or all of the UE's serving CCs or deactivating some CCs. The base station can change the CCs to be activated / deactivated and the number of CCs to be activated / deactivated. When a base station allocates CCs available to a UE as cell-specific or UE-specific, at least one of the allocated CCs may be deactivated unless the CC allocation for the UE is completely reconfigured or the UE is handed over. A CC that is not deactivated by the UE is called a Primary CC (PCC) or a Primary Cell (PCell), and a CC that the base station can activate / deactivate freely is called a Secondary CC (SCC) or a Secondary Cell (SCell).

[0095] On the other hand, 3GPP NR uses the concept that a cell manages radio resources. A cell is defined as a combination of DL resources and UL resources, i.e., a combination of DL CC and UL CC. A cell can be configured with only DL resources or a combination of DL resources and UL resources. When carrier aggregation is supported, the association between the carrier frequency of DL resources (i.e., DL CC) and the carrier frequency of UL resources (i.e., UL CC) may be 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 an SCell. A carrier corresponding to a PCell in the DL is a DL PCC, and a carrier corresponding to a PCell in the UL is a UL PCC. Similarly, a carrier corresponding to an SCell in the DL is a DL SCC, and a carrier corresponding to an SCell in the UL is a UL SCC. According to UE capabilities, a serving cell can be configured with one PCell and zero or more SCells. For a UE that is in RRC_CONNECTED state but is not configured for or does not support carrier aggregation, there is only one serving cell configured with only a PCell.

[0096] As mentioned above, the term "cell" used in carrier aggregation is distinguished from the term "cell" which refers to several geographical areas for which communication services are provided by one base station or one antenna group. That is, one component carrier may also be referred to as a scheduling cell, scheduled cell, primary cell (PCell), secondary cell (SCell), or primary SCell (PScell). However, to distinguish between cells which refer to several geographical areas and cells of carrier aggregation, in this disclosure, cells of carrier aggregation are referred to as CCs, and cells of geographical areas are referred to as cells.

[0097] 10 illustrates an example in which a cross-carrier scheduling technique is applied. When cross-carrier scheduling is configured, a control channel transmitted over a first CC may schedule a data channel transmitted over the first CC or a second CC using a carrier indicator field (CIF). The CIF is included in the DCI. In other words, a scheduling cell is configured, and a DL grant / UL grant transmitted in the PDCCH area of ​​the scheduling cell schedules the PDSCH / PUSCH of the scheduled cell. That is, a search area for multiple component carriers exists in the PDCCH area of ​​the scheduling cell. A PCell may essentially be the scheduling cell, and a specific SCell may be designated as the scheduling cell by higher layers.

[0098] In the embodiment of FIG. 10, it is assumed that three DL CCs are merged. Here, it is assumed that DL component carrier #0 is a DL PCC (or PCell), and DL component carrier #1 and DL component carrier #2 are DL SCCs (or SCells). In addition, it is assumed that the DL PCC is configured as a PDCCH monitoring CC. When cross-carrier scheduling is not configured by UE-specific (or UE group-specific or cell-specific) higher layer signaling, the CIF is disabled, and each DL CC can transmit only a PDCCH for scheduling its PDSCH without using a CIF according to the NR PDCCH rules (non-cross-carrier scheduling, self-carrier scheduling). On the other hand, when cross-carrier scheduling is configured by UE-specific (or UE group-specific or cell-specific) higher layer signaling, the CIF is enabled, and a specific CC (e.g., a DL PCC) may transmit not only a PDCCH for scheduling a PDSCH of DL CC A using the CIF, but also a PDCCH for scheduling a PDSCH of another CC (cross-carrier scheduling). On the other hand, the PDCCH is not transmitted in another DL CC. Thus, the UE monitors either the PDCCH without a CIF to receive a self-carrier scheduled PDSCH or the PDCCH with a CIF to receive a cross-carrier scheduled PDSCH, depending on whether cross-carrier scheduling is configured for the UE.

[0099] 9 and 10 show the subframe structure of a 3GPP LTE-A system, and the same or similar configurations may be applied to a 3GPP NR system, except that in a 3GPP NR system, the subframes in FIGS. 9 and 10 may be replaced with slots.

[0100] FIG. 11 is a block diagram illustrating the configuration of a terminal and a base station according to an embodiment of the present disclosure.

[0101] In the embodiments of the present disclosure, the terminal may be embodied as various wireless communication devices or computer devices that ensure portability and mobility. The terminal may also be referred to as User Equipment (UE), Station (STA), Mobile Subscriber (MS), etc. In addition, in the embodiments of the present disclosure, the base station controls and manages cells (e.g., macrocells, femtocells, picocells, etc.) corresponding to a service area, and may have functions such as signal transmission, channel assignment, channel monitoring, self-diagnosis, and relaying. The base station may also be referred to as a next generation Node B (gNB) or Access Point (AP), etc.

[0102] As shown, a terminal 100 according to one embodiment of the present disclosure may include a processor 110 , a communication module 120 , a memory 130 , a user interface 140 , and a display unit 150 .

[0103] First, the processor 110 can execute various instructions or programs to process data within the terminal 100. The processor 110 can also control the overall operation of the terminal 100, including each unit, and control data transmission and reception between the units. Here, the processor 110 may be configured to perform operations according to the embodiments described in this disclosure. For example, the processor 110 can receive slot configuration information, determine a slot configuration based on the received information, and perform communication according to the determined slot configuration.

[0104] Next, the communication module 120 may be an integrated module that performs wireless communication using a wireless communication network and wireless LAN connection using a wireless LAN. To this end, the communication module 120 may include multiple network interface cards (NICs) such as cellular communication interface cards 121 and 122 and an unlicensed band communication interface card 123, either built-in or external. Although the communication module 120 is shown as an integrated module in the figure, each network interface card may be independently arranged depending on the circuit configuration or application, unlike the drawing.

[0105] The cellular communication interface card 121 can transmit and receive wireless signals to and from at least one of the base station 200, an external device, and a server using a mobile communication network, and can provide 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 can include at least one NIC module using a frequency band below 6 GHz. The at least one NIC module of the cellular communication interface card 121 can independently perform cellular communication with at least one of the base station 200, an external device, and a server in accordance with a cellular communication standard or protocol for the frequency band below 6 GHz supported by the NIC module.

[0106] The cellular communication interface card 122 transmits and receives wireless signals to and from at least one of the base station 200, the external device, and the server using a mobile communication network, and can provide cellular communication services using the second frequency band based on instructions from the processor 110. According to one embodiment, the cellular communication interface card 122 can include at least one NIC module using a frequency band above 6 GHz. The at least one NIC module of the cellular communication interface card 122 can independently perform cellular communication with at least one of the base station 200, the external device, and the server in accordance with a cellular communication standard or protocol for the frequency band above 6 GHz supported by the NIC module.

[0107] The unlicensed band communication interface card 123 transmits and receives wireless signals to and from at least one of the base station 200, an external device, and a server using a third frequency band, which is an unlicensed band, and provides unlicensed band communication services based on instructions from the processor 110. The unlicensed band communication interface card 123 may include at least one NIC module using an unlicensed band. For example, the unlicensed band may be 2.4 GHz, 5 GHz, 6 GHz, 7 GHz, or the 5 GHz band, which is equal to or greater than 52.6 GHz. The at least one NIC module of the unlicensed band communication interface card 123 may independently or dependently communicate with at least one of the base station 200, an external device, and a server in accordance with the unlicensed band communication standard or protocol of the frequency band supported by the NIC module.

[0108] Next, the memory 130 stores control programs and various data used by the terminal 100. Such control programs may include predetermined programs required for the terminal 100 to perform wireless communication with at least one of the base station 200, an external device, and a server.

[0109] Next, the user interface 140 includes various types of input / output means provided in the terminal 100. That is, the user interface 140 can receive user input using various input means, and the processor 110 can control the terminal 100 based on the received user input. Also, the user interface 140 can perform output based on instructions from the processor 110 using various output means.

[0110] The display unit 150 then outputs various images to a display screen, and can display various display objects, such as content executed by the processor 110 or a user interface based on a control instruction of the processor 110.

[0111] Furthermore, the base station 200 according to an embodiment of the present disclosure may include a processor 210, a communication module 220, and a memory 230.

[0112] First, the processor 210 can execute various instructions or programs to process data within the base station 200. The processor 210 can also control the overall operation of each unit of the base station 200 and control data transmission and reception between the units. Here, the processor 210 may be configured to perform operations according to the embodiments described in this disclosure. For example, the processor 210 can signal slot configuration information and perform communication according to the signaled slot configuration.

[0113] Next, the communication module 220 may be an integrated module that performs wireless communication using a wireless communication network and wireless LAN connection using a wireless LAN. To this end, the communication module 220 may include multiple network interface cards, such as cellular communication interface cards 221 and 222 and an unlicensed band communication interface card 223, in an internal or external form. Although the communication module 220 is shown as an integrated module in the figure, each network interface card may be independently arranged depending on the circuit configuration or application, unlike the drawing.

[0114] The cellular communication interface card 221 transmits and receives wireless signals to and from at least one of the terminal 100, the external device, and the server using a mobile communication network, and can provide cellular communication services using the first frequency band based on instructions from the processor 210. According to one embodiment, the cellular communication interface card 221 can include at least one NIC module using a frequency band below 6 GHz. The at least one NIC module of the cellular communication interface card 221 can independently perform cellular communication with at least one of the terminal 100, the external device, and the server in accordance with a cellular communication standard or protocol for the frequency band below 6 GHz supported by the NIC module.

[0115] The cellular communication interface card 222 can transmit and receive wireless signals to and from at least one of the terminal 100, an external device, and a server using a mobile communication network, and can provide cellular communication services using the second frequency band based on instructions from the processor 210. According to one embodiment, the cellular communication interface card 222 can include at least one NIC module using a frequency band above 6 GHz. The at least one NIC module of the cellular communication interface card 222 can independently perform cellular communication with at least one of the terminal 100, an external device, and a server in accordance with a cellular communication standard or protocol for the frequency band above 6 GHz supported by the NIC module.

[0116] The unlicensed band communication interface card 223 transmits and receives wireless signals to and from at least one of the terminal 100, an external device, and a server using a third frequency band, which is an unlicensed band, and provides unlicensed band communication services based on instructions from the processor 210. The unlicensed band communication interface card 223 may include at least one NIC module using an unlicensed band. For example, the unlicensed band may be 2.4 GHz, 5 GHz, 6 GHz, 7 GHz, or the 5 GHz band, which is equal to or greater than 52.6 GHz. The at least one NIC module of the unlicensed band communication interface card 223 may perform wireless communication with at least one of the terminal 100, an external device, and a server, independently or dependently, in accordance with the unlicensed band communication standard or protocol of the frequency band supported by the NIC module.

[0117] The terminal 100 and base station 200 shown in FIG. 11 are block diagrams according to an embodiment of the present invention, and the separated blocks indicate logically distinct device elements. Therefore, the above-described device elements may be implemented as a single chip or multiple chips depending on the device design. In addition, some components of the terminal 100, such as the user interface 140 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 further provided in the base station 200 as necessary.

[0118] FIG. 12 illustrates a method for scheduling a physical uplink shared channel in the time domain according to an embodiment of the present invention.

[0119] A terminal can transmit uplink data to a base station via a PUSCH. The base station can schedule the terminal to transmit uplink data using the PUSCH (PUSCH scheduling). i) In a dynamic grant (DG) method, the base station can perform PUSCH scheduling using DCI included in a PDCCH. Or, ii) in a configured grant (CG) method, the terminal can transmit uplink data to the base station via a PUSCH according to resources and a transmission method that the base station pre-configures in the terminal.

[0120] In this case, the DCI included in the PDCCH may include PUSCH scheduling information. For example, the DCI may include information on the time domain (time-domain resource assignment, TDRA) and information on the frequency domain (frequency-domain resource assignment, FDRA). The UE may receive the DCI transmitted in the control resource set and search space and perform an operation indicated by the DCI (e.g., uplink data transmission using the PUSCH). In this case, the format of the DCI for PUSCH scheduling may be DCI formats 0_0, 0_1, and 0_2. The DCI of DCI formats 0_0, 0_1, and 0_2 may be configured to include a TDRA field including time-domain information of the PUSCH. In this case, the time-domain information may include K2, which is an offset value between a slot in which the base station transmits the PDCCH and a slot in which the UE transmits the PUSCH. In addition, the DCI may include a Start and Length Indication Value (SLIV), which is a value obtained by jointly coding the start symbol index (S) of the PUSCH and the symbol length (L, number) of the PUSCH within the slot indicated by K2. When a UE receives DCI in slot n, the slot in which the PUSCH is scheduled may be floor(n*2μPUSCH / n*2μPDCCH)+K2 slots. μPUSCH and μPDCCH may refer to the subcarrier spacing (SCS) of the cell in which the PUSCH is scheduled and the cell in which the UE receives the PDCCH, respectively. floor(x) is a function that returns the largest integer among integers equal to or smaller than x. In this specification, slot n may refer to the slot indexed with index n.

[0121] 12(a), the subcarrier spacing of the cell in which the UE receives the PDCCH and the cell in which the PUSCH is scheduled may be the same. In this case, if the UE receives the PDCCH in slot n and K2 is indicated as 4, the slot in which the PUSCH is scheduled may be slot n+K2, i.e., slot n+4.

[0122] There are two types of mapping types for scheduling PUSCH: PUSCH mapping type A and PUSCH mapping type B. The starting symbol index of the PUSCH and the range of values ​​that can be used for SLIV may vary depending on the PUSCH mapping type. PUSCH mapping type A only allows resource allocation including a DMRS symbol, and the DMRS symbol may be located at the third or fourth symbol of a slot depending on the value specified by a higher layer. That is, for PUSCH mapping type A, the starting symbol index (S) of the PUSCH is 0, and the length (L) of the PUSCH may have any value from 4 to 14 (12 for extended CP) depending on the DMRS symbol position. For PUSCH mapping type B, the first symbol of the PUSCH may be a DMRS symbol. Therefore, S may have any value from 0 to 13 (11 for extended CP), and L may have any value from 1 to 14 (12 for extended CP). Also, one PUSCH must not cross a slot boundary, and the sum of S and L must be less than or equal to 14 (12 for extended CP).

[0123] 12(b), the base station can schedule PUSCH mapping type A in which the third symbol is a DMRS symbol, the start symbol index (S) is 0, and the length (L) is 7, PUSCH mapping type A in which the fourth symbol is a DMRS symbol, the start symbol index (S) is 0, and the length (L) is 7, and PUSCH mapping type B in which the first symbol is a DMRS symbol, the start symbol index (S) is 5, and the length (L) is 5. In this case, the frequency domain information of the PUSCH indicated in the FDRA field of DCI formats 0_0, 0_1, and 0_2 is divided into two types depending on the frequency resource allocation type.

[0124] FIG. 13 illustrates a method for scheduling a physical uplink shared channel in the frequency domain according to an embodiment of the present invention.

[0125] Hereinafter, frequency resource allocation types will be described with reference to FIG.

[0126] i) The first type, frequency resource allocation type 0 (type 0), may be a type in which a certain number of PRBs are bundled to form an RBG according to the number of RBs included in a BWP configured in a terminal, and whether an RBG is used may be indicated using a bitmap per RBG. That is, the terminal may determine whether a corresponding RBG is used using a bitmap transmitted from a base station. The number of PRBs included in one RBG may be configured from a higher layer, and the more RBs included in the BWP configured in a terminal, the more PRBs may be configured. Referring to FIG. 13(a), the BWP size configured in a terminal is 72 PRBs, and one RBG may be composed of 4 PRBs. In this case, the terminal may determine that four PRBs are one RBG in ascending order starting from PRB0, and each RBG may be indexed starting from 0. That is, an RBG consisting of PRBs PRB0 to PRB3 may be indexed as RBG0, and an RBG consisting of PRBs PRB4 to PRB7 may be indexed as RBG1. RBGs may be indexed up to RBG17 in the same manner. In this case, the base station transmits a total of 18 bits, one bit (0 or 1) for each RBG, to the terminal, and the terminal can determine whether the PRBs constituting the corresponding RBG are used based on the received 18 bits. If the bit value is 0, the terminal can determine that a PUSCH is not scheduled for any of the PRBs constituting the corresponding RBG. If the bit value is 1, the terminal can determine that a PUSCH is scheduled for all PRBs in the corresponding RBG. In this case, the bit values ​​may be reversed. ii) The second type, frequency resource allocation type 1, may indicate information about consecutive PRBs allocated according to the size of the terminal's initial BWP or active BWP. The information of the consecutive PRBs may be a resource indication value (RIV) in which the start index (S) and length (L) of the consecutive PRBs are jointly coded.13(b), when the BWP size of a terminal is 50 PRBs and PUSCH is scheduled for PRB2 to PRB11 among the 50 PRBs, the start index of the consecutive PRBs may be 2 and the length may be 10. That is, the terminal can determine the start index and length of the consecutive PRBs for which PUSCH is scheduled based on the RIV value received from the base station. Specifically, the RIV is N. size BWP *(L-1)+S. size BWP may be the size of the BWP configured in the terminal. For example, if the RIV value received by the terminal is 452, it is calculated as 452 = 50 * (10 - 1) + 2, so the terminal can determine that the start index of the consecutive PRBs for which the PUSCH is scheduled is 2 and the length is 10.

[0127] By using DCI of DCI formats 0_1 and 0_2 that schedules the PUSCH, the terminal may be configured by a higher layer to use only one of the two frequency resource allocation types described above or to dynamically use both types. When the terminal is configured to dynamically use two types, the terminal can determine the type by using the most significant bit (MSB) of the FDRA field of the DCI.

[0128] There may be an uplink shared channel transmission method based on a configured grant for URLLC transmission, etc. The uplink shared channel transmission method based on a configured grant may be described as grant-free transmission. The uplink shared channel transmission method based on a configured grant may be a method in which, if a base station configures resources available for uplink transmission to a terminal through a higher layer (i.e., RRC signaling), the terminal transmits the uplink shared channel using the configured resources. The uplink shared channel transmission method based on a configured grant may be classified into two types depending on whether the DCI indicates activation or release. i) Type 1 uplink shared channel transmission method based on a configured grant may be a method in which a resource and a transmission method are configured in advance by a higher layer. ii) Type 2 uplink shared channel transmission method based on a configured grant may be a method in which grant-based transmission configured by a higher layer is configured, and a resource and a method for actual transmission are configured by the DCI.

[0129] The uplink transmission method based on the configured grant can support URLLC transmission. Therefore, to ensure high reliability, uplink transmission may be repeated over multiple slots. In this case, the RV (redundancy version) sequence may be one of {0,0,0,0}, {0,2,3,1}, and {0,3,0,3}, and an RV corresponding to the mod(n-1, 4)+1 value may be used in the n-th repeated transmission. That is, an RV corresponding to the remainder obtained by dividing n-1 by 4 and adding 1 may be used. In addition, a terminal configured to repeatedly transmit an uplink channel can only start repeated transmission in a slot where the RV value is 0. However, if the RV sequence is {0,0,0,0} and the uplink channel is configured to be repeatedly transmitted over eight slots, the terminal cannot start repeated transmission in the eighth slot. The UE may terminate the repeated transmission when the number of repeated transmissions set by the upper layer is reached or the period is exceeded, or when an UL grant having the same HARQ process ID is received. The UL grant may refer to DCI scheduling a PUSCH.

[0130] As described above, in order to improve the reliability of PUSCH transmission / reception between a base station and a terminal in a wireless communication system, the base station can configure the terminal to repeatedly transmit the PUSCH.

[0131] FIG. 14 illustrates repeated transmission of a physical uplink shared channel according to an embodiment of the present invention.

[0132] There are two types of PUSCH repeat transmission performed by the terminal. i) First, PUSCH repeat transmission type A will be described. When the terminal receives DCI of DCI format 0_1 ​​or 0_2 included in a PDCCH scheduling PUSCH from the base station, the terminal can repeatedly transmit the PUSCH over K consecutive slots. The value of K may be set by a higher layer or may be a value included in the TDRA field of the DCI and set to the terminal. For example, referring to FIG. 14(a), the terminal can receive a PDCCH scheduling PUSCH in slot n, and the value of K2 may be set from the DCI included in the received PDCCH. In this case, if the value of K2 is 2 and the value of K is 4, the terminal can start PUSCH repeat transmission in slot n+K2 and repeatedly transmit PUSCH up to slot n+K2+K-1. That is, the terminal starts PUSCH repeat transmission at n+2 and repeatedly transmits PUSCH up to n+5. In this case, the time and frequency resources on which the PUSCH is transmitted in each slot may be the same as those indicated by the DCI. That is, the PUSCH may be transmitted in the same symbol and PRB(s) within the slot. ii) Next, PUSCH repetition transmission type B will be described. PUSCH repetition transmission type B may be used by the UE to repeatedly transmit a PUSCH with low latency to meet requirements of URLLC, etc. The UE may be configured with the symbol (S) at which the PUSCH repetition transmission starts and the length (L) of the PUSCH to be repeatedly transmitted in the TDRA field of the DCI transmitted by the base station. In this case, the start symbol (S) and length (L) may be for a nominal PUSCH temporarily determined, rather than for a PUSCH actually transmitted by the UE. There may not be another symbol between nominal PUSCHs configured to be repeatedly transmitted. That is, the nominal PUSCHs may be consecutive in the time domain. The UE can determine the actual PUSCH from the nominal PUSCH. One nominal PUSCH may be determined as one or more actual PUSCHs. The base station can configure unavailable symbols in PUSCH repetition transmission type B in the terminal.Symbols that cannot be used in PUSCH repetition transmission type B may be referred to as invalid symbols. The UE may exclude invalid symbols from resources configured for transmitting the nominal PUSCH. As described above, the nominal PUSCH is configured to be repeatedly transmitted on consecutive symbols. However, if invalid symbols are excluded, the resources for nominal PUSCH transmission become discontinuous. The actual PUSCH may be configured to be transmitted on consecutive symbols configured for one nominal PUSCH transmission, excluding the invalid symbols. In this case, if consecutive symbols cross a slot boundary, the actual PUSCH that is actually transmitted may be divided based on the slot boundary. The invalid symbols may include downlink symbols configured for the UE by the base station. Referring to FIG. 14(b), the UE may be scheduled for a 5-symbol long PUSCH transmission starting from the 12th symbol of the first slot (slot n), and four Type B repetition transmissions may be configured. In this case, resources scheduled for the first nominal PUSCH (nominal #1) may include symbols (n, 11), (n, 12), (n, 13), (n+1, 0), and (n+1, 1). Resources scheduled for the second nominal PUSCH (nominal #2) may include symbols (n+1, 2), (n+1, 3), (n+1, 4), (n+1, 5), and (n+1, 6). Resources scheduled for the third nominal PUSCH (nominal #3) may include symbols (n+1, 7), (n+1, 8), (n+1, 9), (n+1, 10), and (n+1, 11). The scheduled resources for the fourth nominal PUSCH (nominal#4) can include symbols (n+1,12), (n+1,13), (n+2,0), (n+2,1), and (n+2,2). Here, symbol (n,k) refers to symbol k in slot n. That is, k can range from 0 to 13 for a normal CP, and can range from 0 to 11 for an extended CP.Ineffective symbols may be set to symbols 6 and 7 of slot n+1. In this case, the last symbol of the second nominal PUSCH (nominal #2) may be excluded, and the first symbol of the third nominal PUSCH (nominal #3) may be excluded to determine the actual PUSCH. The first nominal PUSCH (nominal #1) may be divided into two actually transmitted actual PUSCHs (actual #1 and actual #2) by the slot boundary. The second nominal PUSCH (nominal #2) and the third nominal PUSCH (nominal #3) may be combined into one actual PUSCH (actual #3 and actual #4) by combining consecutive symbols excluding ineffective symbols. Finally, the fourth nominal PUSCH (nominal #4) is divided into two actually transmitted (actual) PUSCHs (actual #5 and actual #6) by the slot boundary. The terminal finally transmits the PUSCH to be actually transmitted. One actual PUSCH must include at least one DMRS symbol. Therefore, when PUSCH repetition transmission type B is configured, if the total length of the actual PUSCH is one symbol, such actual PUSCH may be omitted without being transmitted. This is because the actual PUSCH consisting of one symbol cannot include any information other than DMRS.

[0133] To obtain diversity gain in the frequency domain, frequency hopping may be configured for uplink channel transmission.

[0134] In PUSCH repetition transmission type A, either intra-slot frequency hopping, in which frequency hopping is performed within a slot, or inter-slot frequency hopping, in which frequency hopping is performed for each slot, may be configured in the UE. If intra-slot frequency hopping is configured in the UE, the UE divides the PUSCH into two in the time domain in the slot in which the PUSCH is transmitted, and transmits one half using a scheduled PRB and the other half using a PRB obtained by adding an offset value to the scheduled PRB. In this case, two or four values ​​of the offset value may be configured in a higher layer depending on the active BWP size, and one of these values ​​may be configured (indicated) to the UE by DCI. If inter-slot frequency hopping is configured in the UE, the UE may transmit the PUSCH using a PRB scheduled in a slot with an even slot index and transmit the PUSCH using a PRB scheduled in an odd slot with an offset value added.

[0135] In PUSCH repetition transmission type B, a terminal may be configured with either inter-repetition frequency hopping, in which frequency hopping is performed at nominal PUSCH boundaries, or inter-slot frequency hopping, in which frequency hopping is performed every slot. When inter-repetition frequency hopping is configured in a terminal, the terminal transmits actual PUSCHs corresponding to odd-numbered nominal PUSCHs on scheduled PRBs, and the terminal may transmit actual PUSCHs corresponding to even-numbered nominal PUSCHs on PRBs obtained by adding an offset value to the scheduled PRBs. In this case, the offset value may be configured as two or four values ​​depending on the active BWP size in a higher layer, and one of these values ​​may be configured (indicated) to the terminal by DCI. When inter-slot frequency hopping is configured in a terminal, the terminal may transmit PUSCHs on PRBs scheduled in slots with even slot indices, and may transmit PUSCHs on PRBs scheduled in odd-numbered slots plus an offset value.

[0136] When performing PUSCH repeated transmission, if a symbol scheduled for PUSCH transmission in a specific slot overlaps with a semi-statically configured DL symbol or a symbol set for receiving an SS / PBCH block, the terminal may not transmit the overlapping PUSCH in the slot including the overlapping symbol, and the overlapping PUSCH may be postponed and not transmitted in the next slot.

[0137] When a terminal receives DCI of DCI format 1_0, 1_1, or 1_2 that schedules a PUCCH, the terminal must transmit the PUCCH to the base station. In this case, the PUCCH may include uplink control information (UCI), and the UCI may include at least one of an HARQ-ACK, a Scheduling Request (SR), and Channel State Information (CSI). The HARQ-ACK may be an HARQ-ACK indicating whether the terminal has successfully received two types of channels. A first type may be an HARQ-ACK for a PDSCH when a PDSCH is scheduled to the terminal using DCI of DCI format 1_0, 1_1, or 1_2. A second type may be an HARQ-ACK for a DCI when the DCI of DCI format 1_0, 1_1, or 1_2 is a DCI instructing the release of a semi-statically scheduled (Semi-Persistent Scheduling, SPS) PDSCH. For the transmission of a PUCCH including an HARQ-ACK, the "PDSCH-to-HARQ_feedback timing indicator" field of the DCI can indicate K1, which is information (value) about the slot in which the scheduled PUCCH is transmitted. Here, K1 may be a non-negative integer value. The DCI of DCI format 1_0 can indicate one of {0, 1, 2, 3, 4, 5, 6, 7} as the K1 value. The K1 value that can be indicated in the DCI of DCI formats 1_1 and 1_2 can be set (configured) by a higher layer.

[0138] A method for determining a slot in which a PUCCH including a first type of HARQ-ACK is transmitted will be described. There may be an uplink slot that overlaps with the last symbol in which a PDSCH corresponding to the HARQ-ACK is transmitted. In this case, if the index of the overlapping uplink slot is m, the UE can transmit the PUCCH including the HARQ-ACK in slot m+K1. The index of the uplink slot may be a value determined based on the subcarrier spacing of the BWP in which the PUCCH is transmitted. When downlink slot aggregation is configured in the UE, the last symbol in which a PDSCH is transmitted may refer to the last scheduled symbol in the last slot among the slots in which the PDSCH is transmitted.

[0139] FIG. 15 illustrates a method for scheduling a physical uplink control channel according to an embodiment of the present invention.

[0140] 15, the subcarrier spacing of the DL BWP in which the PDCCH is received, the subcarrier spacing of the DL BWP in which the PDSCH is scheduled, and the subcarrier spacing of the UL BWP in which the PUCCH is transmitted may be the same. The UE may receive the PDCCH scheduling the PDSCH and PUCCH from the base station in slot n. In this case, the DCI included in the PDCCH received in slot n may set (indicate) a K0 value of 2 and a K1 value of 3. For example, if the last symbol in which the PDSCH is transmitted is n+K0 (i.e., n+2), the UE may transmit a HARQ-ACK for the PDSCH in slot n+2+K1 (i.e., n+5). In this case, the HARQ-ACK for the PDSCH may be included in the PUCCH.

[0141] FIG. 16 illustrates repeated transmission of a physical uplink control channel according to an embodiment of the present invention.

[0142] To ensure wide coverage in the NR system, the terminal can repeatedly transmit the long PUCCH over 2, 4, or 8 slots. In this case, the format of the long PUCCH may be PUCCH format 1, 3, or 4. When the terminal repeatedly transmits the PUCCH, the same UCI may be repeatedly transmitted in every slot. Referring to FIG. 16, when the reception of the PDSCH ends in slot n and the K1 value is 2, the terminal can transmit the PUCCH over slot n+K1 (i.e., n+2). When the base station sets the number of repeated transmissions of the PUCCH to 4 (N repeat PUCCH = 4), the UE can repeatedly transmit the PUCCH in slots n+2 to n+5. In this case, the symbol configuration of the repeatedly transmitted PUCCH may be the same. That is, the repeatedly transmitted PUCCH may start from the same symbol in each slot and be composed of the same number of symbols.

[0143] Frequency hopping may also be applied to PUCCH transmission to obtain diversity gain in the frequency domain. When intra-slot frequency hopping is applied, the terminal divides the time domain of a slot for transmitting the PUCCH in half, and transmits half of the PUCCH on the first PRB and the other half on the second PRB. The first and second PRBs may be configured by a higher layer that configures PUCCH resources. When inter-slot frequency hopping is applied, the terminal transmits the PUCCH on the first PRB of a slot with an even slot index and on the second PRB of a slot with an odd slot index. Furthermore, when performing PUCCH repeated transmission, if a symbol of a specific slot scheduled for PUCCH transmission overlaps with a semi-statically configured DL symbol or a symbol configured for receiving an SS / PBCH block, the terminal may not transmit the PUCCH on the slot containing the overlapping symbol. The terminal may postpone transmitting the PUCCH that is not being transmitted to the next slot. In this case, if the symbols for PUCCH transmission in the postponed slot do not overlap with the semi-statically configured DL symbols or symbols set for receiving SS / PBCH blocks, the terminal can transmit the PUCCH.

[0144] Hereinafter, the present invention proposes a method for solving a coverage problem regarding PUSCH transmission performed by a terminal when a random access procedure is performed between the terminal and a base station.

[0145] As described above with reference to FIG. 3, in the random access procedure, the UE transmits the Msg3 PUSCH via an uplink grant (UL grant) included in a random access response (RAR, Msg2). The UL grant is information for scheduling the Msg3 PUSCH, and includes a frequency hopping flag indicating frequency hopping information, time domain resource allocation (TDRA) information, frequency domain resource assignment (FDRA) information, modulation and coding scheme (MCS) information, transmit power control (TPC) command information for PUSCH transmission, CSI request information, ChannelAccess-CPext information, etc. The Msg3 PUSCH transmitted via the uplink grant included in Msg2 is the initial transmission PUSCH. Meanwhile, if the base station cannot receive the Msg3 PUSCH from the UE, the base station instructs the UE to retransmit the Msg3 PUSCH. Retransmission of the Msg3 PUSCH is indicated (scheduled) by the PDCCH. At this time, the retransmission is indicated via DCI of DCI format 0_0, which is scrambled with the Temporary C-RNTI (TC-RNTI) included in the PDCCH. The UE acquires the TC-RNTI through a previously received random access response (Msg2). If the UE successfully detects the DCI instructing retransmission, the UE retransmits the Msg3 PUSCH based on the information included in the DCI. At this time, the information included in the DCI may include a frequency hopping flag, TDRA information, FDRA information, MCS information, TPC information, ChannelAccess-CPext information, New data indicator (NDI) information, Redundancy version (RV) information, HARQ process number (HPN) information, padding bits information, and UL / SUL indicator information. The Msg3 PUSCH indicated via DCI of DCI format 0_0 is the retransmission PUSCH.

[0146] In other words, the Msg3 PUSCH described in this invention is an initial transmission PUSCH or a retransmission PUSCH. Specifically, the PUSCH indicated via the uplink grant of the random access response (Msg2) is for initial transmission, and the PUSCH indicated via the DCI of DCI format 0_0 scrambled with the TC-RNTI is for retransmission.

[0147] Conventionally, the initial transmission PUSCH and the retransmission PUSCH were transmitted in only one slot. In this case, one slot was indicated by the TDRA field of the uplink grant or the TDRA field of the DCI in DCI format 0_0. In other words, the Msg3 PUSCH could not be repeatedly transmitted. Therefore, if the UE could not receive the PDCCH scheduling Msg4 from the base station within a set period of time after transmitting the Msg3 PUSCH, the UE determined that the random access procedure had failed and had to restart the random access procedure from the beginning. For example, in a poor channel environment, even if the UE transmitted the Msg3 PUSCH, the base station may not receive it. Therefore, the base station cannot transmit the PDCCH scheduling Msg4 to the UE, and the random access procedure must be restarted. In other words, Msg3 has low PUSCH coverage. This can cause a problem of delaying the entire random access procedure. Therefore, the present invention will now describe a method for solving the coverage problem of Msg3 PUSCH through repeated transmission of Msg3 PUSCH.

[0148] The base station configures whether or not the Msg3 PUSCH is capable of repeated transmission in the terminal during the random access process. For example, the base station configures whether or not the Msg3 PUSCH is capable of repeated transmission in the terminal via system information block 1 (SIB1) transmitted from the base station during the cell initial access process. That is, the terminal checks whether or not the Msg3 PUSCH is capable of repeated transmission via SIB1. Whether or not the Msg3 PUSCH is capable of repeated transmission may be configured via other SIBs in addition to SIB1. That is, whether or not the Msg3 PUSCH is capable of repeated transmission is configured via SIBx (x = 1, 2, 3, ...). Alternatively, whether or not the Msg3 PUSCH is capable of repeated transmission may be indicated via another channel. For example, the base station configures whether or not the Msg3 PUSCH is capable of repeated transmission via the PBCH. Specifically, whether or not the Msg3 PUSCH is capable of repeated transmission is configured via some bits of the PBCH, or whether or not the Msg3 PUSCH is capable of repeated transmission is inferred from the DMRS sequence or CRC of the PBCH.

[0149] Whether or not repeated transmission of the Msg3 PUSCH is possible is explicitly indicated or inferred from other information included in SIB1. For example, if SIB1 includes parameters for repeated transmission of the Msg3 PUSCH, the UE determines that repeated transmission of the Msg3 PUSCH is possible without a separate configuration (instruction) as to whether or not repeated transmission of the Msg3 PUSCH is possible. Conversely, if SIB1 does not include parameters for repeated transmission of the Msg3 PUSCH, the UE determines that repeated transmission of the Msg3 PUSCH is impossible without a separate configuration (instruction) as to whether or not repeated transmission of the Msg3 PUSCH is possible. In this case, the parameters for repeated transmission of the Msg3 PUSCH indicate PRACH resources on which repeated transmission of the Msg3 PUSCH is performed and the number of times repeated transmission of the Msg3 PUSCH is performed. For example, if the UE is configured with PRACH resources via SIB1, the UE repeatedly transmits the Msg3 PUSCH via the configured PRACH resources. Also, if the number of repetitions of the Msg3 PUSCH is configured in the UE via SIB1, the UE transmits the Msg3 PUSCH for the configured number of repetitions. In this case, the base station configures a single value or multiple values ​​as the number of times the Msg3 PUSCH can be repeatedly transmitted to the UE. For example, the base station configures one of 1, 2, 4, or 8 to the UE, or a set including multiple values ​​(e.g., {1, 2, 4, 8}). That is, the base station configures a single value as the number of repetitions of the Msg3 PUSCH to the UE, or multiple possible values ​​as the number of repetitions. If the base station configures multiple values, the base station instructs the UE to select one of the multiple values ​​via additional signaling (configuration), etc. If the Msg3 PUSCH transmitted by the UE is repeatedly transmitted, the Msg3 PUSCH is repeatedly transmitted in units of slots. For example, if the number of repetitions of the Msg3 PUSCH is 4, the Msg3 PUSCH is repeatedly transmitted over four slots. In other words, this means that the Msg3 PUSCH transmitted in one slot is repeated four times.

[0150] If it is configured that repeated transmission of the Msg3 PUSCH is possible via SIB1, a method for determining whether the UE actually transmits the Msg3 PUSCH repeatedly will be described. Also, the meaning of "interpreted by the UE" described in this specification is the same as the meaning of "configured by the base station to the UE." Also, the meaning of "configured" described in this specification is the same as the meaning of "instructed."

[0151] Method for determining whether to repeatedly transmit Msg3 PUSCH in a terminal If the base station configures the terminal to enable repeated transmission of the Msg3 PUSCH within the cell, the terminal will always recognize that the Msg3 PUSCH is repeatedly transmitted even without additional signaling (configuration) from the base station instructing the actual repeated transmission of the Msg3 PUSCH.

[0152] i) The terminal determines whether to repeatedly transmit the Msg3 PUSCH based on explicit information received from the base station. The explicit information used by the terminal to determine whether to repeatedly transmit the Msg3 PUSCH is as follows:

[0153] ia) Information configured from higher layers: The UE interprets information configured from higher layers and determines whether to enable repeated transmission of the Msg3 PUSCH. For example, the base station configures the UE via SIB1 during the cell initial access process to determine whether repeated transmission of the Msg3 PUSCH is possible within the cell. If the base station determines that repeated transmission of the Msg3 PUSCH is possible, it configures the UE to always transmit the Msg3 PUSCH repeatedly.

[0154] ib) Information in the downlink channel scheduling the Msg3 PUSCH: The terminal interprets the information in the downlink channel scheduling the Msg3 PUSCH and determines whether to enable repeated transmission of the Msg3 PUSCH. In this case, the downlink channel includes an uplink grant for a random access response, or a DCI of DCI format 1_0 scheduling the random access response, or a DCI of DCI format 0_0 scheduling the Msg3 PUSCH. Specifically, the terminal interprets field information in the uplink grant for a random access response scheduling the initial transmission of the Mg3 PUSCH and determines whether to enable repeated transmission of the Mg3 PUSCH. The terminal interprets field information in the DCI of DCI format 0_0 scrambled with the TC-RNTI scheduling the retransmission of the Msg3 PUSCH and determines whether to enable repeated transmission of the Msg3 PUSCH. The terminal interprets field information in the DCI of DCI format 1_0 scheduling the random access response and determines whether to enable transmission of the Msg3 PUSCH. In this case, whether or not to repeatedly transmit the Msg3 PUSCH is indicated using one bit in the information included in each downlink channel (i.e., uplink grant, DCI of DCI format 1_0, DCI of DCI format 0_0), and the terminal determines whether or not to repeatedly transmit the Msg3 PUSCH based on whether or not to repeatedly transmit the PUSCH indicated by the one bit.

[0155] ii) The UE determines whether to repeatedly transmit the Msg3 PUSCH based on implicit information transmitted by the base station. The implicit information used by the UE to determine whether to repeatedly transmit the Msg3 PUSCH is as follows:

[0156] The UE reinterprets information in the downlink channel that schedules the Msg3 PUSCH and determines whether to enable repeated transmission of the Msg3 PUSCH. For example, ii-a) the UE reinterprets field information in the uplink grant that schedules the initial transmission of the Msg3 PUSCH and determines whether to enable repeated transmission of the Msg3 PUSCH. ii-b) the UE reinterprets field information in the DCI of DCI format 0_0 scrambled with the TC-RNTI that schedules retransmission of the Msg3 PUSCH and determines whether to enable repeated transmission of the Msg3 PUSCH. In this case, the field in ii-a) or ii-b) is any one of the TDRA, FDRA, MCS, and TPC fields. In this case, the field interpretation method is as follows.

[0157] The UE determines whether to reinterpret the field based on the number of symbols scheduled by the TDRA field. For example, if the number of symbols scheduled in the TDRA field is equal to or greater than a specific number, the UE reinterprets the field information in the uplink grant of the random access response to determine whether to repeatedly transmit the Msg3 PUSCH. Since the base station allocates a large number of symbols to a UE experiencing insufficient coverage, if the number of allocated symbols is equal to or greater than a predetermined specific number, the UE repeatedly transmits the Msg3 PUSCH to solve the coverage problem. In other words, if the number of allocated symbols is less than a predetermined specific number, the UE does not repeatedly transmit the Msg3 PUSCH. As another example, if the number of symbols scheduled in the TDRA field is equal to or less than a specific number, the UE reinterprets the field information in the uplink grant of the random access response to determine whether to repeatedly transmit the Msg3 PUSCH. This is because if the base station allocates a small number of symbols to the UE, a coverage shortage phenomenon may occur. That is, if the base station allocates more than a certain number of symbols, the terminal does not repeatedly transmit the Msg3 PUSCH. In this case, the certain number is set by a higher layer. The higher layer means SIB1 or another SIB.

[0158] The UE reinterprets the FDRA field based on the number of PRBs scheduled by the FDRA field to determine whether to perform repeated transmission of the Msg3 PUSCH. For example, if the number of PRBs indicated by the FDRA field is equal to or greater than a specific number, the UE reinterprets the field information in the uplink grant of the random access response to determine whether to perform repeated transmission of the Msg3 PUSCH. Since the base station allocates a large number of PRBs to a UE with insufficient coverage, if the number of allocated PRBs is equal to or greater than a predetermined specific number, the UE repeatedly transmits the Msg3 PUSCH to solve the coverage problem. In other words, if the number of allocated PRBs is less than a predetermined specific number, the UE does not repeatedly transmit the Msg3 PUSCH. As another example, if the number of PRBs indicated by the FDRA field is equal to or less than a specific number, the UE reinterprets the field information in the uplink grant of the random access response to determine whether to perform repeated transmission of the Msg3 PUSCH. This is because if the base station allocates a small number of PRBs to the UE, a coverage problem may occur. That is, if the base station allocates more than a certain number of PRBs to the terminal, the terminal does not repeatedly transmit the Msg3 PUSCH. In this case, the certain number is set by a higher layer. The higher layer means SIB1 or other SIBs.

[0159] Depending on the modulation or coding rate indicated by the MCS field, the UE reinterprets the field and determines whether to transmit the Msg3 PUSCH. For example, if the MCS field indicates a low modulation method (e.g., QPSK) or a low coding rate, the UE reinterprets the field information in the uplink grant of the random access response and determines whether to repeatedly transmit the Msg3 PUSCH. Because the base station sets a low modulation method or a low coding rate for UEs with insufficient coverage, if the modulation method or coding rate is low, the UE repeatedly transmits the Msg3 PUSCH.

[0160] Tables 4 and 5 show the modulation method and coding rate to be set in the terminal. The modulation order in Tables 4 and 5 means the modulation method, and if the modulation order is q, it means pi / 2-BPSK (q=1) or QPSK (q=2), if it is 2, it means QPSK, if it is 4, it means 16QAM, if it is 6, it means 64QAM, and if it is 8, it means 256QAM.

[0161] [Table 4]

[0162] [Table 5]

[0163] If transform precoding for PUSCH transmission of the UE is set to disabled, Table 4 is applied; if it is set to enabled, Table 5 is applied. If the UE is scheduled for initial transmission of Msg3 PUSCH (i.e., if Msg3 PUSCH transmission is configured in the uplink grant of the random access response), the base station sets the first 16 indexes (0 to 15) of Table 4 or Table 5. For example, with reference to Table 4, the base station sets QPSK, 16QAM, or 64QAM as the modulation scheme for the UE, and with reference to Table 5, the base station sets pi / 2-BPSK, QPSK, 16QAM, or 64QAM as the modulation scheme for the UE. The lowest modulation scheme among the modulation schemes is pi / 2-BPSK or QPSK. In other words, if pi / 2-BPSK or QPSK is configured for the UE, the UE performs repeated transmission of Msg3 PUSCH.

[0164] Based on the TPC command indicated by the TPC field, the UE reinterprets the field and determines whether to transmit the Msg3 PUSCH repeatedly. For example, if the TPC command indicated by the TPC field indicates a specific value or greater, the UE reinterprets the field information in the uplink grant of the random access response and determines whether to transmit the Msg3 PUSCH repeatedly. The base station indicates a TPC command with a high value (above a specific value) to transmit at high power to a UE with insufficient coverage. Therefore, when the UE receives a TPC command above a specific value, the UE performs repeated transmission of the Msg3 PUSCH. In other words, if the base station sets the TPC command to the UE below a specific value, the UE does not perform repeated transmission of the Msg3 PUSCH.

[0165] Based on the TB size, the UE reinterprets the field and determines whether to perform repeated transmission of the Msg3 PUSCH. The UE determines the TB size of the Msg3 PUSCH based on the FDRA field, TDRA field, MCS field, etc., and determines whether to perform repeated transmission of the Msg3 PUSCH based on the TB size. For example, if the TB size is equal to or less than a certain value, the UE reinterprets the field information in the uplink grant of the random access response and determines whether to perform repeated transmission of the Msg3 PUSCH. Because the base station allocates small TBs (equal to or less than a certain value) to UEs with insufficient coverage, the UE performs repeated transmission of the Msg3 PUSCH when a TB equal to or less than a certain value is allocated. In other words, the UE does not perform repeated transmission of the Msg3 PUSCH when a TB greater than a certain value is allocated.

[0166] The following describes how the terminal determines the number of times to repeatedly transmit the Msg3 PUSCH.

[0167] Msg3 PUSCH repetition transmission count determination method The terminal determines the number of repetitions of the Msg3 PUSCH according to the number of repetitions set by the base station. The terminal then repeatedly transmits the Msg3 PUSCH according to the number of repetitions set by the base station. Before instructing the number of repetitions, the base station sets multiple candidate repetitions to the terminal. The candidate repetitions may be predetermined values, set in broadcasting information, or set in a higher layer. For example, the candidate repetitions may be configured as {N1, N2, N3, N4, ...}. In this case, the candidate repetitions (N1, N2, N3, N4, ...) are natural numbers equal to or greater than 1 and are powers of 2. For example, the multiple candidate repetitions may be {1, 2, 4, 8}. The terminal then repeatedly transmits the Msg3 PUSCH for any one of the values ​​1, 2, 4, and 8 instructed by the base station.

[0168] i) The number of times that the Msg3 PUSCH is repeatedly transmitted is configured in the terminal by a higher layer. For example, if the number of times that the Msg3 PUSCH is repeatedly transmitted is configured as an integer value of n by a higher layer, the terminal repeatedly transmits the Msg3 PUSCH n times.

[0169] ii) The base station sets the number of repeated transmissions of the Msg3 PUSCH to the terminal using a field in the DCI of DCI format 0_0 that schedules the Msg3 PUSCH or the DCI of DCI format 1_0 that schedules the random access response (Msg2). For example, the terminal interprets a certain number of bits in the DCI of DCI format 1_0 scrambled with the RA-RNTI that schedules the random access response as bits indicating the number of repeated transmissions of the Msg3 PUSCH, and performs repeated transmission of the Msg3 PUSCH. As another example, the terminal interprets a certain number of bits in the DCI of DCI format 0_0 scrambled with the TC-RNTI that schedules retransmission of the Msg3 PUSCH as bits indicating the number of repeated transmissions of the Msg3 PUSCH, and performs repeated transmission of the Msg3 PUSCH.

[0170] In this case, the number of repetitions indicated by i) the upper layer or ii) the DCI of DCI format 0_0 or 1_0 is one of multiple candidate values ​​for the number of repetitions. Then, the terminal repeatedly transmits the Msg3 PUSCH by the indicated one value.

[0171] The fields including a certain number of bits in the DCI of DCI format 0_0 scrambled with TC-RNTI in ii) are the NDI (New data indicator), HPN (HARQ process number), CSI request, FDRA, and TPC fields. Since the NDI, HPN, and CSI request fields are not used for transmitting the Msg3 PUSCH, the UE interprets the values ​​of the NDI, HPN, and CSI request fields as field values ​​for repeated transmission of the Msg3 PUSCH.

[0172] For a UE with insufficient coverage, the base station schedules it with a small number of PRBs in the frequency domain or schedules the PUSCH with the highest possible transmission power. Therefore, the UE interprets a certain number of bit values ​​in the FDRA field as a field value for repeated transmission of the Msg3 PUSCH, or interprets some of the indices indicating low dB values ​​in the TPC field as a field value for repeated transmission of the Msg3 PUSCH.

[0173] Hereinafter, a method for the UE to interpret a certain number of bits in the DCI of DCI format 0_0 scrambled with the TC-RNTI for repeated transmission of the Msg3 PUSCH will be described. Hereinafter, candidates for the number of repeated transmissions of the Msg3 PUSCH configured in the UE are {N1, N2, N3, N4}.

[0174] The UE interprets the bit value of one of the DCI fields of DCI format 0_0 scrambled with TC-RNTI as the number of repeated transmissions of the Msg3 PUSCH. That is, the UE interprets X bits of one of the NDI, HPN, CSI request, FDRA, and TPC fields as the field value for repeated transmission of the Msg3 PUSCH. For example, the UE interprets X (e.g., 2) bits of the HPN field as the field value for repeated transmission of the Msg3 PUSCH. In this case, the base station uses 2 bits to indicate one of four repeated transmission numbers (N1, N2, N3, N4). For example, {00}=N1, {01}=N2, {10}=N3, and {11}=N4.

[0175] The UE interprets a combination of bit values ​​of two different fields among the DCI fields of DCI format 0_0 scrambled with TC-RNTI as the number of repeated transmissions of the Msg3 PUSCH. That is, the UE interprets X bit of one of the NDI, HPN, CSI request, FDRA, and TPC fields and Y bit of one of the NDI, HPN, CSI request, FDRA, and TPC fields that does not include X bit as a field value for repeated transmission of the Msg3 PUSCH. For example, the UE interprets a combination of X (e.g., 1) bit of the NDI field and Y (e.g., 1) bit of the HPN field, i.e., 2 bits, as a field value for repeated transmission of the Msg3 PUSCH. In this case, the base station indicates one of four possible repeat transmission counts using 2 bits. For example, {NDI, HPN}'s {0,0}=N1, {0,1}=N2, {1,0}=N3, and {1,1}=N4. Alternatively, {HPN, NDI}'s {0,0}=N1, {0,1}=N2, {1,0}=N3, and {1,1}=N4. As another example, the UE interprets a combination of an X (e.g., 1) bit in the NDI field and a Y (e.g., 1) bit in the CSI request field, i.e., two bits, as a field value for repeated transmission of the Msg3 PUSCH. In this case, if the repetition count candidates for the Msg3 PUSCH configured in the UE are {N1, N2, N3, N4}, the base station indicates one of the four repetition count candidates using the two bits. For example, {NDI, CSI request} is set as {0,0}=N1, {0,1}=N2, {1,0}=N3, {1,1}=N4, or {CSI request, NDI} is set as {0,0}=N1, {0,1}=N2, {1,0}=N3, {1,1}=N4.

[0176] The UE interprets bit values ​​of two different fields among the DCI fields of DCI format 0_0 scrambled with TC-RNTI as field values ​​for repeated transmission of Msg3 PUSCH. Specifically, the UE interprets X bit of one DCI field and Y bit of another field other than the field containing X bit as field values ​​for repeated transmission of Msg3 PUSCH. For example, the X bit indicates whether the UE interprets Y bit as a field value for repeated transmission of Msg3 PUSCH, and the Y bit indicates the number of repeated transmissions of Msg3 PUSCH. For example, one bit of the NDI field indicates whether or not the Y bit of the FDRA field is interpreted as a field value for repeated transmission of the Msg3 PUSCH. In this case, if the value of one bit of the NDI field is '0', the Y bit of the FDRA field is not interpreted as a field value for repeated transmission of the Msg3 PUSCH. In contrast, if the value of one bit of the NDI field is '1', the Y bit of the FDRA field is interpreted as a field value for repeated transmission of the Msg3 PUSCH. In this case, the Y bit indicates one of the candidate repeat transmission counts of the Msg3 PUSCH pre-configured in the UE. For example, if the value of one bit of the NDI field is '1', the Y (e.g., 2) bit of the FDRA field indicates one of the four candidate repeat transmission counts. Specifically, {00}=N1, {01}=N2, {10}=N3, and {11}=N4 are set in {FDRA}. As another example, one bit in the CSI request field indicates whether the UE interprets the Y bit in the HPN field as a field value for repeated transmission of the Msg3 PUSCH. If the value of one bit in the CSI request field is '0', the Y bit in the HPN field is not interpreted as a field value for repeated transmission of the Msg3 PUSCH, and if the value of one bit in the CSI request field is '1', the Y bit in the HPN field is interpreted as a field value for repeated transmission of the Msg3 PUSCH.If the value of one bit of the CSI request field is '1', the Y (e.g., 2) bit of the HPN field indicates one of four repeat transmission counts. Specifically, {HPN} is set as {00}=N1, {01}=N2, {10}=N3, and {11}=N4.

[0177] iii) The UE is instructed on the number of repeated transmissions of the Msg3 PUSCH via a specific field of the uplink grant in the random access response that schedules the initial transmission of the Msg3 PUSCH. The UE repeatedly transmits the Msg3 PUSCH according to the instructed number of repeated transmissions. The UE interprets the bit value of a specific field of the uplink grant as a field value for repeated transmission of the Msg3 PUSCH. In this case, a specific bit of the uplink grant indicates one of multiple repeated transmissions of the Msg3 PUSCH. The specific field of the uplink grant is a CSI request, FDRA, TPC, or MCS field. In this case, since the CSI request field is not used for transmitting the Msg3 PUSCH, the UE interprets the value of the CSI request field as a field value for repeated transmission of the Msg3 PUSCH. For example, since the base station schedules a UE with insufficient coverage with a small number of PRBs in the frequency domain, the UE interprets the bit value of the FDRA field as a field value for repeated transmission of the Msg3 PUSCH. As another example, since the base station schedules a PUSCH at the highest possible transmission power for a terminal with insufficient coverage, the terminal interprets some of the indexes indicating low dB values ​​in the TPC field as field values ​​for repeated transmission of the Msg3 PUSCH. In this case, the TPC field has a size of 3 bits, and the TPC values ​​indicated by each code point are as shown in Table 6. As another example, a terminal with insufficient coverage is scheduled to transmit a PUSCH at the lowest possible modulation scheme (e.g., QPSK) and / or low coding rate. Therefore, the terminal interprets some of the lowest indexes among the first 16 MCS indexes (0 to 15) included in the MCS field in Tables 4 and 5 as field values ​​for repeated transmission of the Msg3 PUSCH.

[0178] [Table 6]

[0179] The following further describes how to interpret a specific number of bits in the uplink grant of the random access response: The candidates for the number of repetitions of Msg3 PUSCH configured in the terminal are {N1, N2, N3, N4}. The bit value of one of the fields of the uplink grant is Msg3.

[0180] This is set to indicate the number of times the PUSCH is repeated. That is, the UE interprets the value of X bits in a specific field among the CSI request, FDRA, TPC, and MCS fields as the value of the Msg3 PUSCH repeat transmission field.

[0181] For example, the base station sets X (e.g., 2) bits of the FDRA field as a field value for repeated transmission of the Msg3 PUSCH, and the base station uses the X (e.g., 2) bits to indicate one of four (N1, N2, N3, N4) repeat transmission counts. The terminal determines N1 if the bit value of the FDRA field is '00', N2 if the bit value is '01', N3 if the FDRA field is '10', and N4 if the FDRA field is '11'. If there are M repeat transmission count candidates set by a higher layer, the X bits of the FDRA field are determined as X = ceil(log2(M)). In this specification, ceil(x) is a function that returns the smallest integer among integers equal to or greater than x. The X bits are X bits from the MSB excluding the bit(s) indicating frequency hopping in the FDRA field. Specifically, if the number of RBs included in the initial UL BWP is less than 50, the X bits are the 2nd to X bits of the FDRA field, and if the number of RBs is greater than or equal to 50, the X bits are the 3rd to X bits of the FDRA field.

[0182] For example, the base station sets X (e.g., 2) bits of the TPC field as the bits of the field for repeated transmission of Msg3 PUSCH, and the base station indicates one of four repeated transmission counts using the two bits of the TPC field. If the bit value of the TPC field is '00', the terminal determines it as N1; if it is '01', it determines it as N2; if it is '10', it determines it as N3; and if it is '11', it determines it as N4. If there are M candidates for the repeated transmission count set by the upper layer, the X bits of the TPC field are determined as X = ceil(log2(M)). The X bits are the most significant bit (MSB) or the most significant bit (LSB) of the 3-bit TPC field.

[0183] For example, the base station sets X (e.g., 2) bits in the MCS field as bits in the field for repeated transmission of Msg3 PUSCH, and the base station indicates one of four repeated transmission counts using the two bits in the MCS field. If the bit value of the MCS field is '00', the terminal determines N1; if it is '01', N2; if it is '10', N3; and if it is '11', N4. If there are M candidates for the number of repeated transmission counts set by a higher layer, the X bits in the MCS field are determined as X = ceil(log2(M)). The X bits are the X most significant bits or the X most significant bits in the 4-bit MCS field.

[0184] The terminal interprets the number of repetitions of Msg3 PUSCH by combining the bit values of two different fields among the fields of the uplink grant of the random access response. If the number of bits required to set the number of repetitions of Msg3 PUSCH is Z, the terminal interprets Z bits obtained by combining the bits of two different fields as the number of repetitions of Msg3 PUSCH. The terminal interprets X bits of the first field and Y bits of the second field among the CSI request, FDRA, TPC, and MCS fields as bits for the repeated transmission of Msg3 PUSCH. The first field and the second field are different fields, and X + Y = Z. Also, X < Z, Y < Z, and Z is at least 2 bits or more. On the other hand, if the terminal interprets X = Z bits of the first field as the number of repetitions of Msg3 PUSCH, the number of repetitions of Msg3 PUSCH is indicated using the X bits of the first field.

[0185] If there are M candidates for the number of repetitions of Msg3 PUSCH (for example, 4 candidates {N1, N2, N3, N4}), Z bits are required to indicate the number of repetitions to the terminal. At this time, Z = ceil(log2(M)) bits. If M is 4, then Z is 2. For example, X (for example, 1) bit of the first field (for example, CSI request field) and Y (for example, 1) bit of the second field (for example, FDRA field, MCS field) are interpreted as bits for the repeated transmission of Msg3 PUSCH, and the base station uses 2 bits to indicate any one of the 4 numbers of repetitions. If {the value of 1 bit of the first field, the value of 1 bit of the second field} is {0, 0}, the number of repetitions is set to N1; if it is {0, 1}, it is set to N2; if it is {1, 0}, it is set to N3; if it is {1, 1}, it is set to N4.

[0186] In addition to the above-described embodiments, for the repeated transmission of the Msg3 PUSCH in the DCI of DCI format 0_0 scrambled with the TC-RNTI in the uplink grant of the random access response, the field is at least one or more fields among the TDRA, FDRA, MCS, and TPC fields. At this time, the terminal reinterprets the bit values of one or more fields to perform the repeated transmission of the Msg3 PUSCH. Hereinafter, a specific method for interpreting the bit values of the fields will be further described. The candidate number of repeated transmission times of the Msg3 PUSCH set for the terminal is {N1, N2, N3, N4}.

[0187] The terminal performs the repeated transmission of the Msg3 PUSCH based on the number of symbols scheduled (assigned) by the TDRA field. For example, if the number of symbols assigned to the transmission of the Msg3 PUSCH by the terminal is 1 to (M1 - 1) symbols, the number of repeated transmissions is set to N1; if it is M1 to (M2 - 1) symbols, the number of repeated transmissions is set to N​​​The terminal performs repeated transmission of Msg3 PUSCH based on the number of PRBs scheduled by the FDRA field. For example, if the number of PRBs allocated for PUSCH transmission is 1 to (M1 - 1) PRBs, the number of repeated transmissions is set to N1; if it is M1 to (M2 - 1) PRBs, the number of repeated transmissions is set to N2; if it is M2 to (M3 - 1) PRBs, the number of repeated transmissions is set to N3; if it is M3 to (M4 - 1) PRBs, the number of repeated transmissions is set to N4. Here, M1 < M2 < M3 < M4 and N1 > N2 > N3 > N4. This is because if the base station allocates a small number of PRBs to the terminal, there is a risk of deepening the coverage shortage phenomenon. That is, if the number of allocated PRBs is small, the terminal repeats the transmission of Msg3 PUSCH more times. As another example, N1 < N2 < N3 < N4. This is because the base station allocates a large number of PRBs to a terminal with insufficient coverage. That is, if the base station allocates a large number of PRBs, the terminal repeats the transmission of Msg3 PUSCH more times. At this time, the number of allocated PRBs is set by the upper layer. Specifically, it is set by SIB1 or other SIBs.

[0189] The terminal performs repeated transmission of Msg3 PUSCH based on the modulation method or coding rate indicated by the MCS field. For example, if the index on the MCS table (table) indicated by the MCS field in the terminal is 0 to (M1 - 1), the number of repeated transmissions is set to N1; if it is M1 to (M2 - 1), the number of repeated transmissions is set to N2; if it is M2 to (M3 - 1), the number of repeated transmissions is set to N3; if it is M3 to (M4 - 1), the number of repeated transmissions is set to N4. Here, M1 < M2 < M3 < M4 and N1 > N2 > N3 > N4. This is because the base station sets a low modulation method or coding rate for a terminal with insufficient coverage. That is, the lower the modulation or coding rate is set, the more times the terminal repeats the transmission of Msg3 PUSCH.

[0190] The terminal repeats transmission of Msg3 PUSCH based on the TPC command indicated by the TPC field. For example, if the TPC command index indicated by the TPC field is 0 to (M1-1), the terminal determines the number of repeat transmissions to be N1, if it is M1 to (M2-1), the number of repeat transmissions to be N2, if it is M2 to (M3-1), the number of repeat transmissions to be N3, and if it is M3 to (M4-1), the number of repeat transmissions to be N4. M1 <M2<M3<M4で、N1> N2>N3>N4. This is because the base station sets a high TPC command value to transmit at high power to a terminal with insufficient coverage. In other words, the higher the TPC command value set, the more frequently the terminal repeatedly transmits Msg3 PUSCH.

[0191] The terminal repeatedly transmits the Msg3 PUSCH based on the TB size. For example, the terminal determines the TB size for transmitting the Msg3 PUSCH based on the FDRA, TDRA, and / or MCS field. If the determined TB size is 0 to (M1-1), the terminal determines the number of repeated transmissions to be N1; if it is M1 to (M2-1), the terminal determines the number of repeated transmissions to be N2; if it is M2 to (M3-1), the terminal determines the number of repeated transmissions to be N3; and if it is M3 to (M4-1), the terminal determines the number of repeated transmissions to be N4. M1 <M2<M3<M4で、N1> N2>N3>N4. This is because the base station sets a small TB size for a terminal with insufficient coverage. That is, the smaller the TB size set, the more times the terminal repeatedly transmits the Msg3 PUSCH.

[0192] iv) The UE is configured by the base station with a TDRA table including the number of repeated transmissions of the Msg3 PUSCH. Each entry in the TDRA table includes information on time domain resources and the number of repeated transmissions of the Msg3 PUSCH. Each entry may include the same number of repeated transmissions or different numbers of repeated transmissions. The UE determines the number of repeated transmissions of the Msg3 PUSCH by referring to the TDRA table. For example, if the UE is configured to repeatedly transmit the Msg3 PUSCH, it performs repeated transmission of the Mg3 PUSCH by referring to the TDRA table. On the other hand, if the UE is configured not to repeatedly transmit the Msg3 PUSCH, it transmits the Mg3 PUSCH by referring to the conventional TDRA table. In this case, the conventional TDRA table refers to a table that does not include the number of repeated transmissions of the Msg3 PUSCH.

[0193] The one or more repeat transmission numbers described in this specification are values ​​that are used commonly or independently for the initial transmission and retransmission of the Msg3 PUSCH. If the base station instructs the UE to retransmit the Msg3 PUSCH, the UE determines the repeat transmission number for the retransmission of the Msg3 PUSCH based on the repeat transmission number instructed for the initial transmission of the Msg3 PUSCH.

[0194] The terminal determines the number of repetitions for retransmission of the Msg3 PUSCH through a bit in a specific field of the DCI transmitted by the base station, or determines the number of repetitions for retransmission of the Msg3 PUSCH through the TDRA table. In this case, the DCI is DCI of DCI format 0_0 scrambled with the TC-RNTI.

[0195] a) The value of the bit indicates that the number of repetitions for retransmission of the Msg3 PUSCH is the same as the number of repetitions for the initial transmission of the Msg3 PUSCH. For example, if some or all of the bits have a value of 0, the UE determines that the number of repetitions for retransmission of the Msg3 PUSCH is the same as the number of repetitions for the initial transmission of the Msg3 PUSCH.

[0196] b) The number of repetitions for retransmission of Msg3 PUSCH is determined based on the number of repetitions for initial transmission of Msg3 PUSCH.

[0197] b) One of the DCI bit values ​​indicates that the number of repeated transmissions for the Msg3 PUSCH retransmission and the initial transmission is the same.

[0198] b-ii) One of the DCI bit values ​​indicates that the number of repetitions for retransmission of the Msg3 PUSCH is greater than the number of repetitions for the initial transmission of the Msg3 PUSCH. Specifically, one of the DCI bit values ​​indicates that the number of repetitions for retransmission of the Msg3 PUSCH is twice as large as the number of repetitions for the initial transmission of the Msg3 PUSCH. If the number of repetitions for the initial transmission of the Msg3 PUSCH has already reached the maximum number of repetitions (or if the determined number of repetitions for retransmission of the Msg3 PUSCH exceeds the maximum number of repetitions), the UE retransmits the Msg3 PUSCH according to the maximum number of repetitions.

[0199] b-iii) One of the DCI bit values ​​indicates that the number of repetitions for retransmission of the Msg3 PUSCH is smaller than the number of repetitions for the initial transmission of the Msg3 PUSCH. Specifically, one of the DCI bit values ​​indicates that the number of repetitions for retransmission of the Msg3 PUSCH is half the number of repetitions for the initial transmission of the Msg3 PUSCH. If the initial number of repetitions for the Msg3 PUSCH has already reached the minimum number of repetitions (e.g., 1) (or if the determined number of repetitions for retransmission of the Msg3 PUSCH is smaller than the minimum number of repetitions (e.g., 1)), the UE retransmits the Msg3 PUSCH according to the minimum number of repetitions.

[0200] The bits of the above-mentioned specific fields of the DCI are replaced with some entries of the TDRA table. For example, the number of repetitions for the retransmission of the Msg3 PUSCH indicated by the some entries of the TDRA table may be the same as, greater than (e.g., twice as large), or smaller than (e.g., half as large) the number of repetitions for the initial transmission of the Msg3 PUSCH.

[0201] Msg3: How to stop repeated PUSCH transmission If the base station configures the terminal to repeatedly transmit the Msg3 PUSCH K times, the terminal repeatedly transmits the Msg3 PUSCH K times. In this case, since the repeatedly transmitted Msg3 PUSCH is the same, if the base station successfully receives some of the K Msg3 PUSCHs, repeated transmission of the Msg3 PUSCH is unnecessary. Therefore, a method for interrupting repeated transmission of the Msg3 PUSCH will be described below.

[0202] i) The UE determines whether to transmit the Mg3 PUSCH repeatedly based on whether it receives the PDCCH scheduling Msg4. After the first transmission of the Mg3 PUSCH, the UE detects the PDCCH scheduling Msg4 transmitted from the base station. If the UE receives the PDCCH scheduling Msg4, the UE recognizes that the base station has successfully received the Mg3 PUSCH. Therefore, after scheduling the PDCCH scheduling Msg4, the UE stops the next repeated transmission of the Mg3 PUSCH without performing it. The PDCCH scheduling Msg4 includes DCI in DCI format 1_0 scrambled with the TC-RNTI.

[0203] ii) The UE determines whether to repeatedly transmit the Msg3 PUSCH based on whether it receives a PDCCH that schedules retransmission of the Msg3 PUSCH. After the first Msg3 PUSCH transmission, the UE detects the PDCCH that schedules retransmission of the Msg3 PUSCH transmitted from the base station. If the UE receives the PDCCH that schedules Msg3, the UE receives scheduling information for the new Mg3 PUSCH. Therefore, the UE stops the repeated transmission of the Mg3 PUSCH that it was previously transmitting. The PDCCH that schedules the Msg3 PUSCH includes DCI in DCI format 0_0 scrambled with the TC-RNTI.

[0204] iii) The UE determines whether to repeatedly transmit the Msg3 PUSCH based on whether it receives an uplink grant in a random access response (Msg2) that schedules the initial transmission of the Msg3 PUSCH. After the initial transmission of the Msg3 PUSCH, the UE receives a PDCCH that schedules the Msg2 uplink grant and the Msg2 uplink grant. If the UE receives the Msg2 uplink grant or a PDCCH that schedules the Msg2 uplink grant, the UE is configured with scheduling information for the new Msg3 PUSCH. Therefore, the UE stops the repeated transmission of the Msg3 PUSCH that was previously being transmitted. The PDCCH that schedules the Msg2 uplink grant includes DCI of DCI format 1_0 scrambled with the RA-RNTI.

[0205] iv) The UE repeatedly transmits the Msg3 PUSCH within a specific time window and stops the repeated transmission of the Msg3 PUSCH when the specific time window ends. In this case, the repeated transmission of the Msg3 PUSCH is not transmitted in certain situations (for example, situations in which the repeated transmission of the Msg3 PUSCH is stopped in i) to iii) above, and is deferred to the next slot. Therefore, the repeated transmission of the Msg3 PUSCH may be delayed for a certain period of time. To prevent this, the UE only transmits the Msg3 PUSCH repeatedly within a specific time (slot) from the first transmission of the Msg3 PUSCH. In other words, the UE transmits the Msg3 PUSCH repeatedly within a specific time (slot), but does not transmit the Msg3 PUSCH repeatedly after the specific time (slot) ends.

[0206] As described above, the UE reinterprets the CSI request field, FDRA field, TPC, and MCS field to determine the number of repeated transmissions of the Msg3 PUSCH. Hereinafter, a method for determining whether the UE should reinterpret the CSI request field, FDRA field, and TPC field to determine the number of repeated transmissions of the Msg3 PUSCH will be described.

[0207] Msg3: Method for determining whether to reinterpret fields depending on the number of PUSCH repetitions i) If a separate PRACH resource (e.g., a PRACH preamble, a RACH opportunity) for repeated transmission of the Msg3 PUSCH is configured for the UE from the base station, and the UE transmits the PRACH to the base station on the separate PRACH resource, the UE reinterprets the CSI request field, FDRA field, and TPC field according to the above-described method. Conversely, if a UE transmits a PRACH on a resource other than the separate PRACH resource, the UE always reinterprets the CSI request field, FDRA field, and TPC field for their intended purpose. In this case, the separate PRACH resource is included in SIB1 and configured by the base station for the UE. That is, the UE repeatedly transmits the Msg3 PUSCH on a resource determined based on at least one of the PRACH preamble and the RACH opportunity. For example, the base station checks on which resource the PRACH transmitted to the UE is transmitted. If the PRACH transmitted by the UE is transmitted on the separate PRACH resource, the base station indicates the number of repetitions of the Msg3 PUSCH using at least one or two of the CSI request field, the FDRA field, and the TPC field. When indicating the number of repetitions, the base station indicates the number of repetitions as 1. That is, the base station sets the Msg3 PUSCH not to be transmitted repeatedly. In this case, one of a plurality of pre-set candidates for the number of repetitions (e.g., N1, N2, N3, and N4) is set to '1'. Furthermore, N1 may be a pre-set value of 1 (not separately set), and the base station may set only the values ​​of N2, N3, and N4.

[0208] Meanwhile, the base station indicates the number of repetitions of the Msg3 PUSCH through a specific field (e.g., a CSI request field). As described above, even if the terminal transmits a PRACH on a resource separately configured by the base station, the base station indicates through a specific field that the Msg3 PUSCH should not be transmitted repeatedly. In this case, if the base station indicates that the Msg3 PUSCH should be transmitted repeatedly through a specific field (e.g., a CSI request field), the number of repetitions is indicated using at least one or two of the FDRA field and the TPC field. In this case, the base station does not need to indicate 1 as the number of repetitions of the Msg3 PUSCH because the base station can indicate that the Msg3 PUSCH should not be transmitted repeatedly through the specific field. Therefore, the values ​​of the repetition number candidates (N1, N2, N3, N4) do not need to include 1. That is, the repetition number candidates are set to values ​​greater than 1.

[0209] ii) The UE determines whether to reinterpret the CSI request field, FDRA field, and TPC field as the purpose of repeated transmission of the Msg3 PUSCH based on the value of a specific field. In this case, the specific field is any one field of the uplink grant in the random access response. For example, the specific field may be the CSI request field, and in this case, whether to reinterpret is determined based on the value of one bit of the CSI request field. If the value of the CSI request field is 0, the UE interprets the FDRA field and TPC field for their original purpose (not for the purpose of determining whether to repeat transmission of the Msg3 PUSCH). If the value of the CSI request field is 1, the UE reinterprets the FDRA field and TPC field. In this case, since the CSI request field is used to determine whether to reinterpret, the CSI request field is excluded from the fields that are reinterpreted for repeated transmission of the Msg3 PUSCH.

[0210] How to determine the transmit power command value The UE should determine the TPC command value of the Msg3 PUSCH. If the UE repeatedly transmits the Msg3 PUSCH, the UE determines the TPC value as the transmit power command value, which is the highest 8 dB increase in Table 6. On the other hand, if the UE repeatedly transmits the Msg3 PUSCH, the base station sets a specific value as the TPC value to the UE.

[0211] The UE determines the transmission power command value based on the remaining bit(s) excluding the X bit for repeated transmission of the Msg3 PUSCH. Since the number of the remaining bit(s) is 3-X, the remaining bit(s) is 1 bit or 2 bits.

[0212] A specific method for determining the TPC value based on the remaining bit(s) will be described below.

[0213] i) If the remaining bit is 1 bit, the terminal inserts "11" into the 2 MSB bits. Therefore, the terminal determines the TPC value based on "11a" (where a is the value of the remaining 1 bit) and Table 6. If the value of the remaining 1 bit (a) is 0, it means "110", and since "110" is 6, it means a 6 dB increase according to Table 6. If the value of the remaining 1 bit (a) is 1, it means "111", and since "111" is 7, it means an 8 dB increase according to Table 6. In other words, when referring to Table 6, the terminal is instructed to only the highest two TPC command values ​​(6, 7).

[0214] ii) If the remaining bit is 1 bit, the TPC value is determined by the value of the 1 bit. More specifically, the TPC value is determined according to Table 7.

[0215] [Table 7]

[0216] Referring to Table 7, the UE uses the TPC_0 value if the remaining bit has a value of '0', and uses the TPC_1 value if the remaining bit has a value of '1'. TPC_0 and TPC_1 are predetermined values ​​or are separately set by the base station. The TPC_0 and TPC_1 values ​​are two of -6, -4, -2, 0, 2, 4, 6, and 8. The TPC_0 value is one of the negative values ​​(or non-positive values) of -6, -4, -2, 0, 2, 4, 6, and 8, and the TPC_1 value is one of the positive values. In addition, to extend the coverage of the PUSCH, TPC_0 to TPC_1 are determined to be two positive (or non-negative) values ​​of -6, -4, -2, 0, 2, 4, 6, and 8. The difference between the TPC_0 and TPC_1 values ​​is 4 dB. Specifically, TPC_0 is 4 dB and TPC_1 is 8 dB, or TPC_0 is 2 dB and TPC_1 is 6 dB, or TPC_0 is 0 dB and TPC_1 is 84 dB. Meanwhile, the difference between TPC_0 and TPC_1 is 8 dB. Specifically, TPC_0 is 8 dB and TPC_1 is 8 dB.

[0217] If the remaining bits are 2 bits, the terminal inserts a '1' into the MSB bit, similar to method i). Therefore, the terminal determines the TPC value based on '1ab' (where ab is the value of the remaining 2 bits) and Table 6. That is, if the value of the remaining 2 bits (ab) is 00, it means '100', and '100' is 4, which means a 2 dB increase. Similarly, if the value of the remaining 2 bits is 01, it means '101', and '101' is 5, which means a 4 dB increase. If the value of the remaining 2 bits is 10, it means '110', and '110' is 6, which means a 6 dB increase. If the value of the remaining 2 bits is 11, it means '111', and '111' is 7, which means an 8 dB increase. The terminal is only instructed to use the highest four TPC command values ​​(4, 5, 6, 7) in Table 6.

[0218] If the remaining bits are two bits, four TPC values ​​are determined based on the remaining two bits in a manner similar to method ii). More specifically, the TPC values ​​are determined according to Table 8.

[0219] [Table 8]

[0220] If the remaining two bits (ab) are '00', the terminal uses the TPC_0 value; if they are '01', the terminal uses the TPC_1 value; if they are '10', the terminal uses the TPC_2 value; and if they are '11', the terminal uses the TPC_3 value. TPC_0, TPC_1, TPC_2, and TPC_3 are pre-determined values ​​or values ​​separately set by the base station. The TPC_0, TPC_1, TPC_2, and TPC_3 values ​​are -6, -4, -2, 0, 2, 4, 6, and 8. The TPC_0 value is one of the negative (or non-positive) values ​​-6, -4, -2, 0, 2, 4, 6, and 8, while the TPC_1, TPC_2, and TPC_3 values ​​are positive. The TPC_0 and TPC_1 values ​​are one of the negative (or non-positive) values ​​-6, -4, -2, 0, 2, 4, 6, and 8, while the TPC_2 and TPC_3 values ​​are positive. Also, to extend the coverage of the PUSCH, the values ​​of TPC_0, TPC_1, TPC_2, and TPC_3 are four positive values ​​(or non-negative values) among -6, -4, -2, 0, 2, 4, 6, and 8. The difference between the values ​​of TPC_0, TPC_1, TPC_2, and TPC_3 is 4 dB. Specifically, TPC_0 is -6 dB, TPC_1 is -2 dB, TPC_2 is 2 dB, and TPC_3 is 6 dB. Also, TPC_0 is -4 dB, TPC_1 is 0 dB, TPC_2 is 4 dB, and TPC_3 is 8 dB.

[0221] The above describes a signaling method for the base station regarding repeated transmission of the Msg3 PUSCH. Information regarding repeated transmission of the Msg3 PUSCH can be configured using some bits of a specific field of the uplink grant or DCI in a random access response. Using some bits requires adding some bits, which creates a problem of overhead. Furthermore, information regarding repeated transmission of the Msg3 PUSCH can be configured by reinterpreting a specific field of the uplink grant or DCI or by reinterpreting bits of a specific field. The reinterpretation method has a problem of restricting the flexible scheduling of the base station. Furthermore, the base station may not be able to recognize information regarding whether the terminal supports repeated transmission of the Msg3 PUSCH. In this case, even if the base station configures information regarding repeated transmission of the Msg3 PUSCH, the terminal may not be able to perform repeated transmission of the Msg3 PUSCH, and may also misinterpret the uplink grant or DCI. To solve this problem, a method for notifying the base station whether or not to perform repeated transmission of the Msg3 PUSCH or the number of repeated transmissions when the terminal transmits the Msg3 PUSCH to the base station will be described below.

[0222] Msg3: Signaling method for information regarding repeated transmission via PUSCH FIG. 17 is a diagram illustrating repeated transmission of Msg3 PUSCH according to one embodiment of the present invention.

[0223] Referring to FIG. 17, a terminal repeatedly transmits an Msg3 PUSCH over four slots. The Msg3 PUSCH transmitted in each slot transmits the same TB. The same TB is repeatedly transmitted in each slot with the same or different RVs (redundancy versions). The Msg3 PUSCH transmitted in each slot includes at least one DMRS symbol. A DMRS symbol refers to a symbol to which a DMRS is mapped. The Msg3 PUSCH transmitted in each slot includes multiple DMRS symbols. The DMRS symbol transmitted earliest in time among the multiple DMRS symbols is referred to as the first DMRS symbol, and the next DMRS symbol is referred to as an additional DMRS symbol. For convenience of explanation, the first DMRS symbol is referred to as the DMRS symbol in this specification, but it is clear that the term additional DMRS symbol also refers to this.

[0224] The base station configures information regarding Msg3 PUSCH transmission in the terminal (e.g., via an uplink grant), and therefore knows in advance the resources (slot, symbol, PRB, etc.) on which the first Msg3 PUSCH (Msg3 PUSCH rep#1) will be transmitted. The base station also knows in advance the position of the DMRS symbol included in Msg3 PUSCH rep#1. The base station receives Msg3 PUSCH rep#1 transmitted by the terminal based on the information regarding repeated transmission. Because the same TB is repeatedly transmitted in each slot, the base station can decode the TB transmitted by Msg3 PUSCH rep#1 even if it receives only Mg3 PUSCH rep#1. However, if the channel environment is poor, the base station cannot decode the TB transmitted by Msg3 PUSCH rep#1 even if it receives only Msg3 PUSCH rep#1. In this case, the base station receives the second Msg3 PUSCH (Msg3 PUSCH rep#2) from the slot next to the slot in which Msg3 PUSCH rep#1 is transmitted. Specifically, the base station determines whether to receive Msg3 PUSCH rep#2 at the same symbol position and / or PRB as Msg3 PUSCH rep#1 in the slot next to the slot in which Msg3 PUSCH rep#1 is transmitted. The base station cannot determine whether the UE will repeatedly transmit Mg3 PUSCH. Therefore, to determine whether to receive Msg3 PUSCH rep#2, the base station measures the energy of the time-frequency resource in which Msg3 PUSCH rep#2 is expected to be transmitted and measures the correlation of the DMRS in the time-frequency resource in which the DMRS of Msg3 PUSCH rep#2 is expected to be transmitted. Based on the measurement results, the base station determines (confirms) whether the UE has transmitted Msg3 PUSCH rep#2. If the base station determines from the measurement results that Msg3 PUSCH rep#2 has been transmitted, the base station combines Msg3 PUSCH rep#1 and Msg3 PUSCH rep#2 to obtain a lower code rate, thereby increasing the possibility of decoding the TB transmitted by the Msg3 PUSCH.Since the code rate is obtained, the possibility of decoding the TB transmitted by the Msg3 PUSCH increases. The process by which the base station determines whether to repeatedly transmit the Msg3 PUSCH is repeatedly performed in slots in which the Msg3 PUSCH may be transmitted. However, in the case of a terminal that repeatedly transmits the Msg3 PUSCH, there is a possibility that coverage may be insufficient due to being located at the edge of the cell, which may result in degradation of performance for the measurement results. In addition, there is a problem that complexity increases because the base station must check whether to repeatedly transmit the Msg3 PUSCH for each slot.

[0225] FIG. 18 is a diagram illustrating repeated transmission of Msg3 PUSCH using three DMRSs according to one embodiment of the present invention.

[0226] Referring to Figure 18, there are three methods for transmitting the Msg3 PUSCH by the terminal. (a) The terminal transmits the Msg3 PUSCH without repeating it. In other words, the terminal transmits the Msg3 PUSCH only in one slot and does not repeat it in the next slot. (b) The terminal transmits the Msg3 PUSCH twice. This is applied when the uplink channel environment is poor but more repeated transmissions of the Msg3 PUSCH are not necessary. (c) The terminal transmits the Msg3 PUSCH four times. This is applied when the uplink channel environment is poorer than method (b).

[0227] 18, the terminal uses DMRS to indicate to the base station the transmission method of the Msg3 PUSCH (whether or not to transmit repeatedly). Specifically, if the terminal transmits the Msg3 PUSCH in method (a), DMRS A is used to indicate the transmission method of the Msg3 PUSCH. If the terminal transmits the Msg3 PUSCH in method (b), DMRS B of Msg3 PUSCH rep#1 and Msg3 PUSCH rep#2 in each of the two slots is used to indicate the transmission method of the Msg3 PUSCH. If the terminal transmits the Msg3 PUSCH in method (c), DMRS C of Msg3 PUSCH rep#1, Msg3 PUSCH rep#2, Msg3 PUSCH rep#3, and Msg3 PUSCH rep#4 in each of the four slots is used to indicate the transmission method of the Msg3 PUSCH. In other words, when the base station receives DMRS A, it recognizes that the Msg3 PUSCH is transmitted once; when it receives DMRS B, it recognizes that the Msg3 PUSCH is transmitted twice; and when it receives DMRS C, it recognizes that the Msg3 PUSCH is transmitted four times.

[0228] Different base sequences are applied to DMRS A, DMRS B, and DMRS C. Because different base sequences are applied to DMRS A, DMRS B, and DMRS C, the base station measures the correlation diagram between each base sequence to determine which base sequence is applied.

[0229] DMRS A, DMRS B, and DMRS C have the same basic sequence but are initialized to different sequence initialization values. If DMRS A is sequence initialized to value 1, DMRS B and DMRS C are sequence initialized to values ​​2 and 3, respectively. The base station measures the correlation diagram assuming sequence initialization to values ​​1, 2, and 3 and determines which sequence initialization value was used based on the correlation diagram measurement results. For example, the DMRS for Msg3 PUSCH with transmit precoding activated is shown in Equation 1 below.

[0230] [Formula 1]

number

[0231] N in Equation 1 slot symb is the number of symbols per slot, n μ s、f is the slot index within the frame whose subcarrier spacing configuration is μ, l is the OFDM symbol index within the slot, and N ID nSCID is the DMRS sequence initialization value n SCID It means a scrambling identity according to (0 to 1). Referring to Equation 1, DMRS A, DMRS B, and DMRS C are divided into at least different c_init values.

[0232] DMRS A, DMRS B, and DMRS C are transmitted through different DMRS ports. In other words, the terminal transmits the Msg3 PUSCH through different DMRS ports. The base station determines which DMRS is used based on the DMRS port of the Msg3 PUSCH transmitted by the terminal.

[0233] The base station determines whether the DMRS in the first slot in which the Msg3 PUSCH is transmitted is DMRS A, DMRS B, or DMRS C, and checks whether and how many times the Msg3 PUSCH is repeatedly transmitted, and then receives the Msg3 PUSCH according to the DMRS determination result.

[0234] However, since a UE with poor coverage repeatedly transmits the Msg3 PUSCH, the probability that the base station correctly determines the DMRS of the Msg3 PUSCH may be low, and therefore, it may be difficult for the base station to accurately determine the transmission method of the Msg3 PUSCH in the first slot using one DMRS among multiple DMRSs (DMRS A, DMRS B, DMRS C). Therefore, hereinafter, a method will be described in which the UE indicates the transmission method of the Msg3 PUSCH using two DMRSs (DMRS A and DMRS B).

[0235] 19 to 21 are diagrams illustrating a method for transmitting an Msg3 PUSCH using two DMRSs according to an embodiment of the present invention.

[0236] Referring to FIG. 19, (a) if the Msg3 PUSCH is not repeatedly transmitted, DMRS A is used to indicate the transmission method of the Msg3 PUSCH. (b) If the Msg3 PUSCH is repeatedly transmitted twice or (c) if it is repeatedly transmitted four times, DMRS B is used to indicate the transmission method of the Msg3 PUSCH. That is, the terminal uses DMRS A or DMRS B to inform the base station whether or not to repeatedly transmit the Msg3 PUSCH. The base station determines whether or not the Msg3 PUSCH is repeatedly transmitted using the DMRS in the first slot in which the Msg3 PUSCH is transmitted. For example, if the base station determines that the received DMRS is DMRS A, it determines that the Msg3 PUSCH is not repeatedly transmitted. Conversely, if the base station determines that the received DMRS is DMRS B, it determines that the Msg3 PUSCH is repeatedly transmitted.

[0237] DMRS A may be the same as or different from the DMRS of a terminal that does not have the capability to repeatedly transmit the Msg3 PUSCH. If the DMRSs are the same, even if the base station determines that the DMRS on the slot is DMRS A, it cannot determine whether the terminal that transmitted the Msg3 PUSCH is capable of repeatedly transmitting the Msg3 PUSCH. Therefore, when instructing retransmission of the Msg3 PUSCH, it must additionally determine whether it cannot instruct repeated transmission for the retransmission, or whether the retransmission was repeatedly transmitted even if it was instructed. On the other hand, if the DMRSs are different (i.e., the base station receives DMRS B), the base station determines that the terminal that transmitted the Msg3 PUSCH is capable of repeatedly transmitting the Msg3 PUSCH. Therefore, when instructing retransmission of the Msg3 PUSCH, the base station instructs repeated transmission of the retransmission.

[0238] Referring to FIG. 20, if the UE does not transmit an Msg3 PUSCH in a slot after the first slot, it transmits DMRS A in the first slot, and if the Msg3 PUSCH is repeatedly transmitted in a slot after the first slot, it transmits DMRS B in the first slot. That is, if the Msg3 PUSCH is not repeatedly transmitted or if the Msg3 PUSCH transmitted in the first slot is the last of the repeated Msg3 PUSCHs, DMRS A is used. For example, referring to FIG. 20a, DMRS A is used because the UE does not repeatedly transmit an Msg3 PUSCH. Referring to FIG. 20b, since the Msg3 PUSCH is repeatedly transmitted in the first and second slots, DMRS B is transmitted in the first slot and DMRS A is transmitted in the second slot. Referring to FIG. 20c, since the Msg3 PUSCH is repeatedly transmitted in the first, second, third, and fourth slots, DMRS B is transmitted in the first, second, and third slots, and DMRS A is transmitted in the fourth slot. That is, the base station determines for each slot whether the DMRS including the Msg3 PUSCH is DMRS A or DMRS B. If the DMRS determined in the first slot is DMRS A, the base station determines that there is no Msg3 PUSCH to be transmitted in slots after the first slot. Conversely, if the DMRS determined in the first slot is DMRS B, the base station determines that the Msg3 PUSCH will be repeatedly transmitted in slots after the first slot. Meanwhile, although the base station determines the DMRS for each slot, there are cases where it is not necessary to determine the DMRS for a particular slot. For example, if the candidate repetition counts for Msg3 PUSCH configured in the terminal are {R_1, R_2, ..., R_r}, DMRS A is transmitted only in the R_1th slot, R_2th slot, and R_rth slot. Therefore, the base station can determine whether there is additional Msg3 PUSCH transmission by determining only the DMRS in the R_1, R_2, ..., R_rth slots. In particular, if the candidate repetition counts for Msg3 PUSCH configured in the terminal are {1, 2, 4}, DMRS A is transmitted only in the first, second, and fourth slots.Therefore, if the Msg3 PUSCH is repeatedly transmitted four times as shown in Figure 20c, the base station only needs to determine the DMRS of the first, second, and fourth slots. In other words, there is no need to determine the DMRS of the third slot in Figure 20c. However, in the method described with reference to Figure 20, if the base station fails to receive the Msg3 PUSCH transmitting DMRS A, the base station cannot determine the slot at which the transmission of the Msg3 PUSCH ends. For example, in the case of an Msg3 PUSCH that is repeatedly transmitted twice, if the base station fails to receive the Msg3 PUSCH containing the DMRS transmitted in the second slot, the base station cannot determine the slot at which the transmission of the Msg3 PUSCH ends.

[0239] Referring to FIG. 21, the UE transmits DMRS A included in the Msg3 PUSCH of a specific number of consecutive slots. The specific number is a predetermined value determined by the number of times the Msg3 PUSCH is repeatedly transmitted. The specific number is half the number of times the Msg3 PUSCH is repeatedly transmitted. That is, if the Msg3 PUSCH is repeatedly transmitted twice, the specific number is 1, and if it is repeatedly transmitted four times, the specific number is 2. In other words, if the Msg3 PUSCH is repeatedly transmitted R times, the specific number is f(R / 2). Here, f(x) is a function that returns any one of the values ​​of x rounded down, rounded up, and rounded up. The specific number of consecutive slots is calculated from the slot at which the repeated transmission of the Msg3 PUSCH ends. Referring to Figure 21c, the Msg3 PUSCH is repeatedly transmitted four times, with the Msg3 PUSCH including DMRS A being transmitted in two consecutive slots from the last slot (i.e., the third and fourth slots). In the method of Figure 21, if the base station determines that the DMRS transmitted in at least one of the third and fourth slots is DMRS A, the base station can determine that transmission of the Msg3 PUSCH ends in the fourth slot.

[0240] In the method using two DMRSs described with reference to Figures 19 to 21, different DMRSs are transmitted in different slots. However, if the base station needs to perform joint channel correction, the same DMRS needs to be transmitted. Therefore, the method using two DMRSs is applicable to all situations except when joint channel estimation is performed.

[0241] Method for signaling information regarding repeated transmission of Msg3 PUSCH using UCI bits 22 to 26 are diagrams illustrating a method for determining the number of modulation symbols for multiplexing uplink control information included in Msg3 PUSCH according to an embodiment of the present invention.

[0242] The number of modulation symbols for transmitting uplink control information (UCI) per layer mapped to the Msg3 PUSCH is calculated as shown in Equation 2. Equation 2 is also used to calculate the number of modulation symbols when multiplexing and transmitting HARQ-ACK onto the PUSCH.

[0243] [Formula 2]

number

[0244] In Equation 2, O CUI L means the number of bits indicating whether or not repeated transmission of Msg3 PUSCH is performed and the number of repeated transmissions. UCI O CUI means the number of CRC bits used when channel coding β PUSCH offset is an offset value for determining the number of resources for mapping UCI to Msg3 PUSCH, and is set by the SIB. UL-SCH K denotes the number of code blocks (CB) included in the Msg3 PUSCH. rmeans the rth CB size included in Msg3 PUSCH. UCI SC (l) denotes the number of REs used for UCI transmission in the l-th symbol of Msg3 PUSCH. N PUSCH symb、all means the total number of symbols used to transmit Msg3 PUSCH including DMRS. The scaling value can be set via SIB. l0 means the index of the first non-DMRS PUSCH symbol after the DMRS symbol. For example, if DMRS is transmitted in the lth symbol, M UCI SC (l) is 0, otherwise M UCI SC (l) is M PUSCH sc -M PT-RS sc (l). M PUSCH sc is the number of subcarriers scheduled for PUSCH in the frequency domain, M PT-RS sc (l) means the number of subcarriers in the l-th PUSCH symbol including the PTRS. The terminal uses Q' calculated from Equation 2. UCI The UCI is multiplexed onto the PUSCH based on the modulation symbols (number of REs). UCI These modulation symbols are Q' of Msg3 PUSCH. UCI In this case, the mapping method is the same as that used when HARQ-ACK is multiplexed onto PUSCH. That is, Q' is mapped to the symbol immediately after the DMRS symbol of Msg3 PUSCH. UCI REs are selected.

[0245] A UE that does not support repeated transmission of the Msg3 PUSCH cannot transmit the Msg3 PUSCH by UCI multiplexing. Therefore, when receiving the Msg3 PUSCH, the base station must determine whether the UCI is multiplexed. For example, if the size of the UCI bits is less than or equal to 2 bits, the UE may transmit the Msg3 PUSCH in Q' of the REs in which the Msg3 PUSCH is transmitted. UCIPuncturing REs to obtain Q' UCI Therefore, the base station does not need to distinguish whether UCI is multiplexed or not. UCI On the other hand, if the size of the UCI bits is greater than 2 bits, the Msg3 PUSCH is mapped to Q' UCI The Msg3 PUSCH is rate-matched around REs and transmitted. The base station must decode the Msg3 PUSCH twice because the matching of the Msg3 PUSCH changes depending on the rate matching between when the UCI is multiplexed and when it is not multiplexed. Therefore, to reduce the number of decoding times at the base station, the size of the UCI bits must be limited to 2 bits or less.

[0246] If the size of the UCI bit is 1 bit, i) the UCI bit indicates that the number of repetitions of Msg3 PUSCH is 1 or R. R is a value set in the SIB. If 1 is not separately set and the value of the size of the UCI bit is "0", the number of repetitions is always determined to be 1. ii) the UCI bit indicates that the number of repetitions of Msg3 PUSCH is R_1 or R_2. The values ​​of R_1 and R_2 are values ​​set in the SIB. In this case, R_1 and R_2 are not 1.

[0247] If the size of the UCI bits is 2 bits, the UCI bits i) indicate that the number of repetitions of Msg3 PUSCH is 1, R_1, R_2, or R_3. R_1, R_2, and R_3 are values ​​set in the SIB. If 1 is not separately set and the UCI bits are '00', the number of repetitions is always determined to be 1. ii) The UCI bits indicate that the number of repetitions of Msg3 PUSCH is R_1, R_2, R_3, or R_4. R_1, R_2, R_3, and R_4 are values ​​set in the SIB.

[0248] If the UE needs to specify a more diverse number of repeated transmissions, such as {1, 2, 4, 8, 16, 32}, the size of the UCI bits should be greater than 2. Therefore, a method for transmitting UCI exceeding 2 bits will be described.

[0249] Referring to Figure 23, the UE generates sub-UCI by grouping UCI bits by up to two bits. The UE transmits the sub-UCI in the first slot and the second slot, respectively. The UE multiplexes and transmits the first sub-UCI with the Msg3 PUSCH in the first slot, and multiplexes and transmits the second sub-UCI with the Msg3 PUSCH in the second slot. The base station receives the first sub-UCI and the second sub-UCI transmitted in the first slot and the second slot, respectively, and generates all UCI bits. The base station then determines the number of repeated transmissions of the Msg3 PUSCH based on all UCI bits. Referring to Figure 24, the UE multiplexes a 1-bit UCI bit value "0" or "1" into the Msg3 PUSCH for each slot, and transmits the Msg3 PUSCH. A UCI bit value of '0' indicates that the Msg3 PUSCH is repeatedly transmitted in a slot following the slot in which the Msg3 PUSCH multiplexed with the UCI bit value '0' is transmitted. A UCI bit value of '1' indicates that the slot in which the Msg3 PUSCH multiplexed with the UCI bit value '1' is transmitted is the last slot in which the Msg3 PUSCH is transmitted. Referring to Figure 24b, the UE multiplexes the UCI bit value '0' onto the Msg3 PUSCH transmitted in the first slot because the Msg3 PUSCH is repeatedly transmitted in the second slot (the slot following the first slot). The UE multiplexes the UCI bit value '1' onto the Msg3 PUSCH transmitted in the second slot because the second slot is the last slot in which the Msg3 PUSCH is repeatedly transmitted. Referring to Figure 24c, the terminal multiplexes the UCI bit value "0" into the Msg3 PUSCH transmitted in the first, second, and third slots, respectively, because the Msg3 PUSCH is repeatedly transmitted in the second slot (the slot after the first slot), the third slot (the slot after the second slot), and the fourth slot (the slot after the third slot).The UE multiplexes the UCI bit value '1' into the Msg3 PUSCH transmitted on the fourth slot. This is because the fourth slot is the last slot in which the Msg3 PUSCH is repeatedly transmitted. In the method of multiplexing the UCI bit value '0' or '1' described with reference to FIG. 24, if the base station cannot receive the Msg3 PUSCH multiplexed with the UCI bit value '1', it is unable to determine the slot in which the repeatedly transmitted Msg3 PUSCH is terminated. For example, in the case of FIG. 24b, the number of repeated transmissions of the Msg3 PUSCH is 2. In this case, if the base station cannot receive the Msg3 PUSCH transmitted on the second slot, the base station cannot confirm the UCI bit value '1', and therefore is unable to determine the slot in which the repeatedly transmitted Msg3 PUSCH is terminated.

[0250] The UE multiplexes the UCI bit value "1" onto the Msg3 PUSCH transmitted over a specific number of consecutive slots. The specific number is a predetermined value determined based on the number of times the Msg3 PUSCH is repeatedly transmitted. The specific number is half the number of times the Msg3 PUSCH is repeatedly transmitted. Specifically, if the Msg3 PUSCH is repeatedly transmitted twice, the specific number is 1, and if the Msg3 PUSCH is repeatedly transmitted four times, the specific number is 2. In other words, if the Msg3 PUSCH is repeatedly transmitted R times, the specific number is f(R / 2). f(x) is a function that returns one of the values ​​of x rounded down, rounded up, and rounded up. The specific number of consecutive slots is selected from the slot in which the Msg3 PUSCH is repeatedly transmitted last. The specific number of consecutive slots is selected from the last slot in which the Msg3 PUSCH is repeatedly transmitted. Referring to Figure 25c, the Msg3 PUSCH is repeatedly transmitted four times. The UE multiplexes a UCI bit value of '1' into each of the Msg3 PUSCHs transmitted in two consecutive slots (the third and fourth slots) from the slot in which the Msg3 PUSCH is last repeatedly transmitted, and then transmits the Msg3 PUSCH. Comparing Figures 24c and 25c, in Figure 25c, when the base station confirms that the UCI bit value '1' is multiplexed into the Msg3 PUSCH transmitted in at least one of the third and fourth slots, the base station confirms that the Msg3 PUSCH ends in the fourth slot.

[0251] According to the above-described method, UCI is multiplexed for each slot, thereby reducing the number of REs used for transmitting the Msg3 PUSCH. Therefore, UCI needs to be multiplexed into as few slots as possible. For example, the base station determines that an Msg3 PUSCH in which a UCI bit value of "1" is not multiplexed is the same as an Msg3 PUSCH in which a UCI bit value of "1" is multiplexed. As another example, the UE multiplexes UCI into the Msg3 PUSCH for each certain slot and transmits the Msg3 PUSCH. For example, the UE bundles N slots in which the Msg3 PUSCH is repeatedly transmitted, and then multiplexes UCI into the first slot of each of the N bundled slots and transmits the Msg3 PUSCH. In this case, the N bundled slots are referred to as a slot bundle. If the Msg3 PUSCH is repeatedly transmitted in a slot bundle after the first slot bundle, the UE multiplexes a UCI bit value of '0' onto the Msg3 PUSCH transmitted in the (first) slot included in the first slot bundle. If the Msg3 PUSCH is not repeatedly transmitted in a slot bundle after the first slot bundle, the UE multiplexes a UCI bit value of '1' onto the Msg3 PUSCH transmitted in the (first) slot included in the first slot bundle. That is, the first slot bundle is the slot bundle in which the Msg3 PUSCH is last transmitted. Referring to FIG. 26b, the UE forms a slot bundle by bundling two slots. The UE multiplexes a UCI bit value of '1' onto the Msg3 PUSCH transmitted in the first slot of the first slot bundle. This is because the Msg3 PUSCH is not repeatedly transmitted in slot bundles after the first slot bundle. Referring to FIG. 26c, the UE forms a slot bundle by bundling two slots. The terminal multiplexes the UCI bit value “0” onto the Msg3 PUSCH transmitted on the first slot of the first bundle because the Msg3 PUSCH is repeatedly transmitted in the second slot bundle (the slot bundle after the first slot bundle).The terminal multiplexes the UCI bit value '1' into the Msg3 PUSCH transmitted on the first slot of the two slot bundles because the Msg3 PUSCH is not repeatedly transmitted in slot bundles after the second slot bundle.

[0252] Method for determining slots for repeated transmission of Msg3 PUSCH in TDD situations The base station sets the symbol direction for TDD operation.

[0253] The base station configures a cell common symbol direction for the terminal. The symbol direction is configured by SIB1 transmitted to the terminals present in the cell. The base station configures a cell common symbol direction for the cell by tdd-UL-DL-ConfigurationCommon in SIB1. The cell common symbol direction is determined to be one of UL symbol, DL symbol, and flexible symbol. A cell common UL symbol refers to a symbol used only for uplink transmission. A cell common DL symbol refers to a symbol used only for downlink transmission. A cell common flexible symbol refers to a symbol for which a specific direction is not determined and which can be changed to a UL symbol or DL ​​symbol by separate configuration.

[0254] The base station further configures the symbol direction specific to each terminal in the terminal. The symbol direction specific to each terminal is configured by RRC signaling during the random access procedure. In particular, the terminal is configured with the UE-specific symbol direction specific to each terminal by tdd-UL-DL-ConfigurationCommon. Since the directions of the cell-common UL symbol and cell-common DL symbol are determined, the direction cannot be further modified, and the cell-common flexible symbol is determined as the UE-specific symbol direction. The UE-specific symbol direction is determined as one of the UE-specific UL symbol, UE-specific DL symbol, and UE-specific flexible symbol. The UE-specific UL symbol refers to a symbol used only for uplink transmission. The UE-specific DL symbol refers to a symbol used only for downlink transmission. The UE-specific flexible symbol refers to a symbol for which a specific direction is not determined and which is changed to a UL symbol or DL ​​symbol by separate configuration.

[0255] The UE is configured with a cell-common symbol direction according to SIB1 received before receiving RRC signaling, and repeatedly transmits the Msg3 PUSCH. Therefore, the UE should repeatedly transmit the Msg3 PUSCH according to the cell-common symbol direction. In this case, the UE cannot determine whether the cell-common flexible symbol can be used for repeated transmission of the Msg3 PUSCH. For example, the base station configures the cell-common flexible symbol as a UE-specific DL symbol for other UEs. In this case, if the UE repeatedly transmits the Msg3 PUSCH using the cell-common flexible symbol, interference with other UEs may occur. Therefore, it is necessary to determine whether the cell-common flexible symbol can be used for repeated transmission of the Msg3 PUSCH. A method for determining this is described below.

[0256] 27 and 28 are diagrams illustrating resources available for repeated transmission of an Msg3 PUSCH according to an embodiment of the present invention. In Figures 27 and 28, a D slot refers to a slot including overlapping symbols if at least one of the symbols scheduled to transmit the Msg3 PUSCH overlaps with a cell-common DL symbol. A U slot refers to a slot including overlapping symbols if all of the symbols scheduled to transmit the Msg3 PUSCH overlap with a cell-common UL symbol. An F slot refers to a slot including overlapping symbols if at least one of the symbols scheduled to transmit the Msg3 PUSCH overlaps with a cell-common flexible symbol (in this case, the symbols scheduled to transmit the Msg3 PUSCH do not overlap with a cell-common DL symbol but overlap with a cell-common UL symbol).

[0257] Referring to FIG. 27, the UE is configured to repeatedly transmit the Msg3 PUSCH in two consecutive slots. In this case, the Msg3 PUSCH is transmitted in slots where transmission of the Msg3 PUSCH is possible, and is dropped without transmission in slots where transmission of the Msg3 PUSCH is not possible. i) Referring to FIG. 27a, the UE repeatedly transmits the Msg3 PUSCH in slots other than the D slot. That is, the UE repeatedly transmits the Msg3 PUSCH in the F and U slots, and drops the PUSCH scheduled in the D slot without transmitting it. However, the Msg3 PUSCH is transmitted using a cell-common flexible symbol, which may cause interference to other UEs. ii) Referring to FIG. 27b, the UE repeatedly transmits the Msg3 PUSCH only in the U slot. That is, the UE drops the Msg3 PUSCH scheduled in the D and F slots without transmitting it. Since the UE transmits the Msg3 PUSCH using only the UL symbol, it does not interfere with other UEs. iii) Referring to FIG. 27c, the UE transmits the first of the repeated transmissions of the Msg3 PUSCH in the slot indicated by the uplink grant (i.e., the slot in which the first of the repeated transmissions of the Msg3 PUSCH is transmitted), and in the next slot, it repeatedly transmits the Msg3 PUSCH only in the U slot. The UE drops the Mg3 PUSCH scheduled in the F and D slots after the slot indicated by the uplink grant without transmitting it. The slot indicated by the uplink grant is determined based on the slot in which the uplink grant is received and the K2 value. The K2 value is set by the base station and represents an offset value from the slot in which the uplink grant is received. That is, if the slot in which the uplink grant is received is the nth slot, the slot indicated by the uplink grant is the (n+K2)th slot. In this case, the slot indicated by the uplink grant is the F slot or the U slot. The base station intentionally configures the cell-common flexible symbol to be used for transmitting the Msg3 PUSCH.

[0258] Referring to FIG. 28, the UE is configured to transmit the Msg3 PUSCH four times repeatedly, i.e., repeatedly in four slots. Therefore, the UE should determine four slots in which the Msg3 PUSCH can be repeatedly transmitted. i) Referring to FIG. 28a, the UE determines the remaining slots excluding slot D as slots in which the Msg3 PUSCH can be transmitted. That is, the UE repeatedly transmits the Msg3 PUSCH in slots F and U. However, the Msg3 PUSCH is transmitted using a cell-common flexible symbol, which may cause interference to other UEs. ii) Referring to FIG. 28b, the UE repeatedly transmits the Msg3 PUSCH only in slot U. That is, the UE cannot repeatedly transmit the Msg3 PUSCH in slots F and U. Compared to the method described in FIG. 28a (method i), the Msg3 PUSCH is repeatedly transmitted in later slots, but since the Msg3 PUSCH is repeatedly transmitted only in the U slot, there is an advantage that interference with other terminals is not caused. iii) Referring to FIG. 28c, the terminal transmits the first of the repeated Msg3 PUSCH transmissions in the slot indicated by the uplink grant (i.e., the slot in which the first of the repeated Msg3 PUSCH transmissions is performed), and in the next slot, the Msg3 PUSCH is repeatedly transmitted only in the U slot. The terminal drops the Mg3 PUSCH scheduled in the F and D slots after the slot indicated by the uplink grant without transmitting it. The slot indicated by the uplink grant is determined based on the slot in which the uplink grant is received and the K2 value. The K2 value is set by the base station and represents an offset value from the slot in which the uplink grant is received. That is, if the slot in which the uplink grant is received is the nth slot, the slot indicated by the uplink grant is the (n+K2)th slot. In this case, the slot indicated by the uplink grant is the F slot or the U slot. The base station intentionally configures the cell-common flexible symbol to be used for transmitting the Msg3 PUSCH.

[0259] The base station configures via the uplink grant to use one of the methods described with reference to Figures 27 and 28. The base station configures a method for determining a slot in which the Msg3 PUSCH is repeatedly transmitted using some bits of a specific field of the uplink grant, and the terminal repeatedly transmits the Msg3 PUSCH based on the configured method. The Msg3 PUSCH in the methods described with reference to Figures 27 and 28 refers to the initial transmission of the Msg3 PUSCH and the retransmission of the Msg3 PUSCH.

[0260] In the above description, the cell-common DL symbols further include symbols configured with a Type-0 common search space (CSS) of CORESET0. Here, CORESET0 indicates the CORESET indicated by the PBCH. Here, the Type-0 common search space is a search space for monitoring DCI format 1_0 that schedules the PDSCH that transmits SIB1. The DCI format has a CRC scrambled by SI-RNTI. That is, the terminal regards symbols configured to receive Type-0 CSS of CORESET0 as symbols that can only be received in the downlink.

[0261] The cell common DL symbols further include symbols configured with the Type-0A CSS (common search space) of CORESET0. The Type-0A CSS is a search space for monitoring DCI of DCI format 1_0 that schedules PDSCH including SIBs excluding SIB1. In this case, the CRC of the DCI is scrambled with the SI-RNTI. The cell common DL symbols further include symbols configured with the Type-1 CSS of CORESET0. The Type-1 CSS is a search space for monitoring DCI that schedules Msg2 PDSCH or Msg4 PDSCH. In this case, the CRC of the DCI is scrambled with the RA-RNTI, MsgB-RNTI, or TC-RNTI. The cell common DL symbols further include symbols configured with the Type-2 CSS of CORESET0. The Type-2 CSS is a search space for monitoring DCI that transmits paging information. In this case, the DCI is scrambled with a CRC on the P-RNTI. The cell-common DL symbols further include symbols with a Type-3 CSS of CORESET0. The Type-3 CSS is a search space for monitoring DCI having various cell-common DCI formats. In this case, the DCI is scrambled with a CRC on the INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, C-RNTI, MCS-C-RNTI, CS-RNTI(s), or PS-RNTI.

[0262] The cell-common DL symbols further include symbols configured to receive SS / PBCH blocks. The symbols configured to receive SS / PBCH blocks are configured by SIB1, more specifically, by ssb-PositionsInBurst in SIB1. In other words, the terminal determines that the symbols configured to receive SS / PBCH blocks are symbols that can only receive downlink channels.

[0263] The cell-common UL symbols further include symbols configured to transmit PRACH. The symbols configured to transmit PRACH are symbols corresponding to valid RACH occasions (ROs). The UE receives a PRACH configuration from the base station via SIB1. In particular, the PRACH configuration is configured by rach-ConfigCommon in the initialUplinkBWP of the UplinkConfigCommonSIB in the ServingCellConfigCommonSIB in SIB1. The UE determines a valid RO based on the PRACH configuration. A method for determining a valid RO will be described below.

[0264] a. If tdd-UL-DL-ConfigurationCommon is not configured in the terminal, N symbols from the last symbol of the SS / PBCH block shall not precede the SS / PBCH block. gap ROs that are more than one symbol apart are determined to be valid ROs.

[0265] b. If tdd-UL-DL-ConfigurationCommon is configured in the terminal, all symbols of RO are superimposed with cell common UL symbols, or RO does not precede the SS / PBCH block and is N symbols from the last symbol of the SS / PBCH block gap ROs that are more than one symbol apart are determined to be valid ROs.

[0266] The terminal transmits the PRACH using a valid RO. That is, the base station considers the valid RO to be used for uplink channel transmission. The cell-common UL symbol is N symbols before the valid RO. gap In this case, the symbols scheduled for PRACH transmission are valid RO symbols. gap This is because the terminal does not receive a downlink channel or signal in the N symbols. gap The symbols are considered to be used for uplink transmission. gapis 0 if the subcarrier spacing of the PRACH is 1.25 kHz or 5 kHz, and is 2 if the subcarrier spacing is 15 kHz, 30 kHz, 60 kHz, or 120 kHz.

[0267] Frequency hopping method for repeated transmission of uplink channel A frequency hopping method applied when a terminal repeatedly transmits an uplink channel will be described below.

[0268] The base station configures the long PUCCH (i.e., PUCCH formats 1, 3, and 4) to be repeatedly transmitted in 2, 4, or 8 slots for the PUCCH coverage of the terminal. When the terminal enters the RRC connected mode (RRC_CONNECTED mode) after initial cell access, the terminal is configured with the number of PUCCH repetitions (nrofSlots) for each PUCCH format according to terminal-specific system information. For example, if the PUCCH formats transmitted on the configured resource for the terminal include PUCCH formats 1, 3, and 4, the number of repetitions for each PUCCH format (nrofSlots) is set to a different number.

[0269] If the UE is configured to transmit the PUCCH repeatedly N times, N slots in which the PUCCH can be transmitted are determined sequentially from the slot configured or indicated for PUCCH transmission. In slots in which the PUCCH can be transmitted, the symbol scheduled to transmit the PUCCH in the slot must not overlap with a semi-statically configured DL symbol or a symbol set to receive an SS / PBCH block. If the symbol scheduled to transmit the PUCCH overlaps with a semi-statically configured DL symbol or a symbol set to receive an SS / PBCH block, the UE does not transmit the PUCCH in the corresponding slot, and the corresponding slot is not included in the N slots for PUCCH transmission.

[0270] Before the terminal completes the repeated transmission of the PUCCH for the number of times of repeated transmission of the PUCCH preset by the base station, a new repeated transmission of the PUCCH is set by the base station. When the terminal enters the RRC connected mode after the first cell access, the terminal is set to repeatedly transmit the PUCCH N times according to the terminal-specific system information. Next, when the channel environment improves, the terminal is newly set to repeatedly transmit the PUCCH M (<N) times to reduce the overhead of the uplink control channel and uplink interference. Conversely, when the channel environment deteriorates, the terminal is newly set to repeatedly transmit the PUCCH M (>N) times to increase the coverage of the uplink control channel. Here, the number of repeated transmissions (M) includes 1. That is, when the terminal receives the setting for the repeated transmission of the new PUCCH, it ignores the setting for the repeated transmission of the previously set PUCCH and repeatedly transmits the new PUCCH based on the setting for the repeated transmission of the new PUCCH.

[0271] The terminal receives explicit information from the base station to determine a new PUCCH repetition count. The explicit information is the PUCCH repetition count. The explicit information is included in the DCI included in the PDCCH that schedules the corresponding PDSCH. The PDSCH corresponding to the PUCCH is a PUCCH that includes HARQ-ACK information for the corresponding PDSCH. When the number of configurable PUCCH repetition counts is K, the explicit information is indicated as ceil(log2(K)) bits. For example, when the configurable PUCCH repetition counts are 1, 2, 4, and 8, K=4, so the explicit information is indicated as ceil(log2(4))=2 bits. The configurable PUCCH repetition count is one of {1, 2, 4, 8}. The base station configures multiple PUCCH repetition counts from the configurable PUCCH repetition counts as explicit information. For example, the base station sets {2, 4} of the PUCCH repetition transmission count {1, 2, 4, 8} as explicit information. The commandable PUCCH repetition transmission count is one of {1, 2, 4, 8, N}, where N is a value preset for each PUCCH format. The base station sets a plurality of PUCCH repetition transmission counts from the commandable PUCCH repetition transmission counts as explicit information. In this case, the plurality of PUCCH repetition transmission counts set as explicit information includes N. For example, the base station sets {2, N} of the PUCCH repetition transmission count {1, 2, 4, 8, N} as explicit information. The commandable PUCCH repetition transmission count is one of {N / 4, N / 2, N, 2*N, 4*N}. In this case, the base station sets {N / 2, N} as the PUCCH repetition transmission count. If N / 4 is set as explicit information, the terminal repeatedly transmits the PUCCH for 1 / 4 of the preset N (i.e., once if N=4, twice if N=8). Similarly, if N / 2 is set as explicit information, the terminal repeatedly transmits the PUCCH for 1 / 2 of the preset N (i.e., once if N=2, twice if N=4, four times if N=8).If 2*N is set as explicit information, the terminal repeatedly transmits the PUCCH twice as many times as N (i.e., two repetitions if N=1, four repetitions if N=2, and eight repetitions if N=4). If 4*N is set as explicit information, the terminal repeatedly transmits the PUCCH four times as many times as N (i.e., four repetitions if N=1, and eight repetitions if N=2). If N / 4 and N / 2 are smaller than 1, the number of repeated transmissions of the PUCCH is 1. If 2*N and 4*N are greater than 8, the number of repeated transmissions of the PUCCH is 8.

[0272] Conventionally, the number of repetitions of a PUCCH was set to be different for each PUCCH format. When a new resource for transmitting a PUCCH is set in a UE and the UE repeatedly transmits the new PUCCH, if the previous PUCCH format and the newly set PUCCH format are the same, the UE repeatedly transmits the newly set PUCCH for the number of repetitions corresponding to the PUCCH format. For example, the PUCCH format transmitted in a resource with a PUCCH resource ID set to 0 is PUCCH format 1, and the number of repetitions is set to 8, and the PUCCH format transmitted in a resource with a PUCCH resource ID set to 1 is PUCCH format 1, and the number of repetitions is set to 2. Next, if the PUCCH resource ID indicated in the PRI (PUCCH resource indicator, PRI) field of DCI included in the PDCCH of the PDSCH corresponding to the PUCCH is 0, the UE repeatedly transmits the PUCCH of PUCCH format 1 in 8 slots, and if the PUCCH resource ID is 1, the UE repeatedly transmits the PUCCH of PUCCH format 1 in 2 slots. The number of repetitions of the PUCCH for each resource on which the PUCCH is transmitted is one of {1, 2, 4, 8}. On the other hand, if the number of repetitions of the PUCCH is not set for the resource on which the PUCCH is transmitted, the UE repeatedly transmits the PUCCH according to the number of repetitions set by the PUCCH format.

[0273] Hereinafter, a method for setting frequency hopping by the base station when the terminal is configured to be able to repeatedly transmit the PUCCH will be described.

[0274] Intra-slot frequency hopping The terminal divides the PUCCH in half in the time domain, matches two hops within a slot set for PUCCH transmission, and transmits the two hops to the base station. In this case, the PUCCH may or may not be transmitted repeatedly. If the length (number) of symbols assigned to transmit the PUCCH in one slot is number of symbols, floor(number of symbols / 2) symbols are matched to the first hop, and number of symbols-floor(number of symbols / 2) symbols are matched to the second hop. The first hop is transmitted on the first frequency band, and the second hop is transmitted on the second frequency band. The PRBs of the first hop are composed of PRBs ranging from the PRB corresponding to the starting PRB index set by the base station to the number of PRBs set by the base station. The PRBs of the second hop are composed of PRBs ranging from the PRB corresponding to the PRB index at which the second hop starts to the number of PRBs set by the base station.

[0275] Inter-slot frequency hopping The slot index for repetition is sequentially indexed based on the slot in which the first PUCCH of the repeatedly transmitted PUCCH is transmitted. The repeat transmission index for the slot in which the first PUCCH is transmitted is 0. The repeat transmission slot index is sequentially indexed for slots after the slot in which the first PUCCH is transmitted. The repeat transmission slot index is determined regardless of whether repeated transmission of the PUCCH is possible in the corresponding slot. For example, if the UE is configured to repeatedly transmit the PUCCH four times in slot X, the UE determines the index for slot X to be 0, the index for slot X+1 to be 1, the index for slot X+2 to be 2, and the index for slot X+3 to be 3. Based on the determined repeat transmission slot index, the UE maps the PUCCH to the first hop in the slot corresponding to the even-numbered repeat transmission slot index. The UE maps the PUCCH to the second hop in the slot corresponding to the odd-numbered repeat transmission slot index. The first hop is transmitted on a first frequency band, and the second hop is transmitted on a second frequency band. The PRBs of the first hop are composed of PRBs from the PRB corresponding to the starting PRB index set by the base station to the number of PRBs set by the base station. The PRBs of the second hop are composed of PRBs from the PRB corresponding to the starting PRB index set by the base station to the number of PRBs set by the base station.

[0276] PUCCH frequency hopping method The base station sets either intra-slot frequency hopping or inter-slot frequency hopping to the mobile station.

[0277] The base station sets whether intra-slot frequency hopping is possible for each resource configured for transmission of PUCCH. For example, if a UE is configured with a resource having a PUCCH resource ID of 1 in a resource set having a PUCCH resource set ID of 0, it is set as to whether intra-slot frequency hopping is possible. If the base station configures that intra-slot frequency hopping is possible, the UE transmits the PUCCH through intra-slot frequency hopping, and if the base station configures that intra-slot frequency hopping is not possible, the UE transmits the PUCCH without intra-slot frequency hopping.

[0278] The base station sets whether inter-slot frequency hopping is possible for each PUCCH format. For example, the base station sets whether inter-slot frequency hopping is possible for the PUCCH of PUCCH format 1. If the base station sets that inter-slot frequency hopping is possible, the terminal transmits the PUCCH by inter-slot frequency hopping regardless of the resource on which the PUCCH is set. If the base station sets that inter-slot frequency hopping is not possible, the terminal transmits the PUCCH according to the resource on which the PUCCH is set. In other words, the terminal transmits the PUCCH according to the availability of intra-slot frequency hopping, which is set for each resource on which PUCCH transmission is set.

[0279] If the UE is configured to allow inter-slot frequency hopping for a specific PUCCH format, it expects that the resource on which the PUCCH of the specific PUCCH format is transmitted will not be configured for inter-slot frequency hopping. In other words, if the base station is configured to allow inter-slot frequency hopping according to the PUCCH format, it will not configure intra-slot frequency hopping according to the resource on which the PUCCH is transmitted.

[0280] The base station sets the number of repetitions (N) greater than 1 and that intra-slot hopping is possible for the first PUCCH repeatedly transmitted in a specific PUCCH format. Then, the terminal sets the number of repetitions of the new PUCCH to 1. At this time, since intra-slot hopping is configured to be possible, the terminal does not expect that the corresponding PUCCH is configured to be capable of inter-slot frequency hopping. In other words, if the PUCCH of a specific PUCCH format is configured to perform inter-slot frequency hopping, the new PUCCH will not be transmitted by intra-slot frequency hopping regardless of the number of repetitions of the new PUCCH. Therefore, a method for determining a frequency hopping method according to the number of repetitions of the new PUCCH is required.

[0281] FIG. 29 illustrates a method for determining a frequency hopping method depending on the number of repeated transmissions of a PUSCH according to an embodiment of the present invention.

[0282] The UE determines the frequency hopping method by interpreting the upper layer field differently depending on the number of repeated transmissions of the new PUCCH. Specifically, the UE interprets the intra-slot frequency hopping or inter-slot frequency hopping value in the upper layer field depending on whether the number of repeated transmissions of the PUCCH is 1 or not. Referring to FIG. 29, nrofSlots indicates the number of repeated transmissions of the PUCCH configured by the base station, and intraSlotFrequencyHopping indicates whether intra-slot frequency hopping can be performed. If intraSlotFrequencyHopping is set to enabled, intra-slot frequency hopping is performed; if not set, intra-slot frequency hopping is not performed. interSlotFrequencyHopping indicates whether inter-slot frequency hopping is performed. If interSlotFrequencyHopping is set to enabled, inter-slot frequency hopping is performed; if not set, inter-slot frequency hopping is not performed. If the number of repeated transmissions of the new PUCCH is 1, the UE checks whether intra-slot frequency hopping is set to enabled, regardless of whether inter-slot frequency hopping is set in the upper layer. If intra-slot frequency hopping is set to enabled, the UE transmits the new PUCCH by performing intra-slot frequency hopping. If the number of repeated transmissions of the new PUCCH is not 1, the UE first checks whether inter-slot frequency hopping is set to enabled in the upper layer. If inter-slot frequency hopping is set to enabled, the UE repeatedly transmits the new PUCCH by performing inter-slot frequency hopping. In this case, the PUCCH is transmitted by performing only inter-slot frequency hopping regardless of whether intra-slot frequency hopping is set. If inter-slot frequency hopping is not set to enabled, the UE checks whether intra-slot frequency hopping is set to enabled in the upper layer.If intra-slot frequency hopping is enabled, the terminal repeatedly transmits the new PUCCH by performing intra-slot frequency hopping; if intra-slot frequency hopping is not set to enabled, the terminal repeatedly transmits the PUCCH without performing frequency hopping.

[0283] In other words, the terminal is configured to determine whether inter-slot frequency hopping is possible for each PUCCH format. The terminal is configured to determine whether intra-slot frequency hopping is possible for each resource configured to transmit the PUCCH. Alternatively, the terminal is configured to perform the number of repeated transmissions of the PUCCH. The terminal determines whether inter-slot frequency hopping is possible depending on whether intra-slot frequency hopping is possible for the resource configured to transmit the PUCCH based on the number of repeated transmissions. If the number of repeated transmissions is 1, inter-slot frequency hopping is not performed. If the number of repeated transmissions is greater than 1 and inter-slot frequency hopping is configured to be possible according to the PUCCH format, the terminal performs inter-slot frequency hopping regardless of whether intra-slot frequency hopping is configured. Conversely, if the number of repeated transmissions is greater than 1 and inter-slot frequency hopping is configured to be impossible according to the PUCCH format, the terminal performs frequency hopping depending on whether intra-slot frequency hopping is configured.

[0284] PUSCH frequency hopping method The frequency hopping method for the PUSCH is described below. The frequency hopping method for the PUSCH is set by a higher layer.

[0285] For example, the UE determines the frequency hopping method by interpreting the bit of the frequency hopping flag in the DCI corresponding to the new PUSCH differently depending on the number of repeated transmissions of the new PUSCH. In this case, the DCI is the DCI of the PDCCH that schedules the PUSCH. Specifically, the UE interprets the 1-bit frequency hopping flag differently depending on whether the number of repeated transmissions of the new PUSCH is 1 or not. i) If the number of repeated transmissions of the new PUSCH set by the UE is 1 and the bit value of the frequency hopping flag is 0, the UE transmits the PUSCH without performing frequency hopping. ii) If the number of repeated transmissions of the new PUSCH set by the UE is 1 and the bit value of the frequency hopping flag is 1, the UE transmits the PUSCH by performing intra-slot frequency hopping. iii) If the number of repeated transmissions of the new PUSCH set by the UE is greater than 1 and the bit value of the frequency hopping flag is 0, the UE transmits the PUSCH by performing intra-slot frequency hopping. iv) If the number of repeated transmissions of the new PUSCH set by the UE is greater than 1 and the bit value of the frequency hopping flag is 1, the UE performs inter-slot frequency hopping to repeatedly transmit the PUSCH. As another example, i) if the number of repeated transmissions of the new PUSCH set by the UE is 1 and the bit value of the frequency hopping flag is 0, the UE transmits the PUSCH without performing frequency hopping. ii) if the number of repeated transmissions of the new PUSCH set by the UE is 1 and the bit value of the frequency hopping flag is 1, the UE transmits the PUSCH by performing intra-slot frequency hopping. iii) if the number of repeated transmissions of the new PUSCH set by the UE is greater than 1 and the bit value of the frequency hopping flag is 0, the UE repeatedly transmits the PUSCH without performing frequency hopping. iv) if the number of repeated transmissions of the new PUSCH set by the UE is greater than 1 and the bit value of the frequency hopping flag is 1, the UE performs inter-slot frequency hopping to repeatedly transmit the PUSCH.

[0286] The UE determines the number of repetitions and the frequency hopping method of the new PUSCH as a pair and interprets the frequency hopping flag bit of the DCI corresponding to the new PUSCH differently to determine the number of repetitions and the frequency hopping method of the new PUSCH. The DCI corresponding to the new PUSCH is the DCI of the PDCCH that schedules the PUSCH. Specifically, the UE transmits the new PUSCH after the number of repetitions and the frequency hopping method of the new PUSCH are set as a pair (i.e., number of repetitions, hopping method) according to the DCI corresponding to the new PUSCH from the base station. In this case, up to two (number of repetitions, hopping method) can be set. In this case, the hopping method is one of three cases: intra-slot frequency hopping, inter-slot frequency hopping, and no frequency hopping.

[0287] Msg3 PUSCH frequency hopping method The above-mentioned new PUSCH is a new Msg3 PUSCH scheduled by an uplink grant in a random access response. The number of times the new Msg3 PUSCH is to be repeated is included in the uplink grant. The frequency hopping method used when the new Msg3 PUSCH is repeatedly transmitted will now be described.

[0288] The base station sets the frequency hopping method for repeated transmission of a new Msg3 PUSCH to achieve frequency diversification gain. The frequency hopping method is set by the 1-bit value of the frequency hopping flag in the uplink grant of the random access response that schedules the new Msg3 PUSCH. In the case of a retransmission Msg3 PUSCH, the frequency hopping method is set by the 1-bit value of the frequency hopping flag in the DCI of DCI format 0_0 scrambled with the TC-RNTI that schedules the retransmission Msg3 PUSCH. If the bit value of the frequency hopping flag is 0, the terminal repeatedly transmits the new Msg3 PUSCH without performing frequency hopping. If the bit value of the frequency hopping flag is 2, the terminal repeatedly transmits the new Msg3 PUSCH by performing intra-slot frequency hopping. When the terminal repeatedly transmits the Msg3 PUSCH, if inter-slot frequency hopping is possible, inter-slot frequency hopping is more advantageous than intra-slot frequency hopping in terms of DMRS overhead. Hereinafter, a method in which the terminal repeatedly transmits a new Msg3 PUSCH by performing inter-slot frequency hopping will be described.

[0289] The UE interprets the bit of the frequency hopping flag according to the number of repeated transmissions of the new Msg3 PUSCH and determines the frequency hopping method. Specifically, the UE interprets the frequency hopping flag differently depending on whether the number of repeated transmissions of the new Msg3 PUSCH is 1 or not. For example, i) if the number of repeated transmissions of the new Msg3 PUSCH set by the UE is 1 and the bit value of the frequency hopping flag is 0, the UE repeatedly transmits the Msg3 PUSCH without performing frequency hopping. ii) if the number of repeated transmissions of the new Msg3 PUSCH set by the UE is 1 and the bit value of the frequency hopping flag is 1, the UE performs intra-slot frequency hopping to transmit the new Msg3 PUSCH. iii) if the number of repeated transmissions of the new Msg3 PUSCH set by the UE is greater than 1 and the bit value of the frequency hopping flag is 0, the UE performs intra-slot frequency hopping to repeatedly transmit the new Msg3 PUSCH. iv) If the number of repetitions of the new Msg3 PUSCH set by the terminal is greater than 1 and the bit value of the frequency hopping flag is 1, the terminal performs inter-slot frequency hopping and repeatedly transmits the new Msg3 PUSCH. As another example, i) if the number of repetitions of the new Msg3 PUSCH set by the terminal is 1 and the bit value of the frequency hopping flag is 0, the terminal transmits the new Msg3 PUSCH without performing frequency hopping. ii) if the number of repetitions of the new Msg3 PUSCH set by the terminal is 1 and the bit value of the hopping flag is 1, the terminal transmits the new Msg3 PUSCH by performing intra-slot frequency hopping. iii) if the number of repetitions of the new Msg3 PUSCH set by the terminal is greater than 1 and the bit value of the frequency hopping flag is 0, the terminal determines to repeatedly transmit the new Msg3 PUSCH without performing frequency hopping. iv) If the number of repeated transmissions of the new Msg3 PUSCH set by the terminal is greater than 1 and the bit value of the frequency hopping flag is 1, the terminal performs inter-slot frequency hopping to repeatedly transmit the new Msg3 PUSCH.

[0290] The UE determines the number of repetitions and the frequency hopping method of the new Msg3 PUSCH by setting the number of repetitions and the frequency hopping method of the new Msg3 PUSCH as a pair and interprets the bits of the frequency hopping flag differently. Specifically, the UE sets the number of repetitions and the frequency hopping method of the new PUSCH as a pair (i.e., number of repetitions, hopping method) according to the DCI corresponding to the new PUSCH from the base station, and transmits the new Msg3 PUSCH. Specifically, the pair indicating the number of repetitions and the frequency hopping method of the new PUSCH is determined by the frequency hopping flag of the uplink grant of the random access response scheduling the Msg3 PUSCH or the DCI of DCI format 0_0. In this case, up to two (number of repetitions, hopping method) can be set. In this case, the hopping method is one of three cases: intra-slot frequency hopping, inter-slot frequency hopping, and no frequency hopping.

[0291] FIG. 30 is a flowchart illustrating a method for a terminal to transmit an Msg3 PUSCH according to one embodiment of the present invention.

[0292] Hereinafter, a method for the terminal described with reference to FIGS. 1 to 29 to transmit the Msg3 PUSCH will be described with reference to FIG.

[0293] The terminal receives system information block 1 (SIB1) from the base station (S3010). System information block 1 is another system information block (e.g., SIBx, where x = 1, 2, 3, ...) as described above. The terminal transmits a preamble for a random access procedure to the base station (S3020). The terminal receives a random access response (RAR) in response to the preamble from the base station (S3030). The random access response includes information for scheduling a physical uplink shared channel (PUSCH) that the terminal will transmit to the base station. The terminal transmits the PUSCH to the base station based on the random access response (S3040). The SIB1 includes information on a repetition count candidate set including values ​​for one or more repetition counts for repeatedly transmitting the PUSCH. The random access response includes information indicating one of the values ​​for the one or more repetition counts included in the repetition count candidate set. The PUSCH is repeatedly transmitted by one of the values. The random access response is a Physical Downlink Shared Channel (PDSCH) including an uplink (UL) grant. Information indicating one of the values ​​is included in at least one of a Time Domain Resource Allocation (TDRA) field, a Modulation and Coding Scheme (MCS) field, and a Transmit Power Control (TPC) field of the random access response. If the information indicating one of the values ​​is included in the MCS field, the one of the values ​​is indicated by one or more MSBs of the MCS field. On the other hand, if the information indicating one of the values ​​is included in the TPC field, the one of the values ​​is indicated by one or more LSBs of the TPC field. Each of the values ​​for the one or more repeated transmission counts is a power of 2. Specifically, the values ​​for the one or more repeated transmission counts are 1, 2, 4, and 8. The SIB1 includes at least one of information about the preamble and RACH opportunities. The PUSCH is transmitted on a resource determined based on one of information about the preamble and RACH opportunities.

[0294] After S3040, the UE receives downlink control information (DCI) from the base station, the DCI including information for scheduling a retransmission PUSCH. The UE repeatedly transmits the retransmission PUSCH to the base station based on the DCI. In this case, the information for scheduling the retransmission PUSCH includes information regarding the number of repetitions of the retransmission PUSCH. The information regarding the number of repetitions of the retransmission PUSCH is included in a HARQ process number field of the DCI. The retransmission PUSCH is the same as the PUSCH transmitted by the UE at S3040. The DCI is transmitted by the base station if the base station fails to receive the PUSCH transmitted by the UE. That is, if the base station fails to receive the PUSCH transmitted by the UE at S3040, the base station transmits information for scheduling the retransmission PUSCH to the UE.

[0295] The random access response includes a frequency hopping flag indicating whether the PUSCH is frequency hopping. The PUSCH is frequency hopped intra-slot or inter-slot based on any one of the values ​​and the frequency hopping flag. When any one of the values ​​is 1, if the value of the frequency hopping flag indicates that the PUSCH is frequency hopping, the PUSCH is frequency hopped intra-slot. When the value of the frequency hopping flag indicates that the PUSCH is not frequency hopping, the PUSCH is not frequency hopped. On the other hand, when any one of the values ​​is greater than 1, if the value of the frequency hopping flag indicates that the PUSCH is frequency hopping, the PUSCH is frequency hopped inter-slot. When the value of the frequency hopping flag indicates that the PUSCH is not frequency hopping, the PUSCH is not frequency hopped. In this case, the PUSCH is a retransmission PUSCH.

[0296] The random access response further includes information about a resource on which the first repeat transmission of the PUSCH is performed. The information about the resource on which the first repeat transmission of the PUSCH is performed is a slot offset value between the resource on which the random access response is received and the resource on which the first repeat transmission of the PUSCH is performed. The SIB1 further includes information about a TDD configuration, which is information about the type of symbols constituting a slot. In this case, the symbol type is one of a downlink symbol configured to be usable for downlink transmission, an uplink symbol configured to be usable for uplink transmission, and a flexible symbol not configured as the downlink symbol or the uplink symbol. The PUSCH is repeatedly transmitted in units of slots. The resource on which the first repeat transmission of the PUSCH is performed is a resource separated by the slot offset value from the resource on which the random access response is received. The resource on which the first repeat transmission of the PUSCH is performed is a flexible slot, and repeat transmissions after the first repeat transmission of the PUSCH are performed in uplink slots. The flexible symbol includes at least one of the flexible symbol, and all of the uplink slots are configured with the uplink symbols. In this case, the PUSCH is a retransmission PUSCH.

[0297] The terminal performing the method described in Figure 30 is the terminal described in Figure 11. In particular, the terminal includes a communication module for transmitting and receiving radio signals and a processor for controlling the communication mode. In this case, the processor of the terminal performs the method for transmitting Msg3 PUSCH described in this specification.

[0298] In addition, a base station that receives an Msg3 PUSCH transmitted by a terminal described in this specification includes a communication module for transmitting and receiving radio signals and a processor that controls the communication mode. In this case, the base station is the base station described in Fig. 11. In this case, the processor of the base station performs the method for receiving an Msg3 PUSCH transmitted by a terminal described in this specification.

[0299] Although the method and system of the present invention have been described in connection with particular embodiments, some or all of the components or operations thereof may be embodied by a computing system having a general-purpose hardware architecture.

[0300] The above description of the present invention is for illustrative purposes only, and those skilled in the art will understand that the present invention can be easily modified into other specific forms without changing the technical spirit or essential features of the present invention. Therefore, the above-described embodiments should be understood as illustrative in all respects and not restrictive. For example, each component described as a single component may be implemented in a distributed form, and similarly, each component described as a distributed component may be implemented in a combined form.

[0301] The scope of the present invention is indicated by the appended claims rather than the above detailed description, and any modifications or variations derived from the meaning and scope of the claims and their equivalents should be construed as being within the scope of the present invention. [Explanation of symbols]

[0302] 100 devices 110 processors 120 Communication Module 121 Cellular communication interface card 122 Cellular communication interface card 123 Unlicensed Spectrum Communication Interface Card 130 memory 140 User Interface 150 display units 200 base stations 210 processors 220 Communication Module 221 Cellular communication interface card 222 Cellular communication interface card 223 Unlicensed Spectrum Communication Interface Card 230 memory

Claims

1. In a method for transmitting an uplink channel in a wireless communication system, a method performed by a terminal includes: receiving a System Information Block 1 (SIB1) from a base station; transmitting a preamble for a random access procedure to the base station; receiving a Random Access Response (RAR) from the base station in response to the preamble; The random access response includes information for scheduling a physical uplink shared channel (PUSCH) that the terminal transmits to the base station; transmitting the PUSCH to the base station based on the random access response; The SIB1 includes information about a repeat transmission count candidate set including values ​​for one or more repeat transmission counts for performing repeat transmission of the PUSCH, the random access response includes information indicating one of values ​​for the one or more repeat transmission numbers included in the repeat transmission number candidate set; The PUSCH is transmitted repeatedly by one of the values.

2. The method of claim 1, wherein the random access response is a Physical Downlink Shared Channel (PDSCH) including an uplink (UL) grant.

3. 2. The method of claim 1, wherein the information indicating any one of the values ​​is included in at least one of a Time Domain Resource Assignment (TDRA) field, a Modulation Coding Scheme (MCS) field, and a Transmission Power Control (TPC) field of the random access response.

4. If information indicating any one of the values ​​is included in the MCS field, The method of claim 3, wherein the one of the values ​​is indicated by one or more Most Significant Bits (MSBs) of the bits of the MCS field.

5. If information indicating any one of the values ​​is included in the TPC field, The method of claim 3, wherein the one of the values ​​is indicated by one or more least significant bits (LSBs) of the bits of the TPC field.

6. The SIB1 includes at least one of information about the preamble and a RACH occasion, The method of claim 1, wherein the PUSCH is transmitted on a resource determined based on at least one of information about the preamble and the RACH opportunity.

7. receiving downlink control information (DCI) from the base station, the DCI including information for scheduling a retransmission PUSCH; and repeatedly transmitting the retransmission PUSCH to the base station based on the DCI; The information for scheduling the retransmission PUSCH includes information regarding the number of repetitions of the retransmission PUSCH, Information about the number of repetitions of the retransmission PUSCH is included in the HARQ process number field of the DCI, The retransmission PUSCH is the same as the PUSCH, The method of claim 1, wherein the DCI is transmitted by the base station if the base station fails to receive the PUSCH transmitted by the terminal.

8. The DCI is scrambled with the TC-RNTI; The method of claim 7, wherein the format of the DCI is DCI format 0_0.

9. 2. The method of claim 1, wherein each of the values ​​for the one or more repeated transmissions is a power of two.

10. 2. The method of claim 1, wherein the values ​​for the one or more repeated transmissions are 1, 2, 4, and 8, respectively.

11. The random access response includes a frequency hopping flag indicating whether the PUSCH is frequency hopping; The method of claim 1, wherein the PUSCH performs intra-slot frequency hopping or inter-slot frequency hopping based on any one of the values ​​and the frequency hopping flag.

12. If any one of the values ​​is 1, If the value of the frequency hopping flag indicates that the PUSCH is frequency hopping, the PUSCH is frequency hopped within a slot; The method of claim 11, wherein if the value of the frequency hopping flag indicates that the PUSCH does not frequency hop, the PUSCH does not frequency hop.

13. If any one of the values ​​is greater than 1, If the value of the frequency hopping flag indicates that the PUSCH is frequency hopping, the PUSCH is frequency hopped between slots; The method of claim 11, wherein if the value of the frequency hopping flag indicates that the PUSCH does not frequency hop, the PUSCH does not frequency hop.

14. The random access response further includes information about a resource on which the first repeated transmission of the PUSCH is performed, The information about the resource on which the first repeated transmission of the PUSCH is performed is a slot offset value between the resource on which the random access response is received and the resource on which the first repeated transmission of the PUSCH is performed, The SIB1 further includes information about the TDD configuration, The information about the TDD configuration is information about a type of symbol constituting a slot, the type of the symbol is any one of a downlink symbol set to be usable for downlink transmission, an uplink symbol set to be usable for uplink transmission, and a flexible symbol that is not set to the downlink symbol or the uplink symbol; The PUSCH is repeatedly transmitted in slot units, The method of claim 1, wherein a resource in which the first repeated transmission of the PUSCH is performed is a resource that is separated by the slot offset value from a resource in which the random access response is received.

15. The resource in which the first repeated transmission of the PUSCH is performed is a flexible slot, Repeated transmissions after the first repeated transmission of the PUSCH are performed on uplink slots; the flexible slot is configured to include at least one of the flexible symbols; The method of claim 14, wherein the uplink slots are all comprised of the uplink symbols.

16. In a terminal that transmits an uplink channel in a wireless communication system, the terminal A transmitter / receiver; a processor for controlling the transceiver; The processor: receiving system information block 1 (SIB1) from the base station; transmitting a preamble for a random access procedure to the base station; receiving a random access response (RAR) to the preamble from the base station; The random access response includes information for scheduling a physical uplink shared channel (PUSCH) that the terminal transmits to the base station; The base station transmits the PUSCH based on the random access response; The SIB1 includes information about a repeat transmission count candidate set including values ​​for one or more repeat transmission counts for performing repeat transmission of the PUSCH, the random access response includes information indicating one of values ​​for the one or more repeat transmission numbers included in the repeat transmission number candidate set; The PUSCH is transmitted repeatedly by one of the values.

17. 17. The terminal of claim 16, wherein the information indicating any one of the values ​​is included in at least one of a Time Domain Resource Allocation (TDRA) field, a Modulation and Coding Scheme (MCS) field, and a Transmit Power Control (TPC) field of the random access response.

18. If information indicating any one of the values ​​is included in the MCS field, The terminal of claim 17, wherein the one of the values ​​is indicated by one or more MSBs of the MCS field.

19. If information indicating any one of the values ​​is included in the TPC field, The terminal of claim 17, wherein the any one value is indicated by one or more least significant bits of the TPC field.

20. 1. A method for receiving an uplink channel in a wireless communication system, the method being performed by a base station, comprising: transmitting a system information block 1 (SIB1) to a terminal; receiving a preamble for a random access procedure from the terminal; transmitting a random access response (RAR) to the terminal in response to the preamble; The random access response includes information for scheduling a physical uplink shared channel (PUSCH) that the terminal transmits to the base station; receiving the PUSCH based on the random access response from the terminal; The SIB1 includes information about a repeat transmission count candidate set including values ​​for one or more repeat transmission counts for performing repeat transmission of the PUSCH, the random access response includes information indicating one of values ​​for the one or more repeat transmission numbers included in the repeat transmission number candidate set; The PUSCH is transmitted repeatedly by one of the values.

Images