Method and device for performing pdcch order-based random access in sbfd environment

The method clarifies PDCCH order-based random access in SBFD by determining whether to continue or perform a second CFRA procedure, addressing ambiguity and reducing delays in SBFD environments.

WO2026235426A1PCT designated stage Publication Date: 2026-11-12HYUNDAI MOTOR CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/096162
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-07
Filing Date
2026-04-22
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In subband full duplex (SBFD) environments, existing methods for performing random access based on physical downlink control channel (PDCCH) orders are ambiguous, leading to potential delays and inefficiencies in contention-free random access (CFRA) procedures due to unclear instructions for additional random access channel (RACH) occasions.

Method used

A method and apparatus for performing random access based on PDCCH orders in SBFD environments, where a terminal or base station receives multiple PDCCH orders and determines whether to continue or perform a second CFRA procedure based on specific information, such as RACH occasion type or RA procedure similarity, indicated by DCI fields, reserved bits, or RNTI, to clarify the random access process.

Benefits of technology

Resolves ambiguity in random access procedures, reducing delays by allowing terminals to correctly determine when to perform Msg1 transmission at additional RACH occasions and enabling smooth execution of CFRA, thereby optimizing the random access process in SBFD operations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026096162_12112026_PF_FP_ABST
    Figure KR2026096162_12112026_PF_FP_ABST
Patent Text Reader

Abstract

This method of a terminal may comprise the steps of: receiving a first PDCCH order indicating a first CFRA procedure from a base station; receiving a second PDCCH order indicating a second CFRA procedure from the base station while performing the first CFRA procedure; and determining, on the basis of first information indicated by the second PDCCH order, whether to continue the first CFRA procedure instead of performing the second CFRA procedure or to perform the second CFRA procedure, wherein the first information is information indicating an RO type for the second CFRA procedure or information indicating whether the second CFRA procedure is the same RA procedure as the first CFRA procedure.
Need to check novelty before this filing date? Find Prior Art

Description

Method and apparatus for performing PDCCH order-based random access in an SBFD environment

[0001] The present disclosure relates to random access technology of a mobile communication system, and more specifically, to a method and apparatus for performing random access based on a physical downlink control channel (PDCCH) order in an environment where a subband full duplex (SBFD) operation is performed.

[0002] Communication networks (e.g., 5G communication networks, 6G communication networks, etc.) are being developed to provide communication services that are improved over existing communication networks (e.g., LTE (long term evolution), LTE-A (advanced), etc.). 5G communication networks (e.g., NR (new radio) communication networks) can support frequency bands above 6 GHz as well as frequency bands below 6 GHz. That is, 5G communication networks can support the FR1 band and / or FR2 band. 5G communication networks can support a wider variety of communication services and scenarios compared to LTE communication networks. For example, usage scenarios for 5G communication networks may include eMBB (enhanced Mobile BroadBand), URLLC (Ultra Reliable Low Latency Communication), mMTC (massive Machine Type Communication), etc.

[0003] 6G communication networks can support a wider variety of communication services and scenarios compared to 5G communication networks. 6G communication networks can meet the requirements for ultra-high performance, ultra-bandwidth, ultra-spatial, ultra-precision, ultra-intelligence, and / or ultra-reliability. 6G communication networks can support a wide range of frequency bands and can be applied to various usage scenarios (e.g., terrestrial communication, non-terrestrial communication, sidelink communication, etc.).

[0004] Meanwhile, as part of the enhancement of the TDD system, 3GPP is proceeding with the standardization of subband full duplex (SBFD) technology, which allows a base station to simultaneously perform downlink (DL) signal transmission and uplink (UL) signal reception using non-overlapping resources in the frequency domain within the TDD band.

[0005] Additional RACH (random access channel) occupations (ROs) for terminals supporting SBFD operation may be configured in SBFD symbols for which subbands for SBFD operation are configured. In this case, if a PDCCH (physical downlink control channel) order-based CFRA (contention-free random access) procedure or CBRA (contention-based random access) procedure is instructed to a terminal supporting SBFD operation, a method for the terminal to perform the CFRA procedure or CBRA procedure needs to be additionally defined.

[0006] The objective of the present disclosure to solve the above-mentioned problems is to provide a method and apparatus for performing random access based on the order of the physical downlink control channel (PDCCH) in an environment where subband full duplex (SBFD) operation is performed.

[0007] A method of a terminal according to embodiments of the present disclosure for achieving the above objective comprises: receiving a first PDCCH order from a base station instructing a first CFRA (contention-free random access) procedure; receiving a second PDCCH order from the base station instructing a second CFRA procedure while performing the first CFRA procedure; and determining whether to continue the first CFRA procedure without performing the second CFRA procedure or to perform the second CFRA procedure based on first information instructed by the second PDCCH order, wherein the first information may be information instructing a RACH (random access channel) occasion type (RO type) for the second CFRA procedure or information instructing whether the second CFRA procedure is the same RA procedure as the first CFRA procedure.

[0008] The first information above may be indicated by a field included in the DCI (downlink control information) of the PDCCH order, by a reserved bit(s) included in the DCI, or by a radio network temporary identifier (RNTI) scrambled by the CRC (cyclic redundancy check) of the DCI.

[0009] The above terminal is an SBFD UE (user equipment) that supports SBFD (subband full duplexing), and the above RO type may be a legacy RO or an additional RO.

[0010] If the first information is information indicating a second RO type for the second CFRA procedure, and the first PDCCH order and the second PDCCH order indicate the same preamble index and / or the same PRACH (physical random access channel) mask index, and the second RO type is the same as the first RO type for the first CFRA procedure, the terminal may continue the first CFRA procedure without performing the second CFRA procedure.

[0011] The above first information is information indicating a second RO type for the above second CFRA procedure, and the first PDCCH order and the second PDCCH order indicate the same preamble index and / or PRACH mask index, and if the above second RO type is different from the first RO type for the above first CFRA procedure, the terminal can perform the above second CFRA procedure.

[0012] The first information is information indicating whether the second CFRA procedure is the same RA procedure as the first CFRA procedure, and if the first information indicates that the second CFRA procedure is the same RA procedure as the first CFRA procedure, the terminal may continue the first CFRA procedure without performing the second CFRA procedure.

[0013] The first information is information indicating whether the second CFRA procedure is the same RA procedure as the first CFRA procedure, and if the first information indicates that the second CFRA procedure is a different RA procedure from the first CFRA procedure, the terminal can perform the second CFRA procedure.

[0014] A method of a base station according to embodiments of the present disclosure for achieving the above objective comprises: transmitting a first PDCCH order instructing a terminal to perform a first CFRA (contention-free random access) procedure; transmitting a second PDCCH order instructing the terminal to perform a second CFRA procedure while performing the first CFRA procedure with the terminal; and, based on first information instructed by the second PDCCH order, continuously performing the first CFRA procedure without performing the second CFRA procedure with the terminal or performing the second CFRA procedure, wherein the first information may be information instructing a RACH (random access channel) occasion type (RO type) for the second CFRA procedure or information instructing whether the second CFRA procedure is the same RA procedure as the first CFRA procedure.

[0015] The first information above may be indicated by a field included in the DCI (downlink control information) of the PDCCH order, by a reserved bit(s) included in the DCI, or by a radio network temporary identifier (RNTI) scrambled by the CRC (cyclic redundancy check) of the DCI.

[0016] The above terminal is an SBFD UE (user equipment) that supports SBFD (subband full duplexing), and the above RO type may be a legacy RO or an additional RO.

[0017] If the first information is information indicating a second RO type for the second CFRA procedure, and the first PDCCH order and the second PDCCH order indicate the same preamble index and / or the same PRACH (physical random access channel) mask index, and the second RO type is the same as the first RO type for the first CFRA procedure, the base station may continue the first CFRA procedure without performing the second CFRA procedure with the terminal.

[0018] If the first information is information indicating a second RO type for the second CFRA procedure, and the first PDCCH order and the second PDCCH order indicate the same preamble index and / or PRACH mask index, and the second RO type is different from the first RO type for the first CFRA procedure, the base station can perform the second CFRA procedure with the terminal.

[0019] The first information is information indicating whether the second CFRA procedure is the same RA procedure as the first CFRA procedure, and if the first information indicates that the second CFRA procedure is the same RA procedure as the first CFRA procedure, the base station may continue the first CFRA procedure without performing the second CFRA procedure with the terminal.

[0020] The first information is information indicating whether the second CFRA procedure is the same RA procedure as the first CFRA procedure, and if the first information indicates that the second CFRA procedure is a different RA procedure from the first CFRA procedure, the base station can perform the second CFRA procedure with the terminal.

[0021] A terminal according to embodiments of the present disclosure for achieving the above objective comprises at least one processor, and the at least one processor enables the terminal to perform: receiving a first PDCCH order from a base station instructing a first CFRA (contention-free random access) procedure; receiving a second PDCCH order from the base station instructing a second CFRA procedure while performing the first CFRA procedure; and determining whether to continue the first CFRA procedure without performing the second CFRA procedure or to perform the second CFRA procedure based on first information instructed by the second PDCCH order, wherein the first information may be information instructing a RACH (random access channel) occasion type (RO type) for the second CFRA procedure or information instructing whether the second CFRA procedure is the same RA procedure as the first CFRA procedure.

[0022] The above terminal is an SBFD UE (user equipment) that supports SBFD (subband full duplexing), and the above RO type may be a legacy RO or an additional RO.

