Method and apparatus for performing random access configuration for subband full duplex in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. In a method by which a user equipment performs communication in a wireless communication system of the present disclosure, a resource for performing a random access procedure is received from a base station. In the method, a first random occasion type for performing the random access procedure is established. In the method, a preamble is transmitted on the basis of the first random occasion type. If reception of a RAR corresponding to the preamble is unsuccessful and a preset condition is satisfied, the first random occasion type is changed to a second random occasion type. On the basis of the change to the second random occasion type, the resource for performing the random access procedure is changed. The first random occasion type and the second random occasion type comprise an SBFD type or a non-SBFD type.

Description

Method and device for performing random access settings for subband full duplex in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and in particular to an operation procedure and apparatus for performing random access settings for sub-band full duplex operation.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes to expand network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) to incorporate Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality.

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas to guarantee coverage in the terahertz band of 6G mobile communication technology; metamaterial-based lenses and antennas; high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM); and Reconfigurable Intelligent Surface (RIS) technology to improve terahertz band signal coverage; as well as full-duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and Artificial Intelligence (AI) from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] The present disclosure provides a method and apparatus for selecting a Physical Random Access Channel (PRACH) Occasion as a method for performing random access settings for subband full duplex in a wireless communication system.

[0009] According to one embodiment of the present disclosure, a method for a terminal to perform communication in a wireless communication system may include: receiving resources for performing a random access procedure from a base station; setting a first random occasion type for performing a random access procedure; transmitting a preamble based on the first random occasion type; changing the first random occasion type to a second random occasion type when the reception of a random access response corresponding to the preamble is unsuccessful and a preset condition is satisfied; and changing resources for performing a random access procedure based on the change to the second random occasion type. The first random occasion type may include a subband full duplex (SBFD) type or a non-SBFD type, and the second random occasion type may include a non-SBFD type or an SBFD type.

[0010] According to one embodiment of the present disclosure, a terminal performing communication in a wireless communication system may include a memory storing a plurality of instructions and at least one processor that executes a plurality of instructions stored in the memory. The terminal may receive resources for performing a random access procedure from a base station by individually or collectively executing a plurality of instructions by at least one processor, set a first random occasion type for performing a random access procedure, transmit a preamble based on the first random occasion type, and if it fails to receive a random access response corresponding to the preamble and a preset condition is satisfied, change the first random occasion type to a second random occasion type and change resources for performing a random access procedure based on the change to the second random occasion type. The first random occasion type may include a subband full duplex (SBFD) type or a non-SBFD type, and the second random occasion type may include a non-SBFD type or an SBFD type.

[0011] FIG. 1 is a drawing illustrating the structure of a wireless communication system according to one embodiment of the present disclosure.

[0012] FIG. 2 is a diagram showing the wireless protocol structure of a wireless communication system according to one embodiment of the present disclosure.

[0013] FIG. 3 is a drawing for explaining the concept of a subband full duplex (hereinafter SBFD) of a base station or cell according to one embodiment of the present disclosure.

[0014] FIG. 4 is a diagram illustrating a method for providing random access settings in a subband full duplex (hereinafter SBFD) of a base station or cell according to one embodiment of the present disclosure.

[0015] FIG. 5 is a drawing illustrating an RO type selection method according to one embodiment of the present disclosure.

[0016] FIG. 6 is a drawing illustrating an RO type selection method according to one embodiment of the present disclosure.

[0017] FIG. 7 is a block diagram illustrating the structure of a terminal according to one embodiment of the present disclosure.

[0018] FIG. 8 is a block diagram illustrating the structure of an NR base station according to one embodiment of the present disclosure.

[0019] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0020] While various details have been described for the purpose of facilitating understanding in describing the embodiments, it will be understood that some aspects of the present disclosure may be practiced without including all such details. Furthermore, various modifications and alternatives are possible regarding the details presented herein, and all of these should be considered to be included within the scope of the present disclosure. Meanwhile, descriptions of technical content that are widely known in the art and may unnecessarily obscure the understanding of the present disclosure may be appropriately omitted, and such omitted descriptions should also be understood to be included within the scope of the present disclosure.

[0021] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual size. Identical or corresponding components in each drawing have been assigned the same or different reference numbers.

[0022] The advantages and features of the present disclosure, and the methods for achieving them, will become clear through the embodiments described below in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments presented below and may be implemented in various forms. Other features, aspects, and advantages disclosed in the present disclosure will become more clear through the following description of the present disclosure. The following embodiments are merely illustrative to aid in understanding the present disclosure and should not be construed as limiting the scope or spirit of the present disclosure in any case. Rather, the present disclosure includes all modifications, changes, and alternatives made within the spirit and scope of the present disclosure as defined by the appended claims and their equivalents. Identical or similar components throughout the disclosure are assigned identical or similar reference numerals. Furthermore, terms described below are defined with consideration of their function in the present disclosure and may be used differently depending on the user, operator, or convention. Accordingly, the definitions of terms should be interpreted based on the entire content of the present disclosure.

[0023] In the present disclosure, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams may be performed based on computer program instructions. Since these computer program instructions may be optionally loaded into at least one processor of a general-purpose computer, a computer for special purposes, or other programmable data processing equipment, the instructions performed through any one or any combination of at least one processor of the computer or other programmable data processing equipment create means for performing the functions described in the flow diagram block(s). Since these computer program instructions may also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the functions in a specific manner, the instructions stored in computer-available or computer-readable memory may also produce a manufactured item containing means of instruction for performing the functions described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0024] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specified logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks (or functions) described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to the corresponding function.

[0025] As used in the embodiments of the present disclosure, the term “part / module” refers to a software or hardware component such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), and the “part / module” performs certain roles. However, the term including “part / module” is not limited to software or hardware. The “part / module” may be configured to reside in an addressable storage medium or may be configured to run one or more processors. Accordingly, by example, the “part / module” includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and 'parts / modules' may be combined into a smaller number of components and 'parts / modules' or further separated into additional components and 'parts / modules'. In addition, the components and 'parts / modules' may be implemented to utilize one or more CPUs (central processing units) within the device or secure multimedia card. Furthermore, in the embodiments, the 'parts / modules' may include one or more processors.

[0026] The entirety of one or more computer programs may be stored in a single memory device, or one or more computer programs may be divided into different parts and stored across multiple memory devices.

[0027] Additionally, any / any function or operation described in this disclosure may be processed by a single processor or a combination of processors. The single processor or combination of processors may be a circuitry that performs processing, and may include an application processor (AP, e.g., a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural network processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near-field communication (NFC) chip, a connectivity chip, a sensor controller, a touch controller, a fingerprint sensor controller, a display driver integrated circuit (IC), an audio codec (CODEC) chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor, a microcontroller, a digital signal processor, an FPGA, an ASIC, a microprocessor unit (MPU), a system-on-chip (SoC), an IC, or similar circuitry. The single processor or combination of processors described above can control the overall operation of an electronic device by executing instructions, such as an operating system, that can be stored in memory. Additionally, the processor or combination of processors can execute other processes or programs residing in memory (e.g., processes related to the present disclosure).

[0028] Additionally, it should be noted that various embodiments in the claims and description of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0029] Such software may be stored on a non-transitory computer-readable storage medium. A non-transitory computer-readable storage medium stores one or more computer programs (software modules), said one or more computer programs include computer-executable instructions that operate an electronic device to perform a method according to the present disclosure when executed individually or collectively by one or more processors of an electronic device. Alternatively, said software may be a computer program (or product) that includes instructions that operate an electronic device to perform a method according to the present disclosure when executed individually or collectively by one or more processors of an electronic device.

[0030] The software may be stored in a transient or non-transient storage device, for example, in the form of read-only memory (ROM) (whether or not it is erasable or rewritable), or random access memory (RAM), memory chips, devices, or integrated circuits (ICs). Additionally, the software may be stored in the form of an optically or magnetically readable medium, for example, a compact disc (CD), a digital multifunction disc (DVD), a magnetic disc, or a magnetic tape. It should be understood that the storage device and the storage medium are examples of non-transient machine-readable storage media suitable for storing programs for implementing various embodiments of the present disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing an apparatus or method according to any one of the claims of the present disclosure, and a non-transient machine-readable storage medium storing such program.

[0031] In the following disclosure, determining the priority between A and B may be referred to in various ways, such as selecting the one with the higher priority according to a predetermined priority rule and performing the corresponding action, or omitting or dropping the action for the one with the lower priority.

[0032] Hereinafter, 'A or B' as described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0033] Additionally, 'at least one of A, B, and C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.

[0034] Additionally, 'at least one of A, B, or C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.

[0035] Additionally, 'A / B' as described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0036] Additionally, 'A, B' described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0037] Additionally, 'A and B' described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0038] Furthermore, the phrase "when conditions A and B are satisfied" as described in the present disclosure is not necessarily limited to cases where both conditions A and B are satisfied, but may be understood to include cases where either condition A or condition B is satisfied individually, cases where both conditions A and B are satisfied, or cases where one or more additional conditions are satisfied together.

[0039] Furthermore, throughout this disclosure, ordinal terms (and similar modifiers) such as 'first', 'second', 'third', etc. are used solely for the purpose of distinguishing various instances, occurrences, configurations, messages, stages, elements, or aspects of elements, operations, or information, as described below. Unless clearly required otherwise by the context, the use of such ordinal terms does not require that the elements, operations, or information distinguished by such terms be structurally different, numerically distinct, or substantially different. For example, 'first signal' and 'second signal' may represent instances of the same signal transmitted at different times, signals containing the same core information even with some variations, or signals having different content or characteristics depending on the specific context. Similarly, 'first value' and 'second value' may represent the same size measured or applied in different situations, or they may represent different sizes. Such interpretation must be determined based on the specific technical context, function, and relationship described in the relevant parts of the disclosure and claims.

[0040] Furthermore, although terms such as "first," "second," etc., as used in this disclosure are used for various elements such as information, objects, actions, and sequences, they are not intended to limit such elements to a specific order. These terms may be understood merely as distinguishing one element from another. For example, a first element may be referred to as a second element, and likewise, a second element may be referred to as a first element.

[0041] Additionally, the terms 'first' and 'second' described in this disclosure may be understood to refer to identical or different elements. For example, if an element is information, the first information and the second information may both be information, and depending on the case, they may be the same information or different information.

[0042] Furthermore, expressions such as "if" and "in case that" as described in the present disclosure or claims may be interpreted, depending on the context, as meaning "when or upon," "in response to," "based on," or "according to," and these expressions may be used interchangeably. In addition, other expressions having substantially the same meaning may be used as substitutes for these expressions, provided that they do not impair the technical features of the present disclosure. Furthermore, if a method step (e.g., a step of transmitting a signal) is performed in relation to such terms (e.g., "in case that" or similar expressions) in accordance with the disclosure of the present specification, this may be interpreted as the method step being performed in response to a prior determination that a specific element has a specific state (e.g., bit length exceeding X).

[0043] For example, physical layer signaling may be referred to as L1 (Layer 1) signaling and may include downlink control information (DCI). Additionally, upper layer signaling may include at least one of a medium access control (MAC) control message, a radio resource control (RRC) signaling message, a non-access stratum (NAS) signaling message, or an application layer message. The RRC signaling message may be referred to as L3 (Layer 3) signaling. However, upper layer signaling is not limited to the above examples.

[0044] Additionally, the term "not perform" as used in this disclosure or claims may be understood, depending on the context, to mean to omit or skip the corresponding step. Such a term may be replaced with other terms having the same or substantially similar meaning.

[0045] Additionally, the phrase “transmitting a message containing A and B” as described in the present disclosure may be interpreted to include not only (i) cases where A and B are transmitted as a single message, but also (ii) cases where A and B are transmitted individually through multiple messages (e.g., transmitting a first message containing A and a second message containing B). This interpretation may also apply to cases where messages containing two or more items, such as A, B, and C, are transmitted together or individually.

[0046] In addition, 'transmitting a message containing A and transmitting a message containing B' can also be interpreted as transmitting a single message containing A and B.

[0047] In the embodiments described in this disclosure, terms or components included in the disclosure may be expressed in the singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the context presented for convenience of explanation, and the disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed in the singular form, and even if a component is expressed in the singular form, it may be composed in the plural form.

