Method and apparatus for random access procedure in SBFD subband

Abstract

Disclosed are a method and an apparatus for a random access procedure in an SBFD subband. A method of a user equipment (UE) comprises the steps of: receiving random access channel (RACH) configuration information from a base station; identifying validity of one or more RACH occasions (ROs) indicated by the RACH configuration information; and transmitting, to the base station, a random access (RA) preamble on a valid RO belonging to an uplink (UL) subband from among the one or more ROs.

Description

Method and device for random access procedure in SBFD subband

[0001] The present disclosure relates to improved communication technology, and more particularly to a technology for random access procedures in a subband full duplex (SBFD) subband.

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

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

[0004] Meanwhile, a communication network may support subband full duplex (SBFD) operation. In a communication network supporting SBFD operation, an uplink (UL) subband may be configured in a downlink (DL) section. The UL subband configured in the DL section may be used for a random access procedure. Some resources within the UL subband may not be available for the random access procedure. In the above-described situation, methods for efficiently performing the random access procedure using the UL subband may be necessary.

[0005] The purpose of the present disclosure to solve the above problems is to provide a method and device for a random access procedure in a subband full duplex (SBFD) subband.

[0006] A method of a UE (user equipment) according to embodiments of the present disclosure for achieving the above object includes: receiving random access channel (RACH) configuration information from a base station; verifying validity of one or more ROs (RACH occasions) indicated by the RACH configuration information; and transmitting a random access (RA) preamble to the base station in a valid RO belonging to an uplink (UL) subband among the one or more ROs.

[0007] The above RACH configuration information may include legacy RACH configuration information and SBFD (subband full duplex) RACH configuration information, and the one or more ROs may be indicated by the SBFD RACH configuration information.

[0008] The above SBFD RACH configuration information can be configured independently from the legacy RACH configuration information, and each of the SBFD RACH configuration information and the legacy RACH configuration information can include at least one of mapping information between an SSB (synchronization signal block) and an RO or mapping information between the RA preamble and the SSB.

[0009] Among the one or more ROs, an RO that completely belongs to the UL subband may be determined as a valid RO, and among the one or more ROs, an RO that partially belongs to the UL subband may be determined as an invalid RO.

[0010] If a DL (downlink) resource exists during a preset period prior to an RO that completely belongs to the UL subband among the above one or more ROs, the RO may be determined to be an invalid RO.

[0011] The method of the UE may further include a step of transmitting a message A (MsgA) physical uplink shared channel (PUSCH) to the base station in a time interval after the valid RO, wherein the RA preamble may be a MsgA preamble, and information of the time interval may be included in the RACH configuration information.

[0012] The above valid RO and the above time interval may belong to the same UL subband or different UL subbands.

[0013] If there is a time interval during which the MsgA PUSCH can be transmitted after the valid RO, the 2-step RA procedure can be performed, and if there is no time interval during which the MsgA PUSCH can be transmitted after the valid RO, the 4-step RA procedure can be performed.

[0014] The above RACH configuration information may include at least one of information indicating whether a 4-step RA procedure is supported in the SBFD resource or information indicating whether a 2-step RA procedure is supported in the SBFD resource.

[0015] The method of the UE may further include a step of retransmitting the RA preamble to the base station in an UL resource indicated by TDD (time division duplexing) dedicated configuration information received from the base station, if transmission of the RA preamble fails.

[0016] The above RA preamble may be retransmitted using increased transmit power determined based on the SBFD power parameter.

[0017] The above RACH configuration information may include an SBFD power parameter, and the transmission power of the RA preamble transmitted in the UL subband belonging to the SBFD resource may be determined based on the SBFD power parameter, and the SBFD power parameter may be set independently from an N-SBFD power parameter used to determine the transmission power of the RA preamble transmitted in the N(non)-SBFD resource.

[0018] According to embodiments of the present disclosure for achieving the above object, a user equipment (UE) includes at least one processor, wherein the at least one processor causes the UE to receive random access channel (RACH) configuration information from a base station; verify validity of one or more ROs (RACH occasions) indicated by the RACH configuration information; and transmit a random access (RA) preamble to the base station in a valid RO belonging to an uplink (UL) subband among the one or more ROs.

[0019] The above RACH configuration information may include legacy RACH configuration information and SBFD (subband full duplex) RACH configuration information, and the one or more ROs may be indicated by the SBFD RACH configuration information.

[0020] The above SBFD RACH configuration information can be configured independently from the legacy RACH configuration information, and each of the SBFD RACH configuration information and the legacy RACH configuration information can include at least one of mapping information between an SSB (synchronization signal block) and an RO or mapping information between the RA preamble and the SSB.

[0021] Among the one or more ROs, an RO that completely belongs to the UL subband may be determined as a valid RO, and among the one or more ROs, an RO that partially belongs to the UL subband may be determined as an invalid RO.

[0022] If a DL (downlink) resource exists during a preset period prior to an RO that completely belongs to the UL subband among the above one or more ROs, the RO may be determined to be an invalid RO.

[0023] The at least one processor may further cause the UE to transmit a message A (MsgA) physical uplink shared channel (PUSCH) to the base station in a time interval after the valid RO, wherein the RA preamble may be a MsgA preamble, and information of the time interval may be included in the RACH configuration information.

[0024] The at least one processor may further cause the UE to retransmit the RA preamble to the base station on an UL resource indicated by time division duplexing (TDD) dedicated configuration information received from the base station if transmission of the RA preamble fails.

[0025] The above RACH configuration information may include an SBFD power parameter, and the transmission power of the RA preamble transmitted in the UL subband belonging to the SBFD resource may be determined based on the SBFD power parameter, and the SBFD power parameter may be set independently from an N-SBFD power parameter used to determine the transmission power of the RA preamble transmitted in the N(non)-SBFD resource.

[0026] According to the present disclosure, a terminal supporting subband full duplex (SBFD) can identify a valid RO (random access channel (RACH) occasion) in an uplink (UL) subband and transmit an RA (random access) preamble to a base station in the valid RO. The terminal can perform a two-step RA procedure in the SBFD resource. If transmission of the RA preamble in the UL subband fails, the terminal can retransmit the RA preamble in the next RO (e.g., the next valid RO). Power control for the RA procedure in the SBFD resource can be performed independently from power control for the RA procedure in the N(non)-SBFD resource. Therefore, the RA procedure in the UL subband can be performed efficiently, and the performance of the communication system can be improved.

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

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

[0029] Figure 3 is a block diagram illustrating embodiments of communication nodes that perform communication.

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

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

[0032] Figure 5 is a conceptual diagram illustrating embodiments of system frames in a communication system.

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

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

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

