Method and apparatus for random access in communication system supporting sbfd

By determining RO types and configuring RAR windows based on PDCCH orders, the method addresses ambiguity in SBFD networks, ensuring reliable and efficient random access procedures.

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

Patent Information

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

AI Technical Summary

Technical Problem

In communication networks supporting subband full duplex (SBFD), the ambiguity in selecting random access channel (RACH) occasions and unclear random access response (RAR) windows during contention-based random access (CBRA) leads to potential RA procedure failures due to unclear criteria for RO type selection and duplicate preamble transmissions.

Method used

A method for user equipment (UE) to determine the appropriate RO type based on the existence of legacy and additional ROs, using a physical downlink control channel (PDCCH) order, and configure a single RAR window for receiving random access responses (RARs), with retransmission options if necessary, to ensure reliable RA procedures.

Benefits of technology

This approach defines clear criteria for selecting RACH occasions, reduces connection delay, and enhances the efficiency of the RA procedure by mitigating connection delays and ensuring successful random access in SBFD environments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026095935_12112026_PF_FP_ABST
    Figure KR2026095935_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Disclosed are a method and an apparatus for random access in a communication system supporting SBFD. A method of a user equipment (UE) comprises the steps of: receiving a physical downlink control channel (PDCCH) order from a base station; transmitting a preamble to the base station in one random access channel (RACH) occasion (RO) type or different RO types on the basis of the PDCCH order; and performing monitoring for reception of one or more random access responses (RARs) in response to the preamble.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for random access in a communication system supporting SBFD

[0001] The present disclosure relates to an improved communication technology, and more specifically, to a technology for random access in a communication system that supports SBFD (subband full duplex).

[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, communication networks can support subband full duplex (SBFD) operation. Random access (RA) procedures can be performed in communication networks that support SBFD. Physical random access channel (PRACH) resources can be classified into legacy RACH occasions and additional ROs. When contention-based random access (CBRA) is triggered by a physical downlink control channel (PDCCH) order, ambiguity regarding the RO type for preamble transmission may arise because clear criteria are not defined for which RO type the terminal selects to transmit the preamble. When preambles are transmitted for each of multiple RO types, problems may occur upon RAR reception because the setting of the random access response (RAR) window for each preamble is not clearly defined. If a preamble is transmitted repeatedly based on the same ID, it may be determined as a duplication of the RA procedure, causing the RA procedure to fail. A method for random access is required to resolve the aforementioned problems.

[0005] The objective of the present disclosure to solve the above-mentioned problems is to provide a method and apparatus for random access in a communication system that supports SBFD (subband full duplex).

[0006] A method of user equipment (UE) according to embodiments of the present disclosure for achieving the above objective comprises: receiving a physical downlink control channel (PDCCH) order from a base station; transmitting a preamble to the base station in one random access channel (RACH) occasion type or different RO types based on the PDCCH order; and performing monitoring for receiving one or more random access responses (RARs) in response to the preamble, wherein the different RO types include a legacy RO and an additional RO, the legacy RO is set in one or more non-SBFD (subband full duplex) symbols, and the additional RO is set in one or more symbols including at least one of non-SBFD symbols or SBFD symbols.

[0007] The step of transmitting the preamble to the base station may include: determining one RO type among the legacy RO and the additional RO based on the existence of the legacy RO and the additional RO having the same index as the PRACH (physical random access channel) mask index included in the PDCCH order; and transmitting the preamble to the base station in the determined RO type.

[0008] The RO type indicated by the above base station can be determined as one RO type for the transmission of the above preamble.

[0009] One RO type for the transmission of the above preamble can be determined based on the result of comparing the measured RSRP (reference signal received power) and the RSRP threshold.

[0010] The RO type used in the RA (random access) procedure during the initial access phase or in the RA procedure prior to the reception of the PDCCH order can be determined as one RO type for the transmission of the preamble.

[0011] The above PDCCH order may include information instructing the transmission of the preamble in each of the above different RO types.

[0012] The above one or more RARs may be received in a single RAR window, and the single RAR window may be configured based on the RO type to which the first preamble was transmitted or the RO type to which the last preamble was transmitted.

[0013] The method of the above UE may further include the step of receiving from the base station information indicating an RO type which is a setting criterion for a single RAR window in which the one or more RARs are received, and the single RAR window may be set based on the RO type indicated by the base station.

[0014] Each of the above one or more RARs may include information indicating the RO type to which the preamble associated with the RAR was transmitted.

[0015] The step of performing monitoring for receiving one or more of the above RARs may include the step of performing decoding for the RAR PDCCH (physical downlink control channel) based on at least one of the RA-RNTI (random access-radio network temporary identifier) ​​based on the legacy RO to which the preamble was transmitted or the RA-RNTI based on the additional RO to which the preamble was transmitted.

[0016] The above method of the UE may further include the step of retransmitting the preamble in one RO type based on the fact that one or more RARs are not received within one RAR window.

[0017] Based on the fact that the above one RAR window is set based on the legacy RO, the preamble can be retransmitted from the legacy RO, and based on the fact that the above one RAR window is set based on the additional RO, the preamble can be retransmitted from the additional RO.

[0018] User equipment (UE) according to embodiments of the present disclosure for achieving the above objective comprises at least one processor, wherein the at least one processor causes the UE to receive a physical downlink control channel (PDCCH) order from a base station; transmit a preamble to the base station in one random access channel (RACH) occasion type or different RO types based on the PDCCH order; and perform monitoring for receiving one or more random access responses (RARs) in response to the preamble, wherein the different RO types include a legacy RO and an additional RO, wherein the legacy RO is set in one or more non-SBFD (subband full duplex) symbols, and the additional RO may be set in one or more symbols including at least one of non-SBFD symbols or SBFD symbols.

[0019] To transmit the above preamble to the base station, the at least one processor can determine one RO type among the legacy RO and the additional RO based on the existence of the legacy RO and the additional RO having an index identical to the PRACH (physical random access channel) mask index included in the PDCCH order; and cause the preamble to be transmitted to the base station in the determined RO type.

[0020] The RO type indicated by the above base station can be determined as one RO type for the transmission of the above preamble.

[0021] One RO type for the transmission of the above preamble can be determined based on the result of comparing the measured RSRP (reference signal received power) and the RSRP threshold.

[0022] The above PDCCH order may include information instructing the transmission of the preamble in each of the above different RO types.

[0023] The above one or more RARs may be received in a single RAR window, and the single RAR window may be configured based on the RO type to which the first preamble was transmitted or the RO type to which the last preamble was transmitted.

[0024] The above at least one processor may further cause the UE to receive from the base station information indicating an RO type which is a setting criterion for a RAR window in which the one or more RARs are received, and the one RAR window may be set based on the RO type indicated by the base station.

[0025] In monitoring for receiving one or more of the above RARs, the at least one processor may cause the UE to perform decoding for the RAR PDCCH (physical downlink control channel) based on at least one of the RA-RNTI (random access-radio network temporary identifier) ​​based on the legacy RO to which the preamble was transmitted or the RA-RNTI based on the additional RO to which the preamble was transmitted.

[0026] According to the present disclosure, in a communication system supporting subband full duplex (SBFD), criteria for selecting a random access channel (RACH) occasion to be used by a terminal during the execution of contention-based random access (CBRA) (e.g., PDCCH order-based CBRA) can be defined, and accordingly, the random access (RA) procedure can be performed reliably. A method for mitigating connection delay during the execution of PDCCH order-based CBRA can be provided, and accordingly, the RA procedure can be completed quickly. Based on the methods proposed in the present disclosure, the efficiency of the RA procedure can be improved, and the connection delay of the terminal can be reduced.

[0027] FIG. 1 is a conceptual diagram illustrating embodiments of a communication system.

[0028] FIG. 2 is a block diagram illustrating embodiments of communication nodes constituting a communication system.

[0029] FIG. 3 is a block diagram illustrating embodiments of communication nodes performing communication.

[0030] FIG. 4a is a block diagram illustrating embodiments of a transmission path.

[0031] FIG. 4b is a block diagram illustrating embodiments of a receiving path.

[0032] FIG. 5 is a conceptual diagram illustrating embodiments of a system frame in a communication system.

[0033] FIG. 6 is a conceptual diagram illustrating embodiments of subframes in a communication system.

[0034] FIG. 7 is a conceptual diagram illustrating embodiments of slots in a communication system.

[0035] FIG. 8 is a conceptual diagram illustrating embodiments of time-frequency resources in a communication system.

[0036] FIGS. 9a, 9b, and 9c are conceptual diagrams illustrating the transmission method of a preamble in a PDCCH order-based RA procedure.

[0037] FIGS. 10a and FIGS. 10b are conceptual diagrams illustrating the configuration of a CORESET for receiving a RAR PDCCH in a PDCCH order-based RA procedure.

[0038] Figure 11 is a conceptual diagram illustrating an RA procedure triggered by a PDCCH order.

[0039] 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.

[0040] 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.

[0041] 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".

[0042] 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".

[0043] 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.

[0044] 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.

[0045] 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.

[0046] 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.

[0047] 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.

[0048] 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 board unit), etc.