[0023] If the first information is information indicating a second RO type for the second CFRA procedure, and the first PDCCH order and the second PDCCH order indicate the same preamble index and / or the same PRACH (physical random access channel) mask index, and the second RO type is the same as the first RO type for the first CFRA procedure, the at least one processor may cause the terminal to continue the first CFRA procedure without performing the second CFRA procedure.

[0024] If the first information is information indicating a second RO type for the second CFRA procedure, and the first PDCCH order and the second PDCCH order indicate the same preamble index and / or PRACH mask index, and the second RO type is different from the first RO type for the first CFRA procedure, the at least one processor may cause the terminal to perform the second CFRA procedure.

[0025] The first information is information indicating whether the second CFRA procedure is the same RA procedure as the first CFRA procedure, and if the first information indicates that the second CFRA procedure is the same RA procedure as the first CFRA procedure, the at least one processor may cause the terminal to continue the first CFRA procedure without performing the second CFRA procedure.

[0026] The first information is information indicating whether the second CFRA procedure is the same RA procedure as the first CFRA procedure, and if the first information indicates that the second CFRA procedure is a different RA procedure from the first CFRA procedure, the at least one processor may cause the terminal to perform the second CFRA procedure.

[0027] According to embodiments of the present disclosure, when an SBFD UE receives a new PDDCH order while performing an RA procedure based on a previous PDCCH order, the problem of continuing to perform the RA procedure based on the previous PDCCH order without performing Msg1 transmission at an additional RO, even though Msg1 transmission could be performed at an additional RO, can be resolved. Accordingly, the base station can reduce the delay of the RA procedure by transmitting a new PDCCH order as needed. In addition, smooth execution of the RA procedure can be achieved by resolving the ambiguity of the type of RO to which the preamble is to be transmitted when performing a CBRA procedure or a CFRA procedure based on a PDCCH order.

[0028] FIG. 1 is a conceptual diagram illustrating a first embodiment of a communication system.

[0029] FIG. 2 is a block diagram illustrating a first embodiment of a communication node constituting a communication system.

[0030] FIG. 3 is a block diagram illustrating a first embodiment of communication nodes performing communication.

[0031] FIG. 4a is a block diagram illustrating a first embodiment of a transmission path.

[0032] FIG. 4b is a block diagram illustrating a first embodiment of a receiving path.

[0033] FIG. 5 is a conceptual diagram illustrating a first embodiment of a system frame in a communication system.

[0034] FIG. 6 is a conceptual diagram illustrating a first embodiment of a subframe in a communication system.

[0035] FIG. 7 is a conceptual diagram illustrating a first embodiment of a slot in a communication system.

[0036] FIG. 8 is a conceptual diagram illustrating a first embodiment of a time-frequency resource in a communication system.

[0037] Figure 9 is a conceptual diagram illustrating potential problems that may occur in a CFRA triggered by a PDCCH order.

[0038] FIG. 10 is a flowchart illustrating a method for performing a PDCCH order-based RA procedure according to the present disclosure.

[0039] FIGS. 11a to 11c are conceptual diagrams for explaining methods of performing Msg1 transmission when CBRA is indicated by a PDCCH order.

[0040] The present disclosure is capable of various modifications and may have various embodiments, and specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the present disclosure to specific embodiments, and it should be understood that it includes all modifications, equivalents, and substitutions that fall within the spirit and scope of the present disclosure.

[0041] Terms such as "first," "second," etc., may be used to describe various components, but said components should not be limited by said terms. Such terms are used solely for the purpose of distinguishing one component from another. For example, without departing from the scope of the present disclosure, the first component may be named the second component, and similarly, the second component may be named the first component. The term "and / or" may mean a combination of a plurality of related described items or any of a plurality of related described items.

[0042] In the present disclosure, "at least one of A and B" may mean "at least one of A or B" or "at least one of one or more combinations of A and B". Additionally, in the present disclosure, "at least one of A and B" may mean "at least one of A or B" or "at least one of one or more combinations of A and B".

[0043] In the present disclosure, (re)transmission may mean "transmission," "retransmission," or "transmission and retransmission"; (re)setting may mean "setting," "resetting," or "setting and resetting"; (re)connection may mean "connection," "reconnection," or "connection and reconnection"; and (re)connection may mean "connection," "reconnection," or "connection and reconnection".

[0044] When it is stated that one component is "connected" or "connected" to another component, it should be understood that while it may be directly connected or connected to that other component, there may also be other components in between. On the other hand, when it is stated that one component is "directly connected" or "directly connected" to another component, it should be understood that there are no other components in between.

[0045] The terms used in this disclosure are used merely to describe specific embodiments and are not intended to limit this disclosure. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this disclosure, terms such as “comprising” or “having” are intended to specify the existence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0046] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which this disclosure pertains. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and should not be interpreted in an ideal or overly formal sense unless explicitly defined in this disclosure.

[0047] Hereinafter, preferred embodiments of the present disclosure will be described in more detail with reference to the attached drawings. To facilitate overall understanding in describing the present disclosure, the same reference numerals are used for identical components in the drawings, and redundant descriptions of identical components are omitted. Operations according to combinations of embodiments, extensions of embodiments, and / or modifications of embodiments may be performed, as well as the embodiments explicitly described in the present disclosure. The performance of some operations may be omitted, and the order of operations may be changed.

[0048] In the embodiments, even when a method performed at a first communication node among the communication nodes (e.g., transmission or reception of a signal) is described, the corresponding second communication node may perform a method corresponding to the method performed at the first communication node (e.g., reception or transmission of a signal). That is, when the operation of a UE (user equipment) is described, the corresponding base station may perform an operation corresponding to the operation of the UE. Conversely, when the operation of a base station is described, the corresponding UE may perform an operation corresponding to the operation of the base station.

[0049] A base station may be referred to as Node B, evolved Node B, gNode B (next generation node B), gNB, device, apparatus, node, communication node, BTS (base transceiver station), RRH (radio remote head), TRP (transmission reception point), RU (radio unit), RSU (road side unit), radio transceiver, access point, access node, etc. A UE may be referred to as terminal, device, apparatus, node, communication node, end node, access terminal, mobile terminal, station, subscriber station, mobile station, portable subscriber station, OBU (on-broad unit), etc.

[0050] In the present disclosure, signaling may be at least one of upper-layer signaling, MAC signaling, or PHY (physical) signaling. A message used for upper-layer signaling may be referred to as an "upper-layer message" or an "upper-layer signaling message." A message used for MAC signaling may be referred to as a "MAC message" or a "MAC signaling message." A message used for PHY signaling may be referred to as a "PHY message" or a "PHY signaling message." Upper-layer signaling may refer to the transmission and reception operations of system information (e.g., MIB (master information block), SIB (system information block)) and / or RRC messages. MAC signaling may refer to the transmission and reception operations of MAC CE (control element). PHY signaling may refer to the transmission and reception operations of control information (e.g., DCI (downlink control information), UCI (uplink control information), SCI (sidelink control information)).

[0051] In the present disclosure, "setting an operation (e.g., a transmission operation)" may mean that "setting information for said operation (e.g., an information element, a parameter)" and / or "information directing the performance of said operation" is signaled. "Setting an information element (e.g., a parameter)" may mean that said information element is signaled. In the present disclosure, "signal and / or channel" may mean a signal, a channel, or "signal and channel," and "signal" may be used to mean "signal and / or channel."

[0052] The communication networks to which the embodiments are applied are not limited to those described below, and the embodiments may be applied to various communication networks (e.g., 4G communication networks, 5G communication networks, and / or 6G communication networks). Here, the term "communication network" may be used interchangeably with "communication system."

[0053] FIG. 1 is a conceptual diagram illustrating a first embodiment of a communication system.

[0054] Referring to FIG. 1, the communication system (100) may include a plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6). Additionally, the communication system (100) may further include a core network (e.g., an S-GW (serving-gateway), a P-GW (PDN (packet data network)-gateway), and an MME (mobility management entity)). If the communication system (100) is a 5G communication system (e.g., a new radio (NR) system), the core network may include an AMF (access and mobility management function), a UPF (user plane function), an SMF (session management function), etc.

[0055] Multiple communication nodes (110 to 130) can support communication protocols defined in 3GPP (3rd generation partnership project) standards (e.g., LTE communication protocol, LTE-A communication protocol, NR communication protocol, etc.). Multiple communication nodes (110 to 130) can support CDMA (code division multiple access) technology, WCDMA (wideband CDMA) technology, TDMA (time division multiple access) technology, FDMA (frequency division multiple access) technology, OFDM (orthogonal frequency division multiplexing) technology, Filtered OFDM technology, CP (cyclic prefix)-OFDM technology, DFT-s-OFDM (discrete Fourier transform-spread-OFDM) technology, OFDMA (orthogonal frequency division multiple access) technology, SC (single carrier)-FDMA technology, NOMA (non-orthogonal multiple access) technology, GFDM (generalized frequency division multiplexing) technology, FBMC (filter bank multi-carrier) technology, UFMC (universal filtered multi-carrier) technology, SDMA (space division multiple access) technology, etc. Each of the multiple communication nodes may have the following structure.

[0056] FIG. 2 is a block diagram illustrating a first embodiment of a communication node constituting a communication system.

[0057] Referring to FIG. 2, the communication node (200) may include at least one processor (210), a memory (220), and a transceiver (230) that is connected to a network to perform communication. Additionally, the communication node (200) may further include an input interface device (240), an output interface device (250), a storage device (260), etc. Each component included in the communication node (200) may be connected by a bus (270) to communicate with one another.