[0036] Figure 9 is a conceptual diagram illustrating embodiments of RO settings within a UL subband.

[0037] Figure 10 is a conceptual diagram illustrating embodiments of RO settings within a UL subband.

[0038] Figure 11 is a conceptual diagram illustrating embodiments of RO settings within a UL subband.

[0039] Figure 12 is a flowchart illustrating embodiments of an RA procedure in a communication system supporting SBFD.

[0040] This disclosure may be subject to various modifications and various embodiments. Specific embodiments are illustrated and described in detail in the drawings. However, this is not intended to limit the disclosure to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the disclosure.

[0041] While terms such as "first" and "second" may be used to describe various components, these components should not be limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present disclosure, a first component could be referred to as a "second component," and similarly, a second component could also be referred to as a "first component." The term "and / or" may refer to a combination of multiple related items described herein or to any of multiple related items described herein.

[0042] In the present disclosure, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more 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 combinations of one or more of A and B.”

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

[0044] When a component is referred to as being "connected" or "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.

[0045] The terminology used in this disclosure is only used to describe specific embodiments and is not intended to limit the present disclosure. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this disclosure, it should be understood that the terms "comprises" or "has" indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, but do not preclude the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

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

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

[0048] In an embodiment, even if a method (e.g., transmitting or receiving a signal) performed by a first communication node among communication nodes is described, a corresponding second communication node can perform a method (e.g., receiving or transmitting a signal) corresponding to the method performed by the first communication node. That is, if an operation of a UE (user equipment) is described, a corresponding base station can perform an operation corresponding to the operation of the UE. Conversely, if an operation of a base station is described, a corresponding UE can perform an operation corresponding to the operation of the base station.

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

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

[0051] In the present disclosure, “an operation (e.g., a transmission operation) is set” may mean that “setting information for the operation (e.g., an information element, a parameter)” and / or “information instructing the performance of the operation” is signaled. “An information element (e.g., a parameter) is set” may mean that the 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 either time or time point depending on the context, and time point may be interpreted as either time or time point depending on the context.

[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 the term "communication system."

[0053] Figure 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). In addition, the communication system (100) may further include a core network (e.g., a serving-gateway (S-GW), a packet data network (PDN)-gateway (P-GW), a mobility management entity (MME)). If the communication system (100) is a 5G communication system (e.g., a new radio (NR) system), the core network may include an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), etc.

[0055] A plurality of communication nodes (110 to 130) can support a communication protocol (e.g., LTE communication protocol, LTE-A communication protocol, NR communication protocol, etc.) specified in the 3GPP (3rd generation partnership project) standard. The plurality of communication nodes (110 to 130) may 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 plurality of communication nodes may have the following structure.

[0056] Figure 2 is a block diagram illustrating embodiments of communication nodes constituting a communication system.

[0057] Referring to FIG. 2, a communication node (200) may include at least one processor (210), a memory (220), and a transmission / reception device (230) that is connected to a network and performs communication. In addition, 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) and communicate with each other.

[0058] The processor (210) can execute program commands stored in at least one of the memory (220) and the storage device (260). The processor (210) may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor in which the methods according to embodiments of the present disclosure are performed. Each of the memory (220) and the storage device (260) may be configured with at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory (220) may be configured with at least one of a read-only memory (ROM) and a 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 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 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 within the cell coverage of the third base station (110-3). The first terminal (130-1) may be within the cell coverage of the fourth base station (120-1). The sixth terminal (130-6) may be within the cell coverage of the fifth base station (120-2).

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

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

[0062] Meanwhile, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may operate in a different frequency band or may operate in the same frequency band. Each of the plurality of 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 the ideal backhaul link or the non-ideal backhaul link. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may be connected to the core network via the ideal backhaul link or the non-ideal backhaul link. Each of the plurality of 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] Additionally, each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) may support MIMO transmission (e.g., single user (SU)-MIMO, multi user (MU)-MIMO, massive MIMO, etc.), coordinated multipoint (CoMP) transmission, carrier aggregation (CA) transmission, transmission in an unlicensed band, sidelink communication (e.g., device to device communication (D2D), proximity services (ProSe)), Internet of Things (IoT) 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 scheme, and the fourth terminal (130-4) can receive a signal from the second base station (110-2) by the SU-MIMO scheme. Alternatively, the second base station (110-2) can transmit signals 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 signals from the second base station (110-2) based on 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 scheme, 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) based on the CoMP scheme. Each of the plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) can transmit and receive a signal with terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) within its cell coverage based on the CA scheme. 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 under the control of the second base station (110-2) and the third base station (110-3), respectively.

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

[0066] Figure 3 is a block diagram illustrating embodiments of communication nodes that perform communication.

[0067] Referring to FIG. 3, each of the first communication node (300a) and the second communication node (300b) may be a base station or a UE. The first communication node (300a) may transmit a signal to the second communication node (300b). The 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 the controller (316). The control information may include at least one of system information, RRC configuration information (e.g., information configured by RRC signaling), MAC control information (e.g., MAC CE), or PHY control information (e.g., DCI, SCI).

[0068] The transmitting processor (311) may perform a processing operation on data (e.g., an encoding operation, a symbol mapping operation, etc.) to generate data symbol(s). The transmitting processor (311) may perform a processing operation on control information (e.g., an encoding operation, a symbol mapping operation, etc.) to generate control symbol(s). In addition, the transmitting processor (311) may generate synchronization / reference symbol(s) for a synchronization signal and / or a reference signal.

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

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

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

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

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

[0074] Memories (315 and 365) can store data, control information, and / or program code. Scheduler (317) can perform scheduling operations for communication. The processors (311, 312, 319, 361, 368, 369) and controllers (316, 366) illustrated in FIG. 3 may be the processor (210) illustrated in FIG. 2 and may be used to perform the methods described in the present 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 in a communication node that transmits a signal, and a reception path (420) may be implemented in a communication node that receives a signal. The transmission path (410) may include a channel coding and modulation block (411), an S-to-P (serial-to-parallel) block (512), an N IFFT (Inverse Fast Fourier Transform) block (413), a P-to-S (parallel-to-serial) block (414), a CP (cyclic prefix) addition block (415), and an UC (up-converter) (UC) (416). The receiving 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 may be a natural number.