[0049] In the present disclosure, signaling may be at least one of upper-layer signaling, MAC (medium access control) 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 (radio resource control) 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)).

[0050] 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." In the present disclosure, "time" and "time point" may be used interchangeably. "Time" may be interpreted as a time or a time point depending on the context, and "time point" may be interpreted as a time point or a time depending on the context.

[0051] In the present disclosure, a phrase containing "~ case (e.g., when ~)" may be expressed as a phrase containing "~ based on (e.g., based on ~)" or a phrase containing "~ in response to (e.g., in response to ~)". In other words, a phrase containing "~ case" may be interpreted as identical or similar to a phrase containing "~ based on" or a phrase containing "~ in response to".

[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 embodiments 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 embodiments of communication nodes 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 embodiments 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 embodiments of a transmission path, and FIG. 4b is a block diagram illustrating embodiments 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 (412), 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 embodiments 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 embodiments of subframes 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 embodiments of slots 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]

[0091] 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.

[0092] 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.

[0093] 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."

[0094] 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.

[0095] 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.

[0096] FIG. 8 is a conceptual diagram illustrating embodiments of time-frequency resources in a communication system.

[0097] 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.

[0098] In the present disclosure, RB may mean a common RB (CRB). Alternatively, RB may mean a physical RB (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) with respect to 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.

[0099] 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.

[0100] 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.

[0101] 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).

[0102] 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.

[0103] 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).

[0104] Meanwhile, communication systems (e.g., NR communication systems, 5G communication systems, 6G communication systems) can support usage scenarios such as eMBB (enhanced Mobile BroadBand), URLLC (Ultra Reliable Low Latency Communication), and mMTC (massive Machine Type Communication). Communication systems (e.g., communication networks) can support SBFD (subband full duplex) operation.

[0105] A communication system may support the time division duplexing (TDD) method. In a communication system that supports the TDD method (hereinafter referred to as the "TDD communication system"), DL (downlink) symbol(s) and UL (uplink) symbol(s) may be set in different time resources within a single carrier. DL symbols and UL symbols may be associated with coverage and / or latency. In a TDD communication system, the base station can utilize resources more efficiently than the frequency division duplexing (FDD) method by considering various use cases. Resource scheduling operations of the base station in a TDD communication system may be important. For enhanced TDD operation, SBFD operations (e.g., SBFD method) may be supported. If SBFD operations are supported in a TDD communication system, DL communication (e.g., transmission and reception of DL signals) and UL communication (e.g., transmission and reception of UL signals) may be performed simultaneously within the same time resource. For example, within the same time resource, some subbands may be DL subbands, and other subbands may be UL subbands and / or FL subbands. In this disclosure, the DL signal may be interpreted as a DL signal, a DL channel, or "DL signal and DL channel" depending on the context. In this disclosure, the UL signal may be interpreted as a UL signal, a UL channel, or "UL signal and UL channel" depending on the context.

[0106] Symbols to which SBFD operations are applied may be referred to as SBFD symbols. Symbols to which SBFD operations are not applied may be referred to as N(non)-SBFD symbols. N-SBFD symbols may be DL symbols, UL symbols, or FL symbols. In an SBFD symbol, the terminal can perform DL communication and UL communication. In other words, in an SBFD symbol, the terminal can perform full-duplex operation. The base station may assume that DL communication and UL communication are possible in an SBFD symbol. In an N-SBFD symbol, the terminal can perform one of DL communication and UL communication. In other words, in an N-SBFD symbol, the terminal can perform half-duplex operation. An SBFD symbol may be a symbol that includes a subband to which SBFD operations are performed. The subband for SBFD may be referred to or interpreted as a UL subband. The UL subband can exist (e.g., be configured) within the symbol where the SSB (synchronization signal block) is transmitted.

[0107] Resources for SBFD operation (e.g., time resources and / or frequency resources) may be configured in a semi-static manner. In other words, the configuration for SBFD resources may be a semi-static configuration. "That the SBFD resource configuration is a semi-static configuration" may mean that the SBFD resource is configured by semi-static signaling (e.g., system information, RRC messages). In this disclosure, SBFD resources may refer to time resources and / or frequency resources for SBFD operation. UL subbands for SBFD may be SBFD resources. Alternatively, SBFD resources may be configured in a dynamic manner. "That the SBFD resource configuration is a dynamic configuration" may mean that the SBFD resource is configured by dynamic signaling (e.g., MAC CE, DCI, SCI).

[0108] SBFD resources (e.g., UL subband, SBFD symbol) may be configured within DL resources and / or FL (flexible) resources configured by TDD-UL-DL configuration common information (e.g., TDD-UL-DL-configCommon). In the time domain, the transition point from an N-SBFD symbol to an SBFD symbol may be limited to one. In the time domain, the transition point from an SBFD symbol to an N-SBFD symbol may be limited to one. Regarding the resource configuration of a subband for SBFD, it may be desirable for the terminal to be aware of the resource configuration information of the subband for SBFD in advance.

[0109] TDD-UL-DL configuration common information can be used to configure patterns (e.g., TDD-UL-DL-Pattern) for DL ​​resources and / or UL resources in the time domain of a TDD communication system. Patterns for DL ​​resources and / or UL resources may be referred to as UL / DL patterns. UL / DL patterns may change depending on the environment of the communication system (e.g., TDD communication system). Up to two UL / DL patterns may be configured on a terminal. TDD-UL-DL configuration common information may be cell-specific parameters (e.g., cell-specific configuration information). The base station may change the configuration for symbol(s) (e.g., transmission direction, type) on a terminal-by-terminal basis based on a specific slot within a preset UL / DL pattern. The slot where the symbol configuration (e.g., symbol direction, symbol type) can be changed may be a slot configured as an FL resource by the TDD-UL-DL configuration common information. The symbol direction (e.g., symbol transmission direction) and / or symbol type may be DL, UL, or FL. The RRC signaling used to change the configuration of an FL slot (e.g., FL resource) may be TDD-UL-DL configuration-dedicated information (e.g., TDD-UL-DL-ConfigDedicated). Table 2 may be TDD-UL-DL configuration common information, and Tables 3 and 4 may be TDD-UL-DL configuration-dedicated information.