[0058] The processor (210) can execute a program command stored in at least one of the memory (220) and the storage device (260). The processor (210) may mean a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which the methods according to embodiments of the present disclosure are performed. Each of the memory (220) and the storage device (260) may be composed of at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory (220) may be composed of at least one of read-only memory (ROM) and random access memory (RAM).

[0059] Referring again to FIG. 1, the communication system (100) may include a plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) and a plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6). Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) may form a macro cell. Each of the fourth base station (120-1) and the fifth base station (120-2) may form a small cell. The fourth base station (120-1), the third terminal (130-3), and the fourth terminal (130-4) may be located within the cell coverage of the first base station (110-1). The second terminal (130-2), the fourth terminal (130-4), and the fifth terminal (130-5) may be located within the cell coverage of the second base station (110-2). The fifth base station (120-2), the fourth terminal (130-4), the fifth terminal (130-5), and the sixth terminal (130-6) may be located within the cell coverage of the third base station (110-3). The first terminal (130-1) may be located within the cell coverage of the fourth base station (120-1). The sixth terminal (130-6) may be located within the cell coverage of the fifth base station (120-2).

[0060] Here, each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be referred to as NB (NodeB), eNB (evolved NodeB), gNB, ABS (advanced base station), HR-BS (high reliability-base station), BTS (base transceiver station), radio base station, radio transceiver, access point, access node, RAS (radio access station), MMR-BS (mobile multihop relay-base station), RS (relay station), ARS (advanced relay station), HR-RS (high reliability-relay station), HNB (home NodeB), HeNB (home eNodeB), RSU (road side unit), RRH (radio remote head), TP (transmission point), TRP (transmission and reception point), etc.

[0061] Each of the multiple terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) may be referred to as UE (user equipment), TE (terminal equipment), AMS (advanced mobile station), HR-MS (high reliability-mobile station), terminal, access terminal, mobile terminal, station, subscriber station, mobile station, portable subscriber station, node, device, OBU (on board unit), etc.

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

[0063] In addition, each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) can support MIMO transmission (e.g., SU (single user)-MIMO, MU (multi user)-MIMO, massive MIMO, etc.), CoMP (coordinated multipoint) transmission, carrier aggregation (CA) transmission, transmission in an unlicensed band, sidelink communication (e.g., D2D (device to device communication), ProSe (proximity services)), IoT (Internet of Things) communication, dual connectivity (DC), etc. Here, each of the plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) can perform an operation corresponding to the base station (110-1, 110-2, 110-3, 120-1, 120-2) and an operation supported by the base station (110-1, 110-2, 110-3, 120-1, 120-2). For example, the second base station (110-2) can transmit a signal to the fourth terminal (130-4) based on the SU-MIMO method, and the fourth terminal (130-4) can receive a signal from the second base station (110-2) based on the SU-MIMO method. Alternatively, the second base station (110-2) can transmit a signal to the fourth terminal (130-4) and the fifth terminal (130-5) based on the MU-MIMO method, and each of the fourth terminal (130-4) and the fifth terminal (130-5) can receive a signal from the second base station (110-2) by the MU-MIMO method.

[0064] Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can transmit a signal to the fourth terminal (130-4) based on the CoMP method, and the fourth terminal (130-4) can receive a signal from the first base station (110-1), the second base station (110-2), and the third base station (110-3) by the CoMP method. Each of the multiple base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit and receive signals based on the CA method with terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) within its cell coverage area. Each of the first base station (110-1), the second base station (110-2), and the third base station (110-3) can control sidelink communication between the fourth terminal (130-4) and the fifth terminal (130-5), and each of the fourth terminal (130-4) and the fifth terminal (130-5) can perform sidelink communication by controlling each of the second base station (110-2) and the third base station (110-3).

[0065] Meanwhile, communication nodes performing communication in a communication network may be configured as follows. The communication node shown in FIG. 3 may be a specific embodiment of the communication node shown in FIG. 2.

[0066] FIG. 3 is a block diagram illustrating a first embodiment of communication nodes performing communication.

[0067] Referring to FIG. 3, the first communication node (300a) and the second communication node (300b) may each be a base station or a UE. The first communication node (300a) may transmit a signal to the second communication node (300b). A transmission processor (311) included in the first communication node (300a) may receive data (e.g., a data unit) from a data source (310). The transmission processor (311) may receive control information from a controller (316). The control information may include at least one of system information, RRC setting information (e.g., information set by RRC signaling), MAC control information (e.g., MAC CE), or PHY control information (e.g., DCI, SCI).

[0068] The transmitting processor (311) can generate data symbol(s) by performing processing operations on data (e.g., encoding operations, symbol mapping operations, etc.). The transmitting processor (311) can generate control symbol(s) by performing processing operations on control information (e.g., encoding operations, symbol mapping operations, etc.). Additionally, the transmitting processor (311) can generate synchronization / reference symbol(s) for synchronization signals and / or reference signals.

[0069] The Tx MIMO processor (312) can perform spatial processing operations (e.g., precoding operations) on data symbol(s), control symbol(s), and / or synchronization / reference symbol(s). The output of the Tx MIMO processor (312) (e.g., a symbol stream) can be provided to modulators (MODs) included in transceivers (313a to 313t). The modulators (MODs) can perform processing operations on the symbol stream to generate modulated symbols and perform additional processing operations on the modulated symbols (e.g., analog conversion operations, amplification operations, filtering operations, up-conversion operations) to generate signals. The signals generated by the modulators (MODs) of the transceivers (313a to 313t) can be transmitted through antennas (314a to 314t).

[0070] Signals transmitted by the first communication node (300a) can be received at the antennas (364a to 364r) of the second communication node (300b). Signals received at the antennas (364a to 364r) can be provided to demodulators (DEMODs) included in the transceivers (363a to 363r). The demodulators (DEMODs) can obtain samples by performing processing operations on the signals (e.g., filtering, amplification, down-conversion, digital conversion). The demodulators (DEMODs) can obtain symbols by performing additional processing operations on the samples. The MIMO detector (362) can perform MIMO detection operations on the symbols. The receiving processor (361) can perform processing operations on the symbols (e.g., deinterleaving, decoding). The output of the receiving processor (361) can be provided to the data sink (360) and the controller (366). For example, data can be provided to the data sink (360), and control information can be provided to the controller (366).

[0071] Meanwhile, the second communication node (300b) can transmit a signal to the first communication node (300a). The transmission processor (368) included in the second communication node (300b) can receive data (e.g., a data unit) from the data source (367) and can generate data symbol(s) by performing a processing operation on the data. The transmission processor (368) can receive control information from the controller (366) and can generate control symbol(s) by performing a processing operation on the control information. Additionally, the transmission processor (368) can generate reference symbol(s) by performing a processing operation on a reference signal.

[0072] The Tx MIMO processor (369) can perform spatial processing operations (e.g., precoding operations) on data symbol(s), control symbol(s), and / or reference symbol(s). The output of the Tx MIMO processor (369) (e.g., a symbol stream) can be provided to modulators (MODs) included in transceivers (363a to 363t). The modulators (MODs) can perform processing operations on the symbol stream to generate modulated symbols and perform additional processing operations on the modulated symbols (e.g., analog conversion operations, amplification operations, filtering operations, up-conversion operations) to generate signals. The signals generated by the modulators (MODs) of the transceivers (363a to 363t) can be transmitted through antennas (364a to 364t).

[0073] Signals transmitted by the second communication node (300b) can be received at the antennas (314a to 314r) of the first communication node (300a). Signals received at the antennas (314a to 314r) can be provided to demodulators (DEMODs) included in the transceivers (313a to 313r). The demodulators (DEMODs) can obtain samples by performing processing operations on the signals (e.g., filtering operation, amplification operation, down-conversion operation, digital conversion operation). The demodulators (DEMODs) can obtain symbols by performing additional processing operations on the samples. The MIMO detector (320) can perform MIMO detection operations on the symbols. The receiving processor (319) can perform processing operations on the symbols (e.g., deinterleaving operation, decoding operation). The output of the receiving processor (319) can be provided to the data sink (318) and the controller (316). For example, data can be provided to the data sink (318), and control information can be provided to the controller (316).

[0074] The memories (315 and 365) may store data, control information, and / or program code. The scheduler (317) may perform scheduling operations for communication. The processors (311, 312, 319, 361, 368, 369) and controllers (316, 366) shown in FIG. 3 may be the processor (210) shown in FIG. 2 and may be used to perform the methods described in this disclosure.

[0075] FIG. 4a is a block diagram illustrating a first embodiment of a transmission path, and FIG. 4b is a block diagram illustrating a first embodiment of a reception path.

[0076] Referring to FIGS. 4a and 4b, a transmission path (410) may be implemented at a communication node that transmits a signal, and a reception path (420) may be implemented at a communication node that receives a signal. The transmission path (410) may include a channel coding and modulation block (411), an S-to-P (serial-to-parallel) block (512), an N IFFT (Inverse Fast Fourier Transform) block (413), a P-to-S (parallel-to-serial) block (414), a CP (cyclic prefix) addition block (415), and an UC (up-converter) (UC) (416). The reception path (420) may include a DC (down-converter) (421), a CP removal block (422), an S-to-P block (423), an N FFT block (424), a P-to-S block (425), and a channel decoding and demodulation block (426). Here, N can be a natural number.

[0077] Information bits in the transmission path (410) can be input to the channel coding and modulation block (411). The channel coding and modulation block (411) can perform coding operations (e.g., LDPC (low-density parity check) (LDPC) coding operations, polar coding operations, etc.) and modulation operations (e.g., QPSK (Quadrature Phase Shift Keying), QAM (Quadrature Amplitude Modulation), etc.) on the information bits. The output of the channel coding and modulation block (411) may be a sequence of modulation symbols.

