Method and apparatus for performing uplink transmission and reception in a wireless communication system - Patents.com

Abstract

A method and an apparatus for performing uplink transmission and reception in a wireless communication system are disclosed. In a wireless communication system according to an embodiment of the present disclosure, a method for performing uplink transmission by a terminal includes receiving configuration information related to repeated PRACH preamble transmission from a base station, and performing repeated PRACH preamble transmission in at least one RO among a plurality of ROs based on the configuration information, and when a specific RO among the plurality of ROs collides with a specific signal or a specific channel, the specific RO may be dropped, and an RA-RNTI may be calculated based on one or more reference ROs determined in the remaining ROs other than the specific RO among the plurality of ROs.

Description

[Technical field]

[0001] The present disclosure relates to wireless communication systems, and more particularly to methods and apparatus for performing uplink transmission and reception in wireless communication systems. [Background technology]

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, the scope of mobile communication systems has expanded beyond voice to data services, and currently, resource shortages are occurring due to the explosive increase in traffic, and users are demanding faster services, so there is a demand for more advanced mobile communication systems.

[0003] The requirements for the next generation mobile communication system are to accommodate large and explosive data traffic, dramatically increase the transmission rate per user, accommodate a significantly increased number of connected devices, support very low end-to-end latency, and high energy efficiency.To achieve this, various technologies such as dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking are being researched. Summary of the Invention [Problem to be solved by the invention]

[0004] A technical problem of the present disclosure is to provide a method and apparatus for performing uplink transmission and reception in a wireless communication system.

[0005] In addition, another technical problem of the present disclosure is to provide a method and apparatus for calculating RA-RNTI / MSGB-RNTI based on a reference RO when performing PRACH / MSGA preamble repeated transmission.

[0006] Furthermore, a further technical problem of the present disclosure is to provide a method and apparatus for handling collisions between RO and other signals / channels for PRACH / MSGA preamble repeated transmission.

[0007] The technical problems to be achieved by the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the following description. [Means for solving the problem]

[0008] As one embodiment of the present disclosure, a method for a terminal performing uplink transmission in a wireless communication system includes a step of receiving configuration information related to repeated transmission of a physical random access channel (PRACH) preamble from a base station, and a step of performing repeated transmission of the PRACH preamble in at least one of a plurality of random access occasions (ROs) based on the configuration information, wherein a specific RO among the plurality of ROs may be dropped based on collision of the specific RO with a specific signal or a specific channel, and a random access (RA)-RNTI (radio network temporary identifier) ​​may be calculated based on one or more reference ROs determined for remaining ROs among the plurality of ROs excluding the specific RO.

[0009] As yet another embodiment of the present disclosure, a method for a base station performing uplink reception in a wireless communication system includes a step of transmitting configuration information related to repeated transmission of a physical random access channel (PRACH) preamble to a terminal, and performing repeated reception of the PRACH preamble in at least one of a plurality of random access occasions (ROs) based on the configuration information, wherein the specific RO among the plurality of ROs may be dropped based on collision of the specific RO with a specific signal or a specific channel, and a random access (RA)-RNTI (radio network temporary identifier) ​​may be calculated by the terminal based on one or more reference ROs determined for remaining ROs among the plurality of ROs excluding the specific RO. Effect of the Invention

[0010] Various embodiments of the present disclosure may provide a method and apparatus for performing uplink transmission and reception in a wireless communication system.

[0011] In addition, various embodiments of the present disclosure may provide a method and apparatus for calculating RA-RNTI / MSGB-RNTI based on a reference RO when performing PRACH / MSGA preamble repeated transmission.

[0012] Various embodiments of the present disclosure may also provide methods and apparatus for handling collisions between RO and other signals / channels for PRACH / MSGA preamble repeat transmissions.

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

[0014] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present disclosure, provide examples of the present disclosure and, together with the detailed description, explain the technical features of the present disclosure.

[0015] [Figure 1] 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied. [Diagram 2] 1 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied. [Diagram 3] 1 illustrates an example of a resource grid in a wireless communication system to which the present disclosure can be applied. [Figure 4] 1 illustrates an example of a physical resource block in a wireless communication system to which the present disclosure can be applied. [Diagram 5] 1 illustrates an example of a slot structure in a wireless communication system to which the present disclosure can be applied. [Figure 6] 1 illustrates examples of physical channels used in a wireless communication system to which the present disclosure can be applied, and a general signal transmission / reception method using the physical channels. [Figure 7] 1 illustrates an example wireless communication system that supports unlicensed spectrum to which the present disclosure can be applied. [Figure 8] 1 is a diagram illustrating an uplink transmission and reception operation in a wireless communication system to which the present disclosure can be applied. [Figure 9] 1 is a diagram for explaining an uplink transmission operation of a terminal in a wireless communication system to which the present disclosure can be applied. [Figure 10] 1 is a diagram for explaining an uplink receiving operation of a base station in a wireless communication system to which the present disclosure can be applied. [Figure 11] FIG. 13 is a diagram for explaining a method for determining a reference RO according to one embodiment of the present disclosure. [Figure 12] A diagram for explaining a signaling procedure between the network side and the terminal according to one embodiment of the present disclosure. [Figure 13] 1 is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed below together with the accompanying drawings is intended to describe exemplary embodiments of the present disclosure, and is not intended to show the only embodiment in which the present disclosure can be implemented. The detailed description below includes specific details to provide a complete understanding of the present disclosure. However, it is understood by those skilled in the art that the present disclosure can be implemented without such specific details.

[0017] In some cases, in order to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or may be shown in the form of a block diagram focusing on the core functions of each structure and device.

[0018] In this disclosure, when an element is "coupled," "coupled," or "connected" to another element, this may include a direct connection as well as an indirect connection where there is still another element between them. Also, in this disclosure, the terms "including" or "having" specify the presence of stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0019] In this disclosure, terms such as "first" and "second" are used only to distinguish one component from another component, and are not used to limit the components, and do not limit the order or importance of the components unless otherwise specified. Therefore, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0020] The terms used in this disclosure are for the purpose of describing particular embodiments and are not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular form is intended to include the plural form unless the context dictates otherwise. The term "and / or" used in this disclosure means that one of the associated listed items may be included, or any and all possible combinations of two or more of them. Also, in this disclosure, " / " between words has the same meaning as "and / or" unless otherwise specified.

[0021] The present disclosure is described with respect to a wireless communication network or wireless communication system, and operations performed in the wireless communication network may be performed in a process in which a device (e.g., a base station) that manages the wireless communication network controls the network and transmits or receives signals, or in a process in which a terminal coupled to the wireless network transmits or receives signals to or between the network.

[0022] In this disclosure, transmitting or receiving a channel includes transmitting or receiving information or signals on that channel. For example, transmitting a control channel means transmitting control information or signals on the control channel. Similarly, transmitting a data channel means transmitting data information or signals on the data channel.

[0023] In the following, downlink (DL) means communication from a base station to a terminal, and uplink (UL) means communication from a terminal to a base station. In the downlink, a transmitter may be a part of the base station, and a receiver may be a part of the terminal. In the uplink, a transmitter may be a part of the terminal, and a receiver may be a part of the base station. The base station may be expressed as a first communication device, and the terminal may be expressed as a second communication device. A base station (BS) may be replaced with terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP), network (5G network), AI (Artificial Intelligence) system / module, RSU (road side unit), robot, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, a terminal may be fixed or mobile, and may be replaced with terms such as User Equipment (UE), Mobile Station (MS), user terminal (UT), Mobile Subscriber Station (MSS), Subscriber Station (SS), Advanced Mobile Station (AMS), Wireless terminal (WT), Machine-Type Communication (MTC) device, Machine-to-Machine (M2M) device, Device-to-Device (D2D) device, vehicle, road side unit (RSU), robot, Artificial Intelligence (AI) module, drone (UAV: Unmanned Aerial Vehicle), Augmented Reality (AR) device, Virtual Reality (VR) device, etc.

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

[0025] For clarity of explanation, the following description will be based on a 3GPP communication system (e.g., LTE-A, NR), but the technical idea of ​​the present disclosure is not limited thereto. LTE refers to technology after 3GPP TS (Technical Specification) 36.xxx Release 8. In detail, LTE technology after 3GPP TS 36.xxx Release 10 is called LTE-A, and LTE technology after 3GPP TS 36.xxx Release 13 is called LTE-A pro. 3GPP NR refers to technology after TS 38.xxx Release 15. LTE / NR may be called a 3GPP system. "xxx" refers to a standard document detail number. LTE / NR may be called a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present disclosure, reference may be made to matters described in standard documents published before the present disclosure. For example, the following documents may be referenced.

[0026] In 3GPP LTE, reference can be made to TS 36.211 (physical channels and modulation), TS 36.212 (multiplexing and channel coding), TS 36.213 (physical layer procedures), TS 36.300 (general description), and TS 36.331 (radio resource control).

[0027] For 3GPP NR, reference can be made to TS 38.211 (Physical channels and modulation), TS 38.212 (Multiplexing and channel coding), TS 38.213 (Physical layer procedures for control), TS 38.214 (Physical layer procedures for data), TS 38.300 (General description of NR and NG-RAN (New Generation-Radio Access Network)), and TS 38.331 (Radio resource control protocol standard).

[0028] The following terminology abbreviations may be used in this disclosure:

[0029] - BM: Beam management

[0030] - CQI: channel quality indicator

[0031] - CRI: channel state information- reference signal resource indicator

[0032] - CSI: channel state information

[0033] - CSI-IM: channel state information-interference measurement

[0034] - CSI-RS: Channel state information-reference signal

[0035] - DMRS: Demodulation Reference Signal

[0036] - FDM: Frequency division multiplexing

[0037] - FFT: Fast Fourier transform

[0038] - IFDMA: Interleaved frequency division multiple access

[0039] - IFFT: inverse fast Fourier transform

[0040] - L1-RSRP: Layer 1 reference signal received power

[0041] - L1-RSRQ: Layer 1 reference signal received quality

[0042] - MAC: medium access control

[0043] - NZP: non-zero power

[0044] - OFDM: Orthogonal frequency division multiplexing

[0045] - PDCCH: physical downlink control channel

[0046] - PDSCH: physical downlink shared channel