[0110]

[0111]

[0112]

[0113] The UL / DL pattern, configured by the common information of the TDD-UL-DL configuration, may be repeated according to a specific period (e.g., dl-UL-TransmissionPeriodicity). In the time interval where the UL / DL pattern is applied, the leading portion may be configured as a DL resource. In the time interval where the UL / DL pattern is applied, the trailing portion may be configured as a UL resource. Resources that are not configured as DL or UL resources in the time interval where the UL / DL pattern is applied may be FL resources. The period of the UL / DL pattern may vary depending on the reference numerology. A guard time (e.g., guard gap) may be required for switching (e.g., transition) from a DL resource (e.g., DL symbol / slot) to a UL resource (e.g., UL symbol / slot). Since the propagation delay of the DL signal causes interference to the UL resource, a guard time may be required for switching from a DL resource to a UL resource. A separate guard time may not be required for switching from UL resources to DL resources. Since UL signals are transmitted based on TAC (timing advance command) directed by the base station, a guard time may not be required for switching from UL resources to DL resources.

[0114] TDD-UL-DL configuration common information (e.g., TDD-UL-DL-ConfigCommon) may be referred to as "TDD Common" or "TDD Common Information". TDD-UL-DL configuration dedicated information (e.g., TDD-UL-DL-ConfigDedicated) may be referred to as "TDD Dedicated" or "TDD Dedicated Information". UL subband may refer to a subband for SBFD. DL symbol(s) and / or DL ​​slot(s) may be referred to as DL area(or DL ​​resource). UL symbol(s) and / or UL slot(s) may be referred to as UL area(or UL resource). FL symbol(s) and / or FL slot(s) may be referred to as FL area(or FL resource). A terminal that supports (e.g. recognizes) SBFD operation may be referred to as an SBFD terminal or SBFD UE. A terminal that does not support (e.g., does not recognize) SBFD operation may be referred to as an N(non)-SBFD terminal or an N-SBFD UE. An N-SBFD terminal may be a legacy terminal (e.g., a legacy UE). In this disclosure, a terminal may be interpreted as an SBFD terminal and / or an N-SBFD terminal depending on the context. Legacy settings (e.g., legacy information, legacy settings information) may be information for an N-SBFD terminal.

[0115] An SBFD resource may be located adjacent to (e.g., contiguously) an N-SBFD resource. An SBFD resource may refer to an SBFD symbol and / or an SBFD slot. An N-SBFD resource may refer to an N-SBFD symbol and / or an N-SBFD slot. SBFD symbols and N-SBFD symbols may be located contiguously or discontinuously within a single slot. In slots (e.g., adjacent slots, contiguous slots), SBFD symbols and N-SBFD symbols may exist adjacently. The types of adjacent symbols (e.g., SBFD symbols or N-SBFD symbols) may be the same or different. The operation of the terminal may vary based on the types of adjacent symbols (e.g., the same symbol type or different symbol types).

[0116] A communication system supporting SBFD may support two SBFD configurations (e.g., SBFD configuration 1, SBFD configuration 2). SBFD configuration 1 may be referred to as configuration 1, SBFD transmission configuration 1, or SBFD configuration 1 transmission. SBFD configuration 2 may be referred to as configuration 2, SBFD transmission configuration 2, or SBFD configuration 2 transmission. If SBFD configuration 1 is configured on a terminal (e.g., indicated), the terminal may perform communication (e.g., downlink communication and / or uplink communication) using the same symbol type (e.g., SBFD symbol or N-SBFD symbol). If SBFD configuration 2 is configured on a terminal (e.g., indicated), the terminal may perform communication (e.g., downlink communication and / or uplink communication) using different symbol types (e.g., SBFD symbol and N-SBFD symbol). An SBFD terminal may operate based on one of SBFD settings, either SBFD setting 1 or SBFD setting 2. Among SBFD setting 1 and SBFD setting 2, SBFD setting 1 may be the default setting. For example, if there is no separate instruction regarding SBFD settings, the SBFD terminal may operate based on SBFD setting 1. If the base station instructs the terminal to SBFD setting 2 (for example, if SBFD setting 2 is enabled), the SBFD terminal may operate based on SBFD setting 2. Symbol types may be classified into SBFD symbols and N-SBFD symbols. Depending on the context, a symbol type may be interpreted as a symbol having the said symbol type (e.g., a resource).

[0117] Meanwhile, in a communication system supporting SBFD, RACH (random access channel) setting 1 (e.g., Option 1) and RACH setting 2 (e.g., Option 2) may be supported. In a scenario where RACH setting 1 is applied, an RA procedure (e.g., PRACH transmission) in an SBFD resource may be performed based on a legacy RACH setting (e.g., legacy RACH setting information). A legacy RACH setting may refer to a RACH setting used for an RA procedure in an N-SBFD resource. In a scenario where RACH setting 2 is applied, additional RACH settings (e.g., additional RACH setting information) may be additionally set in addition to the legacy RACH setting, and an RA procedure in an N-SBFD resource may be performed based on the legacy RACH setting, while an RA procedure in an SBFD resource may be performed based on the additional RACH setting. Additional RACH setting information may be referred to as SBFD RACH setting information.

[0118] An additional RO (RACH occasion) may be configured differently depending on RACH settings 1 and 2. In scenarios where RACH setting 1 applies, an additional RO may refer to an RO configured only on SBFD symbols and an RO configured across SBFD symbols and N-SBFD symbols. In scenarios where RACH setting 2 applies, an additional RO may refer to an RO configured based on SBFD RACH settings. A legacy RO may refer to an RO configured based on legacy RACH settings. A legacy RO may be configured (e.g., located) on N-SBFD symbols. A legacy RO may be referred to as a first PRACH occupation and may be used for legacy terminals that do not support SBFD. An additional RO may be configured (e.g., located) on at least one of N-SBFD symbols or SBFD symbols. An additional RO may be referred to as a second PRACH occupation and may be used for SBFD terminals that support SBFD.

[0119] Based on the SBFD RACH configuration, there may be ROs configured in the N-SBFD resource. The SBFD terminal may determine (e.g., decide) that the RO configured in the N-SBFD resource is an invalid RO according to the SBFD RACH configuration, and may not perform a msg1 transmission or a msgA transmission on the invalid RO. In other words, the SBFD terminal may expect a msg1 transmission on the RO configured by the legacy RACH configuration within the N-SBFD resource, and may expect a msg1 transmission on the RO configured by the SBFD RACH configuration within the SBFD resource. In this disclosure, a msg1 transmission may be interpreted to include not only a msg1 transmission but also a msgA transmission. Transmit power parameters for the legacy RACH configuration and the SBFD RACH configuration, respectively, may be configured independently. An SBFD terminal operating in an RRC connected state can support CBRA (contention-based random access), CFRA (contention-free random access), and PDCCH order-based RA. PDCCH order-based RA may include PDCCH order-based CBRA and / or PDCCH order-based CFRA.