[0078] The S-to-P block (412) can convert modulated symbols in the frequency domain into parallel symbol streams to generate N parallel symbol streams. N can be the IFFT size or the FFT size. The N IFFT block (413) can generate signals in the time domain by performing an IFFT operation on the N parallel symbol streams. The P-to-S block (414) can convert the output of the N IFFT block (413) (e.g., parallel signals) into a serial signal to generate a serial signal.

[0079] The CP addition block (415) can insert CP into the signal. The UC (416) can up-convert the frequency of the output of the CP addition block (415) to an RF (radio frequency) frequency. Additionally, the output of the CP addition block (415) can be filtered in the baseband before up-conversion.

[0080] A signal transmitted from the transmission path (410) can be input to the reception path (420). The operation in the reception path (420) may be the inverse operation of the operation in the transmission path (410). The DC (421) may down-convert the frequency of the received signal to a baseband frequency. The CP removal block (422) may remove CP from the signal. The output of the CP removal block (422) may be a serial signal. The S-to-P block (423) may convert the serial signal into parallel signals. The N FFT block (424) may generate N parallel signals by performing an FFT algorithm. The P-to-S block (425) may convert the parallel signals into a sequence of modulation symbols. The channel decoding and demodulation block (426) may perform a demodulation operation on the modulation symbols and perform a decoding operation on the result of the demodulation operation to restore the data.

[0081] In FIGS. 4a and 4b, Discrete Fourier Transform (DFT) and Inverse DFT (IDFT) may be used instead of FFT and IFFT. In FIGS. 4a and 4b, each of the blocks (e.g., components) may be implemented by at least one of hardware, software, or firmware. For example, in FIGS. 4a and 4b, some blocks may be implemented by software, and the remaining blocks may be implemented by hardware or a "combination of hardware and software." In FIGS. 4a and 4b, one block may be subdivided into multiple blocks, multiple blocks may be integrated into one block, some blocks may be omitted, and blocks supporting other functions may be added.

[0082] FIG. 5 is a conceptual diagram illustrating a first embodiment of a system frame in a communication system.

[0083] Referring to FIG. 5, time resources in a communication system can be divided into frames. For example, system frames can be set consecutively in the time domain of the communication system. The length of a system frame can be 10 ms (millisecond). The system frame number (SFN) can be set from #0 to #1023. In this case, 1024 system frames can be repeated in the time domain of the communication system. For example, the SFN of a system frame after system frame #1023 can be #0.

[0084] A single system frame may contain two half frames. The length of a single half frame may be 5ms. A half frame located at the beginning of the system frame may be referred to as "Half Frame #0", and a half frame located at the end of the system frame may be referred to as "Half Frame #1". A system frame may contain 10 subframes. The length of a single subframe may be 1ms. Within a single system frame, the 10 subframes may be referred to as "Subframe #0-9".

[0085] FIG. 6 is a conceptual diagram illustrating a first embodiment of a subframe in a communication system.

[0086] Referring to FIG. 6, one subframe may include n slots, where n is a natural number. Thus, one subframe may consist of one or more slots.

[0087] FIG. 7 is a conceptual diagram illustrating a first embodiment of a slot in a communication system.

[0088] Referring to FIG. 7, a slot may contain one or more symbols. A slot illustrated in FIG. 7 may contain 14 symbols. The length of the slot may vary depending on the number of symbols included in the slot and the length of the symbols. Alternatively, the length of the slot may vary depending on the numerology.

[0089] Numerals applied to physical signals and channels in a communication system may be variable. Numerals may be variable to meet various technical requirements of the communication system. In a communication system where CP (cyclic prefix) based OFDM waveform technology is applied, numerals may include subcarrier spacing and CP length (or CP type). Table 1 may be a first embodiment of a method for configuring numerals for a CP-OFDM based communication system. Depending on the frequency band in which the communication system operates, at least some of the numerals in Table 1 may be supported. Additionally, numerals not listed in Table 1 may be further supported in the communication system.

[0090] Subcarrier Spacing 15kHz 30kHz 60kHz 120kHz 240kHz 480kHz OFDM Symbol Length (μs) 66.733.316.78.34.22.1 CP Length (μs) 4.762.381.190.600.300.151 ms Number of OFDM Symbols within 142856112224448

[0091]

[0092] When the subcarrier spacing is 15 kHz (e.g., μ=0), the slot length may be 1 ms. In this case, one system frame may contain 10 slots. When the subcarrier spacing is 30 kHz (e.g., μ=1), the slot length may be 0.5 ms. In this case, one system frame may contain 20 slots.

[0093] When the subcarrier spacing is 60 kHz (e.g., μ=2), the slot length may be 0.25 ms. In this case, one system frame may contain 40 slots. When the subcarrier spacing is 120 kHz (e.g., μ=3), the slot length may be 0.125 ms. In this case, one system frame may contain 80 slots. When the subcarrier spacing is 240 kHz (e.g., μ=4), the slot length may be 0.0625 ms. In this case, one system frame may contain 160 slots.

[0094] A symbol can be set as a downlink (DL) symbol, a flexible (FL) symbol, or an uplink (UL) symbol. A slot consisting only of a DL symbol may be referred to as a "DL slot," a slot consisting only of an FL symbol may be referred to as a "FL slot," and a slot consisting only of a UL symbol may be referred to as a "UL slot."

[0095] The slot format can be semi-fixed by upper-layer signaling (e.g., RRC signaling). Information indicating the semi-fixed slot format may be included in system information, and the semi-fixed slot format can be set cell-specifically. Additionally, the semi-fixed slot format can be additionally set per terminal through terminal-specific upper-layer signaling (e.g., RRC signaling). The flexible symbols of the cell-specific slot format can be overridden as downlink symbols or uplink symbols by the terminal-specific upper-layer signaling. Furthermore, the slot format can be dynamically indicated by physical layer signaling (e.g., the SFI (slot format indicator) included in the DCI). The semi-fixed slot format can be overridden by the dynamically indicated slot format. For example, the semi-fixed flexible symbols can be overridden as downlink symbols or uplink symbols by the SFI.

[0096] The reference signal may be a CSI-RS (channel state information-reference signal), SRS (sounding reference signal), DM-RS (demodulation-reference signal), PT-RS (phase tracking-reference signal), etc. The channel may be a PBCH (physical broadcast channel), PDCCH (physical downlink control channel), PDSCH (physical downlink shared channel), PUCCH (physical uplink control channel), PUSCH (physical uplink shared channel), PSCCH (physical sidelink control channel), PSSCH (physical sidelink shared channel), etc. In the present disclosure, the control channel may mean PDCCH, PUCCH, or PSCCH, and the data channel may mean PDSCH, PUSCH, or PSSCH.

[0097] FIG. 8 is a conceptual diagram illustrating a first embodiment of a time-frequency resource in a communication system.

[0098] Referring to FIG. 8, a resource consisting of one symbol (e.g., an OFDM symbol) in the time domain and one subcarrier in the frequency domain can be defined as a "RE (resource element)." A resource consisting of one OFDM symbol in the time domain and K subcarriers in the frequency domain can be defined as a "REG (resource element group)." A REG can include K REs. A REG can be used as the basic unit of resource allocation in the frequency domain. K can be a natural number. For example, K can be 12. N can be a natural number. In the slot illustrated in FIG. 7, N can be 14. N OFDM symbols can be used as the basic unit of resource allocation in the time domain.

[0099] In the present disclosure, RB may mean a common RB (CRB). Alternatively, RB may mean a PRB or a virtual RB (VRB). In a communication system, a CRB may mean an RB that constitutes a set of consecutive RBs (e.g., a common RB grid) based on a reference frequency (e.g., point A). A carrier and / or bandwidth portion may be placed on the common RB grid. That is, the carrier and / or bandwidth portion may be composed of CRB(s). An RB or CRB constituting the bandwidth portion may be referred to as a PRB, and within the bandwidth portion, a CRB index may be appropriately converted to a PRB index.

[0100] Downlink data may be transmitted via PDSCH. A base station may transmit configuration information of the PDSCH (e.g., scheduling information) to a terminal via PDCCH. A terminal may obtain the configuration information of the PDSCH by receiving the PDCCH (e.g., downlink control information (DCI)). For example, the configuration information of the PDSCH may include a modulation coding scheme (MCS) used for transmitting and receiving the PDSCH, time resource information of the PDSCH, frequency resource information of the PDSCH, feedback resource information for the PDSCH, etc. PDSCH may refer to a radio resource where downlink data is transmitted and received. Alternatively, PDSCH may refer to the downlink data itself. PDCCH may refer to a radio resource where downlink control information (e.g., DCI) is transmitted and received. Alternatively, PDCCH may refer to the downlink control information itself.

[0101] The terminal may perform a monitoring operation for the PDCCH to receive the PDSCH transmitted from the base station. The base station may notify the terminal of configuration information for the monitoring operation of the PDCCH using a higher-layer message (e.g., a radio resource control (RRC) message). The configuration information for the monitoring operation of the PDCCH may include CORESET (control resource set) information and search space information.