[0077] In the transmission path (410), information bits may be input to a channel coding and modulation block (411). The channel coding and modulation block (411) may perform a coding operation (e.g., a low-density parity check (LDPC) coding operation, a polar coding operation, etc.) and a modulation operation (e.g., a quadrature phase shift keying (QPSK), a quadrature amplitude modulation (QAM), 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 modulation symbols in the frequency domain into parallel symbol streams to generate N parallel symbol streams. N can be an IFFT size or an FFT size. The N IFFT block (413) can perform an IFFT operation on the N parallel symbol streams to generate signals in the time domain. The P-to-S block (414) can convert the output (e.g., parallel signals) of the N IFFT block (413) into a serial signal to generate a serial signal.

[0079] The CP addition block (415) can insert a CP into a 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 at the baseband before up-conversion.

[0080] A signal transmitted from a transmission path (410) may be input to a reception path (420). An operation in the reception path (420) may be the reverse operation of the operation in the transmission path (410). A DC (421) may down-convert the frequency of the received signal to a baseband frequency. A CP removal block (422) may remove a CP from a signal. The output of the CP removal block (422) may be a serial signal. An S-to-P block (423) may convert the serial signal into parallel signals. An N FFT block (424) may perform an FFT algorithm to generate N parallel signals. A P-to-S block (425) may convert the parallel signals into a sequence of modulation symbols. A 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 data.

[0081] In FIGS. 4A and 4B , Discrete Fourier Transform (DFT) and Inverse DFT (IDFT) may be used instead of FFT and IFFT. Each of the blocks (e.g., components) in FIGS. 4A and 4B may be implemented by at least one of hardware, software, or firmware. For example, some of the blocks in FIGS. 4A and 4B 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 , a block may be subdivided into multiple blocks, multiple blocks may be integrated into a single block, some blocks may be omitted, and blocks supporting other functions may be added.

[0082] Figure 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 frame units. 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 (milliseconds). 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 the system frame after system frame #1023 can be #0.

[0084] A system frame may include two half frames. A half frame may be 5 ms long. 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 include 10 subframes. A subframe may be 1 ms long. The 10 subframes within a system frame may be referred to as "subframes #0-9."

[0085] Figure 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 may be a natural number. Accordingly, one subframe may be composed of one or more slots.

[0087] Figure 7 is a conceptual diagram illustrating embodiments of slots in a communication system.

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

[0089] In a communication system, the numerology applied to physical signals and channels may be variable. The numerology may be variable to meet various technical requirements of the communication system. In a communication system applying CP (cyclic prefix)-based OFDM waveform technology, the numerology may include subcarrier spacing and CP length (or CP type). Table 1 may be a first embodiment of a method for configuring a numerology for a CP-OFDM-based communication system. At least some of the numerologies in Table 1 may be supported depending on the frequency band in which the communication system operates. In addition, the communication system may additionally support numerologies not listed in Table 1.

[0090]

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

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

[0093] A symbol may be configured as a downlink (DL) symbol, a flexible (FL) symbol, or an uplink (UL) symbol. A slot consisting solely of DL symbols may be referred to as a "DL slot," a slot consisting solely of FL symbols may be referred to as an "FL slot," and a slot consisting solely of UL symbols may be referred to as a "UL slot."

[0094] The slot format can be semi-statically configured by higher layer signaling (e.g., RRC signaling). Information indicating the semi-static slot format can be included in the system information, and the semi-static slot format can be configured cell-specifically. In addition, the semi-static slot format can be additionally configured for each terminal through terminal-specific higher layer signaling (e.g., RRC signaling). The flexible symbol of the cell-specifically configured slot format can be overridden to a downlink symbol or an uplink symbol by terminal-specific higher layer signaling. In addition, the slot format can be dynamically indicated by physical layer signaling (e.g., a slot format indicator (SFI) included in DCI). The semi-statically configured slot format can be overridden by a dynamically indicated slot format. For example, the semi-statically configured flexible symbol can be overridden to a downlink symbol or an uplink symbol by the SFI.

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

[0096] Figure 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 may be defined as a "RE (resource element)". Resources consisting of one OFDM symbol in the time domain and K subcarriers in the frequency domain may be defined as a "REG (resource element group)". A REG may include K REs. A REG may be used as a basic unit for resource allocation in the frequency domain. K may be a natural number. For example, K may be 12. N may be a natural number. In the slot illustrated in FIG. 7, N may be 14. N OFDM symbols may be used as a basic unit for resource allocation in the time domain.

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

[0099] Downlink data can be transmitted via the PDSCH. The base station can transmit PDSCH configuration information (e.g., scheduling information) to the terminal via the PDCCH. The terminal can obtain the PDSCH configuration information by receiving the PDCCH (e.g., downlink control information (DCI)). For example, the PDSCH configuration information can include the MCS (modulation coding scheme) 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. The PDSCH can refer to a radio resource through which downlink data is transmitted and received. Alternatively, the PDSCH can refer to the downlink data itself. The PDCCH can refer to a radio resource through which downlink control information (e.g., DCI) is transmitted and received. Alternatively, the PDCCH can refer to the downlink control information itself.

[0100] A terminal can perform a monitoring operation on the PDCCH to receive a PDSCH transmitted from a base station. The base station can inform the terminal of the configuration information for the PDCCH monitoring operation using a higher layer message (e.g., an RRC (radio resource control) message). The configuration information for the PDCCH monitoring operation can 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. The PDCCH occasion may be a region where the PDCCH can exist. That is, the PDCCH occasion may be a region where DCI can be transmitted. The PDCCH occasion may be referred to as a PDCCH candidate. The 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., in PRB (physical resource block) units or CRB (common resource block) units).

[0102] The search space information may include a coreset identifier (ID) associated with the search space, a period of PDCCH monitoring, and / or an offset. The period and offset of PDCCH monitoring may each be indicated on a slot-by-slot basis. In addition, the search space information may further include an index of the symbol at which the PDCCH monitoring operation begins.

[0103] A base station can configure a bandwidth part (BWP) for downlink communication. The BWP can be configured differently for each terminal. The base station can inform the terminal of the BWP configuration information using higher layer signaling. The higher layer signaling can mean "transmission operation of system information" and / or "transmission operation of RRC (radio resource control) message." The number of BWPs configured for one terminal can be one or more. The terminal can receive BWP configuration information from the base station and check the BWP(s) configured by the base station based on the BWP configuration information. When multiple BWPs are configured for downlink communication, the base station can activate one or more BWPs among the multiple BWPs. The base station can transmit the configuration information of the activated BWP(s) to the terminal using at least one of higher layer signaling, a medium access control (MAC) control element (CE), or DCI. The base station can 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 perform a downlink reception operation in 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 TDD (time division duplexing). In a communication system supporting TDD (hereinafter referred to as a "TDD communication system"), downlink (DL) symbol(s) and uplink (UL) symbol(s) may be configured in different time resources within a single carrier. DL and UL symbols may be associated with coverage and / or latency. In a TDD communication system, a base station can utilize resources more efficiently than in a frequency division duplexing (FDD) scheme by considering various use cases. Resource scheduling operations of the base station may be important in a TDD communication system. For improved TDD operation, SBFD operation (e.g., SBFD operation) may be supported. When SBFD operation is 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, while other subbands may be UL subbands and / or FL subbands. In the present disclosure, a DL signal may be interpreted as a DL signal, a DL channel, or "a DL signal and a DL channel" depending on the context. In the present disclosure, a UL signal may be interpreted as a UL signal, an UL channel, or "a UL signal and a UL channel" depending on the context.