[0047] - PMI: Precoding matrix indicator

[0048] - RE: resource element

[0049] - RI: Rank indicator

[0050] - RRC: Radio resource control

[0051] - RSSI: received signal strength indicator

[0052] - Rx: Reception

[0053] - QCL: quasi co-location

[0054] - SINR: signal to interference and noise ratio

[0055] - SSB (or SS / PBCH block): Synchronization signal block (including primary synchronization signal (PSS), secondary synchronization signal (SSS) and physical broadcast channel (PBCH))

[0056] - TDM: time division multiplexing

[0057] - TRP: transmission and reception point

[0058] - TRS: Tracking reference signal

[0059] - Tx: transmission

[0060] - UE: User Equipment

[0061] - ZP: Zero power

[0062] System in general

[0063] As more communication devices require larger communication capacity, the need for improved mobile broadband communication compared to existing radio access technologies (RATs) is emerging. Massive Machine Type Communications (MTC), which connects a large number of devices and objects to provide various services anytime and anywhere, is also one of the major issues to be considered in next-generation communication. In addition, communication system design considering reliability and latency-sensitive services / terminals is also being discussed. Thus, the introduction of next-generation RATs considering eMBB (enhanced mobile broadband communication), Mmtc (massive MTC), URLLC (Ultra-Reliable and Low Latency Communication), etc. is being discussed, and for convenience in this disclosure, the technology is referred to as NR. NR is an expression representing an example of 5G RAT.

[0064] New RAT systems including NR use an OFDM transmission scheme or a similar transmission scheme. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system may follow the existing LTE / LTE-A numerology but support a larger system bandwidth (e.g., 100 MHz). Alternatively, one cell may support multiple numerologies. That is, terminals operating with different numerologies may coexist in one cell.

[0065] A numerology corresponds to a subcarrier spacing in the frequency domain. Different numerologies can be defined by scaling the reference subcarrier spacing by an integer N.

[0066] FIG. 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.

[0067] Referring to FIG. 1, the NG-RAN is composed of gNBs that provide an NG-Radio Access (NG-RA) user plane (i.e., new access stratum (AS) sublayer / Packet Data Convergence Protocol (PDCP) / Radio Link Control (RLC) / MAC / PHY) and control plane (RRC) protocol termination for UEs. The gNBs are interconnected via an Xn interface. The gNBs are also connected to a New Generation Core (NGC) via an NG interface. More specifically, the gNBs are connected to an Access and Mobility Management Function (AMF) via an N2 interface and to a User Plane Function (UPF) via an N3 interface.

[0068] FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.

[0069] The NR system can support multiple numerologies, where the numerology may be defined by subcarrier spacing and cyclic prefix (CP) overhead. In this case, the multiple subcarrier spacing may be derived by scaling the base (reference) subcarrier spacing by an integer N (or μ). In addition, the numerology used may be selected independently of the frequency band, even if it is assumed that very low subcarrier spacing is not used at very high carrier frequencies. In addition, various frame structures with multiple numerologies may be supported in the NR system.

[0070] The following describes OFDM numerologies and frame structures that can be considered in the NR system. Multiple OFDM numerologies supported in the NR system may be defined as shown in Table 1 below.

[0071] [Table 1]

[0072] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in a traditional cellular band, when the SCS is 30 kHz / 60 kHz, it supports dense urban areas, lower latency, and wider carrier bandwidth, and when the SCS is 60 kHz or higher, it supports a bandwidth larger than 24.25 GHz to overcome phase noise. The NR frequency band is defined as two types of frequency ranges (FR1, FR2). FR1 and FR2 may be configured as shown in Table 2 below. Also, FR2 can mean millimeter wave (mmW).

[0073] [Table 2]

[0074] In relation to the frame structure in the NR system, the sizes of the various fields in the time domain are T c =1 / (Δf max N f ) where Δf max =480 10 3 Hz and N f= 4096. Downlink and uplink transmissions are f =1 / (Δf max N f / 100)·T c The radio frame is organized into radio frames each having a duration of T sf =(Δf max N f / 1000)·T c In this case, there may be one set of frames for the uplink and one set of frames for the downlink. Also, the transmission from the terminal in the uplink frame number i starts T TA =(N TA +N TA,offset )T c For a subcarrier spacing configuration μ, a slot is allocated within a subframe. s μ ∈{0,...,N slot subframe,μ -1}, and n s,f μ ∈{0,...,N slot frame,μ The slots are numbered in increasing order {N -1}. symb slot It consists of N consecutive OFDM symbols. symb slot is determined by the CP. s μ The start of OFDM symbol n s μ N symb slotNot all terminals can transmit and receive at the same time, which means that not all OFDM symbols in a downlink slot or uplink slot can be used.

[0075] Table 3 shows the number of OFDM symbols per slot (N symb slot ), the number of slots per radio frame (N slot frame,μ ), the number of slots per subframe (N slot subframe,μ ), and Table 4 shows the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in the extended CP.

[0076] [Table 3]

[0077] [Table 4]

[0078] FIG. 2 is an example when μ=2 (SCS is 60 kHz), and referring to Table 3, one subframe may include four slots. One subframe={1, 2, 4} slots shown in FIG. 2 is an example, and the number of slots that may be included in one subframe is defined as shown in Table 3 or Table 4. Also, a mini-slot may include 2, 4, or 7 symbols, or may include more or less symbols. In relation to physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, and the like may be considered.

[0079] The physical resources that can be considered in the NR system will be specifically described below. First, in relation to antenna ports, the antenna ports are defined such that the channel on which a symbol on an antenna port is carried can be inferred from the channel on which another symbol on the same antenna port is carried. If the large-scale property of the channel on which a symbol on one antenna port is carried can be inferred from the channel on which a symbol on the other antenna port is carried, the two antenna ports are said to be in a QC / QCL (quasi co-located or quasi co-location) relationship.

[0080] Here, the wide range characteristics include at least one of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0081] FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied.

[0082] Referring to FIG. 3, the resource grid is divided into N RB μ N sc RB Each subframe consists of 14.2 subcarriers. μ In the present embodiment, the OFDM symbol is used as an example, but is not limited to, an OFDM symbol. RB μ N sc RB One or more resource grids consisting of subcarriers and two μ N symb (μ) OFDM symbols, where N RBμ ≦N RB max,μ The above N RB max,μ represents the maximum transmission bandwidth, which may vary between uplink and downlink as well as numerology. In this case, one resource grid may be set for each μ and antenna port p. Each element of the resource grid for μ and antenna port p is called a resource element, and is represented by an index pair. JPEG2025512855000006.jpg618, where k=0,...,N RB μ N sc RB -1 is the index in the frequency domain, JPEG2025512855000007.jpg782 represents the position of a symbol within a subframe. When referring to a resource element in a slot, the index pair (k,l) is used, where l=0,...,N symb μ μ and the resource element for antenna port p. JPEG2025512855000008.jpg618 is a complex value JPEG2025512855000009.jpg811. If there is no risk of confusion or if a specific antenna port or numerology is not specified, the indexes p and μ may be dropped, so that the complex value is JPEG2025512855000010.jpg912 or JPEG2025512855000011.jpg912. Also, a resource block (RB) is N sc RB = 12 consecutive subcarriers.

[0083] Point A serves as a common reference point for the resource block grid and is obtained as follows:

[0084] - offsetToPointA for the primary cell (PCell) downlink indicates the frequency offset between point A and the lowest subcarrier of the lowest resource block that overlaps with the SS / PBCH block used by the terminal for initial cell selection. It is expressed in resource block units assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2.

[0085] - absoluteFrequencyPointA denotes the frequency-location of point A expressed as in ARFCN (absolute radio-frequency channel number). Common resource blocks are numbered from 0 upwards in the frequency domain for subcarrier spacing setting μ. The center of subcarrier 0 of common resource block 0 for subcarrier spacing setting μ coincides with 'point A'. Common resource block number n in the frequency domain CRB μ The relationship between k, l and the resource element (k, l) for the subcarrier spacing setting μ is given by the following Equation 1.

[0086] [Formula 1]

number

[0087] In Equation 1, k is defined relative to point A such that k=0 corresponds to the subcarrier centered on point A. The physical resource block is a number ranging from 0 to N BWP,i size,μ The numbering is from -1 to i, where i is the number of the BWP.PRB and common resource block n CRB The relationship between is given by Equation 2 below.

[0088] [Formula 2]

number

[0089] N BWP,i start,μ is the common resource block where the BWP starts relative to common resource block 0.

[0090] Fig. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied, and Fig. 5 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied.

[0091] 4 and 5, a slot includes a number of symbols in the time domain. For example, in the general CP, one slot includes seven symbols, while in the extended CP, one slot includes six symbols.