[0048] The drawings or flowcharts described in this disclosure illustrate exemplary methods that may be implemented according to the principles of this disclosure, and various modifications may be made to the methods illustrated in the flowcharts of this disclosure. For example, although illustrated as a series of steps, the various steps of each drawing or flowchart may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, any step may be omitted or replaced with another step.

[0049] Additionally, the process of the flowchart can be performed by an electronic device, and one or more steps of the flowchart can be implemented by one or more processors that execute instructions to perform specific functions.

[0050] The methods and apparatus proposed in the embodiments of the present disclosure may be disclosed together with drawings including flowcharts to illustrate exemplary methods that may be implemented according to the principles of the present disclosure. Such flowcharts may include different branches and / or sub-branches. It should be understood that the principles of the present disclosure are not limited to combinations of all branches and sub-branches disclosed in the embodiments, and may consist of at least one individual branch or individual sub-branch, in particular only a single branch or a single sub-branch.

[0051] The methods and devices proposed in the embodiments of the present disclosure below are not limited to each embodiment and may be utilized as a combination of all or part of the embodiments proposed in the disclosure. Accordingly, the embodiments of the present disclosure may be applied with some modifications within the scope that does not deviate significantly from the scope of the present disclosure, at the judgment of a person skilled in the art.

[0052] In this case, any wording mentioned in different embodiments may be used interchangeably, combined, or substituted if the concepts correspond. For example, regarding the same or corresponding concepts, even if the expression 'A' is used in one embodiment and the expression 'B' is used in another embodiment, they may be understood by interchangeably, substituted, or combined.

[0053] Terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used. Furthermore, where appropriate, such terms may be replaced with terms defined in similar technical specifications of standardization organizations such as 3GPP (3rd generation partnership project) Technical Specifications (TS) or ETSI (European Telecommunications Standards Institute).

[0054] Hereinafter, the base station is an entity that performs resource allocation of the terminal and may be at least one of gNode B, eNode B, Node B, BS (base station), wireless access unit, base station controller, or a node on the network.

[0055] In addition, the base station of the present disclosure may include a structure split into a central unit (CU) and a distributed unit (DU). In such a structure, the CU is responsible for the upper layer of the control and user plane, and the DU is responsible for the processing of wireless resources in the lower layer. The embodiments of the present disclosure can be equally applied to a 5G base station structure in which functions are split into the CU and DU as described above.

[0056] The terminal may include at least one of user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, tablet, wearable device, Internet of Things (IoT) device, or other device / system capable of performing communication functions.

[0057] In the present disclosure, a downlink (DL) refers to a wireless transmission path of a signal transmitted by a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted by a terminal to a base station.

[0058] In addition, while a 5th generation mobile communication system (5G, new radio, NR) and a 6th generation mobile communication system (6G) may be described below as examples, embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, new advanced mobile communication systems developed after 5G and 6G may be included therein. Furthermore, the present disclosure may be applied to other communication systems (e.g., Wi-Fi systems) with some modifications made in the judgment of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0059] In the following description, the terms "physical channel" and "signal" may be used interchangeably with "data" or "control signal." For example, PDSCH (physical downlink shared channel) is a term referring to a physical channel through which data is transmitted, but PDSCH may also be used to refer to data. That is, in this disclosure, the expression "transmits a physical channel" may be interpreted as equivalent to the expression "transmits data or a signal through a physical channel."

[0060] In describing the present disclosure below, the term "upper layer signaling" may be a signaling corresponding to at least one or a combination of at least one of MIB (master information block), SIB (system information block), SIB M (M=1, 2, …), RRC, MAC CE, NAS (non-access stratum) signaling, or application layer messages. The RRC signaling may also be referred to as L3 signaling (layer 3 signaling).

[0061] Additionally, L1 signaling may be a signaling method corresponding to at least one or a combination of at least one of the following: a physical layer channel or signaling of a PDCCH (physical downlink control channel), a DCI, a UE-specific DCI, a group common DCI, a common DCI, a scheduling DCI (e.g., a DCI used for the purpose of scheduling downlink or uplink data), a non-scheduling DCI (e.g., a DCI not used for the purpose of scheduling downlink or uplink data), a PUCCH (physical uplink control channel), or an UCI (uplink control information). The above L1 signaling may also be referred to as physical layer signaling.

[0062] Hereinafter, the expression in the present disclosure or claims that information can be configured from a base station may mean that, depending on the context, a terminal receives said information from a base station through physical layer signaling or upper layer signaling, and such expression may be replaced with other terms having the same or substantially similar meaning.

[0063] For convenience of explanation below, the present disclosure uses terms and names defined in the 3GPP LTE (3rd Generation Partnership Project Long Term Evolution) standard. However, the present invention is not limited by the above terms and names and can be applied in the same way to systems conforming to other standards.

[0064] FIG. 1 is a drawing illustrating the structure of a wireless communication system according to one embodiment of the present disclosure.

[0065] Referring to FIG. 1, as illustrated, the wireless access network of the wireless communication system consists of a next-generation base station (New Radio gNode B, hereinafter NR gNB, 1-10) and an NR CN (New Radio Core Network, or NG CN: Next Generation Core Network, 1-05). A user terminal (New Radio User Equipment, hereinafter NR UE or terminal, 1-15) can connect to an external network through the NR gNB (1-10) and the NR CN (1-05). Hereinafter, the NR communication system may be used in combination with a next-generation mobile communication system, a wireless communication system, or a 5G-based communication system.

[0066] In FIG. 1, the NR gNB (1-10) corresponds to the eNB (Evolved Node B) of the existing LTE system. The NR gNB is connected to the NR UE (1-15) via a wireless channel and can provide superior service compared to the existing Node B. In the next-generation mobile communication system, since all user traffic is serviced through a shared channel, a device is required to collect status information such as the buffer status, available transmission power status, and channel status of the UEs and perform scheduling, and the NR gNB (1-10) can handle this. A single NR gNB can typically control multiple cells. To achieve ultra-high-speed data transmission compared to existing LTE, it can have a maximum bandwidth greater than that of existing LTE, and can additionally incorporate beamforming technology by using Orthogonal Frequency Division Multiplexing (hereinafter referred to as OFDM) as the wireless access technology. In addition, an Adaptive Modulation & Coding (hereinafter referred to as AMC) method can be applied to determine the modulation scheme and channel coding rate according to the channel conditions of the terminal. The NR CN (1-05) performs functions such as mobility support, bearer configuration, and QoS configuration. The NR CN is a device responsible for various control functions as well as mobility management functions for the terminal, and can be connected to multiple base stations. In addition, the next-generation mobile communication system can be interoperable with the existing LTE system, and the NR CN is connected to the MME (1-25) via a network interface. The MME can be connected to the existing base station eNB (1-30).

[0067] FIG. 2 is a diagram showing the wireless protocol structure of a wireless communication system according to one embodiment of the present disclosure.

[0068] Referring to FIG. 2, the wireless protocol of the wireless communication system consists of NR SDAP (2-01, 2-45), NR PDCP (2-05, 2-40), NR RLC (2-10, 2-35), and NR MAC (2-15, 2-30) at the terminal and the NR base station, respectively.

[0069] The main functions of NR SDAP (2-01, 2-45) may include some of the following functions.

[0070] - User data transfer function (transfer of user plane data)

[0071] - Mapping function between a QoS flow and a DRB for both DL and UL for uplink and downlink

[0072] - Marking QoS flow ID for uplink and downlink (marking QoS flow ID in both DL and UL packets)

[0073] - Function to map reflective QoS flow to data bearers for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0074] Regarding the SDAP layer device, the terminal may receive a setting via an RRC message indicating whether to use the header of the SDAP layer device or the functions of the SDAP layer device for each PDCP layer device, bearer, or logical channel. If the SDAP header is configured, the terminal may be instructed to update or reset the mapping information for the QoS flow of the uplink and downlink and the data bearer using the NAS reflective QoS and AS reflective QoS 1-bit indicators of the SDAP header. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used for data processing priority, scheduling information, etc., to support smooth service.

[0075] The main functions of NR PDCP (2-05, 2-40) may include some of the following functions.

[0076] - Header compression and decompression features (ROHC only)

[0077] - User data transfer function (Transfer of user data)

[0078] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

[0079] - Out-of-sequence delivery of upper layer PDUs

[0080] - Reordering function (PDCP PDU reordering for reception)

[0081] - Duplicate detection function (Duplicate detection of lower layer SDUs)

[0082] - Retransmission of PDCP SDUs

[0083] - Encryption and decryption functions (Ciphering and deciphering)

[0084] - Timer-based SDU discard in uplink.

[0085] In the above, the reordering function of the NR PDCP device refers to a function of reordering PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and may include a function of transmitting data to an upper layer in the reordered order, or a function of transmitting immediately without considering the order, may include a function of recording lost PDCP PDUs by reordering, may include a function of reporting the status of lost PDCP PDUs to the transmitting side, and may include a function of requesting retransmission of lost PDCP PDUs.

[0086] The main functions of NR RLC(2-10, 2-35) may include some of the following functions.

[0087] - Data transfer function (Transfer of upper layer PDUs)

[0088] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

[0089] - Out-of-sequence delivery of upper layer PDUs

[0090] - ARQ function (Error Correction through ARQ)

[0091] - Concatenation, segmentation, and reassembly functions of RLC SDUs

[0092] - Re-segmentation function (Re-segmentation of RLC data PDUs)

[0093] - Reordering function (Reordering of RLC data PDUs)

[0094] - Duplicate detection

[0095] - Error detection function (Protocol error detection)

[0096] - RLC SDU discard function

[0097] RLC re-establishment function

[0098] In the above, the in-sequence delivery function of the NR RLC device refers to the function of delivering RLC SDUs received from a lower layer to an upper layer in sequence; it may include a function to reassemble and deliver them if a single RLC SDU is received divided into multiple RLC SDUs; it may include a function to rearrange received RLC PDUs based on an RLC SN (sequence number) or PDCP SN (sequence number); it may include a function to record lost RLC PDUs after rearranging the order; it may include a function to report the status of lost RLC PDUs to the transmitting side; it may include a function to request retransmission of lost RLC PDUs; if there are lost RLC SDUs, it may include a function to deliver only the RLC SDUs prior to the lost RLC SDU to the upper layer in sequence; or if a predetermined timer has expired even if there are lost RLC SDUs, it may include a function to deliver all RLC SDUs received before the timer started to the upper layer in sequence; or It may include a function that delivers all RLC SDUs received up to the present to the upper layer in order once a predetermined timer has expired, even if there are lost RLC SDUs. Additionally, the RLC PDUs mentioned above may be processed in the order they are received (regardless of the order of sequence numbers, but in the order of arrival) and delivered to the PDCP device out of order (out-of-sequence delivery). In the case of segments, segments stored in a buffer or to be received later may be received, reconstructed into a single complete RLC PDU, processed, and then delivered to the PDCP device.The above NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or replaced with the multiplexing function of the NR MAC layer.

[0099] In the above, the out-of-sequence delivery function of the NR RLC device refers to a function of delivering RLC SDUs received from a lower layer directly to an upper layer regardless of order. It may include a function of reassembling and delivering them when a single RLC SDU is received divided into multiple RLC SDUs, and may include a function of storing the RLC SN or PDCP SN of the received RLC PDUs and sorting the order to record the lost RLC PDUs.

[0100] The NR MAC (2-15, 2-30) can be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of the NR MAC may include some of the following functions.

[0101] - Mapping function (Mapping between logical channels and transport channels)

[0102] - Multiplexing and demultiplexing functions (Multiplexing / demultiplexing of MAC SDUs)

[0103] - Scheduling information reporting function

[0104] - HARQ function (Error correction through HARQ)

[0105] - Priority handling between logical channels of one UE

[0106] - Priority handling between UEs by means of dynamic scheduling

[0107] - MBMS service identification function

[0108] - Transport format selection function

[0109] - Padding

[0110] The NR PHY layer (2-20, 2-25) can perform the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.

[0111] FIG. 3 is a drawing for explaining the concept of a subband full duplex (hereinafter SBFD) of a base station or cell according to one embodiment of the present disclosure.