[0102] CORESET information may include PDCCH DMRS (demodulation reference signal) information, PDCCH precoding information, PDCCH occasion information, etc. The PDCCH DMRS may be a DMRS used to demodulate the PDCCH. A PDCCH occasion may be an area where the PDCCH can exist. That is, a PDCCH occasion may be an area where DCI can be transmitted. A PDCCH occasion may be referred to as a PDCCH candidate. PDCCH occasion information may include time resource information and frequency resource information of the PDCCH occasion. In the time domain, the length of the PDCCH occasion may be indicated in symbol units. In the frequency domain, the size of the PDCCH occasion may be indicated in RB units (e.g., PRB (physical resource block) units or CRB (common resource block) units).

[0103] The search space information may include a CORESET ID (identifier) ​​associated with the search space, the period of PDCCH monitoring, and / or an offset. The period and offset of PDCCH monitoring may each be specified in slot units. Additionally, the search space information may further include the index of the symbol where the PDCCH monitoring operation begins.

[0104] A base station may configure a Bandwidth Part (BWP) for downlink communication. BWPs may be configured differently for each terminal. The base station may notify the terminal of the BWP configuration information using upper-layer signaling. Upper-layer signaling may refer to "transmission operations of system information" and / or "transmission operations of Radio Resource Control (RRC) messages." One or more BWPs may be configured for a single terminal. The terminal may receive BWP configuration information from the base station and identify the BWP(s) configured by the base station based on the BWP configuration information. If multiple BWPs are configured for downlink communication, the base station may activate one or more of the multiple BWPs. The base station may transmit the configuration information of the activated BWP(s) to the terminal using at least one of upper-layer signaling, a Medium Access Control (MAC) Control Element (CE), or a DCI. The base station may perform downlink communication using the activated BWP(s). The terminal can identify the activated BWP(s) by receiving configuration information of the activated BWP(s) from the base station, and can perform a downlink reception operation on the activated BWP(s).

[0105]

[0106] TDD (time division duplex) systems are widely used in NR deployment. In a TDD system, downlink (DL) symbols and uplink (UL) symbols can exist within a single carrier using different time resources. By considering various usage scenarios that account for coverage and latency, resources can be used more efficiently than in FDD (frequency division duplex) systems, which implies that resource scheduling at the base station becomes more important in a TDD system.

[0107] As part of the enhancement of these TDD systems, standardization is underway for subband full duplex (SBFD) technology, which allows base stations to simultaneously perform DL signal transmission and UL signal reception using non-overlapping resources in the frequency domain within the TDD band. In 3GPP Rel-18, SBFD technology was designated as a study item (SI) for discussion, and in 3GPP Rel-19, SBFD technology was designated as a work item (WI) to proceed with full-scale standardization.

[0108] In SBFD technology, it is assumed that the base station can perform DL transmission and UL reception within a single symbol (i.e., full-duplexing), and that the terminal can perform only one of the operations of DL reception or UL transmission within a single symbol (i.e., half-duplexing).

[0109] In the present disclosure, 'SBFD symbol' refers to a symbol containing subbands in which a base station can perform SBFD operations. Meanwhile, 'non-SFBD symbol' may refer to a symbol that is not an SBFD symbol. Generally, a subband for SBFD may be interpreted as referring to a UL subband. As a result of standardization discussions, it was agreed that UL subbands may also exist in symbols in which SSB is transmitted.

[0110] Meanwhile, 3GPP Rel-19 agreed that SBFD operation is performed based on the semi-static configuration of time and frequency domain resources. Although allowing dynamic configuration could be more efficient in terms of resource management, it was decided that standardization for semi-static configuration would proceed first, as it could lead to many problems due to the need to consider conflicts with resources allocated by the semi-static configuration. Additionally, it was decided that subbands exist only within DL and / or flexible symbols configured by the TDD-UL-DL configuration common. Furthermore, within the time domain, transitions between non-SBFD and SBFD symbols and transitions from SBFD to non-SBFD symbols are limited to one per slot. This is because frequent transitions increase implementation complexity and can cause interference between transmitted and received signals during the transition. Regarding the setting of time / frequency resources for subbands, it was agreed that the basic basis is to ensure that the terminal is aware of information about the time / frequency resources of the subband in advance.

[0111] As previously mentioned, it has been agreed that DL and / or flexible symbols configured via TDD-UL-DL-ConfigCommon can be configured as SBFD symbols. TDD-UL-DL-ConfigCommon is configuration information for setting patterns for time-domain DL or UL resources in a TDD system, and such patterns may change depending on the network environment. The current standard stipulates that a maximum of two patterns can be configured. TDD-UL-DL-ConfigCommon is a cell-specific parameter, and the base station can change the configuration of symbols in specific slots within the pre-configured patterns on a terminal-by-terminal basis; however, the slots for which configuration changes are possible are limited to the slots flexibly configured by TDD-UL-DL-ConfigCommon. The RRC signaling used in this case is TDD-UL-DL-ConfigDedicated.

[0112] Table 2 shows the specific configuration of TDD-UL-DL-ConfigCommon.

[0113]

[0114]

[0115] In Table 2, dl-UL-TransmissionPeriodicity indicates the period of the DL-UL pattern, and nrofDownlinkSlots indicates the total number of DL slots that exist consecutively at the beginning of each DL-UL pattern, with a maximum value of 320. nrofDownlinkSymbols indicates the number of DL symbols that exist consecutively at the beginning of the slots following the last total DL slot, derived from nrofDownlinkSlots, and if this value is set to 0, it may indicate that there are no partial-downlink slots. nrofUplinkSlots indicates the total number of UL slots that exist consecutively at the end of each DL-UL pattern, and in this release, the maximum value of this field is 320. nrofUplinkSymbols represents the number of consecutive UL symbols at the end of the slots preceding the first full UL slot, derived from nrofUplinkSlots, and if the value is set to 0, it may indicate that there are no partial-uplink slots.

[0116] Table 3 shows the specific configuration of TDD-UL-DL-ConfigDedicated.

[0117]

[0118]

[0119] Referring to Table 3, slotSpecificConfigurationsToAddModList included in TDD-UL-DL-ConfigDedicated allows overriding the UL / DL assignments provided by tdd-UL-DL-configurationCommon. nrofDownlinkSymbols included in TDD-UL-DL-SlotConfig indicates the number of consecutive DL symbols at the beginning of the slot identified by slotIndex; if this field is absent, the terminal assumes there are no preceding DL symbols. nrofUplinkSymbols indicates the number of consecutive UL symbols at the end of the slot identified by slotIndex; if this field is absent, the terminal assumes there are no trailing UL symbols. slotIndex identifies the slot within the given slot configuration cycle in tdd-UL-DL-configurationCommon. Symbols indicates the direction (downlink or uplink) of the symbols within the slot; if set to allDownlink, it indicates that all symbols within the slot are used for downlinks; if set to allUplink, it indicates that all symbols within the slot are used for uplinks; and if set to explicit, it explicitly indicates how many symbols are assigned to downlinks and uplinks at the beginning and end of the slot, respectively.

[0120] Referring to Tables 2 and 3, it can be seen that the DL / UL pattern by TDD-UL-DL-ConfigCommon is repeated for a specific interval length (e.g., periodicity), with the first half of the interval used for DL ​​and the second half for UL. Additionally, the available values ​​for this periodicity may vary depending on the reference numerology. Current standards stipulate that a guard time or gap required for switching is necessary between consecutive DL symbols / slots and UL symbols / slots, but that no separate guard time or gap is required between consecutive UL symbols / slots and DL symbols / slots. This is because the presence of propagation delay in DL signals causes interference with UL symbols. Furthermore, unlike DL, UL does not encounter problems in receiving consecutive DL signals because the base station transmits a Timing Advance command to the terminal.

[0121] Hereinafter, for the sake of technical convenience, TDD-UL-DL-ConfigCommon and TDD-UL-DL-ConfigDedicated signalings are abbreviated as 'TDD common' and 'TDD dedicated', respectively, and the subband for SBFD is abbreviated as 'UL subband'. Additionally, since the DL symbols / slots, UL symbols / slots, and flexible symbols / slots configured by TDD common and TDD dedicated can be arranged sequentially along the time axis, they are referred to as 'DL region', 'UL region', and 'flexible region', respectively. Furthermore, terminals that support or recognize SBFD are referred to as 'SBFD UE', and terminals that do not support or recognize SBFD are referred to as 'Non-SBFD UE'. Also, the term 'legacy configuration' refers to the configuration for Non-SBFD UEs. In addition, RACH occasions (RO) that non-SBFD UEs do not recognize are referred to as 'SBFD RO', and ROs that non-SBFD UEs can recognize are referred to as 'legacy RO'.

[0122]

[0123] For the configuration of PRACH transmission in an SBFD system, options may be supported: Option #1, which follows the existing configuration of PRACH transmission in a non-SBFD system exactly, and Option #2, which includes separate additional settings in addition to the existing configuration of PRACH transmission in a non-SBFD system and utilizes both configurations. For technical convenience, legacy RACH configuration refers to the configuration for PRACH transmission in a non-SBFD system, and additional RACH configuration refers to additional configuration to support an SBFD system. In the following, unless otherwise specified, Option #1 refers to a method of configuring PRACH-related resources for an SBFD UE using only legacy RACH configuration, and Option #2 refers to a method of configuring PRACH-related resources using separate additional settings for an SBFD UE.

[0124] Regarding the mapping relationship between ROs for transmitting a PRACH corresponding to an SSB (synchronization signal block), for Option #2, it was agreed that ROs are valid if they are located within at least fully usable UL PRBs (physical resource blocks) and do not overlap with the SSB. Additionally, although ROs containing symbols of fundamentally different symbol types (i.e., 'SBFD symbols' and 'non-SBFD symbols') are generally deemed invalid, under Option #2, they may be configured as valid ROs based on network judgment. For the relevant RO (i.e., the RO containing symbols of different symbol types), the terminal assumes the following.