[0092] A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) is defined as multiple consecutive (physical) resource blocks in the frequency domain and may correspond to one numerology (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication is performed in the activated BWPs, and only one BWP may be activated for one terminal. Each element in the resource grid is called a resource element (RE), and one complex symbol may be mapped to it.

[0093] The NR system may support up to 400 MHz per component carrier (CC). If a terminal operating in such a wideband CC always operates with the radio frequency (RF) chip for the entire CC turned on, the terminal battery consumption may increase. Alternatively, considering various use cases (e.g., eMBB, URLLC, Mmtc, V2X, etc.) operating in one wideband CC, different numerologies (e.g., subcarrier spacing, etc.) may be supported for each frequency band in the CC. Alternatively, the capability for maximum bandwidth may differ for each terminal. In consideration of this, the base station may instruct the terminal to operate only in a part of the bandwidth rather than the entire bandwidth of the wideband CC, and the part of the bandwidth is defined as a bandwidth part (BWP) for convenience. The BWP may be composed of continuous RBs on the frequency axis and may correspond to one numerology (e.g., subcarrier spacing, CP length, slot / minislot interval).

[0094] Meanwhile, the base station can set multiple BWPs even within one CC set in the terminal. For example, a BWP occupying a relatively small frequency region can be set in the PDCCH monitoring slot, and the PDSCH indicated by the PDCCH can be scheduled on a larger BWP. Alternatively, when UEs are concentrated in a specific BWP, other BWPs can be set in some terminals for load balancing. Alternatively, in consideration of frequency domain inter-cell interference cancellation between adjacent cells, some spectrums of the entire bandwidth can be excluded and both BWPs can be set in the same slot. That is, the base station can set at least one DL / UL BWP in the terminal associated with the wideband CC. The base station can activate at least one DL / UL BWP among the DL / UL BWPs set at a specific time (by L1 signaling, MAC CE (Control Element), RRC signaling, etc.). The base station may also instruct (eg, by L1 signaling, MAC CE, or RRC signaling) switching to another configured DL / UL BWP.

[0095] Alternatively, when the timer value expires on a timer basis, the UE may switch to a predetermined DL / UL BWP. In this case, the activated DL / UL BWP is defined as an active DL / UL BWP. However, in a situation where the UE is performing an initial access process or before an RRC connection is set up, the UE may not be able to receive the configuration for the DL / UL BWP, and therefore the DL / UL BWP assumed by the UE in such a situation is defined as the initially active DL / UL BWP.

[0096] FIG. 6 illustrates examples of physical channels used in a wireless communication system to which the present disclosure can be applied, and a general signal transmission / reception method using the physical channels.

[0097] In a wireless communication system, a terminal receives information from a base station through a downlink, and transmits information to the base station through an uplink. Information transmitted and received between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type / purpose of the information they transmit and receive.

[0098] When the terminal is powered on or newly enters a cell, the terminal performs an initial cell search such as synchronizing with the base station (S601). To this end, the terminal receives a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station to synchronize with the base station and obtain information such as a cell identifier (ID). After that, the terminal receives a physical broadcast channel (PBCH) from the base station to obtain broadcast information within the cell. Meanwhile, the terminal can receive a downlink reference signal (DL RS) during the initial cell search stage to check the downlink channel state.

[0099] After completing the initial cell search, the terminal can receive a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH) based on the information carried on the PDCCH, thereby obtaining more specific system information (S602).

[0100] Meanwhile, when the terminal first connects to the base station or has no radio resources for signal transmission, the terminal can perform a random access procedure (RACH) to the base station (steps S603 to S606). To this end, the terminal can transmit a specific sequence as a preamble on a physical random access channel (PRACH) (S603 and S605) and receive a response message to the preamble on a PDCCH and a corresponding PDSCH (S604 and S606). In the case of a contention-based RACH, the terminal can also perform a contention resolution procedure.

[0101] After performing the above-mentioned procedures, the terminal can then perform PDCCH / PDSCH reception (S607) and Physical Uplink Shared Channel (PUSCH) / Physical Uplink Control Channel (PUCCH) transmission (S608) as a general uplink / downlink signal transmission procedure. In particular, the terminal receives Downlink Control Information (DCI) through the PDCCH. Here, the DCI includes control information such as resource allocation information for the terminal, and has different formats depending on its purpose.

[0102] Meanwhile, control information that a terminal transmits to a base station in an uplink or that the terminal receives from a base station includes downlink / uplink ACK / NACK (Acknowledgement / Non-Acknowledgement) signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. In a 3GPP LTE system, a terminal can transmit the above-mentioned control information such as CQI / PMI / RI in a PUSCH and / or a PUCCH.

[0103] Table 5 shows an example of a DCI format in an NR system.

[0104] [Table 5]

[0105] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information related to PUSCH scheduling (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), transport block (TB) related information (e.g., MCS (Modulation Coding and Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), HARQ (Hybrid- Automatic Repeat and request) related information (e.g., process number, DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), multiple antenna related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), and power control information (e.g., PUSCH power control, etc.), and the control information included in each of the DCI formats may be predefined.

[0106] DCI format 0_0 is used for scheduling PUSCH in one cell. Information included in DCI format 0_0 is CRC (cyclic redundancy check) scrambled by C-RNTI (Cell RNTI: Cell Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) and transmitted.

[0107] DCI format 0_1 ​​is used to indicate to a terminal the scheduling of one or more PUSCHs in one cell or downlink feedback information of a configured grant (CG). Information included in DCI format 0_1 ​​is CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI (Semi-Persistent CSI RNTI), or MCS-C-RNTI and transmitted.

[0108] DCI format 0_2 is used for PUSCH scheduling in one cell. Information included in DCI format 0_2 is CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI and transmitted.

[0109] Next, DCI formats 1_0, 1_1, and 1_2 may include resource information related to PDSCH scheduling (e.g., frequency resource allocation, time resource allocation, VRB (virtual resource block)-PRB (physical resource block) mapping, etc.), transmission block (TB) related information (e.g., MCS, NDI, RV, etc.), HARQ related information (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), multiple antenna related information (e.g., antenna port, TCI (transmission configuration indicator), SRS (sounding reference signal) request, etc.), PUCCH related information (e.g., PUCCH power control, PUCCH resource indicator, etc.), and the control information included in each of the DCI formats may be pre-defined.

[0110] DCI format 1_0 is used for scheduling the PDSCH in one DL cell. Information included in DCI format 1_0 is CRC scrambled by the C-RNTI, CS-RNTI, or MCS-C-RNTI and transmitted.

[0111] DCI format 1_1 is used for scheduling the PDSCH in one cell. Information included in DCI format 1_1 is CRC scrambled by the C-RNTI, CS-RNTI, or MCS-C-RNTI and transmitted.

[0112] DCI format 1_2 is used for scheduling the PDSCH in one cell. Information included in DCI format 1_2 is CRC scrambled by the C-RNTI, CS-RNTI, or MCS-C-RNTI and transmitted.

[0113] Wireless communication system supporting unlicensed band / shared spectrum

[0114] 7 illustrates a wireless communication system that supports an unlicensed spectrum to which the present disclosure can be applied. For example, FIG. 7 illustrates an unlicensed spectrum (NR-U) wireless communication system.

[0115] In the following description, a cell operating in a licensed band (L-band) is defined as an LCell, and the carrier of the LCell is defined as an LCC (downlink / uplink). A cell operating in an unlicensed band (U-band) is defined as a UCell, and the carrier of the UCell is defined as an UCC (downlink / uplink). The carrier / carrier frequency of a cell may refer to the operating frequency (e.g., center frequency) of the cell. Cells / carriers (e.g., component carriers (CCs) are collectively referred to as cells).

[0116] As shown in (a) of FIG. 7, when a terminal and a base station transmit and receive signals using a carrier aggregated (CA) LCC and UCC, the LCC may be configured as a PCC (primary CC) and the UCC may be configured as a SCC (secondary CC). As shown in (b) of FIG. 7, the terminal and the base station may transmit and receive signals using one UCC or multiple carrier aggregated UCCs. That is, the terminal and the base station may transmit and receive signals using only UCCs without an LCC. For standalone operation, PRACH, PUCCH, PUSCH, SRS transmission, etc. may be supported in the UCell.

[0117] For example, the unlicensed band may be included in a specific frequency range (e.g., from above 52.6 GHz to 71 GHz) that is higher than the existing frequency ranges (e.g., FR1 and FR2). The specific frequency range may be referred to as FR2-2 (in this case, the existing FR2 (i.e., 24250 MHz to 52600 MHz) may be referred to as FR2-1) or FR3. The scope of the present disclosure is not limited to the names FR2-2 or FR3.

[0118] Uplink transmission and reception operations

[0119] FIG. 8 is a diagram illustrating an uplink transmission / reception operation in a wireless communication system to which the present disclosure can be applied.

[0120] 8, the base station schedules uplink transmission such as frequency / time resources, transmission layer, uplink precoder, MCS, etc. (S1501). In particular, the base station can determine a beam for a UE to transmit a PUSCH through the above-mentioned operation.

[0121] The terminal receives DCI for uplink scheduling (ie, DCI including scheduling information of the PUSCH) from the base station on the PDCCH (S1502).

[0122] For uplink scheduling, DCI format 0_0, 0_1, or 0_2 may be used. In particular, DCI format 0_1 ​​includes the following information: DCI format identifier, UL / SUL (Supplementary uplink) indicator, Bandwidth part indicator, Frequency domain resource assignment, Time domain resource assignment, Frequency hopping flag, Modulation and coding scheme (MCS), SRS resource indicator (SRI), Precoding information and number of layers, Antenna port, SRS request, DMRS sequence initialization, and UL-SCH (Uplink Shared Channel) indicator.

[0123] In particular, the SRS resource indicator field may indicate an SRS resource set in an SRS resource set associated with the upper layer parameter 'usage'. In addition, 'spatialRelationInfo' may be set for each SRS resource, and its value may be one of {CRI, SSB, SRI}.

[0124] The terminal transmits uplink data to the base station on the PUSCH (S1503).

[0125] If the terminal detects a PDCCH including DCI format 0_0, 0_1, or 0_2, it transmits the corresponding PUSCH according to the instruction of the DCI.

[0126] Two transmission schemes are supported for PUSCH transmission: codebook-based transmission and non-codebook-based transmission:

[0127] i) When the higher layer parameter "txConfig" is set to "codebook", the terminal is configured for codebook-based transmission. On the other hand, when the higher layer parameter "txConfig" is set to "nonCodebook", the terminal is configured for non-codebook-based transmission. If the higher layer parameter "txConfig" is not set, the terminal does not expect to be scheduled by DCI format 0_1. When PUSCH is scheduled by DCI format 0_0, PUSCH transmission is performed on a single-antenna port basis.

[0128] In the case of codebook-based transmission, the PUSCH may be scheduled in DCI format 0_0, DCI format 0_1, DCI format 0_2, or semi-statically. If the PUSCH is scheduled by DCI format 0_1, the terminal determines a PUSCH transmission precoder based on the SRI, TPMI (Transmit Precoding Matrix Indicator), and transmission rank from the DCI as given by the SRS resource indicator field and the Precoding information and number of layers field. The TPMI is used to indicate the precoder applied across antenna ports, and corresponds to the SRS resource selected by the SRI when multiple SRS resources are configured.

[0129] Alternatively, when a single SRS resource is configured, the TPMI is used to indicate the precoder to be applied across antenna ports corresponding to the single SRS resource. A transmit precoder is selected from an uplink codebook with the same number of antenna ports as the higher layer parameter "nrofSRS-Ports". When the terminal is configured with the higher layer parameter "txConfig" set to "codebook", the terminal is configured with at least one SRS resource. The SRI indicated in slot n is associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS resource precedes the PDCCH (i.e., slot n) carrying the SRI.