[0112] Referring to the drawing, the base station (3-05) performs wireless communication (3-10) with the terminal (3-20), and to this end, it determines frequency and time resources (3-15) and can schedule downlink (DL) and uplink (UL) resources to the terminal within said resources. SBFD basically operates in a cell that supports TDD (Time Division Duplex), and the following embodiment assumes and describes operation in a TDD cell. The resources (3-15) allocated to the terminal in the past could be composed of a downlink slot / symbol (3-25) and an uplink slot / symbol (3-45), and a flexible or special slot / symbol allocated when changing the downlink / uplink direction. Now, with the introduction of SBFD, it is possible to configure SBFD slots / symbols (3-30, 3-35, 3-40) in which downlink and uplink resources are mixed between a base station and a terminal capable of using SBFD. Of course, SBFD slots / symbols (3-30, 3-35, 3-40) can be configured not only in the same location as in FIG. 3, but also in any slot / symbol that the base station wishes to configure, such as the Downlink slot / symbol of 3-25.

[0113] In this situation, to support random access of the terminal, the base station can allocate an uplink physical layer Random Access Channel (PRACH) capable of transmitting and receiving a preamble for random access within an SBFD slot / symbol, rather than the existing uplink slot / symbol (3-45), and can allocate a PRACH occasion (RO) (3-50). The SBFD RO may be contained within an SBFD slot / symbol as shown in FIG. 3, may exist across one or more SBFD slots / symbols, and may exist across not only one or more SBFD slots / symbols but also a normal Uplink slot / symbol (3-45).

[0114] Through this SBFD RO (3-50), terminals supporting SBFD gain additional RO opportunities in addition to existing legacy RO, which enables random access with less delay and collision.

[0115] As explained above, a base station or cell supporting SBFD can support random access using SBFD resources, and can allocate a physical Random Access Channel (PRACH) and a PRACH occasion (RO) for this purpose.

[0116] FIG. 4 is a diagram illustrating a method for providing random access settings in a subband full duplex (hereinafter SBFD) of a base station or cell according to one embodiment of the present disclosure.

[0117] Referring to Fig. 4, a method for selecting the RO type in CFRA (Contention Free Random Access) is illustrated.

[0118] In one embodiment of the present disclosure, a base station may provide a CFRA resource to a terminal for a specific Random Access via an RRC message (e.g., RRCReconfiguration) or a SIB message (e.g., SIB1) in one of the following cases. A Random Access trigger event (4-00) in which a dedicated RACH resource is set may be one of the following cases.

[0119] - The Random Access process was initiated by PDCCH order, and the ra-PreambleIndex provided by PDCCH is a value other than 0b000000.

[0120] - When the relevant Random Access process was initiated by an SI request, and the Random Access resources for the SI request were provided explicitly through RRC settings.

[0121] - The Random Access process was initiated by SpCell (Special Cell) beam failure recovery, and a 4-Step CFRA resource for the beam failure recovery request was provided via RRC for the Bandwidth Part (BWP) selected during the Random Access process.

[0122] - The Random Access process is initiated by reconfiguration with sync, excluding recovery using an LTM candidate configuration, and a 2-Step CFRA resource or a 4-Step CFRA resource is provided via rach-ConfigDedicated for the BWP selected during the Random Access process.

[0123] - When CFRA resources are provided explicitly via LTM Cell Switch Command MAC CE.

[0124] In one embodiment of the present disclosure, when a CFRA resource is provided, the terminal may explicitly receive instructions from the base station regarding the RO Type (SBFD RO or Non-SBFD RO) to be used in the Random Access. In one embodiment, the RO Type instructions may be provided only when a 4-Step CFRA resource is set.

[0125] In one embodiment of the present disclosure, when a CFRA resource is provided, the terminal may explicitly receive a CFRA resource of the indicated RO Type to be used in the corresponding Random Access from the base station.

[0126] In one embodiment of the present disclosure, when a CFRA resource is provided, the terminal may explicitly receive from the base station a CFRA resource belonging to an RO Type other than the indicated RO Type to be used in the Random Access (e.g., if the indicated RO Type is SBFD RO, it means nonSBFD RO; if the indicated RO Type is non-SBFD RO, it means SBFD RO).

[0127] Referring to FIG. 4, in one embodiment of the present disclosure, a Carrier selection (4-10) may be performed after the Random Access process has started. For example, in the case of Random Access initiated by an LTM Cell Switch Command MAC CE, the base station may indicate which UL carrier to use to transmit PRACH through the CFRA resource via a specific field / bit (e.g., S / U field) of the MAC CE. For example, if the field is set to 1, a SUL (Supplementary Uplink) may be selected, and otherwise, a NUL (Normal Uplink) may be selected. The field may be 1 bit.

[0128] For example, in the case of Random Access initiated by an LTM Cell Switch Command MAC CE, the base station can indicate the presence or absence of a CFRA resource field in the MAC CE through a specific field (e.g., the C field) of the MAC CE. For example, the field can be interpreted as follows.

[0129] C: This field indicates the presence of the contention-free Random Access Resources fields. If the value of this field is set to 1, the following fields are present: Random Access Preamble index field, S / U field, SS / PBCH index field, PRACH Mask index field, Repetition number field, RO Type field, and the reserved bits in the same octet. If the value of this field is set to 0, these fields are absent.

[0130] For example, if the above C field is set to 1, it may indicate that CFRA resource fields (e.g., Random Access Preamble index field, S / U field, SS / PBCH index field, PRACH Mask index field, Repetition number field, etc.) exist in the corresponding MAC CE. For example, one of the above CFRA resource fields may include an RO Type field / Bit that indicates whether it is an SBFD RO or a non-SBFD RO, and the above C field may indicate the existence of the corresponding field (e.g., if C is 1, it exists; if C is 0, it does not exist). For example, one of the existing R (Reserved) bits of the LTM Cell Switch Command MAC CE may be used as the above RO Type field / Bit. If the above RO Type field is set to 1, this can be interpreted as instructing the base station to perform the corresponding CFRA through the SBFD RO. If the above RO Type field is set to 0, this can be interpreted as the base station instructing the CFRA to be performed through the non-SBFD RO.

[0131] In one embodiment of the present disclosure, a terminal that has finished Carrier selection (4-10) can select a BWP (4-20) to perform Random Access. In one embodiment of the present disclosure, a terminal that has performed BWP selection (4-20) can perform RO type selection (4-30).

[0132] In one embodiment of the present disclosure, a base station may configure a CFRA resource for an SI Request to a terminal via an RRC message (e.g., RRCReconfiguration) and / or a SIB message (SIB1). For example, the CFRA resource configuration may be included in an SI-RequestConfig IE (when Msg1 repetition is not used) or an SI-RequestConfigRepetition IE (when Msg1 repetition is used). For example, the base station may configure an RO Type for an SI Request.

[0133] For example, the above RO type indicator may be included in SI-RequestConfig IE (when Msg1 repetition is not used) or SI-RequestConfigRepetition IE (when Msg1 repetition is used). For example, the terminal may transmit a Preamble for an SI Request using an SBFD RO if the corresponding RO Type indicator exists or if the RO Type field indicates an SBFD RO. For example, the terminal may transmit a Preamble for an SI Request using a non-SBFD RO if the corresponding RO Type indicator does not exist or if the RO Type field indicates a non-SBFD RO.

[0134] In one embodiment of the present disclosure, the RO type indicator may be included in the SI-RequestResources IE of the SI-RequestConfig IE (when Msg1 repetition is not used). In one embodiment of the present disclosure, the RO type indicator may be included in one or more fields among the SI-RequestResourcesRepetitionNum2 / 4 / 8 fields of the SI-RequestConfigRepetition IE (when Msg1 repetition is used). For example, if the RO Type indicator exists or the RO Type field indicates an SBFD RO, the terminal may use the SBFD RO to transmit a Preamble for an SI Request using a CFRA resource corresponding to the SI Message. For example, if the RO Type indicator does not exist or the RO Type field indicates a non-SBFD RO, the terminal may use the non-SBFD RO to transmit a Preamble for an SI Request using a CFRA resource corresponding to the SI Message. For example, SI-RequestConfig / SI-RequestConfigRepetition / SI-ReqeustResources / SI-RequestResourcesRepetition IE can have the following structure.

[0135] SI-RequestConfiginformation element-- ASN1START-- TAG-SI-REQUESTCONFIG-STARTSI-RequestConfig ::= SEQUENCE {rach-OccasionsSI SEQUENCE {rach-ConfigSI RACH-ConfigGeneric,ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen}} OPTIONAL, -- Need Rsi-RequestPeriod ENUMERATED {one, two, four, six, eight, ten, twelve, sixteen} OPTIONAL, -- Need Rsi-RequestResources SEQUENCE (SIZE (1..maxSI-Message)) OF SI-RequestResourcesro-Type ENUMERATED {sbfd}}SI-RequestResources ::= SEQUENCE {ra-PreambleStartIndex INTEGER (0..63),ra-AssociationPeriodIndex INTEGER (0..15) OPTIONAL, -- Need Rra-ssb-OccasionMaskIndex INTEGER (0..15) OPTIONAL -- Need Rro-Type ENUMERATED {sbfd}}

[0136] SI-RequestConfigRepetitioninformation element-- ASN1START-- TAG-SI-REQUESTCONFIGREPETITION-STARTSI-RequestConfigRepetition-r18 ::= SEQUENCE {rach-OccasionsSI-r18 SEQUENCE {rach-ConfigSI-r18 RACH-ConfigGeneric,ssb-perRACH-Occasion-r18 ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen}} OPTIONAL, -- Need Rsi-RequestResourcesRepetitionNum2-r18 SEQUENCE (SIZE (1..maxSI-Message)) OF SI-RequestResourcesRepetition-r18 OPTIONAL, -- Need Rsi-RequestResourcesRepetitionNum4-r18 SEQUENCE (SIZE (1..maxSI-Message)) OF SI-RequestResourcesRepetition-r18 OPTIONAL, -- Need Rsi-RequestResourcesRepetitionNum8-r18 SEQUENCE (SIZE (1..maxSI-Message)) OF SI-RequestResourcesRepetition-r18 OPTIONAL, -- Need R...ro-Type ENUMERATED {sbfd}}SI-RequestResourcesRepetition-r18 ::= SEQUENCE {ra-PreambleStartIndex-r18 INTEGER (0..63)ro-Type ENUMERATED {sbfd}}-- TAG-SI-REQUESTCONFIGREPETITION-STOP-- ASN1STOP

[0137] In one embodiment of the present disclosure, a base station may, via an RRC message (e.g., RRCReconfiguration) or a SIB1 message, include a BeamFailureRecoveryConfig IE field in the BWP-UplinkDedicated IE for an initial Uplink BWP and / or the BWP-UplinkDedicated IE for other Uplink BWPs to set an indicator (e.g., ro-Type) that can indicate a CFRA resource for beam failure recovery and which RO type (SBFD RO or non-SBFD RO) the said CFRA resource belongs to, or which RO Type should be used to perform beam failure recovery. For example, if the indicator is set to SBFD RO, or if the said field exists, the terminal may perform Beam Failure Recovery using SBFD RO. For example, if the indicator is set to non-SBFD RO, or if the said field does not exist, the terminal may perform Beam Failure Recovery using non-SBFD RO. For example, if the above RO type field instructs to use SBFD RO, the provided CFRA RO resource may include only SBFD RO. For example, if the above RO type field instructs to use non-SBFD RO, the provided CFRA RO resource may include only non-SBFD RO. For example, BeamFailureRecoveryConfig IE may have the following structure.