[0120] An SBFD terminal can perform CBRA on SBFD symbol(s). For example, an SBFD terminal can transmit a preamble (e.g., msg1, msgA) on the RO set in the SBFD symbol(s) as well as on the RO set in the N-SBFD symbol(s). RO types can be classified into legacy ROs and additional ROs. In scenarios where RACH setting 1 applies, the RA procedure can be performed based on a single RACH setting. In scenarios where RACH setting 2 applies, RACH settings independent of each RO type may exist. In scenarios where RACH setting 1 applies, additional ROs can be set based on a single RACH setting and may refer to the RO set in the SBFD symbol(s). In scenarios where RACH setting 2 applies, additional ROs can be determined based on settings additionally signaled for the SBFD terminal. In a scenario where RACH setting 2 applies, RO(s) spanning SBFD symbol(s) and N-SBFD symbol(s) may be indicated by additional RO settings, but the SBFD terminal may expect to transmit a preamble from the RO set in the SBFD symbol(s), and the SBFD terminal may not expect to transmit a preamble from the RO set in the N-SBFD symbol(s). In a scenario where RACH setting 2 applies, the additional RO may be the RO set in the SBFD symbol(s), and the legacy RO may be the RO set in the N-SBFD symbol(s).

[0121] A PDCCH order-based RA procedure may be triggered by the MAC layer or the RRC layer depending on an event. The terminal may perform an RA procedure (e.g., a PDCCH order-based RA procedure) based on parameter(s) set by RRC signaling. A PDCCH order-based RA procedure may be a PDCCH order-based CBRA procedure and / or a PDCCH order-based CFRA procedure. The difference between CBRA and CFRA may be a difference in values ​​indicated by the RA preamble index field within the DCI. If the values ​​of the RA preamble index field within the DCI are all set to 0, this may indicate that a CBRA procedure is performed. If the field value of the RA preamble index within the DCI indicates a non-zero value (e.g., a preamble index available to the terminal (e.g., 1 to 63)), this may indicate that a CFRA procedure is performed. In order to prevent collisions in preamble transmissions between terminals in a CFRA procedure, an RO as well as a preamble index may be set on the terminal. Information regarding the RO may include an SSB index and a PRACH mask index. In a PDCCH order-based CFRA procedure, the value of the RA preamble index field within the DCI may be interpreted as a reserved bit.

[0122] Considering SBFD operations (e.g., SBFD terminals), for a CFRA procedure, the DCI may further include a field (e.g., a field having a size of 1 bit) indicating an RO type (e.g., legacy RO or additional RO). In this disclosure, a CBRA procedure may be interpreted as a normal CBRA procedure or a PDCCH order-based CBRA procedure depending on the context. In other words, the embodiments of this disclosure may be applied to a normal CBRA procedure and / or a PDCCH order-based CBRA procedure. The embodiments of this disclosure may be applied not only to CBRA procedures but also to CFRA procedures (e.g., PDCCH order-based CFRA procedures). In this disclosure, a PDCCH order-based RA procedure may be interpreted as a PDCCH order-based CBRA procedure and / or a PDCCH order-based CFRA procedure depending on the context. The embodiments of this disclosure may be applied to a four-step RA procedure and / or a two-step RA procedure. Even if the embodiments of the present disclosure are described with respect to a four-step RA procedure, said embodiments may be applied to a two-step RA procedure as well as a four-step RA procedure. Alternatively, even if the embodiments of the present disclosure are described with respect to a two-step RA procedure, said embodiments may be applied to a four-step RA procedure as well as a two-step RA procedure. The proposals described in the present disclosure and details thereof may be applied to such proposals as well as other proposals.

[0123] In the initial access phase, the RO type to which the terminal transmits the preamble may be selected based on the determination of RAN2. For example, the base station may transmit information on the RO type to the terminal via signaling (e.g., SIB, RRC message). If such signaling is not present, the terminal may select the RO type based on the reference signal received power (RSRP). The operation described above may be applied in the initial access phase, and the method for selecting the RO type in a PDCCH order-based RA procedure is not clearly defined. The RO type for a CFRA procedure may be set (e.g., indicated) by a field included in the DCI. The terminal may expect to transmit the preamble in an RO having the RO type indicated by the base station. Similar to the method described above, a method for determining (e.g., selecting) the RO type for a CBRA procedure (e.g., a PDCCH order-based CBRA procedure) may also be required.

[0124] Unlike general CBRA procedures, in PDCCH order-based CBRA procedures, a terminal in an RRC connection state can perform a CBRA procedure based on a PDCCH order received from the base station. In other words, a CBRA procedure can be triggered by a PDCCH order. For a PDCCH order-based CBRA procedure, preamble and resource information may not be instructed to the terminal beforehand. In the above-described situation, if a CBRA procedure is triggered by a PDCCH order without a selection criterion for the RO type, the terminal may transmit a preamble (e.g., msg1, msgA) to both the legacy RO and the additional RO, or transmit a preamble to either the legacy RO or the additional RO.

[0125] FIGS. 9a, 9b, and 9c are conceptual diagrams illustrating the transmission method of a preamble in a PDCCH order-based RA procedure.

[0126] Referring to FIGS. 9a, 9b, and 9c, an RA procedure (e.g., a CBRA procedure and / or a CFRA procedure) may be triggered by a PDCCH order, and the criteria for determining the RO type for transmitting a preamble (e.g., msg1, msgA) may not be clearly defined. In the embodiment of FIG. 9a, the terminal may transmit the preamble on both the legacy RO and the additional RO. In the embodiment of FIG. 9b, the terminal may transmit the preamble on the legacy RO. In the embodiment of FIG. 9c, the terminal may transmit the preamble on the additional RO.

[0127] As described above, ambiguity issues regarding the determination of the RO type at the terminal may occur, which may increase the probability of failure in transmitting or receiving the preamble. To resolve the aforementioned problem, the operation of the terminal in the PDCCH order-based RA procedure needs to be clearly defined.

[0128] ● Proposal #1

[0129] When an RA procedure is triggered by a PDCCH order, the terminal may select one RO type and transmit a preamble in the selected RO type (e.g., an RO having the selected RO type). Legacy ROs and additional ROs having values ​​indicated by the PRACH mask index included in the PDCCH order may exist. In other words, legacy ROs and additional ROs having the same PRACH mask index may be configured. At this time, the terminal may select (e.g., determine) one RO type for the PDCCH order-based RA procedure based on the method of selecting the RO type in the legacy RACH procedure (e.g., a RACH procedure for an N-SBFD terminal). The terminal may select (e.g., determine) a preamble for the PDCCH order-based RA procedure based on the method of selecting the preamble in the legacy RACH procedure. The selection of the RO type may be performed based on one of the methods below or a combination of two or more methods. At least one of the methods below may be applied selectively depending on the conditions. For example, if there is no signaling from the base station, the terminal may select an RO type according to predefined criteria, as in Method #1, or select the RO type used for the most recent preamble transmission, as in Method #3. As another example, if signaling from the base station is present, as in Method #4, the terminal may select the RO type indicated by the base station. A specific method may be applied preferentially. If it is impossible to apply the method with priority, another method may be used.

[0130] - Method #1: The terminal selects the RO type based on specific criteria.