[0106] A symbol to which the SBFD operation is applied may be referred to as an SBFD symbol. A symbol to which the SBFD operation is not applied may be referred to as an N(non)-SBFD symbol. An N-SBFD symbol may be a DL symbol, an UL symbol, or an FL symbol. In an SBFD symbol, a terminal may perform DL communication and UL communication. In other words, in an SBFD symbol, a terminal may perform full duplex operation. In an N-SBFD symbol, a terminal may perform one of DL communication and UL communication. In other words, in an N-SBFD symbol, a terminal may perform half duplex operation. An SBFD symbol may be a symbol including a subband on which an SBFD operation is performed. A subband for SBFD may be referred to or interpreted as a UL subband. A UL subband may be present (e.g., configured) in a symbol in which an SSB (synchronization signal block) is transmitted.

[0107] Resources (e.g., time resources and / or frequency resources) for SBFD operation can be configured in a semi-static manner. In other words, the configuration for SBFD resources can be a semi-static configuration. "The SBFD resource configuration being a semi-static configuration" can mean "the SBFD resource is configured by semi-static signaling (e.g., system information, RRC message)." In the present disclosure, SBFD resources can mean time resources and / or frequency resources for SBFD operation. A UL subband for SBFD can be an SBFD resource. Alternatively, SBFD resources can be configured in a dynamic manner. "The SBFD resource configuration being a dynamic configuration" can mean "the SBFD resource is configured by dynamic signaling (e.g., MAC CE, DCI, SCI)."

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

[0109] The TDD-UL-DL configuration common information can be used to configure a pattern (e.g., TDD-UL-DL-Pattern) for DL ​​resources and / or UL resources in the time domain of a TDD communication system. The pattern for DL ​​resources and / or UL resources can be referred to as a UL / DL pattern. The UL / DL pattern can be changed according to the environment of the communication system (e.g., TDD communication system). Up to two UL / DL patterns can be configured for a terminal. The TDD-UL-DL configuration common information can be a cell-specific parameter (e.g., cell-specific configuration information). The base station can change the configuration (e.g., transmission direction, type) for symbol(s) for each terminal based on a specific slot within a preset UL / DL pattern. A slot for which the symbol configuration (e.g., symbol direction, symbol type) can be changed can 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 TDD-UL-DL configuration common information can be repeated according to a specific period (e.g., dl-UL-TransmissionPeriodicity). In the time period to which the UL / DL pattern is applied, the front region can be configured as a DL resource. In the time period to which the UL / DL pattern is applied, the rear region can be configured as a UL resource. In the time period to which the UL / DL pattern is applied, resources that are not configured as DL resources or UL resources can be FL resources. The period of the UL / DL pattern can vary depending on the reference numerology. A guard time (e.g., a guard gap) may be required for switching (e.g., transition) from a DL resource (e.g., a DL symbol / slot) to a UL resource (e.g., a UL symbol / slot). Since the propagation delay of DL signals causes interference to UL resources, a guard time may be required for switching from DL resources to UL resources. A separate guard time may not be required for switching from UL resources to DL resources. Since UL signals are transmitted based on the timing advance command (TAC) indicated 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". A UL subband may mean a subband for SBFD. DL symbol(s) and / or DL ​​slot(s) may be referred to as a DL region (or DL ​​resource). UL symbol(s) and / or UL slot(s) may be referred to as a UL region (or UL resource). FL symbol(s) and / or FL slot(s) may be referred to as an FL region (or FL resource). A terminal that supports (e.g., recognizes) the SBFD operation may be referred to as an SBFD terminal or SBFD UE. A terminal that does not support (e.g., is not aware of) SBFD operation may be referred to as an N(non)-SBFD terminal or N-SBFD UE. An N-SBFD terminal may be a legacy terminal (e.g., a legacy UE). In the present disclosure, a terminal may be interpreted as an SBFD terminal and / or an N-SBFD terminal depending on the context. Legacy configuration (e.g., legacy information, legacy configuration information) may be information for an N-SBFD terminal.

[0115] A random access procedure (e.g., random access channel (RACH) transmission, physical random access channel (PRACH) transmission) can be performed in an UL subband (e.g., SBFD resource). The UL subband can belong to an SBFD resource. The UL subband can exist in a DL region and / or FL region configured by TDD common. The UL subband can be configured in a DL region (e.g., DL time resource). A terminal can perform PRACH transmission in a UL subband. In the present disclosure, PRACH transmission methods for an SBFD terminal will be described.

[0116] ● RACH setup and RACH occasion validity rules

[0117] A terminal can perform PRACH transmission (e.g., preamble transmission, RA (random access) preamble transmission) in an RO (RACH occasion). One RO or multiple ROs can be configured in one slot. A UL subband can be configured in a DL region and / or FL region configured by TDD common and / or TDD dedicated, and one or more ROs can be configured in a UL subband. Configuration information for an SBFD RO can be configured (e.g., indicated) independently of configuration information for a legacy RO. Alternatively, the SBFD RO can be configured based on the configuration information for the legacy RO. In other words, the configuration information for the SBFD RO may not be separately indicated. The configuration information for the SBFD RO may be referred to as an SBFD RO configuration or SBFD RO configuration information. The configuration information for the legacy RO may be referred to as a legacy RO configuration or legacy RO configuration information.

[0118] SBFD RO may refer to an RO configured within an SBFD resource (e.g., an UL subband). Legacy RO may refer to an RO configured within an N-SBFD resource (e.g., an UL resource). In the present disclosure, RO may be interpreted as an SBFD RO and / or an N-SBFD RO depending on the context. Due to the transition time of the terminal, signal propagation delay, etc., a problem may arise where not all SBFD ROs are utilized. In other words, a validity issue may arise for the SBFD RO.

[0119] ■ Proposal #1

[0120] If the SBFD RO configuration (e.g., the SBFD RACH configuration) is not indicated to the UE, the UE may operate based on the legacy RO configuration (e.g., the legacy RACH configuration). The UE may identify one or more ROs based on the legacy RO configuration. The UE may attempt PRACH transmission using the RO(s) existing in the UL subband. The methods proposed in the present disclosure may be applied when the SBFD RO configuration is indicated to the UE (e.g., when the UE operates based on the SBFD RO configuration) and / or when the SBFD RO configuration is not indicated to the UE (e.g., when the UE operates based on the legacy RO configuration).