[0125] The same frequency resource is used in both the SBFD segment and the non-SBFD segment of -PRACH.

[0126] The same UL transmission power is used in both the SBFD and non-SBFD sections of -PRACH.

[0127] The same UL spatial domain filter is used for both the SBFD and non-SBFD sections of -PRACH.

[0128] - The terminal does not interrupt PRACH transmission during the transition interval / gap (if any) between SBFD symbols and non-SBFD symbols.

[0129] There are no phase coherency requirements for terminals between the SBFD and non-SBFD segments of PRACH.

[0130]

[0131] In this disclosure, ROs additionally generated according to Option #1 or Option #2 are defined as 'additional ROs'. Additional ROs may be defined differently depending on each option. Additional ROs for Option #1 refer to both ROs configured within SBFD symbols and ROs configured across SBFD symbols and non-SBFD symbols, while additional ROs for Option #2 refer to ROs configured by an additional configuration for RACH transmission of an SBFD UE. For convenience of description, Option #1 is referred to as RACH Configuration #1 and Option #2 is referred to as RACH Configuration #2. An SBFD UE determines an RO configured within a non-SBFD symbol through an additional configuration as an invalid RO and does not expect a msg1 transmission from that resource. In other words, within non-SBFD symbols, the SBFD UE expects msg1 transmission from the RO configured by the legacy configuration, and within SBFD symbols, expects msg1 transmission from the RO configured by the additional configuration. As a result of recent standard meetings, it has been agreed that parameters related to transmit power for RACH configuration #1 and RACH configuration #2 can be configured separately. Due to the nature of SBFD operation, resources for msg3 transmission can be configured within SBFD symbols and / or non-SBFD symbols. Additionally, for SBFD UEs in an RRC connection state, both CBRA (contention-based random access) and CFRA (contention-free random access) can be supported, and PDCCH order-based RA can also be supported.The present disclosure describes problems that may arise when instructing an SBFD UE to perform a PDCCH order-based CBRA procedure or a PDCCH order-based CFRA procedure, and methods for resolving said problems.

[0132]

[0133] Generally, RA procedures based on PDCCH orders can be triggered at the MAC or RRC layer depending on an event, and the terminal executes the RA procedure based on parameters set through RRC signaling. CBRA and CFRA differ in the setting values ​​of the preamble index field within the DCI of the PDCCH order that directs each procedure. For example, if all bits in the corresponding field are set to '0', the PDCCH order directs the execution of the CBRA procedure; if the bits in the corresponding field are not '0' but indicate a preamble index available to the terminal, such as 1 to 63, the PDCCH order directs the execution of the CFRA procedure. Due to the nature of CFRA, collisions between preambles transmitted by terminals must be prevented; therefore, the PDCCH order can set not only the preamble index but also the RO to which the preamble will be transmitted. The RO can be set by the SSB index and the PRACH mask index. Meanwhile, if the PDCCH order indicates CBRA, the corresponding bit fields can be interpreted as reserved bits. Considering the SBFD UE, for the case of CFRA, an additional 1 bit is added to the DCI of the PDCCH order to indicate the RO type (i.e., legacy RO or additional RO).

[0134] The present disclosure describes potential problems that may occur in the operation of an SBFD UE for each scenario of a CFRA triggered by a PDCCH order and a CBRA triggered by a PDCCH order, and provides solutions thereto. For the sake of convenience of description, 'CBRA' and 'CFRA' refer to a CBRA triggered by a PDCCH order and a CFRA triggered by a PDCCH order, respectively.

[0135]

[0136] Scenario: CFRA triggered by the PDCCH order

[0137] According to current standards, if a PDCCH order instructing the execution of an RA procedure is received while an RA procedure is already being executed, the non-SBFD UE may decide by its implementation whether to prioritize the existing RA procedure and continue with it, or to execute the newly triggered RA procedure. However, if the same preamble resources used in the existing RA procedure (e.g., preamble index, PRACH mask index, uplink (UL) carrier) are set by the PDCCH order while the RA procedure is already being executed, the non-SBFD UE continues to execute the RA procedure that was in progress. This behavior is defined by 3GPP TS38.321 (see Table 4). For the sake of technical convenience, the above-described rule is referred to as the 'Duplicate PDDCH Order-Based RA Procedure Determination Rule'.

[0138]

[0139]

[0140] If the above-described operation is applied directly to the SBFD UE, problems may arise regarding the latency of the RA procedure. In the case of RACH configuration #2, both legacy ROs and additional ROs may exist within the same UL carrier, and the RACH configuration for each RO type can be configured independently of each other. That is, even if the preamble index and PRACH mask index are set identically, a different RO may be indicated depending on the RO type. However, the rule for determining duplicate PDCCH order-based RA procedures defined in 3GPP TS 38.321 determines whether they are the same RA procedure based only on the preamble index, PRACH mask index, and UL carrier, and does not consider the RO type. Therefore, even if the base station sets the same preamble index and PRACH mask index as the existing RA procedure while re-instructing CFRA from the additional RO for the purpose of reducing latency, the terminal may determine that the RA procedure according to the new PDCCH order is the same RA procedure as the existing RA procedure and continue to perform the existing RA procedure without executing the new RA procedure. In this case, the terminal may not be able to immediately transmit a preamble in the additional RO, even though it could, and thus may not fully achieve the objective of reducing the delay of the RA procedure.

[0141] Figure 9 is a conceptual diagram illustrating potential problems that may occur in a CFRA triggered by a PDCCH order.

[0142] Referring to FIG. 9, the aforementioned problem is explained. For example, while an SBFD UE is in the process of performing a previous RA procedure to transmit Msg1 (910) in a legacy RO, a new CFRA procedure is indicated by a PDCCH order (920) received from a base station, and if the PDCCH order contains information indicating an RA procedure in a specific RO type and the RO type is set as an additional RO, and if the PDCCH order sets a preamble index and a PRACH mask index identical to the preamble index and PRACH mask index used in the previous RA procedure, the SBFD UE is expected to ignore the PDCCH order (920) and continue to perform Msg1 transmission (910) according to the previous RA procedure. In this case, a situation may occur where the SBFD UE is unable to transmit Msg1 even though it is capable of transmitting Msg1 in additional ROs (930, 940).

[0143] That is, according to the current standard, the terminal determines whether to execute a newly indicated CFRA procedure based solely on the preamble index and the PRACH mask index, but considering that independent RACH settings are now possible for each RO type for SBFD operation and that the PDCCH order can indicate the RO type for executing the RA procedure, a method is needed to resolve the above problem.

[0144] Below, methods for solving the aforementioned problem are described.

[0145] Method #1: For SBFD UEs, ROs to which preambles can be transmitted can be classified into two types: legacy ROs and additional ROs, and the preamble settings used for each RO type can be configured independently of each other. Therefore, if the preamble index, PRACH mask index, and UL carrier are identical despite the RO types being different, failing to use available RO resources can be inefficient in terms of latency. Accordingly, additional consideration and restrictions may be required to avoid performing a new RACH procedure only when the RO types are identical, by taking into account not only the preamble index, PRACH mask index, and UL carrier but also the RO type. That is, the duplicate PDDCH order-based RA procedure determination rule in Table 4 can be modified as shown in Table 5 below.

[0146]

[0147]

[0148] That is, while an SBFD UE is performing an RA procedure on a specific RO type, if a CFRA for the same RO type is indicated by a new PDCCH order and the preamble resources set by the PDCCH order (e.g., preamble index, PRACH mask index, and UL carrier) are identical, the terminal may ignore the PDCCH order and continue performing the existing RA procedure. On the other hand, even if the preamble resources set by the new PDCCH order (e.g., preamble index, PRACH mask index, and UL carrier) are identical, if the RO type indicated by the PDCCH order is different from the RO type on which the existing RA procedure is performed, the terminal may perform the RA procedure according to the new PDCCH order or continue performing the existing RA procedure, depending on the implementation of the terminal. Additionally, whether the preamble resources are identical may be determined based on whether all parameters (i.e., preamble index, PRACH mask index, and UL carrier) are identical. In addition, the above determination of identity may be based on cases where only some parameters are identical, and additional parameters such as the SSB index may be considered as necessary.

[0149] Method #1 can be implemented with the following detailed methods.

[0150]

[0151] Method #1-1: Since preamble settings and frequency / time resources (e.g., RO and SSB-to-RO mapping) can be set independently for different RO types, the resource area of ​​the RO to which the actual preamble is transmitted may differ even if the preamble index is the same and the value of the PRACH mask index set in different RO types is the same. Therefore, the SBFD UE may continue the existing RA procedure only if both the preamble index and the RO, which is the time / frequency resource used for actual transmission, are the same. Otherwise, the SBFD UE may decide, depending on the implementation of the terminal, whether to perform the RA procedure according to the new PDCCH order. In this case, whether the new PDCCH order indicates an RO type different from the RO type of the existing RA procedure may be determined based on a 1-bit field for RO type indication that may be separately included within the DCI of the PDCCH order. Alternatively, the RO type of the new PDCCH order may be indicated by a field included in the DCI of the PDCCH order, by a reserved bit(s) included in the DCI, or by a radio network temporary identifier (RNTI) scrambled by the cyclic redundancy check (CRC) of the DCI.