[0131] Separate criteria for selecting the RO type may be defined, and the terminal may select the RO type according to the criteria. The criteria may be received signal strength (e.g., RSRP), time (e.g., timer, window), etc. The criteria may be a combination of various conditions. The criterion for selecting the RO type may be received signal strength (e.g., RSRP). In this case, the terminal may measure the RSRP of the SSB by performing SSB monitoring (e.g., monitoring all or some SSBs associated with the RO corresponding to each RO type) and determine the RO type based on the measured RSRP. For example, the terminal may determine the RO type of the RO associated with the SSB having a measured RSRP above the RSRP threshold as the RO type for preamble transmission. Here, the RSRP threshold may be the same as the RSRP threshold for selecting the RO type in the legacy RACH procedure.

[0132] In other words, the terminal can measure the RSRP for the SSB associated with the legacy RO and / or the SSB associated with the additional RO, select the SSB having a measured RSRP greater than the RSRP threshold set for the existing RACH procedure (e.g., 4-stage RACH procedure, 2-stage RACH procedure), and attempt to transmit a preamble in the RO type associated with the selected SSB.

[0133] In a PDCCH order-based RA procedure, a separate RSRP threshold for selecting the RO type may be set on the terminal, and the terminal may determine the RO type for preamble transmission based on the separate RSRP threshold. In a PDCCH order-based RA procedure, the RSRP threshold may be set independently of the RSRP threshold in a legacy RACH procedure (e.g., a RACH procedure for an N-SBFD terminal). In a PDCCH order-based RA procedure, the RSRP threshold for selecting the RO type may be referred to as the additional RSRP threshold, and in a legacy RACH procedure, the RSRP threshold for selecting the RO type may be referred to as the legacy RSRP threshold. The additional RSRP threshold may be the RSRP threshold for SBFD symbol(s) (e.g., additional RO).

[0134] SBFD operation may be introduced to reduce latency. Therefore, it may be desirable for the terminal to connect to the base station without retrying the preamble transmission. An additional RSRP threshold may be set to a value greater than the legacy RSRP threshold. The terminal may preferentially expect a preamble transmission from an additional RO and may perform measurements on the SSB(s) associated with the additional RO(s). If there is an SSB satisfying the additional RSRP threshold, the terminal may transmit the preamble from the additional RO associated with that SSB. If there is no SSB satisfying the additional RSRP threshold, but there is an SSB satisfying the legacy RSRP threshold, the terminal may transmit the preamble from the legacy RO associated with the SSB satisfying the legacy RSRP threshold.

[0135] In another embodiment, the selection criteria for the RO type may be a window or a timer. If an RO type designated by the base station or a default RO type exists within the window (e.g., time corresponding to the timer), the terminal may transmit a preamble from the RO type designated by the base station or the default RO type. The default RO type may be a legacy RO or an additional RO. If an RO type designated by the base station or a default RO type does not exist within the window (e.g., time corresponding to the timer), the terminal may transmit a preamble from an RO type not designated by the base station, an RO type other than the default RO type, or the nearest RO type. The nearest RO type may be determined independently of the RO type.

[0136] The combination of the RSRP and the window (e.g., a timer) described above can be used as a selection criterion for the RO type. For example, a default RO type may be set in the terminal, and the terminal may determine the RO type based on the result of comparing the measured RSRP of the SSB with the RSRP threshold in the window (e.g., a period corresponding to the timer) after the triggering of the RA procedure. The default RO type (e.g., an RO type defined in the technical specifications) or the RO type designated by the base station may have priority, and the terminal may primarily perform measurements on the SSB associated with the RO type having priority in the window (e.g., a period corresponding to the timer), and determine the RO type by comparing the measured RSRP of the SSB with the RSRP threshold. If, within a window (e.g., a period corresponding to a timer), there is no SSB with a measured RSRP above the RSRP threshold, or if measurement of an SSB associated with a priority RO type is impossible, the terminal may select an RO type other than the default RO type or the RO type designated by the base station, and transmit a preamble in the other RO type. The other RO type may be selected according to the implementation of the terminal.

[0137] The start time of the window or the start time of the timer may be the first or last symbol among the symbols received that trigger the RA procedure PDCCH order. Or, the start time of the window or the start time of the timer may be the first or last symbol of the slot where the PDCCH order triggering the RA procedure is received.

[0138] - Method #2: Select the RO type used in the standard CBRA procedure

[0139] When an RA procedure is triggered by a PDCCH order, the terminal can select an RA procedure or an RO type used in a previous RA procedure during the initial connection phase, and can transmit a preamble from an RO having the selected RO type.

[0140] - Method #3: Select the RO type used in the most recent preamble transmission prior to the PDCCH order-based RA procedure

[0141] The terminal may select the RO type used for the most recent preamble transmission prior to the reception of the PDCCH order triggering the RA procedure, and may transmit the preamble in the RO having the selected RO type. The most recent preamble transmission may be determined regardless of the type of RA procedure. For example, the most recent preamble transmission may be a preamble transmission in a general CBRA procedure, a PDCCH order-based RA procedure, or a CFRA procedure.

[0142] - Method #4: Select the RO type specified by the base station

[0143] A base station may explicitly indicate (e.g., set) the RO type to the terminal, and the terminal may expect to transmit a preamble at the RO corresponding to the RO type indicated by the base station. A PDCCH (e.g., a PDCCH order) may include a field indicating the RO type (e.g., a field having a size of 1 bit), and the terminal may identify the RO type indicated by the field included in the PDCCH and transmit a preamble at the RO having the identified RO type. Alternatively, the base station may transmit system information (or an RRC message) containing information indicating the RO type to the terminal. The RO type indicated by the system information (or an RRC message) may be transmitted for the selection of the RO type in a standard CBRA procedure. When an RA procedure is triggered by a PDCCH order, the terminal may expect to transmit a preamble at the RO corresponding to the RO type indicated by the system information (or an RRC message). In other words, the system information (or RRC message) indicates an RO type for a general CBRA procedure, but the terminal can perform a PDCCH order-based RA procedure by referring to the RO type indicated by the system information (or RRC message).

[0144] Meanwhile, a combination of the above-described method #1 and method #4 may be used to determine the RO type. The terminal can check whether the RO type has been set by the base station. If the RO type has been set by the base station to the terminal (e.g., if the RACH setting information includes the RO type), the terminal can determine the RO type for which the transmission of the RA preamble (e.g., the initial RA preamble) is performed based on the RO type. Based on the RO type indicating a legacy RO, the terminal can determine the legacy RO as the initial RO type and start the transmission of the RA preamble from the legacy RO. Based on the RO type indicating an additional RO, the terminal can determine the additional RO as the initial RO type and start the transmission of the RA preamble from the additional RO.

[0145] If the RO type is not set to the terminal by the base station (e.g., if the RACH setting information does not include the RO type), the terminal can determine the RO type for which the transmission of the RA preamble (e.g., the initial RA preamble) is performed based on the RSRP threshold of the RO type and the use of the RSRP threshold. If the use of the RSRP threshold of the RO type is set to below, the terminal can determine an additional RO as the initial RO type if the measured RSRP of the DL signal (e.g., SSB, PT-RS, CSI-RS, DM-RS) is less than the RSRP threshold of the RO type. If the use of the RSRP threshold of the RO type is set to below, the terminal can determine a legacy RO as the initial RO type if the measured RSRP of the DL signal is not less than the RSRP threshold of the RO type.

[0146] When the RSRP threshold usage of the RO type is set to above, the terminal may determine an additional RO as the initial RO type if the measured RSRP of a DL signal (e.g., SSB, PT-RS, CSI-RS, DM-RS) is greater than the RSRP threshold of the RO type. When the RSRP threshold usage of the RO type is set to above, the terminal may determine a legacy RO as the initial RO type if the measured RSRP of a DL signal is not greater than the RSRP threshold of the RO type.