[0121] Figure 9 is a conceptual diagram illustrating embodiments of RO settings within a UL subband.

[0122] Referring to FIG. 9, some ROs may be configured across UL subbands and DL resources. In this case, the UE may not perform PRACH transmission in the ROs configured across the UL subbands and DL resources. The ROs may be configured across UL subbands and FL resources. In this case, the UE may not perform PRACH transmission in the ROs configured across the UL subbands and FL resources. Alternatively, the UE may not perform PRACH transmission in the ROs configured across the UL subbands and DL resources, but the UE may perform PRACH transmission in the ROs configured across the UL subbands and FL resources. Some resources in the DL region of FIG. 9 may be FL resources.

[0123] A UE may determine an RO that is entirely within a UL subband as a valid RO, and may determine an RO that is partially within a UL subband as an invalid RO. The UE may determine the validity of an SBFD RO and transmit a PRACH preamble in a valid SBFD RO. If a signal (e.g., SSB, reference signal, CSI-RS) associated with an invalid RO has a best RSRP (reference signal received power), the UE may expect to perform a PRACH transmission in an RO (e.g., a valid RO) associated with a signal that has a lower quality or second-best quality than the best RSRP.

[0124] Until a valid RO is selected, the terminal may continue to perform the operation of selecting a valid RO associated with a signal having the next RSRP (e.g., a suboptimal RSRP). Alternatively, the terminal may perform the operation of selecting a valid RO associated with a signal having the next RSRP (e.g., a suboptimal RSRP) a preset number of times. Alternatively, the terminal may perform the operation of selecting a valid RO associated with a signal having an RSRP greater than or equal to a quality threshold (e.g., an RSRP threshold). The quality threshold may be configured in the terminal by signaling from the base station. The quality threshold may be included in the RACH configuration information.

[0125] Figure 10 is a conceptual diagram illustrating embodiments of RO settings within a UL subband.

[0126] Referring to FIG. 10, all ROs can be configured within a UL subband, and ROs can be configured in a front region of the UL subband in the time domain. Some resources in the DL region of FIG. 10 may be FL resources. If a DL resource (e.g., a DL region, a DL symbol, a DL slot) exists during a preset period prior to an RO configured within a UL subband (e.g., an SBFD RO), the UE may not expect PRACH transmission in the RO. In other words, the UE may determine the RO as an invalid RO and may not perform PRACH transmission in the invalid RO. Due to the transition time from DL communication to UL communication and / or the propagation delay of DL communication, PRACH transmission may not be possible in an RO configured within a UL subband. In other words, due to the transition time from DL communication to UL communication and / or the propagation delay of DL communication, invalid RO(s) may exist among the SBFD ROs.

[0127] Figure 11 is a conceptual diagram illustrating embodiments of RO settings within a UL subband.

[0128] Referring to FIG. 11, all ROs can be configured within the UL subband, and ROs can be configured in the rear region of the UL subband in the time domain. Some resources in the DL region of FIG. 11 may be FL resources. Unlike the embodiment of FIG. 10, in the embodiment of FIG. 11, invalid RO(s) due to the transition time from DL communication to UL communication and / or the propagation delay of DL communication may not occur. PRACH transmission may be possible in all ROs configured within the UL subband.

[0129] ■ Proposal #2

[0130] The base station can generate SBFD RACH configuration information and transmit the SBFD RACH configuration information to the terminal through signaling (e.g., system information, RRC message, RRC configuration). The terminal can receive the SBFD RACH configuration information through signaling from the base station. The SBFD RACH configuration information can include SBFD RO configuration information. The SBFD RACH configuration information can be configured independently of legacy RACH configuration information. The base station can transmit the SBFD RACH configuration information together with the legacy RACH configuration information to the terminal through signaling. In other words, the base station can transmit the RACH configuration information including the legacy RACH configuration information and the SBFD RACH configuration information to the terminal through signaling. The terminal can receive the legacy RACH configuration information and the SBFD RACH configuration information together through signaling from the base station. The terminal can identify the RO(s) configured in the SBFD resource (e.g., UL subband) based on the SBFD RACH configuration information. The terminal can check the RO(s) set in the N-SBFD resource based on the legacy RACH configuration information.

[0131] Each of the legacy RACH configuration information and the SBFD RACH configuration information may include mapping information between an SSB and an RO and / or mapping information between a preamble (e.g., an RA (random access) preamble) and an SSB. Alternatively, the SBFD RACH configuration information may not include mapping information between an SSB and an RO and / or mapping information between a preamble and an SSB, and the UE may identify RO(s) configured within a UL subband based on the mapping information between an SSB and an RO and / or the mapping information between a preamble and an SSB included in the legacy RACH configuration information, and identify preamble(s) associated with the RO(s).

[0132] The base station can configure ROs in the UE so that all ROs fall within the UL subband. The base station can generate mapping information between the preamble and the SSB by considering the RO configuration within the UL subband. If the SBFD RACH configuration is indicated to the UE, the UE can perform PRACH transmission on the RO(s) indicated by the SBFD RACH configuration without determining the validity of the RO. Alternatively, regardless of the indication of the SBFD RACH configuration, the UE can determine the validity of the RO(s) indicated by the SBFD RACH configuration and / or the legacy RACH configuration, and perform PRACH transmission on the valid RO(s).

[0133] ● 4-step RA procedure and 2-step RA procedure

[0134] In a communication system supporting SBFD, a 4-step RA procedure and / or a 2-step RA procedure may be supported. In other words, the 4-step RA procedure and / or the 2-step RA procedure may be performed using SBFD resources (e.g., UL subbands). A terminal may transmit to a base station through signaling information indicating whether the terminal supports the 4-step RA procedure on SBFD resources and / or information indicating whether the terminal supports the 2-step RA procedure on SBFD resources. The information may be included in a UE capability report transmitted by the terminal to the base station. The base station may determine whether the terminal supports the 4-step RA procedure and / or the 2-step RA procedure on SBFD resources based on the information received from the terminal.

[0135] The base station can transmit to the terminal through signaling information indicating whether the 4-step RA procedure is supported in the SBFD resource and / or information indicating whether the 2-step RA procedure is supported in the SBFD resource. The terminal can determine whether the 4-step RA procedure and / or the 2-step RA procedure is supported in the SBFD resource through signaling from the base station. The base station can transmit to the terminal through signaling configuration information for the 4-step RA procedure and / or configuration information for the 2-step RA procedure, wherein the configuration information can include a legacy RACH configuration and / or an SBFD RACH configuration. The terminal can receive the configuration information for the 4-step RA procedure and / or the configuration information for the 2-step RA procedure through signaling from the base station.