[0152] Method #1-2: Instead of having the terminal make a decision based on the redundant PDCCH order-based RA procedure rules of Table 5 based on the preamble resource or RO type, the base station may explicitly instruct the terminal whether to perform an RA procedure according to a new PDCCH order instead of the existing RA procedure. To this end, a separate 1-bit indicator may be added within the DCI of the PDCCH order. The indicator may be a field separate from the 1-bit field for indicating the RO type, and the base station may use the indicator to instruct the terminal whether to continue the existing RA procedure or perform an RA procedure according to the PDCCH order.

[0153] The SBFD UE may refer to the above indicator to ignore the new PDCCH order and continue the existing RA procedure, or perform the RA procedure according to the new PDCCH order. For example, if the above indicator indicates that the new PDCCH order triggers the same RA procedure as the existing RA procedure, the SBFD UE may continue the existing RA procedure, and if the above indicator indicates that the new PDCCH order triggers the new RA procedure, the SBFD UE may perform the RA procedure according to the new PDCCH order.

[0154] Method #1-3: If the RO type to which the preamble set by the new PDCCH order is transmitted is different from the RO type where the existing RA procedure is being performed, the SBFD UE may operate to prioritize the execution of the RA procedure in the RO type indicated by the new PDCCH order. That is, if the RO type indicated by the new PDCCH order is different from the RO type where the existing RA procedure is being performed, the SBFD UE may operate to perform preamble transmission in the RO indicated by the new PDCCH order regardless of whether the existing RA procedure is being performed. This is because, since preamble settings and RO resources can be configured independently for each RO type, the resource area where the actual preamble is transmitted may differ even if the same preamble index or PRACH mask index is set.

[0155] Method #1-4: Even if the preamble index, PRACH mask index, and UL carrier set by the new PDCCH order are identical to the preamble index, PRACH mask index, and UL carrier of the existing RA procedure, the SBFD UE may not ignore the new PDCCH order. That is, even if the same preamble index, PRACH mask index, and UL carrier are set, the SBFD UE may, depending on the implementation, perform a preamble transfer at the RO indicated by the new PDCCH order, or continue to perform a preamble transfer at the RO where the existing RA procedure is being executed. In other words, the SBFD UE may, depending on the implementation, decide whether to perform the subsequent preamble transfer and RA procedure by considering the RACH settings independent of the RO type.

[0156] FIG. 10 is a flowchart illustrating a method for performing a PDCCH order-based RA procedure according to the present disclosure.

[0157] Referring to FIG. 10, a terminal (i.e., SBFD UE) can receive a PDCCH order (hereinafter, the first PDCCH order) from a base station instructing a CFRA procedure (hereinafter, the first CFRA procedure) (S1010), and can start the first CFRA procedure accordingly (S1020).

[0158] While the terminal is performing the first CFRA procedure (i.e., while performing the transmission of Msg1 according to the first CFRA procedure), the terminal may receive a PDCCH order (hereinafter referred to as the second PDCCH order) instructing the base station to perform a new CFRA procedure (hereinafter referred to as the second CFRA procedure) (S1030).

[0159] A terminal that receives a second PDCCH order can decide whether to continue the first CFRA procedure without performing the second CFRA procedure or to perform the second CFRA procedure based on the first information indicated by the second PDCCH order (S1040).