[0147] ● Proposal #2

[0148] The base station may transmit a PDCCH order to the terminal to trigger an RA procedure. The terminal may receive the PDCCH order from the base station and, based on this, determine that the RA procedure is triggered. When the RA procedure is triggered, the terminal (e.g., an SBFD terminal) may expect to perform preamble transmissions on all RO types (e.g., legacy RO and additional RO). The PDCCH order may include information instructing the transmission of preambles on all RO types, and the terminal may transmit preambles on all RO types based on said information. In this case, the terminal may transmit a preamble on one RO per RO type. For example, the terminal may transmit a preamble on a legacy RO and a preamble on an additional RO. This operation may be interpreted as a repetitive transmission of preambles. The repetitively transmitted preambles may have the same ID (e.g., RAPID (random access preamble identifier)). The base station can receive preambles from the legacy RO and additional RO, respectively. In a PDCCH order-based RA procedure, multiple preambles may be transmitted, and based on this, the RA procedure according to Proposal #2 can be completed faster than the RA procedure according to Proposal #1. However, when multiple preambles are transmitted, the complexity of the communication system may increase, the power consumption of the terminal may increase, and the overhead at the terminal may increase.

[0149] When a terminal transmits multiple preambles, multiple intervals (e.g., multiple RAR windows) may be required to receive responses to the multiple preambles. Since the retransmission of preambles is performed per RO type, the complexity of the RA procedure may increase. In Proposal #2, the configuration of the RAR window and the reception operation within the RAR window will be described when the terminal performs preamble transmission per RO type.

[0150] ■ Proposal #2-1: Utilization of a Single RAR Window

[0151] A RAR window may be involved in the transmission and / or retransmission of a preamble. A preamble and a RAR window may be mapped one-to-one. A terminal may transmit a preamble in each RO type prior to the RAR window, in which case multiple preambles (e.g., up to two preambles) may be transmitted. Even when multiple preambles are transmitted, a single RAR window may be used for RAR reception. After the transmission of the preamble, the terminal may determine a random access (RA)-radio network temporary identifier (RNTI) based on information from the RO to which the preamble was transmitted, and may receive a PDCCH that schedules the RAR for the preamble based on the RA-RNTI. The PDCCH that schedules the RAR may be referred to as the RAR PDCCH. The RAR window may be started based on the first symbol of a receivable CORESET (e.g., the first CORESET). When the terminal transmits a preamble in each RO type, the location of the CORESET (e.g., the first CORESET) where the RAR PDCCH can receive may differ.

[0152] FIGS. 10a and FIGS. 10b are conceptual diagrams illustrating the configuration of a CORESET for receiving a RAR PDCCH in a PDCCH order-based RA procedure.

[0153] Referring to FIGS. 10a and 10b, when a terminal transmits a preamble (e.g., msg1, msgA) at the additional RO and the legacy RO, respectively, the CORESET for receiving the RAR PDCCH may be determined based on the additional RO or the legacy RO. In the embodiment of FIG. 10a, the CORESET for receiving the RAR PDCCH may be determined based on the legacy RO, the base station may transmit the RAR PDCCH at the CORESET determined based on the legacy RO, and the terminal may receive the RAR PDCCH at the CORESET determined based on the legacy RO. In the embodiment of FIG. 10b, the CORESET for receiving the RAR PDCCH may be determined based on the additional RO, the base station may transmit the RAR PDCCH at the CORESET determined based on the additional RO, and the terminal may receive the RAR PDCCH at the CORESET determined based on the additional RO. The location of the RAR window may vary depending on the location of the CORESET. To use a single RAR window, it may be necessary to define the start time of the RAR window (e.g., CORESET for receiving RAR PDCCH). The CORESET for receiving RAR PDCCH may be referred to as RAR CORESET.

[0154] The base station may transmit information indicating the RO type that serves as the setting standard for the RAR window to the terminal via signaling. If preambles are transmitted from different RO types, the information indicating the RO type that serves as the setting standard for the RAR window may be used. For example, the information indicating the RO type that serves as the setting standard for the RAR window may be included in the PDCCH order. The terminal may receive the information indicating the RO type that serves as the setting standard for the RAR window via the base station's signaling. Based on the fact that the RO type that serves as the setting standard for the RAR window is indicated as a legacy RO, the communication node (e.g., base station and / or terminal) may determine that the RAR window (e.g., RAR CORESET) is set based on the legacy RO to which the preamble was transmitted. Based on the fact that the RO type that serves as the setting standard for the RAR window is indicated as an additional RO, the communication node (e.g., base station and / or terminal) may determine that the RAR window (e.g., RAR CORESET) is set based on the additional RO to which the preamble was transmitted.

[0155] ▶ RAR Windows startup point

[0156] If a preamble is transmitted from an RO (e.g., an additional RO) within a UL usable PRB(s) of SBFD symbol(s), the terminal can subsequently decode RAR PDCCH in the DL subband of the SBFD symbol(s). If a preamble is transmitted from an RO (e.g., a legacy RO) within N-SBFD symbol(s) (e.g., UL symbol(s)), the terminal can perform RAR PDCCH decoding in the DL symbol(s) following the UL symbol(s) or in the DL subband of the SBFD symbol(s). The location of the RAR CORESET after the preamble transmission from the additional RO may be the same as or different from the location of the RAR CORESET after the preamble transmission from the legacy RO. If a single RAR window is used, the location of the RAR CORESET may be determined based on the options below.

[0157] - Option #1

[0158] The RAR window can be set based on the start time (e.g., start symbol) of the earliest RAR CORESET after a specific time (e.g., Tx-Rx transition time, gap symbol) from the RO type in which the last preamble was transmitted among the RO types. Option #1 may be an embodiment of FIG. 10a. In other words, the RAR window can be set based on the RO type in which the last preamble was transmitted among the RO types. If the last preamble was transmitted from a legacy RO, the RAR window can be set (e.g., determined) based on the legacy RO (e.g., legacy RACH configuration information). If the last preamble was transmitted from an additional RO, the RAR window can be set (e.g., determined) based on the additional RO (e.g., additional RACH configuration information).

[0159] - Option #2

[0160] The RAR window can be set based on the start time (e.g., start symbol) of the earliest RAR CORESET after a specific time (e.g., Tx-Rx transition time, gap symbol) from the RO type in which the first preamble was transmitted among the RO types. Option #2 may be an embodiment of FIG. 10b. In other words, the RAR window can be set based on the RO type in which the first preamble was transmitted among the RO types. If the first preamble was transmitted from a legacy RO, the RAR window can be set (e.g., determined) based on the legacy RO (e.g., legacy RACH configuration information). If the first preamble was transmitted from an additional RO, the RAR window can be set (e.g., determined) based on the additional RO (e.g., additional RACH configuration information).

[0161] A base station may receive one or more preambles from a terminal. If multiple preambles are received from a terminal in different RO types and the multiple preambles have the same ID (e.g., RAPID), the base station may transmit a scrambled RAR PDCCH to the terminal using at least one RA-RNTI based on an additional RO or a legacy RO to which the preamble was transmitted. In other words, if multiple preambles are received from a terminal in different RO types and the multiple preambles have the same ID, the base station may transmit a RAR for one of the multiple preambles instead of transmitting a RAR for each of the multiple preambles.