[0130] ii) In the case of non-codebook-based transmission, the PUSCH may be scheduled in DCI format 0_0, DCI format 0_1, or semi-statically. When multiple SRS resources are configured, the terminal may determine the PUSCH precoder and transmission rank based on the wideband SRI, where the SRI is given by the SRS resource indicator in the DCI or by the higher layer parameter "srs-ResourceIndicator".

[0131] The terminal uses one or multiple SRS resources for SRS transmission, where the number of SRS resources may be configured for simultaneous transmission in the same RB based on the UE capability. Only one SRS resource is configured for each SRS resource. Only one SRS resource may be configured with the higher layer parameter "usage" set to "nonCodebook". The maximum number of SRS resources that may be configured for non-codebook based uplink transmission is four. The SRI indicated in slot n is associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS transmission precedes the PDCCH (i.e., slot n) carrying the SRI.

[0132] PRACH repetition transmission method

[0133] In order to improve the UL coverage of a basic wireless communication system, a PRACH preamble repeat transmission operation may be performed. In the following, a method for calculating RA-RNTI / MSGB-RNTI based on a reference RO according to an embodiment of the present disclosure and an operation of a terminal / base station when an RO selected for PRACH repeat transmission collides with another signal / channel will be described.

[0134] Here, in the four-step RACH procedure, Msg.1 (message 1) may include a preamble (i.e., a PRACH preamble), Msg.2 may include a random access response (RAR) corresponding to Msg.1, and Msg.3 may include a PUSCH based on uplink resource allocation information provided by the RAR.

[0135] The present disclosure may be applied in combination with the above-mentioned contents (e.g., NR frame structure, RACH procedure, U-band system, etc.). In addition, a method related to a PRACH transmission opportunity configuration described later may be equally applied to an uplink signal transmission and reception method.

[0136] As an example, uplink transmission using a method related to the PRACH transmission opportunity configuration described below may be performed in an L-cell and / or a U-cell defined in an NR system or a U-Band system.

[0137] In a basic wireless communication system, repeated transmission of the PRACH preamble may be performed for UL coverage enhancement.

[0138] The RA-RNTI associated with the PRACH occasion in which the random access preamble is transmitted may be calculated according to Equation 3.

[0139] [Formula 3] RA-RNTI = 1 + s_id + 14 * t_id + 14 * 80 * f_id + 14 * 80 * 8 * ul_carrier_id

[0140] where s_id (e.g., 0≦s_id<14) is the index of the first OFDM symbol of the PRACH opportunity; t_id (e.g., 0≦t_id<80) is the index of the first slot of the PRACH opportunity in the system frame; the SCS for determining t_id may be based on the μ (i.e., the SCS associated with the PRACH transmission) value; f_id (e.g., 0≦f_id<8) is the index of the PRACH opportunity in the frequency domain; ul_carrier_id may be the UL carrier used for random access preamble transmission. For example, for a NUL carrier, ul_carrier_id may be 0, and for a SUL carrier, ul_carrier_id may be 1.

[0141] The MSGB-RNTI associated with the PRACH occasion in which the random access preamble is transmitted may be calculated according to Equation 4.

[0142] [Formula 4] MSGB-RNTI = 1 + s_id + 14 * t_id + 14 * 80 * f_id + 14 * 80 * 8 * ul_carrier_id + 14 * 80 * 8 * 2

[0143] where s_id (e.g., 0≦s_id<14) is the index of the first OFDM symbol of the PRACH opportunity; t_id (e.g., 0≦t_id<80) is the index of the first slot of the PRACH opportunity in the system frame; the SCS for determining t_id may be based on the μ value (i.e., the SCS associated with the PRACH transmission); f_id (e.g., 0≦f_id<8) is the index of the PRACH opportunity in the frequency domain; ul_carrier_id may be the UL carrier used for random access preamble transmission. For example, for a NUL carrier, ul_carrier_id may be 0, and for a SUL carrier, ul_carrier_id may be 1.

[0144] Here, when performing repeated PRACH preamble transmission according to the existing scheme, the UE cannot arbitrarily determine the RO (i.e., the RO for determining s_id, f_id, and t_id) used in Equation 3 and / or Equation 4. Therefore, there may be a problem that the UE cannot accurately calculate the RA-RNTI and / or MSGB-RNTI values.

[0145] In the following, in order to solve the above-mentioned problems, a method for setting the RA-RNTI when the PRACH (or / and Msg. A) preamble repeated transmission operation is defined will be described.

[0146] FIG. 9 is a diagram for explaining an uplink transmission operation of a terminal in a wireless communication system to which the present disclosure can be applied.

[0147] The terminal may receive configuration information related to repeated PRACH preamble transmission from the base station (S910).

[0148] Here, the terminal may transmit to the base station first terminal capability information indicating that it supports repeated PRACH preamble transmission and / or second terminal capability information indicating that it supports repeated physical uplink shared channel (PUSCH) transmission based on the RAR (i.e., the RAR for the PRACH preamble transmission).

[0149] As an example, the configuration information related to the PRACH preamble repeat transmission may include the number of PRACH preamble repeat transmissions, information related to time / frequency resources for PRACH preamble transmission, information related to a PRACH preamble index, and the like.

[0150] The operation according to S910 may also be applied to repeated transmission of the MSGA preamble, i.e., the PRACH preamble in the operation according to S910 and related configuration information may be replaced with the MSGA preamble.

[0151] The terminal may perform PRACH preamble repetitive transmission in at least one of the multiple ROs based on the configuration information (S920).

[0152] Here, the terminal may drop a specific RO based on collision of the specific RO with a specific signal or a specific channel among the multiple ROs. The terminal may calculate RA-RNTI based on one or more reference ROs determined in the remaining ROs excluding the specific RO among the multiple ROs. Then, the terminal may transmit a PRACH preamble in the remaining ROs excluding the specific RO among the multiple ROs.

[0153] Here, the specific signal or specific channel may refer to a signal or channel scheduled / activated / configured by the base station, i.e., if a resource corresponding to a signal or channel scheduled / activated / configured by the base station overlaps / collides with a resource corresponding to a specific RO, the terminal may drop the specific RO.

[0154] As an example, the terminal may calculate one or more RA-RNTIs based on the index of the first symbol of one or more reference ROs, the index of the first slot of one or more reference ROs in a system frame, the index of one or more reference ROs in the frequency domain, and the index of an uplink carrier used for PRACH preamble repetition transmission.

[0155] Here, the number of reference ROs may be one, but is not limited to this and may be two or more.

[0156] As an example, the reference RO may be a single RO selected from the remaining ROs excluding a specific RO among the multiple ROs, and may be the first RO or the last RO among the remaining ROs.

[0157] The terminal may receive an RAR including a system frame number (SFN) value corresponding to the single reference RO from the base station. The terminal may determine whether the RAR is an RAR for the terminal by using the RA-RNTI calculated based on the single reference RO and the SFN corresponding to the single reference RO.

[0158] That is, the terminal can determine whether the RAR is an RAR transmitted for the terminal by comparing the RA-RNTI calculated based on the single-reference RO and the SFN corresponding to the single-reference RO with corresponding information included in the RAR.

[0159] As an example of the present disclosure, based on the determination of multiple reference ROs for the remaining ROs excluding a specific RO among the multiple reference ROs, the terminal can calculate the RA-RNTI based on the reference RO from which the last PRACH preamble was transmitted among the multiple reference ROs.

[0160] Additionally or alternatively, the terminal may receive information regarding one or more reference ROs from the base station through higher layer signaling (e.g., SIB, RRC signaling, etc.), where the higher layer signaling may include configuration information related to PRACH preamble repeated transmission.

[0161] However, this is merely an example, and information regarding one or more reference ROs and configuration information related to repeated PRACH preamble transmission may be transmitted independently from the base station to the terminal.

[0162] Additionally or alternatively, the one or more reference ROs may be determined to be a predefined default RO based on no higher layer signaling including information regarding the one or more reference ROs being received from the base station.

[0163] Additionally or alternatively, the terminal may receive configuration information related to a preamble index hopping operation related to the PRACH preamble repeated transmission from the base station. The terminal may perform preamble index hopping and PRACH preamble repeated transmission based on the configuration information related to the preamble index hopping operation and / or the configuration information related to the PRACH preamble repeated transmission.

[0164] Here, the configuration information related to the preamble index hopping operation may include at least one of information regarding a preamble index pool for PRACH preamble repetitive transmission or an RO allocated for preamble index hopping.

[0165] The operation and setting information related to S920 may also be applied to MSGA preamble transmission and MSGB reception operations.

[0166] That is, the PRACH preamble and the RAR in S920 may be replaced with the MSGA preamble and the MSGB, respectively, and the RA-RNTI in S920 may be replaced with the MSGB-RNTI.

[0167] FIG. 10 is a diagram for explaining an uplink transmission operation of a base station in a wireless communication system to which the present disclosure can be applied.

[0168] The base station may transmit configuration information related to repeated PRACH preamble transmission to the terminal (S1010).

[0169] As an example, based on receiving first terminal capability information related to PRACH preamble repeated transmission from the terminal, the base station may transmit configuration information related to PRACH preamble repeated transmission to the terminal.

[0170] The operations and parameters in S1010 may correspond to those in S910, and therefore a duplicated description will be omitted.

[0171] The base station may perform repeated PRACH preamble reception in at least one RO among the multiple ROs based on configuration information related to repeated PRACH preamble transmission (S1020).

[0172] For example, a specific signal or a specific channel scheduled / activated / configured by the base station may overlap / collide with a time / frequency resource corresponding to a specific RO among multiple ROs. In this case, the specific RO may be dropped by the terminal, and the base station may repeatedly receive the PRACH preamble in the remaining ROs excluding the specific RO among the multiple ROs.

[0173] The operations and parameters associated with S1020 may correspond to those associated with S920, and therefore a duplicated description will be omitted.

[0174] Hereinafter, RA-RNTI design for PRACH repeated transmission, an RO collision handling method for PRACH repeated transmission, and a RAPID hopping method for PRACH repeated transmission will be described in detail.

[0175] Example 1