[0160] Here, the first information may be information indicating the RO type for the second CFRA procedure (i.e., in the case of Method #1-1 described above) or information indicating whether the second CFRA procedure is the same RA procedure as the first CFRA procedure (i.e., in the case of Method #1-2 described above).

[0161] The first information may be indicated by a field (e.g., a 1-bit field) included in the downlink control information (DCI) of the PDCCH order, by a reserved bit(s) included in the DCI, or by a radio network temporary identifier (RNTI) scrambled by the cyclic redundancy check (CRC) of the DCI. Alternatively, the first information may be indicated by a specific combination of values ​​set in the fields of the DCI of the PDCCH order. Additionally, if the first information indicates an RO type for the second CFRA procedure, the RO type may indicate a legacy RO or an additional RO.

[0162] Specifically, at step (S1040), the terminal may decide whether to continue the first CFRA procedure without performing the second CFRA procedure or to perform the second CFRA procedure as follows.

[0163] For example, if the first information indicates a second RO type for the second CFRA procedure, and the first PDCCH order and the second PDCCH order indicate the same preamble index and / or the same PRACH mask index, and the second RO type is the same as the first RO type for the first CFRA procedure, the terminal may decide not to perform the second CFRA procedure and to continue the first CFRA procedure (S1050).

[0164] On the other hand, if the first information is information indicating a second RO type for the second CFRA procedure, and the first PDCCH order and the second PDCCH order indicate the same preamble index and / or PRACH mask index, and the second RO type is different from the first RO type for the first CFRA procedure, the terminal may decide to perform the second CFRA procedure (S1060).

[0165] As another example, the first information is information indicating whether the second CFRA procedure is the same RA procedure as the first CFRA procedure, and if the first information indicates that the second CFRA procedure is the same RA procedure as the first CFRA procedure, the terminal may decide not to perform the second CFRA procedure and to continue the first CFRA procedure (S1050).

[0166] On the other hand, the first information indicates whether the second CFRA procedure is the same RA procedure as the first CFRA procedure, and if the first information indicates that the second CFRA procedure is a different RA procedure from the first CFRA procedure, the terminal may decide to perform the second CFRA procedure (S1060).

[0167]

[0168] Scenario: CBRA triggered by a PDDCH order

[0169] As described above, when a PDCCH order directs a CFRA for an SBFD UE, a 1-bit field indicating the RO type may be added within the DCI of the PDCCH order to explicitly provide information about the type of RO to which the preamble will be transmitted. However, when a CBRA is triggered by a PDCCH order, the base station may trigger the CBRA for the SBFD UE using the existing DCI format of the PDCCH order. In this case, the RO to which the SBFD UE can transmit the preamble may exist in both types: legacy ROs and additional ROs. Therefore, when a CBRA is directed to an SBFD UE via a PDCCH order, a problem may arise where it is unclear whether the SBFD UE will transmit the preamble on different RO types or on only one of these RO types. Methods to resolve the aforementioned problem are described below.

[0170] FIGS. 11a to 11c are conceptual diagrams for explaining methods of performing Msg1 transmission when CBRA is indicated by a PDCCH order.

[0171] Method #2: Referring to FIG. 11a, if a separate DCI format is not defined for a PDCCH order instructing a CBRA to an SBFD UE, the SBFD UE that receives a PDCCH order (1110) instructing a CBRA may be configured to transmit Msg1 in both RO types (1111 and 1112).

[0172] Referring to FIG. 11a, since ROs (1111) in SBFD symbols and ROs (1112) in non-SBFD symbols can be configured to have independent patterns, ROs in SBFD symbols and ROs in non-SBFD symbols may have different channel characteristics and collision probabilities. Therefore, when a PDCCH order indicating CBRA is received, the SBFD UE can perform Msg1 transmission on ROs of all RO types associated with a specific SSB selected based on SSB measurement results for fast connection. According to Method 2, since the terminal can perform Msg1 transmission on more ROs, it can gain an advantage in terms of delay, which is one of the purposes of SBFD operation. In this case, the terminal can recognize that Msg1 transmitted from a specific RO type has been received by the base station based on the random access response (RAR) (1113) received from the base station, and if retransmission of Msg1 is performed, Msg1 can be retransmitted from ROs according to the corresponding RO type. To this end, the RAR may include an indicator indicating which RO type the received Msg1 was transmitted from, and the terminal can identify the type of RO to which the received Msg1 was transmitted based on the indicator.

[0173] Method #3: As in Method #2, if the SBFD UE is configured to perform preamble transmissions on ROs included in all RO types, the terminal will perform preamble transmissions on multiple ROs, which may result in overhead in terms of power consumption. Therefore, referring to FIGS. 11b and 11c, the base station may instruct the terminal to perform preamble transmissions on a specific RO type by including an RO type indicator within the DCI field of the PDCCH order (1120) indicating the CBRA. The RO type indicator may consist of a single bit, and depending on the bit value, one of the additional RO (1121) or legacy RO (1122) may be indicated. The SBFD UE may operate to perform preamble transmissions on ROs included in the RO type indicated by the RO type indicator. In this case, the settings of the SSB, RO, and preamble index may follow the existing CBRA behavior (e.g., CBRA behavior of non-SBFD UE).

[0174] Method #4: Method #4 is a method that enables support for both Method #2 and Method #3. To this end, the base station may instruct the terminal on the RO type setting method to apply via SIB, RRC, or DCI signaling.

[0175] For example, a 2-bit field may be used to configure the RO type, and depending on the value of the field, 'legacy RO', 'additional RO', 'both RO types', or 'default' may be indicated. The said 2-bit field may be included within the SIB, RRC, or DCI fields. For example, if 'legacy RO' or 'additional RO' is indicated, the SBFD UE may perform preamble transmissions on the ROs included in the corresponding RO type as described in Method 3. On the other hand, if 'both RO types' is indicated, the SBFD UE may perform preamble transmissions on both ROs included in the two RO types as described in Method 2. Additionally, the 'default' value may be used as a reserved state for future extension and may be interpreted according to the terminal's implementation. Alternatively, the RO type to be applied in the default state may be separately defined or indicated by standard specifications or additional signaling. For example, when RACH is configured, RO type information that allows the terminal to perform preamble transmission for the default state may be transmitted together.

[0176]

[0177] Although the embodiments described above have been explained based on the uplink for convenience of explanation, the same embodiments can be applied equally to the downlink. To this end, uplink-related terms used in the description of the embodiments (e.g., initial UL BWP, UL subband, UL usable PRBs, etc.) can be replaced with terms corresponding to the downlink (e.g., initial DL BWP, DL subband, DL usable PRBs, etc.) and applied equally.

[0178] The methods described in this disclosure are not limited to specific scenarios and types and may be applied to other scenarios and types, and may be used in a single or multiple combination depending on the conditions.

[0179] The UL subband described in this disclosure represents a time and frequency range in which uplink transmission is possible in DL and / or flexible symbols, and may be replaced by 'UL usable PRBs', which refers to the overlapping area between the UL subband and the active UL BWP in the context of this disclosure, which targets the transmission and reception operations of an actual terminal. Likewise, the DL subband and the DL usable PRBs may also be regarded as the same in this disclosure.

[0180] With respect to the function(s) described in this disclosure, the terminal may notify the base station of whether it supports them, and the base station may transmit different information to the terminal depending on the function(s) supported by the terminal. In addition, some of the details proposed in this disclosure may be equally applicable to other methods.

[0181] The configuration of the UL subband described in this disclosure can be transmitted via RRC signaling and can basically be provided after the configuration of the TDD common.

[0182] The methods described in this disclosure can be utilized in unlicensed bands as well as licensed bands, and can be extended to uplink transmission power in sidelinks and supplementary uplinks (SULs).

[0183] With respect to the function(s) described in the present disclosure, the terminal may report to the base station whether it supports the said function when reporting capability, and the base station may perform signaling and operations related to the methods described in the present disclosure according to the terminal's capability.

[0184] The methods described in this disclosure may be applied together in a single or multiple combinations and may be applied commonly regardless of the RRC state.

[0185] The methods described in this disclosure may be applied to various subsequent types of RACH procedures, such as 4-step RACH procedures as well as 2-step RACH procedures, and the names of messages or information defined in this disclosure may be varied.

[0186]

[0187] The operation of the method according to the present disclosure can be implemented as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes any type of recording device in which information that can be read by a computer system is stored. Additionally, a computer-readable recording medium may be distributed across networked computer systems, allowing the computer-readable program or code to be stored and executed in a distributed manner.

[0188] In addition, computer-readable recording media may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, and flash memory. Program instructions may include machine code, such as that generated by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc.

[0189] Some aspects of the present disclosure have been described in the context of a device, but may also be described according to a corresponding method, wherein a block or device corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method may also be described according to a corresponding block or item or a feature of a corresponding device. Some or all of the method steps may be performed by (or using) a hardware device, such as, for example, a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, at least one of the most important method steps may be performed by such a device.

[0190] A programmable logic device (e.g., a field-programmable gate array) may be used to perform some or all of the functions of the methods described in this disclosure. A field-programmable gate array may operate with a microprocessor to perform one of the methods described in this disclosure. Generally, it is preferable that the methods be performed by some hardware device.

[0191] Although the present disclosure has been described with reference to preferred embodiments, those skilled in the art will understand that various modifications and changes can be made to the present disclosure without departing from the spirit and scope of the present disclosure as set forth in the following claims.

Claims

1. In the method of the terminal, A step of receiving a first PDCCH order from a base station instructing a first CFRA (contention-free random access) procedure; A step of receiving a second PDCCH order from the base station instructing a second CFRA procedure while performing the first CFRA procedure; It includes a step of determining whether to continue the first CFRA procedure without performing the second CFRA procedure or to perform the second CFRA procedure based on the first information indicated by the second PDCCH order, The first information is information indicating a RACH (random access channel) occasion type (RO type) for the second CFRA procedure, or information indicating whether the second CFRA procedure is the same RA procedure as the first CFRA procedure. method.

2. In Claim 1, The first information is indicated by a field included in the DCI (downlink control information) of the PDCCH order, by reserved bit(s) included in the DCI, or by a radio network temporary identifier (RNTI) scrambled by the CRC (cyclic redundancy check) of the DCI, method.

3. In Claim 1, The above terminal is an SBFD UE (user equipment) that supports SBFD (subband full duplexing), and the above RO type is a legacy RO or an additional RO, method.

4. In Claim 1, The above first information is information indicating a second RO type for the second CFRA procedure, and the first PDCCH order and the second PDCCH order indicate the same preamble index and / or the same PRACH (physical random access channel) mask index, and if the second RO type is the same as the first RO type for the first CFRA procedure, the terminal does not perform the second CFRA procedure and continues the first CFRA procedure. method.

5. In Claim 1, The above first information is information indicating a second RO type for the above second CFRA procedure, and the first PDCCH order and the second PDCCH order indicate the same preamble index and / or PRACH mask index, and if the above second RO type is different from the first RO type for the above first CFRA procedure, the terminal performs the above second CFRA procedure. method.

6. In Claim 1, The first information is information indicating whether the second CFRA procedure is the same RA procedure as the first CFRA procedure, and if the first information indicates that the second CFRA procedure is the same RA procedure as the first CFRA procedure, the terminal does not perform the second CFRA procedure and continues the first CFRA procedure. method.

7. In Claim 1, The first information is information indicating whether the second CFRA procedure is the same RA procedure as the first CFRA procedure, and if the first information indicates that the second CFRA procedure is a different RA procedure from the first CFRA procedure, the terminal performs the second CFRA procedure. method.

8. Regarding the base station method, A step of transmitting a first PDCCH order instructing the terminal to perform a first CFRA (contention-free random access) procedure; A step of transmitting a second PDCCH order instructing the terminal to perform a second CFRA procedure while performing the first CFRA procedure with the terminal; and Based on the first information directed by the second PDCCH order, the method includes the step of continuously performing the first CFRA procedure or performing the second CFRA procedure without performing the second CFRA procedure with the terminal, and The first information is information indicating a RACH (random access channel) occasion type (RO type) for the second CFRA procedure, or information indicating whether the second CFRA procedure is the same RA procedure as the first CFRA procedure. method.

9. In Claim 8, The first information is indicated by a field included in the DCI (downlink control information) of the PDCCH order, by reserved bit(s) included in the DCI, or by a radio network temporary identifier (RNTI) scrambled by the CRC (cyclic redundancy check) of the DCI, method.

10. In Claim 8, The above terminal is an SBFD UE (user equipment) that supports SBFD (subband full duplexing), and the above RO type is a legacy RO or an additional RO, method.

11. In Claim 8, If the first information is information indicating a second RO type for the second CFRA procedure, and the first PDCCH order and the second PDCCH order indicate the same preamble index and / or the same PRACH (physical random access channel) mask index, and the second RO type is the same as the first RO type for the first CFRA procedure, the base station does not perform the second CFRA procedure with the terminal and continues the first CFRA procedure. method.

12. In claim 8, The above first information is information indicating a second RO type for the above second CFRA procedure, and the first PDCCH order and the second PDCCH order indicate the same preamble index and / or PRACH mask index, and if the above second RO type is different from the first RO type for the above first CFRA procedure, the base station performs the above second CFRA procedure with the terminal. method.

13. In claim 8, The first information is information indicating whether the second CFRA procedure is the same RA procedure as the first CFRA procedure, and if the first information indicates that the second CFRA procedure is the same RA procedure as the first CFRA procedure, the base station does not perform the second CFRA procedure with the terminal and continues the first CFRA procedure. method.

14. In Claim 8, The first information is information indicating whether the second CFRA procedure is the same RA procedure as the first CFRA procedure, and if the first information indicates that the second CFRA procedure is a different RA procedure from the first CFRA procedure, the base station performs the second CFRA procedure with the terminal. method.

15. In a terminal comprising at least one processor, the at least one processor is: the terminal A step of receiving a first PDCCH order from a base station instructing a first CFRA (contention-free random access) procedure; A step of receiving a second PDCCH order from the base station instructing a second CFRA procedure while performing the first CFRA procedure; Performing a step of determining whether to continue the first CFRA procedure without performing the second CFRA procedure or to perform the second CFRA procedure based on the first information indicated by the second PDCCH order, and The first information is information indicating a RACH (random access channel) occasion type (RO type) for the second CFRA procedure, or information indicating whether the second CFRA procedure is the same RA procedure as the first CFRA procedure. Terminal.

16. In Claim 15, The above terminal is an SBFD UE (user equipment) that supports SBFD (subband full duplexing), and the above RO type is a legacy RO or an additional RO, Terminal.

17. In Claim 15, If the first information is information indicating a second RO type for the second CFRA procedure, and the first PDCCH order and the second PDCCH order indicate the same preamble index and / or the same PRACH (physical random access channel) mask index, and the second RO type is the same as the first RO type for the first CFRA procedure, the at least one processor causes the terminal to continue the first CFRA procedure without performing the second CFRA procedure. Terminal.

18. In Claim 15, The first information is information indicating a second RO type for the second CFRA procedure, and the first PDCCH order and the second PDCCH order indicate the same preamble index and / or PRACH mask index, and if the second RO type is different from the first RO type for the first CFRA procedure, the at least one processor causes the terminal to perform the second CFRA procedure. Terminal.

19. In Claim 15, The first information is information indicating whether the second CFRA procedure is the same RA procedure as the first CFRA procedure, and if the first information indicates that the second CFRA procedure is the same RA procedure as the first CFRA procedure, the at least one processor causes the terminal to continue the first CFRA procedure without performing the second CFRA procedure. Terminal.

20. In Claim 15, The first information is information indicating whether the second CFRA procedure is the same RA procedure as the first CFRA procedure, and if the first information indicates that the second CFRA procedure is a different RA procedure from the first CFRA procedure, the at least one processor causes the terminal to perform the second CFRA procedure. Terminal.