[0138] BeamFailureRecoveryConfiginformation element-- ASN1START-- TAG-BEAMFAILURERECOVERYCONFIG-STARTBeamFailureRecoveryConfig ::= SEQUENCE {rootSequenceIndex-BFR INTEGER (0..137) OPTIONAL, -- Need Mrach-ConfigBFR RACH-ConfigGeneric OPTIONAL, -- Need Mrsrp-ThresholdSSB RSRP-Range OPTIONAL, -- Need McandidateBeamRSList SEQUENCE (SIZE(1..maxNrofCandidateBeams)) OF PRACH-ResourceDedicatedBFR OPTIONAL, -- Need Mssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two,four, eight, sixteen} OPTIONAL, -- Need Mra-ssb-OccasionMaskIndex INTEGER (0..15) OPTIONAL, -- Need MrecoverySearchSpaceId SearchSpaceId OPTIONAL, -- Need Rra-Prioritization RA-Prioritization OPTIONAL, -- Need RbeamFailureRecoveryTimer ENUMERATED {ms10, ms20, ms40, ms60, ms80, ms100, ms150, ms200} OPTIONAL, -- Need M...,[[msg1-SubcarrierSpacing SubcarrierSpacing OPTIONAL -- Need M]],[[ra-PrioritizationTwoStep-r16 RA-Prioritization OPTIONAL, -- Need RcandidateBeamRSListExt-v1610 SetupRelease{ CandidateBeamRSListExt-r16} OPTIONAL -- Need M]],[[spCell-BFR-CBRA-r16 ENUMERATED {true} OPTIONAL -- Need R]]ro-Type ENUMERATED {sbfd}}PRACH-ResourceDedicatedBFR ::= CHOICE {ssb BFR-SSB-Resource,csi-RS BFR-CSIRS-Resource}BFR-SSB-Resource ::= SEQUENCE {ssb SSB-Index,ra-PreambleIndex INTEGER (0..63),ro-Type ENUMERATED {sbfd}...}BFR-CSIRS-Resource ::= SEQUENCE {csi-RS NZP-CSI-RS-ResourceId,ra-OccasionList SEQUENCE (SIZE(1..maxRA-OccasionsPerCSIRS)) OF INTEGER (0..maxRA-Occasions-1) OPTIONAL, -- Need Rra-PreambleIndex INTEGER (0..63) OPTIONAL, -- Need Rro-Type ENUMERATED {sbfd}...}CandidateBeamRSListExt-r16::= SEQUENCE (SIZE(1.. maxNrofCandidateBeamsExt-r16)) OF PRACH-ResourceDedicatedBFR-- TAG-BEAMFAILURERECOVERYCONFIG-STOP-- ASN1STOP.

[0139] In one embodiment of the present disclosure, a base station may configure a terminal's CFRA handover (Reconfiguration with sync) resource by including a RACH-ConfigDedicated IE in an RRC message (e.g., RRCReconfiguration) or a SIB1 message. For example, the base station may configure an indicator (e.g., ro-Type) in the RACH-ConfigDedicated IE that indicates which RO type (SBFD RO or non-SBFD RO) the CFRA resource belongs to, or which RO Type should be used to perform the CFRA handover (Reconfiguration with sync). For example, if the indicator is set to SBFD RO, or if the corresponding field exists, the terminal may perform the CFRA handover (Reconfiguration with sync) using the SBFD RO. For example, if the indicator is set to non-SBFD RO, or if the corresponding field does not exist, the terminal may perform the CFRA handover (Reconfiguration with sync) using the non-SBFD RO. For example, if the RO type field indicates to use SBFD RO, the provided CFRA RO resources may include only SBFD RO. For example, if the RO type field indicates to use non-SBFD RO, the provided CFRA RO resources may include only non-SBFD RO.

[0140] RACH-ConfigDedicatedinformation element-- ASN1START-- TAG-RACH-CONFIGDEDICATED-STARTRACH-ConfigDedicated ::= SEQUENCE {cfra CFRA OPTIONAL, -- Need Sra-Prioritization RA-Prioritization OPTIONAL, -- Need N...,[[ra-PrioritizationTwoStep-r16 RA-Prioritization OPTIONAL, -- Need Ncfra-TwoStep-r16 CFRA-TwoStep-r16 OPTIONAL -- Need S]]}CFRA ::= SEQUENCE {occasions SEQUENCE {rach-ConfigGeneric RACH-ConfigGeneric,ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen}OPTIONAL -- Cond Mandatory} OPTIONAL, -- Need Sresources CHOICE {ssb SEQUENCE {ssb-ResourceList SEQUENCE (SIZE(1..maxRA-SSB-Resources)) OF CFRA-SSB-Resource,ra-ssb-OccasionMaskIndex INTEGER (0..15)},csirs SEQUENCE {csirs-ResourceList SEQUENCE (SIZE(1..maxRA-CSIRS-Resources)) OF CFRA-CSIRS-Resource,rsrp-ThresholdCSI-RS RSRP-Range}},...,[[totalNumberOfRA-Preambles INTEGER (1..63) OPTIONAL -- Cond Occasions]],[[msg1-RepetitionNum-r18 ENUMERATED {n2, n4, n8, spare1} OPTIONAL -- Cond 4StepCFRArep]]ro-Type ENUMERATED {sbfd}}CFRA-TwoStep-r16 ::= SEQUENCE {occasionsTwoStepRA-r16 SEQUENCE {rach-ConfigGenericTwoStepRA-r16 RACH-ConfigGenericTwoStepRA-r16,ssb-PerRACH-OccasionTwoStepRA-r16 ENUMERATED {oneEighth, oneFourth, oneHalf, one,two, four, eight, sixteen}} OPTIONAL, -- Need SmsgA-CFRA-PUSCH-r16 MsgA-PUSCH-Resource-r16,msgA-TransMax-r16 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL, -- Need SresourcesTwoStep-r16 SEQUENCE {ssb-ResourceList SEQUENCE (SIZE(1..maxRA-SSB-Resources)) OF CFRA-SSB-Resource,ra-ssb-OccasionMaskIndex INTEGER (0..15)},...}CFRA-SSB-Resource ::= SEQUENCE {ssb SSB-Index,ra-PreambleIndex INTEGER (0..63),...,[[msgA-PUSCH-Resource-Index-r16 INTEGER (0..3071) OPTIONAL -- Cond 2StepCFRA]]ro-Type ENUMERATED {sbfd}}CFRA-CSIRS-Resource ::= SEQUENCE {csi-RS CSI-RS-Index,ra-OccasionList SEQUENCE (SIZE(1..maxRA-OccasionsPerCSIRS)) OF INTEGER (0..maxRA-Occasions-1),ra-PreambleIndex INTEGER (0..63),...ro-Type ENUMERATED {sbfd}}-- TAG-RACH-CONFIGDEDICATED-STOP-- ASN1STOP.

[0141] In one embodiment of the present disclosure, if a terminal includes an indicator that indicates an RO type in RACH-ConfigDedicated, BeamFailureRecoveryConfig, SI-RequestConfig, and SI-RequestConfigRepetition, it can select the RO type indicated by the indicator and perform a Random Access process.

[0142] In one embodiment of the present disclosure, a terminal that has finished selecting an RO type (4-30) may select a random access resource set by considering the applicable feature or feature combination. For example, if the terminal has set a threshold value for SBFD RO dedicated to the threshold value that determines the number of repetitions of Msg1, i.e., rsrp-ThresholdMsg1-RepetitionNum2 / 4 / 8, and has selected an SBFD RO during the Random Access process, the terminal may determine the number of repetitions of Msg1 using the threshold value for SBFD RO dedicated to the threshold value. For example, if the terminal has set a threshold value for SBFD RO dedicated to the threshold value that determines the number of repetitions of Msg1, i.e., rsrp-ThresholdMsg1-RepetitionNum2 / 4 / 8, and has selected a non-SBFD RO during the Random Access process, the terminal may determine the number of repetitions of Msg1 using the threshold value for legacy / non-SBFD RO for the legacy RO / non-SBFD RO. For example, the above operation can be applied to the process of determining Msg 1 repetition for an initial random access / SI Request.

[0143] In one embodiment of the present disclosure, RO type selection (4-30) may be performed after the random access resource set selection (4-40) operation. In one embodiment of the present disclosure, RO type selection (4-30) may be performed during the random access resource set selection (4-40) operation.

[0144] In one embodiment of the present disclosure, a terminal that selects a random access resource set (4-40) can select a random access type (2-step / 4-step) (4-50).

[0145] In one embodiment of the present disclosure, a terminal that selects an SBFD RO during the RO type selection (4-30) process may be restricted from performing 2-Step random access. That is, it may be restricted to performing only 4-Step Random access.

[0146] In one embodiment of the present disclosure, a terminal that has finished selecting an RA type can perform a variable initialization (4-60) operation corresponding to the RA type.

[0147] In one embodiment of the present disclosure, a terminal that has completed variable initialization (4-60) can perform RA resource selection (4-70). For example, during RA resource selection (selection of SSB / RO / Preamble, etc.), the terminal can select an RO belonging to the selected RO type and transmit a Preamble.

[0148] FIG. 5 is a drawing illustrating an RO type selection method according to one embodiment of the present disclosure.

[0149] Referring to FIG. 5, if the terminal does not receive a random access response (RAR) containing preamble identifiers such as the transmitted preamble index after completing the preamble transmission and before the ra-ResponseWindow expires, it may consider the RAR reception to have failed (5-10) and increase a counter (e.g., PREAMBLE_TRANSMISSION_COUNTER) that records the number of preamble transmissions by 1 (5-20).

[0150] In one embodiment of the present disclosure, after completing the transmission of Msg3, the terminal may consider that contention resolution was unsuccessful (5-10) when ra-ContentionResolutionTimer expires. For example, the terminal that failed to achieve contention resolution (5-10) may increase PREAMBLE_TRANSMISSOION_COUNTER by 1 (5-20).

[0151] In one embodiment of the present disclosure, the terminal can perform an RO Type change (5-40) after increasing the PREAMBLE_TRANSMISSON_COUNTER by 1 and when the value is equal to the RO type change threshold value (e.g., preambleTransMaxSBFD) plus 1 (5-30).

[0152] In one embodiment of the present disclosure, the RO type change operation (5-40) may not be performed when the base station provides CFRA resources and an RO type indicator for the corresponding Random Access process. For example, when the random access process is performed for at least one of CFRA-based beam failure recovery, dedicated resource-based SI request, CFRA-based reconfiguration with sync, CFRA-based pdcch order, and CFRA-based LTM cell switch, if the base station provides CFRA resource settings and the corresponding RO type indicator, the terminal may not perform the RO type change operation and may maintain the RO type indicated by the base station.

[0153] In one embodiment of the present disclosure, the RO type change operation (5-40) may be performed by changing the current RO type to a non-SBFD RO when the current RO type is an SBFD RO, or changing the current RO type to an SBFD RO when the current RO type is a non-SBFD RO.

[0154] In one embodiment of the present disclosure, the RO type change operation (5-40) may be performed when the base station provides a CFRA resource for the corresponding random access process, and the CFRA resource includes both SBFD RO and non-SBFD RO.

[0155] In one embodiment of the present disclosure, the RO type change operation (5-40) may be performed when the base station provides CFRA resources for the corresponding random access process, and when it provides corresponding CFRA resources for the SBFD RO and the non-SBFD RO, respectively. For example, if the current RO type is SBFD RO and the base station provides CFRA resources only for the SBFD RO and does not provide CFRA resources for the non-SBFD RO, the RO type change procedure may be omitted / not performed. For example, if the current RO type is non-SBFD RO and the base station provides CFRA resources only for the non-SBFD RO and does not provide CFRA resources for the SBFD RO, the RO type change procedure may be omitted / not performed.

[0156] In one embodiment of the present disclosure, after the RO type change (5-40) is performed, the terminal can apply a threshold value setting corresponding to the RO type to determine whether to apply the feature / feature combination again, and select an RA resource set (5-50) corresponding to the applied feature / feature combination.

[0157] In one embodiment of the present disclosure, a terminal that has selected the RA resource set (5-50) can perform an RA type (2-step / 4-step) selection (5-60). For example, if the current RO type is SBFD RO, the terminal can perform only a 4-step RA.

[0158] In one embodiment of the present disclosure, when the current RO type is a non-SBFD RO, the terminal can perform only a 4-step RA.

[0159] In one embodiment of the present disclosure, when a base station sets a 4-step CFRA resource for the corresponding random access process, the terminal may perform a 4-step RA without performing the RA type operation (5-60).

[0160] In one embodiment of the present disclosure, the terminal can perform a variable initialization operation (5-70) that is suitable for the RA type. For example, during the variable initialization operation, the terminal can perform variable initialization that is suitable for the RO type by considering the current RO type.

[0161] In one embodiment of the present disclosure, the terminal can perform RA resource (SSB / CSI-RS / RO / Preamble index) selection (5-80) and then perform Preamble transmission through the selected resource.