[0176] Since PRACH repetitive transmission is not performed in the basic wireless communication system, the terminal can obtain one s_id, f_id, and t_id for the RO selected to transmit the PRACH preamble, and can calculate the RA-RNTI (or MSGB-RNTI) based on this.

[0177] In an improved wireless communication system, when PRACH repeated transmission is supported for a terminal / base station and the base station configures the terminal to repeatedly transmit a PRACH preamble (or an MSGA preamble), the terminal can repeatedly transmit the PRACH preamble across multiple ROs.

[0178] Example 1-1, Example 1-2, and Example 1-3 relate to a method in which a terminal calculates an RA-RNTI (or an MSGB-RNTI) when performing repeated PRACH preamble transmission using multiple ROs.

[0179] Example 1-1

[0180] The UE may set one specific RO among the ROs that have transmitted the PRACH preamble as a reference RO and calculate the RA-RNTI (or MSGB-RNTI) based on the set reference RO. That is, the UE may be configured to calculate the RA-RNTI (or MSGB-RNTI) based on the s_id, f_id, and t_id values ​​of the reference RO.

[0181] In this case, the reference RO may be predefined between the UE and the base station. Additionally or alternatively, the base station may configure / indicate the reference RO to the UE together with the PRACH configuration through RRC signaling. Thus, the UE may calculate the RA-RNTI and / or the MSGB-RNTI using Equation 3 and / or Equation 4.

[0182] As yet another example of the present disclosure, the reference RO may be the last RO among a plurality of ROs in which the terminal repeatedly transmits the preamble. Even if the RO required for the repeated transmission exceeds the PRACH period boundary (i.e., 10 ms), the above example (i.e., the method of defining / setting / indicating the reference RO as the last RO) may be applied.

[0183] FIG. 11(a) is a diagram for explaining a method for setting the last RO among multiple ROs as a reference RO according to an embodiment of the present disclosure.

[0184] Referring to FIG. 11(a), it is assumed that the RO for the terminal to repeatedly transmit the preamble starts from RACH period #N (i.e., starts from the start RO) and exists until RACH period #N+1 (i.e., the RA-RNTI reference RO).

[0185] The last RO among the ROs used in the repeated transmission may be set / indicated / defined as a reference RO for RA-RNTI calculation, and the terminal may receive an RAR from the base station using the RA-RNTI calculated based on the reference RO in the RAR window #N+1. In this case, the terminal may use s_id, f_id, and t_id values ​​associated with the reference RO for RA-RNTI calculation, and may receive an RAR UL grant using a preamble index transmitted in the reference RO as RAPID.

[0186] As yet another example of the present disclosure, the reference RO may be the first RO among multiple ROs in which the terminal repeatedly transmits the preamble. Even if the RO required for the repeated preamble transmission exceeds the RACH interval boundary (i.e., 10 ms), the above example (i.e., the method of defining / setting / indicating the reference RO as the first RO) may be applied. In addition, it may be preferable that the above example be applied when the base station knows the RO in which the terminal starts the repeated transmission and the RO in which the terminal ends the repeated transmission.

[0187] FIG. 11(b) is a diagram for explaining a method for setting a first RO among multiple ROs as a reference RO according to one embodiment of the present disclosure.

[0188] Referring to FIG. 11(b), it is assumed that an RO for the UE to repeatedly transmit a preamble is set to RACH period #N. In this case, the first RO among the ROs used for the repeated transmission may be set as a reference RO for RA-RNTI calculation. In this case, the UE may use the s_id, f_id, and t_id values ​​of the reference RO for RA-RNTI calculation, and may receive an RAR UL grant by using the preamble index transmitted to the reference RO as RAPID.

[0189] As an example of the present disclosure, when a terminal attempts to repeat transmission of a preamble for the number of repetitions set / instructed by a base station, a case may occur in which the RO required for the repeat transmission (based on SSB-to-RO mapping and / or RACH setting) exceeds the RACH interval or the total required RO time exceeds 10 ms.

[0190] In this case, the terminal may be configured / instructed / defined to perform repeated transmission only in ROs that do not exceed the RACH duration (when a specific condition is satisfied), and may be configured / defined / instructed to analyze the last RO among the ROs actually transmitted by the terminal as a reference RO.

[0191] In this case, the specific condition may be, for example, a case where the terminal performs repeat transmission more than X% (for example, X is a threshold value that is predefined or can be set / instructed by the base station) of the number of repetitions set / instructed by the base station even if the terminal does not perform repeat transmission in an RO that exceeds the RACH interval.

[0192] If the specific condition is not met, the terminal may repeat transmission of the preamble even beyond the RACH interval, and the RO that transmitted the last preamble may be the reference RO.