[0136] If only the 4-step RA procedure is supported on the SBFD resource, the UE can perform the 4-step RA procedure on the SBFD resource. If only the 2-step RA procedure is supported on the SBFD resource, the UE can perform the 2-step RA procedure on the SBFD resource. If both the 4-step RA procedure and the 2-step RA procedure are supported on the SBFD resource, the UE can select one RA procedure from the 4-step RA procedure and the 2-step RA procedure, and perform the selected one RA procedure on the SBFD resource.

[0137] ■ Proposal #3

[0138] A two-step RA procedure may be supported in SBFD resources. The UE may transmit an RA preamble (e.g., a MsgA (message A) preamble) to the base station in a Relay Output (RO) within an UL subband, and may transmit the MsgA PUSCH to the base station in a time interval following the Relay Output (RO). The time interval for the MsgA PUSCH transmission may be within the UL subband. Alternatively, the time interval for the MsgA PUSCH transmission may be an N-SBFD resource. The N-SBFD resource may be indicated by a TDD common configuration and / or a TDD-specific configuration. The time interval for the MsgA PUSCH transmission may be defined in a technical specification. Alternatively, the base station may transmit information on the time interval for the MsgA PUSCH transmission to the UE through signaling. Information on the time interval for the MsgA PUSCH transmission may be included in the SBFD RACH configuration information. The terminal can receive information on the time interval for MsgA PUSCH transmission through signaling from the base station.

[0139] A time interval for MsgA PUSCH transmission may be referred to as a MsgA PUSCH interval. The MsgA PUSCH interval may be composed of time resource(s) and / or frequency resource(s). The MsgA PUSCH interval may be configured with M symbols and / or N slots. Each of M and N may be a natural number. The value of each of M and N may be indicated to the UE by signaling from the base station. If there is a MsgA PUSCH interval (e.g., a valid MsgA PUSCH interval) after the RO in which the MsgA preamble is transmitted, the UE may perform a two-step RA procedure. The MsgA PUSCH interval may be the minimum time required for MsgA PUSCH transmission.

[0140] A terminal can selectively perform a 4-step RA procedure or a 2-step RA procedure based on an RSRP threshold. The terminal can selectively perform a 4-step RA procedure or a 2-step RA procedure based on a configuration of a Radio Access Point (RO) of the terminal (e.g., location and / or existence of the RO) and / or a configuration of a MsgA PUSCH period (e.g., location and / or existence of the MsgA PUSCH period). If the RSRP of a signal received from a base station satisfies the RSRP threshold and the MsgA PUSCH period exists, the terminal can perform (e.g., attempt) the 2-step RA procedure. Alternatively, the terminal can perform (e.g., attempt) the 2-step RA procedure if the MsgA PUSCH period exists, regardless of whether the RSRP of the signal received from the base station satisfies the RSRP threshold.

[0141] "The existence of a MsgA PUSCH period" may mean "the existence of a MsgA PUSCH period associated with a RO (e.g., a valid RO) within a UL subband." The RO and the MsgA PUSCH periods may exist within the same UL subband. If the RO and the MsgA PUSCH periods are configured in different UL subbands, the MsgA PUSCH period may be regarded as an invalid period. In this case, the UE may not perform a two-step RA procedure. Alternatively, the RO and the MsgA PUSCH periods configured in different UL subbands may each be regarded as a valid RO and a valid period. In this case, the UE may transmit the MsgA preamble in the RO configured in the first UL subband, and may transmit the MsgA PUSCH in the MsgA PUSCH period configured in the second UL subband. The second UL subband may be located after the first UL subband in the time domain.

[0142] If the RSRP of the signal received from the base station satisfies the RSRP threshold but the MsgA PUSCH interval does not exist, the UE may perform the 4-step RA procedure instead of the 2-step RA procedure. In other words, the 2-step RA procedure may not be performed. Alternatively, regardless of whether the RSRP of the signal received from the base station satisfies the RSRP threshold, if the MsgA PUSCH interval does not exist, the 4-step RA procedure may be performed instead of the 2-step RA procedure. "The MsgA PUSCH interval does not exist" may mean "the MsgA PUSCH interval is not configured within the UL subband" or "the MsgA PUSCH interval configured within the UL subband is an invalid interval."

[0143] ■ Proposal #4

[0144] The terminal may perform an RA procedure in an UL subband based on legacy RACH configuration information. Within the UL subband, RO(s) may be configured based on legacy RACH configuration information, and preamble transmission (e.g., transmission of a PRACH preamble) in the RO(s) configured within the UL subband may be performed based on the legacy RACH configuration information.

[0145] Some parameters for RO configuration and / or preamble transmission within a UL subband may be defined separately. For example, some parameters for RO configuration and / or preamble transmission within a UL subband may be included in SBFD configuration information (e.g., SBFD RACH configuration information). The base station may transmit the SBFD configuration information to the terminal via signaling. The terminal may receive the SBFD configuration information via signaling from the base station, and may identify "some parameters for RO configuration and / or preamble transmission within a UL subband" based on the SBFD configuration information. The terminal may update some parameters in the legacy RACH configuration information to parameters indicated by the SBFD configuration information (e.g., some parameters for RO configuration and / or preamble transmission within a UL subband), and may perform an RA procedure in the UL subband based on the updated parameters.

[0146] ● PRACH repeated transmission

[0147] UL subbands can be configured within the DL region, and FL resources can exist after the UL subbands. A terminal can perform PRACH repeated transmissions (e.g., repeated transmissions of a PRACH preamble, repeated transmissions of MsgA) using the UL subbands and FL resources. When repeated PRACH transmissions are performed, the transmission coverage of the PRACH can be increased. In other words, the transmission coverage of the PRACH can be improved. FL resources can be changed to UL resources by a TDD-only configuration. In other words, the TDD-only configuration can indicate that the FL resources should be changed to UL resources. A terminal supporting SBFD operation can perform PRACH repeated transmissions based on Proposal #5 below.

[0148] ■ Proposal #5