[0162] The terminal may perform monitoring in a single RAR window to receive one or more RARs. For example, the terminal may perform decoding (e.g., blind decoding) for a RAR PDCCH within a single RAR window using at least one RA-RNTI based on an additional RO to which the preamble was transmitted or a legacy RO to which the preamble was transmitted. The terminal may receive a RAR based on the RAR PDCCH. The terminal may perform subsequent procedures based on the result of comparing the ID of the preamble transmitted by itself with the RAPID included in the RAR. If a RAR having the same RAPID as the ID of the preamble transmitted by the terminal is not received within the RAR window (e.g., if the transmission of the preamble failed), the terminal may retransmit the preamble in one RO type. Complexity may increase if preamble retransmission is performed per RO type, and to resolve the above problem, it may be permitted to perform preamble retransmission in one RO type. One RO type for preamble retransmission may be determined based on the terminal's implementation. As another example, the RO type considered to determine the start time of the RAR window may be used for preamble retransmission. If the RAR window is set based on a legacy RO, the terminal may retransmit the preamble from the legacy RO. If the RAR window is set based on an additional RO, the terminal may retransmit the preamble from the additional RO. As another example, the base station may transmit information to the terminal via signaling indicating one RO type for which preamble retransmission is performed, and the terminal may perform preamble retransmission at one RO type indicated by the base station's signaling. The terminal may transmit the preamble by RO type during the initial transmission of the preamble, and may retransmit the preamble at one RO type during the retransmission of the preamble.When the preamble is first transmitted, multiple preambles (e.g., up to two preambles) are transmitted from different RO types, thereby increasing the probability of a successful connection and, consequently, reducing the delay of the RA procedure.

[0163] ▶ RAR window size

[0164] Even when preambles are transmitted from different RO types, the terminal can decode the RAR PDCCH from the same RAR CORESET. The RAR may include a RAPID, and the RAR may further include information (e.g., information having a size of 1 bit) to indicate which RO type the RAPID is the ID of the preamble transmitted from. Alternatively, the RAR may further include information indicating the RO type to which the preamble associated with the RAR was transmitted. In a scenario where RACH setting 2 is applied, the RACH setting may vary by RO type, and the RACH setting information per RO type may include setting information for the RAR window. The size of the RAR window may be determined based on the setting of the RO type where the preamble transmission closest to the RAR window was performed.

[0165] If the adjacent RAR CORESET of the additional RO and legacy RO to which the preambles have been transmitted overlaps, the terminal may refer to a RACH type indicator (e.g., RO type indicator) for a general CFRA procedure set by system information (or RRC signaling). If a previous CFRA procedure has been performed, the terminal may determine the size of the RAR window by referring to the RAR window size indicated by the RACH setting of a specific RO type based on the RO type indicator included in the RAR PDCCH in the previous CFRA procedure.

[0166] ■ Proposal #2-2: Utilization of Multiple RAR Windows

[0167] In scenarios where RACH setting 2 is applied, parameters related to the (re)transmission of the preamble can be set independently for each RO type. These parameters may include parameters related to the transmission power of the (re)transmission of the preamble. The terminal may perform overall RA procedures, such as preamble transmission and RAR PDCCH reception, for each RO type until RAR reception. The RAR window may start at the RAR CORESET closest to each RO type. The starting point of the RAR window may be the first symbol of the RAR CORESET. The RAR CORESET for the additional RO and the RAR CORESET for the legacy RO may be the same. In this case, the terminal may assume that two RAR windows exist (e.g., a RAR window for the additional RO and a RAR window for the legacy RO) and may perform the (re)transmission of the preamble based on this assumption. Information indicating the size of the RAR window may be included in the RACH setting information. In this case, the size of the RAR window may be determined per RO type. If the RAR window size is specified as a single value, the RAR window size for additional ROs and the RAR window size for legacy ROs can be set to be the same. The terminal can perform (re)transmission of the preamble based on transmit power parameters set for each RO type.

[0168] ▶ RAR Settings

[0169] In the embodiments of the present disclosure, it may be assumed that different preamble indices are assigned according to RO types. The preamble indices used in different RO types may be distinguished. In this case, RAR may not include an indicator for indicating the RO type associated with RAPID.

[0170] Meanwhile, when the RACH procedure is triggered by a PDCCH order, the SBFD terminal in the RRC connection state may consider the following options in the RA procedure.

[0171] - Option #1: The SBFD terminal can use one RACH setting.

[0172] ○ ROs existing in the UL subband within the SBFD symbol(s) may be valid for the SBFD terminal.

[0173] - Option #2: Two RACH configurations, including one legacy RACH configuration and one additional RACH configuration, may be used.

[0174] ○ ROs of UL subbands within SBFD symbols indicated by additional RACH settings may be valid for SBFD UEs.

[0175] For RAs triggered by a PDCCH order, a 1-bit field within the PDCCH order (e.g., DCI) may explicitly indicate that the SBFD UE uses an additional RO or a legacy RO.

[0176] Indexing of additional ROs indicated by the PRACH mask index can be performed based on the indexing rules of legacy ROs, and indexing of additional ROs can be performed independently of the indexing of legacy ROs.

[0177] If, while an RA procedure triggered by a PDCCH order is in progress, a subsequently received PDCCH order indicates the same preamble resources (e.g., preamble index, PRACH mask index, uplink carrier) used in the ongoing RA procedure, the SBFD terminal may not start a new RA procedure and may continue to perform the ongoing RA procedure.

[0178] If a terminal receives another PDCCH order indicating the same RA preamble, PRACH mask index, and uplink carrier while it is executing an RA procedure triggered by a PDCCH order, the RA procedure triggered by the other PDCCH order may be considered the same procedure as the RA procedure currently in progress, and the new RA procedure may not be restarted. Problems may arise if the above-described behavior is applied directly to an SBFD UE.

[0179] Figure 11 is a conceptual diagram illustrating an RA procedure triggered by a PDCCH order.

[0180] Referring to FIG. 11, in a scenario where RACH setting 2 is applied, the RACH settings (e.g., preamble index and PRACH mask index) can be set independently for each RO type. Even if the base station initiates RA procedures for different RO types using an RO type indicator, if the preamble index and PRACH mask index are identical to the values ​​of the currently ongoing RACH procedure, the SBFD UE may incorrectly determine that it is a duplicate PDCCH order, ignore the PDCCH order, and continue the existing RACH procedure. In other words, the terminal may fail to transmit the preamble even though it is required to transmit the preamble for the indicated RO type. To resolve this issue, when determining whether a PDCCH order is duplicate, the RO type can be considered together with the preamble index and PRACH mask index used in the current procedure.

[0181] If the existing rules for determining duplicate PDCCH orders are applied directly to the SBFD UE, the following problems may occur.

[0182] Even if the base station initiates RA for different RO types using an RO type indicator, if the preamble index and PRACH mask index are identical to the values ​​of the currently ongoing RA procedure, the SBFD UE may incorrectly determine that the PDCCH order is duplicated, and as a result, a problem may occur where the RA procedure cannot be started anew.

[0183] When determining whether a PDCCH order is duplicated, it may be necessary to consider the RO type as well as the preamble index and PRACH mask index.

[0184] If a terminal receives another PDCCH order indicating the same RA preamble, PRACH mask index, uplink carrier, and RO type while the terminal is performing an RA procedure triggered by a PDCCH order, the RA procedure may be considered the same RA procedure as the ongoing RA procedure and may not be re-initialized.

[0185] Selection and Improvement of RO Type for Latency Reduction

[0186] Specific configuration conditions and / or priorities related to the selection of RO for the initial transmission attempt of the preamble in a single RA procedure can be defined.

