FIRST WIRELESS USER EQUIPMENT AND BASE STATION

Abstract

The invention relates to a method and apparatus for random access for user equipment with reduced capacity in a wireless communication system. The method for implementing random access by user equipment (UE) in a wireless communication system according to a scheme of the invention may include: an operation to acquire configuration information related to random access from the base station; an operation to identify at least one of the RACH occasion (RO) groups related to the transmission of a random access preamble, one or more ROs, and a group of random access preambles based on at least one of the configuration information related to random access, UE type, and repeat level; and an operation to transmit one or more random access preambles in each of the one or more ROs.

Description

Random access method and device for a reduced capacity terminal in a wireless communication system The present disclosure relates to random access in a wireless communication system, and specifically to a random access method and apparatus for a terminal with reduced capacity compared to a conventional terminal. 3GPP (3rd Generation Partnership Project) NR (New Radio) systems can support various numerologies for time-frequency resource unit standards by considering various scenarios, service requirements, and potential system compatibility to meet the requirements for 5th generation (5G) communication. In addition, NR systems can support the transmission of physical signals or physical channels through multiple beams to overcome poor channel environments, such as high path loss, phase noise, and frequency offset occurring at high carrier frequencies. Through this, NR systems can support applications such as eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type Communications), and URLLC (Ultra Reliable and Low Latency Communication), and additionally support TSC (Time Sensitive Communication) applications located at the boundary between mMTC and URLLC. Here, mMTC, URLLC, and TSC can be associated with the utilization of the Internet of Things (IoT) considering vertical industries. These applications can be supported on the same network. Discussions are underway to support new types of devices in the 3GPP NR system. For example, these new types of devices may include industrial wireless sensors, video surveillance, and wearable devices. The service requirements for these new types of devices are higher than those of conventional LPWANs such as LTE-M (LTE-MTC) or NB-IoT (Narrow Band-IoT), but lower than those of eMBB or URLLC. Considering this, such new types of devices can be referred to as Reduced Capability (RC) devices. Measures to support RC terminals in the 3GPP NR system are currently under discussion, and specific measures have not yet been established, particularly regarding random access for RC terminals. The technical problem of the present disclosure is to provide a new random access method and apparatus for an RC terminal in a wireless communication system. An additional technical objective of the present disclosure is to provide a method and apparatus for identifying an RC terminal in a network during initial access of a terminal. An additional technical objective of the present disclosure is to provide a method and apparatus for identifying an RC terminal in a network during the transmission of a random access preamble of a terminal. The technical problems to be solved in this disclosure are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this disclosure belongs from the description below. A method for a terminal to perform random access in a wireless communication system according to one aspect of the present disclosure may include: receiving random access-related configuration information from a base station; determining one or more of a random access preamble group, one or more ROs, or a random access preamble group related to the transmission of the random access preamble based on one or more of the random access-related configuration information, a terminal type, or a repetition level; and transmitting one or more random access preambles in each of the one or more ROs. The features briefly summarized above regarding the present disclosure are merely exemplary aspects of the detailed description of the present disclosure that follows and do not limit the scope of the present disclosure. According to the present disclosure, a new random access method and apparatus for an RC terminal in a wireless communication system may be provided. According to the present disclosure, a method and apparatus for identifying an RC terminal in a network during initial access of a terminal may be provided. According to the present disclosure, a method and apparatus for identifying an RC terminal in a network during the transmission of a random access preamble of a terminal may be provided. The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below. FIG. 1 is a drawing for illustrating an NR frame structure to which the present disclosure can be applied. FIG. 2 is a diagram showing an NR resource structure to which the present disclosure can be applied. FIG. 3 is a diagram illustrating an NR random access procedure to which the present disclosure may be applied. FIG. 4 is a drawing for illustrating an embodiment of a preamble group setting to which the present disclosure may be applied. FIG. 5 is a drawing for illustrating an additional embodiment of a preamble group setting to which the present disclosure may be applied. FIG. 6 is a drawing for illustrating additional embodiments of preamble group settings to which the present disclosure may be applied. FIG. 7 is a drawing for illustrating an example of an initial active bandwidth portion (BWP) setting to which the present disclosure may be applied. FIG. 8 is a drawing for illustrating an embodiment of an RO setting to which the present disclosure may be applied. FIG. 9 is a drawing for illustrating additional embodiments of RO settings to which the present disclosure may be applied. FIG. 10 is a drawing for illustrating additional embodiments of preamble group settings to which the present disclosure may be applied. FIG. 11 is a drawing for illustrating additional embodiments of preamble group settings to which the present disclosure may be applied. FIG. 12 is a drawing for illustrating additional embodiments of preamble group settings to which the present disclosure may be applied. FIG. 13 is a flowchart for explaining terminal operation according to the present disclosure. FIG. 14 is a diagram showing the configuration of a base station device and a terminal device according to the present disclosure. Hereinafter, embodiments of the present disclosure are described in detail with reference to the attached drawings so that those skilled in the art can easily implement them. However, the present disclosure may be embodied in various different forms and is not limited to the embodiments described herein. In describing the embodiments of the present disclosure, if it is determined that a detailed description of known configurations or functions may obscure the essence of the present disclosure, such detailed description is omitted. Furthermore, parts of the drawings unrelated to the description of the present disclosure have been omitted, and similar parts are denoted by similar reference numerals. In the present disclosure, when a component is described as being “connected,” “combined,” or “joined” with another component, this may include not only a direct connection but also an indirect connection in which another component exists in between. Furthermore, in the present disclosure, the terms “comprising” or “having” specify the presence of the mentioned features, steps, actions, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, actions, elements, components, and / or groups thereof. In the present disclosure, terms such as first, second, etc. are used solely for the purpose of distinguishing one component from another and are not used to limit the components, nor do they limit the order or importance of the components unless specifically stated otherwise. Accordingly, within the scope of the present disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and likewise, a second component in one embodiment may be referred to as a first component in another embodiment. In this disclosure, distinct components are intended to clearly describe their respective features and do not imply that the components are separate. That is, multiple components may be integrated to form a single hardware or software unit, or a single component may be distributed to form multiple hardware or software units. Accordingly, such integrated or distributed embodiments are included within the scope of this disclosure, unless otherwise noted. In the present disclosure, the components described in various embodiments do not necessarily mean essential components, and some may be optional components. Accordingly, embodiments consisting of a subset of the components described in one embodiment are also included within the scope of the present disclosure. Furthermore, embodiments including additional components in addition to the components described in various embodiments are also included within the scope of the present disclosure. The terms used in this disclosure are for the description of specific embodiments and are not intended to limit the claims. As used in the description of embodiments and in the appended claims, the singular form is intended to include the plural form unless the context clearly indicates otherwise. Additionally, the term "and / or" as used in this disclosure may refer to one of the related enumerated items, or refers to and includes any and all possible combinations of two or more of them. The present disclosure describes a wireless communication network or a wireless communication system, and operations performed in the wireless communication network may be performed in the process of controlling the network and transmitting or receiving signals at a device (e.g., a base station) governing the wireless communication network, or in the process of transmitting or receiving signals at a terminal connected to the wireless network or between terminals. It is self-evident that various operations performed for communication with a terminal in a network consisting of multiple network nodes, including a base station, can be performed by the base station or other network nodes other than the base station. The term 'Base Station (BS)' may be replaced by terms such as fixed station, Node B, eNodeB (eNB), ng-eNB, gNodeB (gNB), and Access Point (AP). Additionally, the term 'terminal' may be replaced by terms such as User Equipment (UE), Mobile Station (MS), Mobile Subscriber Station (MSS), Subscriber Station (SS), and non-AP Station (non-AP STA). In the present disclosure, transmitting or receiving a channel includes the meaning of transmitting or receiving information or signals through said channel. For example, transmitting a control channel means transmitting control information or signals through the control channel. Similarly, transmitting a data channel means transmitting data information or signals through the data channel. The definitions of the abbreviations used in this disclosure are as follows. BSR: Buffer Status Report CSI-RS: Channel State Information-Reference Signal MAC: Medium Access Control PDCCH: Physical Downlink Control Channel PDSCH: Physical Downlink Shared Channel PRACH: Physical Random Access Channel RA: Random Access RACH: Random Access Channel RC: Reduced Capability or Reduced Complexity RO: RACH Occasion or PRACH Occasion RRC: Radio Resource Control RSRP: Reference Signal Received Power SCS: Sub-Carrier Spacing SIB: System Information Block SSB: Synchronization Signal Block A 5G system can be defined as including not only NR systems but also all existing LTE (Long Term Evolution) series systems. That is, a 5G system may include not only cases where NR radio access technology is applied alone, but also cases where LTE series radio access technology and NR radio access technology are applied together. Furthermore, 5G sidelink technology can be said to include both sidelink technologies where NR is applied alone or where LTE series and NR are applied together. The physical resource structure of the NR system is described below. FIG. 1 is a drawing for illustrating an NR frame structure to which the present disclosure can be applied. FIG. 1 is a drawing for illustrating an NR frame structure to which the present disclosure can be applied. In NR, the fundamental unit of the time domain is T c =1 / (Δf max ·N f ) can be, and Δf max =480·10 3 and N f =4096. Meanwhile, the basic unit of the time domain in LTE is T s =1 / (Δf ref ·N f,ref ) can be, and Δf ref =15·10 3 and N f,ref =2048 can be. The constant for the multiple relationship between the NR time base unit and the LTE time base unit is κ=T s / T c It can be defined as =64. Referring to FIG. 1, the time structure of a frame for DL / UL transmission is T f =1 / (Δf max N f / 100)·T c It can have =10ms. In this case, one frame is T sf =(Δf max N f / 1000)·T c It consists of 10 subframes corresponding to time. The number of consecutive OFDM symbols per subframe is N. symb subframe,μ =N symb slot N slot subframe,μ It may be possible. In addition, each frame may be divided into two half frames of the same size, half frame 1 may consist of subframes 0-4, and half frame 2 may consist of subframes 5-9. Referring to Fig. 1, N TA represents the timing advance (TA) between the downlink (DL) and the uplink (UL). At this time, the transmission timing of the uplink transmission frame i is determined based on the downlink reception timing at the terminal and the following mathematical formula 1. N in mathematical formula 1 TA,offset can be a TA offset value resulting from duplex mode differences, etc. Basically, in FDD (Frequency Division Duplex), N TA,offset Although it has a value of 0, in TDD (Time Division Duplex), N is used to account for the margin regarding DL-UL switching time. TA,offset It can be defined as a fixed value. FIG. 2 is a diagram showing an NR resource structure to which the present disclosure can be applied. Resource elements (REs) within a resource grid can be indexed according to each subcarrier spacing. In this case, one resource grid can be created for each antenna port and for each subcarrier spacing. Uplink and downlink transmission and reception can be performed based on the corresponding resource grid. In the frequency domain, a single Resource Block (RB) consists of 12 REs, and for each of the 12 REs, there is an index (n) for one RB. PRB ) can be configured. The index for RB can be utilized within a specific frequency band or system bandwidth. The index for RB can be defined as shown in Equation 2 below. Here, N sc RB represents the number of subcarriers per RB, and k represents the subcarrier index. Numericals can be configured in various ways to satisfy the diverse services and requirements of the NR system. Table 1 below shows examples of numericals supported by the NR system. μΔf=2 μ ·15 [kHz]Cyclic prefix015Normal130Normal260Normal, Extended3120Normal4240Normal Referring to Table 1, the numeralities can be defined based on the subcarrier spacing (SCS), cyclic prefix (CP) length, and the number of OFDM symbols per slot used in an Orthogonal Frequency Division Multiplexing (OFDM) system. The aforementioned values ​​can be provided to the terminal via the upper layer parameters DL-BWP-mu and DL-BWP-cp for the downlink, and via the upper layer parameters UL-BWP-mu and UL-BWP-cp for the uplink. As an example, in Table 1, when the subcarrier spacing setting index (μ) is 2, the subcarrier spacing (Δf) is 60 kHz, and normal CP and extended CP can be applied. For other numerality indices, only normal CP can be applied. In this case, a normal slot can be defined as the basic time unit used to transmit a single piece of data and control information in an NR system. The length of a normal slot can basically consist of 14 OFDM symbols. In addition, unlike a slot, a subframe has an absolute time length of 1ms in an NR system and can be used as a reference time for the length of other time intervals. In this case, for the coexistence or backward compatibility of LTE and NR systems, a time interval similar to that of an LTE subframe may be required in the NR standard. For example, in LTE, data can be transmitted based on a unit of time called a Transmission Time Interval (TTI), and the TTI can be composed of one or more subframes. In this case, in LTE, one subframe can be set to 1ms and can contain 14 OFDM symbols (or 12 OFDM symbols). Additionally, non-slots may be defined in NR. A non-slot may refer to a slot having a number of symbols smaller than that of a normal slot by at least one symbol. For example, when providing low latency such as in a URLLC service, latency can be reduced through non-slots having a number of symbols smaller than that of a normal slot. In this case, the number of OFDM symbols included in the non-slot may be determined by considering the frequency range. For example, in a frequency range of 6 GHz or higher, a non-slot with a length of 1 OFDM symbol may be considered. As another example, the number of OFDM symbols defining a non-slot may include at least 2 OFDM symbols. In this case, the range of the number of OFDM symbols included in the non-slot may be configured as the length of a mini-slot up to the normal slot length minus 1. However, as a specification for the non-slot, the number of OFDM symbols may be limited to a range of 2, 4, or 7 symbols, but is not limited to the embodiments described above. In addition, for example, in the unlicensed band below 6 GHz, subcarrier spacing corresponding to μ 1 and 2 may be used, and in the unlicensed band above 6 GHz, subcarrier spacing corresponding to μ 3 and 4 may be used. In this case, for example, when μ is 4, it may be used for the Synchronization Signal Block (SSB). μN symb slot N slot frame,μ N slot subframe,μ 01410111420221440431480841416016 Table 2 shows the number of OFDM symbols per slot (N) for normal CP for each subcarrier spacing setting (μ). symb slot ), number of slots per frame (N slot frame,μ ), number of slots per subframe (N slot subframe,μ ) represents. Table 2 shows the values ​​described above based on a normal slot having 14 OFDM symbols. μN symb slot N slot frame,μ N slot subframe,μ 212404 Table 3 shows the number of slots per frame and the number of slots per subframe based on a normal slot with 12 OFDM symbols per slot when extended CP is applied (i.e., when μ is 2 and subcarrier spacing is 60 kHz). The RC NR to which the present disclosure can be applied is described below. 3GPP confirmed that IMT-2020 requirements can be certified for mMTC purposes through NB-IoT or LTE-M. To support URLLC, URLLC features were all introduced in Rel-15 LTE / NR. Furthermore, NR URLLC continues to evolve through Rel-16 eURLLC and the Industrial IoT (IIoT) work item. In addition, 5G integration work is underway in Rel-16 for the application of Time-Sensitive Networking (TSN) and Time-Sensitive Communication (TSC). 5G wireless communication systems include supporting the connected industry. This 5G connectivity can serve as the foundation for the next driving force of industrial and digitalization. Within this industrial environment, terminals based on 5G connectivity will be interconnected in large numbers. These massive industrial wireless networks support not only high-demand URLLC services but also small terminals with relatively low performance, and provide battery life capable of operating for many years. The requirements for these services are higher than those of LPWA technologies such as NB-IoT or LTE-M, but lower than those of eMBB or URLLC. Similar to the aforementioned connected industry, 5G connectivity can be utilized as a foundation for next-generation smart city innovation. For example, in smart city use cases, 5G connectivity can be effectively utilized for data collection within the city and for the utilization and monitoring of urban resources. In particular, the installation of surveillance cameras can be utilized for an important / essential role not only in cities but also in industrial zones. Additionally, wearable devices, such as smartwatches, rings, and health-related devices, can be considered as a use case due to their small size. Therefore, considering the scenarios and use cases described above, the requirements from a technical perspective include relatively lower terminal cost and complexity compared to Rel-15 or Rel-16 eMBB or URLLC terminals for terminal connectivity, a terminal size with a compact form factor, and for the installation environment, FR1 (Frequency Range 1) and FR2 bands for FDD and TDD can be considered. For industrial wireless sensors, communication service availability is 99.99%, end-to-end latency is less than 100ms, reference bit rate is less than 2Mbps for all use cases (e.g., considering potentially asymmetric cases such as high uplink traffic compared to downlink traffic), terminals are assumed to be fixed, batteries must last for at least several years, and for security-related sensors, latency requirements may be considered to be less than 5-10ms. For video surveillance, an economical reference video bitrate of 2–4 Mbps, latency of less than 500 ms, and reliability of 99%–99.9% can be considered; for high-end video, a bitrate of 7.5–25 Mbps can be considered, along with traffic patterns where uplink transmission is dominant over downlink transmission. For example, video camera devices such as CCTVs are mid-to-high capability devices that are difficult to support with conventional LPWA technologies like NB-IoT and eMTC. In particular, CCTVs are experiencing high growth as a model for smart city configurations, with many companies participating in related manufacturing and paying close attention to the connectivity between these devices. For wearables, for smart wearable applications, a reference bit rate of 10-50 Mbps in the downlink and at least 5 Mbps in the uplink, and a peak bit rate of 150 Mbps in the downlink and 50 Mbps in the uplink may be considered. As such, for RC terminals or RC NR, new IoT technologies that cannot be supported by existing eMTC (or LTE-M) or NB-IoT are required. Specifically, relatively lower latency, relatively higher data rates, and reliability than eMTC or NB-IoT terminals are required, relatively lower cost and complexity and relatively longer battery life than eMBB terminals are required, and relatively wider coverage than URLLC terminals is required. Hereinafter, a random access procedure in an NR system related to the present disclosure will be described. FIG. 3 is a diagram illustrating an NR random access procedure to which the present disclosure may be applied. Random access procedures can be used for a terminal to obtain uplink (UL) synchronization with a base station or to be allocated UL resources. A contention-based (CB) random access procedure may include a first step in which a terminal transmits a random access preamble (or Msg1) to a base station, a second step in which the terminal receives a random access response (RAR) (or Msg2) from the base station, a third step in which the terminal transmits a layer 2 / layer 3 (L2 / L3) message (or Msg3) to the base station, and a fourth step in which the terminal receives a contention resolution message (or Msg4) from the base station. Additionally, a contention-based random access procedure using only two steps may also be included. The two-step contention-based random access procedure may include a step A in which the terminal transmits a random access preamble and a random access-related message over an uplink channel to the base station, and a step B in which the terminal receives a random access response and a contention resolution message, etc., from the base station. A non-contention (Contention-Free, CF) random access procedure may include only the first and second steps of the CB random access procedure, and since no contention occurs between terminals, the third and fourth steps are not required. This random access procedure can be initiated by the occurrence of a trigger event and the subsequent initialization operation. Specifically, the random access procedure can be initialized by a PDCCH order, a MAC sublayer, an RRC sublayer, or a beam failure indication from the physical layer (PHY). The relationship between the specific causes that trigger random access in an NR system and the events can be shown in Table 4. Random access procedures on SCells (Secondary Cells), excluding PSCells (Primary Secondary Cells), are initialized solely by the PDCCH order, and the random access preamble index value may be indicated by the PDCCH order. Here, PSCell refers to the PCell (Primary Cell) in the MCG (Master Cell Group) or SCG (Secondary Cell Group) in the case of dual connectivity. Additionally, information related to random access settings may be provided to terminals through RRC signaling. For example, one or more of the information related to random access settings may be provided to terminals through system information block 1 (SIB1). For example, SIB1 may include information elements (IE) such as ServingCellConfigCommonSIB, ServingCellConfigCommonSIB may include IE such as UplinkConfigCommonSIB, UplinkConfigCommonSIB may include IE such as initialUplinkBWP (or BWP-UplinkCommon), BWP-UplinkCommon may include IE such as RACH-ConfigCommon, and RACH-ConfigCommon may include information related to random access settings. Specifically, the following information may be provided to terminals as information related to random access settings: -Prach-ConfigIndex: An available set of PRACH resources (e.g., PRACH occasions) for the transmission of a random access preamble; -PreambleReceivedTargetPower: Initial random access preamble power; -rsrp-ThresholdSSB: RSRP threshold for SSB selection; -rsrp-ThresholdCSI-RS: RSRP threshold for CSI-RS selection; -rsrp-ThresholdSSB-SUL: RSRP threshold for selection between NUL (Normal Uplink) carrier and SUL (Supplementary Uplink) carrier; -powerRampingStep: power-ramping factor; -ra-PreambleIndex: Random access preamble index; -preambleTransMax: Maximum number of preamble transfers; -ra-ResponseWindow: Size of the time window for monitoring RAR (instructed to the terminal as the number of slots); - Set of random access preambles for SI (System Information) requests and / or the corresponding PRACH resources (if necessary) - ra-ContentionResolutionTimer: Contention Resolution Timer; -groupBconfigured: Whether to configure Random Access Preamble Group B; -numberOfRA-PreamblesGroupA: The number of random access preambles in random access preamble group A. If preamble group B is established, the remaining preambles, excluding numberOfRA-PreamblesGroupA, belong to group B. In this regard, depending on whether a mapping relationship between each SSB (or CSI-RS) and preamble transmission resources and indices is pre-established, a group of preamble indices and the indices within that group may be sequentially assigned to each SSB (or CSI-RS). The preamble group may be used by the base station to estimate the size of the UL resource required for Msg3 transmission. That is, if preamble group B is set for the terminal, the size of the Msg3 that the terminal intends to transmit is larger than a predetermined Msg3 threshold size (e.g., a value determined by the ra-Msg3SizeGroupA parameter, which is the size of the UL data information including the MAC header and MAC CEs), and the path loss value is smaller than the “PCMAX-preambleReceivedTargetPower-msg3-DeltaPreamble-messagePowerOffsetGroupB” of the serving cell performing random access, the terminal may select a preamble index within group B and transmit the preamble. If the base station determines that a preamble belonging to group B has been received, it may schedule the terminal by including information on the size of the UL resource required for transmitting Msg3 within Msg2, which is the response information for the preamble. That is, a 1-bit instruction for the size of Msg3 (i.e., L2 / L3 message) may be embedded in the random access preamble transmission. Otherwise (i.e., if the size of Msg3 that the terminal intends to transmit is less than or equal to the predetermined Msg3 threshold size, or if the path loss value is greater than or equal to “PCMAX-preambleReceivedTargetPower-msg3-DeltaPreamble-messagePowerOffsetGroupB of the serving cell), the terminal may select a preamble index within group A and perform preamble transmission.From the perspective of the base station, it can expect to receive a potential preamble on all preamble indices within the preamble group within the set RACH occasions and perform an associated preamble reception operation. When initializing the random access procedure, the terminal may flush the Msg3 buffer and set the preamble transmission counter to 1, the preamble power ramping counter to 1, and the preamble backoff to 0ms. Next, if the carrier on which the random access procedure is performed is explicitly signaled, the random access procedure may be performed on that carrier. Otherwise, if SUL is set on the cell for the random access procedure and the RSRP value of the downlink path loss (DL pathloss) of that cell is less than the value of rsrp - ThresholdSSB - SUL, then SUL is selected as the carrier for the random access procedure, and P for SUL CMAX The (terminal maximum transmission power) value can also be set. Otherwise, select the NUL carrier as the carrier for performing the random access procedure, and P for the NUL carrier CMAX You can set the value. Subsequently, the terminal can set a preamble index value through a resource selection procedure and determine the associated next available PRACH opportunity. More specifically, the PRACH opportunity is determined depending on whether an association setting exists between the SSB block index and the PRACH opportunity, or between the CSI-RS and the PRACH opportunity, or if the aforementioned association settings are not provided to the terminal. If there is an association setting between the SSB or CSI-RS and the PRACH opportunity, the associated PRACH opportunity may be determined according to the SSB or CSI-RS selected by the terminal. If there is no association setting between the SSB or CSI-RS and the PRACH opportunity, the terminal may perform a preamble transmission at the next available PRACH opportunity. After that, the terminal can perform a preamble transmission based on the selected PRACH opportunity. Specifically, the MAC can instruct the PHY to perform the selected preamble transmission by providing the selected preamble, the associated RNTI (Radio Network Temporary Identifier), the preamble index, and the receive target power. After the terminal transmits a preamble, it must monitor for the reception of the corresponding Msg2 (or RAR), and the time (window) interval for this can be defined by ra-ResponseWindow. After transmitting the preamble and a certain number of symbols later, the terminal expects the reception of the RAR and can perform PDCCH / PDSCH monitoring for the Msg2 during the time corresponding to the window interval. More specifically, RAR information may be transmitted from a base station in the form of a MAC PDU via a PDSCH, and to receive the PDSCH, the terminal may monitor the PDSCH based on the RA (Random Access)-RNTI value. That is, the PDSCH may include information about the terminal that needs to receive the PDSCH, information about the PDSCH transmission resource, and the transmission format of the PDSCH. In addition, the RAR may include a Random Access Preamble Identifier (RAPID), an Uplink Grant (UL Grant) indicating the resource for Msg3 transmission, a Temporary Cell Identifier (Temporary C(Cell)-RNTI), and a Timing Adjustment / Advance Command (TAC). If the received Msg2 contains response information (e.g., RAPID), the terminal considers it a successful RAR reception; otherwise, it may perform the aforementioned preamble resource selection again to prepare for preamble retransmission. Based on parameter information for transmitting Msg3, such as UL grant information within the received Msg2, the terminal can transmit Msg3. Once Msg3 is transmitted, the terminal starts a contention resolution timer (CR timer) and can perform PDCCH monitoring based on C(Cell)-RNTI for receiving Msg4. If Msg4 is received while the CR timer is running, the terminal can determine that contention resolution has been successfully executed. Hereinafter, embodiments of the present disclosure regarding random access procedures in an RC NR system will be described. In existing NR systems, there are general terminals with high-end UE capability for eMBB and / or URLLC services. Meanwhile, when terminals with medium-low UE capability (i.e., reduced capability / complexity (RC) terminals) are introduced for services such as industrial wireless sensors, video surveillance, and wearables, terminals with various capabilities may coexist on the NR network. For example, RC terminals may have capabilities where the number of transmit and receive antennas is limited to one each, bandwidth is reduced, they have a low transmission power class, or limited half-duplex is applied. In this case, since there are terminals with different channel environments and different capabilities within a single cell, the base station (e.g., NG-RAN) needs to quickly identify the distinct capabilities of the terminals from the initial cell connection process. This is because the cell coverage or resource allocation method established by the existing base station based on terminals that support NR eMBB, URLLC, and / or wideband (e.g., terminals with the highest capability, hereinafter referred to as "general terminals" or "Type 1 terminals") may not be suitable for new types of terminals that do not support eMBB, URLLC, and / or wideband (e.g., terminals with lower-middle capability, hereinafter referred to as "RC terminals" or "Type 2 terminals"). For example, if the base station can know the coverage level (e.g., repetition level) of an RC terminal in advance during the initial cell selection (or initial access) process, it can optimize resource utilization for transmission and reception between the various base station and terminals present during the initial access process. For example, if an RC terminal can be identified in advance during the random access process by distinguishing it from general terminals (e.g., Rel-15 and / or Rel-16 UEs (or eMBB, URLLC, and / or wideband UEs)), it is possible not only to optimize resource utilization for transmission and reception between the base station and terminals after the random access process, but also to guarantee the reception reliability and coverage of the RC terminal. As such, in order to minimize or limit performance degradation caused by the reduction of terminal complexity, a coverage recovery function is required to compensate for potential coverage reduction resulting from the reduction of terminal complexity. To this end, it is required that the network or network operator explicitly identify RC terminals, and it may be required to ensure the coexistence of general terminals and RC terminals. The present disclosure includes embodiments for random access for RC terminals. A base station may transmit an SSB based on a predetermined transmission pattern. The SSB includes a synchronization signal (SS) and a Physical Broadcast Signal (PBCH), the SS includes a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS), and the PBCH may include a DeModulation Reference Signal (DMRS) and PBCH data. After receiving the SSB and SIB1 from the base station during the initial access process, the first physical signal or physical channel that the terminal transmits over the uplink is the Random Access Preamble (or PRACH or Msg1). Based on the SSB transmitted from the base station, terminals operating in the NR system can select the optimal SSB index suitable for each channel environment (e.g., the index of the SSB with the highest SSB-RSRP). Here, unlike a standard terminal (e.g., Rel-15 and / or Rel-16 UE (or eMBB, URLLC and / or wideband UE)), an RC terminal may need to perform longer SSB monitoring or measurements. This is because, even when the reception level or reception coverage of SSB and SIB1 is the same, an RC terminal may need to receive SSB and / or SIB1 for a longer period of time compared to a standard terminal to verify the information. After verifying the SSB and SIB1 information, the RC terminal may perform a random access procedure including the transmission of a random access preamble using the selected SSB index (or, in RRC CONNECTED mode, the CSI-RS index) and the random access configuration information provided through SIB1. To provide coverage for RC terminals similar to that of general terminals, a function is required to compensate for coverage loss and reduced reception reliability caused by the reduced capacity or complexity of RC terminals. For example, since the Random Access Preamble transmission is the first signal transmitted by any terminal to a base station, in order to provide coverage compensation or stable wireless access for RC terminals, it is necessary for the base station to identify in advance whether a terminal is an RC terminal (or the existence of an RC terminal) during the initial access or random access process, and to perform data transmission specialized for that terminal. This is because, under previously defined procedures, it was difficult to explicitly verify the terminal's capacity during the initial access or random access process, and the base station could only verify the terminal's capacity by receiving signaling regarding the terminal's capacity after the initial access or random access process. Therefore, a new method is required to enable the base station to verify whether the terminal is an RC terminal through the transmission of a Random Access Preamble, which is an uplink transmission performed by the terminal to the base station. Accordingly, additional or improved measures, such as coverage compensation and optimization of resource utilization for the terminal, can be applied through uplink and downlink transmissions, such as RAR (or Msg2), L2 / L3 messages (or Msg3), and contention resolution messages (or Msg4), which are performed after the terminal's Random Access Preamble. In the embodiments of the present disclosure, as described below, a random access operation can be defined to identify an RC terminal by distinguishing it from a general terminal in terms of system information transmission, transmission carrier selection, preamble selection, and RO (RACH Occasion) setting. System Information Transmission The base station can provide system parameters that are common (or cell-specific) to both general terminals and RC terminals through a common channel (e.g., PDCCH and PDSCH) by transmitting system information (e.g., SIB1) containing information related to random access settings. For example, the base station may perform optimal SIB1 transmission independently for each of the general terminal and the RC terminal by identifying the RC terminal separately from the general terminal. That is, the SIB1 information for the RC terminal can be configured with a smaller size compared to the size of the SIB1 information for the general terminal. Along with this, or separately, the SIB1 PDCCH / PDSCH providing the same system information for the RC terminal can be repeatedly transmitted with a shorter transmission period (e.g., 20, 40, 80ms) compared to the transmission period of 160ms for the PDCCH and SIB1 for SIB1 scheduling for the general terminal (hereinafter, SIB1 PDCCH / PDSCH). Furthermore, distinguishing between general terminals and RC terminals to set separate SIB1 information and / or transmission cycles can increase signaling overhead, thereby reducing resource utilization efficiency from a cell perspective. Therefore, it is possible to transmit a common SIB1 in the same manner without distinguishing between general terminals and RC terminals. In this case, to compensate for reception coverage and reliability for RC terminals, RC terminals may be required to receive SIB1 for a longer period than general terminals. Consequently, longer delays may be expected for SIB1 reception by RC terminals compared to general terminals. Select transmission carrier The terminal can select a transmission carrier (Tx carrier) to perform random access. In the case of a general terminal, if it is a wideband terminal with additional SUL configured, select SUL or NUL depending on whether the RSRP value of the downlink path loss is less than or greater than rsrp-ThresholdSSB-SUL within the random access configuration information, and P accordingly CMAX You can set the value. In the case of an RC terminal (if the RC terminal is configured with SUL), in addition to the method of comparing the downlink path loss with the configured threshold value (i.e., selecting the SUL carrier if the RSRP value of the downlink path loss is smaller than the threshold value, and selecting the NUL carrier otherwise), the carrier for random access between SUL and NUL may be selected based on one or more of the coverage level, repeat transmission level (or repeat level), terminal type, or terminal category. For example, an RC terminal corresponding to a coverage level / repeat transmission level that is smaller than the threshold value and above a certain level (i.e., a situation requiring a high coverage level) may use the SUL carrier. Otherwise, the RC terminal may use NUL. In addition, for RC terminals, a new transmission carrier selection threshold (e.g., rsrp-ThresholdSSB-SUL-RCNR) can be set that is distinct from the transmission carrier selection threshold for general terminals (e.g., rsrp-ThresholdSSB-SUL). Alternatively, a transmission carrier selection threshold (e.g., rsrp-ThresholdSSB-SUL) may be set commonly for general terminals and RC terminals, and the RC terminal may be configured to select a transmission carrier for random access from SUL and NUL based on one or more of downlink path loss, coverage level, repeat transmission level, terminal type, or terminal category. Alternatively, if SUL is set for the RC terminal, SUL may always be selected as the transmission carrier for random access regardless of the transmission carrier selection threshold. Alternatively, for the RC terminal, one of the UL carriers (NUL or SUL) set for a single serving cell can be directly set as a carrier for random access through upper layer information. Preamble selection An RC terminal that has received information related to random access settings from a base station via system information (e.g., SIB1) can determine the values ​​of parameters for performing random access. Some of the system information (e.g., SIB1) related to random access setting information to which embodiments of the present disclosure may be applied may be configured as shown in Table 5. However, the parameters included in Table 5 are exemplary, and the random access setting information may be configured with some or all of them, and parameters not exemplified may be additionally included in the random access setting information. SIB1> ServingCellConfigCommonSIB>> UplinkConfigCommonSIB>>> initialUplinkBWP (BWP-UplinkCommon)>>>> RACH-ConfigCommon>>>>>>>> RACH-ConfigGeneric>>>>>>>>>>>> prach-ConfigurationIndex>>>>>>>>>>>> msg1-FDM>>>>>>>>>>>> msg1-FrequencyStart>>>>>>>>>>>> zeroCorrelationZoneConfig>>>>>>>>>>>> preambleReceivedTargetPower>>>>>>>>>>>> preambleTransMax>>>>>>>>>>>> powerRampingStep>>>>>>>>>>>> ra-ResponseWindow>>>>>>>> totalNumberOfRA-Preambles>>>>>>>> ssb-perRACH-OccasionAndCB-PreamblesPerSSB >>>>>>>> groupBconfigured>>>>>>>>>>>> ra-Msg3SizeGroupA>>>>>>>>>>>> messagePowerOffsetGroupB>>>>>>>>>>>> numberOfRA-PreamblesGroupA>>>>>>>> ra-ContentionResolutionTimer>>>>>>>> rsrp-ThresholdSSB>>>>>>>> rsrp-ThresholdSSB-SUL>>>>>>>> prach-RootSequenceIndex>>>>>>>> msg1-SubcarrierSpacing>>>>>>>> restrictedSetConfig>>>>>>>>msg3-transformPrecoding>>>>>>>>rsrp-ThresholdSSB-repetition>>>>>>>>groupCconfigured>>>>>>>>>>>>ra-Msg 3SizeGroupA>>>>>>>>>>>>messagePowerOffsetGroupC>>>>>>>>>>>>numberOfRA-PreamblesGroupB>>>>>>>>>>>>>offs etOfRA-PreamblesGroupC>>>>>>>>>>>>>numRepetitionPerPreamble>>>>>>>>>>>>sub-group-list>>>>>>>>>>>>>>>nu mberOfRA-PreamblesSubGroup>>>>>>>>>>>>>>>>...>>>>>>>>ssb-perRACH-OccasionAndCB-PreamblesPerSSB-RCNR... Cell-specific (or terminal-common) random access configuration information, such as the example in Table 5, may include parameters for the general terminal and parameters for the RC terminal if the same system information is shared between the general terminal and the RC terminal. For example, parameters for the RC terminal may include the number of times the random access preamble (or Msg1) is repeated (e.g., numRepetitionPerPreamble), and parameters related to a new preamble group for the RC terminal (e.g., group C) (e.g., groupCconfigured, ra-Msg3SizeGroupA, messagePowerOffsetGroupC, numberOfRA-PreamblesGroupB, sub-group-list, numberOfRA-PreamblesSubGroup, etc.). groupCconfigured: Indicates whether to configure preamble group C. ra-Msg3SizeGroupA: Threshold for Msg3 size to select preamble group C messagePowerOffsetGroupC: Offset for preamble transmission power within preamble group C numberOfRA-PreamblesGroupB: Number of preamble indices within preamble group B sub-group-list: List of subgroups within preamble group C (if necessary) numberOfRA-PreamblesSubGroup: Number of preamble indices belonging to each of the above subgroups Here, parameters regarding the number of repeated transmissions of the random access preamble and the transmission power adjustment can be used for the purpose of coverage compensation for RC terminals having low transmission capacity in terms of uplink transmission. The terminal may determine at least the number of random access preamble repeat transmissions (or repeat transmission levels) and / or transmission power offset values ​​based on the base station's signaling (e.g., system information or dedicated RRC signaling). Alternatively, if a mapping relationship between the number of preamble repeat transmissions and the preamble index / RO is defined, the terminal may select a preamble corresponding to the repeat transmission level and / or transmission power offset value based on channel information measured as follows and channel measurement thresholds set for each repeat level. Additionally, the terminal may determine the repeat level based on the settings for SSB index(s) that share the same RO(s). Alternatively, the terminal may determine the number of repeated transmissions of a random access preamble (or the number of repeated transmissions) based on channel information measured by itself (e.g., RSRP of downlink path loss), transmission power, transmission power offset, power class, terminal type, terminal category, etc., and based on a predetermined threshold value set or predefined for the terminal. Alternatively, if a mapping relationship between the number of repeated transmissions of a preamble and a preamble is defined, the terminal may select a preamble corresponding to the corresponding number of repeated transmissions. For example, when a terminal determines the number of repeated transmissions of a random access preamble (or the repetition level) based on the RSRP value of the downlink path loss, a predetermined threshold value (e.g., rsrp-ThresholdSSB-repetition) set for the terminal may be applied. If a downlink path loss RSRP value below the predetermined threshold value is measured, the terminal may repeat the random access preamble i times (or select and repeat the preamble corresponding to i repetitions). If a downlink path loss RSRP value above the predetermined threshold value is measured, the terminal may repeat the random access preamble j times (or select and repeat the preamble corresponding to j repetitions). Here, the values ​​of i (i is 1 or greater) and j (j is 1 or greater) may be set for the terminal or predefined. Also, i <j 일 수도 있다. In addition, as described above, the terminal may not only determine the number of repeated transmissions but also determine the magnitude (level) of the transmission power offset value by comparing it with the RSRP value of the downlink path loss and a predetermined threshold value as described above. Here, the repeated transmission of a random access preamble is distinguished from a preamble retransmission performed when at least the RAR is not successfully received after the preamble transmission, or when the preamble is not successfully received by the base station. That is, unlike the conventional case of performing a single preamble transmission, the repeated transmission considered in the present invention refers to the operation of multiple repeated transmissions that can be considered during a single preamble transmission. In addition to comparing the RSRP measurement value of the downlink path loss with its threshold value, the number of repeated transmissions of the random access preamble may be determined according to the terminal type (or terminal category or terminal capability (UE capability)). The terminal type (or terminal category or terminal capability (UE capability) mentioned herein may be considered to distinguish the transmission and reception capabilities of the RC terminal (e.g., maximum supported bandwidth, half-duplex mode capability, number of antennas, MIMO transmission capability, etc.), transmission power, transmission power offset, power class, etc., and it is assumed that each terminal type has different terminal characteristics and capabilities. Additionally, the RC terminal may determine a different number of preamble transmissions according to the method regarding the random access procedure (i.e., 4-stage CBRA, 2-stage CBRA, or 4-stage CFRA, 2-stage CFRA). In particular, in the case of 2-stage CBRA and 2-stage CFRA, since the preamble transmission and the uplink message (PUSCH) transmission occur together, the number of repeated transmissions can be determined independently based on the above method for the successful reception of the preamble and the uplink message. RO settings RO (RACH Occasion or PRACH Occasion) corresponds to a resource in which a terminal can perform random access preamble transmission. RO can be defined by time domain resources and frequency domain resources. The time domain resource associated with RO configuration can be referred to as a PRACH slot, and a PRACH slot may correspond to one or more time slots or multiple OFDM symbols within a single slot depending on the format of the preamble (e.g., short preamble format or long preamble format). The frequency domain resource associated with RO configuration can be defined in units of subcarrier, resource element (RE), resource block (RB), or bandwidth portion (BWP), and its size can be determined based on the length of the preamble sequence. In embodiments of the present disclosure, the ROs of the general terminal and the RC terminal may be referred to as the first RO and the second RO, respectively. For example, the first RO and the second RO may be configured to be partially overlapping or common. That is, part or all of the first RO for the general terminal may be configured as the second RO for the RC terminal, and the partially overlapping or common RO may be used for either the general terminal or the RC terminal. Alternatively, the first RO and the second RO may be configured separately. That is, a second RO distinct from the first RO for the general terminal in the time and / or frequency domain may be additionally configured to the first RO. Alternatively, the first RO may include an RO dedicated to the general terminal and a shared RO with the RC terminal, and the second RO may include an RO dedicated to the RC terminal and a shared RO with the general terminal. In addition, depending on whether the first RO and the second RO are set commonly, partially overlappingly, or separately for general terminals and RC terminals, some of the parameters included in Table 5 may be included or excluded. The first RO and the second RO for general terminals and RC terminals can be set for the terminal(s) by the base station. In setting ROs, the base station may additionally provide RO masking information for some or all of the set ROs. The masking information may indicate the availability of RO(s) corresponding to specific index(s) among the set ROs. For example, if a first RO is set for a general terminal and a second RO is set for an RC terminal, and then additional masking information is provided, the RC terminal can determine the available RO by considering the masking information. The available RO of the RC terminal may be common to, partially overlap with, or entirely distinct from the available RO of the general terminal. If no masking information is provided, the RC terminal can determine the second RO as the available RO. That is, the available RO of the general terminal and the RC terminal is basically determined according to the first and second RO settings, and if additional masking information is provided, it can be additionally applied to finally determine the available RO. In addition, whether the first and second ROs overlap can be finally determined based on masking information provided. Accordingly, in the following description, the first RO and the second RO may refer to available ROs for a general terminal and an RC terminal, respectively, to which masking information is applied if provided. For example, if the first RO and the second RO are configured to partially overlap or be common, the base station may configure the RC terminal to share a subset or the entire set of ROs used by the general terminal through masking information (e.g., rc-ssb-sharedROmaskindex). In this case, the first RO and the second RO may be configured to have an intersection. Alternatively, the first RO may be configured to include all of the second RO, or the first RO and the second RO may be configured to be the same set. Among the first RO and second RO associated with each configured SSB (or CSI-RS), the RO that the RC terminals can use for actual preamble transmission can be indicated through such masking information (or RO mask index). That is, the ROs available for use by the general terminal and the RC terminal can be distinguished or indicated independently through such parameters, and depending on the indicated information, the RO of the general terminal and the RO of the RC terminal can be freely configured to not overlap, partially overlap, or be identical. In the following, first and second ROs are considered, each of which can be distinguished and indicated through independent RO settings or the aforementioned independent RO mask settings based on the same RO settings. In this case, the first and second ROs indicated based on the mask settings can be set to be common / partially overlapping or non-overlapping as described below. In the following, embodiments of the present disclosure are described for notifying a base station whether a terminal is an RC terminal during an initial access or random access procedure of a terminal, based on system information transmission, transmission carrier selection, preamble selection, and / or RO setting as described above. Example 1 Example 1 includes a method for informing a base station whether a terminal performing random access using a preamble index group within the overlapping RO is an RC terminal when the first and second ROs are set up in common or partially overlapping. In addition, Example 1 includes a method for allocating preamble resources (e.g., preamble groups and / or indices) that are distinct for general terminals and RC terminals. For example, preamble group A and / or group B may be assigned to a general terminal, referred to as the first preamble group. Meanwhile, preamble group C may be assigned to an RC terminal, referred to as the second preamble group. That is, it is assumed that the first preamble group includes group A and the second preamble group includes group C, or that the first preamble group includes group A and group B and the second preamble group includes group C. Furthermore, the range of preamble indices assigned to each preamble group A, B, and C, or the number of preamble indices per group, may be set or predefined by the base station. Thus, the scope of the present disclosure is not limited by the name of the preamble group (i.e., group A, B, or C) or the range or number of preamble indices belonging to each group, and includes the assignment of any preamble group that is distinct from the general terminal and the RC terminal. Additionally, the scope of the present disclosure may include cases where one SSB (or one CSI-RS) is associated with one RO, cases where one SSB (or one CSI-RS) is associated with multiple ROs, and cases where multiple SSBs (or multiple CSI-RS) are associated with one RO. For clarity, the following description assumes an RO associated with an SSB, but the following embodiments may also be applied to an RO associated with a CSI-RS instead of an SSB. Example 1-1 FIG. 4 is a drawing for illustrating an embodiment of a preamble group setting to which the present disclosure may be applied. Referring to FIG. 4, there may be one or more ROs associated with a single SSB#k, and it is assumed that the one or more ROs are shared by a general terminal and an RC terminal (i.e., the first RO and the second RO are the same set). For the one or more ROs, the total number of preamble indices (or the number of preambles) per RO may be set. The total number of preambles in one RO may correspond to the sum of the number of preambles belonging to the first preamble group (i.e., group A and / or B) and the number of preambles belonging to the second preamble group. Alternatively, the total number of preambles in one RO may correspond to the number of candidate preambles available for the first and / or second preamble groups. In addition to a first preamble group for general terminals, configuration information for a second preamble group for RC terminals may be provided to the terminal(s) by the base station. For example, the base station may provide group C configuration information for RC terminals through system information (e.g., SIB1 or dedicated RRC signaling). For example, group C configuration information may include whether group C is configured (groupCconfigured). If group C is indicated to be configured, the number of group C preambles may be determined by subtracting the number of group B preambles (numberOfRa-PreambleGroupB) and the number of group A preambles (numberOfRA-PreamblesGroupA) from the total number of preambles. Alternatively, if the first preamble group includes only group A, the number of group C preambles may be determined by subtracting the number of group A preambles (numberOfRA-PreamblesGroupA) from the total number of preambles. The starting index of a preamble belonging to the second preamble group (or group C) can be determined as the next index of the ending index of a preamble belonging to the first preamble group (or groups A and / or B). As an additional example, an offset (e.g., offsetOfRA-PreamblesGroupC) may be set to indicate the starting index of a preamble belonging to the second preamble group (or group C). In this case, the starting preamble index of the second preamble group is the preamble index that is offset from the ending index of the preamble belonging to the first preamble group (or group A and / or B) by the offset value, and the preamble index from the starting preamble index to the ending index of all preambles or the number of preamble groups may belong to the second preamble group. Alternatively, the starting index of the preamble belonging to the second preamble group (or group C) may be set directly instead of the aforementioned offset. Here, the starting index of the second preamble group may be set so as not to overlap with the index belonging to the first preamble group. In this case, the number of preambles in the second preamble group can be determined by subtracting the number of preambles in the first preamble group (or group A and / or B) from the total number of preambles, and further subtracting the number from the index after the first preamble group end index to the index before the second preamble group start index. As an additional example, the second preamble group may be set to a predetermined number of preambles in descending order of preamble index from the end index of the entire preamble group. In this case, the predetermined number may be indicated by the base station (e.g., through system information). For example, the total number of available preambles in a single RO may be set to 41, and the available preamble indices may be set to 0 to 40. A first preamble group may be set to preamble indices 0 to 23. Specifically, preamble indices 0 to 16 may be set as Group A, and preamble indices 17 to 23 may be set as Group B. Additionally, a second preamble group may be set to preamble indices 32 to 40. Such preamble group settings are merely exemplary and the scope of the present disclosure is not limited thereto, and the number of preambles and index ranges belonging to each group may be set in various ways. The terminal can select a preamble group according to a predetermined criterion, and then randomly select one preamble index from within the selected preamble group. For example, a terminal may select one of the first or second preamble groups based on its type or terminal capability. Specifically, in the case of a general terminal, one preamble index from the first preamble group may be selected, and in the case of an RC terminal, one preamble index from the second preamble group may be selected. If the base station can initially identify the terminal type or terminal capability based on which preamble index received from the terminal belongs to which preamble group. For example, if the index of a random access preamble received by the base station from the terminal belongs to the second preamble group, the base station can initially identify that the terminal attempting random access is an RC terminal or an RC terminal, and what the type, repeat transmission level, coverage level, and / or terminal capability of the RC terminal is. From the perspective of the base station, such terminal type repeat transmission levels, coverage levels, and / or capability information may be considered in subsequent procedures. For example, if the base station identifies that it has received a random access preamble from an RC terminal, it may establish, apply, or consider independent or new resources, transmissions, repeat transmissions, etc., corresponding to the reduction capability of the RC terminal in subsequent procedures. For example, procedures following the reception of the random access preamble may include the exchange of Msg2, Msg3, and Msg4 during the random access procedure, or may include the establishment or processing of HARQ-ACK / NACKs transmitted from the terminal via an uplink channel (e.g., PUCCH). As an additional example, the terminal may select a preamble group based on the size of the Msg3 to be transmitted and the downlink path loss value. This example may be applied in conjunction with or separately from the preamble group selection based on the aforementioned terminal type or capability. Generally, downlink / uplink transmissions with a minimum size must be performed for RC terminals so that the system can apply coverage and reception reliability comparable to general terminals. Considering this, in relation to the random access procedure, RC terminals may have a smaller Msg3 size compared to general terminals. Therefore, a terminal may select a preamble group based on a predetermined threshold for the Msg3 size (e.g., ra-Msg3SizeGroupA). As a specific example, when groups A, B, and C are set as preamble groups by a base station, the size of Msg3 may have the relationship Group B > Group A > Group C. In this case, the terminal can select a preamble group according to conditions such as those in Table 6 based on the size of the Msg3 to be transmitted. * In the example of Table 6, when a new Msg3 size for an RC terminal is defined and a MAC-subPDU format for it is defined (i.e., when a Msg3 MAC-subPDU format smaller than the Msg3 size for a general terminal is defined), conditions for selecting a second preamble group (or group C) considering the new Msg3 size are shown. Condition 1: Terminal's Msg3 size < ra-Msg3SizeGroupA, and path loss measured by the terminal > [P CMAX ] - [preambleReceivedTargetPower] - [RC-msg3-Deltapreamble] - [messagePowerOffsetGroupC]; or - if the random access procedure was initialized for a Common Control Channel (CCCH) logical channel, and the size of the corresponding CCCH Service Data Unit (SDU) + MAC header is smaller than ra-Msg3SizeGroupA. Among the parameters in Table 6, ra-Msg3SizeGroupA represents the Msg3 size associated with preambles belonging to group A. P CMAXrepresents the maximum transmit power value of the terminal. preambleReceivedTargetPower represents the target receive power at which the base station wants to receive the preamble. RC-msg3-Deltapreamble represents the difference value for the preamble transmit power for the RC terminal (e.g., the difference from preambleReceivedTargetPower). messagePowerOffsetGroupC represents the power offset value of Msg3 associated with the preamble belonging to group C. If the Msg3 power control value associated with the preamble belonging to group C can be set independently (i.e., by a new independent parameter), the RC-msg3-Deltapreamble and messagePowerOffsetGroupC can be replaced by a single parameter. For example, a second preamble group (e.g., group C) may be selected if the size of the Msg3 that the terminal intends to transmit is smaller than or less than ra-Msg3SizeGroupA and the path loss measured by the terminal satisfies the requirements specified in condition 1, or if the sum of the size of the CCCH SDU and the size of the MAC header that the terminal intends to transmit is smaller than ra-Msg3SizeGroupA. Meanwhile, if group B is set and the Msg3 size is greater than ra-Msg3SizeGroupA, group B may be selected. Alternatively, even if group B is not set, one of the first preamble group (e.g., group A) or the second preamble group (e.g., group C) may be selected according to conditions such as those in Table 6. Examples 1-2 FIG. 5 is a drawing for illustrating an additional embodiment of a preamble group setting to which the present disclosure may be applied. Referring to FIG. 5, when the first RO and the second RO are shared similarly to the example in FIG. 4, a first preamble group (i.e., group A and / or B) may be set for one RO associated with one SSB, and a second preamble group (i.e., group C) may be set. Although group C is set similarly to the example in FIG. 4, the number and range of preambles may be different; in the example in FIG. 5, group C may be set to 25 preambles with preamble indices 32 to 56. Specifically, in the example of FIG. 5, the number of available preamble indices within a single RO associated with SSB#k is set to a total of 57, and the range of available preamble indices can be set from 0 to 56. The first preamble group can be set to preamble indices 0 to 23. Specifically, preamble indices 0 to 16 can be set as Group A, and preamble indices 17 to 23 can be set as Group B. Additionally, the second preamble group can be set to preamble indices 32 to 56. Such preamble group settings are merely exemplary and the scope of the present disclosure is not limited thereto, and the number of preambles and index ranges belonging to each group can be set in various ways. In the example of FIG. 5, the second preamble group may include up to M subgroups (where M is an integer greater than or equal to 1). The subgroups may be set by parameters such as numRepetitionPerPreamble, sub-group-list, and numberOfRA-PreamblesSubGroup in Table 5. As a specific example, the number of preamble repeat transmissions (or repeat levels or coverage levels) may be set to a maximum of M times (e.g., M=3). That is, repeat levels 1, 2, and 3 may be set, and the number of preambles belonging to the preamble subgroups corresponding to each repeat level may be set. For example, as shown in the example of FIG. 5, repetition level 1 can be mapped to a first subgroup (e.g., preamble indices 32 to 40), repetition level 2 to a second subgroup (e.g., preamble indices 41 to 48), and repetition level 3 to a third subgroup (e.g., preamble indices 49 to 56). In this way, a group of preamble indices corresponding to a value M of the number of repetition transmissions (or repetition level or coverage level) of one or more repetition transmissions can be defined. If a general terminal and an RC terminal share the same RO, the remaining preamble indices can be divided into one or more subgroups, excluding the preamble indices corresponding to the first preamble group (e.g., Group A and / or B) set for the general terminals. Each subgroup may have a one-to-one mapping relationship with a different preamble repetition level. The number of subgroups can be set by the base station. All preambles within the second preamble group (e.g., Group C) containing all subgroups are set by the base station for the RC terminal, and if a preamble transmission by a terminal using the corresponding preamble resource or index is received by the base station, the base station may identify in advance that it is a random access operation by the RC terminal and prepare the subsequent Msg2, Msg3, Msg4 exchange procedure. FIG. 6 is a drawing for illustrating additional embodiments of preamble group settings to which the present disclosure may be applied. In the example of FIG. 6, a first preamble group is set up similarly to the example of FIG. 5, but unlike the example of FIG. 5, one or more preamble groups for the RC terminal may be set up. Additionally, each of the one or more preamble groups for the RC terminal may correspond to one repetition level (or coverage level). That is, as in the example of FIG. 5, one or more subgroups corresponding to the repetition level are not set within the second preamble group, but in the example of FIG. 6, one or more preamble groups corresponding to the repetition level (e.g., second, third, fourth, ... preamble groups, or groups C, D, E, ...) may be set for the RC terminal. In this way, the base station may configure the terminal to perform independent preamble repeat transmissions based on its capacity (e.g., repeat level) and / or measurements of downlink path loss. Accordingly, the terminal may select a preamble group (or subgroup) corresponding to the repeat transmissions configured / determined based on its capacity and / or measurements of downlink path loss, and select one preamble within the selected preamble group (or subgroup) to transmit to the base station. In this case, the base station may roughly determine the capacity of the terminal by checking which preamble group (or subgroup) the preamble index received from the terminal belongs to (i.e., which repeat level the terminal supports). Accordingly, the base station may perform a random access procedure including subsequent Msg2, Msg3, and Msg4 exchanges, taking into account the capacity of the terminal (particularly an RC terminal). As described above, when the number of preamble repeat transmissions (or repeat level or coverage level) is set, the terminal can select a preamble group in consideration of this. For example, the terminal can select a preamble group according to conditions such as those in Table 7 based on the size of the Msg3 to be transmitted. Condition 2: Terminal's Msg3 size < ra-Msg3SizeGroupA, and path loss measured by the terminal > [P CMAX ] - [preambleReceivedTargetPower'] - [RC-msg3-Deltapreamble'] - [messagePowerOffsetGroupC']; or - if the random access procedure was initialized for a CCCH logical channel and the size of the corresponding CCCH SDU + MAC header is smaller than ra-Msg3SizeGroupA. Among the parameters in Table 7, at least one parameter value among [preambleReceivedTargetPower'], [RC-msg3-Deltapreamble'], and [messagePowerOffsetGroupC'] may be determined according to the preamble repeat transmission level or the MSG3 repeat transmission level (set by the terminal or determined by the terminal). That is, in the example of Table 6, the parameters [preambleReceivedTargetPower], [RC-msg3-Deltapreamble], and [messagePowerOffsetGroupC] are given by the base station regardless of the preamble repeat transmission level or the Msg3 repeat transmission level, but in the example of Table 7, one or more of [preambleReceivedTargetPower'], [RC-msg3-Deltapreamble'], and [messagePowerOffsetGroupC'] may be set by the base station or determined by the terminal based on the preamble repeat transmission level or the Msg3 repeat transmission level. For example, if the size of the Msg3 that the terminal intends to transmit is smaller than or less than ra-Msg3SizeGroupA and the path loss measured by the terminal satisfies the requirements specified in Condition 2 (i.e., the requirement that the repetition level is additionally considered compared to Condition 1), or if the sum of the size of the CCCH SDU and the size of the MAC header that the terminal intends to transmit is smaller than ra-Msg3SizeGroupA, then the second preamble group (or the second, third, fourth, ... preamble groups, or one of groups C, D, E, ...) may be selected. Meanwhile, if group B is set and the Msg3 size is greater than ra-Msg3SizeGroupA, group B may be selected. Alternatively, even if group B is not set, a first preamble group (e.g., group A) or a second preamble group (e.g., group C, or the second, third, fourth, ... preamble groups, or one of groups C, D, E, ...) may be selected according to conditions such as those in Table 6. In this way, the base station can set the number of repeated transmissions (or repetition levels) for the transmission of a random access preamble by an RC terminal through system information (e.g., SIB1 or dedicated RRC signaling). Accordingly, the terminal can repeatedly transmit one selected preamble within a second preamble group (specifically, within a specific subgroup mapped to a repetition level within the second preamble group, or in one of the second, third, fourth, ... preamble groups, or groups C, D, E, ...) according to the number of repeated transmissions (or repetition levels) set through the system information, and the uplink coverage loss can be compensated accordingly. In this way, the base station can identify whether a random access attempt has been made by an RC terminal based on a specific preamble group and / or preamble index transmitted by the terminal. If it is identified that a random access preamble transmission has been made from an RC terminal, the base station may set a reduced message size, whether to apply repeated transmission, etc., suitable for the RC terminal in the subsequent RAR (or Msg2) transmission, and perform downlink transmission to the RC terminal based on this. Examples 1-3 Unlike the aforementioned embodiments assuming a case where one or more ROs associated with a single SSB are shared by a general terminal and an RC terminal, in this embodiment, there may be multiple ROs associated with a single SSB, said multiple ROs are configured for the general terminal, and some of said multiple ROs may be configured for the RC terminal. To this end, it is necessary to establish the relationship between the SSB and the RO. Specifically, a configuration for the SSB-to-RO association is required for the repeated transmission of the preamble of the RC terminal. In this regard, the configuration of the initial active bandwidth part (BWP) and the configuration of the RO for the RC terminal (i.e., the second RO) will be explained. System information provided by the base station (e.g., SIB1 or dedicated RRC signaling) may include information instructing that repetitive transmission be applied to the preamble transmission of the RC terminal. Alternatively, the preamble repetitive transmission level of the terminal may be implicitly indicated based on other information provided by the base station or other system information (e.g., preamble group and / or index, preamble transmission power offset, etc.). Furthermore, for the terminal to perform repeated preamble transmission, it is necessary to redefine the SSB-to-RO association. This is because repeated preamble transmission is not supported in the random access procedure for general terminals. Therefore, to support repeated preamble transmission in a single Msg1 transmission step (i.e., to distinguish it from the retransmission of the preamble performed when the RAR is not successfully received after the preamble transmission), a new method for RO configuration and selection is required. Preamble indices or preamble index groups corresponding to a specific number of repeated transmissions within a second preamble group for an RC terminal according to the present disclosure may be set by a base station, and the base station may also set which preamble index or preamble index group to use for the RC terminal. Alternatively, among the indices and / or preamble index groups corresponding to the number of repeated transmissions set by the base station, the terminal may select the preamble index and / or preamble index group corresponding to a specific number of repeated transmissions based on the terminal's channel environment (e.g., path loss measurement, CSI, HARQ-ACK, SSB / CSI-RS based RSRP / RSRQ, etc.) and / or terminal capability / category / type. In the following description, it is assumed that for an RC terminal, a correspondence relationship between a preamble index (or preamble group) associated with one or more ROs and a repeat level (or number of repeat transmissions) is provided in advance. This correspondence relationship may be provided by a base station, or it may be given as a predetermined rule without signaling from the base station. Additionally, based on this correspondence relationship, an RO and / or preamble (or preamble group) corresponding to the repeat level determined by the terminal can be selected. Accordingly, when a base station receives a random access preamble from a terminal, it may determine the repeat level of the terminal based on one or more of the index of the preamble, the preamble group to which the preamble belongs, or the RO to which the preamble was received. For example, the preamble repeat transmission method according to the present disclosure performs a final preamble repeat transmission through a combination of one or more preamble indices selected by the methods described above and one or more selected ROs mentioned below. For example, if only one RO is configured / determined to be selected by the terminal, multiple preamble transmissions may be performed by selecting one or more preamble indices within a preamble group (second preamble group) within the corresponding RO for the preamble repeat transmission of the RC terminal. As another example, it is assumed that a preamble for the RC terminal can be selected and repeated transmission performed for each selected RO through multiple ROs selected by considering one or more FDM, TDM, or a combination of FDM and TDM. In this case, the values ​​of preamble indices within multiple ROs associated with a single preamble repeat transmission of the RC terminal may be selected to be the same or different from each other by a predetermined rule or additional base station signaling. That is, the selection of preamble indices and ROs associated with a single preamble repeat transmission can be determined according to predetermined rules (e.g., consecutive or rule-based preamble indices and consecutive ROs in the time / frequency domain associated with a single SSB) or base station upper layer signaling. By doing so, the base station receiver can easily identify the association of a single preamble repeat transmission by a single RC terminal, thereby clearly identifying information obtained through the reception of the correct preamble, such as the RAPID (Random Access Preamble ID) value included in the subsequent RAR transmission. In particular, the aforementioned details regarding ROs must be assumed identically in the subsequent method for selecting ROs. FIG. 7 is a drawing for illustrating an example of an initial active bandwidth portion (BWP) setting to which the present disclosure may be applied. RO can be defined on a specific resource. For example, the aforementioned specific resource can be defined as a BWP, which can be called an Initial Active BWP. Specifically, the aforementioned specific resource can be referred to as an Initial Active Uplink (IAU) BWP. If the terminal subsequently enters RRC CONNECTED mode, BWP settings for the RC terminal can be provided via dedicated RRC signaling. The BWP settings for the RRC CONNECTED mode RC terminal may differ from the IAU BWP set during initial access. Basically, it is assumed that the RO is defined on the configured BWP regardless of whether the RC terminal is in RRC connection mode or not. First, prior to RO settings, the IAU BWP settings considered during initial cell connection are explained. On the other hand, while the BWP that can be configured during RRC connection mode may have different settings (e.g., bandwidth, numerology, etc.) than the IAU BWP, it can be assumed that ROs are defined within the configured BWP as mentioned above. Referring to FIG. 7, an IAU BWP (i.e., a first IAU BWP) for general terminals (or broadband NR UEs) can be configured (IAU BWP for FIG. 7). Additionally, an IAU BWP (i.e., a second IAU BWP) for RC terminals can be configured. The first and second IAU BWPs can be configured independently through system information (e.g., SIB1 or dedicated RRC signaling). In the case of RRC CONNECTED mode, a second IAU BWP for performing random access of RC terminals can be configured independently through dedicated RRC signaling. For example, the second IAU BWP may be set as a part of the first IAU BWP. Or, a part of the second IAU BWP may be set to overlap with a part of the first IAU BWP. Or, the first IAU BWP and the second IAU BWP may be set not to overlap. Or, the first IAU BWP and the second IAU BWP may be set to be identical (or completely overlapped). In addition, setting parameters for the first IAU BWP and setting parameters for the second IAU BWP may be defined separately in the system information. Alternatively, common setting parameters may be defined for the first and second IAU BWPs in the system information. If setting parameters for the second IAU BWP are not defined separately, the setting parameters for the first IAU BWP may be applied as setting parameters for the second IAU BWP. FIG. 8 is a drawing for illustrating an embodiment of an RO setting to which the present disclosure may be applied. The RO setting parameter (the first RO setting parameter) may indicate the number of ROs associated with a single SSB. The first RO setting parameter may be provided from the base station to the terminal through system information (e.g., SIB1). For example, the first RO setting parameter may be the ssb-perRACH-OccasionAndCB-PreamblesPerSSB parameter of Table 5, through which the number of SSBs per RO and the number of CBRA (Contention-Based Random Access) preambles per SSB may be indicated. Additionally, a new RO setting parameter (second RO setting parameter) for the RC terminal can be defined. This second RO setting parameter for the RC terminal can be provided to the terminal from the base station through system information (e.g., SIB1). For example, the second RO setting parameter may be referred to as ssb-perRACH-OccasionAndCB-PreamblesPerSSB-RCNR. Unlike general terminals, RC terminals need to support the repeated transmission of random access preambles to provide additional compensation for coverage loss. Additionally, the repeated transmission of preambles needs to be performed for each associated SSB. Accordingly, the RC terminal may consider a specific RO indicated by the second RO setting parameter (e.g., ssb-perRACH-OccasionAndCB-PreamblesPerSSB-RCNR) as an RO for the preamble transmission of the RC terminal, within the number of ROs associated with the SSB indicated by the first RO setting parameter (e.g., ssb-perRACH-OccasionAndCB-PreamblesPerSSB). That is, the RC terminal may select one or more ROs corresponding to a part of one or more sets of ROs shared with the general terminal. Referring to FIG. 8, the terminal may select one SSB from among a plurality of SSBs (e.g., SSB1, SSB2, SSB3, ...) for which the best SSB-RSRP value is measured, for subsequent associated RO selection. The terminal may select one or more ROs to use for random access preamble repeat transmission from among the ROs associated with the selected SSB index. The method of selecting the one or more ROs associated with a single preamble repeat transmission is based on a predetermined rule (e.g., consecutive ROs in the time / frequency domain or a predetermined RO pattern) or an RO set by base station signaling, as mentioned above. Here, RO can be defined by time domain resources (e.g., PRACH slots) and frequency domain resources (e.g., subcarrier, RE, RB, or BWP). Additionally, multiple ROs can be distinguished by time division multiplexing (TDM) and / or frequency division multiplexing (FDM) methods. That is, multiple ROs on the same frequency domain resource may be distinguished by different time domain resources, and multiple ROs on the same time domain resource may be distinguished by different frequency domain resources. In the example of FIG. 8, prach_FDM may represent the number of frequency domain resources that distinguish ROs on the same time domain resource. For example, prach_FDM=4 may mean that 4 distinct ROs are set on the same single time domain resource (or PRACH slot). Additionally, ssb_per_RO can represent the association between an SSB and an RO. Here, the value of ssb_per_RO can be expressed in the form x / y. If x is 1 and y is 1, 2, 4, 8, ..., it may mean that for one SSB, 1 RO, 2 ROs, 4 ROs, 8 ROs, ... are associated. If y is 1 and x is 1, 2, 4, 8, ..., it may mean that for one RO, 1 SSB, 2 SSBs, 4 SSBs, 8 SSBs, ... are associated. That is, if x / y is an integer greater than 1, it may mean that the number of available preambles (up to 64) from one RO are distributed and associated with one or more SSBs. In the example of Fig. 8, ssb_per_RO=1 / 8 may mean that 8 distinct ROs are set for one SSB. The location of the RO(s) configured in this way in the time-frequency domain can be provided to the terminal through system information (e.g., PRACH configuration information within SIB1). Accordingly, the terminal can identify all locations in the time-frequency domain of the ROs associated with the SSB it has selected. For example, the eight ROs associated with SSB#2 may include four ROs corresponding to the first to fourth frequency resources in the first time resource, and four additional ROs corresponding to the first to fourth frequency resources in the second time resource. In the example of FIG. 8, it is assumed that the terminal selects SSB#2. Additionally, each SSB is mapped to two time domain RO resources (or PRACH slots), and since the prach_FDM value is 4, four distinct RO resources are set on one time domain RO resource; consequently, eight distinct RO resources can be set for one SSB. This RO setting information can be verified by the terminal through system information from the base station. In the case of a general terminal (or wideband UE), one RO can be randomly selected from among the ROs associated with SSB#2 to attempt preamble transmission. FIG. 8 exemplarily shows a general terminal selecting one RO on the first time resource and the third frequency resource from among the eight ROs associated with SSB#2. In the case of an RC terminal, one or more ROs can be selected according to the repetition level to support preamble repeat transmission. For example, among the ROs associated with SSB#2, one RO can be selected when the repetition level is 1, and two ROs can be selected when the repetition level is 2. In the example of FIG. 8, the RC terminal can determine the repetition level through system information or other system parameters, and can select the corresponding RO(s) according to the determined repetition level (or the number of repeat transmissions). Here, when the RC terminal selects one or more ROs for repetitive transmission, it may randomly select one or more ROs from among the available ROs. Alternatively, the RC terminal may select one or more ROs from among the available ROs based on a predetermined pattern. Alternatively, the RC terminal may select one or more ROs from among the available ROs in order of lowest (or highest) time domain resource index and / or frequency domain resource index. Here, the available ROs may correspond to a part of the set of one or more ROs shared by the RC terminal and the general terminal, indicated by system information as described above. In FIG. 8, the repetition level for the RC terminal can be set to 2. In this case, among the 8 ROs associated with SSB#2, the RC terminal can select one RO on the first time resource and first frequency and another RO on the second time resource and first frequency resource. The RC terminal can transmit the same preamble repeatedly on the two selected ROs. The RO selection of the RC terminal in FIG. 8 is exemplary and the scope of the present disclosure is not limited thereto. For example, the repeated transmission of a random access preamble may include transmitting the preamble on a plurality of ROs distinguished in the time domain. Additionally, the repeated transmission of a random access preamble may include transmitting the preamble on a plurality of ROs distinguished in the frequency domain. The repeated transmission of a random access preamble may include transmitting the preamble on a plurality of ROs distinguished in the time and / or frequency domains. Example 2 Example 2 includes a method for notifying the base station whether a terminal performing random access is an RC terminal when the first and second ROs are set separately. The aforementioned Example 1 pertains to a case where common or partially redundant random access-related settings are applied to a general terminal and an RC terminal. In this embodiment, a method for transmitting a random access preamble is described in the case where a first RO for a general terminal and a second RO for an RC terminal are configured separately (i.e., separately) based on independent random access-related settings for a general terminal and an RC terminal. FIG. 9 is a drawing for illustrating additional embodiments of RO settings to which the present disclosure may be applied. FIG. 9 illustrates an exemplary case where a first RO for a general terminal and a second RO for an RC terminal are set separately. In this case, an independent RO can be set for the RC terminal. Accordingly, except for the independent RO set for the RC terminal, the RC terminal can perform preamble transmission (in particular, preamble repetition transmission) on the RO as described in Example 1. Here, an independent RO setting for an RC terminal may include allocating or setting some RO(s) for the RC terminal and allocating or setting the remaining RO(s) for the general terminal within the entire RO set commonly for the general terminal and the RC terminal (or without distinguishing between the general terminal and the RC terminal) through system information. Alternatively, the setting for the first RO for the general terminal and the setting for the second RO for the RC terminal may be set individually through separate system information parameters. Additionally, through RO mask signaling (e.g., rc-ssb-sharedROmaskindex), available ROs for the general terminal and the RC terminal, respectively, may be indicated or set among the entire RO set commonly for the general terminal and the RC terminal (or without distinguishing between the general terminal and the RC terminal). In the example of FIG. 9, two first ROs associated with SSB#2 are configured for a general terminal (or wideband UE), and separately, two second ROs associated with SSB#2 may be configured for an RC terminal. The two first ROs and the two second ROs may be distinguished in terms of time resources and / or frequency resources. The above RO settings are merely examples, and the scope of the present disclosure is not limited to a specific RO setting method and may include all cases where the RO for a general terminal and an RC terminal is set in any manner. That is, assuming that separate ROs are set for a general terminal and an RC terminal by various RO setting methods included or not included in the present disclosure, the preamble transmission method described below may be applied. In addition, in Example 1, since a common RO is set for some or all of the general terminal and the RC terminal, a new preamble group (e.g., a second (, third, fourth, ...) preamble group, or group C (, D, E, ...)) needs to be defined to distinguish between the general terminal and the RC terminal. In contrast, in the present embodiment, since a first RO for the general terminal and a second RO for the RC terminal are set separately, a new preamble group to distinguish between the general terminal and the RC terminal may not be defined. In this embodiment, a method for selecting a preamble index group and / or RO based on the repetition level (or the number of repetition transmissions / level or coverage level) is described without defining a new preamble group. When separate ROs are configured for general terminals and RC terminals, different preamble formats may be configured for each. For example, an RC terminal may not support all of the preamble formats configured for a general terminal, but may support only some of them. For example, if a first preamble type (e.g., short preamble type) and a second preamble type (e.g., long preamble type) are supported for a general terminal, an RC terminal may support only a specific preamble format (e.g., second preamble type) among the first and second preamble types. Alternatively, if a preamble format index (e.g., preamble format #0, #1, #2, #3, A1, A2, A3, B1, B2, B3, B4, C0, C2, etc.) is supported for a general terminal, an RC terminal may support only a specific preamble format index (e.g., preamble format #0, #1, #2, #3). The limitations on the preamble type or format for such an RC terminal are merely exemplary, and the preamble type and / or format available to the RC terminal may be configured according to the settings by the base station or in a predefined manner. Next, a random access configuration table may be used to configure separate ROs for general terminals and RC terminals. The random access configuration table may refer to a set of configuration parameters (e.g., preamble format, period, subframe number, start symbol, number of PRACH slots, number of time domain ROs within PRACH slots, PRACH duration, etc.) that are predefined for each random access configuration index (e.g., PRACH configuration index). When an entire RO is configured that applies commonly to general terminals and RC terminals (or without distinguishing between general terminals and RC terminals), terminals of each type may share the configured entire RO. Additionally, some RO(s) of the entire RO may be configured for RC terminals (or exclusively for general terminals). In this case, general terminals and RC terminals may use the same random access configuration table. For example, the same prach-ConfigurationIndex value may indicate the same set of random access parameters to general terminals and RC terminals. When the settings for the first RO for a general terminal and the settings for the second RO for an RC terminal are individually configured through separate system information parameters, each type of terminal may use an independent random access-related configuration table. For example, the same prach-ConfigurationIndex value may indicate different sets of random access parameters to the general terminal and the RC terminal. On the other hand, even if the first RO and the second RO are configured individually, if a separate random access-related configuration table for the RC terminal is not defined, the RC terminal may also use the random access-related configuration table for the general terminal. For example, the same prach-ConfigurationIndex value may indicate the same set of random access parameters to the general terminal and the RC terminal. In addition, when separate ROs are configured for a general terminal and an RC terminal, the first RO for the general terminal and the second RO for the RC terminal may be distinguished in terms of time resources and / or frequency resources. Here, FDM-related settings may be provided by the base station for the first RO and the second RO. That is, even within the same time resource, the first and second ROs may be distinguished (i.e., FDM) in terms of frequency resources. For the FDM settings of the first and second ROs, for example, the base station may independently configure the msg1-FDM and msg1-FrequencyStart parameters of Table 5 for the general terminal and the RC terminal. If independent FDM-related parameters for the RC terminal are not provided, the RC terminal may use the FDM-related parameters for the general terminal. Additionally, the first RO for a general terminal and the second RO for an RC terminal may be distinguished in terms of time and / or frequency. Here, the first and second ROs may be selected from each available RO (or RO candidate or RO pool). That is, in this embodiment, the RO selected by the general terminal and the RO selected by the RC terminal are distinguished, but the range in which the general terminal can select an RO and the range in which the RC terminal can select an RO may partially or entirely overlap. In this case, if the respective RO candidates for the general terminal and the RC terminal overlap in terms of time resources and frequency, it may be assumed that both the general terminal and the RC terminal are invalid for the RO candidate (i.e., the RO candidate is not selected as either the first RO or the second RO). Alternatively, it may be assumed that the RC terminal is invalid for the RO candidate, while the general terminal is valid (i.e., the RO candidate can be selected as the first RO but not as the second RO). Alternatively, it may be assumed that the general terminal is invalid for the RO candidate, while the RC terminal is valid (i.e., the RO candidate is not selected as the first RO but can be selected as the second RO). Alternatively, the selection of the RO candidate may be determined by the terminal's own settings. In addition, when separate ROs are set for a general terminal and an RC terminal, the SCS values ​​for the preamble transmission of the general terminal and the RC terminal may be set independently. For example, a first SCS value may be set for the preamble transmission of the general terminal, and a second SCS value may be set for the preamble transmission of the RC terminal, respectively, or predefined. For example, in the case of the RC terminal, it is necessary to secure more ROs within the same time for repeated preamble transmission, and to this end, a higher SCS value may be set for the RC terminal compared to the general terminal. In addition, when separate ROs are configured for general terminals and RC terminals, the number of SSBs per RO and the number of CBRA preambles per SSB can be configured independently for general terminals and RC terminals. For example, the ssb-perRACH-OccasionAndCBPreamblesPerSSB parameter of Table 5 may be applied to general terminals, and the ssb-perRACH-OccasionAndCB-PreamblesPerSSB-RCNR parameter of Table 5 may be applied to RC terminals. In the embodiments described below, when separate ROs are set for a general terminal and an RC terminal, a preamble for one type of terminal may be set in one RO. That is, only a preamble for a general terminal may be set in the first RO, and only a preamble for an RC terminal may be set in the second RO. Additionally, if one or more repetition levels are applied in the second RO for the RC terminal, the preamble group for the general terminal (e.g., group A and / or B) may not be used in the second RO. For example, in the second RO for the RC terminal, the first preamble group for the general terminal is not defined, and only the second ( , 3, 4, ...) preamble group (or group C ( , D, E, ...)) for the RC terminal may be defined. That is, if the repetition level is set to 1, only the second preamble group (or group C) may be defined in the second RO. If the repetition level is set to 2 or more, the second, 3, ... (or group C, D, ...) may be set in the second RO. However, such preamble group index does not limit the scope of the present disclosure, and a plurality of preamble groups within the second RO may be referred to as the first, second, third, ... preamble groups (or groups A, B, C, ...) (independently of the preamble groups within the first RO for the general terminal). Example 2-1 FIG. 10 is a drawing for illustrating additional embodiments of preamble group settings to which the present disclosure may be applied. FIG. 10 illustrates, by way of example, a preamble setting within a single RO (e.g., a second RO) corresponding to a single SSB for an RC terminal. For example, a total of 48 preambles ranging from preamble index 0 to 47 may be set within a single RO. Among these, four different preamble groups may be set according to four repetition levels (or coverage levels) associated with a single SSB set by the system. The number of preambles belonging to each preamble group may be the same or different. Additionally, a set of actual available preamble indices may be set for each preamble group. For example, a first preamble group (or group A) within a single RO associated with SSB#k corresponds to iteration level #1, and group A may include 17 preamble indices, with total preamble indices 0 through 15. Here, the number of actually available preamble indices among the total 16 preamble indices may be set to have a value less than 16. Similarly, for the second, third, and fourth preamble groups (or groups B, C, D), the number or set of actually available preamble indices may be set within the range of total preamble indices for each group. Accordingly, for each RO associated with each SSB, the number of preamble groups associated with one RO and the number of preamble indices set for each preamble group can be set, and among the total number of preamble indices set for each preamble group, the number or set of preamble indices set to be actually available can be optionally set. In the example of FIG. 10, it is assumed that the terminal has selected SSB#k based on the optimal SSB-RSRP. For each of one or more ROs associated with SSB#k, four preamble groups corresponding to four repetition levels (or coverage levels) may be established. The terminal determines a repetition level according to its capacity and may select a preamble from one preamble group corresponding to the determined repetition level (or from a range of available preamble indices within one preamble group). The selected preamble may be transmitted repeatedly according to the repetition level. For example, if the terminal determines the repetition level #2, it may select a second preamble group (or group B) and select one preamble index from among all preamble indices 16 to 22 within group B (or from the number or set of preamble indices available among preamble indices 16 to 22). The terminal may transmit the preamble corresponding to the selected preamble index twice. Accordingly, the base station can determine the repetition level (or coverage level) of the terminal from the fact that a preamble belonging to the second preamble group (or group B) has been received at the corresponding RO. Example 2-2 FIG. 11 is a drawing for illustrating additional embodiments of preamble group settings to which the present disclosure may be applied. One RO is associated with one or more SSBs, and a preamble group corresponding to one or more iteration levels can be established in the RO corresponding to one SSB. The example in FIG. 11 illustrates a case where two SSBs (i.e., SSB#k and SSB#k+1) are associated with one RO. In this case, the entire set of preamble indices corresponding to one RO can be distinguished into parts corresponding to each SSB. Among the entire set of preamble indices 0 to 63 corresponding to one RO, preamble indices in the range of 0 to 23 may correspond to SSB#k, and preamble indices in the range of 32 to 55 may correspond to SSB#k+1. Additionally, within the preamble index portion corresponding to each SSB, one or more preamble groups may be set according to the repetition level. For example, among the preamble index portions (0 to 23) corresponding to SSB#k, preamble groups A, B, C, and D corresponding to repetition levels #1, #2, #3, and #4, respectively, may be set. Additionally, for example, among the preamble index portions (32 to 55) corresponding to SSB#k+1, preamble groups A, B, C, and D corresponding to repetition levels #1, #2, #3, and #4, respectively, may be set. That is, within a single RO, a number of preamble groups corresponding to the product of the number of SSBs associated with the RO and the (maximum) repetition level may be set. Alternatively, within a single RO, the preamble portion corresponding to each SSB may be set as a preamble group, and within that preamble group, a set of preamble indices corresponding to the repetition level may be set as a subgroup. Information regarding the number of start indices, end indices, and / or preamble indices for each preamble group (or subgroup) within a single RO can be provided to the terminal in advance from the base station through system information. Accordingly, the terminal can select a preamble group (or subgroup) within a single RO based on the corresponding SSB and repeat level, and select one preamble from among them to transmit (repeatedly) to the base station. Accordingly, the base station can identify which preamble group the preamble belonging to was received in the corresponding RO, thereby determining the SSB associated with the RO and the repeat level (or coverage level) of the terminal. Examples 2-3 FIG. 12 is a drawing for illustrating additional embodiments of preamble group settings to which the present disclosure may be applied. If there are multiple ROs associated with a single SSB, the multiple ROs can be grouped according to the repetition level. To this end, independent ROs corresponding to different repetition levels (or coverage levels) can be set. In the aforementioned embodiments, the preamble indices within a single RO are set into one or more preamble groups according to the repetition level, whereas in this embodiment, all preamble indices within a single RO correspond to the same repetition level, and different repetition levels may correspond to different ROs (or RO groups). In this way, a preamble repeat level can be set at the RO or RO group level. Accordingly, the terminal can select an RO corresponding to the repeat level or an RO according to the base station's settings, select a preamble index within the corresponding RO, and transmit a preamble to the base station. For example, within an RO group corresponding to a specific repeat level, a number of ROs corresponding to the specific repeat level may be selected. For each of the plurality of ROs, the terminal can select a preamble index and perform preamble transmission based on the preamble index selected on the plurality of ROs. Here, for each of the plurality of ROs, the terminal may select the same or different preamble index, or may randomly select a preamble index from each RO. Additionally, within a group of ROs corresponding to a specific repetition level, a number of ROs corresponding to the repetition level may be distinguished in time resources and / or frequency resources. For example, if the repetition level is 2 or more, the terminal may perform preamble transmission on multiple ROs on frequency resources distinguished from the same time resource, or perform preamble transmission on multiple ROs on time resources distinguished from the same frequency resource, or perform preamble transmission on multiple ROs on time resources distinguished from time resources. In the example of FIG. 12, the terminal determines SSB#1 as the optimal SSB and can identify a total of 32 ROs corresponding to SSB#1. Additionally, the total of 32 ROs corresponding to one SSB can be configured into 4 RO groups. The first RO group corresponds to repetition level #1, the second RO group corresponds to repetition level #2, the third RO group corresponds to repetition level #3, and the fourth RO group corresponds to repetition level #4. Among the total ROs corresponding to one SSB, as the repetition level index (starting from 0) increases, some ROs are mapped to their respective repetition level indices, thereby establishing a mapping relationship as shown in the example of FIG. 12. If the terminal determines repetition level 2, it can select 2 (the first RO and the second RO) from among the 8 ROs belonging to the second RO group and perform two repetition transmissions of the preamble. Here, in each RO, the terminal may randomly select a preamble index, select the same preamble index in the first RO and the second RO, or select different preamble indices in the first RO and the second RO. In this way, when a terminal performs a preamble transmission on one or more ROs belonging to the same RO group corresponding to a specific repeat level, the base station can determine the repeat level of the terminal based on which RO group the terminal performs the preamble transmission. The preamble repetitive transmission method in the examples described above corresponds to the case where a preamble of a single preamble index is transmitted from a single RO. That is, a number of ROs corresponding to the value of the repetition level can be used for preamble repetitive transmission. For example, when a preamble group corresponding to a repetition level M determined by the terminal is selected, a preamble index within the selected preamble group can be selected, and a single preamble can be transmitted on each of the M ROs. Additionally, when a RO group corresponding to a repetition level M determined by the terminal is selected, a single preamble can be transmitted on each of the M ROs within the selected RO group. As an additional preamble iteration transmission method according to the present disclosure, multiple preambles may be transmitted in a single RO. For example, multiple preambles may be multiplexed through distinct time and / or frequency resources within a single RO, or multiple preambles may be distinguished by Code Division Multiplexing (CDM) on the same time-frequency resource within a single RO. Here, the multiple preambles transmitted in a single RO may have the same preamble index or different preamble indices. In this case, the repetition level M may correspond to the product of the number of preambles transmitted from a single RO (M_Preamble) and the number of ROs transmitting preambles (M_RO) (where the number of preambles transmitted from a single RO is distinguished from the number of different preamble indices transmitted from a single RO). For example, depending on the repetition level M, the number of preambles transmitted in a single RO, M_Preamble, and the number of preamble-transmitting ROs, M_RO, may be determined. For example, if the repetition level M determined by the terminal is 4, M_Preamble and M_RO may be determined as 2, M_Preamble and M_RO may be determined as 4, or M_Preamble and M_RO may be determined as 1. In this way, one or more preamble transmissions may be performed in a single RO. In this regard, the number of allowed preambles in a single RO may be set by the base station. Alternatively, RO groups may be set according to the number of preambles transmitted in a single RO. For example, in some RO groups among RO groups corresponding to two or more repetition levels, the transmission of multiple (e.g., two) preambles in a single RO may be set. Here, the preamble iteration transmission method described above must be distinguished from the correspondence between the iteration transmission level and the preamble group and / or RO group. For example, the selection of a preamble group and / or RO group corresponding to the repeat level of the terminal may be applied in the same manner as the examples described above. In this case, the base station may determine the repeat level determined by the terminal not based on the actual number of times the preamble is received repeatedly, but from the preamble group or RO group index selected by the terminal. Specifically, one or more preamble indices may be selected from a single preamble group corresponding to a repetition level M determined by the terminal. Alternatively, one RO group may be selected from a single RO group corresponding to a repetition level M determined by the terminal, and one or more preamble indices may be selected within that RO (without distinguishing between preamble groups). For example, the terminal may determine a repetition level M=4. In this case, the terminal may select one preamble group corresponding to repetition level M=4 and select one or more preamble indices from the selected preamble group. Accordingly, in each of the M_RO ROs among the ROs associated with one SSB (or CSI-RS), one or more preamble indices selected from the selected preamble group may be repeatedly transmitted as M_Preamble preambles. Alternatively, the terminal may select one RO group corresponding to repetition level M=4 and select one or more preamble indices from the ROs belonging to that RO group. Accordingly, in each of the M_RO ROs within the selected RO group, one or more selected preamble indices may be repeatedly transmitted as M_Preamble preambles. As an additional example, the repeat level determined by the terminal may correspond to a combination of RO groups and preamble groups. For example, ROs associated with a single SSB (or CSI-RS) may include multiple RO groups, and each RO may include multiple preamble groups. In this case, the base station may determine the repeat level determined by the terminal from the combination of preamble groups and RO groups selected by the terminal. For example, the repetition level determined by the terminal may correspond to a combination of a first repetition level corresponding to an RO group and a second repetition level corresponding to a preamble group. For example, if the repetition level M determined by the terminal is 4, the terminal may select one RO group corresponding to the first repetition level 2 and select one preamble group corresponding to the second repetition level 2 within the RO belonging to that RO group. Alternatively, the terminal may select one RO group corresponding to the first repetition level 1 and select one preamble group corresponding to the second repetition level 4 within the RO belonging to that RO group. Alternatively, the terminal may select one RO group corresponding to the first repetition level 4 and select one preamble group corresponding to the second repetition level 1 within the RO belonging to that RO group. In this way, the terminal can select one or more preamble indices from a selected preamble group within a selected RO group and an RO belonging to that RO group. Accordingly, for each of the M_ROs within the selected RO group, one or more preamble indices selected within the selected preamble group can be repeatedly transmitted as M_Preamble preambles. Additionally, if the base station is based on the channel status of the RC terminal, its type / capability, and / or whether it is in RRC connection mode, it may explicitly instruct or set the preamble repeat transmission level to the terminal. In this case, unlike the above, the terminal does not select the repeat level, but the base station may instruct the repeat level through DCI signaling and / or upper layer signaling. After receiving information regarding the repeat level from the base station, the terminal may subsequently repeat the preamble or message A (e.g., in the case of 2-stage CBRA and 2-stage CFRA, the preamble and PUSCH) based on that information. Additionally, in the 2-stage CBRA or 2-stage CFRA transmitting message A, the preamble and PUSCH payloads included in message A may each be set by the base station or selected by the terminal for independent repeat transmission. For example, the number of preamble repeat transmissions (P) and the number of PUSCH payload repeat transmissions (P') corresponding to the repetition level selected by the terminal or directed by the base station by the proposed method above may be determined independently of each other or determined to be the same value. FIG. 13 is a flowchart for explaining terminal operation according to the present disclosure. In step S1310, the terminal can receive configuration information related to random access. For example, configuration information related to random access may be provided through system information signaling from the base station. The terminal can receive system information (e.g., SIB1 or dedicated RRC signaling) containing configuration information related to random access through cell search operations such as downlink synchronization via SSB or receiving a Master Information Block (MIB) via PBCH. In step S1320, the terminal can determine the terminal type. If it is a first type terminal (or general terminal), it can proceed to step S1330, and if it is a second type terminal (or RC terminal), it can proceed to step S1335. In this way, the random access preamble transmission operation can be determined according to the type of terminal. In steps S1330 and S1335, the terminal can determine the RO setting type. A shared RO that is common to some or all of the first and second type terminals may be set, or a separate RO that is distinct from the first and second type terminals may be set. In the case of a Type 1 terminal where a separate RO is configured, at step S1350, the terminal determines the optimal SSB (or CSI-RS) and can select one RO from among the available ROs associated with the determined SSB (or CSI-RS). One preamble index can be selected (randomly) from among all preamble indices of the selected RO. Here, one preamble index may be selected from one of preamble groups A or B. Subsequently, proceed to step S1364 to transmit a preamble according to the selected preamble index on one RO. If it is a Type 1 terminal and a shared RO is configured, in step S1360, the terminal determines an optimal SSB (or CSI-RS) and can select one RO from among the available ROs associated with the determined SSB (or CSI-RS). The entire preamble index of the selected RO can be configured into a preamble group distinguished according to the terminal type. The Type 1 terminal can select a first preamble group (or group A and / or B). In step S1362, the terminal can (randomly) select one preamble index within the selected preamble group. In step S1364, the terminal can transmit a preamble according to the selected preamble index on one RO. In the case of a Type 2 terminal, a repeat level may be determined. The repeat level may be determined by the terminal or explicitly specified by the base station. Additionally, an RO group, a preamble group, or a combination of an RO group and a preamble group corresponding to the repeat level may be set according to a predetermined rule or by the signaling of the base station. In the case where the terminal is of type 2 and a shared RO is configured, at step S1370 the terminal determines an optimal SSB (or CSI-RS) and can select one or more ROs from among the available ROs associated with the determined SSB (or CSI-RS). Here, when one preamble transmission is supported in one RO, the number of selected ROs may correspond to the repetition level, and when multiple preamble transmissions are supported in one RO, the product of the number of ROs and the number of preambles transmitted in one RO may correspond to the repetition level. Additionally, for each of the selected one or more ROs, the total preamble index may be set as a preamble group distinguished according to the terminal type. Additionally, the terminal may select a preamble group for each of the one or more ROs based on the terminal type and the repetition level. The second type terminal may select the second preamble group (or group C), select one or more subgroups of the second preamble group according to the repetition level, or select one of the second, third, ... preamble groups (or groups C, D, ...) according to the repetition level. In step S1372, the terminal may (randomly) select one or more preamble indices within the selected preamble group. If the repetition level is 2 or more, 2 or more ROs are selected, and for each of the 2 or more ROs, one preamble group based on the terminal type and repetition level is selected, and one or more preamble indices within the selected preamble group may be selected. Alternatively, if the repetition level is 2 or more, the number of preamble transmission ROs and the number of preambles transmitted from one RO are determined, and based thereon, one or more ROs, one preamble group, and / or one or more preamble indices may be selected. In step S1374, the terminal can transmit one or more preambles according to one or more selected preamble indices on one or more ROs. If it is a Type 2 terminal and a separate RO is set, a repetition level distinction type may be determined in step S1340. Depending on the repetition level distinction type, a preamble group corresponding to the repetition level may be set, or an RO group corresponding to the repetition level may be set. In the case where the terminal is of type 2, a separate RO is configured, and the repetition level distinction type is configured as a preamble group, at step S1380 the terminal determines an optimal SSB (or CSI-RS) and can select one or more ROs from among the available ROs associated with the determined SSB (or CSI-RS). Here, if one preamble transmission is supported in one RO, the number of selected ROs may correspond to the repetition level, and if multiple preamble transmissions are supported in one RO, the product of the number of ROs and the number of preambles transmitted in one RO may correspond to the repetition level. Additionally, for each of the selected one or more ROs, the total preamble index may be configured as a preamble group distinguished according to the repetition level. The terminal may select one preamble group based on the repetition level. Subsequently, in step S1372, the terminal may select one or more preamble indices within the selected preamble group. If the repetition level is 2 or more, 2 or more ROs are selected, and for each of the 2 or more ROs, one preamble group based on the terminal type and repetition level is selected, and one or more preamble indices within the selected preamble group may be selected. Alternatively, if the repetition level is 2 or more, the number of preamble transmission ROs and the number of preambles transmitted from one RO are determined, and based thereon, one or more ROs, one preamble group, and / or one or more preamble indices may be selected. In step S1374, the terminal may transmit one or more preambles according to the selected preamble index on one or more ROs. In the case where a second type terminal is configured with a separate RO and the repetition level classification type is configured as an RO group, at step S1390 the terminal determines an optimal SSB (or CSI-RS) and can select one RO group based on the repetition level from among the available ROs associated with the determined SSB (or CSI-RS). At step S1392 the terminal can select one or more ROs within the selected RO group. Here, when one preamble transmission is supported in one RO, the number of selected ROs may correspond to the repetition level, and when multiple preamble transmissions are supported in one RO, the product of the number of ROs and the number of preambles transmitted in one RO may correspond to the repetition level. In step S1394, the terminal may select one or more preambles from each of the selected one or more ROs. If the repetition level is 2 or more, two or more ROs are selected, and one or more preamble indices may be selected from each of the two or more ROs. Alternatively, if the repetition level is 2 or more, the number of preamble transmission ROs and the number of preambles transmitted from one RO are determined, and based thereon, one or more ROs and / or one or more preamble indices may be selected. Afterwards, proceed to step S1374, and the terminal can transmit one or more preambles according to the selected preamble index on one or more ROs. In the case where the terminal is of type 2, a separate RO is set, and the repetition level distinction type is set as a combination of an RO group and a preamble group, in step S1342, the terminal determines the optimal SSB (or CSI-RS) and can select one RO group and one preamble group based on the repetition level from among the available ROs associated with the determined SSB (or CSI-RS). In step S1344, the terminal may select one or more ROs within the selected RO group. Here, if one preamble transmission is supported in one RO, the number of selected ROs may correspond to a repetition level, and if multiple preamble transmissions are supported in one RO, the product of the number of ROs and the number of preambles transmitted in one RO may correspond to a repetition level. Additionally, for each of the one or more selected ROs, the entire preamble index can be set into preamble groups distinguished by the repetition level. The terminal can select one preamble group based on the repetition level and the selected RO group. In step S1346, the terminal may select one or more preamble indices within a selected preamble group from each of the selected one or more ROs. If the repetition level is 2 or more, two or more ROs are selected, and for each of the two or more ROs, one preamble group based on the terminal type and repetition level is selected, and one or more preamble indices within the selected preamble group may be selected. Alternatively, if the repetition level is 2 or more, the number of preamble transmission ROs and the number of preambles transmitted from one RO are determined, and based thereon, one or more ROs, one preamble group, and / or one or more preamble indices may be selected. Afterwards, proceed to step S1374, and the terminal can transmit one or more preambles according to the selected preamble index on one or more ROs. The terminal that transmitted the preamble in the aforementioned step S1364 or step S1374 may monitor the Random Access Response (RAR) transmitted from the base station in step S1366. After receiving the RAR (or Msg2), the terminal may complete the Random Access procedure through the exchange of Msg3 and Msg4 with the base station. As in the examples described above, the terminal may select an RO group, a preamble group, and / or a preamble index based on its capacity (or type) and / or repetition level. When the base station receives a random access preamble (or Msg1) from the terminal, it may identify whether the terminal belongs to a general terminal or an RC terminal based on the RO group to which the preamble is received, the group to which the preamble belongs, and / or the preamble index, and if it is an RC terminal, identify the repetition level (or coverage level). In this way, the base station may initially identify the presence of an RC terminal attempting a random access procedure and support a suitable random access procedure for the RC terminal. Specifically, when the base station identifies a random access attempt by an RC terminal, it may perform a random access procedure suitable for the RC terminal's capacity in the subsequent exchange of Msg2, Msg3, and Msg4 and the transmission of HARQ-ACK / NACK, taking into account the repetition level, message transmission and reception timing, message size, etc. In the embodiments of the present disclosure, the operation or configuration of the base station and / or terminal may be applied to a 4-stage RACH procedure (e.g., a contention-based random access procedure through the exchange of Msg1, Msg2, Msg3, and Msg4 similar to the example of FIG. 3), as well as to a 2-stage contention-based RACH procedure (e.g., a contention-based random access procedure consisting of a stage A in which the terminal transmits information corresponding to Msg1 and Msg3, and a stage B in which the base station transmits information corresponding to Msg4 (and Msg2)). That is, since the embodiments of the present disclosure relate to the selection of a random access preamble and the transmission of Msg1 to indicate whether it is an RC terminal, they may be applied to both a 4-stage and a 2-stage contention-based RACH procedure. FIG. 14 is a diagram showing the configuration of a base station device and a terminal device according to the present disclosure. The base station device (1400) may include a processor (1410), an antenna unit (1420), a transceiver (1430), and a memory (1440). The processor (1410) performs baseband-related signal processing and may include an upper layer processing unit (1411) and a physical layer processing unit (1415). The upper layer processing unit (1411) may process operations of the MAC layer, the RRC layer, or higher upper layers. The physical layer processing unit (1415) may perform operations of the PHY layer (e.g., uplink reception signal processing, downlink transmission signal processing, etc.). In addition to performing baseband-related signal processing, the processor (1410) may also control operations of the base station device (1400). The antenna section (1420) may include one or more physical antennas, and if it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (1430) may include an RF transmitter and an RF receiver. The memory (1440) may store information processed by the processor (1410), software related to the operation of the base station device (1400), an operating system, an application, etc., and may include components such as a buffer. The processor (1410) of the base station device (1400) can be configured to implement the operation of the base station in the embodiments described in the present invention. For example, the upper layer processing unit (1411) of the processor (1410) of the base station device (1400) may include a random access related setting information generation unit (1412), a terminal type determination unit (1413), and a repetition level determination unit (1414). The random access related setting information generation unit (1412) can set an RO group, a preamble group, and / or a preamble index based on the terminal type and / or repetition level, and provide this setting information to the terminal device (1450) through system information signaling. The terminal type determination unit (1413) can identify the type of the terminal device (1450) that transmitted the preamble (e.g., a general terminal or an RC terminal) based on the RO group and / or preamble group to which the random access preamble received from the terminal device (1450) belongs. When the terminal device (1450) that transmitted the preamble is identified as a second type terminal (or RC terminal), the repetition level determining unit (1414) can identify the repetition level (or coverage level) of the terminal device (1450) that transmitted the preamble based on the RO group to which the preamble was received, the preamble group to which the preamble belongs, etc., for the random access preamble received from the terminal device (1450). The base station device (1400) can provide an operation suitable for the terminal in a subsequent random access procedure, etc., by taking into account the type and repetition level of the terminal device (1450) attempting random access. The terminal device (1450) may include a processor (1460), an antenna unit (1470), a transceiver (1480), and a memory (1490). The processor (1460) performs baseband-related signal processing and may include an upper layer processing unit (1461) and a physical layer processing unit (1465). The upper layer processing unit (1461) may process operations of the MAC layer, the RRC layer, or higher layers. The physical layer processing unit (1465) may perform operations of the PHY layer (e.g., downlink reception signal processing, uplink transmission signal processing, etc.). In addition to performing baseband-related signal processing, the processor (1460) may also control operations of the terminal device (1460). The antenna section (1470) may include one or more physical antennas, and if it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (1480) may include an RF transmitter and an RF receiver. The memory (1490) may store information processed by the processor (1460), software related to the operation of the terminal device (1450), an operating system, an application, etc., and may include components such as a buffer. The processor (1460) of the terminal device (1450) can be configured to implement the operation of the terminal in the embodiments described in the present invention. For example, the upper layer processing unit (1461) of the processor (1460) of the terminal device (1450) may include a random access related setting determination unit (1462), an RO determination unit (1463), and a preamble group determination unit (1464). The random access related setting determination unit (1462) can determine the settings to be applied to the terminal device (1450) based on random access related setting information provided from the base station device (1400). For example, the terminal device (1450) can determine the settings for the RO group, preamble group, and / or preamble index according to the terminal type and / or repetition level. The RO determination unit (1463) can determine an RO for random access preamble transmission. For example, among the available ROs associated with the optimal SSB (or CSI-RS) determined by the terminal device (1450), an RO group or one or more ROs may be determined according to the terminal type and / or repetition level. First, an RO setting type may be determined according to random access related setting information. The RO setting type may be partially or entirely shared for different terminal types, or separate ROs may be set. According to this RO setting type, the terminal device (1450) may select one or more ROs from among the ROs corresponding to its terminal type. Additionally, if the repetition level distinction setting is associated with an RO group, an RO group corresponding to the repetition level may be selected. The preamble group determination unit (1464) can determine one preamble group per RO according to the terminal type and / or repetition level. If the repetition level distinction setting is associated with the preamble group, the preamble group corresponding to the repetition level can be selected. Additionally, one or more preamble indices can be selected within the selected preamble group. The RO determination unit (1463) and the preamble group determination unit (1464) can select an RO group and a preamble group corresponding to the repetition level if the repetition level distinction setting is associated with a combination of an RO group and a preamble group. The physical layer processing unit (1465) can transmit a random access preamble to the base station device (1400) according to the RO and preamble index determined by the upper layer processing unit (1461). In the operation of the base station device (1400) and the terminal device (1450), the matters described for the base station and the terminal in the examples of the present invention may be applied in the same way, and redundant descriptions are omitted. The exemplary methods of the present disclosure are described as a series of operations for clarity of description, but this is not intended to limit the order in which the steps are performed, and if necessary, each step may be performed simultaneously or in a different order. To implement the method according to the present disclosure, additional steps may be included in addition to the steps exemplified, steps excluding some steps and including the remaining steps, or steps excluding some steps and including additional steps. The various embodiments of the present disclosure are not intended to list all possible combinations but are intended to illustrate representative aspects of the present disclosure, and some or all of the details described in the various embodiments may be applied independently or in combination of two or more. In addition, various embodiments of the present disclosure may be implemented by hardware, firmware, software, or a combination thereof. In the case of implementation by hardware, it may be implemented by one or more ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), DSPDs (Digital Signal Processing Devices), PLDs (Programmable Logic Devices), FPGAs (Field Programmable Gate Arrays), general processors, controllers, microcontrollers, microprocessors, etc. The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that enable operations according to the methods of various embodiments to be executed on a device or computer, and a non-transitory computer-readable medium on which such software or instructions, etc. are stored and executable on a device or computer. Instructions that may be used to program a processing system to perform the features described in the present disclosure may be stored on or within a storage medium or a computer-readable storage medium, and the features described in the present disclosure may be implemented using a computer program product comprising such a storage medium. The storage medium may include, but is not limited to, high-speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, 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 may optionally include one or more storage devices located remotely from the processor(s). Memory or alternatively, non-volatile memory device(s) within memory comprises a non-transient computer-readable storage medium. The features described in this disclosure may be stored in any one of the machine-readable media and integrated into software and / or firmware that can control the hardware of a processing system and allow the processing system to interact with other mechanisms utilizing results according to the embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers. Examples of the present disclosure can be applied to various wireless communication systems.

Claims

1. In a method for a terminal to perform random access in a wireless communication system, A step of receiving random access related setting information from a base station; A step of determining one or more of the RO (RACH Occasion) groups related to the random access preamble transmission, one or more of the ROs or random access preamble groups based on one or more of the random access-related configuration information, terminal type or repetition level; a step of transmitting one or more random access preambles in each of the one or more ROs. How to perform random access.

Images