[0162] In one embodiment of the present disclosure, if the terminal satisfies the CFRA resource selection criteria, it can perform Preamble transmission through the CFRA resource.

[0163] In one embodiment of the present disclosure, after changing the RO type (5-40), the terminal immediately performs the RA resource selection (5-80) operation, and other operations (5-50, 5-60, 5-70) may be omitted. The omission may be performed only when the Random Access process is for CFRA-based reconfiguration with sync (L3 handover) or CFRA-based LTM cell switch.

[0164] In one embodiment of the present disclosure, after the RO type change (5-40), if the Random Access process is for a dedicated resource-based SI request, the RA resource set selection (5-50) operation may be performed. This is because the threshold value used for determining the Msg 1 repetition for the SI request may change due to the RO type change.

[0165] FIG. 6 is a drawing illustrating an RO type selection method according to one embodiment of the present disclosure.

[0166] Referring to FIG. 6, if the terminal that sent MsgA does not successfully receive MsgB or RAR until the msgB-ResponseWindow expires (6-00), it may increase PREAMBLE_TRANSMISSION_COUNTER by 1 (6-10).

[0167] In one embodiment of the present disclosure, a terminal that has increased PREAMBLE_TRANSMISSION_COUNTER by 1 (6-10) can change the RA type to 4-step RA when the PREAMBLE_TRANSMISSION_COUNTER value is equal to a value obtained by adding 1 to a specific threshold value (e.g., msgA-TransMax).

[0168] In one embodiment of the present disclosure, a terminal that has changed the RA type from 2-step to 4-step can perform RO type selection (6-40).

[0169] For example, the above RO type selection operation can be compared with a specific RSRP threshold value (e.g., rsrp-ThresholdSBFD) set by the base station, and if the threshold value condition is satisfied, an SBFD RO is selected, and if not, a non-SBFD RO is selected.

[0170] In one embodiment of the present disclosure, a terminal that has performed RO type selection (6-40) can determine an applicable feature / feature combination using a threshold value corresponding to the corresponding RO type (e.g., a threshold value determining msg1 repetition) and select an RA resource set corresponding to the applicable feature / feature combination (6-50). Subsequently, the terminal can perform 4-step RA and variable initialization according to the selected RO type. Subsequently, the terminal can select an RA resource corresponding to the selected RO type (6-70) and perform Preamble transmission (6-80) through the selected RA resource.

[0171] In one embodiment of the present disclosure, a terminal that has changed the RA type from 2-step to 4-step (6-30) may not perform RO type selection (6-40). That is, when the terminal performs 4-Step RA, it may perform it while maintaining the existing RO type, the non-SBFD RO type.

[0172] For example, a terminal that has changed the RA type from 2-step to 4-step (6-30) can perform variable initialization suitable for 4-step RA and non-SBFD RO without performing RO type selection (6-40). Subsequently, the terminal can select an RA resource suitable for non-SBFD RO and perform Preamble transmission through the selected RA resource.

[0173] In one embodiment of the present disclosure, in 4-50 of FIG. 4, the terminal may operate as follows when setting the RA_TYPE. For example, the RA_TYPE may be set to 2-step RA only when the RO_TYPE is a non-SBFD RO. This may be because SBFD RO does not support 2-step RA.

[0174] 1> if the Random Access procedure is initiated by PDCCH order and if the ra-PreambleIndex explicitly provided by PDCCH is not 0b000000; or

[0175] 1> if the Random Access procedure was initiated for SI request (as specified in TS 38.331 [5]) and the Random Access Resources for SI request have been explicitly provided by RRC; or

[0176] 1> if the Random Access procedure was initiated for SpCell beam failure recovery (as specified in clause 5.17) and if the contention-free Random Access Resources for beam failure recovery request for 4-step RA type have been explicitly provided by RRC for the BWP selected for Random Access procedure; or

[0177] 1> if the Random Access procedure was initiated for reconfiguration with sync not initiated for recovery using an LTM candidate configuration as specified in TS 38.331 [5] clause 5.3.7.3 and if the contention-free Random Access Resources for 4-step RA type have been explicitly provided in rach-ConfigDedicated for the BWP selected for Random Access procedure; or

[0178] 1> if the contention-free Random Access Resources have been explicitly provided in the LTM Cell Switch Command MAC CE:

[0179] 2> set the RA_TYPE to 4-stepRA.

[0180] 1> else if the RO_TYPE is set to non-SBFD-RO, and the BWP selected for Random Access procedure is configured with both 2-step and 4-step RA type Random Access Resources within the selected set of Random Access resources (as specified in clause 5.1.1b) and the RSRP of the downlink pathloss reference is above msgA-RSRP-Threshold; or

[0181] 1> if the BWP selected for Random Access procedure is only configured with 2-step RA type Random Access resources within the selected set of Random Access resources according to clause 5.1.1b; or

[0182] 1> if the Random Access procedure was initiated for reconfiguration with sync not initiated for recovery using an LTM candidate configuration as specified in TS 38.331 [5] clause 5.3.7.3 and if the contention-free Random Access Resources for 2-step RA type have been explicitly provided in rach-ConfigDedicated for the BWP selected for Random Access procedure:

[0183] 2> set the RA_TYPE to 2-stepRA.

[0184] 1> else:

[0185] 2> set the RA_TYPE to 4-stepRA.

[0186] In one embodiment of the present disclosure, in 4-30 of FIG. 4, the terminal may operate as follows when setting the RO_TYPE.

[0187] 1> If an SBFD RO for Random Access Preamble transmission is provided via a higher layer (e.g., RRC) for the Random Access process (e.g., if the terminal supports SBFD functionality and settings related to SBFD RO resources configured by the base station):

[0188] 2> If the RO type for the corresponding Random Access process is specified as SBFD RO:

[0189] 3> You can set RO_TYPE to SBFD-RO.

[0190] 2> If the RO type for the corresponding Random Access process is specified as non-SBFD RO:

[0191] 3> You can set RO_TYPE to non-SBFD-RO.

[0192] 2> If the RO type is not specified for the Random Access process:

[0193] 3> If a specific threshold (e.g., sbfd-RSRP-ThresholdRO-Type) is set for the corresponding Random Access process:

[0194] 4> If the RSRP of the downlink pathloss reference value is less than the corresponding threshold (e.g., sbfd-RSRP-ThresholdRO-Type) and the usage method for that threshold (e.g., sbfd-RSRP-ThresholdRO-TypeUsage) is set to below; or

[0195] 4> If the RSRP of the downlink pathloss reference is greater than the corresponding threshold (e.g., sbfd-RSRP-ThresholdRO-Type) and the usage method of that threshold (e.g., sbfd-RSRP-ThresholdRO-TypeUsage) is set to above:

[0196] 5> You can set RO_TYPE to SBFD-RO.

[0197] 4> If not:

[0198] 5> You can set RO_TYPE to non-SBFD-RO.

[0199] 1> Otherwise (e.g., if the terminal does not support SBFD, and / or if the terminal does not support SBFD RO resource-related settings configured by the base station):

[0200] 2> You can set RO_TYPE to non-SBFD-RO.

[0201] In one embodiment of the present disclosure, referring to FIG. 5, if the number of preamble transmissions in 5-30 is equal to a specific threshold value (e.g., preambleTransMaxRO-Type) + 1, the terminal can change the RO_TYPE in 5-40. For example, if the current RO_TYPE is SBFD-RO, the RO_TYPE can be changed to non-SBFD-RO. For example, if the current RO_TYPE is non-SBFD-RO, the RO_TYPE can be changed to SBFD-RO.

[0202] In one embodiment of the present disclosure, referring to FIG. 5, the terminal can operate as follows after changing RO_TYPE in 5-40.

[0203] If a threshold value determining at least one Msg1 repetition (e.g., rsrp-ThresholdMsg1-RepetitionNumX, X=2, 4, or 8) is set separately for SBFD RO and non-SBFD RO, or if the application of Msg1 repetition and / or the number of times Msg1 repetition is applied differs for SBFD RO and non-SBFD RO, the terminal may perform Section 5.1.1b of TS 38.321 (Selection of the set of Random Access resources for the Random Access procedure) in 5-50. For example, after changing the RO Type, the re-selection of the RA resource set may be performed only if there exists an RA resource set associated with the same feature or feature combination among the RA resource sets that share the same prach-ConfigurationIndex as the existing RA resource set, and the re-selection to that RA resource set may be performed. For example, re-selection to the RA resource set may be performed only if an RO resource corresponding to the RO Type after the change is configured or provided in the above RA resource set. The above RA resource set re-selection may not be performed if a CFRA resource is provided and / or a RACH resource for an SI Request is provided. When the above RA resource set re-selection is performed, the terminal may perform parameter initialization by applying the RACH setting corresponding to the selected RA resource set.For example, the above parameter may include one or more of startPreambleForThisPartition, numberOfPreamblesPerSSB-ForThisPartition, numberOfRA-PreamblesGroupA, and msg1-RepetitionTimeOffsetROGroup. For example, if, after changing the RO Type, an RO resource set re-selection can be performed only if an RO resource having the changed RO Type is set / provided in the RA resource set corresponding to the feature or feature combination corresponding to the changed RO Type. For example, after selecting the RO Type (4-30), the terminal can select the corresponding RA resource set only if an RO resource corresponding to the selected RO Type is set in the RA resource set corresponding to the feature or feature combination corresponding to the selected RO Type. For example, after selecting an RO type (4-30), if the RO resource corresponding to the selected RO type (e.g., SBFD RO) is not set in the RA resource set corresponding to the feature or feature combination corresponding to the selected RO type (e.g., SBFD RO), the terminal may select an RO type (non-SBFD RO) corresponding to the RO resource set (e.g., non-SBFD RO) set in the RA resource set. For example, if the base station separately sets an RSRP threshold for msg1 repetition number X (e.g., X is one of 2, 4, or 8) for SBFD RO, the base station setting may be restricted so that SBFD RO is unconditionally set in the RA resource set indicated by msg1 repetition number X.For example, if the base station specifies the initial RO Type of the RA procedure as SBFD RO, or sets an RSRP threshold for selecting the RO type, or sets at least one Msg1 repetition RSRP threshold separately for SBFD RO, the base station configuration may be restricted to setting SBFD RO for all configured RA resource sets.

[0204] If there is no threshold value for determining Msg1 repetition set separately for SBFD RO and non-SBFD RO respectively (e.g., rsrp-ThresholdMsg1-RepetitionNumX, X=1 of 2, 4, 8), and / or if the application of Msg1 repetition and / or the number of applications is the same for SBFD RO and non-SBFD RO, the terminal may not perform 5-50. For example, the terminal may not perform 5-50 if an RO Type change occurs.

[0205] In one embodiment of the present disclosure, the 5-50 operation may be performed only when an RO resource corresponding to the changed RO_TYPE is provided through a higher layer (e.g., RRC). For example, if a specific threshold value (e.g., preambleTransMaxRO-Type) is set, the base station operation may be restricted so that an SBFD RO resource is provided unconditionally.

[0206] Next, the terminal can operate as follows.

[0207] 1> if the Random Access Preamble is transmitted with repetitions and neither contention-free Random Access Resources nor Random Access resources for SI request have been provided for this Random Access procedure:

[0208] 2> if PREAMBLE_TRANSMISSION_COUNTER = [preambleTransMax-Msg1-Repetition] + 1; or

[0209] 2> if PREAMBLE_TRANSMISSION_COUNTER = 2 Х [preambleTransMax-Msg1-Repetition] + 1:

[0210] 3> if set of Random Access resources configured with the same prach-ConfigurationIndex and associated with a higher Msg1 repetition number with the same feature or feature combination as the current set of Random Access resources is available:

[0211] 4> select the set of Random Access resources associated with the next higher Msg1 repetition number with the same feature or feature combination for this Random Access procedure;

[0212] 4> initialize startPreambleForThisPartition, numberOfPreamblesPerSSB-ForThisPartition, numberOfRA-PreamblesGroupA and msg1-RepetitionTimeOffsetROGroup parameters for the Random Access procedure according to the values configured by RRC for the selected set of Random Access resources.

[0213] 1> select a random backoff time according to a uniform distribution between 0 and the PREAMBLE_BACKOFF;