[0187] It may be the default operation for an SBFD terminal to select only one RO type and perform the RA procedure. This approach may not fully utilize the characteristics of the SBFD operation. In the SBFD operation, ROs can exist in N-SBFD symbols (e.g., legacy ROs) as well as in SBFD symbols (e.g., additional ROs). Considering that one of the primary purposes of introducing the SBFD operation is latency reduction, it may be permissible for the SBFD terminal to transmit preambles in parallel for each RO type. In this case, the terminal can connect to the base station more quickly.

[0188] At least when an RA is performed (e.g., when an RA triggered by an initial connection step or a PDCCH order is performed), it may be necessary to support the SBFD terminal being not limited to a single RO type selected in advance, but to enable the transmission of preambles in parallel at each RO type.

[0189] Although the embodiments of the present disclosure have been described with respect to UL channels, they may be applied identically or similarly to DL channels. For example, embodiments related to an initial UL BWP may be applied identically or similarly to an initial DL BWP, embodiments related to a UL subband may be applied identically or similarly to a DL subband, and embodiments related to UL available PRB(s) may be applied identically or similarly to DL available PRB(s).

[0190] Each of the proposals of the present disclosure may be applied independently. Or a combination of the proposals of the present disclosure may be applied. Some proposals of the present disclosure may be applied to other proposals. Each of the options of the present disclosure may be applied independently. Or a combination of the options of the present disclosure may be applied. Some options of the present disclosure may be applied to other options. The proposals and / or options of the present disclosure may be applied regardless of the RRC state of the terminal. For example, a terminal in an RRC idle state, a terminal in an RRC inactive state, and / or a terminal in an RRC connected state may perform the proposals and / or options of the present disclosure. A base station may perform the proposals and / or options of the present disclosure for a terminal in an RRC idle state, a terminal in an RRC inactive state, and / or a terminal in an RRC connected state.

[0191] The channels / signals to which the proposals of the present disclosure apply may not be limited to specific channels / signals. In other words, the proposals of the present disclosure may be applied identically or similarly to all channels / signals (e.g., all uplink channels, all uplink signals, all downlink channels, all downlink signals). The proposals of the present disclosure may be extended to various RA procedures (e.g., two-stage RA procedures, RA procedures proposed in 6G communication systems) as well as four-stage RA procedures. The names of messages in RA procedures may be described differently.

[0192] 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.

[0193] 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.

[0194] 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.

[0195] 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.

[0196] 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. As a method of UE (user equipment), A step of receiving a PDCCH (physical downlink control channel) order from a base station; A step of transmitting a preamble to the base station in one RO (RACH (random access channel) occasion) type or different RO types based on the above PDCCH order; and The method includes the step of performing monitoring for receiving one or more RARs (random access responses) in response to the above preamble, The above different RO types include legacy RO and additional RO, wherein the legacy RO is set in one or more non-SBFD (subband full duplex) symbols, and the additional RO is set in one or more symbols including at least one of non-SBFD symbols or SBFD symbols. UE's method.

2. In Claim 1, The step of transmitting the above preamble to the base station is, A step of determining one RO type among the legacy RO and the additional RO based on the existence of the legacy RO and the additional RO having an index identical to the PRACH (physical random access channel) mask index included in the above PDCCH order; and A step comprising transmitting the preamble to the base station in one of the determined RO types above, UE's method.

3. In Claim 2, The RO type indicated by the above base station is determined as one RO type for the transmission of the above preamble, UE's method.

4. In Claim 2, One RO type for the transmission of the above preamble is determined based on the result of comparing the measured RSRP (reference signal received power) and the RSRP threshold, UE's method.

5. In Claim 2, The RO type used in the RA (random access) procedure during the initial connection phase or in the RA procedure prior to the reception of the PDCCH order is determined as one RO type for the transmission of the preamble, UE's method.

6. In Claim 1, The above PDCCH order includes information instructing the transmission of the preamble in each of the above different RO types, UE's method.

7. In Claim 1, The above one or more RARs are received in a single RAR window, and the single RAR window is configured based on the RO type to which the first preamble was transmitted or the RO type to which the last preamble was transmitted, UE's method.

8. In Claim 1, The method further includes the step of receiving from the base station information indicating an RO type which is a setting criterion for a single RAR window in which the above one or more RARs are received, The above-mentioned RAR window is set based on the RO type indicated by the base station, UE's method.

9. In Claim 1, Each of the above one or more RARs includes information indicating the RO type to which the preamble associated with the RAR was transmitted, UE's method.

10. In Claim 1, The step of performing monitoring for receiving one or more of the above RARs is: A step comprising performing decoding for a RAR PDCCH (physical downlink control channel) based on at least one of a RA-RNTI (random access-radio network temporary identifier) ​​based on the legacy RO to which the preamble was transmitted, or a RA-RNTI based on the additional RO to which the preamble was transmitted. UE's method.

11. In Claim 1, A method further comprising the step of retransmitting the preamble in one RO type based on the fact that one or more of the above RARs are not received within one RAR window. UE's method.

12. In Claim 11, Based on the fact that the above one RAR window is set based on the legacy RO, the preamble is retransmitted from the legacy RO, and based on the fact that the above one RAR window is set based on the additional RO, the preamble is retransmitted from the additional RO, UE's method.

13. As UE (user equipment), It includes at least one processor, The above at least one processor is the UE, Receive a PDCCH (physical downlink control channel) order from the base station; Based on the above PDCCH order, a preamble is transmitted to the base station in one RO (RACH (random access channel) occasion) type or different RO types; and Causes monitoring for the reception of one or more RARs (random access responses) in response to the above preamble, The above different RO types include legacy RO and additional RO, wherein the legacy RO is set in one or more non-SBFD (subband full duplex) symbols, and the additional RO is set in one or more symbols including at least one of non-SBFD symbols or SBFD symbols. UE.

14. In Claim 13, In order to transmit the above preamble to the base station, the at least one processor, the UE, Based on the existence of the legacy RO and the additional RO having the same index as the PRACH (physical random access channel) mask index included in the above PDCCH order, determine the type of one RO among the legacy RO and the additional RO; and Causing the transmission of the preamble to the base station in one of the above-determined RO types, UE.

15. In Claim 14, The RO type indicated by the above base station is determined as one RO type for the transmission of the above preamble, UE.

16. In Claim 14, One RO type for the transmission of the above preamble is determined based on the result of comparing the measured RSRP (reference signal received power) and the RSRP threshold, UE.

17. In Claim 13, The above PDCCH order includes information instructing the transmission of the preamble in each of the above different RO types, UE.

18. In Claim 13, The above one or more RARs are received in a single RAR window, and the single RAR window is configured based on the RO type to which the first preamble was transmitted or the RO type to which the last preamble was transmitted, UE.

19. In Claim 13, The above at least one processor is the UE, Further causing the above one or more RARs to receive information from the base station indicating an RO type which is a setting criterion for a single RAR window in which the above RARs are received, and The above-mentioned RAR window is set based on the RO type indicated by the base station, UE.

20. In Claim 13, In monitoring for receiving one or more of the above RARs, the at least one processor is such that the UE, Causing to perform decoding for the RAR PDCCH (physical downlink control channel) based on at least one of the RA-RNTI (random access-radio network temporary identifier) ​​based on the legacy RO to which the preamble was transmitted, or the RA-RNTI based on the additional RO to which the preamble was transmitted. UE.