[0193] As yet another example of the present disclosure, the base station may configure a reference RO for the terminal by higher layer signaling (including PRACH configuration) (e.g., SIB, RRC, etc.). In this case, if an RO required for repeated transmission exists in an interval beyond the RACH interval bound, the terminal may be configured not to expect that the reference RO configured by the base station is configured as an RO belonging to the RACH interval (e.g., within the RACH interval # when an RO is required as in (a) of FIG. 11).

[0194] The terminal can determine that the RAR window begins after transmitting a preamble in the last RO, and therefore the terminal can expect the base station to set a reference RO from among the ROs present in the RACH period including the last RO among the ROs required for repeated transmission.

[0195] Additionally or alternatively, if the base station does not configure / indicate a reference RO to the terminal (i.e., RRC parameters such as PRACH configuration do not include information related to the reference RO), the terminal may use a predefined default reference RO.

[0196] The preset default reference RO may be a specific RO (e.g., the first RO or the last RO) among the ROs used by the terminal for repeated transmission. Alternatively, the preset default reference RO may be a specific RO (e.g., the first RO or the last RO) among the ROs set in a RACH interval including the last RO among the ROs used by the terminal for repeated transmission.

[0197] When a reference RO is set / indicated by the base station, the terminal may be configured to calculate the RA-RNTI (or MSGB-RNTI) based on the set / indicated reference RO. When a reference RO is not set / indicated by the base station, the terminal may be configured to calculate the RA-RNTI (or MSGB-RNTI) based on a default reference RO.

[0198] In the above example, the terminal can determine that the RAR window is set after the preamble transmission is completed in the last RO among the ROs for the repeated preamble transmission, and the terminal can expect that the RAR will be transmitted from the base station within the RAR window.

[0199] Example 1-2

[0200] A specific RO (e.g., one RO) among the multiple ROs that have transmitted the preamble may be set as a reference RO, and additional time information (e.g., SFN, etc.) may be set / defined for the terminal. The terminal may calculate the RA-RNTI (or MSGB-RNTI) based on the reference RO and the additional time information.

[0201] It is assumed that the first RO among the ROs used in the repeated transmission of the preamble by the UE is set / indicated as the reference RO. In this case, if the number of repetitions is large or the interval between the ROs in which the repeated preamble is transmitted is large, the last RO among the ROs used in the repeated transmission may exceed the RACH interval boundary (or the entire preamble repeated transmission interval may exceed 10 ms).

[0202] In this case, a problem may occur in that the RA-RNTI value calculated based on the reference RO in the RAR window in which the RAR for the repeated transmission is transmitted overlaps with the RA-RNTI value of another RO.

[0203] To solve the above-mentioned problems, additional time information may be set / defined / indicated in the RA-RNTI value.

[0204] As an example, the SFN (sub-frame) value in which the reference RO is located may be used as the additional time information. When the base station transmits the SFN value in which the reference RO is located to the terminal using the RAR UL grant (e.g., by a reserved field such as DCI or RAR), the base station can further indicate the additional time information to the terminal. In this case, the terminal can determine whether the RAR received from the base station is for the terminal based on the RA-RNTI value calculated based on the reference RO and the SFN value in which the reference RO is located (e.g., by comparing the SFN in which the reference RO is located with the calculated RA-RNTI value).

[0205] When the RAR window is longer than 10 ms in a 2-step RACH and / or NR-U 4-step RACH of a basic wireless communication system, the RA-RNTI values ​​may overlap, so the base station can further instruct the terminal on the SFN for RA-RNTI classification.

[0206] In the improved wireless communication system, when preamble repeat transmission is supported, the RAR window may be fixed at 10 ms. However, the above example is an example for solving the problem that the RO transmitting the actual preamble exceeds the RACH period (or the preamble repeat transmission period exceeds 10 ms).

[0207] Thus, when the preamble repeat transmission is configured / instructed to be performed and the preamble repeat transmission satisfies a specific condition, the base station can further instruct the terminal of additional time information, i.e., the terminal can expect the additional time information to be instructed by the base station.

[0208] In this case, the specific condition may be a case where the last RO among the ROs used in the repeated preamble transmission exceeds a RACH period boundary, or a case where the entire repeated preamble transmission exceeds 10 ms, etc. And, the additional time information may be an SFN where a reference RO is located, etc.

[0209] If the repeated preamble transmission does not satisfy the specific condition, the terminal can expect that no additional time information will be indicated by the base station.

[0210] Examples 1-3

[0211] Two or more of the ROs that have transmitted the preamble may each be set as a reference RO, and multiple RA-RNTIs (or MSGB-RNTIs) may be set based on the reference RO.

[0212] In this case, the reference RO may be predefined between the terminal and the base station. Additionally or alternatively, the base station may configure / instruct the terminal to configure / instruct multiple ROs together with the PRACH configuration through higher layer signaling. Characteristically, the embodiments 1-3 may be applied to a situation in which the terminal is to terminate the repeated preamble transmission early.

[0213] When an embodiment of early termination of preamble repetitive transmission is applied, a specific terminal can release a pre-configured RACH resource at an appropriate time without continuing to occupy it in order to repeatedly transmit a preamble. This has the advantage that the base station can operate the RACH resource with a margin. In addition, the terminal can save transmission power because it does not need to complete excessive preamble repetitive transmissions.

[0214] For example, the reference RO may be the last N ROs (consecutive or non-consecutive) among the ROs in which the UE has repeatedly transmitted the preamble. In this case, the value of N may be predefined and is not limited thereto. The base station may set / instruct the value of N to the UE through higher layer signaling.

[0215] In addition, when the terminal completes a preamble repetition transmission a certain number of times (e.g., the initially set number of repetitions - N+1 times), the base station can transmit an RAR to the terminal based on the received preamble. The terminal can expect that the RAR will be transmitted in the RAR window that exists after the last preamble that was actually transmitted.

[0216] As an example, if the number of repetitions initially set / instructed by the base station is 8 and the N value set by the base station is 2, the terminal can expect to receive an RAR based on the 7th RO after transmitting 7 (i.e., 8-2+1) preamble repetitions.

[0217] If a proper RAR is received (i.e., if an RAR with matching RA-RNTI and RAPID is received), the terminal may be configured to abort the remaining repeated preamble transmissions and transmit Msg.3PUSCH. As yet another example, if a proper RAR is not received, the terminal may transmit a final repeated transmission in the last 8th RO (after a predefined time) and expect to receive an RAR based on that RO.

[0218] When the terminal expects an RAR during repeated preamble transmission, the terminal may be configured to calculate the RA-RNTI based on the reference RO in which the last transmitted preamble exists among a plurality of reference ROs.

[0219] For example, the above-mentioned scheme may be applied when a RACH resource capable of repeated preamble transmission is distinguished from a RACH resource for single preamble transmission. For example, the above-mentioned scheme may be applied when a RACH resource is distinguished based on a preamble index in a specific RO or when a base station distinguishes RACH resources by independently configuring different ROs.

[0220] In this case, the base station may configure the terminal to use a separately indicated RO for requesting repeated transmission of Msg.3PUSCH as an RO capable of repeated preamble transmission.

[0221] In this case, a terminal that desires to repeatedly transmit a preamble and an Msg.3 PUSCH can report to the base station the UE capability that the Msg.3 PUSCH can be repeatedly transmitted and / or the UE capability that the preamble can be repeatedly transmitted. The terminal can perform the preamble repeated transmission according to the RO set by the base station, and the base station can configure / instruct the terminal to enable the Msg.3 PUSCH to be repeatedly transmitted.

[0222] The above example may be applied to a case where the RACH resource is divided according to the preamble repetition transmission and the single preamble transmission, but is not limited thereto. The above example may also be applied to a case where the RACH resource is shared during the preamble repetition transmission or the single preamble transmission.

[0223] For example, the above example may be applied when a specific terminal selects an arbitrary preamble index without separately classifying preamble indexes in a specific RO and performs preamble repeated transmission. The above example may also be applied when a specific terminal selects an arbitrary preamble index and performs single preamble transmission.

[0224] For this purpose, the base station may provide start RO information and the number of repetitive transmissions that can start preamble repetitive transmission together with PRACH configuration for the terminal for performing preamble repetitive transmission. Then, the base station may perform the following operations 1 and 2 simultaneously.

[0225] 1. Provide RAR grant for preamble detected in RO at specific time

[0226] 2. Providing RAR grant based on preamble detected by non-coherent (or coherent) detection from the start RO where preamble repeat transmission can start to the RO at a specific time point.

[0227] The terminal can perform one of the following operations A or B depending on the presence or absence of the UE capability for the repeated preamble transmission.

[0228] A. A terminal in a basic wireless communication system without UE capability for repeated preamble transmission expects to receive an RAR after transmitting a single preamble.

[0229] B. In an improved wireless communication system having UE capability for preamble repeated transmission, after completing repeated transmission within an RO corresponding to the number of repetitions from the start RO, the terminal calculates RA-RNTI based on the RO and expects to receive RAR.

[0230] According to the above-mentioned scheme, the base station can provide an RAR grant for a preamble repeatedly transmitted by a terminal in the improved wireless communication system, and the method of dividing the RACH resource can solve the problem of a reduction in the RACH resource of a terminal in the basic wireless communication system.

[0231] Example 2

[0232] The second embodiment relates to a method for handling RO collision for PRACH repeated transmission. The terminal can select an appropriate RO for the repeated preamble transmission according to a predefined method or a setting / instruction by the base station. However, a situation may occur in which the RO selected by the terminal must be dropped or postponed due to a collision with DL / UL signals / channels, etc.

[0233] If an RO collides with other signals / channels when a single preamble is transmitted, the terminal can select another RO instead of the RO to transmit the preamble. However, if an RO collides with other signals / channels when a repeated preamble is transmitted, additional base station / terminal operations such as RO dropping / postponement may be required.

[0234] As an example of the present disclosure, a RO in which a collision occurs may be dropped, and the dropped RO may be set / defined to be included in the number of repeated transmissions. The following describes the operation of a base station / terminal based on a scheme in which a RO in which a collision occurs is dropped and the dropped RO is included in the number of repeated transmissions.

[0235] Example 2-1

[0236] Example 2-1 relates to the operation of a terminal / base station depending on the location of an RO in which an RO collision occurs among ROs selected by a terminal for repeated preamble transmission.

[0237] As an example, if an RO collision occurs in the first RO (i.e., the starting RO) among the ROs selected by the terminal for repeated transmission, the terminal may perform operations according to the following case 1 or / and case 2.

[0238] Case 1: The terminal does not perform (i.e., postpones) the preamble repeat transmission with the RO (i.e., the RO where the collision occurred) as the first RO, and can select another RO as the first RO for the repeat transmission and perform the preamble repeat transmission.

[0239] Case 2: The terminal performs preamble repeat transmission with the relevant RO as the initial RO, but drops the initial RO and / or the colliding RO, and can perform preamble repeat transmission only in the remaining ROs.

[0240] As another example, if an RO collision occurs in the last RO among the ROs selected by the UE for repeated transmission, the UE may perform operations according to the following case 3 or / and case 4.

[0241] Case 3: Even if the terminal does not actually transmit a preamble in the last RO and drops the RO, the terminal may determine that the start time of the RAR window is determined based on the last RO and may be configured to expect reception of the RAR. In this case, the RA-RNTI (or MSGB-RNTI) value used by the terminal and the base station may be calculated / defined based on the last RO.

[0242] The operation according to case 3 may be performed when the RACH resources for preamble repeated transmission and the RACH resources for single preamble transmission are distinguished.

[0243] Case 4: Since the terminal knows in advance that it may drop the last RO without actually transmitting a preamble in the last RO, the terminal may determine that the start point of the RAR window is determined based on the last RO among the ROs in which a preamble is actually transmitted, and may be configured to expect reception of the RAR. In this case, the RA-RNTI (or MSGB-RNTI) value used by the terminal and the base station may be calculated / defined based on the last RO among the ROs in which a preamble is actually transmitted.

[0244] The operation according to case 4 may be performed when the RACH resources for preamble repeated transmission and the RACH resources for single preamble transmission are not distinguished.

[0245] As another example, an RO collision may occur not in the first or last RO selected by the UE for repeated transmission but in other ROs, in which case the UE may drop the RO that has the collision and perform preamble repeated transmission only in the remaining ROs.

[0246] Example 2-2

[0247] Example 2-2 relates to the operation of a terminal / base station depending on the reason why a collision occurred in each of the ROs selected by the terminal for repeated preamble transmission (i.e., the type of signal / channel in which the collision occurred).

[0248] As an example of the present disclosure, it is assumed that the reason why a terminal cannot transmit a preamble in a particular RO among the ROs selected for repeated preamble transmission is due to collision with another UL signal / channel.

[0249] In this case, the terminal can drop a specific RO that collides with another UL signal / channel and include the dropped RO in the number of preamble repetitions. By including the dropped RO in the number of preamble repetitions, misunderstanding between the terminal and the base station can be prevented.

[0250] As yet another example of the present disclosure, assume that the reason why a terminal cannot transmit a preamble in a particular RO among the ROs selected for repeated preamble transmission is due to a collision with other semi-static DL symbols and / or semi-static DL signals / channels (e.g., SSB), etc.

[0251] In this case, the terminal may postpone preamble transmission in an RO that collides with other semi-static DL symbols and / or semi-static DL signals / channels (e.g., SSB), etc. And, since no misunderstanding occurs between the terminal and the base station in relation to the preamble transmission, the terminal may not include the postponed RO in the number of repeated transmissions.

[0252] Additionally or alternatively, the terminal may (re)select ROs for the entire preamble repeat transmission count based on the above-mentioned operation and perform preamble repeat transmission. Here, if the dropped RO is included in the preamble repeat transmission count, the preamble repeat transmission count actually performed by the terminal may be smaller than the actually instructed preamble repeat transmission count.

[0253] At this time, it is assumed that the preamble transmission in the last RO is postponed. The start point of the RAR window and the RO for setting the RA-RNTI are postponed, so that the terminal can transmit the last preamble in the newly selected RO. Thus, the terminal can determine that the RAR window starts based on the RO in which the last preamble is transmitted, and can calculate the RA-RNTI based on the RO.

[0254] As yet another example, if the last RO is dropped, the terminal may perform an operation according to case 3 or case 4 described above.

[0255] The operations of the terminal / base station disclosed in each of the second embodiment, the second embodiment, and the second embodiment may be performed independently or together.

[0256] Example 3

[0257] Example 3 relates to a RAPID hopping scheme for PRACH repeated transmission.

[0258] When a terminal performs preamble repetitive transmission, a preamble index determined arbitrarily (at the MAC layer) (or set / instructed by the base station for contention-free random access (CFRA)) may be maintained each time the terminal transmits a preamble. However, when considering inter-cell interference randomization, the preamble index may be hopped each time the terminal transmits a preamble.

[0259] Specifically, the base station can set / instruct the terminal whether or not to perform the preamble index hopping operation through higher layer signaling. Also, the preamble index hopping operation may be applied when the RACH resource for the preamble repetitive transmission and the RACH resource for the single preamble transmission are distinguished. In this case, the preamble index hopping may be set / instructed / defined to operate only in the RACH resource for the preamble repetitive transmission.

[0260] As an example, when the RO is shared but the RACH resources for repeated transmission and single transmission are divided at the preamble level, the base station may predefine / configure a preamble index pool for repeated transmission, and preamble index hopping may be performed only within the preamble index pool.

[0261] As yet another example, if RACH resources for preamble repeated transmission and single preamble transmission are partitioned at the RO level, preamble index hopping may be performed only within the RO allocated for preamble repeated transmission.

[0262] As an example of the present disclosure, the first preamble index may be selected arbitrarily (at the MAC layer), and the preamble index used for the subsequent preamble repeat transmission may be set / defined / instructed to be hopped pseudo-randomly using a cell-ID or the like as a seed. Additionally or alternatively, a T (time) domain index (e.g., symbol, slot, subframe, SFN, etc.) may be considered as a seed for the cell ID. As a result, the preamble index (transmitted in the RO) may be set to be determined based on a combination of the T-domain index of the RO to be transmitted and the cell-ID.

[0263] Thus, when the terminal selects the first preamble index, the preamble index to be used by the terminal thereafter may be determined according to a predefined method.

[0264] Additionally or alternatively, for RO collision handling, the preamble index may be determined according to the number of preamble repetitions, however, this is merely an example, and the preamble index may be set to hop quasi-randomly based on the f(frequency)-domain index, slot index, symbol index, and / or cell-ID of the RO to which the UE is going to transmit the preamble.

[0265] In this case, the base station can know the order in which the terminal hops and / or transmits the preamble indexes based on the initially selected preamble index. The base station can combine the preamble indexes received in each RO based on the above information (e.g., the order in which the terminal hops and / or transmits the preamble indexes).

[0266] In this case, since the terminal hops the preamble index every time it transmits a preamble repeatedly, it needs to determine what value the base station instructs the RAPID value required for the terminal to confirm the RAR grant.

[0267] As an example, a preamble index value selected by the UE (at the MAC layer) in a start RO among ROs for preamble repeated transmission may be set / defined to be used as RAPID.

[0268] As yet another example, a preamble index used in the last RO after multiple preamble hopping (i.e., regardless of whether or not there is an actual transmission, taking into account RO dropping, etc.) may be set / defined to be used as RAPID.

[0269] As yet another example, the last preamble index among preambles actually transmitted by the terminal may be set / defined to be used as RAPID.

[0270] In the above embodiment, the method of calculating RA-RNTI based on the reference RO may be applied to the method of calculating MSGB-RNTI based on the reference RO. Also, the above embodiment can be configured / applied to other UL signals / channels such as PUSCH / PUCCH.

[0271] The above-described embodiment may be included as one of the implementation methods of the present disclosure. Also, the above-described embodiment may be implemented independently, or may be implemented in the form of a combination (or merging) of some of the embodiments. The information on whether to apply the operation / setting / instruction included in the above-described embodiment (or information on the rule of the above-described embodiment) may be defined so that the base station notifies the terminal by a predefined signal (e.g., a physical layer signal or a higher layer signal). The higher layer may include one or more functional layers such as MAC, RLC, PDCP, RRC, and SDAP.

[0272] FIG. 12 is a diagram for explaining a signaling procedure of a network side and a terminal according to an embodiment of the present disclosure.

[0273] FIG. 12 illustrates signaling between the network side and the terminal (UE) in an M-TRP situation to which the above-described examples of the present disclosure (e.g., Example 1, Example 1-1, Example 1-2, Example 1-3, Example 2, Example 2-1, Example 2-2, or a combination of one or more of the detailed examples thereof) may be applied.

[0274] Here, the UE / network side is exemplary and may be replaced with various devices as described with reference to FIG. 13. FIG. 12 is for convenience of explanation and does not limit the scope of the present disclosure. Also, some steps shown in FIG. 12 may be omitted depending on the situation and / or settings. Also, in the operation of the network side / UE in FIG. 12, the above-mentioned uplink transmission / reception operation, M-TRP-related operation, etc. may be referred to or used.

[0275] In the following description, the network side may be one base station including multiple TRPs, or one cell including multiple TRPs. Alternatively, the network side may include multiple RRHs (remote radio heads) / RRUs (remote radio units). As an example, an ideal / non-ideal backhaul may be set between TRP1 and TRP2 constituting the network side. In addition, the following description is based on multiple TRPs, but this may be equally extended and applied to transmission through multiple panels / cells, and may be equally extended and applied to transmission through multiple RRHs / RRUs, etc.

[0276] In addition, the following description will be based on "TRP", but as described above, "TRP" may be applied in place of expressions such as panel, antenna array, cell (e.g., macro cell / small cell / pico cell, etc.), TP (transmission point), base station (gNB, etc.), etc. As described above, TRP may be classified according to information (e.g., CORESET index, ID) related to the CORESET group (or CORESET pool).

[0277] As an example, when one terminal is configured to transmit and receive from multiple TRPs (or cells), this may mean that multiple CORESET groups (or CORESET pools) are configured for one terminal. Such configuration of the CORESET group (or CORESET pool) may be performed by higher layer signaling (e.g., RRC signaling, etc.).

[0278] Also, the base station may collectively refer to an object that transmits and receives data to and from a terminal. For example, the base station may be a concept including one or more TPs (Transmission Points) and one or more TRPs (Transmission and Reception Points). Also, the TPs and / or TRPs may include a panel of the base station, a transmission and reception unit, etc.

[0279] 12, a base station (e.g., BS) can periodically transmit an SSB to a terminal (S1202). Here, the SSB may include a PSS / SSS / PBCH. The base station can transmit the SSB to the terminal using beam sweeping.

[0280] The base station may transmit remaining minimum system information (RMSI) and other system information (OSI) to the terminal (S1204). The RMSI may include information (e.g., PRACH configuration information) required for the terminal to initially connect to the base station. In this case, the terminal may identify the best SSB after performing SSB detection.

[0281] The terminal may then transmit a RACH preamble (Message 1, Msg1) to the base station using a PRACH resource linked / corresponding to the index (i.e., beam) of the best SSB (S1206).

[0282] The beam direction of the RACH preamble may be associated with the PRACH resource, and the association between the PRACH resource (and / or the RACH preamble) and the SSB index may be configured by system information (e.g., RMSI).

[0283] In this case, the terminal may perform repeated PRACH preamble transmission. The terminal may perform repeated PRACH preamble transmission based on configuration information related to repeated PRACH transmission received from the base station.

[0284] Thereafter, as part of the RACH process, the base station may send a Random Access Response (RAR) (Msg2) to the terminal in response to the PRACH preamble (S1208).

[0285] The RAR may include at least one of a field related to PUSCH repeated transmission, a field for indicating the presence or absence of PUSCH preamble repeated transmission, or a PUSCH time / frequency resource field.

[0286] The terminal can transmit Msg.3 PUSCH (eg, RRC Connection Request) using the uplink grant in the RAR (S1210).

[0287] The terminal may perform PUSCH repeat transmission based on the RAR, where the number of PUSCH repeat transmissions may be based on the number of PRACH preamble repeat transmissions.

[0288] The base station may transmit a contention resolution message (Msg4) to the terminal (S1212). Msg4 may include an RRC connection setup.

[0289] When an RRC connection is established between the base station and the terminal by the RACH procedure, subsequent beam alignment may be performed based on SSB / CSI-RS (in the downlink) and SRS (in the uplink). For example, the terminal may receive SSB / CSI-RS (S1214). The SSB / CSI-RS may be used by the terminal to generate a beam / CSI report.

[0290] The base station may then request a beam / CSI report from the terminal using the DCI (S1216). At this time, the terminal may generate a beam / CSI report based on the SSB / CSI-RS and transmit the generated beam / CSI report to the base station on the PUSCH / PUCCH (S1218). The beam / CSI report may include beam measurement results, information on a preferred beam, etc. The base station and the terminal may switch beams based on the beam / CSI report (S1220a, S1220b).

[0291] Thereafter, the terminal and the base station may perform the above-described / proposed embodiments. For example, the terminal and the base station may process information in the memory and transmit a radio signal according to the embodiments of the present disclosure based on configuration information obtained in a network connection procedure (e.g., a system information acquisition procedure, an RRC connection procedure using RACH, etc.), or process a received radio signal and store it in the memory. Here, the radio signal may include at least one of a PDCCH, a PDSCH, and a Reference Signal (RS) in the downlink, and at least one of a PUCCH, a PUSCH, and an SRS in the uplink.

[0292] Apparatus to which the present disclosure can be applied

[0293] FIG. 13 illustrates a block diagram of a wireless communication device according to an embodiment of the present disclosure.

[0294] Referring to FIG. 13, the first device 100 and the second device 200 can transmit and receive wireless signals using various wireless connection technologies (e.g., LTE, NR).

[0295] The first device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may be configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed in the present disclosure.

[0296] For example, the processor 102 may process the information in the memory 104 to generate a first information / signal and then transmit a wireless signal including the first information / signal from the transceiver 106. The processor 102 may also receive a wireless signal including a second information / signal from the transceiver 106 and then store in the memory 104 information resulting from signal processing of the second information / signal.

[0297] The memory 104 may be coupled to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including instructions for performing a part or all of the processes controlled by the processor 102 or for executing the descriptions, functions, procedures, suggestions, methods and / or operation flow diagrams disclosed in the present disclosure. Here, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to embody a wireless communication technology (e.g., LTE, NR). The transceiver 106 may be coupled to the processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be referred to as an RF (Radio Frequency) unit. In the present invention, the device may mean a communication modem / circuit / chip.

[0298] The second device 200 may include one or more processors 202, one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may be configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in the present disclosure. For example, the processor 202 may process information in the memory 204 to generate a third information / signal, and then transmit a wireless signal including the third information / signal from the transceiver 206. In addition, the processor 202 may receive a wireless signal including a fourth information / signal from the transceiver 206, and then store information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 may be coupled to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including instructions for performing part or all of the processes controlled by the processor 202 or executing the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed in the present disclosure. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to embody a wireless communication technology (e.g., LTE, NR). The transceiver 206 may be coupled to the processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be referred to as an RF unit. In the present invention, the device may mean a communication modem / circuit / chip.

[0299] The hardware elements of the devices 100, 200 are described in more detail below. One or more protocol layers may be embodied by one or more processors 102, 202, without being limited thereto. For example, one or more processors 102, 202 may embody one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102, 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in the present disclosure. One or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in the present disclosure. The one or more processors 102, 202 can generate and provide signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information to one or more transceivers 106, 206 according to the functions, procedures, suggestions, and / or methods disclosed in this disclosure. The one or more processors 102, 202 can receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure.

[0300] The one or more processors 102, 202 may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. The one or more processors 102, 202 may be embodied in hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in the present disclosure may be embodied using firmware or software, and the firmware or software may be embodied to include modules, procedures, functions, etc. Firmware or software configured to execute the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure may be included in one or more processors 102, 202 or stored in one or more memories 104, 204 and executed by one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in the present disclosure may be embodied in firmware or software in the form of code, instructions and / or collections of instructions.

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

[0302] The one or more transceivers 106, 206 may transmit user data, control information, wireless signals / channels, etc., as referred to in the methods and / or operational flow diagrams of the present disclosure, to one or more other devices. The one or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams of the present disclosure, from one or more other devices. For example, the one or more transceivers 106, 206 may be coupled to one or more processors 102, 202 and may transmit and receive wireless signals. For example, the one or more processors 102, 202 may control the one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, the one or more processors 102, 202 may control the one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. In addition, one or more transceivers 106, 206 may be coupled to one or more antennas 108, 208, and the one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, radio signals / channels, etc., as described, functions, procedures, suggestions, methods, and / or operation flow diagrams disclosed in the present disclosure, via the one or more antennas 108, 208. In the present disclosure, the one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 may convert the received radio signals / channels, etc., from RF band signals to baseband signals for processing the received user data, control information, radio signals / channels, etc., using one or more processors 102, 202. The one or more transceivers 106, 206 may convert the user data, control information, radio signals / channels, etc., processed using one or more processors 102, 202, from baseband signals to RF band signals. To that end, one or more of the transceivers 106, 206 may include (analog) oscillators and / or filters.

[0303] The above-described embodiments are combinations of the components and features of the present disclosure in a predetermined form. Each component or feature should be considered as optional unless otherwise expressly stated. Each component or feature may be implemented in a form not combined with other components or features. It is also possible to combine some components and / or features to configure the embodiments of the present disclosure. The order of operations described in the embodiments of the present disclosure may be changed. Some configurations or features of one embodiment may be included in another embodiment, or may be replaced with corresponding configurations or features of another embodiment. It is clear that claims that do not have an explicit reference relationship in the claims may be combined to configure an embodiment, or may be included as a new claim by amendment after filing.

[0304] It is obvious to those skilled in the art that the present disclosure can be embodied in other specific forms without departing from the essential features of the present disclosure. Therefore, the above detailed description should not be interpreted as limiting in any respect, but should be considered as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the attached claims, and any modifications within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

[0305] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that cause a device or computer to perform operations according to the methods of the various embodiments, and non-transitory computer-readable media on which such software or instructions or the like can be stored and executed on a device or computer. Instructions available for programming a processing system to perform features described in the present disclosure may be stored on / in a storage medium or computer-readable storage medium, and computer program products including such storage media may be used to embody features described in the present disclosure. The storage medium may include high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, but is not limited thereto, and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory optionally includes one or more storage devices that are located remotely from the processor. The memory or alternatively the non-volatile memory devices in the memory include non-transitory computer-readable storage media. The features described in this disclosure may be embodied in software and / or firmware stored on any one of a number of machine-readable media and capable of controlling the hardware of a processing system and allowing the processing system to interact with other mechanisms that utilize the results of embodiments of the present disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0306] Here, the wireless communication technology implemented in the devices 100 and 200 of the present disclosure may include LTE, NR, and 6G as well as Narrowband Internet of Things (NB-IoT) for low power communication. At this time, for example, the NB-IoT technology may be an example of a Low Power Wide Area Network (LPWAN) technology, and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the devices 100 and 200 of the present disclosure may perform communication based on the LTE-M technology. At this time, as an example, the LTE-M technology may be an example of an LPWAN technology, and may be called various names such as eMTC (enhanced Machine Type Communication). For example, the LTE-M technology may be embodied by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above names. Additionally or alternatively, the wireless communication technology embodied in the devices 100 and 200 of the present disclosure may include at least one of ZigBee (registered trademark), Bluetooth (registered trademark), and Low Power Wide Area Network (LPWAN), which consider low power communication, and is not limited to the above names. As an example, the ZigBee (registered trademark) technology may generate personal area networks (PANs) related to small / low power digital communication based on various standards such as IEEE 802.15.4, and may be called various names. [Industrial Applicability]

