Method for controlling terminal access in communication system

By introducing two-step and four-step random access processes in the high-frequency band communication system, using RA preamble and RA payload, combined with MAC subprotocol data unit and system information, the problem of signal performance deterioration during terminal access is solved. , realizes effective access and resource management of terminals in high-frequency band communication systems, and improves the performance and access efficiency of the communication system.

CN119071934APending Publication Date: 2024-12-03ELECTRONICS & TELECOMM RES INST
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411360058.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2020-03-09
Filing Date
2020-03-10
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

In high-frequency band communication systems, especially in millimeter bands, there are problems of signal performance deterioration and reception performance degradation during the access process of terminals. It is difficult for the prior art to effectively control the access process of terminals, which affects the performance of the communication system.

Method used

By introducing two-step random access and four-step random access processes in the communication system, the terminal connection is controlled by using the transmission of RA preamble and RA payload, combined with the modulation and encoding scheme in the MAC sub-protocol data unit and system information. and monitor and resource management through temporary identifiers and resource allocation information of RA radio networks.

Benefits of technology

It realizes effective access and resource management of terminals in high-frequency band communication systems, improves the performance and access efficiency of the communication system, supports multiple access processes, and enhances the flexibility and stability of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119071934A_ABST
    Figure CN119071934A_ABST
Patent Text Reader

Abstract

A method for controlling access of a terminal in a communication system is provided. An operation method of a terminal comprises the steps of: receiving configuration information for a two-step random access procedure from a base station; transmitting an RA MSG-A including an RA preamble and an RA payload to the base station on the basis of the configuration information; and receiving, from the base station, an RA MSG-B in response to the RA MSG-A. Therefore, the performance of the communication system can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This patent application is a divisional application of the Chinese invention patent application with application number 202080002260.6 and invention name “Method for controlling terminal access in a communication system”, which entered the Chinese national phase of the international patent application PCT / KR2020 / 003325 filed on March 10, 2020. Technical Field

[0002] The present invention relates to a technology for access of a terminal in a communication system, and more particularly, to a technology for contention- and non-contention-based access control in a communication system using a high frequency band. Background Art

[0003] With the development of information and communication technology, various wireless communication technologies have been developed. Typical wireless communication technologies include Long Term Evolution (LTE) and New Radio (NR), which are defined in the Third Generation Partnership Project (3GPP) standard. LTE can be one of the fourth generation (4G) wireless communication technologies, and NR can be one of the fifth generation (5G) wireless communication technologies.

[0004] A communication system (hereinafter referred to as a new radio (NR) communication system) using a higher frequency band (e.g., a frequency band of 6 GHz or more) than that of long term evolution (LTE) (or LTE-A) (e.g., a frequency band of 6 GHz or less) is being considered for handling rapidly growing wireless data. The 5G communication system may support enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), massive machine type communication (mMTC), and the like.

[0005] At the same time, millimeter frequency bands (e.g., frequency bands of 6 to 90 GHz) can be used to process rapidly increasing data. Small base stations can be used to overcome the degradation of received signal performance due to path attenuation and reflection of radio waves in high frequency bands (e.g., millimeter frequency bands). In a communication system supporting millimeter frequency bands, instead of a small base station that supports all functions of a radio protocol, multiple remote radio transmit / receive blocks (e.g., remote radio heads (RRHs)) and centralized baseband processing functional blocks may be deployed.

[0006] That is, all functions of the radio protocol can be distributedly supported in the remote wireless transmission / reception block and the baseband processing function block in a functional split scheme. When the functional split technology is used, the communication system can be configured by multiple transmission and reception points (TRPs). Multiple transmission and reception points can perform communication using a carrier aggregation scheme, a dual connection scheme, a retransmission scheme, etc. In a communication system supporting a functional split scheme, a carrier aggregation scheme, a dual connection scheme, a dual broadcast scheme, a retransmission scheme, etc., a method for effectively performing an access procedure (e.g., a random access procedure) of a terminal is required. Summary of the invention

[0007]

Technical issues

[0008] An object of the present invention to solve the above-mentioned problems is to provide a method and apparatus for controlling access according to an operation state of a terminal in a communication system.

[0009]

Technical solution

[0010] According to the first exemplary embodiment of the present invention for achieving the above-mentioned purpose, the operation method of the terminal may include: receiving configuration information for a two-step random access process from a base station; transmitting a random access (RA) message-A (MSG-A) including an RA preamble code and an RA payload to the base station based on the configuration information; receiving an RA MSG-B from the base station in response to the RA MSG-A, wherein the RA MSG-B includes one or more MAC sub-protocol data units (subPDUs), each of the one or more MAC sub-PDUs includes a MAC sub-header, and the MAC sub-header includes a first indicator indicating the type of the MAC sub-PDU.

[0011] The operating method may further include receiving system information including information indicating a modulation and coding scheme (MCS) for the RA payload from the base station, wherein the RA payload is transmitted based on the MCS level indicated by the system information.

[0012] The first indicator may indicate that the MAC subPDU is a first type MAC subPDU including a backoff indicator (BI), the MAC subPDU is a second type MAC subPDU including a backoff random access response (RAR), or the MAC subPDU is a third type MAC subPDU including a successful RAR.

[0013] The size of the first indicator may be 2 bits, a first bit of the 2 bits may indicate a first type MAC sub-PDU or a second type MAC sub-PDU, and a second bit of the 2 bits may indicate a third type MAC sub-PDU.

[0014] The operation method may further include: when the first indicator included in the RA MSG-B indicates the first type MAC sub-PDU, performing a two-step random access procedure or a four-step random access procedure based on the BI included in the RA MSG-B.

[0015] The operating method may further include transmitting, to the base station, a RA MSG3 according to a four-step random access procedure when the first indicator included in the RA MSG-B indicates the second type MAC sub-PDU.

[0016] The RA MSG3 may be transmitted using resources indicated by an uplink (UL) grant included in the fallback RAR.

[0017] The RA MSG-B including the fallback RAR may be generated based on the format of the RA MSG2 of the four-step random access procedure.

[0018] When the first indicator indicates the third type of MAC sub-PDU, the two-step random access procedure may be terminated.

[0019] When the RA MSG-B is received within the RAR window from the transmission end time point of the RA preamble, it can be determined that the contention is resolved in the two-step random access procedure.

[0020] The MAC subheader may also include a second indicator indicating whether the MAC sub-PDU is a fourth type MAC sub-PDU including a MAC service data unit (SDU), and the MAC SDU may include data or control information. The MAC subheader may also include a third indicator indicating whether there is another MAC sub-PDU.

[0021] According to the second exemplary embodiment of the present invention for achieving the above-mentioned purpose, the operation method of the base station may include: transmitting two-step configuration information for a two-step random access (RA) process to a terminal; transmitting four-step configuration information for a four-step random access process to the terminal; receiving message 1 from the terminal by performing a monitoring operation using the two-step configuration information and the four-step configuration information; and when message 1 is an RA message-A (MSG-A) of the two-step RA process, transmitting an RA MSG-B including one or more MAC sub-protocol data units (subPDUs) to the terminal, wherein each of the one or more MAC sub-PDUs includes a MAC sub-header, and the MAC sub-header includes a first indicator indicating the type of the MAC sub-PDU.

[0022] The operating method may further include transmitting system information including information indicating a modulation and coding scheme (MCS) for the RA payload included in the RA MSG-A to the terminal.

[0023] The first indicator may indicate that the MAC subPDU is a first type MAC subPDU including a backoff indicator (BI), the MAC subPDU is a second type MAC subPDU including a backoff random access response (RAR), or the MAC subPDU is a third type MAC subPDU including a successful RAR.

[0024] The operation method may further include receiving RA MSG3 from the base station through resources indicated by an uplink (UL) grant included in the fallback RAR according to a four-step random access procedure when the first indicator included in the RA MSG-B indicates the second type MAC subPDU.

[0025] The RA MSG-B including the fallback RAR may be generated based on the format of the RA MSG2 of the four-step random access procedure.

[0026] When a RA MSG-B is received from the terminal within the RAR window from the transmission end time point of the RA preamble and the first indicator included in the RAMSG-B indicates the third type MAC sub-PDU, the two-step random access procedure may be terminated.

[0027] A MAC sub-PDU among one or more MAC sub-PDUs may include a MAC service data unit (SDU) containing control information or data, and a radio network temporary identifier (RNTI) for a MAC sub-PDU including the MAC SDU may be configured independently of the RNTI for another MAC sub-PDU containing a BI, fallback RAR, or success RAR.

[0028] The MAC subheader may also include a second indicator indicating whether the MAC sub-PDU is a fourth type MAC sub-PDU including a MAC service data unit (SDU), and the MAC SDU may include data or control information. The MAC subheader may also include a third indicator indicating whether there is another MAC sub-PDU.

[0029] An operating method of a terminal according to a third exemplary embodiment of the present invention for achieving the above-mentioned purpose may include: receiving configuration information for a two-step random access procedure from a base station; and transmitting a random access (RA) message-A (MSG-A) including an RA preamble and an RA payload to the base station based on the configuration information; determining a random access radio network temporary identifier (RA-RNTI) by using information of a radio resource through which the RA preamble is transmitted and a preconfigured offset; receiving downlink control information (DCI) including resource allocation information of an RA MSG-B from the base station by performing a physical downlink control channel (PDCCH) monitoring operation using the RA-RNTI; and receiving the RA MSG-B from the base station through resources indicated by the resource allocation information included in the DCI.

[0030] The RA-RNTI used for the two-step random access procedure may be configured differently from the RA-RNTI used for the four-step random access procedure.

[0031] The RA-RNTI may be determined by applying a preconfigured offset to the RA-RNTI of the four-step random access procedure.

[0032] The preconfigured offset may be received from a base station.

[0033] The PDCCH monitoring operation may be performed within a random access response (RAR) window.

[0034] When a two-step random access procedure is performed in a contention-free random access (CFRA) scheme, the configuration information may include information of transmission resources exclusively allocated to the RA MSG-A of the terminal.

[0035] An operating method of a base station according to a fourth exemplary embodiment of the present invention for achieving the above-mentioned purpose may include: transmitting configuration information for a two-step random access procedure to a terminal; and receiving a random access (RA) message-A (MSG-A) including an RA preamble and an RA payload from the terminal by performing a monitoring operation based on the configuration information; determining a random access radio network temporary identifier (RA-RNTI) by using information of a radio resource through which the RA preamble is received and a preconfigured offset; performing a scrambling operation on downlink control information (DCI) including resource allocation information of an RA MSG-B by using the RA-RNTI; transmitting the scrambled DCI to the terminal; and transmitting the RA MSG-B to the terminal through resources indicated by the resource allocation information contained in the DCI.

[0036] The RA-RNTI may be determined by applying a preconfigured offset to the RA-RNTI of the four-step random access procedure.

[0037] The operating method may further include transmitting the preconfigured offset to the terminal.

[0038] The scrambled DCI may be transmitted to the terminal within a random access response (RAR) window.

[0039] When a two-step random access procedure is performed in a contention-free random access (CFRA) scheme, the configuration information may include information of transmission resources exclusively allocated to the RA MSG-A of the terminal.

[0040]

Beneficial effects

[0041] According to an exemplary embodiment of the present invention, a communication system may support a two-step random access procedure and a four-step random access procedure. A terminal may perform a two-step random access procedure when a first execution condition is met, and may perform a four-step random access procedure when a second execution condition is met. A random access (RA) MSG-A of a two-step random access procedure and a RA MSG1 of a four-step random access procedure may be distinguished based on an RA preamble index or a transmission resource.

[0042] The RA Radio Network Temporary Identifier (RA-RNTI) used for transmission and reception of the RA MSG-B of the two-step random access procedure may be configured differently from the RA-RNTI used for transmission and reception of the RA MSG2 of the four-step random access procedure. The terminal may receive the RA MSG-B or RA MSG2 from the base station by using the RA-RNTI. The medium access control (MAC) subheader of the RA MSG-B may include an indicator indicating the type of the RA MSG-B. The terminal may identify the type of the RA MSG-B based on the indicator. Therefore, the random access procedure may be efficiently performed and the performance of the communication system may be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Figure 1 is a conceptual diagram illustrating a first exemplary embodiment of a communication system.

[0044] Figure 2 is a block diagram showing a first exemplary embodiment of a communication node constituting a communication system.

[0045] Figure 3 is a conceptual diagram illustrating a second exemplary embodiment of a communication system.

[0046] Figure 4 is a conceptual diagram illustrating a first exemplary embodiment of an integrated communication system.

[0047] Figure 5 is a conceptual diagram illustrating a second exemplary embodiment of an integrated communication system.

[0048] Figure 6The present invention is a concept showing a first exemplary embodiment of a communication method based on beamforming in a communication system.

[0049] Figure 7 is a conceptual diagram illustrating a first exemplary embodiment of a method for configuring a bandwidth part (BWP) in a communication system.

[0050] Figure 8 is a conceptual diagram showing a first exemplary embodiment of an operation state of a terminal in a communication system.

[0051] Fig. 9 is a sequence diagram showing a first exemplary embodiment of a random access procedure in a communication system.

[0052] Fig.10 is a sequence diagram illustrating a second exemplary embodiment of a random access procedure in a communication system.

[0053] Fig.11 is a conceptual diagram illustrating a first exemplary embodiment of an RA MSG-A transmission method in a communication system.

[0054] Fig.12a is a conceptual diagram showing a first exemplary embodiment of a MAC subheader in a random access procedure.

[0055] Figure 12b is a conceptual diagram showing a second exemplary embodiment of a MAC subheader in a random access procedure.

[0056] Fig.12c is a conceptual diagram showing a first exemplary embodiment of an RA MSG-B in a random access procedure.

[0057] Fig.12d is a conceptual diagram showing a second exemplary embodiment of an RA MSG-B in a random access procedure.

[0058] Fig.12e is a conceptual diagram illustrating a third exemplary embodiment of a RA MSG-B in a random access procedure.

[0059] Fig.12f is a conceptual diagram illustrating a fourth exemplary embodiment of a RA MSG-B in a random access procedure.

[0060] Fig.13a is a conceptual diagram illustrating a fifth exemplary embodiment of a RA MSG-B in a random access procedure.

[0061] Fig.13b is a conceptual diagram illustrating a sixth exemplary embodiment of a RA MSG-B in a random access procedure.

[0062] Fig.13cis a conceptual diagram illustrating a seventh exemplary embodiment of a RA MSG-B in a random access procedure.

[0063] Fig.14a is a conceptual diagram illustrating an eighth exemplary embodiment of a RA MSG-B in a random access procedure.

[0064] Fig.14b is a conceptual diagram illustrating a ninth exemplary embodiment of a RA MSG-B in a random access procedure.

[0065] Fig.14c is a conceptual diagram illustrating a tenth exemplary embodiment of a RA MSG-B in a random access procedure.

[0066] Fig.15 is a timing diagram illustrating a third exemplary embodiment of a random access procedure in a communication system.

[0067] Fig.16a is a conceptual diagram showing a third exemplary embodiment of a MAC subheader in a random access procedure.

[0068] Fig.16b is a conceptual diagram showing a fourth exemplary embodiment of a MAC subheader in a random access procedure.

[0069] Fig.16c is a conceptual diagram illustrating an eleventh exemplary embodiment of a RA MSG-B in a random access procedure.

[0070] Fig.16d is a conceptual diagram illustrating a twelfth exemplary embodiment of a RA MSG-B in a random access procedure.

[0071] Fig.16e is a conceptual diagram illustrating a thirteenth exemplary embodiment of a RA MSG-B in a random access procedure.

[0072] Fig.16f is a conceptual diagram illustrating a fourteenth exemplary embodiment of a RA MSG-B in a random access procedure.

[0073] Figure 16g is a conceptual diagram illustrating a fifteenth exemplary embodiment of a RA MSG-B in a random access procedure.

[0074] Fig.17a is a conceptual diagram showing a fifth exemplary embodiment of a MAC subheader in a random access procedure.

[0075] Fig.17b is a conceptual diagram showing a sixth exemplary embodiment of a MAC subheader in a random access procedure.

[0076] Fig.17c is a conceptual diagram showing a seventh exemplary embodiment of a MAC subheader in a random access procedure.

[0077] Fig.17d is a conceptual diagram showing an eighth exemplary embodiment of a MAC subheader in a random access procedure.

[0078] Fig.17e is a conceptual diagram showing a ninth exemplary embodiment of a MAC subheader in a random access procedure.

[0079] Fig.17f is a conceptual diagram illustrating a sixteenth exemplary embodiment of a RA MSG-B in a random access procedure.

[0080] Figure 17g is a conceptual diagram illustrating a seventeenth exemplary embodiment of a RA MSG-B in a random access procedure.

[0081] Fig.18 is a sequence diagram showing a third exemplary embodiment of a random access procedure in a communication system. DETAILED DESCRIPTION

[0082] Although the present disclosure allows various modifications and alternative forms, specific embodiments are shown in the drawings as examples and will be described in detail herein. However, it should be understood that this description is not intended to limit the present invention to specific embodiments, on the contrary, the present invention will cover all modifications, equivalents and alternative forms that fall within the spirit and scope of the present invention.

[0083] Although the terms "first", "second", etc. may be used herein with reference to various components, such components should not be construed as being limited by these terms. These terms are used only to distinguish one component from another component. For example, a first component may be referred to as a second component, and a second component may be referred to as a first component without departing from the scope of the present invention. The term "and / or" includes any and all combinations of one or more of the associated listed items.

[0084] It will be understood that when a component is referred to as being "connected" or "coupled" to another component, it can be directly connected or coupled to the other component, or there may be intervening components. In contrast, when a component is referred to as being "directly connected" or "directly coupled" to another component, there are no intervening components.

[0085] The terms used herein are only for the purpose of describing specific embodiments and are not intended to limit embodiments of the present invention. As used herein, the singular forms "a", "an" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will also be understood that the terms "include", "include", "comprise" and / or "comprises" when used herein specify the presence of stated features, integers, steps, operations, parts, components and / or combinations thereof, but do not exclude the presence or addition of one or more other features, integers, steps, operations, parts, components and / or combinations thereof.

[0086] Unless otherwise defined, the terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those skilled in the art to which the present invention relates. It will be further understood that, unless expressly defined herein, terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology and will not be interpreted in an idealized or overly formal sense.

[0087] Hereinafter, embodiments of the present disclosure will be described in more detail with reference to the accompanying drawings. In order to facilitate an overall understanding of the present invention, the same reference numerals refer to the same components throughout the description of the drawings, and the description of the same components will not be repeated.

[0088] A communication system according to an exemplary embodiment of the present invention will be described. However, the communication system to which the exemplary embodiment of the present invention is applied is not limited to the communication system to be described below. That is, the exemplary embodiment of the present invention can be applied to various communication systems. Here, the term "communication system" can be used in the same meaning as the term "communication network".

[0089] Figure 1 is a conceptual diagram illustrating a first exemplary embodiment of a communication system.

[0090] refer to Figure 1 , the communication system 100 may include a plurality of communication nodes 110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6. The plurality of communication nodes may support fourth generation (4G) communication (e.g., long term evolution (LTE), advanced LTE (LTE-A)), fifth generation (5G) communication (e.g., new radio (NR)), etc. 4G communication may be performed in a frequency band of 6 gigahertz (GHz) or less, and 5G communication may be performed in a frequency band of 6 GHz or more.

[0091] For example, for 4G and 5G communications, multiple communication nodes can support a communication protocol based on code division multiple access (CDMA), a communication protocol based on wideband CDMA (WCDMA), a communication protocol based on time division multiple access (TDMA), a communication protocol based on frequency division multiple access (FDMA), a communication protocol based on orthogonal frequency division multiplexing (OFDM), a communication protocol based on filtered OFDM, a communication protocol based on cyclic prefix OFDM (CP-OFDM), a communication protocol based on discrete Fourier transform spread OFDM (DFT-s-OFDM), a communication protocol based on orthogonal frequency division multiple access (OFDMA), a communication protocol based on single carrier FDMA (SC-FDMA), a communication protocol based on non-orthogonal multiple access (NOMA), a communication protocol based on general frequency division multiplexing (GFDM), a communication protocol based on filter bank multi-carrier (FBMC), a communication protocol based on universal filtered multi-carrier (UFMC), a communication protocol based on space division multiple access (SDMA), and the like.

[0092] Moreover, the communication system 100 may further include a core network. When the communication system 100 supports 4G communication, the core network may include a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a mobility management entity (MME), etc. When the communication system 100 supports 5G communication, the core network may include a user plane function (UPF), a session management function (SMF), an access and mobility management function (AMF), etc.

[0093] Meanwhile, each of the plurality of communication nodes 110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6 constituting the communication system 100 may have the following structure.

[0094] Figure 2 is a block diagram showing a first embodiment of a communication node constituting a communication system.

[0095] Reference Figure 2 , the communication node 200 may include at least one processor 210, a memory 220, and a transceiver 230 connected to a network to perform communication. Moreover, the communication node 200 may further include an input interface device 240, an output interface device 250, a storage device 260, etc. Each component included in the communication node 200 can communicate with each other when connected through the bus 270.

[0096] However, each component included in the communication node 200 may be connected to the processor 210 via an independent interface or a separate bus instead of the common bus 270. For example, the processor 210 may be connected to at least one of the memory 220, the transceiver 230, the input interface device 240, the output interface device 250, and the storage device 260 via a dedicated interface.

[0097] The processor 210 may execute a program stored in at least one of the memory 220 and the storage device 260. The processor 210 may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which the method according to an embodiment of the present disclosure is executed. Each of the memory 220 and the storage device 260 may be composed of at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory 220 may include at least one of a read-only memory (ROM) and a random access memory (RAM).

[0098] Reference again Figure 1 , the communication system 100 may include a plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 and a plurality of terminals 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6. The communication system 100 including the base stations 110-1, 110-2, 110-3, 120-1, and 120-2 and the terminals 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6 may be referred to as an "access network". Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 may form a macro cell, and each of the fourth base station 120-1 and the fifth base station 120-2 may form a small cell. The fourth base station 120-1, the third terminal 130-3 and the fourth terminal 130-4 may belong to the cell coverage of the first base station 110-1. In addition, the second terminal 130-2, the fourth terminal 130-4 and the fifth terminal 130-5 may belong to the cell coverage of the second base station 110-2. Moreover, the fifth base station 120-2, the fourth terminal 130-4, the fifth terminal 130-5 and the sixth terminal 130-6 may belong to the cell coverage of the third base station 110-3. In addition, the first terminal 130-1 may belong to the cell coverage of the fourth base station 120-1, and the sixth terminal 130-6 may belong to the cell coverage of the fifth base station 120-2.

[0099] Here, each of the multiple base stations 110-1, 110-2, 110-3, 120-1 and 120-2 may refer to a Node B, an evolved Node B (eNB), a base transceiver station (BTS), a radio base station, a radio transceiver, an access point, an access node, a road side unit (RSU), a radio remote head (RRH), a transmission point (TP), a transmit and receive point (TRP), an eNB, a gNB, etc.

[0100] Here, each of the multiple terminals 130-1, 130-2, 130-3, 130-4, 130-5 and 130-6 may refer to a user equipment (UE), a terminal, an access terminal, a mobile terminal, a station, a subscriber station, a mobile station, a portable subscriber station, a node, a device, an Internet of Things (IoT) device, an installed device (e.g., an installed module / device / terminal or an on-board device / terminal, etc.), etc.

[0101] At the same time, each of the multiple base stations 110-1, 110-2, 110-3, 120-1 and 120-2 can operate in the same frequency band or in different frequency bands. The multiple base stations 110-1, 110-2, 110-3, 120-1 and 120-2 can be connected to each other via an ideal backhaul or a non-ideal backhaul, and exchange information with each other via an ideal or non-ideal backhaul. In addition, each of the multiple base stations 110-1, 110-2, 110-3, 120-1 and 120-2 can be connected to the core network via an ideal or non-ideal backhaul. Each of the multiple base stations 110-1, 110-2, 110-3, 120-1 and 120-2 can transmit the signal received from the core network to the corresponding terminal 130-1, 130-2, 130-3, 130-4, 130-5 or 130-6, and transmit the signal received from the corresponding terminal 130-1, 130-2, 130-3, 130-4, 130-5 or 130-6 to the core network.

[0102] Moreover, each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may support multiple-input multiple-output (MIMO) transmission (e.g., single-user MIMO (SU-MIMO), multi-user MIMO (MU-MIMO), massive MIMO, etc.), coordinated multi-point (CoMP) transmission, carrier aggregation (CA) transmission, transmission in an unlicensed band, device-to-device (D2D)) communication (or proximity service (ProSe)), etc. Here, each of the plurality of terminals 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6 may perform operations corresponding to operations of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 and operations supported by the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2. For example, the second base station 110-2 may transmit a signal to the fourth terminal 130-4 in SU-MIMO mode, and the fourth terminal 130-4 may receive a signal from the second base station 110-2 in SU-MIMO mode. Alternatively, the second base station 110-2 may transmit a signal to the fourth terminal 130-4 and the fifth terminal 130-5 in MU-MIMO mode, and the fourth terminal 130-4 and the fifth terminal 130-5 may receive a signal from the second base station 110-2 in MU-MIMO mode.

[0103] The first base station 110-1, the second base station 110-2 and the third base station 110-3 can transmit signals to the fourth terminal 130-4 in a CoMP transmission manner, and the fourth terminal 130-4 can receive signals from the first base station 110-1, the second base station 110-2 and the third base station 110-3 in a CoMP manner. Moreover, each of the multiple base stations 110-1, 110-2, 110-3, 120-1 and 120-2 can exchange signals with the corresponding terminal 130-1, 130-2, 130-3, 130-4, 130-5 or 130-6 in a CA manner, which belongs to its cell coverage. Each of base stations 110-1, 110-2 and 110-3 can control D2D communication between the fourth terminal 130-4 and the fifth terminal 130-5, and thus the fourth terminal 130-4 and the fifth terminal 130-5 can perform D2D communication under the control of the second base station 110-2 and the third base station 110-3.

[0104] Hereinafter, a method for configuring and managing a radio interface in a communication system will be described. Even when a method (e.g., transmission or reception of a data packet) performed at a first communication node among communication nodes is described, a corresponding second communication node may perform a method (e.g., reception or transmission of a data packet) corresponding to the method performed at the first communication node. That is, when the operation of a terminal is described, a corresponding base station may perform an operation corresponding to the operation of the terminal. Conversely, when the operation of a base station is described, a corresponding terminal may perform an operation corresponding to the operation of the base station.

[0105] Meanwhile, in a communication system, a base station may perform all functions of a communication protocol (e.g., remote radio transmission and reception functions, baseband processing functions, etc.). Alternatively, the remote radio transmission and reception functions among all functions of the communication protocol may be performed by a transmission reception point (TRP) (e.g., a flexible TRP (f-TRP)), and the baseband processing functions among all functions of the communication protocol may be performed by a baseband unit (BBU) block. The TRP may be a remote radio head (RRH), a radio unit (RU), a transmission point (TP), etc. The BBU block may include at least one BBU or at least one digital unit (DU). The BBU block may be referred to as a "BBU pool", "centralized BBU", etc. The TRP may be connected to the BBU block via a wired fronthaul link or a wireless fronthaul link. A communication system consisting of a backhaul link and a fronthaul link may be as follows. When the functional splitting technique of the communication protocol is applied, the TRP may selectively perform certain functions of the BBU or certain functions of the media access control (MAC) or the radio link control (RLC).

[0106] Figure 3 is a conceptual diagram illustrating a second exemplary embodiment of a communication system.

[0107] Reference Figure 3, the communication system may include a core network and an access network. The core network supporting 4G communication may include MME 310-1, S-GW 310-2, P-GW 310-3, etc. The core network supporting 5G communication may include AMF 310-1, UPF310-2, PDN-GW 310-3, etc. The access network may include a macro base station 320, a small base station 330, TRPs 350-1 and 350-2, terminals 360-1, 360-2, 360-3, 360-4, and 360-5, etc. The macro base station 320 or the small base station 330 may be connected to the terminal node of the core network via a wired backhaul. TRPs 350-1 and 350-2 may support remote radio transmission and reception functions among all functions of the communication protocol, and the baseband processing functions for TRPs 350-1 and 350-2 may be performed by a BBU block 340. The BBU block 340 may belong to an access network or a core network. Communication nodes (e.g., MME, S-GW, P-GW, AMF, UPF, PDN-GW, macro base station, small base station, TRP, terminal, and BBU block) belonging to the communication system may be connected to Figure 2 The illustrated communication nodes 200 are similarly configured or identically configured.