[0214] 1> if the criteria (as defined in clause 5.1.2) to select contention-free Random Access Resources is met during the backoff time:

[0215] 2> perform the Random Access Resource selection procedure (see clause 5.1.2).

[0216] 1> else if the Random Access procedure for an SCell is performed on uplink carrier where pusch-Config is not configured:

[0217] 2> delay the subsequent Random Access transmission until the Random Access Procedure is triggered by a PDCCH order with the same ra-PreambleIndex, ra-ssb-OccasionMaskIndex, and UL / SUL indicator TS 38.212 [9].

[0218] 1> else:

[0219] 2> perform the Random Access Resource selection procedure (see clause 5.1.2) after the backoff time

[0220] In one embodiment of the present disclosure, when RO_TYPE is SBFD RO, the terminal may not perform the following Msg1 repetition number fallback operation. In one embodiment of the present disclosure, only when the current RO_TYPE is non-SBFD RO, the terminal may perform the following Msg1 repetition number fallback operation.

[0221] In one embodiment of the present disclosure, the terminal may perform the following Msg1 repetition number fallback operation before or after performing the RO_TYPE change operation in 5-40 or before or after performing the RA resource set selection in 5-50. In one embodiment of the present disclosure, if the terminal performs the RA resource set selection in 5-50 after the RO_TYPE is changed in 5-40, the terminal may not perform the following Msg1 repetition number fallback operation. For example, the terminal may perform the Msg1 repetition fallback only if an RO (SBFD RO or non-SBFD RO) resource corresponding to the current RO Type is set / provided in the RA resource set re-selected for the Msg1 repetition number fallback.

[0222] Msg1 repetition number fallback operation example 1:

[0223] 1> if the Random Access Preamble is transmitted with repetitions and neither contention-free Random Access Resources nor Random Access resources for SI request have been provided for this Random Access procedure:

[0224] 2> if PREAMBLE_TRANSMISSION_COUNTER = [preambleTransMax-Msg1-Repetition] + 1; or

[0225] 2> if PREAMBLE_TRANSMISSION_COUNTER = 2 Х [preambleTransMax-Msg1-Repetition] + 1:

[0226] 3> if set of Random Access resources configured with the same prach-ConfigurationIndex and associated with a higher Msg1 repetition number with the same feature or feature combination as the current set of Random Access resources is available:

[0227] 4> select the set of Random Access resources associated with the next higher Msg1 repetition number with the same feature or feature combination for this Random Access procedure;

[0228] 4> initialize startPreambleForThisPartition, numberOfPreamblesPerSSB-ForThisPartition, numberOfRA-PreamblesGroupA and msg1-RepetitionTimeOffsetROGroup parameters for the Random Access procedure according to the values configured by RRC for the selected set of Random Access resources.

[0229] Msg1 repetition number fallback 동작 실시예 2:

[0230] 1> if the Random Access Preamble is transmitted with repetitions and neither contention-free Random Access Resources nor Random Access resources for SI request have been provided for this Random Access procedure:

[0231] 2> if PREAMBLE_TRANSMISSION_COUNTER = [preambleTransMax-Msg1-Repetition] + 1; or

[0232] 2> if PREAMBLE_TRANSMISSION_COUNTER = 2 Х [preambleTransMax-Msg1-Repetition] + 1:

[0233] 3> if set of Random Access resources configured with the same prach-ConfigurationIndex and associated with a higher Msg1 repetition number with the same feature or feature combination as the current set of Random Access resources and configured with the RO resource of the current RO type (SBFD RO or non-SBFD RO) is available:

[0234] 4> select the set of Random Access resources associated with the next higher Msg1 repetition number with the same feature or feature combination for this Random Access procedure;

[0235] 4> initialize startPreambleForThisPartition, numberOfPreamblesPerSSB-ForThisPartition, numberOfRA-PreamblesGroupA and msg1-RepetitionTimeOffsetROGroup parameters for the Random Access procedure according to the values ​​configured by RRC for the selected set of Random Access resources.

[0236] In one embodiment of the present disclosure, among the aforementioned RO types, SBFD RO / additional RO may be referred to as second PRACH occasions. For example, among the aforementioned RO types, non-SBFD RO / legacy RO may be referred to as first PRACH occasions. The first PRACH occasion and the second PRACH occasions may be defined as follows.

[0237] first PRACH occasions: each including only symbols that are indicated as uplink or flexible by tdd-UL-DL-ConfigurationCommon and considered as uplink for the random access procedure.

[0238] second PRACH occasions: in RBs that are both in the active UL BWP and in the UL sub-band, and associated either only with SBFD symbols that include at least one SBFD symbol indicated as downlink by tdd-UL-DL-ConfigurationCommon, when the UE is provided either sbfd-RACHSingleConfig or sbfd-RACHDualConfig, or start from an SBFD symbol and end in a non-SBFD symbols when the UE is provided sbfd-RACHDualConfig and sbfd-RACHDualConfig-ValidROAcrossSymbolTypes

[0239] In one embodiment of the present disclosure, for a terminal to perform an RO type change (changing from first PRACH occasions to second PRACH occasions, or from second PRACH occasions to first PRACH occasions), one or more of the following conditions may be simultaneously satisfied.

[0240] Condition 1: The 4-Step CBRA procedure, i.e., the Random Access procedure for contention-free and SI requests, may not be considered.

[0241] Condition 2: The number of preamble transmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER) may be equal to a specific threshold value (e.g., preambleTransMaxRO-Type) + 1 set by the base station to change the RO type.

[0242] Condition 3: For the RO type to be changed, if a feature or feature combination that is the same as the current set is set among the Random Access resources sets configured by the base station, that set can be selected.

[0243] Condition 4: For the RO type to be changed, if there is a set among the Random Access resources sets set by the base station that has the same Msg1 repetition number as the current set, that set can be selected.

[0244] Condition 5: For the RO type to be changed, if there is no set among the Random Access resources sets configured by the base station that has the same Msg1 repetition number as the current set, then if there is a set with a Msg1 repetition number greater than the current set, that set can be selected. If there are multiple sets with a Msg1 repetition number greater than the current set, then the set with the next higher Msg1 repetition number can be selected.

[0245] In one embodiment of the present disclosure, when the RO type is changed, the terminal may also change the Random Access resources set. If the changed Random Access resources set is configured by a RACH-ConfigCommon different from the existing one (for example, if the current or set to be changed is configured via sbfd-RACH-DualConfig), the terminal may perform parameter resetting ((re)initialization) based on the RACH-ConfigCommon corresponding to the newly selected Random Access resources set. For example, the parameter resetting may be performed for all parameters configured by the corresponding RACH-ConfigCommon. For example, the parameter resetting may be performed excluding the following parameters.

[0246] - preambleTransMax (set by RACH-ConfigCommon->RACH-ConfigGeneric): If, when changing the RO type, the number of preamble transmissions (e.g., PREAMBLE TRANSMISSION COUNTER) is already greater than preambleTransMax + 1 to be reset, performing the reset would result in the number of preamble transmissions not becoming equal to preambleTransMax + 1 after the RO type change, and thus a RACH failure could not be triggered. Therefore, the parameter may continue to apply the existing parameter and not be reset to a new value.

[0247] In one embodiment of the present disclosure, a base station may restrict Random Access resources sets with the same feature or feature combination to set the preambleTransMax to the same value for two RO types. This may be intended to ensure that the same preambleTransMax value is applied both before and after switching, even when the preambleTransMax is initialized when performing RO type switching.

[0248] In one embodiment of the present disclosure, the RACH failure condition may be as follows.

[0249] When RAR fails:

[0250] 1> if ra-ResponseWindow configured in RACH-ConfigCommon expires, and if the Random Access Response containing Random Access Preamble identifiers that matches the transmitted PREAMBLE_INDEX has not been received:

[0251] 2> consider the Random Access Response reception not successful;

[0252] 2> increment PREAMBLE_TRANSMISSION_COUNTER by 1;

[0253] 2> if PREAMBLE_TRANSMISSION_COUNTER >= preambleTransMax + 1:

[0254] 3> if the Random Access Preamble is transmitted on the SpCell:

[0255] 4> indicate a Random Access problem to upper layers;

[0256] 4> if this Random Access procedure was triggered for SI request:

[0257] 5> consider the Random Access procedure unsuccessfully completed.

[0258] 3> else if the Random Access Preamble is transmitted on an SCell:

[0259] 4> consider the Random Access procedure unsuccessfully completed.

[0260] Contention resolution 실패 시:

[0261] 1> if the Contention Resolution is considered not successful:

[0262] 2> flush the HARQ buffer used for transmission of the MAC PDU in the Msg3 buffer;

[0263] 2> increment PREAMBLE_TRANSMISSION_COUNTER by 1;

[0264] 2> if PREAMBLE_TRANSMISSION_COUNTER >= preambleTransMax + 1:

[0265] 3> indicate a Random Access problem to upper layers.

[0266] 3> if this Random Access procedure was triggered for SI request:

[0267] 4> consider the Random Access procedure unsuccessfully completed.

[0268] In one embodiment of the present disclosure, a base station may add an RO type indicator to the CFRA settings (e.g., BeamFailureRecoveryConfig, RACH-ConfigDedicated) of an RRCReconfiguration message to instruct a terminal to perform CFRA using the corresponding RO type. For example, the RO type indicator may indicate whether the indicated RO type is legacy RO / non-SBFD RO / first PRACH occasions or additional RO / SBFD RO / second PRACH occasions.

[0269] In one embodiment of the present disclosure, when the RO type indicated for CFRA is SBFD RO / second PRACH occasions, the base station may add an indicator to the RRC configuration / CFRA configuration (e.g., BeamFailureRecoveryConfig, RACH-ConfigDedicated) that indicates the SBFD RACH configuration criteria to be applied when determining valid SBFD RO / second PRACH occasions included in the Random Access resource configured for CFRA (e.g., BeamFailureRecoveryConfig->rach-ConfigBFR (RACH-ConfigGeneric), RACH-ConfigDedicated->cfra->occasions->rach-ConfigGeneric (RACH-ConfigGeneric)).

[0270] For example, when determining valid second PRACH occasions, the criteria can be determined as follows.

[0271] second PRACH occasions: in RBs that are both in the active UL BWP and in the UL sub-band, and associated either only with SBFD symbols that include at least one SBFD symbol indicated as downlink by tdd-UL-DL-ConfigurationCommon, when the UE is provided either sbfd-RACHSingleConfig or sbfd-RACHDualConfig, or start from an SBFD symbol and end in a non-SBFD symbols when the UE is provided sbfd-RACHDualConfig and sbfd-RACHDualConfig-ValidROAcrossSymbolTypes.

[0272] In one embodiment of the present disclosure, when only sbfd-RACHSingleConfig or sbfd-RACHDualConfig is configured (when sbfd-RACHDualConfig-ValidROAcrossSymbolTypes is not configured), the RO may be a valid second PRACH occasion only when it satisfies only with SBFD symbols that include at least one SBFD symbol indicated as downlink by tdd-UL-DL-ConfigurationCommon. For example, when sbfd-RACHDualConfig and sbfd-RACHDualConfig-ValidROAcrossSymbolTypes are configured together, the RO starting from an SBFD symbol and ending in a non-SBFD symbol may also be a valid second PRACH occasion.

[0273] In one embodiment of the present disclosure, a base station may specify a criterion to apply when determining the validity of a second PRACH occasion in a CFRA RACH resource (e.g., BeamFailureRecoveryConfig->rach-ConfigBFR (RACH-ConfigGeneric), RACH-ConfigDedicated->cfra->occasions->rach-ConfigGeneric (RACH-ConfigGeneric))) through an RRC setting. The criterion indicator (existing only when the RO type of the corresponding CFRA is specified as SBFD RO / second PRACH occasions) may be added for the purpose of indicating one or more of the following criteria.

[0274] Case 1: Apply the criteria where both sbfd-RACHDualConfig and sbfd-RACHDualConfig-ValidROAcrossSymbolTypes are set to CFRA.

[0275] Case 2: Apply criteria to CFRA where only sbfd-RACHDualConfig is set (i.e., sbfd-RACHDualConfig-ValidROAcrossSymbolTypes is not set).