[0307] The method proposed in this disclosure has been described mainly as being applied to 3GPP LTE / LTE-A and 5G systems, but it can be applied to various wireless communication systems other than 3GPP LTE / LTE-A and 5G systems.

Claims

1. A method for a terminal performing uplink transmission in a wireless communication system, the method comprising: receiving configuration information related to repeated transmission of a physical random access channel (PRACH) preamble from a base station; and repeating the PRACH preamble in at least one of a plurality of random access channel occasions (ROs) based on the configuration information; A method in which, based on a collision between a specific RO among the plurality of ROs and a specific signal or a specific channel, the specific RO is dropped, and a random access (RA)-RNTI (radio network temporary identifier) ​​is calculated based on one or more reference ROs determined in the remaining ROs among the plurality of ROs excluding the specific RO.

2. The method of claim 1 , wherein the single RO selected from the remaining ROs of the plurality of ROs excluding the specific RO is the first RO or the last RO of the remaining ROs.

3. The information regarding the one or more reference ROs is received from the base station by higher layer signaling; The method of claim 1 , wherein the higher layer signaling includes configuration information related to the PRACH preamble repeated transmission.

4. The method of claim 1 , wherein the one or more reference ROs are determined to be a predefined default RO based on the fact that no higher layer signaling including information regarding the one or more reference ROs is received from the base station.