[0108] The macro base station 320 can be connected to the core network (e.g., AMF 310-1, UPF 310-2, MME, S-GW) using a wired backhaul link or a wireless backhaul link, and can provide communication services to the terminals 360-3 and 360-4 based on a communication protocol (e.g., 4G communication protocol, 5G communication protocol). The small base station 330 can be connected to the core network (e.g., AMF 310-1, UPF 310-2, MME, S-GW) using a wired backhaul link or a wireless backhaul link, and can provide communication services to the terminal 360-5 based on a communication protocol (e.g., 4G communication protocol, 5G communication protocol).

[0109] The BBU block 340 may be located in the AMF 310-1, UPF 310-2, MME, S-GW, or macro base station 320. Alternatively, the BBU block 340 may be located independently of each of the AMF 310-1, UPF 310-2, MME, S-GW, and macro base station 320. For example, the BBU block 340 may be configured as a logical function between the macro base station 320 and the AMF 310-1 (or UPF 310-2). The BBU block 340 may support multiple TRPs 350-1 and 350-2, and may be connected to each of the multiple TRPs 350-1 and 350-2 using a wired fronthaul link or a wireless fronthaul link. That is, the link between the BBU block 340 and the TRPs 350-1 and 350-2 may be referred to as a "fronthaul link".

[0110] The first TRP 350-1 can be connected to the BBU block 340 via a wired fronthaul link or a wireless fronthaul link, and provide communication services to the first terminal 360-1 based on a communication protocol (e.g., 4G communication protocol, 5G communication protocol). The second TRP 350-2 can be connected to the BBU block 340 via a wired fronthaul link or a wireless fronthaul link, and provide communication services to the second terminal 360-2 based on a communication protocol (e.g., 4G communication protocol, 5G communication protocol).

[0111] In the exemplary embodiments to be described below, the communication system including the access network, the Xhaul network and the core network may be referred to as an "integrated communication system". Figure 2 The communication node 200 shown is similarly or identically configured as a communication node (e.g., MME, S-GW, P-GW, AMF, UPF, BBU block, distributed unit (DU), central unit (CU), base station, TRP, terminal, etc.) An Xhaul link may be used to connect communication nodes belonging to an Xhaul network, and the Xhaul link may be a backhaul link or a fronthaul link.

[0112] Moreover, the UPF (or S-GW) of the integrated communication system may refer to a terminal communication node of the core network, which exchanges packets (e.g., control information, data) with the base station, and the AMF (or MME) of the integrated communication system may refer to a communication node in the core network, which performs a control function in the radio access part (or interface) of the terminal. Here, each of the backhaul link, fronthaul link, Xhaul link, DU, CU, BBU block, S-GW, MME, AMF and UPF may be referred to as different terms according to the function (e.g., function of Xhaul network, function of core network) of the communication protocol depending on the radio access technology (RAT).

[0113] Figure 4 is a conceptual diagram illustrating a first exemplary embodiment of an integrated communication system.

[0114] Reference Figure 4 The integrated communication system may include an access network, an Xhaul network, and a core network. The Xhaul network may be located between the access network and the core network and may support communication between the access network and the core network. The communication nodes belonging to the integrated communication system may be configured to communicate with Figure 2The communication nodes 200 shown are the same or similar. The access network may include a TRP 430, a terminal 440, etc. The Xhaul network may include a plurality of communication nodes 420-1, 420-2, and 420-3. The communication nodes constituting the Xhaul network may be referred to as "DU" or "CU". In the Xhaul network, DU 420-1 and 420-2 and CU 420-3 may be connected using a wireless Xhaul link and may be connected based on a multi-hop scheme. The core network may include UPF / AMF 410-1 (or S-GW / MME), PDN-GW 410-2, etc. UPF / AMF 410-1 may refer to a communication node including UPF and AMF, and S-GW / MME may refer to a communication node including S-GW and MME. The BBU block 450 may be located in the UPF / AMF 410-1 and may be connected to the CU 420-3 via a wired link.

[0115] The first DU 420-1 of the Xhaul network may be connected to the TRP 430 using a wired link. Alternatively, the first DU 420-1 may be integrated into the TRP 430. The second DU 420-2 may be connected to each of the first DU 420-1 and the CU 420-3 using a wireless link (e.g., a wireless Xhaul link), and the CU 420-3 may be connected to a terminal communication node (e.g., UPF / AMF 410-1) of the core network using a wired link. In the Xhaul network, the CU 420-3 connected to the terminal communication node of the core network may be referred to as an "aggregator". The function of the aggregator may be performed by the UPF / AMF 410-1.

[0116] The communication between DU 420-1 and 420-2 and CU 420-3 can be performed using a communication protocol for an Xhaul link (hereinafter referred to as "Xhaul protocol"), which is different from an access protocol (e.g., a communication protocol for communication between a terminal 440 and a TRP 430 (or a macro base station, a small base station)). Data packets to which the Xhaul protocol is applied can be transmitted to each of the core network and the access network through the Xhaul link. Here, the packet may be control information, data, etc.

[0117] The TRP 430 can provide communication services to the terminal 440 using an access protocol (e.g., 4G communication protocol, 5G communication protocol), and can be connected to the first DU 420-1 using a wired link. The TRP 430 can support long-range radio transmission and reception functions among all functions of the communication protocol, and the baseband processing function for the TRP 430 can be performed by the BBU block 450. The link between the TRP 430 that performs long-range radio transmission and reception functions and the BBU block 450 that performs the baseband processing function (e.g., "TRP 430-first DU 420-1-second DU 420-2-CU 420-3-BBU block 450 (or UPF / AMF 410-1)") can be referred to as a "fronthaul link". For example, the fronthaul link can be configured differently depending on the location of the BBU block 450 that performs the baseband processing function.

[0118] Figure 5 is a conceptual diagram illustrating a second exemplary embodiment of an integrated communication system.

[0119] Reference Figure 5 The integrated communication system may include an access network, an Xhaul network, and a core network. The Xhaul network may be located between the access network and the core network and may support communication between the access network and the core network. The communication nodes belonging to the integrated communication system may be configured to communicate with Figure 2 The communication nodes 200 shown are the same or similar. The access network may include a macro base station 530, a small base station 540, a TRP 550, a terminal 560-1, 560-2 and 560-3, etc. The Xhaul network may include a plurality of communication nodes 520-1, 520-2, 520-3, 520-4, 520-5 and 520-6. The communication nodes constituting the Xhaul network may be referred to as "DU" or "CU". In the Xhaul network, DU 520-1, 520-2, 520-3, 520-4 and 520-5 and CU 520-6 may be connected using a wireless Xhaul link and may be connected based on a multi-hop scheme. The BBU block 570 may be located in one of the plurality of CU / DU 520-1, 520-2, 520-3, 520-4, 520-5 and 520-6. For example, the BBU block 570 may be located in the fifth DU 520-5. The core network may include UPF.AMF 510-1 (or S-GW / MME), PDN-GW 510-2, etc. UPF / AMF 510-1 may refer to a communication node including UPF and AMF, and S-GW / MME may refer to a communication node including S-GW and MME.

[0120] The first DU 520-1 of the Xhaul network may be connected to the macro base station 530 using a wired link, or may be integrated into the macro base station 530. The second DU 520-2 of the Xhaul network may be connected to the small base station 540 using a wired link, or may be integrated into the small base station 540. The fourth DU 520-4 of the Xhaul network may be connected to the TRP 550 using a wired link, or may be integrated into the TRP 550.

[0121] CU 520-6 can be connected to a terminal communication node (e.g., UPF / AMF510-1) of a core network using a wired link. CU 520-6 connected to a terminal communication node of a core network can be called an "aggregator". Communication between multiple CU / DUs 520-1, 520-2, 520-3, 520-4, 520-5, and 520-6 can be performed using the Xhaul protocol. Packets (e.g., data, control information) to which the Xhaul protocol is applied can be transmitted to each of the core network and the access network via the Xhaul link.

[0122] The macro base station 530 can provide communication services to the first terminal 560-1 using an access protocol (e.g., 4G communication protocol, 5G communication protocol), and can be connected to the first DU 520-1 via a wired link. The macro base station 530 can be connected to the core network via an Xhaul network, and the link of "macro base station 530-first DU 520-1-CU 520-6-UPF / AMF 510-1" can be referred to as a "backhaul link". The small base station 540 can provide communication services to the second terminal 560-2 using an access protocol (e.g., 4G communication protocol, 5G communication protocol), and can be connected to the second DU 520-2 using a wired link. The small base station 540 can be connected to the core network via an Xhaul network, and the link of "small base station 540-second DU 520-2-third DU 520-3-CU520-6-UPF / AMF 510-1" can be referred to as a "backhaul link".

[0123] The TRP 550 may provide a communication service to the third terminal 560-3 using an access protocol (e.g., a 4G communication protocol, a 5G communication protocol), and may be connected to the fourth DU 520-4 using a wired link. The TRP 550 may support a long-range radio transmission and reception function among all functions of the communication protocol, and a baseband processing function for the TRP 550 may be performed by the BBU block 570. The link between the TRP 550 that performs the long-range radio transmission and reception function and the BBU block 570 that performs the baseband processing function (e.g., a link of "TRP 550-fourth DU 520-4-BBU block 570 (or fifth DU 520-5)") may be referred to as a "fronthaul link", and the link between the BBU block 570 and the UPF / AMF 510-1 (e.g., a link of "BBU block 570 (or fifth DU 520-5)-CU520-6-UPF / AMF 510-1") may be referred to as a "backhaul link". For example, the fronthaul link may be configured differently depending on the location of the BBU block 570 that performs the baseband processing function.

[0124] At the same time, reference Figure 4 and 5 , when the functional splitting technique is applied, the CUs 420-3 and 520-6 and the DUs 420-1, 420-2, 520-1, 520-2, 520-3, 520-4, and 520-5 may perform different functions. The CUs 420-3 and 520-6 may be gNB-CUs of the NR communication system, and the DUs 420-1, 420-2, 520-1, 520-2, 520-3, 520-4, and 520-5 may be gNB-DUs of the NR communication system. CUs 420-3 and 520-6 may control the operation of one or more of DUs 420-1, 420-2, 520-1, 520-2, 520-3, 520-4, and 520-5, and may be logical nodes that perform radio resource control (RRC) functions, service data adaptation protocol (SDAP) functions, and / or packet data convergence protocol (PDCP) functions. DUs 420-1, 420-2, 520-1, 520-2, 520-3, 520-4, and 520-5 may be logical nodes that perform radio link control (RLC) functions, medium access control (MAC) functions, and / or physical (PHY) functions (e.g., certain PHY functions).

[0125] One DU 420-1, 420-2, 520-1, 520-2, 520-3, 520-4, or 520-5 may support one or more cells, and one cell may support one DU 420-1, 420-2, 520-1, 520-2, 520-3, 520-4, or 520-5. Operations (e.g., certain operations) of the DUs 420-1, 420-2, 520-1, 520-2, 520-3, 520-4, and 520-5 may be controlled by the CUs 420-3 and 520-6, and communication between the DUs 420-1, 420-2, 520-1, 520-2, 520-3, 520-4, and 520-5 and the CUs 420-3 and 520-6 may be performed through an F1 interface.

[0126] Depending on the configuration, role and / or attribute of the node for functional division, the DU 420-2, 520-3 and 520-5 for relay may be present in the communication part between the DU 420-1, 520-1, 520-2 and 520-4 and the CU 420-3 and 520-6. In this case, a relay link may be formed between the DU 420-1, 520-1, 520-2 and 520-4 and the DU 420-2, 520-3 and 520-5. The DU 420-1 and 520-4 may be connected to the TRP 430 and 550 wirelessly or wired. The DU 520-1 and 520-2 may be configured to be integrated with the base station 530 and 540.

[0127] Figure 6 The present invention is a concept showing a first exemplary embodiment of a communication method based on beamforming in a communication system.