[0149] A base station can transmit TDD-only configuration (e.g., a TDD-only configuration indicating changing a FL resource to a UL resource) and PRACH repetition configuration information to a terminal via signaling. The terminal can receive the TDD-only configuration and PRACH repetition configuration information via signaling from the base station. The PRACH repetition configuration information can be included in RACH configuration information. The PRACH repetition configuration information can include information indicating whether PRACH repeated transmission is possible and / or information on the number of PRACH repeated transmissions. The terminal can identify UL resource(s) indicated by the TDD-only configuration, and the PRACH repetition configuration information can be applied to the identified UL resource(s). The UL resource(s) indicated by the TDD-only configuration can be SBFD resource(s) and / or N-SBFD resource(s). The terminal can perform PRACH transmission on a UL subband, and can perform PRACH repetition transmission on UL resource(s) after the UL subband (e.g., UL resource(s) indicated by TDD-only settings). If transmission of the RA preamble fails (e.g., if a response message to the RA preamble is not received within a preset time), the terminal can perform PRACH repetition transmission.

[0150] ● Power control

[0151] Power control for RA procedures based on SBFD RACH configurations may differ from power control for RA procedures based on legacy RACH configurations. Power control for RA procedures based on SBFD RACH configurations may differ, taking into account validity rules (e.g., RO validity determination rules) and / or repeated PRACH transmissions.

[0152] ■ Proposal #6

[0153] A terminal may perform a PRACH transmission in an RO associated with a signal (e.g., an SSB, a reference signal, a CSI-RS) having suboptimal quality (e.g., suboptimal RSRP) based on a validity rule (e.g., a judgment rule for RO validity). In the above situation, since the performance of a transmission beam (e.g., a transmission beam of a base station) of a signal (e.g., an SSB, a reference signal, a CSI-RS) associated with the PRACH transmission does not have an optimal performance, the base station may not receive (e.g., detect) the PRACH transmission transmitted from the terminal. In other words, since the base station performs a reception operation (e.g., a detection operation) of the PRACH transmission using a reception beam corresponding to a transmission beam that does not have an optimal performance (e.g., has a low performance), the reception (e.g., detection) of the PRACH transmission at the base station may fail.

[0154] To solve the above problem, the base station can set power parameter(s) for the SBFD terminal (e.g., p0, ramping step size, etc.) and transmit the power parameter(s) to the terminal via signaling. The terminal can receive the power parameter(s) for the SBFD terminal via signaling from the base station. The power parameter(s) for the SBFD terminal may be referred to as SBFD power parameter(s). The SBFD power parameter(s) may be set independently from the power parameter(s) for the N-SBFD terminal. The power parameter(s) for the N-SBFD terminal may be referred to as N-SBFD power parameter(s). The SBFD power parameter(s) may be included in the legacy RACH configuration information and / or the SBFD RACH configuration information. The terminal can determine the transmit power of the RA preamble (e.g., PRACH transmission) based on the SBFD power parameter(s), and transmit the RA preamble to the base station using the determined transmit power. The transmit power determined based on the SBFD power parameter(s) may be greater than the transmit power determined based on the N-SBFD power parameter(s). In other words, the transmit power of the RA preamble transmitted on the SBFD resource may be greater than the transmit power of the RA preamble transmitted on the N-SBFD resource.

[0155] A UE may not be able to transmit a PRACH preamble in an RO (e.g., SBFD RO) due to configuration and / or physical constraints of a base station. The UE may use the value of "ramping counter (conuter) + 1" to determine the transmit power of the PRACH preamble in the next RO (e.g., the next SBFD RO). The UE may determine the transmit power using the value of "ramping counter (conuter) + 1" and transmit the PRACH preamble using the transmit power in the next RO (e.g., the next SBFD RO). In other words, the UE may retransmit the PRACH preamble using the increased transmit power. The increased transmit power for retransmission of the PRACH preamble may be determined based on the SBFD power parameter(s). Since the importance of use cases for PRACH transmission in UL subbands may be higher than that of use cases for PRACH transmission in general UL domains, power control for PRACH transmission in UL subbands may differ from power control for PRACH transmission in general UL domains. For example, PRACH transmission in UL subbands may be applied to low-latency scenarios.

[0156] Figure 12 is a flowchart illustrating embodiments of an RA procedure in a communication system supporting SBFD.

[0157] Referring to FIG. 12, a base station may generate RACH configuration information (S1201). The RACH configuration information may include at least one of legacy RACH configuration information or SBFD RACH configuration information. Based on the above-described proposal #1, the RACH configuration information may include only legacy RACH configuration information. Based on the above-described proposal #2, the RACH configuration information may include legacy RACH configuration information and SBFD RACH configuration information. Based on the above-described proposal #3 and / or proposal #4, the RACH configuration information may include configuration information for a two-step RA procedure and / or configuration information for a four-step RA procedure. Based on the above-described proposal #5, the RACH configuration information may include PRACH repetition configuration information (e.g., configuration information for PRACH repeated transmission). Based on the above-described proposal #6, the RACH configuration information may include power parameter(s) (e.g., SBFD power parameter(s)).

[0158] RACH configuration information may be generated by considering at least one of proposals #1 to #6. The base station may transmit the RACH configuration information to the terminal via signaling (e.g., system information, RRC message, MAC CE, and / or DCI) (S1202). The terminal may receive the RACH configuration information via signaling from the base station (S1202). The terminal may check the information included in the RACH configuration information.

[0159] The terminal can check (e.g., determine, judge) an RO (e.g., a valid RO) belonging to a UL subband based on the RACH configuration information (S1203). In S1203, the terminal can optionally perform a procedure for determining the validity of the RO. For example, if SBFD RACH configuration information is received from the base station, the terminal can check the SBFD RO indicated by the SBFD RACH configuration information without performing the procedure for determining the validity of the RO. If SBFD RACH configuration information is not received from the base station (e.g., if SBFD RACH configuration is not indicated to the terminal), the terminal can determine the validity of the RO(s) indicated by the legacy RACH configuration information. Alternatively, regardless of whether SBFD RACH configuration information is received, the terminal can determine the validity of the RO(s) indicated by the SBFD RACH configuration information and / or the legacy RACH configuration information. The terminal may determine the validity of the RO(s) based on the method(s) according to the above-described proposal #1 and / or proposal #2.

[0160] The terminal can transmit a PRACH preamble to the base station in an SBFD RO (e.g., a valid RO) (S1204). Based on the above-described proposal #3 and / or proposal #4, the terminal can transmit a PRACH preamble according to a four-step RA procedure or a MsgA (e.g., MsgA preamble and MsgA PUSCH) according to a two-step RA procedure to the base station. If repeated PRACH transmission is required, the terminal can perform repeated PRACH transmission based on the above-described proposal #5. The terminal can determine the transmission power using the power parameter(s) according to the above-described proposal #6, and can perform PRACH transmission using the transmission power. The base station can receive PRACH transmission from the terminal by performing a monitoring operation in the SBFD RO(s) (S1204). When a PRACH transmission is received from a terminal, the base station can perform subsequent operations with the terminal based on a 4-step RA procedure or a 2-step RA procedure.