[0276] Case 3: Apply the criteria set with sbfd-RACHSingleConfig to CFRA.

[0277] Case 4: Apply the criteria set to CFRA as sbfd-RACHDualConfig (sbfd-RACHDualConfig-ValidROAcrossSymbolTypes is not set) or sbfd-RACHSingleConfig.

[0278] In one embodiment of the present disclosure, the reference indicator may exist only when the base station (e.g., source cell for BFR, target cell for RACH-ConfigDedicated based handover) does not provide an SBFD CBRA setting (e.g., sbfd-RACH-Config included in BWP-UplinkCommon). If an SBFD CBRA setting is provided, the same setting / reference may be applied to CFRA.

[0279] In one embodiment of the present disclosure, the reference indicator may be restricted to be indicated by the same reference when a base station (e.g., BFR is a source cell, RACH-ConfigDedicated based handover is a target cell) provides an SBFD CBRA setting (e.g., sbfd-RACH-Config included in BWP-UplinkCommon).

[0280] In one embodiment of the present disclosure, the terminal may set the transmission power as follows when transmitting a preamble.

[0281] > if the selected PRACH occasion is of the second PRACH occasions (as defined in TS 38.213) and sbfd-RACH-SingleConfig-preambleReceivedTargetPower is configured for the Random Access Procedure:

[0282] >> set PREAMBLE_RECEIVED_TARGET_POWER to sbfd-RACH-SingleConfig-preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP + POWER_OFFSET_2STEP_RA + POWER_OFFSET_RO_TYPE.

[0283] > else if the selected PRACH occasion is of the second PRACH occasions (as defined in TS 38.213) and sbfd-RACH-DualConfig is configured for the Random Access Procedure:

[0284] >> set PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower (included in the sbfd-RACH-DualConfig) + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP + POWER_OFFSET_2STEP_RA + POWER_OFFSET_RO_TYPE.

[0285] > else:

[0286] >> set PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP + POWER_OFFSET_2STEP_RA + POWER_OFFSET_RO_TYPE;

[0287] 상기 POWER_OFFSET_RO_TYPE(변수명은 바뀔 수 있음)은 Random Access 시작 시 0으로 설정된 후, 아래와 같이 설정될 수 있다.

[0288] The power ramping step can be set differently for each RO type. Therefore, when changing the RO type, a power offset is introduced to compensate for the power ramping offset that occurs when the power ramping steps differ for each RO type. This offset is added to the preamble transmission power after the RO type change, thereby reducing abrupt power changes.

[0289] For example, a new terminal variable, POWER_OFFSET_RO_TYPE, can be introduced so that when an RO type change is performed (e.g., when PREAMBLE_TRANSMISSION_COUNTER is equal to preambleTransMaxRO-Type + 1 and the power ramping step is reset while changing the Random Access resources set), the power offset can be stored in the corresponding variable as follows.

[0290] set POWER_OFFSET_RO_TYPE to (PREAMBLE_POWER_RAMPING_COUNTER - 1) × (PREAMBLE_POWER_RAMPING_STEP_RO_TYPE_BEFORE - PREAMBLE_POWER_RAMPING_STEP_RO_TYPE_AFTER).

[0291] The above PREAMBLE_POWER_RAMPING_STEP_RO_TYPE_BEFORE (variable name may change) refers to the preamble power ramping step set in the corresponding Random Access resources set before the RO type change, and PREAMBLE_POWER_RAMPING_STEP_RO_TYPE_AFTER (variable name may change) refers to the preamble power ramping step set in the changed Random Access resources set after the RO type change.

[0292] For example, if RACH-ConfigCommon is not changed when the RO type is changed (e.g., if sbfd-RACHSingleConfig is set), and / or if the preamble power ramping step setting value is not changed, the power offset compensation may not be performed.

[0293] In one embodiment of the present disclosure, the power offset compensation may also be applied to an operation of notifying a lower layer of preamble transmission power.

[0294] > if the received UL grant indicates that the corresponding PUSCH transmission is in SBFD symbols as specified in clause 11.1 of TS 38.213:

[0295] >> if sbfd-RACH-SingleConfig (see TS 38.331) is configured for the Random Access procedure:

[0296] >>> indicate the sbfd-RACH-SingleConfig-preambleReceivedTargetPower if configured, or the preambleReceivedTargetPower otherwise, and the amount of power ramping applied to the latest Random Access Preamble transmission to lower layers (ie (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP + POWER_OFFSET_2STEP_RA + POWER_OFFSET_RO_TYPE).

[0297] >> else if sbfd-RACH-DualConfig (see TS 38.331) is configured for the Random Access procedure:

[0298] >>> indicate the preambleReceivedTargetPower included in the sbfd-RACH-DualConfig, and the amount of power ramping applied to the latest Random Access Preamble transmission to lower layers (i.e. (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP + POWER_OFFSET_2STEP_RA + POWER_OFFSET_RO_TYPE).

[0299] >> else:

[0300] >>> indicate the preambleReceivedTargetPower and the amount of power ramping applied to the latest Random Access Preamble transmission to lower layers (i.e. (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP + POWER_OFFSET_2STEP_RA + POWER_OFFSET_RO_TYPE).

[0301] > else (i.e., the received UL grant indicates that the corresponding PUSCH transmission is in non-SBFD symbols as specified in clause 11.1 of TS 38.213):

[0302] >> indicate the preambleReceivedTargetPower and the amount of power ramping applied to the latest Random Access Preamble transmission to lower layers (i.e. (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP + POWER_OFFSET_2STEP_RA + POWER_OFFSET_RO_TYPE);

[0303] 본 개시의 일 실시예로, 단말은 preamble 전송 시, 송신 power를 아래와 같이 power offset compensation 없이 설정할 수 있다.

[0304] > if the selected PRACH occasion is of the second PRACH occasions (as defined in TS 38.213) and sbfd-RACH-SingleConfig-preambleReceivedTargetPower is configured for the Random Access Procedure:

[0305] >> set PREAMBLE_RECEIVED_TARGET_POWER to sbfd-RACH-SingleConfig-preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP.

[0306] > else if the selected PRACH occasion is of the second PRACH occasions (as defined in TS 38.213) and sbfd-RACH-DualConfig is configured for the Random Access Procedure:

[0307] >> set PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower (included in the sbfd-RACH-DualConfig) + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP.

[0308] > else:

[0309] >> set PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP + POWER_OFFSET_2STEP_RA;

[0310] 본 개시의 일 실시예로, 하위 계층에 preamble 전송 power를 통보 시, 아래와 같이 power offset compensation을 SBFD symbol에 적용하지 않을 수 있다.

[0311] > if the received UL grant indicates that the corresponding PUSCH transmission is in SBFD symbols as specified in clause 11.1 of TS 38.213:

[0312] >> if sbfd-RACH-SingleConfig (see TS 38.331) is configured for the Random Access procedure:

[0313] >>> indicate the sbfd-RACH-SingleConfig-preambleReceivedTargetPower if configured, or the preambleReceivedTargetPower otherwise, and the amount of power ramping applied to the latest Random Access Preamble transmission to lower layers (i.e. (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP).

[0314] >> else if sbfd-RACH-DualConfig (see TS 38.331) is configured for the Random Access procedure:

[0315] >>> indicate the preambleReceivedTargetPower included in the sbfd-RACH-DualConfig, and the amount of power ramping applied to the latest Random Access Preamble transmission to lower layers (i.e. (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP).

[0316] >> else:

[0317] >>> indicate the preambleReceivedTargetPower and the amount of power ramping applied to the latest Random Access Preamble transmission to lower layers (i.e. (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP).

[0318] > else (i.e., the received UL grant indicates that the corresponding PUSCH transmission is in non-SBFD symbols as specified in clause 11.1 of TS 38.213):

[0319] >> indicate the preambleReceivedTargetPower and the amount of power ramping applied to the latest Random Access Preamble transmission to lower layers (i.e. (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP + POWER_OFFSET_2STEP_RA);

[0320] 도 7은 본 개시의 일 실시예에 따른 단말의 구조를 도시하는 블록도이다.

[0321] The terminal (100) is an electronic device capable of wireless communication and may have various form factors. Examples of the terminal may include at least one of a user device (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, a tablet, a wearable device, an Internet of Things (IoT) device, or other devices / systems capable of performing wireless communication with a base station (BS) and / or other terminals via a wireless channel.

[0322] Referring to FIG. 7, the terminal (100) may include at least one communication unit (7-30) (hereinafter, communication unit), at least one processor (7-20) (hereinafter, processor), and at least one memory (7-10) (hereinafter, memory). The communication unit (7-30), processor (7-20), and memory (7-10) of the terminal (100) may be operated according to at least one or a combination thereof of the methods corresponding to the embodiments of the present disclosure. However, the components of the terminal (100) are not limited to the examples of components shown in FIG. 7. In other embodiments, the terminal (100) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in some embodiments, any combination of the communication unit (7-30), processor (7-20), or memory (7-10) may be integrated into a single component.

[0323] The communication unit (7-30) may be a basic communication circuit or communication circuitry that enables the terminal (100) to perform wireless communication with a node or entity of a network. For example, the communication unit (7-30) may enable the terminal (100) to transmit and receive signals to and from a base station via cellular wireless communication, or to transmit and receive signals to and from another terminal via cellular wireless communication. For example, the communication unit (7-30) may support at least one of various cellular wireless communication technologies including 3G (3rd generation), 4G (4th generation) LTE (long-term evolution), 5G (5th generation) NR (new radio), 6G (6th generation), etc., and the various cellular wireless communication technologies supported by the communication unit (7-30) may include all subsequent evolved generations of wireless communication.

[0324] According to one embodiment, the terminal (100) may include a plurality of communication units, and for example, when supporting EN-DC (E-UTRA (evolved-universal terrestrial radio access) - NR dual connectivity), it may include a first communication unit that supports 4G LTE wireless communication and a second communication unit that supports 5G NR wireless communication. According to another embodiment, when the terminal (100) supports NR-DC (NR Dual Connectivity), the terminal (100) may include a plurality of communication units that support 5G NR wireless communication. According to another embodiment, when the terminal (100) supports short-range wireless communication, the terminal (100) may separately include a communication unit that supports at least one of a group of wireless communication protocol standards such as Bluetooth®, wireless LAN or WLAN (wireless local area network) network (including, but not limited to, IEEE (institute of electrical and electronics engineer) 802.11-2016 standard or modifications thereof such as 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba and 802.11be).

[0325] According to one embodiment, the communication unit (7-30) may include various circuit structures used to transmit and receive signals through a base station and a wireless channel. The signals may include control information and data. For example, the communication unit (7-30) may be configured to include an RF (radio frequency) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The communication unit (7-30) may output the signal received through the wireless channel to a processor (7-20) and transmit the signal output from the processor (7-20) through the wireless channel.

[0326] A processor (7-20) can control the overall operation of a terminal (100) according to an embodiment of the present disclosure. The processor (7-20) may be implemented as one or more IC (integrated circuit (or circuitry)) chips and may execute various data processing operations. The processor (7-20) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (7-10) individually, collectively, or in any combination. Additionally, the processor (7-20) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.

[0327] The processor (7-20) is electrically, operatively, and / or communicatively coupled to the communication unit (7-30) so as to control the communication unit (7-30).

[0328] The processor (7-20) may include at least one processor (or processing circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. For example, the processor (7-20) may include a communication processor (CP) that controls communication operations and an application processor (AP) that controls the execution of an upper layer (e.g., an application layer). In a specific embodiment, at least one part of the processor (7-20) may be included in one chip (or IC), and another part of the processor (7-20) may be included in a separate chip (or IC). Alternatively, at least one processor may be included in other components, such as a communication unit (7-30) or a memory (7-10).

[0329] The processor (7-20) may perform, cause, or control the operation of a terminal to perform at least one or a combination thereof of the methods according to the embodiments of the present disclosure. For example, the processor (7-20) may control the operation of a terminal to process a downlink signal received from a base station or to generate an uplink signal and transmit it to a base station. To this end, the processor (7-20) may control other components of the terminal (100) to perform various operations by executing computer programs, code, or instructions stored in memory (7-10).

[0330] Memory (7-10) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (7-10) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0331] The memory (7-10) can be electrically, operatively, and / or communicatively coupled to the processor (7-20) and can be accessed by the processor (7-20).

[0332] A computer program, code, or instruction that can be executed by a processor (7-20) may be stored in the memory (7-10). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (7-20) may be stored in a single memory device or may be separated and distributed across two or more memory devices. The processor (7-20) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (7-10).

[0333] According to one embodiment of the present disclosure, the operation of the terminal (100) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer programs or code) stored in memory (7-10), based on processing circuitry not configured to execute instructions, and / or based on components of a processing circuitry not configured to execute instructions. FIG. 8 is a block diagram illustrating the structure of an NR base station (200) according to one embodiment of the present disclosure.

[0334] The base station (200) can perform wireless communication with at least one terminal within the area of ​​the base station (200) via a wireless channel. The base station (200) can perform communication with a node or entity of the network via wired or wireless communication.

[0335] Referring to FIG. 8, a base station (200) may include at least one communication unit (8-30) (hereinafter, communication unit), at least one processor (8-20) (hereinafter, processor), and at least one memory (8-10) (hereinafter, memory). According to at least one or a combination thereof of methods corresponding to embodiments of the present disclosure, the communication unit (8-30), processor (8-20), and memory (8-10) of the base station (200) may be operated. However, the components of the base station (200) are not limited to the examples of components shown in FIG. 8. In other embodiments, the base station (200) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in some embodiments, any combination of the communication unit (8-30), processor (8-20), or memory (8-10) may be integrated into a single component.

[0336] The communication unit (8-30) may be a communication circuit or communication circuitry that enables the base station (200) to perform wireless communication with a node or entity of the network. For example, the communication unit (8-30) may enable the base station (200) to transmit and receive signals to and from a terminal (100) via cellular wireless communication or to transmit and receive signals to and from another network entity via wireless communication. For example, the communication unit (8-30) may support various cellular wireless communication technologies including 3G (3rd generation), 4G (4th generation) LTE (long-term evolution), 5G (5th generation) NR (new radio), 6G (6th generation), etc., and the various cellular wireless communication technologies supported by the communication unit (8-30) may include all subsequent generations of wireless communication. According to one embodiment, the communication unit (8-30) may include various circuit structures used to transmit and receive signals to and from a terminal via a wireless channel. The above signal may include control information and data. For example, the communication unit (8-30) may be configured to include an RF (radio frequency) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The communication unit (8-30) may output the signal received through a wireless channel to a processor (8-20) and transmit the signal output from the processor (8-20) through a wireless channel.

[0337] Meanwhile, according to one embodiment of the present disclosure, a base station (200) may communicate with an entity or node of a network via wired or wireless communication. For example, the base station (200) may communicate via wired or wireless communication with an entity or node of an adjacent base station or core network via a backhaul network. Although not shown in the drawings, when the base station (200) performs wired communication, the base station (200) may include a separate network interface for wired communication in addition to the communication unit (8-30). The network interface may be referred to as network interface circuitry, communication interface circuitry, etc.

[0338] A processor (8-20) can control the overall operation of a base station (200) according to an embodiment of the present disclosure. The processor (8-20) may be implemented as one or more IC (integrated circuit or circuitry) chips and may execute various data processing operations. The processor (8-20) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (8-10) individually, collectively, or in any combination. Additionally, the processor (8-20) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.

[0339] The processor (8-20) is electrically, operatively, and / or communicatively coupled to the communication unit (8-30) so as to control the communication unit (8-30).

[0340] The processor (8-20) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. In a specific embodiment, at least one part of the processor (8-20) may be included in one chip (or IC), and another part of the processor (8-20) may be included in a separate chip (or IC). Alternatively, at least one processor may be included in other components, such as a communication unit (8-30) or a memory (8-10).

[0341] The processor (8-20) may perform, cause, or control the operation of a base station to execute at least one or a combination of methods according to embodiments of the present disclosure. For example, the processor (8-20) may control the operation of a base station to generate a downlink signal and transmit it to a terminal, or to process an uplink signal received from a terminal. Alternatively, the base station may transmit and receive signals with an adjacent base station, transmit a signal received from a terminal to an upper node of the network, or receive a signal from an upper node of the network and transmit it to a terminal. To this end, the processor (8-20) may control other components of the base station (200) to perform various operations by executing computer programs, codes, and instructions stored in memory (8-10).

[0342] Memory (8-10) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (8-10) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semi-permanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0343] The memory (8-10) can be electrically, operatively, and / or communicatively coupled to the processor (8-20) and can be accessed by the processor (8-20).

[0344] A computer program, code, or instruction that can be executed by a processor (8-20) may be stored in the memory (8-10). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (8-20) may be stored in a single memory device or may be separated and distributed among two or more memory devices. The processor (8-20) may perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (8-10).

[0345] According to one embodiment of the present disclosure, the operation of a base station (200) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer programs or code) stored in memory (8-10), based on a processing circuitry not configured to execute instructions, and / or based on a component of a processing circuitry not configured to execute instructions. According to one embodiment of the present disclosure, a method for a terminal to perform communication in a wireless communication system comprises the steps of receiving resources for performing a random access procedure from a base station, setting a first random occasion type for performing a random access procedure, transmitting a preamble based on the first random occasion type, changing the first random occasion type to a second random occasion type when the reception of a random access response corresponding to the preamble is unsuccessful and a preset condition is satisfied, and the second random Based on a change to an occupancy type, the method may include a step of changing resources for performing a random access procedure. The first random occupancy type may include a subband full duplex (SBFD) type or a non-SBFD type, and the second random occupancy type may include a non-SBFD type or an SBFD type.

[0346] In one embodiment, the random access procedure is a four-step non-contention-based random access procedure, and the random access procedure may include a beam failure recovery procedure or a handover procedure.

[0347] In one embodiment, the resource for performing the random access procedure may be set via an RRC (radio resource control) message or a SIB1 (system information block) message.

[0348] In one embodiment, the preset condition may include a condition regarding a counter for preamble transmission. The method may include the step of changing the preset random occupation type when the value obtained by increasing the counter for preamble transmission by 1 is equal to the value obtained by adding 1 to a threshold value regarding the change of the random occupation type.

[0349] In one embodiment, the method may include the step of changing to a resource set for a second random occupation type having the same feature as the resource set set for a first random occupation type, to a resource set having the same number of times as the number of repeated transmissions of the preamble.

[0350] In one embodiment, the method may include the step of changing to a resource set having the next largest number of repeated transmissions if there is no resource set having the same number of repeated transmissions as the preamble.

[0351] In one embodiment, the method may include the step of initializing parameters for a random access procedure based on resources for performing a modified random access procedure.

[0352] In one embodiment, the method may include the step of changing parameters regarding transmission power for preamble transmission.

[0353] According to one embodiment of the present disclosure, a terminal performing communication in a wireless communication system may include a memory storing a plurality of instructions and at least one processor that executes a plurality of instructions stored in the memory. The terminal may receive resources for performing a random access procedure from a base station by individually or collectively executing a plurality of instructions by at least one processor, set a first random occasion type for performing a random access procedure, transmit a preamble based on the first random occasion type, and if it fails to receive a random access response corresponding to the preamble and a preset condition is satisfied, change the first random occasion type to a second random occasion type and change resources for performing a random access procedure based on the change to the second random occasion type. The first random occasion type may include a subband full duplex (SBFD) type or a non-SBFD type, and the second random occasion type may include a non-SBFD type or an SBFD type.

[0354] A device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory storage medium' simply means that it is a tangible device and does not contain a signal (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily. For example, a 'non-transitory storage medium' may include a buffer in which data is stored temporarily.

[0355] According to one embodiment, the method according to the various embodiments disclosed herein may be provided by being included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or distributed online (e.g., download or upload) through an application store or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product (e.g., downloadable app) may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

[0356] A device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory storage medium' simply means that it is a tangible device and does not contain a signal (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily. For example, a 'non-transitory storage medium' may include a buffer in which data is stored temporarily.

[0357] According to one embodiment, the method according to the various embodiments disclosed herein may be provided by being included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or distributed online (e.g., download or upload) through an application store or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product (e.g., downloadable app) may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

Claims

1. In a method for a terminal to perform communication in a wireless communication system, A step of receiving resources from a base station for performing a random access procedure; A step of setting a first random occasion type for performing the above random access procedure; A step of transmitting a preamble based on the first random occupation type; If the reception of a random access response (RAR) corresponding to the above preamble is unsuccessful and a preset condition is satisfied, the step of changing the first random occupation type to a second random occupation type; and Based on the change to the second random occupation type, the method includes the step of changing the resources for performing the random access procedure; A method in which the first random occupation type includes a subband full duplex (SBFD) type or a non-SBFD type, and the second random occupation type includes the non-SBFD type or the SBFD type.

2. In Paragraph 1, The above random access procedure is a four-step non-competition-based random access procedure, and The above random access procedure is a method comprising a beam failure recovery procedure or a handover procedure.

3. In Paragraph 1, A method in which a resource for performing the above random access procedure is established via an RRC (radio resource control) message or a SIB1 (system information block) message.

4. In claim 1, the previously set condition is, Includes conditions regarding a counter for the above-mentioned preamble transmission, and The step of changing the random occupation type set above is, A method comprising the step of changing the set random occupation type when the value obtained by increasing the counter for the preamble transmission by 1 is equal to the value obtained by adding 1 to the threshold for changing the random occupation type.

5. In Paragraph 1, The step of changing resources for performing the above random access procedure is, A method comprising the step of changing a resource set for a second random occupation type, which has the same feature as the resource set set for the first random occupation type, to a resource set having the same number of times as the number of repeated transmissions of the preamble.

6. In Paragraph 5, If there is no resource set having the same number of times as the number of repeated transmissions of the above preamble, A method comprising the step of changing to a resource set having the next largest number of repeated transmissions.

7. In Paragraph 1, A method comprising the step of initializing parameters for the random access procedure based on resources for performing the modified random access procedure.

8. In Paragraph 1, The step of changing resources for performing the above random access procedure is, A method comprising the step of changing parameters regarding transmission power for the above-mentioned preamble transmission.

9. In a terminal that performs communication in a wireless communication system, Memory for storing multiple instructions; and It includes at least one processor that executes the plurality of instructions stored in the memory, By executing the above plurality of instructions individually or collectively by the at least one processor, the terminal, Receive resources from the base station for performing a random access procedure, and Set a first random occasion type for performing the above random access procedure, and Transmit a preamble based on the above first random occupation type, and If the reception of a random access response (RAR) corresponding to the above preamble is unsuccessful and a preset condition is satisfied, the above first random occupation type is changed to a second random occupation type, and Based on the change to the above second random occupation type, the resources for performing the above random access procedure are changed, and A terminal in which the first random occupancy type includes a subband full duplex (SBFD) type or a non-SBFD type, and the second random occupancy type includes the non-SBFD type or the SBFD type.

10. In Paragraph 9, The above random access procedure is a four-step non-competition-based random access procedure, and The above random access procedure is a terminal that includes a beam failure recovery procedure or a handover procedure.

11. In Paragraph 9, A terminal for performing the above random access procedure, the resource is configured via an RRC (radio resource control) message or a SIB1 (system information block) message.

12. In Paragraph 9, By executing the above plurality of instructions individually or collectively by the at least one processor, the terminal, A terminal that changes the set random occupancy type when the value obtained by increasing the counter for preamble transmission by 1 is equal to the value obtained by adding 1 to the threshold for changing the random occupancy type.

13. In Paragraph 9, By executing the above plurality of instructions individually or collectively by the at least one processor, the terminal, Among the resource sets for the second random occupation type having the same feature as the resource set set for the first random occupation type, change to a resource set having the same number as the number of repeated transmissions of the preamble. A terminal that, if there is no resource set having the same number of repeated transmissions as the above preamble, changes to a resource set having the next largest number of repeated transmissions.

14. In Paragraph 9, By executing the above plurality of instructions individually or collectively by the at least one processor, the terminal, A terminal that initializes parameters for the random access procedure based on resources for performing the above-mentioned modified random access procedure.

15. In Paragraph 9, By executing the above plurality of instructions individually or collectively by the at least one processor, the terminal, A terminal that changes parameters regarding transmission power for the above-mentioned preamble transmission.

Images