[0128] Reference Figure 6 , the communication system may include base stations 611, 612, and 613, terminals 621 and 622, etc., and the communication nodes (e.g., base stations, terminals) may perform communication based on a beamforming scheme. For example, each of the base stations 611, 612, and 613 may communicate using multiple beams (e.g., beams #1 to #4), and each of the terminals 621 and 622 may also communicate using multiple beams (e.g., beams #1 to #4).

[0129] The operating state of the first terminal 621 may be a state in which the connection establishment with the first base station 611 is completed. For example, the operating state of the first terminal 621 may be a radio resource control (RRC) connection state or an RRC inactive state. Alternatively, the first terminal 621 may operate in an RRC idle state within the service area of ​​the first base station 611. The operating state of the second terminal 622 may be a state in which the connection establishment with the second base station 612 or the third base station 613 is completed. For example, the operating state of the second terminal 622 may be an RRC connection state or an RRC inactive state. Alternatively, the second terminal 622 may operate in an RRC idle state within the service area of ​​the second base station 612 or the third base station 613.

[0130] The base stations 611, 612, and 613 may support a mobility function, and thus may ensure the mobility of the terminals 621 and 622 between the base stations 611, 612, and 613. The signals received from the terminals 621 and 622 may be used by the base stations 611, 612, and 613 to select the best beam.

[0131] A beam pair (e.g., transmit beam (beam #3)-receive beam (beam #2)) may be configured between the first base station 611 and the first terminal 621, and the beam pair may be used to provide a communication service. Here, the receive beam may be a receive direction of the first terminal 621. The beam pair may be reconfigured according to a change in the quality of a radio channel between the first base station 611 and the first terminal 621. For example, the transmit beam of the first base station 611 may be changed from beam #3 to beam #2 or beam #4, and the receive beam (e.g., receive direction) of the first terminal 621 may be changed from beam #2 to beam #1, beam #3, or beam #4.

[0132] In addition, a beam pair may be configured between the second base station 612 and the second terminal 622, and a communication service may be provided using the beam pair. According to a change in the quality of a radio channel between the second base station 612 and the second terminal 622 and / or the movement of the second terminal 622, the second terminal 622 may be connected to the third base station 613 by performing a handover process, and a beam pair may be configured between the third base station 613 and the second terminal 622. That is, in order to change the beam pair, a mobility support function and a radio resource management function based on the handover process may be performed.

[0133] In order to perform mobility support functions and radio resource management functions, the base station may transmit a synchronization signal (e.g., a synchronization signal / physical broadcast channel (SS / PBCH) block) and / or a reference signal. In order to support multiple parameter sets (numerology), a frame format supporting symbols with different lengths may be configured. In this case, the terminal may perform a monitoring operation of a synchronization signal and / or a reference signal in a frame according to an initial parameter set, a default parameter set, or a default symbol length. Each of the initial parameter set and the default parameter set may be applied to a frame format applied to radio resources in which a UE common search space is configured, to a frame format applied to radio resources in which a control resource set (CORESET) #0 of an NR communication system is configured, and / or to a frame format applied to radio resources in which a burst of synchronization symbols capable of identifying a cell in an NR communication system is transmitted.

[0134] The frame format may refer to information of configuration parameters for subcarrier spacing, control channels (e.g., CORESET), symbols, time slots, and / or reference signals (e.g., configuration parameter values, offsets, indices, identifiers, ranges, periodicities, intervals, durations, etc.). The base station may notify the terminal of the frame format using system information and / or a control message (e.g., a dedicated control message).

[0135] A terminal connected to a base station may transmit a reference signal (e.g., an uplink dedicated reference signal) to the base station using resources configured by the corresponding base station. For example, an uplink dedicated reference signal may include a sounding reference signal (SRS). In addition, a terminal connected to a base station may receive a reference signal (e.g., a downlink dedicated reference signal) from the base station in resources configured by the corresponding base station. The downlink dedicated reference signal may be a channel state information reference signal (CSI-RS), a phase tracking reference signal (PT-RS), a demodulation reference signal (DM-RS), etc. Each of the base station and the terminal may perform beam management operations by monitoring a configured beam or an active beam based on a reference signal.

[0136] For example, the first base station 611 may transmit a synchronization signal and / or a reference signal so that the first terminal 621 in its service area can search for itself to perform downlink synchronization maintenance, beam configuration, or link monitoring operations. In addition, the first terminal 621 connected to the first base station 611 (e.g., a serving base station) may receive physical layer radio resource configuration information for connection configuration and radio resource management from the first base station 611. The physical layer radio resource configuration information may refer to a configuration parameter included in an RRC control message of an LTE communication system or an NR communication system. For example, the resource configuration information may include: PhysicalConfigDedicated, PhysicalCellGroupConfig, PDCCH-Config (Common), PDSCH-Config (Common), PDCCH-ConfigSIB1, ConfigCommon, PUCCH-Config (Common), PUSCH-Config (Common), BWP-DownlinkCommon, BWP-UplinkCommon, ControlResourceSet, RACH-ConfigCommon, RACH-ConfigDedicated, RadioResourceConfigCommon, RadioResourceConfigDedicated, ServingCellConfig, ServingCellConfigCommon, and the like.

[0137] The radio resource configuration information may include parameter values, such as the configuration (or allocation) periodicity of the signal (or radio resource) according to the frame format (or transmission frequency) of the base station, the time resource allocation information for transmission, the frequency resource allocation information for transmission, the transmission (or allocation) time, etc. In order to support a variety of parameter sets, the frame format of the base station may mean a frame format having different symbol lengths according to a plurality of subcarrier intervals within one radio frame. For example, the number of symbols constituting each of a pico slot, a slot, and a subframe present in one radio frame (e.g., a 10 ms frame) may be configured differently.

[0138] ●Configuration information of the base station's transmission frequency and frame format

[0139] ■ Transmission frequency information: information about all transmission carriers in the base station (i.e., cell-specific transmission frequencies), information about the BWP in the base station, information about the transmission reference time of the transmission frequencies in the base station or the time difference therebetween (e.g., a transmission period or offset parameter indicating the transmission reference time (or time difference) of a synchronization signal, etc.

[0140] ■Frame format information: Configuration parameters of mini-slots, time slots, and subframes supporting multiple symbol lengths according to SCS

[0141] ● Downlink reference signal configuration information (e.g., channel state information reference signal (CSI-RS), common reference signal (Common-RS), etc.)

[0142] ■ Configuration parameters such as the transmission period, transmission position, code sequence or masking (or scrambling) sequence of the reference signal that is typically applied within the coverage area of ​​a base station (or beam).

[0143] ●Configuration information of uplink control signal

[0144] ■ Configuration parameters, such as sounding reference signal (SRS), uplink beam scanning (or beam monitoring) reference signal (RS), uplink unlicensed radio resources, or uplink radio resources for random access (or RA preamble), etc.

[0145] ● Configuration information of the physical downlink control channel (eg, PDCCH)

[0146] ■Configuration parameters, such as reference signals used for PDCCH demodulation, beam-common reference signals (for example, reference signals that can be received by all terminals within the beam coverage), beam scanning (or beam monitoring) reference signals, reference signals used for channel estimation, etc.

[0147] ● Configuration information of the physical uplink control channel (eg, PUCCH)

[0148] ●Scheduling request signal configuration information

[0149] ●Configuration information of feedback (ACK or NACK) transmission resources used to support HARQ functions, etc.

[0150] ● Number of antenna ports, antenna array information, beam configuration or beam index mapping information used to apply beamforming technology

[0151] ● Configuration information of downlink and / or uplink signals (or uplink access channel resources) for beam scanning (or beam monitoring)

[0152] ●Configuration information of parameters used for beam configuration, beam recovery, beam reconfiguration or radio link reconstruction operations, beam change operations within the same base station, received signals that trigger switching to a beam of another base station, timers for controlling the above operations, etc.

[0153] In the case of a radio frame format that supports multiple symbol lengths to support multiple parameter sets, the configuration (or allocation) periodicity of parameters, time resource allocation information, frequency resource allocation information, transmission time and / or allocation time (which constitute the above information) can be information configured for each corresponding symbol length (or subcarrier spacing).

[0154] In the following exemplary embodiments, "resource configuration (Resource-Config) information" may be a control message including one or more parameters among the radio resource configuration information of the physical layer. In addition, "resource configuration information" may mean the attributes and / or configuration values ​​(or ranges) of the information elements (or parameters) transmitted by the control message. The information elements (or parameters) transmitted by the control message may be radio resource configuration information commonly applied to the entire coverage of the base station (or beam), or may be radio resource configuration information specifically allocated to a specific terminal (or a specific terminal group).

[0155] The configuration information included in the "resource configuration information" may be transmitted through one control message or different control messages according to the attributes of the configuration information. The beam index information may not be able to clearly express the index of the transmit beam and the index of the receive beam. For example, the beam index information may be expressed using a reference signal associated with or mapped to an index (or identifier) ​​of a transmission configuration indicator (TCI) state for beam management or a corresponding beam index.

[0156] Therefore, the first terminal 621 operating in the RRC connection state can receive communication services through the beam (e.g., beam pair) configured between the first terminal 621 and the first base station 611. For example, when communication services are provided using beam #3 of the first base station 611 and beam #2 of the first terminal 621, the first terminal 621 can perform a search operation or a monitoring operation on the radio channel by using a reference signal and / or a synchronization signal transmitted through beam #3 of the first base station 611. Here, the expression that a communication service is provided through a beam may mean sending and receiving packets through an active beam in one or more configured beams. In the NR communication system, the expression that a beam is activated may mean that the configured TCI state is activated.

[0157] The terminal 621 may operate in an RRC idle state or an RRC inactive state. In this case, the terminal 621 may perform a search operation (e.g., a monitoring operation) of a downlink channel by using (one or more) parameters obtained from system information or common resource configuration information. In addition, the terminal 621 operating in an RRC idle state or an RRC inactive state may attempt to access by using an uplink channel (e.g., a random access channel or a physical layer uplink control channel). Alternatively, the terminal 621 may transmit control information by using an uplink channel.

[0158] The terminal 621 may identify or detect a radio link problem by performing a radio link monitoring (RLM) operation. Here, the expression that a radio link problem is detected may mean that there is a problem with the configuration or maintenance of the physical layer synchronization of the radio link. For example, the expression that a radio link problem is detected may mean that it is detected that the physical layer synchronization between the base station 611 and the terminal 621 is not maintained during a preconfigured time. When a radio link problem is detected, the terminal may perform a recovery operation of the radio link. When the radio link is not restored, the terminal may declare a radio link failure (RLF) and perform a reconstruction process of the radio link.

[0159] The process for detecting physical layer problems of the radio link, the process for restoring the radio link, the process for detecting (or declaring) a radio link failure, and the process for reestablishing the radio link according to the RLM operation can be performed by the functions of layer 1 (e.g., physical layer), layer 2 (e.g., MAC layer, RLC layer, PDCP layer, etc.) and / or layer 3 (e.g., RRC layer) of the radio protocol.

[0160] The physical layer of the terminal can monitor the radio link by receiving a downlink synchronization signal (e.g., a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a SS / PBCH block) and / or a reference signal. In this case, the reference signal can be a base station common reference signal, a beam common reference signal, or a terminal (or terminal group) specific reference signal (e.g., a dedicated reference signal assigned to the terminal (or terminal group)). Here, the common reference signal can be used for channel estimation operations for all terminals located within the corresponding base station or beam coverage (or service area). The dedicated reference signal can be used for channel estimation operations for a specific terminal or a specific terminal group located within the base station or beam coverage.

[0161] Accordingly, when the base station or beam (for example, a beam configured between the base station and the terminal) changes, the dedicated reference signal used for beam management may change. The beam may be changed based on (one or more) configuration parameters between the base station and the terminal. A process for changing the configured beam may be required. The statement that the beam is changed in the NR communication system may mean that the index (or identifier) ​​of the TCI state is changed to the index of another TCI state, the TCI state is newly configured, or the TCI state is changed to an active state. The base station may transmit system information including configuration information of the common reference signal to the terminal. The terminal may obtain the common reference signal based on the system information. During a switching process, a synchronization reconfiguration process, or a connection reconfiguration process, the base station may transmit a dedicated control message containing configuration information of the common reference signal to the terminal.

[0162] In order to provide service continuity between the base station and the terminal, a method may be considered in which the base station allocates multiple beams to one terminal to provide service. Figure 6 In the exemplary embodiment shown, base stations 611, 612, and 613 may allocate multiple beams to terminals 621 and 622. Base station 611 may allocate beams #2 to #4 to terminal 621. Base station 612 may allocate beams #3 and #4 to terminal 622. The process of allocating multiple beams may be performed in consideration of the moving speed, moving direction, and location information of the terminal, radio channel quality, and / or beam interference. For example, when the moving speed of terminal 621 is low, base station 611 may allocate continuous beams #2 and #3 to terminal 621. When the moving speed of terminal 621 is high, base station 611 may allocate non-continuous beams #2 and #4 to terminal 621.

[0163] The base station 612 may allocate beams #3 and #4 to the terminal 622, and provide services to the terminal 622 by using beams #3 and #4. In this case, the terminal 622 may move from the coverage of the base station 612 to the coverage of the base station 613. When the cell (or sector) of the base station 612 is different from the cell (or sector) of the base station 613, the terminal 622 may perform a handover procedure. In the handover procedure, the base station 612 may transmit a handover (or mobility) control message containing beam configuration information of the base station 613 (e.g., configuration information of beams #1 and #2) to the terminal 622. The terminal 622 may receive the beam configuration information of the base station 613 from the base station 612.

[0164] The beam configuration information may include an index of a transmit beam and / or receive beam configured according to a result of a beam monitoring operation or a beam measurement operation, configuration information of each beam (e.g., transmission power, beam width, vertical angle, horizontal angle, etc.), transmission and / or reception timing information of each beam (e.g., subframe index, slot index, mini-slot index, symbol index, offset), configuration information of a reference signal of each beam (e.g., sequence, index), etc. In order to allocate multiple beams, a control message including configuration information of multiple beams, information on the mobility state of the terminal (e.g., moving speed, moving direction, location information, etc.), beam monitoring (or measurement) results, etc. may be sent and received between the base stations 612 and 613 and the terminal 622. Here, the control message may be a control signaling message for performing switching.

[0165] Base station 612 may allocate beams #3 and #4 to terminal 622, and provide services to terminal 622 by using beams #3 and #4. In this case, terminal 622 may move from the coverage of base station 612 to the coverage of base station 613. When the cell (or sector) of base station 612 is the same as the cell (or sector) of base station 613, a process for changing a transmission node within the cell may be performed. In this case, base stations 612 and 613 may be transmission nodes (e.g., RRH, TRP) to which functional partitioning is applied. For example, base stations 612 and 613 may support (one or more) functions of (some) layers among the physical layer (i.e., PHY layer), MAC layer, RLC layer, PDCP layer, adaptation layer, and RRC layer. Here, the adaptation layer may be a layer higher than the PDCP layer. The adaptation layer may perform a function of mapping between a QoS flow and a data radio bearer (DRB) and / or a function of marking a QoS flow identifier for a downlink (or uplink) packet.

[0166] When base stations 612 and 613 belonging to the same cell support (one or more) functions of certain layer(s) among the radio protocol layers except the RRC layer, the terminal 622 can perform the change process from base station 612 to base station 613 by exchanging MAC layer control messages (for example, MAC control elements (CE) or control protocol data units (PDUs), etc.) without exchanging RRC layer control messages.

[0167] The layer(s) performing the function of generating, sending or receiving the control message for changing the base station may be determined according to the layer(s) included in the base stations 612 and 613. For example, when the base stations 612 and 613 include from the physical layer to the MAC layer or from the physical layer to the RLC layer, the control message for changing the base station may be generated, sent or received in a layer higher than the MAC layer (or the RLC layer). The MAC function (or the MAC function and the RLC function) of the base stations 612 and 613 and the terminal 622 may be reconfigured after the reset.

[0168] When the base stations 612 and 613 support only certain (some) functions of the MAC layer, or when the base stations 612 and 613 support only (one or more) functions of the physical layer, a control message for changing the base station may be generated, sent, or received by the MAC layer. The process for changing the base station may be performed without resetting the MAC functions of the base stations 612 and 613 and the terminal 622.

[0169] In the process of changing the base station, information for identifying the base station may be delivered to the terminal 622 by using a control message of the RRC layer, a control message of the MAC layer, or a physical layer control channel according to the layer(s) included in the base stations 612 and 613. In an exemplary embodiment, the control message of the RRC layer may be referred to as an "RRC control message" or "RRC message", the control message of the MAC layer may be referred to as a "MAC control message" or "MAC message", and the physical layer control channel may be referred to as a "PHY control channel", "PHY control message" or "PHY message".

[0170] Here, the information for identifying the base station may include one or more of a base station identifier, reference signal information, reference symbol information, configured beam information, and configured TCI state information. The reference signal information (or reference symbol information) may include configuration information (e.g., radio resources, sequence, index) of a reference signal allocated to each base station and / or configuration information (e.g., radio resources, sequence, index) of a dedicated reference signal allocated to a terminal.

[0171] Here, the radio resource information of the reference signal may include time domain resource information (e.g., frame index, subframe index, time slot index, symbol index) and frequency domain resource information (e.g., a parameter indicating the relative position or absolute position of a subcarrier). The parameter indicating the radio resource of the reference signal may be a resource element (RE) index, a resource set index, a resource block (RB) index, a subcarrier index, etc. The RB index may be a physical resource block (PRB) index or a common resource block (CRB) index.

[0172] In the following exemplary embodiments, the reference signal information may include transmission periodicity information, sequence information (e.g., code sequence), masking information (e.g., scrambling information), radio resource information, and / or index information of the reference signal. The reference signal identifier may mean a parameter (e.g., resource ID, resource set ID) for identifying each of a plurality of reference signal information. The reference signal information may refer to configuration information of the reference signal.

[0173] The configured beam information may include a configured beam index (or identifier), a configured TCI state index (or identifier), configuration information of each beam (e.g., transmission power, beam width, vertical angle, horizontal angle), transmit and / or receive timing information of each beam (e.g., subframe index, time slot index, mini-time slot index, symbol index, offset), reference signal information corresponding to each beam, and a reference signal identifier.

[0174] In an exemplary embodiment, the base station can be a base station installed in the air. For example, the base station can be installed on an unmanned aerial vehicle (such as a drone), a manned aircraft or a satellite.

[0175] The terminal can receive configuration information of the base station (for example, identification information of the base station) from the base station through one or more of RRC messages, MAC messages and PHY messages, and can identify the base station used by the terminal to perform beam monitoring operations, radio access operations and / or control (or data) packet sending and receiving operations.

[0176] When multiple beams are configured, the multiple beams can be used to perform communication between the base station and the terminal. In this case, the number of downlink beams may be the same as the number of uplink beams. Alternatively, the number of downlink beams may be different from the number of uplink beams. For example, the number of downlink beams may be two or more, and the number of uplink beams may be one.

[0177] When multiple beams are configured, one or some of the multiple beams can be used to perform communication between the base station and the terminal, and the remaining beams can be configured as (one or more) reserved beams or (one or more) candidate beams. For example, control information and data may not be transmitted through (one or more) reserved beams and / or (one or more) candidate beams. Multiple beams can be classified into main beams, sub-beams, and reserved beams (or candidate beams). In the NR communication system, configuring multiple beams may mean configuring them by classifying the configured TCI state identifiers (IDs) into main TCI states, auxiliary TCI states, and reserved TCI states.

[0178] For example, a main beam (e.g., a beam for a main TCI state ID) may mean a beam capable of sending and receiving data as well as control information. An auxiliary beam (e.g., a beam for an auxiliary TCI state ID or a beam for a deactivated TCI state ID) may mean a beam capable of sending and receiving data excluding control information. The expression of excluding control information may mean that the control signaling is constrained by the physical layer, layer 2 (e.g., MAC layer, RLC layer, PDCP layer) and / or layer 3 (e.g., RRC layer) for the corresponding layer; may mean that the control signaling is partially constrained according to the functions of the physical layer, layer 2 and / or layer 3; or the control signaling is constrained according to the type of control message.

[0179] Control messages (e.g., RRC messages, MAC messages, and PHY messages) may be control messages for discontinuous transmission / reception operations (e.g., discontinuous reception (DRX) operations, discontinuous transmission (DTX) operations), retransmission operations, connection configuration / management operations, measurement / reporting operations, paging operations, and / or access operations.

[0180] The reserved (or candidate) beam (e.g., a beam for reserving a TCI state ID or a beam for deactivating a TCI state ID) may not be used for transmission and reception of data and / or control information. The reserved (or candidate) beam may be a beam used for beam measurement / reporting operations and beam monitoring operations for beam matching (or configuration) of a base station and / or terminal.

[0181] Therefore, the measurement result for the reserved (or candidate) beam can be reported through the main beam or the auxiliary beam. The measurement / reporting operation for the reserved (or candidate) beam can be performed based on the preconfigured (one or more) parameters. Alternatively, the measurement / reporting operation for the reserved (or candidate) beam can be performed according to the determination of the terminal or event conditions. The measurement / reporting operation for the reserved (or candidate) beam can be performed periodically or aperiodically.

[0182] The result of the measurement operation (e.g., beam monitoring operation) for the reserved (or candidate) beam may be reported through a physical layer control channel (e.g., PUCCH) and / or a MAC message (e.g., MAC CE, control PDU). Here, the result of the beam monitoring operation may be a measurement result for one or more beams (or beam groups). For example, the result of the beam monitoring operation may be a measurement result of a beam (or beam group) according to a beam scanning operation of the base station.

[0183] The base station can obtain the result of the beam measurement operation or the beam monitoring operation from the terminal, and can change the properties of the beam or the properties of the TCI state based on the result of the beam measurement operation or the beam monitoring operation. According to the properties of the beam, it can be classified into a main beam, an auxiliary beam, a reserved (or candidate) beam, an active beam, and a deactivated beam. According to the properties of the TCI state, the TCI state can be classified into a main TCI state, an auxiliary TCI state, a reserved (or candidate) TCI state, a service TCI state, a configured TCI state, an active TCI state, and a deactivated TCI state. Each of the main TCI state and the auxiliary TCI state can be assumed to be an active TCI state and a service TCI state. The reserved (or candidate) TCI state can be assumed to be a deactivated TCI state or a configured TCI state.

[0184] The process of changing the beam (or TCI state) attributes can be controlled by the RRC layer and / or the MAC layer. When the process for changing the beam (or TCI state) attributes is controlled by the MAC layer, the MAC layer can notify the upper layer of the information about the change in the beam (or TCI state) attributes. The information about the change in the beam (or TCI state) attributes can be transmitted to the terminal via a MAC message and / or a physical layer control channel (e.g., PDCCH). The information about the change in the beam (or TCI state) attributes can be included in the downlink control information (DCI) or the uplink control information (UCI). The information about the change in the beam (or TCI state) attributes can be represented as a separate indicator or field.

[0185] The terminal may request to change the attributes of the TCI state based on the result of the beam measurement operation or the beam monitoring operation. The terminal may send control information (or feedback information) requesting to change the attributes of the TCI state to the base station by using one or more of a PHY message, a MAC message, and an RRC message. The control information (or feedback information, control message, control channel) requesting to change the attributes of the TCI state may be configured using one or more of the above-configured beam information.

[0186] The change of the attribute of the beam (or TCI state) may mean a change from an active beam to a deactivated beam, a change from a deactivated beam to an active beam, a change from a main beam to an auxiliary beam, a change from an auxiliary beam to a main beam, a change from a main beam to a reserved (or candidate) beam, or a change from a reserved (or candidate) beam to a main beam. The process of changing the attribute of the beam (or TCI state) may be controlled by the RRC layer and / or the MAC layer. The process of changing the attribute of the beam (or TCI state) may be performed through partial cooperation between the RRC layer and the MAC layer.

[0187] When multiple beams are allocated, one or more of the multiple beams may be configured as (one or more) beams for transmitting a physical layer control channel. For example, a main beam and / or an auxiliary beam may be used for sending and receiving a physical layer control channel (e.g., a PHY message). Here, the physical layer control channel may be a PDCCH or a PUCCH. The physical layer control channel may be used to transmit one or more of the following items: scheduling information (e.g., radio resource allocation information, modulation and coding scheme (MCS) information), feedback information (e.g., channel quality indication (CQI), precoding matrix indicator (PMI), HARQ ACK, HARQ NACK), resource request information (e.g., scheduling request (SR)), results of a beam monitoring operation for supporting beamforming functions, TCI state ID, and measurement information of an active beam (or deactivated beam).

[0188] The physical layer control channel may be configured to be transmitted through the main beam of the downlink. In this case, feedback information may be sent and received through the main beam, and data scheduled by the control information may be sent and received through the auxiliary beam. The physical layer control channel may be configured to be transmitted through the main beam of the uplink. In this case, resource request information (e.g., SR) and / or feedback information may be sent and received through the main beam.

[0189] In the process of allocating multiple beams (or configuring the TCI state), the allocated (or configured) beam index, information indicating the interval between beams, and / or information indicating whether continuous beams are allocated may be sent and received through a signaling process between the base station and the terminal. The signaling process of the beam allocation information may be performed differently according to the state information of the terminal (e.g., moving speed, moving direction, location information) and / or the quality of the radio channel. The base station may acquire the state information of the terminal from the terminal. Alternatively, the base station may obtain the state information of the terminal by another method.

[0190] The radio resource information may include (one or more) parameters indicating frequency domain resources (e.g., center frequency, system bandwidth, PRB index, number of PBRs, CRB index, number of CRBs, subcarrier index, frequency offset, etc.) and (one or more) parameters indicating time domain resources (e.g., radio frame index, subframe index, transmission time interval (TTI), slot index, mini-slot index, symbol index, time offset, and periodicity, length or window of a transmission period (or reception period)). In addition, the radio resource information may also include a frequency hopping pattern of the radio resource, information for beamforming (e.g., beam shaping) operations (e.g., beam configuration information, beam index), and information about resources occupied according to characteristics of a code sequence (or bit sequence, signal sequence).

[0191] The name of the physical layer channel and / or the name of the transmission channel may vary depending on the type (or attribute) of data, the type (or attribute) of control information, the transmission direction (e.g., uplink, downlink, sidelink), etc.

[0192] The reference signal for beam (or TCI state) or radio link management may be a synchronization signal (e.g., PSS, SSS, SS / PBCH block), CSI-RS, PT-RS, SRS, DM-RS, etc. The reference parameter(s) for the reception quality of the reference signal for beam (or TCI state) or radio link management may include a measurement time unit, a measurement time interval, a reference value indicating improvement in reception quality, a reference value indicating degradation in reception quality, etc. Each of the measurement time unit and the measurement time interval may be configured in units of absolute time (e.g., milliseconds, seconds), TTI, symbol, slot, frame, subframe, scheduling periodicity, operation periodicity of a base station, or operation periodicity of a terminal.

[0193] The reference value indicating the change in reception quality can be configured as an absolute value (dBm) or a relative value (dB). In addition, the reception quality of the reference signal used for beam (or TCI state) or radio link management can be expressed as reference signal received power (RSRP), reference signal received quality (RSRQ), received signal strength indicator (RSSI), signal-to-noise ratio (SNR), signal-to-interference ratio (SIR), etc.

[0194] At the same time, in the NR communication system using millimeter frequency band, the flexibility of channel bandwidth operation for packet transmission can be ensured based on the concept of bandwidth part (BWP). The base station can be configured with up to 4 BWPs, and the bandwidths of these BWPs to the terminal are different. For the downlink and uplink, the BWP can be configured independently. That is, the downlink BWP can be distinguished from the uplink BWP. Each BWP can have different subcarrier spacing and different bandwidths. For example, the BWP can be configured as follows.

[0195] Figure 7 is a conceptual diagram illustrating a first exemplary embodiment of a method for configuring a bandwidth part (BWP) in a communication system.

[0196] like Figure 7As shown, multiple bandwidth parts (e.g., BWP#1 to #4) can be configured within the system bandwidth of the base station. BWP#1 to #4 can be configured to be no larger than the system bandwidth of the base station. The bandwidths of BWP#1 to #4 can be different, and different subcarrier spacings can be applied to BWP#1 to #4. For example, the bandwidth of BWP#1 can be 10 MHz, and BWP#1 can have a subcarrier spacing of 15 kHz. The bandwidth of BWP#2 can be 40 MHz, and BWP#2 can have a subcarrier spacing of 15 kHz. The bandwidth of BWP#3 can be 10 MHz, and BWP#3 can have a subcarrier spacing of 30 kHz. The bandwidth of BWP#4 can be 20 MHz, and BWP#4 can have a subcarrier spacing of 60 kHz.

[0197] BWP can be classified into an initial BWP (e.g., a first BWP), an active BWP (e.g., an activated BWP), and a default BWP. The terminal can perform an initial access procedure (e.g., an access procedure) with the base station in the initial BWP. One or more BWPs can be configured through an RRC connection configuration message, and one of the one or more BWPs can be configured as an active BWP. Each of the terminal and the base station can send and receive packets in an active BWP among the configured BWPs. Therefore, the terminal can perform a monitoring operation on a control channel for packet transmission and reception in an active BWP.

[0198] The terminal may switch the operating BWP from the initial BWP to the active BWP or the default BWP. Alternatively, the terminal may switch the operating BWP from the active BWP to the initial BWP or the default BWP. The BWP switching operation may be performed based on an indication or a timer of the base station. The base station may transmit information indicating the BWP switching to the terminal using one or more of an RRC message, a MAC message (e.g., a MAC control element (CE)), and a PHY message (e.g., a DCI). The terminal may receive information indicating the BWP switching from the base station, and may switch the operating BWP of the terminal to the BWP indicated by the received information.

[0199] When no random access (RA) resources are configured in the active uplink (UL) BWP in the NR communication system, the terminal may switch the operating BWP of the terminal from the active UL BWP to the initial UL BWP in order to perform a random access procedure. The operating BWP may be a BWP in which the terminal performs communication (e.g., transmission and reception operations of signals and / or channels).

[0200] A measurement operation (e.g., a monitoring operation) for beam (or TCI state) or radio link management may be performed at the base station and / or the terminal. The base station and / or the terminal may perform a measurement operation (e.g., a monitoring operation) according to (one or more) parameters configured for the measurement operation (e.g., the monitoring operation). The terminal may report a measurement result according to (one or more) parameters configured for the measurement report.

[0201] When the reception quality of the reference signal according to the measurement result meets the preconfigured reference value and / or the preconfigured timer condition, the base station can determine whether to perform a beam (or radio link) management operation, a beam switching operation, or a beam deactivation (or activation) operation according to the beam blocking situation. When it is determined to perform a specific operation, the base station can transmit a message triggering the execution of the specific operation to the terminal. For example, the base station can transmit a control message to the terminal for instructing the terminal to perform a specific operation. The control message may include configuration information for the specific operation.

[0202] When the reception quality of the reference signal according to the measurement result meets the preconfigured reference value and / or the preconfigured timer condition, the terminal can report the measurement result to the base station. Alternatively, the terminal can transmit a control message triggering a beam (or radio link) management operation, a beam switching operation (or a TCI state ID change operation, an attribute change operation) or a beam deactivation operation (or a beam activation operation) to the base station. The control message can request the execution of a specific operation.

[0203] The basic process of beam (or TCI state) management through radio link monitoring may include a beam failure detection (BFD) process of the radio link, a beam restoration (BR) request process, etc. The operation of determining whether to perform a beam failure detection process and / or a beam restoration request process, the operation of triggering the execution of the beam failure detection process and / or the beam restoration request process, and the control signaling operation for the beam failure detection process and / or the beam restoration request process may be performed by one or more of the PHY layer, the MAC layer, and the RRC layer.

[0204] The process (e.g., random access process) of a terminal accessing a base station can be classified into an initial access process and a non-initial access process. A terminal operating in an RRC idle state can perform an initial access process. Alternatively, when there is no context information managed by a base station, a terminal operating in an RRC connected state can also perform an initial access process. The context information may include RRC context information, access layer (AS) configuration information (e.g., AS context information), etc. The context information may include RRC configuration information for the terminal, security configuration information for the terminal, PDCP information containing a robust header compression (ROHC) state for the terminal, an identifier (e.g., a cell radio resource temporary identifier (C-RNTI)), and an identifier of a base station that has completed connection configuration with the terminal.

[0205] In addition to the initial access procedure, the non-initial access procedure may refer to an access procedure performed by the terminal. For example, the non-initial access procedure may be performed for an access request for sending or receiving data arriving at the terminal, a connection recovery, a resource allocation request, an information transmission request based on a user (UE) request, a link reconfiguration request after a radio link failure (RLF), mobility function (e.g., handover function) support, auxiliary cell addition / change, active beam addition / change, or physical layer synchronization configuration.

[0206] The random access procedure may be performed based on an initial access procedure or a non-initial access procedure according to an operation state of the terminal.

[0207] Figure 8 is a conceptual diagram showing a first exemplary embodiment of an operation state of a terminal in a communication system.

[0208] like Figure 8 As shown, the operating state of the terminal can be classified into an RRC connected state, an RRC inactive state, and an RRC idle state. When the terminal operates in the RRC connected state or the RRC inactive state, a radio access network (RAN) (e.g., a control function block of the RAN) and a base station can store and manage RRC connection configuration information and / or context information (e.g., RRC context information, AS context information) of the corresponding terminal.

[0209] A terminal operating in an RRC connection state can receive configuration information of a physical layer control channel and / or a reference signal required for maintaining connection configuration and data transmission / reception from a base station. The reference signal can be a reference signal for demodulating data. Alternatively, the reference signal can be a reference signal for channel quality measurement or beamforming. Therefore, a terminal operating in an RRC connection state can send and receive data without delay.

[0210] When the terminal operates in the RRC inactive state, the same or similar mobility management functions / operations as those supported in the RRC idle state can be supported for the corresponding terminal. That is, when the terminal operates in the RRC inactive state, the data bearer for sending and receiving data may not be configured, and the function of the MAC layer may be deactivated. Therefore, the terminal operating in the RRC inactive state may change the operating state of the terminal from the RRC inactive state to the RRC connected state by performing a non-initial access process to transmit data. Alternatively, the terminal operating in the RRC inactive state may transmit data with a limited size, data with a limited service quality, and / or data associated with a limited service.

[0211] When the terminal operates in the RRC idle state, there may be no connection configuration between the terminal and the base station, and the RRC connection configuration information and / or context information (e.g., RRC context information, AS context information) of the terminal may not be stored in the RAN (e.g., the control function block of the RAN) and the base station. In order to change the operating state of the terminal from the RRC idle state to the RRC connected state, the terminal may perform an initial access procedure. Alternatively, when performing the initial access procedure, the operating state of the terminal may be changed from the RRC idle state to the RRC inactive state according to the determination of the base station.

[0212] The terminal may transition from the RRC idle state to the RRC inactive state by performing an initial access procedure or a separate access procedure defined for the RRC inactive state. When limited services are provided to the terminal, the operating state of the terminal may transition from the RRC idle state to the RRC inactive state. Alternatively, depending on the capabilities of the terminal, the operating state of the terminal may transition from the RRC idle state to the RRC inactive state.

[0213] The control function block and / or the base station of the RAN may configure (one or more) conditions for transitioning to the RRC inactive state by considering one or more of the type, capability, and service of the terminal (e.g., the service currently being provided and the service to be provided), and may control the operation for transitioning to the RRC inactive state based on (one or more) configured conditions. When the base station allows the transition to the RRC inactive state or when configured to allow the transition to the RRC inactive state, the operation state of the terminal may transition from the RRC connected state or the RRC idle state to the RRC inactive state.

[0214] Fig. 9 is a sequence diagram showing a first exemplary embodiment of a random access procedure in a communication system.

[0215] Reference Fig. 9 , the communication system may include a base station, a terminal, etc. The base station may be Figure 1 The base stations 110-1, 110-2, 110-3, 120-1 or 120-2 are shown, and the terminal may be Figure 1 The base station and the terminal may be configured to communicate with the terminal 130-1, 130-2, 130-3, 130-4, 130-5 or 130-6 shown in FIG. Figure 2 The communication nodes shown are the same or similar. The random access procedure can be performed in four steps.

[0216] The base station may transmit system information and / or a control message including configuration information of radio resources (e.g., uplink radio resources) for a random access procedure to the terminal (S901). The terminal may obtain configuration information of radio resources for a random access procedure by receiving the system information and / or the control message from the base station. The system information may be common system information for a plurality of base stations or base station-specific system information (e.g., cell-specific system information). The control message may be a dedicated control message.

[0217] System information may be configured for each base station, for each beam group, or for each beam. System information may include allocation information of radio resources (e.g., uplink radio resources) for a random access procedure. Configuration information of radio resources for a random access procedure may include one or more of the following items: transmission frequency information of the physical layer, system bandwidth information (or BWP configuration information), subcarrier spacing information, beam configuration information according to beamforming technology (e.g., beam width, beam index), variable radio resource configuration information in the frequency domain and / or time domain (e.g., radio resource reference value, offset), and inactive (or unused) radio resource area / interval information.

[0218] The terminal may transmit an RA message 1 (RA-MSG1) including an RA preamble to the base station using radio resources configured by the base station (e.g., a physical random access channel (PRACH)) (S902). In the four-step random access procedure, the message 1 including the RA preamble may be referred to as "RA MSG1", and the RA preamble in the four-step random access procedure may be referred to as "four-step RA preamble".

[0219] The terminal may randomly select a code sequence (e.g., RA preamble, signature) defined for the random access procedure and transmit an RA MSG1 containing the selected code sequence. In a contention-based random access (CBRA) procedure, the terminal may randomly select an RA preamble. In a contention-free random access (CFRA) procedure, the base station may pre-allocate an RA preamble to the terminal. The pre-allocation of the RA preamble may mean that an index, masking information, etc. of the RA preamble for RA MSG1 is specifically allocated to the terminal. In this case, the terminal may perform a random access procedure (e.g., CFRA procedure) without competing with other terminals.

[0220] The base station may receive RA MSG1 from the terminal. The base station may generate RA MSG2 in response to RA MSG1, and may transmit RA MSG2 to the terminal (S903). In the four-step random access procedure, RA MSG2 may mean message 2, random access response (RAR), or RA response message. The base station may identify information required by the terminal based on RA MSG1 received in step S902 or the radio resource through which RA MSG1 is received. In this case, in step S903, the base station may transmit the required information to the terminal.

[0221] Identification of the required information at the terminal may mean identifying an on-demand transmission request for system information according to the request of the terminal, a transmission request for downlink data according to an update of the terminal's firmware or required software, or an uplink resource allocation request based on the information received in step S901 (e.g., a preamble code index, a specific signal sequence for uplink resource request (e.g., sequence, signature), a specific field value of an uplink control channel).

[0222] In this case, allocation information of uplink radio resources may be transmitted in step S903. Alternatively, RA MSG2 may be transmitted on a PDCCH or a physical downlink shared channel (PDSCH).

[0223] In step S903, the base station may transmit only the PDCCH (e.g., DCI) without transmitting the RA response message (e.g., RA MSG2) on the PDSCH. In this case, the corresponding DCI may include uplink resource allocation information (e.g., scheduling information), transmission timing adjustment information (e.g., timing advance (TA) value, TA command), transmission power adjustment information, backoff information, beam configuration information, TCI state information, configured scheduling (CS) state information, state transition information, PUCCH configuration information, an index of the RA MSG1 received in step S902 (e.g., an index of the RA preamble), and one or more of the uplink resource allocation information for transmitting RAMSG3 in step S904.

[0224] Here, the beam configuration information may be information indicating activation or deactivation of a specific beam. The TCI state information may be information indicating activation or deactivation of a specific TCI state. The CS state information may be information indicating activation or deactivation of radio resources allocated in the CS scheme. The state transition information may be information indicating activation or deactivation of radio resources allocated in the CS scheme. Figure 8 The state transition information may indicate a transition from a specific operating state to an RRC idle state, an RRC connected state, or an RRC inactive state. Alternatively, the state transition information may indicate the maintenance of the current operating state. The PUCCH configuration information may be allocation information of a scheduling request (SR) resource. Alternatively, the PUCCH configuration information may be information indicating activation or deactivation of an SR resource.

[0225] When the base station transmits only PDCCH (e.g., DCI) but not RA MSG2 in step S903, the terminal can recognize that RA MSG2 is not transmitted on PDSCH by using control information contained in PDCCH, DCI format contained in PDCCH and / or scheduling identifier for PDCCH transmission. The base station can transmit scheduling information of RAMSG2 to the terminal using random access (RA)-RNTI. For example, the cyclic redundancy check (CRC) of the DCI including scheduling information of RA MSG2 can be scrambled by RA-RNTI, and the corresponding DCI can be transmitted by PDCCH. In addition, the base station can transmit RA MSG2 using cell RNTI (C-RNTI). The base station can transmit RA MSG2 on PDSCH indicated by scheduling information addressed by scheduling identifier (e.g., RA-RNTI, C-RNTI). The terminal can receive RA MSG2 from the base station. The terminal can transmit RA MSG3 (i.e., message 3) containing its own information to the base station (S904). The terminal information may include one or more of the terminal's identifier, capability, attribute, mobility state, location information, reason for radio access, size information of uplink data (e.g., buffer status report (BSR)), connection configuration request information, and uplink data. In addition, in step S904, the terminal may transmit information requesting information required by the terminal to the base station.

[0226] In addition, the terminal may use RA MSG3 to transmit one or more of beam failure recovery request information, BWP switching request information, BWP deactivation / activation request information, measurement result information for a base station (or cell) in a carrier aggregation (CA) environment, and CA activation / deactivation request information. Here, when a random access procedure for beam recovery is performed after a beam failure is detected, the beam failure recovery request information may request that a beam recovery procedure be performed based on a beam measurement result. In this case, the terminal may transmit measurement result information for each beam and / or TCI status information for configuring a new beam to the base station.

[0227] Each of the BWP switching request information or the BWP deactivation / activation request information may include one or more of the active BWP switching request information based on the measurement result of the BWP, the measurement result information of the deactivated BWP, and the information about the active BWP preferred by the terminal. In addition, the RA MSG3 may include one or more of the BWP identifier, the base station (or cell) identifier, and the configured beam information (for example, the SS / PBCH index that can identify the beam, the TCI state, or the CSI-RS index). The RA MSG3 can be transmitted in the form of a MAC CE or an RRC message.

[0228] When RA MSG2 is received based on PDCCH (or DCI) in step S903, the terminal may perform an operation according to (one or more) information elements included in PDCCH (or DCI). The (one or more) information elements included in PDCCH (or DCI) may include one or more of the information request information for changing the operating state of the terminal, the request information for maintaining the operating state of the terminal, the information indicating the activation or deactivation of the beam, the information indicating the activation or deactivation of the TCI state, and the information indicating the activation or deactivation of the CS state. In this case, the random access procedure may be terminated without performing step S904.

[0229] In step S903, if RA MSG2 is received based on PDCCH (or DCI) and uplink radio resources for RAMSG3 are not allocated, the terminal may wait until allocation information of uplink radio resources for RA MSG3 is received. When allocation information of uplink radio resources for RA MSG3 is received before the expiration of the preconfigured timer, the terminal may transmit RA MSG3 to the base station using the uplink radio resources. On the other hand, when allocation information of uplink radio resources for RA MSG3 is not received until the expiration of the preconfigured timer, the terminal may perform the random access procedure again. That is, the terminal may perform again from step S902.

[0230] In step S905, the base station may transmit downlink information requested by the terminal. Alternatively, the base station may transmit downlink data or a control message to the terminal. In step S905, the base station may transmit a terminal identifier received from the terminal (e.g., the terminal identifier received in step S904) to the terminal. The message 4 transmitted by the base station in step S905 may be referred to as "RA MSG4".

[0231] The base station may use RA MSG2 to transmit resource allocation information (e.g., scheduling information) for transmitting RA MSG3 to the terminal. The scheduling information may include one or more of an identifier of the base station transmitting the scheduling information, a beam index, an identifier for identifying the scheduling information, radio resource allocation information, MCS information, and resource allocation information for transmitting feedback information (e.g., ACK or NACK) indicating whether the scheduling information is received. The radio resource allocation information may include frequency domain resource allocation information (e.g., transmission band information, subcarrier allocation information) and / or time domain resource allocation information (e.g., frame index, subframe index, time slot index, symbol index, transmission period, transmission timing).

[0232] exist Fig. 9In the random access procedure shown, RA MSG3 may include one or more of the following information elements.

[0233] -Terminal Identifier (ID)

[0234] -Terminal capabilities, attributes, mobility status and location information

[0235] -The reason for attempting an access procedure (e.g., a random access procedure)

[0236] - Uplink data and / or size information of uplink data (e.g., length indicator (LI))

[0237] - Uplink buffer (e.g. BSR) size information

[0238] -Control message for connection configuration request

[0239] -Measurement results of radio channels

[0240] -Uplink resource allocation information

[0241] -Switch request information or measurement result information

[0242] -Terminal operation status transition (or change) request information

[0243] - Radio channel recovery information

[0244] - Radio channel reconstruction information

[0245] - Information about beam scanning, beam reconfiguration, or beam changes for beamforming

[0246] - Information about physical channel synchronization acquisition

[0247] - Updates to location information

[0248] -Movement status or buffer status report

[0249] The reason for attempting the access procedure may be a transmission request for system information according to a request of the terminal, a transmission request for downlink data according to an update of the firmware or necessary software of the terminal, or an uplink resource allocation request. The information indicating the reason for attempting the access procedure may be information capable of distinguishing the reason for performing the access procedure.

[0250] When RA MSG3 includes the above-mentioned information elements, one or more (one or more) control fields indicating whether (one or more) information elements are included, as well as the attributes and length of the corresponding data (or control information) can be configured in the form of a MAC header, a logical channel identifier (e.g., LCID) or a MAC CE.

[0251] Fig.10 is a sequence diagram illustrating a second exemplary embodiment of a random access procedure in a communication system.

[0252] Reference Fig.10 , the communication system may include a base station, a terminal, etc. The base station may be Figure 1 The base stations 110-1, 110-2, 110-3, 120-1 or 120-2 are shown, and the terminal may be Figure 1 The base station and the terminal may be configured to communicate with the terminal 130-1, 130-2, 130-3, 130-4, 130-5 or 130-6 shown in FIG. Figure 2 The communication nodes shown are the same or similar. The random access procedure can be performed in two steps.

[0253] The base station may transmit system information and / or a control message including configuration information of radio resources (e.g., uplink radio resources) for a random access procedure to the terminal (S1001). The terminal may obtain the configuration information of the radio resources for the random access procedure by receiving the system information and / or the control message from the base station. Here, the control message may be a dedicated control message. The system information and / or the dedicated control message may be associated with the Fig. 9 The system information and / or dedicated control message in step S901 are the same or similar.

[0254] The terminal may transmit RA MSG-A to the base station using radio resources configured by the base station (S1002). RA MSG-A may include an RA preamble and a terminal identifier (e.g., UE ID, C-RNTI). In addition, RA MSG-A may further include uplink data and / or control information. In the two-step random access procedure, message 1 may be referred to as "RA MSG-A", while in the four-step random access procedure, RA MSG-A may be distinguished from RA MSG1.

[0255] RA MSG-A may include an RA preamble and an RA payload. In a two-step random access process, the RA preamble may be referred to as a "two-step RA preamble", and in a two-step random access process, the RA payload may be referred to as a "two-step RA payload". The RA preamble of RA MSG-A may be selected by the MAC layer of the terminal. The RA payload of RA-MSG-A may be generated by the MAC layer or the RRC layer. The RA preamble selected by the MAC layer of the terminal and the RA payload generated by the MAC layer or the RRC layer of the terminal may be delivered to the physical layer. The RA payload of RA MSG-A may include one or more of a terminal identifier (e.g., UE ID, C-RNTI), uplink data, and control information.

[0256] The control information may include BSR, measurement result information (e.g., quality information), BFR request information, RLF report information, RRC connection establishment request information, RRC connection reconstruction request information, recovery request information, terminal location information (e.g., location estimated based on GPS signals, positioning schemes, or built-in sensors), and system information transmission request information. When performing a CBRA procedure or a CFRA procedure, the RA payload may include a terminal identifier. The uplink radio resources used for transmission of the RA preamble may be configured independently of the uplink radio resources used for transmission of the RA payload.

[0257] For example, the radio resources configured (or allocated) for the radio access procedure may be discontinuous in the time domain or the frequency domain. When the radio resources of the RA preamble included in the RA MSG-A and the radio resources of the RA payload included in the RA MSG-A are discontinuous, a time domain offset may be configured between the radio resources configured (or allocated) for the RA preamble and the RA payload. Alternatively, the radio resources configured (or allocated) for the radio access procedure may be continuous in the time domain or the frequency domain. The radio resources used for the radio access procedure may be radio resources configured (or allocated) in different schemes. Alternatively, the radio resources used for the radio access procedure may be radio resources defined by different physical layer channels.

[0258] Different expressions of radio resources for radio access procedures may mean that one or more of the position of the radio resource in the time domain or frequency domain, the index of the radio resource, the index of the RA preamble, the transmission timing and the offset are configured differently. Different radio resources may be used to transmit the RA preamble or the RA payload. For example, the RA preamble may be transmitted on the PRACH, while the RA payload may be transmitted on the physical uplink shared channel (PUSCH).

[0259] In order to configure the transmission resources for the RA preamble of the RA MSG-A differently from the transmission resources for the RA payload of the RA MSG-A, the uplink radio resources for transmitting the RA payload of the RA MSG-A (for example, the PUSCH configured for transmitting the RA payload of the RA MSG-A) may be configured to correspond to the RA preamble of the RA MSG-A. That is, a mapping relationship between the uplink radio resources for transmitting the RA preamble of the RA MSG-A and the uplink radio resources for transmitting the RA payload of the RA MSG-A may be configured.

[0260] For example, the transmission resources of the RA preamble may be mapped one-to-one with the transmission resources of the RA payload. In this case, one PRACH may be mapped to one PUSCH. Alternatively, multiple transmission resources of the RA preamble may be mapped to one transmission resource of the RA payload. In this case, multiple PRACHs may be mapped to one PUSCH. Alternatively, one transmission resource of the RA preamble may be mapped to multiple transmission resources of the RA payload. In this case, one PRACH may be mapped to multiple PUSCHs. In order to improve the reception quality of the RA payload, the RA payload may be retransmitted. Uplink radio resources for repeated transmission of the RA payload may be configured, and the corresponding uplink radio resources may be mapped to the transmission resources of the RA preamble. That is, according to other reasons, one or more uplink radio resources may be configured for retransmission of the RA payload or transmission of the RA payload. When configuring one or more radio resources for transmitting an RA payload, the configuration information of the RA payload may include information indicating a time interval for transmitting multiple RA payloads, the number of radio resources used to transmit the RA payload within the time interval, the interval between the radio resources, the number of symbols (or start symbol, end symbol and / or length) of each radio resource, and the like.

[0261] For example, when the transmission resources of RA MSG-A are preconfigured, or when the RA preamble of RA MSG-A is transmitted through a preconfigured area (or group), the base station can configure radio resources to retransmit the RA payload of RA MSG-A. Therefore, when the coverage extension function is applied or when the preconfigured reference condition is met, the terminal can select the RA preamble resource or the RA preamble index for retransmission of the RA payload, and can repeatedly transmit the RA payload based on the selected resource or index. The terminal can retransmit the RA payload using the uplink radio resources mapped to the RA preamble index. The uplink radio resources (e.g., repeated radio resources) for the transmission of the RA payload can be configured within a predetermined period in the frequency domain or the time domain. Information on the mapping relationship of the uplink radio resources used for the transmission of the RA MSG-A can be transmitted to the terminal through system information and / or RRC messages.

[0262] When a two-step random access process is performed in a non-contention scheme, the transmission resources of the RA preamble and / or the RA payload of the RA MSG-A can be specifically allocated to the terminal. In the CFRA process, the resource information of the RA preamble specifically configured for the terminal may include an SS / PBCH resource list, a CSI-RS resource list, an SS / PBCH index, a CSI-RS index, an RA preamble index, and the like. The transmission resources of the RA payload of the RA MSG-A can be determined based on a mapping relationship (e.g., a one-to-one mapping relationship) between the transmission resources of the RA preamble and the transmission resources of the RA payload. In the CFRA process, the resource information of the RA payload specifically configured for the terminal may include allocation information of uplink radio resources, beam configuration information for transmission of the RA payload, MCS information, and the like.

[0263] In the two-step random access procedure, the transmission resources of the RA preamble may be continuous with the transmission resources of the RA payload in the time domain. The transmission resources of the RA payload may be allocated within a time window. A terminal performing the two-step random access procedure may transmit the RA payload using radio resources continuous with the RA preamble. Alternatively, the terminal may transmit the RA payload by using radio resources that are discontinuous with the radio resources of the RA preamble (e.g., radio resources that are time-domain offset with the radio resources of the RA preamble within the time window).

[0264] In addition, the (one or more) parameters for allocating the transmission resources of the RA preamble and the transmission resources of the RA payload may include a frequency offset and / or a time offset. Accordingly, the terminal can transmit the RA payload by using the radio resources for the RA payload mapped to the RA preamble. Alternatively, the terminal can randomly select a radio resource among a plurality of radio resources (which are configured to transmit the RA payload) mapped to the RA preamble, and transmit the RA payload by using the selected radio resource.

[0265] The RA payload of the RA MSG-A transmitted in step 1002 may be configured to be the same as in Fig. 9 The RA MSG-A may be the same or similar to the RA MSG3 transmitted in step S904 shown in . For example, the RA payload of the RA MSG-A may include one or more of the following items: an identifier, capability, attribute, mobility state and location information of the terminal, a reason for attempting an access procedure, beam failure recovery request information, measurement results about a base station (or cell) in a CA environment, CA activation / deactivation request information, BWP switching request information, BWP deactivation / activation request information, uplink data, uplink data size, uplink buffer size information (e.g., BSR), a control message for requesting connection configuration, and measurement results of a radio channel.

[0266] Here, the beam failure recovery request information may refer to information used by the terminal to detect beam failure to request beam recovery based on the beam measurement result in the random access process. In this case, the terminal may transmit the measurement result of each beam and / or the TCI state information for configuring the new beam to the base station. Each of the BWP switching request information and the BWP deactivation / activation request information may include: an active BWP switching request based on the measurement result of the configured BWP, the measurement result of the deactivated BWP, and one or more of the information about the active BWP preferred by the terminal. Each of the beam failure recovery request information, the measurement result of the base station (or cell) in the CA environment, the CA activation / deactivation request information, the BWP switching request information, and the BWP deactivation / activation request information may include one or more of the measurement result, the BWP identifier, the base station (or cell) identifier, and the configured beam information (for example, the TCI state, CSI-RS index, or SS / PBCH index used to identify the beam). Beam failure recovery request information, measurement results about base stations (or cells) in a CA environment, CA activation / deactivation request information, BWP switching request information, and BWP deactivation / activation request information can be transmitted through MAC messages and / or RRC messages.

[0267] When the RA payload is transmitted together with the RA preamble in step 1002, the RA payload may include one or more of the terminal identifier, uplink data, and control information. The attributes of the uplink data, the length of the uplink data, the attributes of the control information, the length of the control information, and whether the control information is included may be indicated by a MAC header, a logical channel identifier (e.g., LCID), or a MAC CE. For transmission timing adjustment (e.g., adjustment of the TA value) or transmission power control, the terminal may insert a preamble, a pilot symbol, or a reference signal in the first symbol or some symbols within the RA payload of the RA MSG-A.

[0268] The base station may receive the RA MSG-A from the terminal, and may obtain the RA preamble and the RA payload included in the RA MSG-A. In addition, the base station may obtain one or more of the terminal identifier, uplink data, and control information from the RA payload. The base station may generate a RA MSG-B (e.g., message 2, RAR) in response to the RA MSG-A, and may transmit the RA MSG-B to the terminal (S1003). The terminal may receive the RA MSG-B from the base station, and may identify the (one or more) information elements included in the RA MSG-B.

[0269] RA MSG-B may include one or more of a backoff indicator (BI), uplink radio resource allocation information, information indicating the RA preamble code of RA MSG-A (i.e., the index of the RA preamble code), transmission timing adjustment information (e.g., TA value or TA command), a scheduling identifier (e.g., C-RNTI, temporary cell (TC)-RNTI, etc.), and a terminal identifier for contention resolution (e.g., UE contention resolution ID).

[0270] A RA MSG-B (e.g., a MAC PDU) may include one or more MAC sub-PDUs. Each of the one or more MAC sub-PDUs included in the RA MSG-B may be configured based on one of the following configuration schemes. Information indicating the configuration scheme of the MAC sub-PDU may be included in the MAC sub-header of the corresponding MAC sub-PDU. A MAC sub-PDU may mean a "MAC sub-PDU".

[0271] -Configuration #1: MAC subheader containing backoff indicator (BI)

[0272] -Configuration #2: MAC subheader and fallback RAR

[0273] -Configuration #3: MAC subheader and successful RAR

[0274] - Configuration #4: MAC subheader and MAC service data unit (SDU) (e.g., data or control information)

[0275] -Configuration #5: MAC subheader and padding

[0276] When RA MSG-B is scheduled by the C-RNTI assigned to the terminal, or when RA MSG-B includes the terminal identifier (eg, UE contention resolution ID) included in RA MSG-A, the terminal can determine that the contention is resolved. That is, the terminal can determine that the two-step random access procedure is completed.

[0277] When the CRC of the DCI including the scheduling information of the PDSCH on which the RA MSG-B is transmitted (e.g., RAR for RAMSG-A) is scrambled by the C-RNTI, and the RA MSG-B including the TA information and / or the UL grant is received within the RAR window (or before the timer expires), the terminal can determine that the contention of the two-step random access procedure is resolved. Here, the TA information can be a TA value or a TA command.

[0278] A specific field (or bit) of the PDCCH (e.g., DCI or UCI) may indicate that the RA MSG-B scheduled by the PDCCH is the RA MSG-B scheduled by the C-RNTI. Alternatively, a logical channel identifier (LCID) for transmission of a MAC CE for the RA MSG-B or a field of a MAC subheader may indicate that the RA MSG-B scheduled by the PDCCH is the RA MSG-B scheduled by the C-RNTI.

[0279] In the four-step random access process, the RAR window may start at the end time point of the transmission of RA MSG1. In the two-step random access process, the RAR window may start at the end time point of the transmission of the RA payload of RA MSG-A. When RA MSG-B (e.g., RA MSG-B scheduled by C-RNTI) including TA information and / or UL grant is not received within the RAR window (or before the timer expires), the terminal may determine that the contention of the two-step random access process has not been resolved.

[0280] When a RA MSG-B scheduled by C-RNTI is transmitted in response to a RA MSG-A in a two-step random access procedure, the PDCCH (e.g., DCI or UCI) may include TA information, an indicator notifying that the corresponding PDCCH includes scheduling information for a response to the RA MSG-A, and the like. The RA MSG-B may be transmitted in the form of a MAC message (e.g., MAC CE) or an RRC message. When the RA MSG-B is transmitted in the form of a MAC message, the RRC layer of the base station that obtains the information of the RA MSG-A may pass (one or more) parameters to be included in the RAMSG-B to the MAC layer of the base station, and the MAC layer of the base station may generate the RA MSG-B in the form of a MAC CE. The RA MSG-B may include a terminal identifier obtained through the RA payload of the RA MSG-A.

[0281] When the RA preamble of RA MSG-A is exclusively allocated to the terminal, or when radio resources of the RA preamble of RA MSG-A are mapped one-to-one with radio resources of the RA payload of RA MSG-A, RA MSG-B may not include an index of the RA preamble received from the terminal.

[0282] When the RA preamble of RA MSG-A is exclusively allocated to the terminal, or when the RA payload of RA MSG-A includes a scheduling identifier (e.g., C-RNTI) assigned to the terminal, the base station may transmit DCI including scheduling information of transmission resources for RA MSG-B to the terminal using the scheduling identifier assigned to the terminal. That is, the CRC of the DCI may be scrambled by the scheduling identifier assigned to the terminal. The terminal may receive the DCI using the scheduling identifier assigned to the terminal, obtain scheduling information of transmission resources for the RA MSG-B included in the DCI, and receive the RA MSG-B in the transmission resources indicated by the scheduling information.

[0283] In step S1003, the base station may transmit a PDCCH for scheduling uplink radio resources, a PDCCH (e.g., DCI) for RAR (e.g., RA MSG-B) or RA MSG-B. RA MSG-B may be transmitted on PDSCH. When only PDCCH is transmitted in step S1003, the corresponding PDCCH may include allocation information (e.g., scheduling information) for uplink radio resources of the terminal, transmission timing adjustment information (e.g., TA information), transmission power adjustment information, backoff information, beam configuration information, TCI state information, CS state information, state transition information, PUCCH configuration information, an index of the RA preamble included in RA MSG-A, and one or more of allocation information of radio resources for transmitting the RA payload of RA MSG-A. In addition, when only PDCCH is transmitted in step S1003, the terminal may recognize that no RA response is transmitted on PDSCH based on the DCI format of PDCCH and / or the above-mentioned PDCCH configuration information.

[0284] The beam configuration information may be information indicating activation or deactivation of a specific beam. The TCI state information may be information indicating activation or deactivation of a specific TCI state. The CS state information may be information indicating activation or deactivation of radio resources allocated in the CS scheme. The state transition information may be information indicating activation or deactivation of radio resources allocated in the CS scheme. Figure 8 The state transition information may indicate a transition from a current operating state to an RRC idle state, an RRC inactive state, or an RRC connected state. Alternatively, the state transition information may indicate maintaining the current operating state. The PUCCH configuration information may be allocation information of transmission resources for SR. Alternatively, the PUCCH configuration information may be information indicating activation or deactivation of transmission resources for SR.

[0285] The base station may transmit the control information described in step S1003 on the PDSCH by transmitting only the PDCCH. The control message transmitted on the PDSCH may include allocation information of uplink radio resources (e.g., scheduling information), transmission timing adjustment information (e.g., TA information), transmission power adjustment information, backoff information, beam configuration information, TCI state information, configured scheduled (CS) state information, state transition information, PUCCH configuration information, an index of the RA preamble included in the RA MSG-A, and allocation information of uplink radio resources for transmitting the uplink data and / or control message in step S1004.

[0286] In the process of generating and transmitting the RA MSG-B, the base station may transmit the DCI including the scheduling information for the transmission of the RA MSG-B by using the scheduling identifier (e.g., C-RNTI) or RA-RNTI assigned to the terminal. That is, the CRC of the DCI may be scrambled by the RA-RNTI or C-RNTI. The base station may transmit the RA MSG-B to the terminal using the PDSCH indicated by the DCI.

[0287] When the terminal successfully receives RA MSG-B from the base station, the two-step random access procedure may be terminated. The terminal receiving RA-MSG B may transmit uplink data and / or control messages to the base station by using uplink scheduling information (eg, scheduling information included in RA-MSG B) (S1004).

[0288] Information indicating whether a base station (or cell) allows a two-step random access procedure and / or conditions for performing the two-step random access procedure may be transmitted to a terminal through system information transmitted in a broadcast manner, a control message transmitted in a multicast manner, or a dedicated control message. Information indicating whether a base station (or cell) allows a two-step random access procedure may be information indicating whether a base station allows a terminal located in a service area to attempt to access through a two-step random access procedure, information indicating whether a base station restricts an access attempt of a terminal located in a service area through a two-step random access procedure, or information indicating whether a base station partially restricts an access attempt of a terminal located in a service area through a two-step random access procedure.

[0289] When the access attempt through the two-step random access procedure is restricted, the base station may notify the terminal of the restriction condition of the two-step random access procedure. When the access attempt through the two-step random access procedure is partially restricted, the base station may notify the terminal of the partial restriction condition of the two-step random access procedure. When the base station does not allow the two-step random access procedure, or when the restriction condition or partial restriction condition of the two-step random access procedure is met, the terminal may not attempt the two-step random access procedure.

[0290] When the execution condition (e.g., permission condition) of the two-step random access process is met, the terminal can perform the two-step random access process. For example, if the quality of the radio channel measured by the terminal is equal to or greater than the threshold (e.g., reference value) configured by the base station, the terminal can perform the two-step random access process. When the quality of the wireless channel measured by the terminal is less than the threshold configured by the base station, the terminal can perform a four-step random access process. For example, the quality of the radio channel can be measured as a received signal strength indicator (RSSI), received signal code power (RSCP), reference signal received power (RSRP), or reference signal received quality (RSRQ). Alternatively, the quality of the radio channel can be measured as other parameters (e.g., reference parameters for measuring the quality of the radio segment between the base station (or cell or TRP) and the terminal).

[0291] The RA preamble (e.g., signature) of RA MSG1 in the four-step random access procedure may be configured to be the same as the RA preamble (e.g., signature) of RA MSG-A in the two-step random access procedure. In the process of generating the RA preambles of RA MSG1 and RA MSG-A, the same code generation equation may be used to generate a code sequence.

[0292] The transmission resources of the RA preamble code of RA MSG1 in the four-step random access procedure may be configured to be the same as or different from the transmission resources of the RA preamble code of RA MSG-A in the two-step random access procedure.

[0293] When the transmission resources of the RA preamble of RA MSG1 and the transmission resources of the RA preamble of RA MSG-A are the same, the configuration of the index of the RA preamble of RA MSG1 and the index of the RA preamble of RA MSG-A may be different. That is, the range of the index of the RA preamble of RA MSG1 and the range of the index of the RA preamble of RA MSG-A may be configured differently within the same transmission resources of the RA preamble.

[0294] When the transmission resources of the RA preamble of RA MSG1 and the transmission resources of the RA preamble of RA MSG-A are different, the transmission resources of the RA preamble of RA MSG1 can be configured to be different from the transmission resources of the RA preamble of RA MSG-A in the time domain and / or frequency domain. According to the beamforming technology, the transmission resources of the RA preamble in the frequency domain may include one or more of the frequency band information, PRB information, CRB information, subcarrier information and beam information. The transmission resources of the RA preamble in the time domain may be configured or indicated in units of radio frames, subframes, TTIs, time slots, micro-time slots, symbols or specific time intervals. The base station may determine whether to perform a four-step random access procedure or a two-step random access procedure based on the RA preamble received from the terminal or the radio resource through which the RA preamble is received.

[0295] The size of the RA payload of the RA MSG-A and / or the MCS level of the RA payload of the RA MSG-A may be determined as follows. The base station may configure the size of the RA payload of the RA MSG-A to be a fixed value among multiple candidate values, and the MCS level used to transmit the RA payload of the RA MSG-A may be fixed to a fixed level among multiple candidate levels. The base station may notify the terminal of the size and / or MCS level of the RA payload configured by the base station. The base station may configure the terminal to select the RA preamble of the RA MSG-A according to the size and / or MCS level of the RA payload of the RA MSG-A. For example, the terminal may select the RA preamble of the RA MSG-A based on at least one of the radio quality information (e.g., path loss information) of the RA MSG-A received from the base station, the size of the RA payload of the RA MSG-A, and the MCS level used to transmit the RA payload of the RA MSG-A. The terminal may transmit the selected RA preamble of the RA MSG-A to the base station.

[0296] Accordingly, the base station can estimate one or more of the MCS level, size, and radio quality of the downlink channel of the RA payload of the corresponding RAMSG-A based on the RA preamble of the RA MSG-A received from the terminal. The RA preamble of the RA MSG-A that can be used can vary according to the radio quality of the downlink channel, the size of the RA payload of the RA MSG-A, and / or the MCS level. The base station can transmit system information and / or a control message (e.g., a dedicated control message) to the terminal, which includes information about the RA preamble that can be used according to the radio quality of the downlink channel, the size of the RA payload of the RA MSG-A, and / or the MCS level.

[0297] In addition, the system information and / or control message (e.g., a dedicated control message) may include (one or more) configuration parameters for selecting the RA preamble of the RAMSG-A that can be used according to the radio quality of the downlink channel, the size of the RA payload of the RA MSG-A, and / or the MCS level. The (one or more) configuration parameters may include one or more of the radio quality information of the downlink channel, the size and MCS level of the RA payload of the RA MSG-A, the information of the RA preamble of the RA MSG-A corresponding to the corresponding reference value (e.g., an index or an index range), and the reference value of the transmission resource information of the RA preamble of the RA MSG-A corresponding to the reference value.

[0298] Alternatively, the MCS level for transmitting the RA payload of the RA MSG-A may be fixed. The base station may set the MCS level for transmitting the RA payload of the RA MSG-A to a fixed level. The base station may transmit system information and / or a control message (e.g., a dedicated control message) including the MCS level for transmitting the RA payload of the RA MSG-A to the terminal. The terminal may receive the system information and / or the control message (e.g., a dedicated control message) from the base station, and identify the MCS level (e.g., a fixed MCS level) for transmitting the RA payload of the RA MSG-A configured by the base station. The terminal may transmit the RA payload of the RA MSG-A by using the fixed MCS level.

[0299] In addition, the RA payload of the RA MSG-A may include the MCS level applied to the corresponding RA payload. For example, the terminal may determine the MCS level for the RA payload of the RA MSG-A, and transmit the RA payload of the RA MSG-A including the determined MCS level to the base station. The RA payload of the RA MSG-A may include other information elements as well as the MCS level. The base station may configure the MCS level range of the RA payload of the RA MSG-A, and transmit a control message (e.g., a dedicated control message) and / or system information including the MCS level range to the terminal.

[0300] In this case, the terminal may select an MCS level within the range of MCS levels configured by the base station, and transmit the RA payload of the RA MSG-A to the base station using the selected MCS level. Here, the RA payload of the RA MSG-A may include the MCS level selected by the terminal. The base station may receive the RA payload of the RA MSG-A from the terminal, and identify the MCS level applied to the RA payload by checking a specific portion (e.g., UCI) within the RA payload of the RA MSG-A. The base station may perform demodulation and decoding operations on the RA payload of the RA MSG-A based on the identified MCS level.

[0301] Alternatively, the RA preamble of the RA MSG-A may be selected by a combination of the above methods. In addition, the size and / or MCS level of the RA payload of the RA MSG-A may be selected by a combination of the above methods. For example, the RA preamble of the RA MSG-A may be selected according to the radio quality of the downlink channel and / or the size of the RA payload of the RA MSG-A. The MCS level of the RA payload of the RA MSG-A may be fixed to a specific level. A specific portion (e.g., UCI) within the RA payload of the RA MSG-A may indicate the MCS level applied to the corresponding RA payload.

[0302] The index (e.g., RA preamble index), masking information, and / or offset of RA MSG1 may be configured differently according to the path loss of the downlink and / or the size of RA MSG3. When the base station supports both the four-step random access procedure and the two-step random access procedure, the condition (or criterion) for the terminal to select the RA preamble of RA MSG-A in the two-step random access procedure may be configured to be the same as the condition (or criterion) (e.g., RA preamble) for the terminal to select RA MSG1.

[0303] By using system information and / or a control message (e.g., a dedicated control message), the base station may transmit to the terminal one or more of information indicating whether a four-step random access procedure is supported, information indicating whether a two-step random access procedure is supported, a condition (e.g., a criterion) for selecting RA MSG1 in the four-step random access procedure (e.g., an RA preamble), and a condition (e.g., a criterion) for selecting an RA preamble of RA MSG-A in the two-step random access procedure.

[0304] Through the system information and / or control message, the terminal can obtain the resource configuration information of the two-step random access process configured by the base station according to the purpose of performing the two-step random access process (e.g., BFR process, recovery request, connection configuration request, system information request), the size of the RA payload to be transmitted by the terminal, the radio quality of the downlink channel, etc. The resource configuration information for the two-step random access process may include the MCS level and / or transmission resource information of the RA MSG-A (e.g., RA preamble, RA payload). The terminal can select resources that meet the above selection conditions (e.g., selection criteria), and can use the selected resources to transmit the RA MSG-A (e.g., RA preamble, RA payload) to perform the two-step random access process.

[0305] The terminal may determine the MCS level of the corresponding RA payload based on the radio resource selection scheme for transmission of the RA payload of the RA MSG-A. For example, the base station may configure the radio resources for transmitting the corresponding RA payload according to the size and / or MCS level of the RA payload of the RA MSG-A, and transmit the resource configuration information of the RA payload to the terminal by using system information and / or a control message (e.g., a dedicated control message). The radio resources for transmission of the RA payload may be configured differently according to the size and / or MCS level of the RA payload.

[0306] The terminal may receive resource configuration information of the RA payload of the RA MSG-A from the base station, and may select a radio resource corresponding to the size and / or MCS level of the RA payload based on the resource configuration information. The terminal may transmit the RA preamble of the RA MSG-A corresponding to (e.g., mapped to) the selected radio resource to the base station, and may use the selected radio resource to transmit the RA payload of the RA MSG-A to the base station. The base station may receive the RA preamble of the RAMSG-A from the terminal, and identify the size and / or MCS level of the RA payload corresponding to (e.g., mapped to) the radio resource through which the RA preamble is received. The base station may receive the RA payload of the RA MSG-A based on the size and / or MCS level of the identified RA payload.

[0307] The scheduling identifier (e.g., RA-RNTI) used to transmit RA MSG-B in the two-step random access process may be different from the RA-RNTI used to transmit message 2 (e.g., RA MSG2) in the four-step random access process. In the two-step random access process, the RA-RNTI may be a RA-RNTI (e.g., MSG-B RA-RNTI) configured separately for transmission of RA MSG-B. The MSG-B RA-RNTI may be mapped to the transmission resources (e.g., radio resources) of the RA preamble of RA MSG-A. When the terminal selects the transmission resources of the RA preamble of RA MSG-A, the MSG-B RA-RNTI used to receive RAMSG-B in the two-step random access process may be determined.

[0308] In the two-step random access process, the format of the RA MSG-B may vary depending on the parameters contained in the RA MSG-B. In order to support various RA MSG-B formats, a separate MAC subheader or a separate field in the MAC CE may be defined for the RA MSG-B. The "MsgB-type" field indicating the format of the RA MSG-B may be configured in a separate MAC subheader or MAC CE for the RA MSG-B. For example, the MsgB-type field may be configured in the first octet in a separate MAC subheader or MAC CE for the RA MSG-B. When the size of the MsgB-type field is 2 bits, the format of the RA MSG-B may be defined as follows. The (one or more) parameters contained in the RA MSG-B may vary depending on the format of the corresponding RA MSG-B.

[0309] 00: TA information, UL grant, TC-RNTI, UE ID (e.g., terminal identifier included in RA MSG-A)

[0310] 01:UL permission, TC-RNTI, UE ID

[0311] 10:TA information, UL permission, beam configuration information, TCI status information

[0312] 11: UL permission, beam configuration information, TCI status information

[0313] TA information (eg, TA value, TA command) may be used to adjust uplink transmission timing. UL grant may be uplink scheduling information. TC-RNTI may be a scheduling identifier (eg, temporary C-RNTI) assigned to a terminal.

[0314] The size of the MsgB-Type field may be 1 bit or more. The MsgB-Type field may indicate the parameter(s) contained in the RA MSG-B. The parameter(s) contained in the RA MSG-B may be one or more of TA information, UL grant, TC-RNTI, UE ID, beam configuration information, TCI status information, other control information, and downlink data.

[0315] When resources for RA preamble of RA MSG-A and resources for RA MSG1 (eg, RA preamble) are configured in the same scheme, a scheduling identifier for transmission and reception of RA MSG-B and a scheduling identifier for transmission and reception of RA MSG2 may not be distinguished. Here, the scheduling identifier may be RA-RNTI.

[0316] The transmission resource of the RA preamble of RA MSG-A may be the same as the transmission resource of RA MSG1, and the index of the RA preamble of RA MSG-A may be different from the index of RA MSG1 (e.g., the index of RA preamble). The scheduling identifier for transmission and reception of RA MSG-B may be determined according to the index and / or transmission resource of the RA preamble of RA MSG-A. The scheduling identifier for transmission and reception of RA MSG2 may be determined according to the index and / or transmission resource of RA MSG1 (e.g., the RA preamble). When the transmission resource of the RA preamble of RA MSG-A is the same as the transmission resource of RA MSG1, and the index of the RA preamble of RA MSG-A is different from the index of RA MSG1 (e.g., the index of RA preamble), the scheduling identifier for transmission and reception of RA MSG-B may be the same as the scheduling identifier for transmission and reception of RA MSG2.

[0317] Even when the scheduling identifier for transmission and reception of RA MSG-B and the scheduling identifier for transmission and reception of RA MSG2 are configured in the same scheme, the configuration of the RA-RNTI for RA MSG-B (e.g., MSG-B RA-RNTI) may be different from the RA-RNTI for RA MSG2. The RA-RNTI for RA MSG-B may be a RA-RNTI determined by adding a preconfigured offset value to the RA-RNTI for RA MSG2. That is, the RA-RNTI for RA MSG-B may be determined by adding a constant value to the RA-RNTI for RA MSG2.

[0318] The base station may transmit information indicating whether the resources for the RA preamble of RA MSG-A are configured in the same scheme as the resources for RA MSG1 to the terminal by using system information and / or a control message (e.g., a dedicated control message). The RA-RNTI determined by the same scheme may be used in the two-step random access procedure and the four-step random access procedure. In this case, the terminal may identify whether the received RAR is RA MSG-B of the two-step random access procedure or RA MSG2 of the four-step random access procedure based on a specific field in the MAC header (or MAC subheader), which is a header of the corresponding RAR received based on the RA-RNTI.

[0319] For example, the reserved bit(s) in the MAC subheader included in the RAR (e.g., RA MSG-B) may indicate whether the corresponding RAR is RA MSG-B or RA-MSG2. The reserved bit(s) set to "00" may indicate that the corresponding RAR is RA MSG2. The reserved bit(s) set to "01", "10", or "11" may indicate that the corresponding RAR is RA MSG-B.

[0320] When RA MSG-B and RA MSG2 are transmitted through one radio resource region, RA MSG-B may be transmitted earlier than RA MSG2 in the one radio resource region. For this operation, the MAC subheader of RA MSG-B may be located before the MAC subheader of RAMSG2. Alternatively, RAMSG-B may be transmitted after RA MSG2 in one radio resource region. For this operation, the MAC subheader of RA MSG-B may be located after the MAC subheader of RA MSG2.

[0321] When the MAC subheader of RA MSG-B is located after the MAC subheader of RA MSG2, all MAC subheaders of one or more RA MSG2s may be located before the MAC subheader of RA MSG-B in the downlink message for transmitting the (one or more) RA MSG-B and / or (one or more) RA MSG2. If there is no RA MSG2 to be transmitted by the base station, the downlink message may include only the (one or more) MAC subheaders of (one or more) RA MSG-B.

[0322] On the other hand, when the MAC subheader of RA MSG-B is located before the MAC subheader of RA MSG2, all MAC subheaders of one or more RA MSG-Bs may be located before the (one or more) MAC subheaders of RAMSG2 in the downlink message used to transmit RA MSG-B and / or RA MSG2.

[0323] RA MSG-B may include the above-mentioned (one or more) parameters and RRC messages (e.g., RRC control information). When receiving RA MSG-A (e.g., RA payload of RA MSG-A) including an RRC message (e.g., connection request message, recovery request message), the base station may generate a MAC PDU of RA MSG-B for each terminal and transmit the MAC PDU of RA MSG-B to each terminal.

[0324] In the two-step random access process, the MAC PDU of the RA MSG-B may include (one or more) of the above parameters (e.g., TA information, UL grant, TC-RNTI, UE ID, beam configuration information, etc.) without RRC control information. The MAC PDU of the RA MSG-B including the above (one or more) parameters without RRC control information may be referred to as "MSG-B with UEsMux". Alternatively, the MAC PDU of the RA MSG-B may include the above (one or more) parameters with RRC control information. The MAC PDU of the RA MSG-B including the above (one or more) parameters and RRC control information may be referred to as "MSG-B with SRB". The MSG-B with UEsMux may include RA MSG-Bs for multiple terminals, and the MSG-B with SRB may include RA MSG-Bs for one terminal. RA MSG-Bs of multiple terminals may be multiplexed in the MSG-B with UEsMux consisting of one MAC PDU.

[0325] A scheduling identifier for addressing a PDCCH (e.g., DCI) including scheduling information for transmitting a PDSCH where an MSG-B with SRBs is located may be separately assigned. The RA-RNTI for sending and receiving an MSG-B with UEsMux may be configured independently of the RA-RNTI for sending and receiving an MSG-B with SRBs. The RA-RNTI for addressing the scheduling information for the PDSCH where an MSG-B with SRBs is located may be configured differently from the RA-RNTI for addressing the scheduling information for the PDSCH where an MSG-B with UEsMux is located. In a two-step random access procedure, a terminal transmitting an RA MSG-A may perform a PDCCH monitoring operation by using both the RA-RNTI for an MSG-B with SRBs and the RA-RNTI for an MSG-B with UEsMux. For example, the RA-RNTI for an MSG-B with SRBs may be a RA-RNTI obtained by applying a preconfigured offset to the RA-RNTI for an MSG-B with UEsMux.

[0326] Alternatively, the RA-RNTI for MSG-B with SRB may be a RA-RNTI obtained by applying a first preconfigured offset to the RA-RNTI of RA MSG2, and the RA-RNTI for MSG-B with UEsMux may be a RA-RNTI obtained by applying a second preconfigured offset to the RA-RNTI of RA-MSG2. The first offset may be different from the second offset. In the above exemplary embodiments, the base station may notify the terminal of the preconfigured offsets (e.g., the first offset and the second offset). The terminal may identify the RA-RNTI for MSG-B with SRB and the RA-RNTI for MSG-B with UEsMux by using the preconfigured offsets (one or more) obtained from the base station. When the scheduling identifier (e.g., RA-RNTI) is configured differently in the two-step random access procedure and / or the four-step random access procedure, the terminal can use the corresponding scheduling identifier to distinguish the RA response message (e.g., RAMSG2, RA MSG-B, MSG-B with SRB, or MSG-B with UEsMux) in the two-step random access procedure and / or the four-step random access procedure. The RA response message of the two-step random access procedure can be a successful RAR (e.g., MSG-B with SRB MAC PDU, MSG-B with UEsMux MAC PDU) or the fallback RAR described below. Therefore, the RA MSG-B of the two-step random access procedure can be composed of the above-mentioned backoff indicator (BI), contention resolution information using the terminal identifier (e.g., successful RAR), or fallback RAR. If the scheduling identifier used to transmit the RA response message of the two-step random access procedure is set to MSG-B RA-RNTI, the terminal can use the scheduling identifier RA-RNTI and MSG-B RA-RNTI to distinguishably receive RA MSG2 of the four-step random access procedure and RAMSG-B of the two-step random access procedure.

[0327] When reporting uplink measurements using the RA payload of RA MSG-A in a two-step random access procedure, or using Fig.10When the uplink measurement result information is reported in the message of step S1004 shown in FIG. 1004, or when the uplink measurement result information is reported using RA MSG3 in the four-step random access process, the uplink measurement result information may include information for identifying the downlink beam (e.g., TCI state configuration information, SS / PBCH index, CSI-RS index) and / or information of the BWP identifier. When the uplink measurement result information is transmitted according to the beam order in the beam configuration list included in the control message for configuring multiple beams, the uplink measurement result information may not include information for identifying the downlink beam (e.g., downlink beam identifier). When the uplink measurement result information is transmitted according to the BWP order in the BWP configuration list included in the control message for configuring multiple BWPs, the uplink measurement result information may not include the BWP identifier.

[0328] The RA MSG3 in the four-step random access procedure and the RA MSG-A (e.g., RA payload) in the two-step random access procedure may be configured according to the same format. Alternatively, the RA MSG3 and the RA MSG-A (e.g., RA payload) may be configured according to different formats. Here, the format may mean a form constituting a MAC message or an RRC message. Expression using the same format may mean including the same (one or more) parameters, (one or more) fields, and / or (one or more) information elements in the MAC message or the RRC message.

[0329] Regardless of whether the format of RA MSG3 is the same as that of RA MSG-A (e.g., RA payload), fields within the MAC header (or MAC subheader) and / or a logical channel identifier (e.g., LCID) can be configured to distinguish RA MSG3 from RAMSG-A (e.g., RA payload).

[0330] The field in the MAC header (or MAC subheader) indicating RA MSG3 may be configured differently from the field in the MAC header (or MAC subheader) indicating RA MSG-A (e.g., RA payload). The field in the MAC header (or MAC subheader) used to distinguish RA MSG3 from RA MSG-A (e.g., RA payload) may be referred to as an "RA-M3" field. The RA-M3 field set to "1" may indicate that the corresponding message is RA MSG3. The RA-M3 field set to "0" may indicate that the corresponding message is RA MSG-A (e.g., RA payload).

[0331] The LCID indicating RA MSG3 may be configured differently from the LCID indicating RA MSG-A (eg, RA payload). Therefore, the base station may distinguish RA MSG3 from RA MSG-A (eg, RA payload) based on the LCID included in the MAC header (or MAC subheader, MAC message).

[0332] The terminal may respectively perform the above-mentioned four-step random access process and two-step random access process based on the CBRA scheme or the CFRA scheme. When the terminal transmits message 1 (e.g., RA MSG-A (e.g., RA preamble, RA payload), RA MSG1) more times than the preconfigured number of times in the CFRA process, or when the terminal does not receive the RAR for message 1 within the time corresponding to the preconfigured timer, the terminal may switch from the CFRA process to the CBRA process. That is, the terminal may perform the two-step random access process or the four-step random access process according to the CBRA scheme.

[0333] When dedicated radio resources for a two-step random access procedure or a four-step random access procedure are configured in the CFRA procedure, if the reference condition (e.g., radio channel quality) for transmitting the RA preamble is not met, the CBRA procedure may be performed instead of the CFRA procedure. For example, when the radio channel quality is higher than the reference condition, the terminal may perform the CFRA procedure by using the dedicated radio resources allocated for the CFRA procedure. When the radio channel quality is less than the reference condition, the terminal may perform the CBRA procedure instead of the CFRA procedure.

[0334] When executing Fig.10 In the two-step random access process shown in , in step S1002, the base station may receive the RA preamble or RA payload included in the RA MSG-A. That is, the base station may not receive both the RA preamble and the RA payload. In this case, the base station may not transmit the RA MSG-B to the terminal in response to the RA MSG-A. When the RA MSG-B is not received from the base station within the RAR window, the terminal may perform a retransmission operation of the RA MSG-A within a preconfigured time period (or a predetermined number of times).

[0335] Alternatively, when the base station receives the RA preamble or RA payload in step S1002, the base station and / or the terminal may operate as follows. In the two-step random access process, the RAR window (or timer) for receiving the RA MSG-B may start at the transmission time point of the RA payload of the RAMSG-A. When the RA payload of the RA MSG-A is retransmitted, the RAR window may start at the transmission time point of the last RA payload. The transmission time point of the RA payload of the RA MSG-A may be the transmission start time point or the transmission end time point of the RA payload. The transmission time point of the RA payload of the RA MSG-A may be expressed based on a subframe, a time slot, a mini-time slot, or a symbol.

[0336] In the two-step random access procedure, the RAR window for receiving RA MSG-B may be configured to be the same as the RAR window for receiving RAMSG2. The RAR window for receiving RA MSG-B may be configured based on (one or more) parameters related to the RAR window for receiving RA MSG2. When a base station (or cell) is configured according to a functional split scheme of a radio protocol, the base station may transmit at least one of configuration information (e.g., (one or more) parameters) of the RAR window for receiving RA MSG-B and configuration information (e.g., (one or more) parameters) of the RAR window for receiving RA MSG2 to the terminal by using system information and / or a control message (e.g., an RRC message).

[0337] When only the RA preamble of the RA MSG-A is received at the base station, a retransmission procedure of the RA payload of the RA MSG-A may be performed. The retransmission procedure of the RA payload of the RA MSG-A may be performed as follows.

[0338] The two-step random access procedure may be performed according to the CFRA scheme. In step S1002, the base station may receive an RA preamble of an RA MSG-A from the terminal. When a decoding operation of an RA payload of an RA MSG-A fails or when an RA payload of an RA MSG-A is not received before a preconfigured timer (hereinafter referred to as "T2-stepRA") expires, the base station may identify the terminal that initiated the two-step random access procedure based on the RA preamble of the RAMSG-A.

[0339] T2-stepRA may be started at a time point (e.g., a reception start time point, a reception end time point) at which the base station receives the RA preamble. The base station may use system information and / or a control message (e.g., a dedicated control message) to notify the terminal of T2-stepRA. The terminal shall transmit the RA payload to the base station before T2-stepRA expires. When the RA preamble of RAMSG-A is mapped to the RA payload of RA MSG-A, T2-stepRA may be a timer according to a time relationship corresponding to the mapping relationship between the RA preamble and the RA payload.

[0340] When the RA payload is not received from the terminal before the expiration of T2-stepRA from the reception time point of the RA preamble (e.g., the reception start time point, the reception end time point), the base station may transmit a DCI including scheduling information for transmitting the PDSCH where the RA MSG-B is located by using one of the following scheduling identifiers. The DCI may be transmitted on the PDCCH. The scheduling identifiers are as follows:

[0341] - A dispatch identifier specifically configured for the terminal

[0342] - Scheduling identifier for transmission of RA MSG-B (e.g., MSG-B RA-RNTI)

[0343] - The scheduling identifier of RA MSG-B used to transmit the RA payload requesting retransmission of RA MSG-A

[0344] In step S1003, the base station may transmit a DCI including allocation information (e.g., scheduling information) of uplink radio resources through a PDCCH. Alternatively, in step S1003, the base station may transmit a RA MSG-B through a PDSCH. A RA MSG-B requesting retransmission of the RA payload of RA MSG-A may be transmitted on a PDSCH (e.g., a PDSCH scheduled by a DCI). The RA MSG-B requesting retransmission of the RA payload may include one or more information elements. For example, the RA MSG-B may include allocation information (e.g., scheduling information) of uplink radio resources, transmission timing adjustment information, transmission power adjustment information, beam configuration information, retransmission request information (e.g., retransmission indication information) of the RA payload of RA MSG-A, radio resource allocation information for (re)transmitting the RA payload of RA MSG-A, and one or more of the MCS levels. Each of the multiple information elements included in the RA MSG-B may be configured in the form of a MAC CE. Alternatively, a plurality of information elements included in the RA MSG-B may be configured in the form of one MAC CE. In this case, an additional MAC header format may be used.

[0345] When the base station that receives only the RA preamble of RA MSG-A transmits a RAMSG-B requesting retransmission of the RA payload of RA MSG-A, the terminal may receive the RA MSG-B from the base station and identify the (one or more) information elements contained in the RA MSG-B. The (one or more) information elements contained in the RA MSG-B may be radio resource allocation information, MCS level, TA information, transmission power adjustment information and / or configured beam information for (retransmission) transmission of the RA payload. The terminal may retransmit the RA payload of RA MSG-A based on the (one or more) information elements included in the RA MSG-B. When the retransmitted RA payload is received from the terminal, the base station may transmit the RA MSG-B to the terminal. The terminal may receive the RA MSG-B from the base station. When the RA MSG-B is received from the base station, the terminal may determine that the RA payload of RA MSG-A is successfully received at the base station.

[0346] On the other hand, when only the RA preamble of RA MSG-A is received at the base station, the two-step random access process can be switched to the four-step random access process. The two-step random access process can be performed according to the CFRA scheme. In step S1002, the base station can receive the RA preamble of RA MSG-A from the terminal. When the decoding operation of the RA payload of RA MSG-A fails, or when the RA payload of RA MSG-A is not received before the expiration of a preconfigured timer (hereinafter referred to as "T2-stepMsgA"), the base station can identify the terminal that initiated the two-step random access process based on the RA preamble of RA MSG-A. That is, when performing the two-step random access process according to the CFRA scheme, the base station can identify the corresponding terminal based on the index or radio resource of the RA preamble of RA MSG-A according to the CFRA scheme, which is received from the terminal. T2-stepMsgA can be started at the time point (e.g., reception start time point, reception end time point) at which the RA preamble is received at the base station. The base station may use system information and / or a control message (e.g., a dedicated control message) to notify the terminal of T2-stepMsgA. The terminal shall transmit the RA payload to the base station before T2-stepMsgA expires. When the RA payload is received from the terminal before T2-stepMsgA expires, the base station may transmit RA MSG-B to the terminal. T2-stepMsgA may be greater than T2-stepRA.

[0347] When the RA payload is not received from the terminal before the expiration of T2-stepMsgA from the reception time point of the RA preamble of the two-step random access process according to the CFRA scheme, the base station can identify the terminal based on the RA preamble of the RA MSG-A according to the CFRA scheme (which is received from the corresponding terminal). Therefore, the base station can transmit DCI including scheduling information for transmitting the PDSCH where the RA MSG-B is located to the terminal by using a scheduling identifier (e.g., C-RNTI) specifically assigned to the corresponding terminal or a scheduling identifier for transmitting RAR (e.g., RA-RNTI or RNTI for sending and receiving RA MSG-B). DCI can be transmitted on PDCCH. Therefore, the terminal can receive DCI by performing a PDCCH monitoring operation using a scheduling identifier for receiving RAR or a scheduling identifier assigned to itself. The terminal can obtain one or more of the scheduling information, downlink scheduling information, and uplink scheduling information of the PDSCH where the RA MSG-B is located by receiving DCI from the base station.

[0348] In step S1003, the base station may transmit DCI including allocation information (e.g., scheduling information) of uplink radio resources through PDCCH. Alternatively, in step S1003, the base station may transmit RA MSG-B through PDSCH. RA MSG-B may be transmitted through PDSCH (e.g., PDSCH scheduled by DCI). RA MSG-B may include one or more information elements. For example, RA MSG-B may include allocation information (e.g., scheduling information) of uplink radio resources, transmission timing adjustment information, transmission power adjustment information, beam configuration information, retransmission request information (e.g., retransmission indication information) of RA payload of RA MSG-A, radio resource allocation information for (re)transmission of RA payload of RA MSG-A, and one or more of MCS levels. Each of the multiple information elements included in RA MSG-B may be configured in the form of MAC CE. Alternatively, the multiple information elements included in RA MSG-B may be configured in the form of one MAC CE. In this case, an additional MAC header format may be used. The transmission operation of RA MSG-B based on RA-RNTI can be Fig. 9 The transmission operation of message 2 in step S903 is shown.

[0349] The DCI transmitted in response to the RA MSG-A may include one or more information elements among the information elements included in the above-mentioned RA MSG-B. The terminal may receive the DCI from the base station in response to the RA MSG-A. In this case, the terminal may retransmit the RA payload of the RA MSG-A using the radio resources indicated by the scheduling information included in the DCI. Alternatively, the terminal may retransmit the RA payload of the RA MSG-A using the radio resources indicated by the scheduling information included in the DCI. Fig.10 In step S1004 shown in FIG. 1 , the uplink data and / or control information is transmitted to the base station.

[0350] In step S1002 according to the CBRA scheme, the base station may receive an RA preamble of an RA MSG-A from the terminal. When a decoding operation of an RA payload of the RA MSG-A fails, or when the RA payload of the RA MSG-A is not received before a preconfigured timer (e.g., T2-stepRA or T2-stepMsgA) expires, the base station may not be able to identify the terminal that initiated the two-step random access procedure based on the RA preamble of the RA MSG-A. In this case, when the preconfigured timer expires, the base station may transmit a RA preamble to the terminal. Fig. 9 The RA MSG-2 of step S903 shown in the figure or the RAMSG-B configured in the same manner as the RA MSG-2 (for example, fallback RAR). That is, the two-step random access procedure can be switched to the four-step random access procedure. Therefore, the terminal transmitting the RA MSG-A in step S1002 according to the CBRA scheme can perform a PDCCH monitoring operation (for example, a PDCCH monitoring operation for a UE-specific search space (USS)) to receive the RA MSG-A. Fig.10 RA MSG-B of step S1003 shown in FIG. 1004 , and performing a PDCCH monitoring operation (eg, a PDCCH monitoring operation on a common search space (CSS)) in order to receive Fig. 9 RA MSG2 of step S903 is shown.

[0351] When receiving RA MSG-B (e.g., fallback RAR) or RA MSG2 from the base station after step S1002, the terminal may Fig. 9 The RA MSG3 of step S904 shown in the figure is transmitted to the base station. That is, when receiving RA MSG-B (e.g., fallback RAR) or RA MSG2 from the base station, the terminal can determine that the two-step random access process has been switched to the four-step random access process, and can transmit RA MSG3 of the four-step random access process to the base station. The base station can receive RA MSG3 from the terminal, and can transmit RA MSG4 to the terminal.

[0352] On the other hand, when the base station receives only the RA payload of the RA MSG-A, the following operations may be performed. In step S1002 according to the CFRA scheme, the terminal may transmit the RA MSG-A including the RA preamble and the RA payload to the base station. The base station may receive only the RA payload of the RA MSG-A. That is, the base station may not receive the RA preamble of the RA MSG-A. In this case, the base station may identify the terminal identifier based on (one or more) information elements included in the RA payload of the RA MSG-A. Alternatively, the base station may obtain information for identifying the terminal that has transmitted the RA payload based on the resource allocation rule according to the CFRA scheme. For example, when the transmission resources of the RA payload are exclusively allocated to the terminal, or when the transmission resources of the RA payload are exclusively allocated to the terminal and the transmission resources of the RA preamble are mapped to the transmission resources of the RA payload, the terminal may identify the terminal that has initiated the random access process based on the resource allocation rule according to the CFRA scheme and based on the resources through which the RA payload is received.

[0353] When only the RA payload of RA MSG-A is received and the terminal that has initiated the corresponding random access procedure is identified based on the RA payload, the base station may transmit to the terminal Fig.10 RA MSG-B of step S1003 is shown.

[0354] The base station that receives the RA preamble code can transmit the DCI including the scheduling information of the PDSCH where the RA MSG-B is located by using the terminal-specific scheduling identifier or the scheduling identifier for the transmission of RAR (for example, MSG-B RA-RNTI). The DCI can be transmitted on the PDCCH. Here, the base station can transmit the uplink resource allocation information to the terminal through the PDCCH. The base station can transmit the RA MSG-B to the terminal through the PDSCH indicated by the scheduling information included in the DCI. RAMSG-B may include the above-mentioned (one or more) information elements. The transmission operation of the RA MSG-B based on the RA-RNTI can be the same as Fig. 9 The transmission operation of RA MSG2 in step S903 is the same or similar.

[0355] The DCI transmitted in response to the message 1 (e.g., RA MSG-A, RA preamble) may include one or more of uplink resource allocation information (e.g., scheduling information), transmission timing adjustment information, transmission power adjustment information, and resource allocation information for transmission of the RA payload. When only the DCI is received in response to the RA MSG-A, the terminal may retransmit the RA payload by using the radio resources indicated by the scheduling information included in the DCI. Fig.10Alternatively, the terminal may transmit the RA MSG-A (eg, RA payload) of step S1002 as shown in FIG. 1004 by using the radio resources indicated by the scheduling information included in the DCI. Fig.10 The uplink data and / or control message of step S1004 shown in FIG.

[0356] In step S1002 according to the CBRA scheme, the base station may receive an RA preamble of an RA MSG-A from the terminal. When a decoding operation of an RA payload of the RA MSG-A fails, or when the RA payload of the RA MSG-A is not received before a preconfigured timer (e.g., T2-stepRA or T2-stepMsgA) expires, the base station may not be able to identify the terminal that initiated the two-step random access procedure based on the RA preamble of the RA MSG-A. In this case, when the preconfigured timer expires, the base station may Fig. 9 The RA MSG2 of step S903 shown in the figure is transmitted to the terminal. That is, the two-step random access process can be switched to the four-step random access process. Therefore, the terminal that transmits RA MSG-A in step S1002 according to the CBRA scheme can perform the operation for receiving Fig.10 The PDCCH monitoring operation of the RA MSG-B (eg, the PDCCH monitoring operation on the USS) of step S1003 shown in FIG. Fig. 9 The PDCCH monitoring operation (eg, PDCCH monitoring operation on the CSS) of message 2 (eg, RA MSG2 or fallback RAR) of step S903 is shown.

[0357] The RA-RNTI for MSG-B with SRB may be configured differently from the RA-RNTI for MSG-B with UEsMux. In this case, the terminal may perform a PDCCH monitoring operation based on the RA-RNTI for MSG-B with SRB, and perform a PDCCH monitoring operation based on the RA-RNTI for MSG-B with UEsMux.

[0358] When receiving RA MSG2 of the four-step random access procedure instead of RA MSG-B of the two-step random access procedure after step S1002, the terminal may Fig. 9The RA MSG3 of step S904 shown in the figure is transmitted to the base station. In this case, the RA MSG3 may be configured based on the RA payload of the RA MSG-A. The RA MSG3 may include (one or more) information elements constituting the RA payload of the RA MSG-A. When the configuration of the RA MSG3 is different from the configuration of the RA payload of the RA MSG-A, the RA MSG3 and the RA payload of the RA MSG-A may be distinguished by using a field in the MAC header (or MAC subheader) and / or LCID. When the RA MSG3 is received from the terminal, the RA payload of the RA MSG-A may be distinguished from the RA payload of the RA MSG-A. Fig. 9 When the RA MSG3 of step S904 is sent, the base station may transmit the RA MSG4 of step S905 to the terminal.

[0359] When the two-step random access procedure is switched to the four-step random access procedure, the terminal can identify whether the RAR received from the base station is the RA MSG-B (e.g., fallback RAR) of the two-step random access procedure or the RA MSG2 of the four-step random access procedure. For this operation, the base station can indicate whether the RAR is the RA MSG-B (e.g., fallback RAR) of the two-step random access procedure or the RA MSG2 of the four-step random access procedure based on the following method.

[0360] - Method #1: A method of configuring a scheduling identifier for transmission of RA MSG-B differently from a scheduling identifier for transmission of RA MSG2 (eg, fallback RAR)

[0361] - Method #2: A method of configuring each of the PDCCH, CORESET, and search interval of scheduling information for RA MSG-B (eg, fallback RAR) differently from each of the PDCCH, CORESET, and search interval of scheduling information for RA MSG2

[0362] - Method #3: A method in which DCI (eg, a specific field in DCI) includes information indicating that "scheduling information included in DCI is scheduling information for RA MSG-B (eg, fallback RAR) or RA MSG2"

[0363] - Method #4: A method in which the RAR includes information indicating whether the corresponding RAR is RA MSG-B (eg, fallback RAR) or RA MSG2

[0364] The RA MSG-B of the two-step random access procedure can be distinguished from the RA MSG2 of the four-step random access procedure by the scheduling identifier (e.g., RA-RNTI) of the RAR. In this case, the RA MSG-B can be transmitted based on the scheduling information addressed by the RA-RNTI configured for the RA MSG-B, and the RA MSG2 can be transmitted based on the scheduling information addressed by the RA-RNTI configured for the RA MSG2.

[0365] Alternatively, when the two-step random access procedure is switched to the four-step random access procedure, a separate RA-RNTI (e.g., fallback RA-RNTI) for message 2 may be allocated. The terminal that initiated the two-step random access procedure may transmit RA MSG2 of the four-step random access procedure. In this case, RA MSG2 may be transmitted based on scheduling information addressed by the fallback RA-RNTI.

[0366] Scheduling information for transmission resources of RA MSG-B may be sent and received using the RA-RNTI configured for RA MSG-B. Scheduling information for transmission resources of fallback RAR may be sent and received using the RA-RNTI for the four-step random access procedure or the RA-RNTI configured for fallback RAR. Therefore, the RA-RNTI for RA MSG2, the RA-RNTI for RA MSG-B (e.g., successful RAR), and the RA-RNTI for fallback RAR may be configured differently, and the configured RA-RNTI may be signaled to the terminal from the base station. RA MSG-B may be classified into successful RAR and fallback RAR. Successful RAR may be an RA MSG-B transmitted from a base station that has successfully received both the RA preamble and the RA payload of RA MSG-A. The fallback RAR may be an RA MSG-B transmitted from a base station that has only received the RA preamble of RA MSG-A.

[0367] For RA MSG2, successful RAR and / or fallback RAR, CORESET, search interval and / or PDCCH may be configured differently. The base station may configure different CORESET, search interval and / or PDCCH resources for each message 2 (e.g., RA MSG2, successful RAR, fallback RAR), and transmit the configuration information of CORESET, search interval and / or PDCCH resources to the terminal by using system information and / or control message (e.g., dedicated control message).

[0368] Alternatively, the DCI including resource allocation information (e.g., scheduling information) of the PDSCH on which the message 2 is transmitted may include a field indicating whether the message 2 scheduled by the DCI is RA MSG2, successful RAR, or fallback RAR. In this case, the terminal can receive the DCI including the scheduling information by using the RA-RNTI, and identify whether the message 2 scheduled by the DCI is RA MSG2, successful RAR, or fallback RAR based on the field contained in the DCI.

[0369] Alternatively, a separate MAC subheader for transmitting message 2 or a "MsgB-type" field indicating the format of RA MSG-B may be configured. The MAC subheader or MsgB-type field may indicate whether message 2 is RA MSG2, successful RAR, or fallback RAR. The base station may transmit an MsgB-type field or a MAC subheader indicating whether message 2 is RA MSG2, successful RAR, or fallback RAR. The terminal may receive a MAC subheader or MsgB-type field from the base station, and may identify whether message 2 is RA MSG2, successful RAR, or fallback RAR based on the MAC subheader or MsgB-type field.

[0370] When the carrier aggregation (CA) function is supported, multiple cells (or base stations) can provide communication services to the terminal. The primary cell (PCell) that controls the CA operation can activate or deactivate the secondary cell (SCell) that supports the CA function. In addition, the terminal can perform a CFRA process or a CBRA process with each of the PCell and the SCell for a beam recovery process with multiple cells. When radio resources for the CFRA process are exclusively allocated to the terminal, if the quality of the radio resources does not meet the existing conditions, the terminal can perform a CBRA process instead of a CFRA process for beam recovery.

[0371] For beam recovery of each of PCell and SCell, a CFRA process or a CBRA process may be performed. In this case, by using the RA payload of RA MSG3 or RA MSG-A, the terminal may transmit one or more of the terminal identifier, configured beam information (e.g., TCI state, CSI-RS index, or SS / PBCH index capable of identifying the beam), beam measurement result information, and cell measurement result information to the base station. In addition, the terminal may transmit information of a preferred beam to the base station.

[0372] When performing a random access procedure to support the mobility of a terminal, the terminal may transmit information requesting deactivation of a base station (or cell) by using the RA payload of RA MSG3 or RAMSG-A. For example, when the source base station and the target base station simultaneously provide communication services to the terminal during a handover, the terminal may transmit information requesting (or triggering) deactivation of the source base station or the target base station by using the RA payload of RA MSG3 or RA MSG-A. In this case, the terminal may transmit the identifier of the base station to be deactivated together with the information requesting deactivation.

[0373] During the handover process, beam failure or RLF may occur. In this case, the base station and the terminal may store / maintain context information (e.g., RRC context information, AS context information) until a preconfigured timer (e.g., TRRC_CONT) expires. When beam failure or RLF occurs during the handover process, an RRC connection reestablishment process may be performed. In this case, if the RRC connection reestablishment process is completed before the preconfigured timer (e.g., TRRC_CONT) expires, the base station and the terminal may reuse the stored context information (e.g., RRC context information, AS context information).

[0374] In this case, in the CBRA process or CFRA process performed in the RRC connection reestablishment process, one or some parameters can be reconfigured based on the above-mentioned measurement results. During the RRC connection reestablishment process, some parameters of the context information between the base station and the terminal can be updated (e.g., changed), and the remaining (one or more) parameters of the context information can be used again. For example, the (one or more) beam configuration parameters or (one or more) BWP configuration parameters of the context information can be reconfigured, and the remaining (one or more) parameters of the context information can be maintained. For this operation, the base station can use system information and / or a control message (e.g., a dedicated control message) to configure TRRC_CONT and pass TRRC_CONT to the terminal.

[0375] Each of the RA MSG1 of the four-step random access procedure and the RA MSG-A of the two-step random access procedure may be transmitted one or more times within one random access opportunity (e.g., random access opportunity (RO)). The terminal may retransmit the RA MSG1 or RA MSG-A by using different radio resources in the time domain and / or frequency domain before receiving message 2 from the base station. In such a retransmission process, the terminal may randomly select a random access (RA) resource based on a mapping relationship for an SS / PBCH index or a CSI-RS index (e.g., a resource index of a CSI-RS). Alternatively, in such a retransmission process, the terminal may select a radio resource associated with the initially selected RA resource (e.g., a transmission resource of RA MSG1, a transmission resource of RA MSG-A (e.g., RA preamble, RA payload)) according to the mapping relationship.

[0376] For the BFR process or the handover process, the base station may allocate multiple RA resources exclusively to the terminal (e.g., CFRA scheme). For example, the base station may transmit information of multiple RA resources mapped to multiple beams to the terminal. Alternatively, the base station may transmit information of multiple RA resources configured in the time domain and / or frequency domain to the terminal regardless of the beam. The terminal may receive information of the exclusively allocated RA resources from the base station, and may retransmit RA MSG1 or RA MSG-A by using multiple RA resources.

[0377] When uplink physical layer synchronization between multiple terminals is maintained in an OFDMA-based communication system, interference between multiple terminals can be reduced. The base station can transmit transmission timing adjustment information (e.g., TA information) to the terminal. The terminal can adjust the uplink physical layer synchronization with the base station based on the transmission timing adjustment information received from the base station. Therefore, the signals received from multiple terminals can be aligned at the base station within a specific time period, and in this case, interference between multiple terminals can be reduced.

[0378] In the two-step random access process, the terminal may transmit the RA payload of RA MSG-A to the base station without transmission timing adjustment information. When uplink synchronization between the terminal and the base station is not maintained, the RA payload of RA MSG-A may cause interference between terminals, and the reception performance of the RA payload of RA MSG-A may be degraded. In order to solve this problem, a transmission gap may be configured in the front part of the uplink radio resource (e.g., PUSCH) where the RA payload of RA MSG-A is transmitted.

[0379] Fig.11 is a conceptual diagram illustrating a first exemplary embodiment of an RA MSG-A transmission method in a communication system.

[0380] Reference Fig.11 , the PUSCH resources for the first terminal may be aligned with the subframe. For example, the start time point of the PUSCH resources for the first terminal may be aligned at the start time point of subframe #2 in the time domain, and the end time point of the PUSCH resources for the first terminal may be aligned at the end time point of subframe #2 in the time domain. The transmission resources for the RA payload of the RA MSG-A may be allocated in subframe #2. In subframe #2, a transmission gap may be configured before the transmission resources for the RA payload of the RA MSG-A. The RA payload of the RA MSG-A may be transmitted by using the transmission resources after the transmission gap. This may be applied even when the transmission resources for the PUSCH and the RA payload are configured in a time slot or a micro-time slot instead of a subframe. Fig.11 An exemplary embodiment is shown in .

[0381] The subframe in which the transmission resources of the RA payload of the RA MSG-A are located may be the same as the subframe in which the transmission resources used for the uplink transmission procedure other than the random access procedure (e.g., the PUSCH of the first terminal) are located. Alternatively, the subframe in which the transmission resources of the RA payload of the RA MSG-A are located may be different from the subframe in which the transmission resources used for the uplink transmission procedure other than the random access procedure (e.g., the PUSCH of the first terminal) are located.

[0382] For example, subframe #1 may be configured as a radio resource (e.g., RA resource) for a random access procedure, and other subframes (e.g., subframes #2 to #3) may be configured as radio resources for a general uplink transmission procedure instead of a random access procedure. The transmission gap may be configured in units of symbols or as an absolute time. The base station may transmit information indicating whether there is a transmission gap and length information of the transmission gap to a terminal (e.g., a second terminal) by using system information and / or a control message (e.g., a dedicated control message).

[0383] The second terminal may identify information indicating whether there is a transmission gap and length information of the transmission gap by receiving system information and / or a control message (e.g., a dedicated control message) from the base station before performing the two-step random access procedure. When there is a transmission gap, the second terminal may transmit the RA payload of the RA MSG-A to the base station by using radio resources after the transmission gap. When there is no transmission gap, the second terminal may transmit the RA payload of the RA MSG-A to the base station based on the estimated subframe synchronization. In this case, the RA payload of the RA MSG-A may be transmitted from the start time point of the subframe. For example, the transmission resources of the RA payload of the RA MSG-A may be configured in the same manner as the transmission resources of the PUSCH in subframe #2.

[0384] The transmission gap may be used for transmission of a reference signal or a preamble (e.g., RA MSG-A) for a two-step random access procedure. The reference signal (or preamble) may be a signal designed to compensate for a delay spread of a base station or a transmission delay in a radio segment. The reference signal (or preamble) may be designed in consideration of the cyclic prefix (CP) of an OFDMA symbol. The reference signal (or preamble) may be transmitted in the transmission gap. Alternatively, the reference signal (or preamble) may be transmitted through radio resources after the transmission gap. The RA payload of the RA MSG-A may be transmitted after the transmission of the reference signal (or preamble). For example, in the time domain, the transmission resources of the reference signal (or preamble) may be located after the transmission gap, and the transmission resources of the RA payload of the RA MSG-A may be located after the transmission gap of the reference signal (or preamble).

[0385] Fig.12a is a conceptual diagram showing a first exemplary embodiment of a MAC subheader in a random access procedure, Figure 12b is a conceptual diagram showing a second exemplary embodiment of a MAC subheader in a random access procedure, Fig.12c is a first exemplary embodiment showing a RA MSG-B in a random access procedure, Fig.12d is a conceptual diagram showing a second exemplary embodiment of a RA MSG-B in a random access procedure, Fig.12e is a conceptual diagram showing a third exemplary embodiment of a random access procedure RA MSG-B, and Fig.12f is a conceptual diagram showing a fourth exemplary embodiment of RA MSG-B in a random access procedure.

[0386] Reference Figure 12a to 12F, RA MSG-B can be classified into successful RAR and fallback RAR. RA MSG-B can include a MAC header (e.g., MAC subheader) and / or a MAC payload (e.g., MAC RAR or MAC sub-PDU). Alternatively, when RAMSG-B includes only a MAC payload (e.g., MAC RAR), the MAC header (e.g., MAC subheader) can be configured separately from the MAC RAR (or MAC sub-PDU). Figure 12c to Figure 12f The exemplary embodiment shown may be a MAC payload (eg, MACRAR).

[0387] The MAC subheader included in the RA MSG-B may be a backoff indicator (BI) subheader or a random access preamble identifier or a random access preamble index (RAPID) subheader. The BI subheader and the RAPID subheader may be distinguished by using the T field of the MAC subheader. Fig.12a As shown, a MAC subheader with the T field set to "0" may be a BI subheader, and Figure 12b As shown, the MAC subheader with the T field set to "1" may be a RAPID subheader. When the terminal performs a random access procedure to request transmission of system information, the RA MSG-B in the corresponding random access procedure may include a RAPID subheader.

[0388] RA MSG-B may be transmitted based on scheduling information addressed by a scheduling identifier (e.g., MSG-B RA-RNTI) for a two-step random access procedure. RA preamble generation may be based on RA MSG-A Figure 12b The RAPID subheader shown in FIG. RAPID of the RAPID subheader may indicate the RA preamble index of the RA MSG-A. The T field included in each of the BI subheader and the RAPID subheader may be used to distinguish different RA MSG-Bs (eg, MAC RARs).

[0389] like Fig.12c As shown in the exemplary embodiment shown in the figure, when the C-RNTI is assigned to the terminal and the RAMSG-A is received from the terminal, the T field may be set to "0". The RA MSG-B may include transmission timing adjustment information (e.g., TA command), uplink resource allocation information (e.g., UL grant), and the C-RNTI assigned to the terminal. Fig.12dAs shown in the exemplary embodiment shown, when C-RNTI is not assigned to the terminal and RA MSG-A is received from the terminal, the T field may be set to "1". RA MSG-B may include transmission timing adjustment information (e.g., TA command), uplink resource allocation information (e.g., UL grant), TC-RNTI, and UE contention resolution ID for contention resolution. The UE contention resolution ID may be a terminal identifier (e.g., UE ID) included in the RA payload of the RA MSG-A. When the size of the UE contention resolution ID is 6 bytes (i.e., 48 bits), Fig.12d Octet N in may be octet #13.

[0390] exist Fig.12d In the RA MSG-B shown in FIG. 1 , the UE contention resolution ID may be omitted. In this case, the UE contention resolution ID may be transmitted in the form of a MACCE. For example, the RA MSG-B may be configured with Fig.12d The MAC CE of the (one or more) information elements shown and a separate MAC CE including the UE contention resolution ID. When the RA MSG-B includes two MAC CEs, the two MAC CEs can be transmitted in the same radio resource area. Alternatively, the two MAC CEs can be transmitted through different radio resource areas. Alternatively, the RA MSG-B can include "MAC CE+RRC control information" or "MAC CE+downlink data". RRC control information or downlink data can be transmitted in the transmission resources of the second MAC CE for the RA MSG-B.

[0391] The MAC RAR format for RA MSG-B may be the same as the MAC RAR format for RA MSG 2. In this case, the scheduling identifier (eg, RA-RNTI, MSG-B RA-RNTI) for transmission of message 2 may be shared in the two-step random access procedure and the four-step random access procedure.

[0392] Fig.12e The exemplary embodiment shown may be a MAC RAR for RA MSG2. When C-RNTI is not assigned to the terminal and RA MSG-A is received from the terminal, the base station may transmit RA MSG-B including timing adjustment information (e.g., TA information), uplink resource allocation information (e.g., UL grant), and a scheduling identifier (e.g., TC-RNTI) to the terminal. The UE contention resolution ID may be transmitted through a MAC header (or MAC subheader), and the LCID may be transmitted through a separate MAC CE. Fig.12dThe RA MSG-B including the UE contention resolution ID is configured as in the illustrated exemplary embodiment. In this case, the T field of octet #1 may be replaced with an R field.

[0393] exist Fig.12f In the exemplary embodiment shown, when C-RNTI is assigned to the terminal and RAMSG-A is received from the terminal, the base station can transmit a RA MSG-B to the terminal including timing adjustment information (e.g., TA information), uplink resource allocation information (e.g., UL grant), and a scheduling identifier assigned to the terminal (e.g., C-RNTI).

[0394] Fig.13a is a conceptual diagram showing a fifth exemplary embodiment of a RA MSG-B in a random access procedure, Fig.13b is a conceptual diagram showing a sixth exemplary embodiment of a RA MSG-B in a random access procedure, and Fig.13c is a conceptual diagram illustrating a seventh exemplary embodiment of a RA MSG-B in a random access procedure.

[0395] Reference Figures 13a to 13c , the RA MSG-B may be transmitted based on the scheduling information addressed by the RA-RNTI or C-RNTI. The RA MSG-B may optionally include a BI subheader (e.g., Fig.12a When the terminal performs a random access procedure to acquire system information, the RA MSG-B may include only the RAPID subheader (e.g., Figure 12b RAPID subheader shown).

[0396] exist Fig.13b In the exemplary embodiments of 13C and 13D, when a scheduling identifier (e.g., C-RNTI) is not assigned to the terminal and the terminal performs a two-step random access procedure, the base station may transmit MSG-B based on the MSG-B RA-RNTI. The RA preamble code of the RA MSG-A transmitted by the terminal may include Figure 12b The RAPID subheader shown. The base station may receive a RA MSG-A from the terminal, and may transmit a RA MSG-B to the terminal in response to the RA MSG-A. The T field may indicate whether the RA MSG-B contains a TA command.

[0397] A RA MSG-B containing a T field set to "1" (e.g., Fig.12d The RA MSG-B) shown may include the following information elements.

[0398] - Transmit timing adjustment information (e.g., TA command)

[0399] -UL resource allocation information (e.g., UL grant)

[0400] - Scheduling identifier (e.g., TC-RNTI)

[0401] -UE Contention Resolution ID

[0402] RA MSG-B including a T field set to "0" (e.g., Fig.13a The RA MSG-B) shown in FIG. 1 may include the following information elements.

[0403] -UL resource allocation information (e.g., UL grant)

[0404] - Scheduling identifier (e.g., TC-RNTI)

[0405] -UE Contention Resolution ID

[0406] Fig.12a The BI subheader shown and Figure 12b The E field included in each of the illustrated RAPID subheaders may be a field indicating whether the MAC subheader is extended. The E field set to "1" may indicate that another MAC subheader exists continuously after the corresponding MAC subheader. The E field set to "0" may indicate that the corresponding MAC subheader is the last MAC subheader. That is, after the MAC subheader including the E field set to "0", another MAC subheader may not exist.

[0407] In the above exemplary embodiment, the scheduling identifier (e.g., MSG-BRA-RNTI, RA-RNTI, C-RNTI) used for the scheduling information of message 2 may be changed according to whether C-RNTI is assigned to the terminal that attempts the two-step random access procedure. Alternatively, the base station may transmit the scheduling information of message 2 to the terminal by using the scheduling identifier regardless of whether C-RNTI is assigned, and the base station may transmit message 2 (e.g., RA MSG2, RA MSG-B) to the terminal based on the scheduling information.

[0408] For example, when the base station receives RA MSG-A including C-RNTI in consideration of downlink radio resources or RAR window, or when the base station identifies the C-RNTI of the terminal that initiated the two-step random access process according to the CFRA scheme, the base station can transmit DCI including scheduling information to the terminal by using MSG-B RA-RNTI or RA-RNTI, and can transmit message 2 (e.g., RA MSG-B) to the terminal by using the resources indicated by the scheduling information. Regardless of whether C-RNTI is assigned, the base station can transmit message 2 having the same format to the terminal. Therefore, the terminal that transmits RA MSG-A can perform a PDCCH monitoring operation by using both MSG-B RA-RNTI (or RA-RNTI) and C-RNTI to receive RA MSG-B. When the MSG-B RA-RNTI for MSG-B with SRB and the MSG-B RA-RNTI for MSG-B with UEsMux are configured differently, the terminal can perform a PDCCH monitoring operation through both the MSG-B RA-RNTI for MSG-B with SRB and the MSG-B RA-RNTI for MSG-B with UEsMux.

[0409] At the same time, the terminal can receive a MSG-B with UEsMux that does not contain RRC control information. In this case, the terminal can perform a PDCCH monitoring operation by using the TC-RNTI contained in the MSG-B with UEsMux to receive an RRC message or a DRB packet. In the two-step random access process, the PDSCH where the MSG-B with UEsMux is transmitted may be configured differently from the PDSCH where the RRC message or the DRB packet is transmitted. The base station may transmit an MSG-B with UEsMux on the PDSCH and may transmit a DRB packet on another PDSCH. In this case, the terminal can perform a PDCCH monitoring operation by using both the MSG-B RA RNTI for the MSG-B with UEsMux and the TC-RNTI contained in the MSG-B with UEsMux to receive scheduling information of the MSG-B with UEsMux and an RRC message (or DRB data packet).

[0410] According to the exemplary embodiments shown in Figures 12 and 13, when transmitting RA MSG-B based on the scheduling information addressed by MSG-B RA-RNTI in the two-step random access process, the base station can transmit message 2 (e.g., RA MSG-B) to one or more terminals. A separate MAC subheader or "MsgB-type" field indicating the format type of RA MSG-B can indicate (one or more) information elements contained in RA MSG-B. RA MSG-B can include one or more of TA information, UL grant, TC-RNTI, UEID, beam configuration information, and TCI status information.

[0411] In addition, the MAC subheader may indicate whether the corresponding message 2 is RA MSG2, successful RAR, or fallback RAR. For example, the terminal may transmit RA MSG-A to the base station, and may receive message 2 from the base station. The terminal may identify whether the corresponding message 2 is RA MSG2, successful RAR, or fallback RAR based on the MAC subheader included in message 2.

[0412] The MAC RAR format of each of the successful RAR and the fallback RAR may be the same as the MAC RAR format of the exemplary embodiments in FIGS. 12 , 13 , 14 , 16 , and 17 . The RA MSG-B (e.g., successful RAR, fallback RAR) may include one or more of TA information, UL grant, TC-RNTI, UE ID, beam configuration information, and TCI status information. Figure 12b 12. The RA MSG-B is generated without the RAPID subheader shown in FIG. That is, the RA MSG-B can be generated according to the exemplary embodiments shown in FIGS. 14, 16 and 17. For one or more terminals, in order to transmit the RA MSG-B, a MAC subheader for identifying the RA MSG-B can be generated for each terminal. The MAC subheader can be located at the front of the MAC RAR in the MSG-B MAC PDU. That is, it can be configured in the form of a separate MAC subheader as shown in the exemplary embodiment shown in FIG. 12. The terminal can identify the number of MAC RARs included in the MSG-B MAC PDU based on the MAC subheader included in the MSG-B MAC PDU.

[0413] In the two-step random access process, the terminal can distinguish a successful RAR from a fallback RAR based on the MAC subheader in the MSG-B MAC PDU. The terminal can determine whether the corresponding message 2 is for itself by comparing its UE ID (e.g., the UE ID included in the RA MSG-A) with the UE ID included in the message 2. A successful RAR may mean an RA MSG-B (e.g., RA preamble, RA payload) transmitted by the base station that has successfully received the RA MSG-A. The base station can generate one MAC PDU containing the RA MSG-B for one or more terminals, and can transmit the one MAC PDU on a downlink channel (e.g., PDSCH).

[0414] When the transmission resources of the RA preamble used for the two-step random access procedure are the same as the transmission resources of the RA preamble used for the four-step random access procedure, and the RA preamble index of the two-step random access procedure is different from the RA preamble index of the four-step random access procedure, RA MSG2 and fallback RAR can be multiplexed in one MAC PDU. The one MAC PDU including RA MSG2 and fallback RAR can be transmitted on a downlink channel (e.g., PDSCH). This operation can be performed when the scheduling identifier (e.g., RA-RNTI) used for the two-step random access procedure is the same as the scheduling identifier used for the four-step random access procedure. Since RA MSG2 includes the index of the RA preamble included in RA MSG1 transmitted by the terminal, and RA MSG-B includes the index of the RA preamble included in RA MSG-A transmitted by the terminal, the terminal can distinguish RA MSG-B from RA MSG2 based on the index of the RA preamble transmitted by the terminal.

[0415] Fig.14a is a conceptual diagram showing an eighth exemplary embodiment of a RA MSG-B in a random access procedure, Fig.14b is a conceptual diagram showing a ninth exemplary embodiment of a RA MSG-B in a random access procedure, Fig.14c is a conceptual diagram illustrating a tenth exemplary embodiment of a RA MSG-B in a random access procedure.

[0416] Fig.14a and Fig.14b The exemplary embodiment shown may be a RA MSG-B generated based on the RAPID subheader, and Fig.14cThe exemplary embodiment shown may be a RA MSG-B generated without a RAPID subheader. The E field may indicate whether there is another MAC RAR after the corresponding MAC RAR (i.e., the MAC RAR including the corresponding E field). The E field set to "1" may indicate that there is another MAC RAR after the corresponding MAC RAR. The E field set to "0" may indicate that there is no other MAC RAR after the corresponding MAC RAR. That is, the MAC RAR including the E field set to "0" may be the last MAC RAR.

[0417] The T field may indicate whether the MAC RAR is a successful RAR or a fallback RAR. A T field set to "1" may indicate that the corresponding MAC RAR (i.e., the MAC RAR including the corresponding T field) is a successful RAR (e.g., Fig.14a RA MSG-B shown). A T field set to "0" may indicate that the corresponding MAC RAR is a fallback RAR (e.g., Fig.14b When the RA MSG-B is generated without the RAPID subheader, the fallback RAR may include the RAPID, as shown in Fig.14c As in the exemplary embodiment shown in .

[0418] When the length of the UE ID (e.g., UE contention resolution ID) included in the MAC RAR is fixed to one of two values, the ID field may indicate whether the UE ID included in the MAC RAR is a long UE ID or a short UE ID UE ID. An ID field set to "1" may indicate that the corresponding MAC RAR (i.e., a MAC RAR including the corresponding ID field) includes a long UE ID. An ID field set to "0" may indicate that the corresponding MAC RAR includes a short UE ID. Since the length of the UE ID included in the MAC RAR is fixed to one of two values, the terminal can identify the number of octets representing the UE ID based on the ID field. That is, the terminal can identify N shown in Figure 14 based on the ID field.

[0419] The G field may indicate whether the second message includes a UL grant. A G field set to "1" may indicate that the corresponding second message (i.e., the second message including the G field) includes a UL grant. When the G field included in the successful RAR is set to "1", the corresponding G field may indicate that the successful RAR also includes a UL grant. A G field set to "0" may indicate that the corresponding second message does not include a UL grant. When the G field is set to "1", even if the T field included in the successful RAR is set to "1", the corresponding successful RAR (e.g., Fig.14bThe RA MSG-B shown may also include a UL grant. The UL grant may include uplink resource allocation information (e.g., resource allocation information in the time domain and the frequency domain), an MCS level, a BWP index, information indicating whether to perform retransmission (or retransmission), the number of retransmissions (or retransmissions), and a time period for retransmissions (or retransmissions).

[0420] The exemplary embodiments shown in FIGS. 12 to 14 may be RA MSG-B. The arrangement order of the fields included in the RA MSG-B may be different from the arrangement order of the fields in the exemplary embodiments shown in FIGS. 12 to 14. The RA MSG-B may include one or some of the fields shown in FIGS. 12 to 14. The MAC subheader used for the RA MSG-B may be the BI subheader described above. The MAC subheader used for a successful RAR or a fallback RAR may be a RAPID subheader.

[0421] The MAC subheader for RA MSG-B may further include information indicating the time when RA MSG-A was received. The information indicating the time when RA MSG-A was received may be represented by a system frame number (SFN), a subframe index, a slot index, a symbol index and / or an offset. When a RAPID subheader for RA MSG-B is used, the corresponding RA MSG-B (e.g., a RA MSG-B associated with or corresponding to a RAPID subheader) may be distinguished from other MAC RARs (e.g., a fallback RAR, a success RAR, or a RAMSG-B associated with a BI subheader). When the BI subheader is transmitted before a success RAR or a fallback RAR, the BI subheader may be the first MAC subheader in consecutive MAC subheaders. When the RAPID subheader is transmitted before the BI subheader, the BI subheader may be the last MAC subheader in consecutive MAC subheaders.

[0422] The MAC subheader (e.g., RAPID subheader) for successful RAR and the MAC subheader (e.g., RAPID subheader) for fallback RAR may not be transmitted alternately. The RAPID subheader for fallback RAR may be arranged first, and the RAPID subheader for successful RAR may be arranged after the last RAPID subheader for fallback RAR. Alternatively, the RAPID subheader for successful RAR may be arranged first, and the RAPID subheader for fallback RAR may be arranged after the last RAPID subheader for successful RAR. When the RAPID subheader for successful RAR is arranged before the RAPID subheader for fallback RAR, the fallback RAR may be transmitted after the successful RAR is transmitted. Alternatively, when the RAPID subheader for fallback RAR is arranged before the RAPID subheader for successful RAR, the successful RAR may be transmitted after the fallback RAR is transmitted.

[0423] When based on Figure 12b When generating a RA MSG-B based on the RAPID subheader shown in FIG. 14 , a successful RAR and a fallback RAR can be distinguished based on the control field shown in FIG. 14 . For example, a successful RAR and a fallback RAR can be distinguished based on the T field. The size of the MAC subheader for RAMSG-B can be 2 bytes. A MAC subheader having a size of 2 bytes may include the above-mentioned E field, a T field (e.g., a T field having a size of 2 bits), and a RAPID. A T field set to "00" may indicate that a BI is transmitted. A T field set to "10" may indicate that the corresponding message 2 (e.g., a message 2 associated with a MAC subheader including the corresponding T field) is a successful RAR. A T field set to "01" may indicate that the corresponding message 2 is a fallback RAR. A T field set to "11" may indicate that the corresponding message 2 is a RA MSG-B including RRC control information (e.g., a MSG-B with SRB). When the T field is set to "11", the MAC subheader and / or RAR may include an LCID for an RRC message (e.g., RRC control information).

[0424] The RAPID subheader may be included in the fallback RAR. When the success RAR and the fallback RAR are transmitted together, the RAPID subheader may be associated with the fallback RAR. The fallback RAR may be arranged and transmitted according to the arrangement order of the RAPID subheader. The success RAR may be arranged after the fallback RAR. That is, the success RAR may be transmitted after the fallback RAR. The E field may be located at the front of the success RAR, and the E field may indicate whether there is another RAR after the success RAR. The success RAR may include UE contention resolution ID, TC-RNTI, TA command, etc. In this case, the arrangement order of the information elements included in the success RAR may be as follows.

[0425] - Arrangement order #1: E field → UE contention resolution ID → TC-RNTI → TA command

[0426] - Arrangement order #2: E field → UE contention resolution ID → TA command → TC-RNTI

[0427] - Arrangement order #3: UE contention resolution ID → E field → TC-RNTI → TA command

[0428] - Arrangement order #4: UE contention resolution ID → E field → TA command → TC-RNTI

[0429] - Arrangement order #5: E field → TC-RNTI → TA command → UE contention resolution ID

[0430] - Arrangement order #6: E field → TA command → TC-RNTI → UE contention resolution ID

[0431] - Arrangement order #7: UE contention resolution ID → TC-RNTI → TA command → E field

[0432] - Arrangement order #8: UE contention resolution ID → TA command → TC-RNTI → E field

[0433] - Arrangement order #9: TC-RNTI → TA command → UE contention resolution ID → E field

[0434] - Arrangement order #10: TA command → TC-RNTI → UE contention resolution ID → E field

[0435] The MSG-B MAC PDU or successful RAR may further include an index of a BWP in which the RRC message or uplink message is transmitted after the corresponding successful RAR. The terminal may obtain the BWP index from the RA MSG-B received from the base station, and may obtain scheduling information by performing a PDCCH monitoring operation within the BWP corresponding to the BWP index.

[0436] The following exemplary embodiments may be considered in the above two-step random access procedure and four-step random access procedure: The transmission resources of the RA preamble code for each of the two-step random access procedure and the four-step random access procedure may be configured based on the following PRACH configuration method #1 or PRACH configuration method #2.

[0437] -PRACH configuration method #1: PRACH resources for a two-step random access procedure are configured differently from PRACH resources for a four-step random access procedure.

[0438] -PRACH configuration method #2: Sharing PRACH resources in two-step random access procedure and four-step random access procedure. The same PRACH resources are used in two-step random access procedure and four-step random access procedure.

[0439] The PRACH resource may be referred to as a RACH opportunity (RO). When PRACH configuration method #1 or PRACH configuration method #2 is used, the following may be considered. The RA MSG-B of the two-step random access procedure may be distinguished from the RAMSG2 of the four-step random access procedure. The terminal may identify whether message 2 (e.g., RA MSG-B) of the two-step random access procedure is a successful RAR, a fallback RAR, or a RAR including a BI. The RAR transmission scenario may be defined as shown in Table 1 below.

[0440] Table 1

[0441]

[0442]

[0443] When the PRACH configuration method #1 of Table 1 is used in the communication system, a successful RAR, a fallback RAR, a BI (e.g., a RAR including a BI), and a RA MSG2 may be distinguished according to case #1 or case #2. In case #1, the RA-RNTI for RA MSG-B may be configured differently from the RA-RNTI for RA MSG2. When the RO of the two-step random access procedure is distinguished from the RO of the four-step random access procedure, the RA-RNTI of the two-step random access procedure may be configured differently from the RA-RNTI of the four-step random access procedure.

[0444] The RO of the two-step random access process and the RO of the four-step random access process can be distinguished based on the mapping relationship (e.g., association relationship) between PRACH and RO. Here, PRACH can be the resource where message 1 (e.g., RA MSG1, RA MSG-A) is actually transmitted, and RO can be a candidate resource where message 1 can be transmitted. The terminal can distinguish RA MSG-B from RA MSG2 by using the RA-RNTI associated with the RO of the two-step random access process and the RA-RNTI associated with the RO of the four-step random access process, where they are configured differently. The terminal can distinguish between successful RAR, fallback RAR and BI (e.g., RAR including BI) based on information obtained through PHY signaling and / or MAC signaling.

[0445] In case #2, one RA-RNTI associated with the RO for the two-step random access procedure may be used for transmission of a successful RAR, and another RA-RNTI associated with the RO for the two-step random access procedure may be used for transmission of a fallback RAR. The RA-RNTI may be determined according to an association scheme for the RO for the four-step random access procedure. According to the new association scheme, a new RA-RNTI (e.g., MSG-B RA-RNTI) associated with the RO for the two-step random access procedure may be configured, and the new RA-RNTI may be used to transmit the fallback RAR. In order to configure the new RA-RNTI (e.g., MSG-B RA-RNTI), an offset may be applied to the association scheme for the RO for the four-step random access procedure.

[0446] The scheduling identifier for transmission of the BI (e.g., RAR including the BI) may be a new RA-RNTI (e.g., MSG-B RA-RNTI). Alternatively, the scheduling identifier for transmission of the BI (e.g., RAR including the BI) may be a scheduling identifier of a successful RAR or a fallback RAR. The terminal may distinguish between the BI (e.g., RAR including the BI), the successful RAR, and the fallback RAR based on information obtained through PHY signaling and / or MAC signaling.

[0447] When the PRACH configuration method #2 of Table 1 is used in the communication system, a successful RAR, a fallback RAR, a BI (e.g., a RAR including a BI), and a RA MSG2 may be identified according to case #3, case #4, or case #5. In PRACH configuration method #2, the RO used for the two-step random access procedure may be the same as the RO used for the four-step random access procedure. Alternatively, the same RO may be shared in the two-step random access procedure and the four-step random access procedure. The RA-RNTI associated with the RO used for the four-step random access procedure may be the same as the RA-RNTI associated with the RO used for the two-step random access procedure.

[0448] In case #3, a new MSG-B RA-RNTI may be introduced, and the terminal may distinguish between successful RAR, fallback RAR, and BI (e.g., RAR including BI) based on information obtained through PHY signaling and / or MAC signaling. The new MSG-B RA-RNTI may be configured by applying an offset to the association scheme of the RO for the four-step random access procedure.

[0449] In case 4, a new MSG-B RA-RNTI for successful RAR and another new MSG-B RA-RNTI for fallback RAR may be introduced. The new MSG-B RA-RNTI may be configured by applying an offset to the association scheme of the RO for the four-step random access procedure. An additional MSG-B RA-RNTI may be allocated for the transmission of the BI (e.g., the RAR including the BI). Alternatively, the scheduling identifier used for the transmission of the BI (e.g., the RAR including the BI) may be the scheduling identifier used for the transmission of the successful RAR or the fallback RAR.

[0450] In case #5, a new MSG-B RA-RNTI may be introduced for transmitting a successful RAR. The RA-RNTI for the fallback RAR may be the same as the RA-RNTI for RA MSG2. The base station may multiplex the fallback RAR and RA MSG2 in one MAC PDU and transmit one MAC PDU on the PDSCH. In addition, the BI (e.g., RAR including the BI) may be multiplexed with the fallback RAR and RAMSG2 in one MAC PDU. The terminal may distinguish between the fallback RAR, the BI (e.g., RAR including the BI), and the RA MSG2 based on information obtained through PHY signaling and / or MAC signaling.

[0451] The base station may transmit to the terminal, through system information and / or a control message (e.g., a dedicated control message), (one or more) parameters for PRACH configuration method #1, (one or more) parameters for PRACH configuration method #2, and an offset applied to the association scheme for configuring a new MSG-B RA-RNTI. The (one or more) information elements transmitted through MAC signaling may be (one or more) information elements indicated by (one or more) fields shown in Figures 12 to 14. The (one or more) information elements transmitted through PHY signaling may be (one or more) information elements indicated by (one or more) fields included in the DCI.

[0452] When the configuration of the MSG-B RA-RNTI for the successful RAR is different from that of the MSG-B RA-RNTI for the fallback RAR, PHY signaling and / or MAC signaling for transmitting information for identifying the successful RAR and the fallback RAR may not be required. When multiple RA MSG-As (e.g., RA preambles) are received from multiple terminals in a two-step random access process, the base station may multiplex multiple successful RARs (or multiple fallback RARs), which are responses to multiple RA MSG-As in one MAC PDU, and the base station transmits one MAC PDU on the PDSCH. In order to distinguish the successful RAR from the fallback RAR, the MAC header, the MAC subheader, and / or (one or more) information elements included in the MAC message may be used.

[0453] For example, the base station can be based on Figure 12b One or more RAPID subheaders are shown, one or more successful RARs are multiplexed in one MAC PDU, and one MAC PDU is transmitted on the PDSCH. In addition, the base station can be based on Figure 12b One or more RAPID subheaders shown in the figure are multiplexed in one MAC PDU with one or more fallback RARs, and one MAC PDU is transmitted on the PDSCH. The terminal can receive a RAPID subheader from the base station, and when the index of the RA preamble indicated by the RAPID subheader is the same as the index of the RA preamble transmitted by the terminal, the terminal can receive a successful RAR or a fallback RAR mapped to the corresponding RAPID subheader. The BI can be transmitted together with the successful RAR or the fallback RAR. When the random access process fails, the BI may be useful. Therefore, the BI can be transmitted together with the fallback RAR. Alternatively, the BI can be transmitted independently of each of the successful RAR and the fallback RAR.

[0454] When the configuration of the MSG-B RA-RNTI for successful RAR is different from that of the MSG-B RA-RNTI for fallback RAR, the terminal can identify the RA MSG-B by using the MSG-B RA-RNTI for successful RAR. When the RA MSG-B is not identified based on the MSG-B RA-RNTI for successful RAR, the terminal can identify the RA MSG-B by using the MSG-B RA-RNTI for fallback RAR. When the RA MSG-B is not identified based on the MSG-B RA-RNTI for fallback RAR, the terminal can perform a two-step random access procedure or a four-step random access procedure according to preconfigured conditions after performing a backoff procedure based on the BI.

[0455] Fig.15 is a timing diagram illustrating a third exemplary embodiment of a random access procedure in a communication system.

[0456] Reference Fig.15 The communication system may include a base station, a first terminal, and a second terminal. The first terminal may be a terminal that performs a four-step random access procedure. The second terminal may be a terminal that performs a two-step random access procedure.

[0457] The first terminal may transmit RA MSG1 to the base station on PRACH. The base station may receive RA MSG1 from the first terminal, and may transmit RA MSG2 to the first terminal in response to RA MSG1. The first terminal may receive RA MSG2 from the base station based on a result of performing a monitoring operation on a downlink channel (e.g., PDCCH) within the RAR window. The RAR window may start from the transmission end time point of RAMSG1. Alternatively, the RAR window may start from the first symbol of the earliest CORESET (e.g., the CORESET where the PDCCH is located) after the transmission of RA MSG1. The RAR offset may indicate the difference between the transmission end time point of RA MSG1 (e.g., the last symbol of PRACH) and the first symbol of CORESET.

[0458] The first terminal may transmit RA MSG3 to the base station by using the resources indicated by the scheduling information (e.g., UL grant) included in RA MSG2. The base station may receive RA MSG3 from the first terminal and may transmit RA MSG4 to the first terminal. The first terminal may receive RA MSG4 from the base station. When RA MSG4 is successfully received at the first terminal, the four-step random access procedure may be terminated.

[0459] In the two-step random access process, the second terminal may transmit an RA MSG-A to the base station. The RA MSG-A may include an RA preamble and an RA payload. The RA preamble may be transmitted on the PRACH, and the RA payload may be transmitted on the PUSCH. The transmission interval D between the RA preamble and the RA payload may vary according to the resources configured for the two-step random access process (e.g., the mapping relationship of the resources). The base station may transmit resource configuration information (e.g., information about the mapping relationship of the resources) for the two-step random access process to the terminal (e.g., the second terminal) through system information and / or control messages.

[0460] The base station may receive a RA MSG-A (e.g., RA preamble, RA payload) from the second terminal. When both the RA preamble and the RA payload are successfully received, the base station may transmit a RA MSG-B (e.g., successful RAR) to the second terminal in response to the RA MSG-A. When only the RA preamble is received, the base station may transmit a fallback RAR to the second terminal in response to the RA MSG-A. The terminal may perform a PDCCH monitoring operation within the RAR window to receive the RA MSG-B. The RAR window may start from the transmission end time point of the RA MSG-A (e.g., RA payload). Alternatively, the RAR window may start from the first symbol of the earliest CORESET (e.g., the CORESET where the PDCCH is located) after the transmission of the RA MSG-A (e.g., RA payload). The RAR offset may indicate the difference between the transmission end time point of the RA MSG-A (e.g., RA payload) (e.g., the last symbol of the PDSCH) and the first symbol of the CORESET.

[0461] The second terminal may receive RA MSG-B (e.g., successful RAR, fallback RAR) from the base station within the RAR window. When a successful RAR is received within the RAR window, the two-step random access procedure may be terminated. When a fallback RAR is received within the RAR window, the second terminal may transmit the RA payload of RA MSG-A to the base station by using the resources indicated by the scheduling information (e.g., UL grant) included in the fallback RAR. That is, when the fallback RAR is received from the base station, the second terminal may determine that the base station has received the RA preamble of RA MSG-A, but has not received the RA payload of RA MSG-A. The base station may receive the RA payload of RA MSG-A from the second terminal, and may transmit RA MSG4 or the same information as RA MSG4 (e.g., information of the identifier of the second terminal for contention resolution) to the second terminal in response to the RA payload of RA MSG-A. When RA MSG4 is successfully received at the second terminal, the two-step random access procedure (e.g., fallback random access procedure) may be terminated.

[0462] According to the RAR offset and / or the transmission interval D, the RAR window of the four-step random access procedure (hereinafter referred to as the "four-step RAR window") may overlap with the RAR window of the two-step random access procedure (hereinafter referred to as the "two-step RAR window"). Alternatively, according to the RAR offset and / or the transmission interval D, the four-step RAR window may not overlap with the two-step RAR window. When the four-step RAR window overlaps with the two-step RAR window, a method is required for identifying whether the message 2 (e.g., RAR) received in the overlapping interval between the four-step RAR window and the two-step RAR window is RA MSG2 or RA MSG-B (e.g., successful RAR, fallback RAR). When the above-mentioned PRACH configuration method #2 is used, a method for identifying whether the message 2 received in the overlapping interval between the four-step RAR window and the two-step RAR window is RA MSG2 or RA MSG-B is also required. RA MSG2, successful RAR, fallback RAR, and BI (e.g., RAR including BI) can be distinguished according to the above-mentioned cases #3 to #5.

[0463] When the four-step RAR window does not overlap with the two-step RAR window, the transmission resources of RA MSG2 may be different from the transmission resources of RAMSG-B in the time domain. Since the period during which the first terminal (e.g., the terminal that initiated the four-step random access procedure) performs the PDCCH monitoring operation within the RAR window is different from the period during which the second terminal (e.g., the terminal that initiated the two-step random access procedure) performs the PDCCH monitoring operation within the RAR window, a different scheduling identifier may not be used for each of the first terminal and the second terminal. In addition, the MAC message may not be used to distinguish between the four-step random access procedure and the two-step random access procedure.

[0464] Even when PRACH configuration method #2 is used, the PRACH of the two-step random access process may not be configured to be different from the PRACH of the four-step random access process. By using system information and / or a control message (e.g., a dedicated control message), the base station may transmit to the terminal information indicating whether the four-step RAR window and the two-step RAR window overlap with each other, and configuration information of the PRACH and RO according to the overlap between the four-step RAR window and the two-step RAR window. When information indicating whether the four-step RAR window and the two-step RAR window overlap with each other is not received from the base station, the terminal (e.g., the first terminal and the second terminal) can determine whether the two-step RAR window overlaps with the four-step RAR window by using the RAR offset, the transmission interval D, the configuration information of the four-step RAR window, and / or the configuration information of the two-step RAR window.

[0465] By using system information and / or a control message (e.g., a dedicated control message), the base station may transmit to the terminal parameter(s) for a two-step random access procedure, information indicating whether the parameter(s) are applied in the two-step random access procedure, parameter(s) for a four-step random access procedure, and information indicating whether the parameter(s) are applied to the four-step random access procedure.

[0466] Fig.16a is a conceptual diagram showing a third exemplary embodiment of a MAC subheader in a random access procedure, Fig.16b is a conceptual diagram showing a fourth exemplary embodiment of a MAC subheader in a random access procedure, Fig.16c is a conceptual diagram showing an eleventh exemplary embodiment of a RA MSG-B in a random access procedure, Fig.16d is a conceptual diagram showing a twelfth exemplary embodiment of a RAMSG-B in a random access procedure, Fig.16e is a conceptual diagram illustrating a thirteenth exemplary embodiment of a RA MSG-B of a random access procedure. Fig.16f is a conceptual diagram showing a fourteenth exemplary embodiment of a RA MSG-B in a random access procedure, Figure 16g is a conceptual diagram illustrating a fifteenth exemplary embodiment of a RA MSG-B in a random access procedure.

[0467] Fig.16a The MAC subheader shown in may be subheader #1 for a successful RAR, and Fig.16b The MAC subheader shown in may be subheader #2 for a successful RAR (eg, UE Contention Resolution ID (UE CRID) subheader). Fig.16a In the exemplary embodiment shown in FIG. 16B, the T field may be set to "0" and the S field may be set to "1". The S field set to "0" may indicate that the corresponding MAC subheader (e.g., a MAC subheader including the corresponding S field) includes a BI. The S field set to "1" may indicate that the corresponding MAC subheader is a subheader of a successful RAR. Fig.16a The subheader #1 of the successful RAR shown in the figure may further include a "Number of Successful RARs (NOSR)" field, and the NOSR field may indicate the number of successful RARs included in the MSG-B MAC PDU. Alternatively, the NOSR field may indicate whether there is a successful RAR in the MSG-B MAC PDU. In this case, the size of the NOSR field may be 1 bit. For example, a NOSR field set to "1" may indicate that the RA MSG-B includes a successful RAR. A NOSR field set to "0" may indicate that the RA MSG-B does not include a successful RAR.

[0468] Fig.16c The RA MSG-B shown may be a fallback RAR, while Fig.16d The RA MSG-B shown could be a successful RAR. Fig.16c In the exemplary embodiment shown in FIG. 16D, a T field set to "0" may indicate that the corresponding RA MSG-B (e.g., a MAC RAR including the corresponding T field) is a fallback RAR, and a T field set to "1" may indicate that the corresponding RA MSG-B is a successful RAR. The arrangement order of the fields included in the successful RAR may be configured in various ways. For example, within the successful RAR, the UE contention resolution ID may be located after the T field.

[0469] When the RAPID subheader indicates fallback to RAR, Fig.12e In the exemplary embodiments shown in Figures 16A, 16E, 16F, and 16G, a subheader for a successful RAR may be used. The RAPID subheader may correspond to a fallback RAR. The subheader for a successful RAR may indicate whether the MSG-B MAC PDU includes a successful RAR. Alternatively, the subheader for a successful RAR may indicate the number of successful RARs included in the MSG-B MAC PDU. Fig.12e The RA MSG-B shown may be a fallback RAR. Figure 16e to 1 RAMSG-B shown in 6G may be a successful RAR.

[0470] When the index of the RA preamble indicated by the RAPID subheader is the same as the index of the RA preamble of the RA MSG-A transmitted from the terminal, the terminal can obtain the fallback RAR corresponding to the RAPID subheader from the base station. When there is no RAPID subheader indicating the same RA preamble as the RA preamble of the RA MSG-A transmitted from the terminal, the terminal can identify the (one or more) information elements contained in the subheader for the successful RAR. When it is determined that there is a successful RAR, the terminal can obtain the successful RAR from the base station and compare the UE contention resolution ID contained in the successful RAR with the UE contention resolution ID contained in the RA MSG-A transmitted from the terminal. The operation of comparing the UE contention resolution ID can be performed until a successful RAR (e.g., the last successful RAR) with the E field set to "0" is obtained. When the UE contention resolution ID contained in the successful RAR is the same as the UE contention resolution ID contained in the RA MSG-A transmitted from the terminal, the terminal can determine that the two-step random access process is completed.

[0471] Alternatively, Fig.16bThe subheader #2 for successful RAR shown may indicate whether the RA MSG-B includes a successful RAR. The subheader #2 for successful RAR may include an S field set to "1", a UE contention resolution ID, etc. When both the T field and the S field are set to "0" in the subheader #2 for successful RAR, the terminal may determine that the corresponding MAC subheader (e.g., subheader #2 for successful RAR) includes a BI.

[0472] When the T field is set to "0" and the S field is set to "1" in the subheader #2 for successful RAR, the terminal can determine that the corresponding MAC subheader (e.g., subheader #2 for successful RAR) includes the UE contention resolution ID. When the UE contention resolution ID included in the subheader #2 for successful RAR is the same as the UE contention resolution ID included in the RA MSG-A transmitted from the terminal, the terminal can obtain the successful RAR associated with the subheader #2 for successful RAR. In this case, Figure 16e to 1 The successful RAR shown in 6G may not include the UE contention resolution ID. Furthermore, the successful RAR may not include the E field.

[0473] Fig.17a is a conceptual diagram showing a fifth exemplary embodiment of a MAC subheader in a random access procedure, Fig.17b is a conceptual diagram showing a sixth exemplary embodiment of a MAC subheader in a random access procedure, Fig.17c is a seventh exemplary embodiment showing a MAC subheader in a random access procedure, Fig.17d is a conceptual diagram showing an eighth exemplary embodiment of a MAC subheader in a random access procedure, Fig.17e is a conceptual diagram showing a ninth exemplary embodiment of a MAC subheader in a random access procedure, Fig.17f is a conceptual diagram showing a sixteenth exemplary embodiment of a RA MSG-B in a random access procedure, Figure 17g is a conceptual diagram illustrating a seventeenth exemplary embodiment of a RA MSG-B in a random access procedure.

[0474] Figure 17a to 1 The MAC subheader shown in FIG. 7E may be a MAC subheader for RA MSG-B. The MAC subheader may include a T field, and the size of the T field may be 2 bits. Fig.17a In the exemplary embodiment shown, a T field set to "00" may indicate that the corresponding MAC subheader includes a BI. Fig.17b In the exemplary embodiment shown, a T field set to "01" may indicate that the corresponding MAC subheader indicates a fallback RAR. Fig.17cIn the exemplary embodiment shown, a T field set to "10" may indicate that the corresponding MAC subheader indicates a successful RAR.

[0475] exist Fig.17d In the exemplary embodiment shown, the T field set to "11" may indicate that the corresponding MAC subheader is the last MAC subheader among multiple MAC subheaders. Fig.17d In the MAC subheader shown, all bits after the T field may be set to "0" or "1". The size of the MAC subheader indicating that it is the last MAC subheader among multiple MAC subheaders may be one octet, and all bits constituting the one octet may be set to the same value (e.g., "0" or "1"). When a MAC subheader that does not indicate a successful RAR and / or a fallback RAR (e.g., Fig.17a ), can be transmitted after the corresponding MAC subheader Fig.17d The MAC subheader shown in .

[0476] (One or more) padding bits or (one or more) padding bytes may be added to the MAC PDU including the RA MSG-B. In this case, Fig.17d The reserved bit(s) (R) of the MAC subheader shown may indicate the number of padding bits or padding bytes contained in the MSG-B MAC PDU. When a MAC subheader including a T field set to "11" is detected, or when a MAC subheader including an octet in which each bit is set to the same value (e.g., "0" or "1") is detected, the terminal may determine that the MAC subheader for the RA MSG-B is terminated. In this case, the terminal may stop the search operation (e.g., identification operation) of the MAC subheader, and perform a reception operation of the RA MSG-B (e.g., BI, successful RAR, fallback RAR) according to the search result (e.g., identification result) of the MAC subheader.

[0477] When the RAPID included in the MAC subheader is the same as the index of the RA preamble of the RA MSG-A transmitted from the terminal, the terminal can perform a reception operation of a successful RAR or a fallback RAR. Fig.17e ), RAPID and UE contention resolution ID, and the UE contention resolution ID included in the MAC subheader is the same as the UE contention resolution ID included in the RA MSG-A transmitted from the terminal, the terminal can perform a successful RAR reception operation. Here, the fallback RAR can be Fig.12e The fallback RAR shown.

[0478] When received Fig.17c When the MAC subheader is shown, a successful RAR can be Figure 16e to Figure 16g The RA MSG-B shown in FIG. 1 is composed of the fields except the E field. Fig.17e When the MAC subheader is shown, a successful RAR can be Fig.17f and RA MSG-B shown in 17G.

[0479] When a radio bearer (e.g., signaling radio bearer (SRB) or data radio bearer (DRB)) packet needs to be transmitted in a two-step random access procedure, the MAC message for transmitting the radio bearer packet may include a success RAR and another MAC sub-PDU (or MAC PDU). The radio bearer packet may be included in another MAC sub-PDU or another MAC PDU. The above-mentioned MAC subheader constituting the RA MSG-B or the reserved bit(s) R included in the MAC RAR may indicate whether there is a MAC sub-PDU or MAC PDU including the radio bearer packet.

[0480] The MAC control information for the radio bearer packet may include at least one of the following: an indicator indicating whether there is a MAC subPDU or MAC PDU for transmitting the radio bearer packet (for example, whether it is transmitted), a time offset between the reception time point of the RAMSG-B (for example, the reception start time point, the reception end time point) and the reception time point of the MAC subPDU or MAC PDU for transmitting the radio bearer packet (for example, the reception start time point, the reception end time point), the LCID of the radio bearer, the beam configuration information (or TCI status, active TCI index information) of the MAC subPDU or MAC PDU for transmitting the radio bearer packet, and information about the BWP where the MAC subPDU or MAC PDU for transmitting the radio bearer packet is located (for example, BWP configuration parameters, BWP index or BWP activation indication information).

[0481] The arrangement order of the fields included in the above RA MSG-B may vary. The RA MSG-B may include one or more of the above fields. Each of the MAC subheader, the MAC sub-PDU (or MAC PDU) including the fallback RAR, and the MAC sub-PDU (or MAC PDU) including the successful RAR may be aligned in bytes. When each of the MAC subheader, the MAC sub-PDU (or MAC PDU) including the fallback RAR, and the MAC sub-PDU (or MAC PDU) including the successful RAR is not aligned in bytes, (one or more) reserved bits may be omitted. When the successful RAR is located after the fallback RAR, a specific bit pattern (e.g., 1 octet of each bit is set to the same value) may be inserted after the fallback RAR to identify the boundary between the fallback RAR and the successful RAR. In order to indicate that a valid RA MSG-B or MAC RAR has ended, a specific bit pattern (e.g., 1 octet of each bit is set to the same value) may be inserted after the end of the fallback RAR and / or the successful RAR.

[0482] Fig.18 is a sequence diagram illustrating a third exemplary embodiment of a random access procedure in a communication system.

[0483] Reference Fig.18 , the communication system may include a base station and a terminal. The base station may be Figure 1 The base stations 110-1, 110-2, 110-3, 120-1 or 120-2 are shown, and the terminal may be Figure 1 The base station and the terminal may be configured to communicate with the terminal 130-1, 130-2, 130-3, 130-4, 130-5 or 130-6 shown in FIG. Figure 2 The communication nodes 200 shown are the same or similar.

[0484] The base station may transmit configuration information for a four-step random access procedure (hereinafter referred to as "four-step configuration information") to the terminal (S1801). In addition, the base station may transmit configuration information for a two-step random access procedure (hereinafter referred to as "two-step configuration information") to the terminal (S1802). The four-step configuration information and the two-step configuration information may be transmitted through different messages. Alternatively, the four-step configuration information and the two-step configuration information may be transmitted through one message. Here, the message may be an RRC message or a MAC message.

[0485] Each of the four-step configuration information and the two-step configuration information may include configuration information of the PRACH opportunity, information of the RA preamble sequence, a channel quality threshold (e.g., an RSRP threshold), etc. When the CFRA scheme is used, each of the four-step configuration information and the two-step configuration information may include configuration information of the PRACH opportunity specifically allocated to the terminal, an RA preamble sequence, etc. The configuration information of the PRACH opportunity may include periodic information of the PRACH opportunity, time domain resource information, and frequency domain resource information. The two-step configuration information for the CFRA scheme may also include configuration information of the RA payload for the RA MSG-A. Here, the configuration information of the RA payload may be determined based on the mapping relationship (e.g., a one-to-one mapping relationship) between the transmission resources of the RA preamble and the transmission resources of the RA preamble. The two-step configuration information for the CFRA scheme may include one or more of the information elements #1 to #6 described below. The four-step configuration information or the two-step configuration information for the CFRA scheme may be transmitted to the terminal using a dedicated control message.

[0486] The PRACH timing for the four-step random access procedure may be the same as the PRACH timing for the two-step random access procedure. Alternatively, the PRACH timing for the four-step random access procedure may be different from the PRACH timing for the two-step random access procedure. In this case, the base station may determine that the message 1 received in the PRACH timing of the four-step random access procedure is RA MSG1, and the message 1 received in the PRACH timing of the two-step random access procedure is RA MSG-A.

[0487] The sequence (or index) group to which the RA preamble sequence (or index) used in the four-step random access process belongs (hereinafter referred to as the "four-step sequence group") may be configured to be different from the sequence group to which the RA preamble sequence used in the two-step random access process belongs (hereinafter referred to as the "two-step sequence group"). The four-step sequence group may be referred to as a four-step sequence set, and the two-step sequence group may be referred to as a two-step sequence set. In the following exemplary embodiments, the RA preamble sequence may mean an RA preamble code index, the four-step sequence group may mean a four-step index group or a four-step index set, and the two-step sequence group may mean a two-step index group or a two-step index set.

[0488] The (one or more) RA preamble sequences belonging to the four-step sequence group may be different from the (one or more) RA preamble sequences belonging to the two-step sequence group. In this case, when the PRACH opportunity of the four-step random access procedure is the same as the PRACH opportunity of the two-step random access procedure, the base station may determine that the message 1 received in the PRACH opportunity is RA MSG1 or RA MSG-A based on the RA preamble sequence. The four-step configuration information may include information of the four-step sequence group, and the two-step configuration information may include information of the two-step sequence group.

[0489] A channel quality threshold (e.g., an RSRP threshold) may be used to determine the type of random access procedure performed by a terminal. When the channel quality between the terminal and the base station is equal to or greater than the RSRP threshold, the terminal may perform a two-step random access procedure. When the channel quality between the terminal and the base station is less than the RSRP threshold, the terminal may perform a four-step random access procedure. The channel quality threshold may be included in system information, rather than in four-step configuration information and two-step configuration information. That is, the base station may transmit system information including an RSRP threshold (e.g., a channel quality threshold) for determining the type of random access procedure to the terminal.

[0490] Furthermore, the two-step configuration information may also include one or more of the following information elements.

[0491] - Information element #1: Time domain offset between resources transmitting the RA preamble included in the RA MSG-A (e.g., PRACH) and resources transmitting the RA payload included in the RA-MSG-A (e.g., PUSCH)

[0492] - Information element #2: Frequency domain offset between the resource transmitting the RA preamble contained in the RA MSG-A (e.g., PRACH) and the resource transmitting the RA payload contained in the RA-MSG-A (e.g., PUSCH)

[0493] - Information element #3: Information on a mapping relationship between resources (eg, PRACH) transmitting an RA preamble included in an RA MSG-A and resources (eg, PUSCH) transmitting an RA payload included in an RA-MSG-A

[0494] - Information element #4: Information indicating the start timing of resources for transmitting the RA payload included in the RA-MSG-A (eg, the start symbol index of the PUSCH)

[0495] - Information element #5: Information indicating the length of resources transmitting the RA payload included in the RA-MSG-A (e.g., duration of a PUSCH, an interval between PUSCHs, the number of PUSCHs, or the number of symbols constituting a PUSCH (or a start symbol, an end symbol, and / or the length of a PUSCH))

[0496] - Information element #6: Information indicating the MCS level used for transmitting the RA payload included in the RA MSG-A The time domain offset included in the two-step configuration information may be the interval between the end time point of the PRACH and the start time point of the PUSCH, or the interval between the start time point of the PRACH and the start time point of the PUSCH. The frequency domain offset included in the two-step configuration information may be the interval between the start RB of the PRACH and the start RB of the PUSCH, the interval between the end RB of the PRACH and the start RB of the PUSCH, or the interval between the reference RB (e.g., the start RB of the system bandwidth or bandwidth part (BWP)) and the start RB of the PUSCH. Here, the RB may be a PRB or a CRB. The start RB may be an RB having the lowest frequency resource among the RBs occupied by the corresponding channel (e.g., frequency band), and the end RB may be an RB having the highest frequency resource among the RBs occupied by the corresponding channel.

[0497] The two-step configuration information may include information indicating an MCS level. The RA payload included in the RA MSG-A may be transmitted based on the MCS level indicated by the two-step configuration information. Alternatively, information indicating the MCS level for the RA payload included in the RA MSG-A may be included in the system information instead of the two-step configuration information. That is, the base station may transmit the system information including information indicating the MCS level to the terminal. The terminal may receive one or more of the system information, the four-step configuration information, and the two-step configuration information from the base station. When the four-step configuration information is received and the two-step configuration information is not received, the terminal may perform a four-step random access process based on the four-step configuration information. When the two-step configuration information is received and the four-step configuration information is not received, the terminal may perform a two-step random access process based on the two-step configuration information. When the four-step configuration information and the two-step configuration information are received, the type of random access process performed by the terminal may be determined based on the channel quality between the terminal and the base station (S1803). For example, the terminal may receive a reference signal and / or an SS / PBCH block from the base station and measure the quality of the received signal (e.g., RSRP). When the RSRP measured by the terminal is equal to or greater than the RSRP threshold configured by the base station, the terminal can perform a two-step random access procedure based on the two-step configuration information. When the RSRP measured by the terminal is less than the RSRP threshold configured by the base station, the terminal can perform a four-step random access procedure based on the four-step configuration information.

[0498] When it is determined that the two-step random access procedure is performed, the terminal may generate an RA MSG-A including an RA preamble and an RA payload, and transmit the RA MSG-A to the base station (S1804). The terminal may select an RA preamble sequence in the two-step sequence group, and may transmit the selected RA preamble sequence (i.e., RA preamble). The RA preamble may be transmitted in the PRACH opportunity indicated by the two-step configuration information.

[0499] In addition, when switching to the two-step random access procedure according to the CBRA scheme when CFRA is configured, the terminal may select a set of RA preamble sequences according to the size of the RA payload of RA MSG-A or RA MSG3 of the four-step random access procedure, select an RA preamble code from the determined set, and transmit the selected RA preamble code. When switching from the two-step random access procedure to the four-step random access procedure, the terminal may select a set of RA preamble sequences and RA preamble codes according to the same method, and transmit the selected RA preamble code.

[0500] The RA payload may be transmitted by a PUSCH identified by one or more of a time domain offset, a frequency domain offset, a PUSCH start symbol index, a PUSCH duration, and a mapping relationship information included in the two-step configuration information. The RA payload may be transmitted based on the MCS level configured by the base station. The RA payload may include one or more of a terminal identifier, data, and control information. Here, the control information may include one or more of a BSR, measurement result information (e.g., radio channel quality information), a BFR request information, an RLF report information, an RRC connection establishment request information, an RRC connection reconstruction request information, a recovery request information, the location information of the terminal (e.g., a location estimated by a GPS signal, a positioning measurement method, or a built-in sensor, etc.), and a transmission request information of the system information. The RA payload may include the information included in the RA MSG3 in the four-step random access process. The terminal may calculate the RA-RNTI based on the radio resource information (e.g., PRACH opportunity) of the PRACH where the RA preamble is transmitted. The RA-RNTI used to receive the RA MSG-B in the two-step random access procedure may be referred to as “MSG-B RA-RNTI” or “MSGB-RNTI.” For example, the MSGB-RNTI may be calculated based on Equation 1 below.

[0501] [Equation 1]

[0502]

[0503] sid may be the index of the first symbol of a PRACH opportunity. tid may be the index of the first slot of a PRACH opportunity in a system frame (eg, a radio frame). fid may be the index of a PRACH opportunity in the frequency domain. The UL carrier used for transmission of the RA preamble can be indicated. When the normal uplink (NUL) carrier is used, May be 0. When using the Supplemental Uplink (SUL) carrier, It can be 1. The offset can be signaled from the base station to the terminal. For example, the base station can transmit a DCI, an RRC message, or a MAC message including the offset to the terminal. The offset for the generation of the MSGB-RNTI can be included in the system information or the two-step configuration information. The time domain offset or the frequency domain offset included in the two-step configuration information can be used as the offset for generating the MSGB-RNTI. Alternatively, the offset can be predefined in the technical specification.

[0504] The RA-RNTI for receiving the RA MSG 2 in the four-step random access procedure may be calculated based on the following equation 2. That is, the offset of equation 1 may not be applied to equation 2. Therefore, even when the radio resources of the PRACH opportunity at which the RA preamble is transmitted in the two-step random access procedure are the same as the radio resources of the PRACH opportunity at which the RA preamble is transmitted in the four-step random access, the MSG B-RNTI may be configured to be different from the RA-RNTI of the four-step random access procedure.

[0505] [Equation 2]

[0506]

[0507] Meanwhile, the base station may receive RA MSG-A or RA MSG1 by performing a monitoring operation in (one or more) PRACH opportunities indicated by the two-step configuration information and / or the four-step configuration information. When message 1 is received in the PRACH opportunity indicated by the two-step configuration information, or when the RA preamble sequence of message 1 belongs to the two-step sequence group, the base station may determine that the corresponding message 1 is RA MSG-A of the two-step random access procedure. On the other hand, when message 1 is received in the PRACH opportunity indicated by the four-step configuration information, or when the RA preamble sequence of message 1 belongs to the four-step sequence group, the base station may determine that the corresponding message 1 is RA MSG1 of the four-step random access procedure.

[0508] Upon receiving the RA MSG-A, the base station may identify information included in the RA payload of the RA MSG-A. In addition, the base station may calculate the MSGB-RNTI based on Equation 1. Upon receiving the RA MSG1, the base station may calculate the RA-RNTI based on Equation 2. Here, it is assumed that the base station receives the RA MSG-A from the terminal.

[0509] The base station may generate a RA MSG-B in response to the RA MSG-A (S1805). The RA MSG-B may be a MAC PDU. The RA MSG-B may include one or more MAC sub-PDUs. Each of the one or more MAC sub-PDUs may be generated according to one of the following configuration schemes. The MAC sub-PDU may be configured according to the exemplary embodiments shown in Figures 12, 14, 16, and / or 17 above.

[0510] -Configuration #1: MAC subheader including BI,

[0511] -Configuration #2: MAC subheader and fallback RAR

[0512] -Configuration #3: MAC subheader and successful RAR

[0513] - Configuration #4: MAC subheader and MAC SDU (e.g., data or control information)

[0514] -Configuration #5: MAC subheader and padding

[0515] The MAC subheader may include a first indicator indicating the type of a MAC subPDU including the corresponding MAC subheader (e.g., the type of information included in the MAC subPDU). The first indicator may indicate a first type MAC subPDU including a BI (e.g., a MAC subPDU according to configuration scheme #1), a second type MAC subPDU including a fallback RAR (e.g., a MAC subPDU according to configuration scheme #2), or a third type MAC subPDU including a successful RAR (e.g., a MAC subPDU according to configuration scheme #3). The size of the first indicator may be 2 bits, and the first bit of the 2 bits may indicate the first type MAC subPDU or the second type MAC subPDU, and the second bit of the 2 bits may indicate the third type MAC subPDU.

[0516] Alternatively, the first indicator may indicate a first type MAC sub-PDU including a BI (e.g., a MAC sub-PDU according to configuration scheme #1), a second type MAC sub-PDU including a fallback RAR (e.g., a MAC sub-PDU according to configuration scheme #2), a third type MAC sub-PDU including a successful RAR (e.g., a MAC sub-PDU according to configuration scheme #3), or a fourth type MAC sub-PDU including a MAC SDU (e.g., a MAC PDU according to configuration scheme #4). The size of the first indicator may be 2 bits, and the first bit of the 2 bits may indicate the first type MAC sub-PDU or the second type MAC sub-PDU, and the second bit of the 2 bits may indicate the third type MAC sub-PDU or the fourth type MAC sub-PDU.

[0517] In addition, the MAC subheader may include a second indicator indicating whether a fourth type of MAC sub-PDU exists. The size of the second indicator may be 1 bit. A second indicator set to "0" may indicate that a fourth type of MAC sub-PDU does not exist. A second indicator set to "1" may indicate that a fourth type of MAC sub-PDU exists.

[0518] In addition, the MAC subheader may include a third indicator indicating whether there is another MAC sub-PDU after the MAC sub-PDU including the corresponding MAC subheader. The size of the third indicator may be 1 bit. The third indicator set to "0" may indicate that there is no another MAC sub-PDU after the corresponding MAC sub-PDU. The third indicator set to "1" may indicate that there is another MAC sub-PDU after the corresponding MAC sub-PDU.

[0519] In addition, the first type MAC sub-PDU may include information indicating switching to a four-step random access procedure. The information indicating switching from a two-step random access procedure to a four-step random access procedure may be configured as a separate bit, and the separate bit may be included in the first type MAC sub-PDU together with the BI. Alternatively, the information indicating switching from a two-step random access procedure to a four-step random access procedure may be configured as a specific pattern of a bit string constituting the BI.

[0520] The base station may generate DCI including resource allocation information of the RA MSG-B, perform a scrambling operation (eg, CRC of the DCI) on the DCI by using the MSGB-RNTI, and transmit the DCI (eg, scrambled DCI) to the terminal (S1806).

[0521] The DCI may be transmitted within a RAR window. The RAR window may start at the start time point of the PRACH, the end time point of the PRACH, the start time point of the PUSCH, the end time point of the PUSCH, the start time point of the RA preamble, the end time point of the RA preamble, the start time point of the RA payload, or the end time point of the RA payload. Here, the PRACH may be a radio resource where the RA preamble for transmitting the RAMSG-A is located, and the PUSCH may be a radio resource where the RA payload for transmitting the RA MSG-A is located. The base station may notify the terminal of the duration of the RAR window (or the end time point of the RA window, the timer of the RAR window). Information indicating the duration of the RAR window (or the end time point of the RA window, the timer of the RAR window) may be included in the system information and / or the two-step configuration information.

[0522] The terminal can perform a PDCCH monitoring operation by using the MSGB-RNTI. The PDCCH monitoring operation can be performed within the RAR window. For example, the terminal can perform a descrambling operation on the DCI received from the base station by using the MSGB-RNTI. When the DCI is successfully received from the base station, the terminal can obtain the resource allocation information of the RA MSG-B included in the DCI. The terminal can perform a monitoring operation for receiving the RA MSG-B in the radio resources indicated by the resource allocation information of the RAMSG-B.

[0523] The base station may transmit the RA MSG-B to the terminal (S1807) by using the DCI of the above step S1806. The RA MSG-B may be transmitted in the radio resources indicated by the resource allocation information included in the DCI scrambled by the MSGB-RNTI. The terminal may receive the RA MSG-B from the base station. The terminal may identify the type of the corresponding MAC sub-PDU by checking the first indicator of the MAC sub-header included in the MAC sub-PDU identified by the RA MSG-B. For example, the terminal may identify whether the corresponding MAC sub-PDU is a first type MAC sub-PDU, a second type MAC sub-PDU, or a third type MAC sub-PDU based on the first indicator included in the MAC sub-header. In addition, the terminal may identify whether a fourth type MAC sub-PDU exists by checking the second indicator included in the MAC sub-header.

[0524] In addition, the terminal can identify whether there is another MAC sub-PDU after the corresponding MAC sub-PDU by checking the third indicator of the MAC sub-header. When there is another MAC sub-PDU, the terminal can identify the first indicator, the second indicator and / or the third indicator included in the other MAC sub-PDU, and perform an operation according to the result of the identification.

[0525] When the RA MSG-B received from the base station includes a MAC subheader containing a BI, the terminal may perform a two-step random access procedure after a backoff operation according to the received BI. Alternatively, the terminal may perform a four-step random access procedure again without a backoff operation. In addition, when information indicating switching to a four-step random access procedure is received from the base station, the terminal may perform a four-step random access procedure again without a backoff operation.

[0526] When the RA MSG-B received from the base station includes a MAC subheader and a fallback RAR, the terminal may transmit RA MSG3 according to a four-step random access procedure to the base station. That is, the two-step random access procedure may be switched to a four-step random access procedure. RA MSG3 may be transmitted via the radio resources indicated by the UL grant included in the fallback RAR. RA MSG-B including a MAC subheader and a fallback RAR may be generated based on the format of RA MSG2 of the four-step random access procedure. For example, RA MSG-B may include information contained in RA MSG2. The base station may receive RA MSG3 from the terminal and may transmit RA MSG4 to the terminal. The terminal may receive RA MSG4 from the base station. In this case, the random access procedure may be terminated. That is, contention between terminals may be resolved.

[0527] When the RA MSG-B received from the base station includes a MAC subheader and a successful RAR, the terminal can determine that the two-step random access procedure has been terminated. When the RA MSG-B including the MAC subheader and the successful RAR is received within the RAR window, the terminal can determine that the two-step random access procedure has been terminated. That is, the contention between the terminals may be resolved.

[0528] When the two-step random access process of the CFRA scheme is performed in the process according to steps S1804 to S1807, the base station may receive only the RA preamble of the RA MSG-A according to the CFRA scheme from the terminal, but not the RA payload of the RA MSG-A. In this case, the base station can identify the corresponding terminal by the index information or radio resource of the RA preamble of the RA MSG-A according to the CFRA scheme received from the terminal. Therefore, the base station can transmit the DCI including the scheduling information of the PDSCH where the RA MSG-B is transmitted to the terminal by using a scheduling identifier (e.g., C-RNTI) or MSGB-RNTI dedicated to the terminal. Therefore, the terminal can receive the DCI by performing a PDCCH monitoring operation using the MSGB-RNTI or the scheduling identifier assigned to itself. The terminal can obtain one or more of the scheduling information, downlink scheduling information, and uplink scheduling information of the PDSCH where the RA MSG-B is transmitted.

[0529] In addition, when the above two-step configuration information (e.g., information elements #1 to #6) does not include radio resource configuration information for RA payload, the terminal may transmit only the RA preamble in step S1804 of transmitting RA MSG-A. That is, when the two-step configuration information does not include association information (e.g., mapping relationship information) between the RA preamble and the RA payload included in RA MSG-A, the terminal may transmit only the RA preamble of RA MSG without transmitting the RA payload of RA MSG-A. In this case, when the terminal transmits only the RA preamble of RA MSG-A for the two-step random access procedure, the base station and the terminal may perform operations conforming to the four-step random access procedure.

[0530] That is, the base station can recognize that only the RA preamble is received from the terminal based on the two-step configuration information. Therefore, when the RA preamble is received from the terminal, the base station can transmit a random access response message to the terminal according to the above-mentioned two-step random access procedure or four-step random access procedure. The base station performing the two-step random access procedure can transmit the RA MSG-B composed of the fallback RAR to the terminal by using the MSG-B RNTI. The base station performing the four-step random access procedure can transmit a response message configured in the form of RA MSG2 to the terminal by using the RA-RNTI.

[0531] In addition, the terminal may monitor the DCI to receive a random access response message after transmitting only the RA preamble of MSG-A. In this case, the RAR window may start at the time point when the terminal transmits the PRACH (e.g., the start time point or the end time point of the PRACH transmission). In addition, the terminal may monitor the PDCCH by using both the RA-RNTI and the MSG-B RNTI. Through PDCCH monitoring, the terminal may receive a response message configured in the form of RA MSG2 by using the RA-RNTI. Alternatively, through PDCCH monitoring, the terminal may receive a RA MSG-B configured as a fallback RAR by using the MSG-B RNTI.

[0532] In the present disclosure, the radio channel quality may be a channel state indicator (CSI), a received signal strength indicator (RSSI), a reference signal received power (RSRP), a reference signal received quality (RSRQ), or a signal to interference and noise ratio (SINR). Regarding the operation of the timer defined or described in the present disclosure, although the operations such as starting, stopping, resetting, restarting or expiring of the defined timer are not described separately, they mean or include the operation of the corresponding timer or the counter for the corresponding timer.

[0533] In the present disclosure, a base station (or cell) may refer to a NodeB, an evolved NodeB, a base transceiver station (BTS), a radio base station, a radio transceiver, an access point, an access node, a roadside unit (RSU), a radio remote control head (RRH), a transmission point (TP), a transmission and reception point (TRP), or a gNB. In addition, a base station (or cell) may be a CU node or a DU node to which functional partitioning is applied.

[0534] In the present disclosure, a terminal may refer to a UE, a terminal, an access terminal, a mobile terminal, a station, a user station, a mobile station, a portable user station, a node, a device, an Internet of Things (IoT) device, or an installed apparatus (e.g., an installed module / device / terminal or an onboard device / terminal).

[0535] The exemplary embodiments of the present disclosure may be implemented as program instructions that can be executed by various computers and recorded on a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, or a combination thereof. The program instructions recorded on a computer-readable medium may be specially designed and configured for the present disclosure, or may be well-known and available to those skilled in the art of computer software.

[0536] Examples of computer-readable media may include hardware devices such as ROM, RAM, and flash memory, which are specifically configured to store and execute program instructions. Examples of program instructions include machine code, such as generated by a compiler, and high-level language codes that can be executed by a computer using an interpreter. The above exemplary hardware devices may be configured to operate as at least one software module to perform embodiments of the present disclosure, and vice versa.

[0537] Although the embodiments of the present disclosure and its advantages have been described in detail, it should be understood that various changes, substitutions, and alterations can be made herein without departing from the scope of the disclosure.

Claims

1. A method for operating a terminal in a communication system, the method comprising: receiving configuration information for a two-step random access procedure from a base station; transmitting a random access (RA) message-A (MSG-A) including an RA preamble and an RA payload to the base station based on the configuration information; determining a random access radio network temporary identifier (RA-RNTI) by using information of a radio resource on which the RA preamble is transmitted and a preconfigured offset; receiving downlink control information (DCI) including resource allocation information of the RA MSG-B from the base station by performing a physical downlink control channel (PDCCH) monitoring operation using the RA-RNTI; and The RA MSG-B is received from the base station through resources indicated by resource allocation information included in the DCI.

2. The operating method according to claim 1, wherein: The RA-RNTI used for the two-step random access procedure is configured to be different from the RA-RNTI used for the four-step random access procedure.

3. The operating method according to claim 1, wherein: The RA-RNTI is determined by applying the preconfigured offset to the RA-RNTI used for a four-step random access procedure.

4. The operating method according to claim 1, wherein: The preconfigured offset is received from the base station.

5. The operating method according to claim 1, wherein: The PDCCH monitoring operation is performed within a random access response (RAR) window.

6. The operating method according to claim 1, wherein: When the two-step random access procedure is performed in a contention-free random access (CFRA) scheme, the configuration information includes information of transmission resources exclusively allocated to the RA MSG-A of the terminal.

7. A method for operating a base station in a communication system, the method comprising: transmitting configuration information for a two-step random access procedure to a terminal; receiving a random access (RA) message-A (MSG-A) including an RA preamble and an RA payload from the terminal by performing a monitoring operation based on the configuration information; determining a random access radio network temporary identifier (RA-RNTI) by using information of the radio resource on which the RA preamble is received and a preconfigured offset; performing a scrambling operation on downlink control information (DCI) including resource allocation information of the RA MSG-B by using the RA-RNTI; transmitting the scrambled DCI to the terminal; and The RA MSG-B is transmitted to the terminal through the resources indicated by the resource allocation information included in the DCI.

8. The operating method according to claim 7, wherein: The RA-RNTI is determined by applying the preconfigured offset to the RA-RNTI used for a four-step random access procedure.

9. The operating method according to claim 7, further comprising transmitting the preconfigured offset to the terminal.

10. The operating method according to claim 7, wherein: The scrambled DCI is transmitted to the terminal within a random access response (RAR) window.

11. The operating method according to claim 7, wherein: When the two-step random access procedure is performed in a contention-free random access (CFRA) scheme, the configuration information includes information of transmission resources exclusively allocated to the RA MSG-A of the terminal.