[0161] In this disclosure, a terminal may transmit information indicating whether it supports the function(s) proposed in this disclosure to a base station. The information indicating whether it supports the function(s) may be included in a UE capability report. The base station may receive the UE capability report from the terminal and perform signaling and / or operations based on information included in the UE capability information (e.g., information indicating whether it supports the function(s)).

[0162] The configuration for the UL subband (e.g., SBFD configuration) can be transmitted via signaling (e.g., RRC signaling). The SBFD configuration can be transmitted after the transmission of the TDD common configuration. The methods proposed in this disclosure can be applied to both licensed and unlicensed bands. The methods proposed in this disclosure can be applied to the sidelink and / or the supplementary uplink (SUL). For example, the methods proposed in this disclosure can be applied to determine the transmit power in the sidelink and / or the SUL. Each of the proposals of this disclosure can be applied independently, or a combination of the proposals of this disclosure can be applied.

[0163] The operations 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 that stores information readable by a computer system. Furthermore, a computer-readable recording medium can be distributed across network-connected computer systems, allowing the computer-readable program or code to be stored and executed in a distributed manner.

[0164] Additionally, the computer-readable recording medium may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. The program instructions may include not only machine language codes produced by a compiler, but also high-level language codes that can be executed by a computer using an interpreter, etc.

[0165] While some aspects of the present disclosure have been described in the context of a device, they may also represent a description of 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 as 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 or more of the most significant method steps may be performed by such a device.

[0166] 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 the present disclosure. The field-programmable gate array may operate in conjunction with a microprocessor to perform one of the methods described in the present disclosure. In general, the methods are preferably performed by some hardware device.

[0167] Although the present disclosure has been described with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various modifications and changes may be made to the present disclosure without departing from the spirit and scope of the present disclosure as set forth in the claims below.

Claims

1. As a method of UE (user equipment), A step of receiving RACH (random access channel) setting information from a base station; A step of verifying the validity of one or more ROs (RACH occasions) indicated by the above RACH configuration information; and A step of transmitting a random access (RA) preamble to the base station from a valid RO belonging to an uplink (UL) subband among the one or more ROs, UE's method.

2. In claim 1, The above RACH configuration information includes legacy RACH configuration information and SBFD (subband full duplex) RACH configuration information, and the one or more ROs are indicated by the SBFD RACH configuration information. UE's method.

3. In claim 2, The SBFD RACH configuration information is set independently from the legacy RACH configuration information, and each of the SBFD RACH configuration information and the legacy RACH configuration information includes at least one of mapping information between an SSB (synchronization signal block) and an RO or mapping information between the RA preamble and the SSB. UE's method.

4. In claim 1, Among the one or more ROs, an RO that completely belongs to the UL subband is determined to be a valid RO, and among the one or more ROs, an RO that partially belongs to the UL subband is determined to be an invalid RO. UE's method.

5. In claim 1, If a DL (downlink) resource exists during a preset interval before an RO that completely belongs to the UL subband among the above one or more ROs, the RO is judged to be an invalid RO. UE's method.

6. In claim 1, Further comprising a step of transmitting a MsgA (message A) PUSCH (physical uplink shared channel) to the base station in a time interval after the above valid RO, The above RA preamble is a MsgA preamble, and the information of the time interval is included in the RACH configuration information. UE's method.

7. In claim 6, The above valid RO and the above time interval belong to the same UL subband or different UL subbands. UE's method.

8. In claim 1, If there is a time interval in which the MsgA PUSCH can be transmitted after the valid RO, the 2-step RA procedure is performed, and if there is no time interval in which the MsgA PUSCH can be transmitted after the valid RO, the 4-step RA procedure is performed. UE's method.

9. In claim 1, The above RACH configuration information includes at least one of information indicating whether a 4-step RA procedure is supported in the SBFD resource or information indicating whether a 2-step RA procedure is supported in the SBFD resource. UE's method.

10. In claim 1, If the transmission of the RA preamble fails, further comprising a step of retransmitting the RA preamble to the base station in an UL resource indicated by TDD (time division duplexing) dedicated configuration information received from the base station. UE's method.

11. In claim 10, The above RA preamble is retransmitted using increased transmit power determined based on the SBFD power parameter. UE's method.

12. In claim 1, The RACH configuration information includes an SBFD power parameter, and the transmission power of the RA preamble transmitted in the UL subband belonging to the SBFD resource is determined based on the SBFD power parameter, and the SBFD power parameter is set independently from the N-SBFD power parameter used to determine the transmission power of the RA preamble transmitted in the N(non)-SBFD resource. UE's method.

13. As UE (user equipment), Contains at least one processor, At least one processor of the UE, Receive RACH (random access channel) configuration information from the base station; Verify the validity of one or more ROs (RACH occasions) indicated by the above RACH configuration information; and Causing a RA (random access) preamble to be transmitted to the base station from a valid RO belonging to an UL (uplink) subband among the one or more ROs. UE.

14. In claim 13, The above RACH configuration information includes legacy RACH configuration information and SBFD (subband full duplex) RACH configuration information, and the one or more ROs are indicated by the SBFD RACH configuration information. UE.

15. In claim 14, The SBFD RACH configuration information is set independently from the legacy RACH configuration information, and each of the SBFD RACH configuration information and the legacy RACH configuration information includes at least one of mapping information between an SSB (synchronization signal block) and an RO or mapping information between the RA preamble and the SSB. UE.

16. In claim 13, Among the one or more ROs, an RO that completely belongs to the UL subband is determined to be a valid RO, and among the one or more ROs, an RO that partially belongs to the UL subband is determined to be an invalid RO. UE.

17. In claim 13, If a DL (downlink) resource exists during a preset interval before an RO that completely belongs to the UL subband among the above one or more ROs, the RO is judged to be an invalid RO. UE.

18. In claim 13, At least one processor of the UE, Further, it causes the base station to transmit MsgA (message A) PUSCH (physical uplink shared channel) in the time interval after the above valid RO, The above RA preamble is a MsgA preamble, and the information of the time interval is included in the RACH configuration information. UE.

19. In claim 13, At least one processor of the UE, If the transmission of the RA preamble fails, further causing the RA preamble to be retransmitted to the base station in the UL resource indicated by the TDD (time division duplexing) dedicated configuration information received from the base station. UE.

20. In claim 13, The RACH configuration information includes an SBFD power parameter, and the transmission power of the RA preamble transmitted in the UL subband belonging to the SBFD resource is determined based on the SBFD power parameter, and the SBFD power parameter is set independently from the N-SBFD power parameter used to determine the transmission power of the RA preamble transmitted in the N(non)-SBFD resource. UE.

Images