5. A random access response (RAR) including a system frame number (SFN) value corresponding to a single reference RO is received from the base station; The method of claim 1 , wherein the RA-RNTI and the SFN value calculated based on the single reference RO determine whether the RAR is an RAR for the terminal.

6. The method according to claim 1, wherein a plurality of reference ROs are determined from the remaining ROs excluding the specific RO among the plurality of ROs, and the RA-RNTI is calculated based on the reference RO from which the last PRACH preamble was transmitted among the plurality of reference ROs.

7. The method of claim 1, wherein first terminal capability information indicating that the PRACH preamble repeat transmission is supported and second terminal capability information indicating that the PUSCH repeat transmission based on the RAR is supported are transmitted to the base station.

8. The method of claim 1 , wherein the PRACH preamble is transmitted to the base station in remaining ROs other than the specific RO among the plurality of ROs.

9. The method of claim 1, wherein the RA-RNTI is calculated based on an index of a first symbol of the one or more reference ROs, an index of a first slot of the one or more reference ROs in a system frame, an index of the one or more reference ROs in a frequency domain, and an index of an uplink carrier used for the PRACH preamble repetition transmission.

10. The method of claim 1 , wherein configuration information related to a preamble index hopping operation related to the PRACH preamble repeated transmission is received from the base station.

11. The method of claim 10, wherein the configuration information related to the preamble index hopping operation includes at least one of information regarding a preamble index pool for the PRACH preamble repetition transmission or an RO allocated for preamble index hopping.

12. A terminal that performs uplink transmission in a wireless communication system, the terminal comprising: one or more transceivers; one or more processors coupled to the one or more transceivers; The one or more processors: receiving configuration information related to repeated transmission of a physical random access channel (PRACH) preamble from a base station via the one or more transceivers; The PRACH preamble is configured to be repeatedly transmitted in at least one RO (random access channel occasion) among a plurality of ROs based on the configuration information; A terminal, comprising: a terminal that, based on a collision between a specific RO among the plurality of ROs and a specific signal or a specific channel, drops the specific RO; and calculates a random access (RA)-RNTI (radio network temporary identifier) ​​based on one or more reference ROs determined in the remaining ROs among the plurality of ROs excluding the specific RO.

13. 1. A method for a base station performing uplink reception in a wireless communication system, the method comprising: transmitting configuration information related to repeated transmission of a physical random access channel (PRACH) preamble to a terminal; and performing repeated reception of the PRACH preamble in at least one of a plurality of random access channel occasions (ROs) based on the configuration information; A method in which, based on a collision between a specific RO among the plurality of ROs and a specific signal or a specific channel, the specific RO is dropped, and a random access (RA)-RNTI (radio network temporary identifier) ​​is calculated by the terminal based on one or more reference ROs determined in the remaining ROs among the plurality of ROs excluding the specific RO.

14. A base station performing uplink reception in a wireless communication system, the base station comprising: one or more transceivers; one or more processors coupled to the one or more transceivers; The one or more processors: transmitting configuration information related to repeated transmission of a physical random access channel (PRACH) preamble to a terminal via the one or more transceivers; The PRACH preamble is configured to be repeatedly received in at least one of a plurality of random access channel occasions (ROs) based on the configuration information; A base station, wherein the specific RO among the plurality of ROs is dropped based on collision of the specific RO with a specific signal or a specific channel, and a random access (RA)-RNTI (radio network temporary identifier) ​​is calculated by the terminal based on one or more reference ROs determined in the remaining ROs excluding the specific RO among the plurality of ROs.

15. 1. A processing device configured to control a terminal for uplink transmission in a wireless communication system, the processing device comprising: one or more processors; one or more computer memories operatively coupled to the one or more processors and configured to store instructions for performing operations based on being executed by the one or more processors; The operation includes: receiving configuration information related to repeated transmission of a physical random access channel (PRACH) preamble from a base station; and performing an operation of repeatedly transmitting the PRACH preamble in at least one of a plurality of random access channel occasions (ROs) based on the configuration information; A processing device, comprising: a processing unit for calculating a random access (RA)-RNTI (radio network temporary identifier) ​​based on one or more reference ROs determined in remaining ROs excluding the specific RO, the specific RO being dropped based on collision of the specific RO with a specific signal or a specific channel among the plurality of ROs.

16. One or more non-transitory computer-readable media storing one or more instructions, The one or more instructions are executed by one or more processors, providing an apparatus for uplink transmission in a wireless communication system, comprising: Receive configuration information related to repeated transmission of a physical random access channel (PRACH) preamble from a base station; The PRACH preamble is repeatedly transmitted in at least one of a plurality of random access channel occasions (ROs) based on the configuration information; A computer-readable medium, comprising: a first RO among the plurality of ROs; a second RO among the plurality of ROs; a third RO among the plurality of ROs; a second RO among the plurality of ROs; a third RO among the plurality of ROs;

Images