Method and apparatus for random access procedure in SBFD subband

Abstract

A method and an apparatus for a random access procedure in an SBFD subband are disclosed. A method of a user equipment (UE) according to the present invention comprises the steps of: receiving subband full duplex (SBFD) random access channel (RACH) configuration information and legacy RACH configuration information from a base station; determining a valid RACH occasion (RO) on the basis of at least one of the SBFD RACH configuration information and the legacy RACH configuration information; and transmitting a random access (RA) preamble to the base station in the valid RO.

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] According to embodiments of the present disclosure for achieving the above object, a method of a UE (user equipment) includes the steps of: receiving SBFD (subband full duplex) RACH (random access channel) configuration information and legacy RACH configuration information from a base station; determining a valid RO (RACH occasion) based on at least one of the SBFD RACH configuration information or the legacy RACH configuration information; and transmitting an RA (random access) preamble to the base station in the valid RO, wherein the SBFD RACH configuration information is configured for an SBFD UE supporting an SBFD operation, and the legacy RACH configuration information is configured for a legacy UE not supporting the SBFD operation.

[0007] The SBFD RO set by the above SBFD RACH setting information and the legacy RO set by the above legacy RACH setting information can be determined as the valid RO.

[0008] The SBFD RO set by the above SBFD RACH setting information can be determined as the valid RO, and the legacy RO set by the above legacy RACH setting information can be determined as an invalid RO.

[0009] Among the SBFD ROs set by the above SBFD RACH setting information, one or more SBFD ROs belonging to the SBFD resource can be determined as the valid RO, and among the SBFD ROs, at least one SBFD RO that does not belong to the SBFD resource can be determined as an invalid RO.

[0010] Among the SBFD ROs set by the above SBFD RACH setting information, one or more SBFD ROs belonging to the SBFD resource can be determined as the valid RO, and among the SBFD ROs, at least one SBFD RO that does not belong to the SBFD resource can be determined as the valid RO.

[0011] Among the SBFD ROs set by the above SBFD RACH setting information, an SBFD RO that does not overlap with a legacy RO set by the above legacy RACH setting information may be determined as the valid RO, and among the SBFD ROs, an SBFD RO that overlaps with the legacy RO may be determined as the invalid RO.

[0012] Each of the above SBFD RACH configuration information and the above legacy RACH configuration information may include at least one of RACH-configuration common, 2-step RA RACH-configuration common, RACH-configuration dedicated, RACH-configuration generic, or 2-step RA RACH-configuration generic.

[0013] At least one of the above SBFD RACH configuration information or the legacy RACH configuration information may include at least one of a time offset or a frequency offset, and the SBFD RO based on the SBFD RACH configuration information may be determined by applying at least one of the time offset or the frequency offset to the legacy RO configured by the legacy RACH configuration information.

[0014] The mapping rule of the SSB (synchronization signal block) for the SBFD RO set by the above SBFD RACH configuration information may be set differently from the mapping rule of the SSB for the legacy RO set by the above legacy RACH configuration information, and the mapping rule may be a frequency priority mapping rule or a time priority mapping rule.

[0015] In order to achieve the above object, the method of the base station in embodiments of the present disclosure includes the steps of: generating SBFD RACH (random access channel) configuration information for an SBFD UE (user equipment) supporting a SBFD (subband full duplex) operation; generating legacy RACH configuration information for a legacy UE that does not support the SBFD operation; transmitting the SBFD RACH configuration information and the legacy RACH configuration information to the UE; and receiving an RA (random access) preamble from the UE in at least one of an SBFD RO (RACH occasion) configured by the SBFD RACH configuration information or a legacy RO configured by the legacy RACH configuration information.

[0016] Each of the above SBFD RACH configuration information and the above legacy RACH configuration information may include at least one of RACH-configuration common, 2-step RA RACH-configuration common, RACH-configuration dedicated, RACH-configuration generic, or 2-step RA RACH-configuration generic, and the SBFD RACH configuration information may be generated independently from the legacy RACH configuration information.

[0017] The above SBFD RACH configuration information may be generated based on one or more parameters included in the legacy RACH configuration information.

[0018] At least one of the above SBFD RACH configuration information or the above legacy RACH configuration information may include at least one of a time offset or a frequency offset, and the SBFD RO may be determined by applying at least one of the time offset or the frequency offset to the above legacy RO.

[0019] The mapping rule of the SSB (synchronization signal block) for the above SBFD RO may be set differently from the mapping rule of the SSB for the above legacy RO, and the mapping rule may be a frequency priority mapping rule or a time priority mapping rule.

[0020] In 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 subband full duplex (SBFD) random access channel (RACH) configuration information and legacy RACH configuration information from a base station; determine a valid RO (RACH occasion) based on at least one of the SBFD RACH configuration information or the legacy RACH configuration information; and transmit a random access (RA) preamble to the base station in the valid RO, wherein the SBFD RACH configuration information is configured for an SBFD UE supporting an SBFD operation, and the legacy RACH configuration information is configured for a legacy UE not supporting the SBFD operation.

[0021] The SBFD RO set by the above SBFD RACH setting information and the legacy RO set by the above legacy RACH setting information can be determined as the valid RO.

[0022] The SBFD RO set by the above SBFD RACH setting information can be determined as the valid RO, and the legacy RO set by the above legacy RACH setting information can be determined as an invalid RO.

[0023] Among the SBFD ROs set by the above SBFD RACH setting information, one or more SBFD ROs belonging to the SBFD resource can be determined as the valid RO, and among the SBFD ROs, at least one SBFD RO that does not belong to the SBFD resource can be determined as an invalid RO.

[0024] Among the SBFD ROs set by the above SBFD RACH setting information, one or more SBFD ROs belonging to the SBFD resource can be determined as the valid RO, and among the SBFD ROs, at least one SBFD RO that does not belong to the SBFD resource can be determined as the valid RO.

[0025] Among the SBFD ROs set by the above SBFD RACH setting information, an SBFD RO that does not overlap with a legacy RO set by the above legacy RACH setting information may be determined as the valid RO, and among the SBFD ROs, an SBFD RO that overlaps with the legacy RO may be determined as the invalid RO.

[0026] According to the present disclosure, a base station can generate subband full duplex (SBFD) random access channel (RACH) configuration information and legacy RACH configuration information, and transmit the SBFD RACH configuration information and the legacy RACH configuration information to a terminal. The terminal can determine a valid RO (RACH occasion) based on the SBFD RACH configuration information and / or the legacy RACH configuration information received from the base station, and transmit an RA (random access) preamble to the base station in the valid RO. Therefore, the RA procedure can be efficiently performed in SBFD resources (e.g., UL subbands), 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] FIG. 9a is a conceptual diagram illustrating embodiments of a shift method of legacy RO in the frequency domain.

[0037] FIG. 9b is a conceptual diagram illustrating embodiments of a shift method of legacy RO in the time domain.

[0038] Figure 10 is a conceptual diagram illustrating embodiments of shift methods of legacy RO in the time and frequency domains.

[0039] Figure 11 is a flowchart illustrating an RA procedure in a communication system.

[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 network to which the embodiment is applied is not limited to what is described below, and the embodiment may be applied to various communication networks (e.g., 4G communication networks, 5G communication networks, and / or 6G communication networks). Here, the communication network may be used in the same sense as the 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] ● RO validity rules and RO settings for SBFD terminals

[0117] A UL subband may have limited frequency resources. RACH configuration information for an RA procedure in a UL subband may be configured considering the limited frequency resources of the UL subband. For example, information indicating the number of PRACH transmission occasions multiplexed in the frequency domain (e.g., msg1-FDM, msgA-RO-FDM) may be configured considering the frequency resources of the UL subband, and information indicating the number of SSBs per RACH occasion (e.g., ssb-perRACH-Occasion, ssb-perRACH-OccasionTwoStep) may be configured considering the frequency resources of the UL subband.

[0118] RACH configuration information (e.g., RACH configuration) for N-SBFD resources may be referred to as legacy RACH configuration information (e.g., legacy RACH configuration). The legacy RACH configuration information may be referred to as first RACH configuration information for convenience. RACH configuration information (e.g., RACH configuration) for UL subbands (e.g., SBFD resources) may be referred to as SBFD RACH configuration information (e.g., SBFD RACH configuration). The SBFD RACH configuration information may be referred to as second RACH configuration information or additional RACH configuration information for convenience.

[0119] SBFD RACH configuration information can be configured independently from legacy RACH configuration information. Each of the SBFD RACH configuration information and the legacy RACH configuration information can include at least one of RACH-configuration common (e.g., RACH-ConfigCommon), two-step RA RACH-configuration common (e.g., RACH-ConfigCommonTwoStepRA), RACH-configuration dedicated (e.g., RACH-ConfigDedicated), RACH-configuration generic (e.g., RACH-ConfigGeneric), or two-step RA RACH-configuration generic (e.g., RACH-ConfigGenericTwoStepRA). Some or all of the parameters included in the legacy RACH configuration information can be reconfigured for an RA procedure in a UL subband, and some or all of the reconfigured parameters can be included in the SBFD RACH configuration information. In other words, the parameter(s) included in the SBFD RACH configuration information can be set based on the parameter(s) included in the legacy RACH configuration information. The base station can transmit the legacy RACH configuration information and the SBFD RACH configuration information to the terminal through signaling. The SBFD terminal can receive the legacy RACH configuration information and the SBFD RACH configuration information through signaling from the base station. The legacy terminal can receive the legacy RACH configuration information and the SBFD RACH configuration information through signaling from the base station. According to the above-described method, the signaling overhead of the RACH configuration information may increase.

[0120] The base station can generate RACH configuration information for an SBFD terminal (e.g., SBFD RACH configuration information) and RACH configuration information for an N-SBFD terminal (e.g., legacy RACH configuration information), transmit the SBFD RACH configuration information to the SBFD terminal through signaling, and transmit the legacy RACH configuration information to the N-SBFD terminal (e.g., legacy terminal) through signaling. The manner in which each of the legacy RACH configuration information and the SBFD RACH configuration information is configured may be referred to as an independent configuration manner.

[0121] Alternatively, the SBFD RACH configuration information may not be configured separately, and the SBFD terminal and / or the legacy terminal may perform the RA procedure based on the legacy RACH configuration information. The legacy RACH configuration information may be commonly used by the SBFD terminal and the legacy terminal. A method in which only the legacy RACH configuration information is configured may be referred to as a common configuration method. The SBFD terminal and / or the base station may determine the RO(s) belonging to the UL subband (e.g., the RO(s) overlapping with the UL subband) as valid RO(s).

[0122] The base station can support at least one of the independent configuration method or the common configuration method. If the base station supports the independent configuration method, the SBFD terminal can be expected to transmit the RA preamble (e.g., msg1, msgA) on the RACH resource indicated by the SBFD RACH configuration information, and the legacy terminal can be expected to transmit the RA preamble (e.g., msg1, msgA) on the RACH resource indicated by the legacy RACH configuration information. The RACH resource can mean an RO (RACH occasion).

[0123] An RO indicated by the SBFD RACH configuration information can be configured not only in an SBFD resource (e.g., a UL subband) but also in an N-SBFD resource (e.g., a UL resource and / or a UL symbol within the N-SBFD resource). An SBFD terminal can determine an RO configured within an SBFD resource (e.g., a UL subband) as a valid RO and transmit an RA preamble in the valid RO. An SBFD terminal can determine an RO configured within an N-SBFD resource as a valid RO and transmit an RA preamble in the valid RO. Among the ROs indicated by the SBFD RACH configuration information, an RO belonging to an N-SBFD resource may overlap with an RO configured for a legacy terminal (e.g., an RO indicated by the legacy RACH configuration information). In this situation, transmission of an RA preamble of an SBFD terminal may collide with transmission of an RA preamble of a legacy terminal. Due to the above collision issue, the SBFD terminal may not expect the RA preamble to be transmitted in the RO indicated by the SBFD RACH configuration information within the N-SBFD resource. In other words, the SBFD terminal may determine the RO belonging to the N-SBFD resource among the ROs indicated by the SBFD RACH configuration information as an invalid RO.

[0124] Since the UL subband has limited resources (e.g., time resources, frequency resources, and / or spatial resources), it may be difficult to apply the existing RACH format (e.g., legacy RACH format) to the UL subband (e.g., UL region, UL resources). At least, information related to the RACH format (e.g., prach-ConfigurationIndex) can be separately configured for SBFD terminals. At least, information related to RO configuration (e.g., ssb-perRACH-Occasion, ssb-perRACH-OccasionTwoStep) can be separately configured for SBFD terminals. At least information related to RACH frequency configuration (e.g., msg1-FrequencyStart, msgA-RO-FrequencyStart, msg1-FDM, msgA-RO-FDM) may be separately configured for SBFD terminals. Each of msg1-FrequencyStart and msgA-RO-FrequencyStart may indicate an offset between PRB 0 and the lowest PRACH transmission occasion in the frequency domain.

[0125] ◆ Proposal #1: Single RACH configuration (e.g., common RACH configuration)

[0126] The base station can set the same RACH configuration (e.g., common RACH configuration) to the SBFD terminal and the legacy terminal. For example, the same PRACH configuration index (e.g., PRACH-ConfigurationIndex, msgA-PRACH-ConfigurationIndex) can be set to the SBFD terminal and the legacy terminal. The SBFD terminal and the legacy terminal can transmit the RA preamble in the RO(s) existing in the N-SBFD resource. The base station can expect to receive the RA preamble from the SBFD terminal and / or the legacy terminal in the RO(s) existing in the N-SBFD resource. The SBFD terminal can transmit the RA preamble in the RO(s) existing in the SBFD resource (e.g., UL subband). The legacy terminal may not transmit the RA preamble in the RO(s) existing in the SBFD resource (e.g., UL subband). The base station may expect to receive an RA preamble from an SBFD terminal in the RO(s) existing within the SBFD resource (e.g., UL subband).

[0127] In an embodiment based on Proposal #1, no additional configuration may be required. In an embodiment based on Proposal #1, validity rules may be required to determine valid ROs. For example, rules may be required to determine the validity of ROs that partially or fully overlap with guard bands and / or guard intervals. An SBFD terminal may determine ROs that partially or fully overlap with guard bands and / or guard intervals as invalid ROs and may not transmit RA preambles in invalid ROs. The base station may not expect to receive RA preambles in invalid ROs.

[0128] ◆ Proposal #2: Two RACH configurations (e.g., independent RACH configurations)

[0129] Legacy RACH configuration information and SBFD RACH configuration information can be configured independently. Each of the SBFD RACH configuration information and the legacy RACH configuration information can include at least one of RACH-configuration common (e.g., RACH-ConfigCommon), two-step RA RACH-configuration common (e.g., RACH-ConfigCommonTwoStepRA), RACH-configuration dedicated (e.g., RACH-ConfigDedicated), RACH-configuration generic (e.g., RACH-ConfigGeneric), or two-step RA RACH-configuration generic. In addition, each of the SBFD RACH configuration information and the legacy RACH configuration information can include other information in addition to the above information.

[0130] Specifically, each of the SBFD RACH configuration information and the legacy RACH configuration information may include a PRACH configuration index (e.g., PRACH-ConfigurationIndex, msgA-PRACH-ConfigurationIndex), frequency configuration parameters (e.g., msg1-FrequencyStart, msgA-RO-FrequencyStart, msg1-FDM, msgA-RO-FDM), power related parameters (e.g., preambleReceivedTargetPower, powerRampingStep, msgA-PreamblePowerRampingStep, msgA-PreambleReceivedTargetPower), SSB-RO mapping related parameters (e.g., ssb-perRACH-OccasionAndCB-PreamblesPerSSB, msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB), etc.

[0131] In an embodiment based on Proposal #2, a rule may be needed as to in which RO a terminal (e.g., an SBFD terminal and / or a legacy terminal) transmits an RA preamble among the RO configured by the legacy RACH configuration information and the RO configured by the SBFD RACH configuration information.

[0132] ◆ Proposal #3: Setting dedicated parameters (e.g., additional parameters) for SBFD terminals

[0133] Some parameters configured for legacy terminals (e.g., PRACH-ConfigurationIndex, msgA-PRACH-ConfigurationIndex, msg1-FrequencyStart, msgA-RO-FrequencyStart, msg1-FDM, msgA-RO-FDM, etc.) can be additionally configured for SBFD terminals. The base station can transmit some parameters additionally configured for SBFD terminals to the SBFD terminal through signaling. The SBFD terminal can receive some parameters through signaling from the base station. Alternatively, new parameters (e.g., dedicated parameters) for the SBFD terminal can be added to legacy RACH configuration information. New parameters for the SBFD terminal can be generated based on parameters included in the legacy RACH configuration information. The base station can transmit legacy RACH configuration information including new parameters for the SBFD terminal to the terminals (e.g., legacy terminals and / or SBFD terminals). A legacy terminal and / or an SBFD terminal can receive legacy RACH configuration information through signaling from a base station and check new parameters for the SBFD terminal included in the RACH configuration information.

[0134] In the RA procedure, new parameters for SBFD terminals may be referred to as SBFD parameters. The new parameters (e.g., SBFD parameters) may be included in legacy RACH configuration information and / or SBFD RACH configuration information. The SBFD parameters may include a time offset (e.g., time shift information) and / or a frequency offset (e.g., frequency shift information) for RO(s) configured by the legacy RACH configuration information. An RO configured by the legacy RACH configuration information may be referred to as a legacy RO. In other words, a legacy RO may refer to an RO configured for a legacy terminal (e.g., an N-SBFD terminal). An RO configured by SBFD RACH configuration information (e.g., SBFD parameters) may be referred to as an SBFD RO. In other words, an SBFD RO may refer to an RO configured for an SBFD terminal.

[0135] The SBFD RO can be set at a position that is a time offset from the legacy RO in the time domain. The SBFD RO can be set at a position that is a frequency offset from the legacy RO in the frequency domain. The UL subband can be variably set in the time and frequency domains, and the legacy RO can be set without considering the position of the UL subband set in the time and frequency domains. The legacy RO may not belong to a UL subband, and the time offset and / or frequency offset can be used to move the legacy RO into a UL subband.

[0136] FIG. 9a is a conceptual diagram illustrating embodiments of a shift method of a legacy RO in the frequency domain, and FIG. 9b is a conceptual diagram illustrating embodiments of a shift method of a legacy RO in the time domain.

[0137] Referring to FIGS. 9A and 9B, RO may mean a legacy RO. The legacy RO may be configured based on legacy RACH configuration information. The legacy RO may be located outside a UL subband. An SBFD terminal may not transmit an RA preamble in a legacy RO located outside a UL subband. The base station may transmit a time offset (e.g., time shift information) and / or a frequency offset (e.g., frequency shift information) to the terminal through signaling in order to move the legacy RO configured by the legacy RACH configuration information into a UL subband. The time offset and / or the frequency offset may be included in the legacy RACH configuration information and / or the SBFD RACH configuration information. The terminal may receive the time offset and / or the frequency offset through signaling from the base station.

[0138] In the embodiment of FIG. 9a, a frequency offset may be applied to a legacy RO, and the legacy RO to which the frequency offset is applied may belong to a UL subband. By applying the frequency offset, the legacy RO belonging to the UL subband may be interpreted (e.g., regarded) as a SBFD RO. The frequency offset may be applied to the lowest subcarrier or the highest subcarrier of consecutive legacy ROs.

[0139] In the embodiment of FIG. 9b, a time offset may be applied to a legacy RO, and the legacy RO to which the time offset is applied may belong to a UL subband. By applying the time offset, the legacy RO belonging to the UL subband may be interpreted (e.g., regarded) as an SBFD RO. The time offset may be applied to the start symbol or the last symbol of consecutive legacy ROs.

[0140] Meanwhile, the base station can transmit a time offset and / or a frequency offset to the terminal using at least one of an RRC message, MAC CE, or DCI. The terminal can receive a signaling message (e.g., an RRC message, MAC CE, and / or DCI) from the base station and check the time offset and / or frequency offset included in the signaling message. The RO can be set in slot units. A slot in which the RO is set can be referred to as a RACH slot. The base station can generate RACH slot configuration information and transmit the RACH slot configuration information to the terminal using at least one of an RRC message, MAC CE, or DCI. The terminal can receive a signaling message (e.g., an RRC message, MAC CE, and / or DCI) from the base station and check the RACH slot configuration information included in the signaling message.

[0141] RACH slot configuration information may be set as a bitmap. The RACH slot configuration information may include at least one of information about RACH slot(s), information about RO(s) belonging to each RACH slot, or information about the validity of the RO(s). An RO belonging to a RACH slot may be indicated (e.g., set) as valid. In other words, the RACH slot configuration information may include information indicating that an RO belonging to a RACH slot is valid.

[0142] Figure 10 is a conceptual diagram illustrating embodiments of shift methods of legacy RO in the time and frequency domains.

[0143] Referring to FIG. 10, RO may mean a legacy RO. The legacy RO may be configured based on legacy RACH configuration information. The legacy RO may be located outside a UL subband. An SBFD terminal may not transmit an RA preamble in a legacy RO located outside a UL subband. The base station may transmit a time offset (e.g., time shift information) and a frequency offset (e.g., frequency shift information) to the terminal through signaling to move the legacy RO configured by the legacy RACH configuration information into a UL subband. The time offset and the frequency offset may be included in the legacy RACH configuration information and / or the SBFD RACH configuration information. The terminal may receive the time offset and the frequency offset through signaling from the base station.

[0144] Time offsets and frequency offsets can be applied to legacy ROs. By applying time offsets and frequency offsets, legacy ROs belonging to a UL subband can be interpreted (e.g., considered) as SBFD ROs. The time offset can be applied to the start symbol or the last symbol of consecutive legacy ROs. The frequency offset can be applied to the lowest or highest subcarrier of consecutive legacy ROs.

[0145] Among the legacy ROs with time offset and frequency offset, some legacy ROs may not entirely belong to the UL subband. In other words, some legacy ROs may span resources outside the UL subband (e.g., UL resources) and UL subbands. SBFD UEs and / or base stations may expect not to perform PRACH transmissions in some legacy ROs (e.g., ROs that do not entirely belong to the UL subband). Alternatively, PRACH transmissions may be allowed in ROs that fall within a time interval (e.g., n symbols) before the start symbol of the UL subband among some legacy ROs (e.g., ROs that do not entirely belong to the UL subband). PRACH transmissions may be allowed in ROs that fall within a time interval (e.g., n symbols) after the end symbol of the UL subband among some legacy ROs (e.g., ROs that do not entirely belong to the UL subband). A time interval (e.g., n symbols) may be defined in a technical specification. Alternatively, the base station may signal the time interval (e.g., n symbols) to the terminal. n may be a natural number.

[0146] Among some legacy ROs (e.g., ROs that do not entirely belong to a UL subband), PRACH transmission may be allowed in RO(s) that belong to a frequency range (e.g., m subcarriers) lower than the lowest subcarrier of the UL subband. Among some legacy ROs (e.g., ROs that do not entirely belong to a UL subband), PRACH transmission may be allowed in RO(s) that belong to a frequency range (e.g., m subcarriers) higher than the highest subcarrier of the UL subband. The frequency range (e.g., m subcarriers) may be defined in a technical specification. Alternatively, the base station may signal the frequency range (e.g., m subcarriers) to the UE. m may be a natural number. The SBFD UE and / or the base station may expect to perform PRACH transmission in RO(s) where PRACH transmission is allowed among some legacy ROs (e.g., ROs that do not entirely belong to a UL subband).

[0147] Proposal #4

[0148] The base station can transmit legacy RACH configuration information and SBFD RACH configuration information to the terminal through signaling. The terminal can receive the legacy RACH configuration information and SBFD RACH configuration information through signaling from the base station. The SBFD terminal can expect to transmit the RA preamble in the RO indicated by the legacy RACH configuration information (e.g., the legacy RO). In other words, the SBFD terminal can expect to transmit the RA preamble in the RO indicated by the legacy RACH configuration information (e.g., the SBFD RO) as well as the RO indicated by the legacy RACH configuration information (e.g., the legacy RO). The SBFD terminal can determine both the SBFD RO and the legacy RO as valid ROs.

[0149] When the priority of the SBFD terminal is higher than that of the legacy terminal, an embodiment based on proposal #4 can be performed. The SBFD terminal can transmit or retransmit an RA preamble in the RO based on RACH configuration information (e.g., power-related parameters, transmission-related parameters) associated with the RO. The power-related parameters can include power control adjustment information, preambleReceivedTargetPower, powerRampingStep, msgA-PreamblePowerRampingStep, msgA-PreambleReceivedTargetPower, etc. For example, when the SBFD terminal transmits or retransmits an RA preamble in the SBFD RO, the SBFD terminal can transmit or retransmit the RA preamble based on the SBFD RACH configuration information. When an SBFD terminal transmits or retransmits an RA preamble in a legacy RO, the SBFD terminal can transmit or retransmit the RA preamble based on legacy RACH configuration information.

[0150] The SBFD terminal can separately perform the transmission procedure (or retransmission procedure) of the RA preamble in the legacy RO and the transmission procedure (or retransmission procedure) of the RA preamble in the SBFD RO. In other words, the transmission procedure (or retransmission procedure) of the RA preamble in the legacy RO and the transmission procedure (or retransmission procedure) of the RA preamble in the SBFD RO can be performed in parallel. The RO used by the SBFD terminal for PRACH transmission (e.g., transmission of the RA preamble) can be the SBFD RO and / or the legacy RO.

[0151] Proposal #5

[0152] The base station can transmit legacy RACH configuration information and SBFD RACH configuration information to the terminal through signaling. The terminal can receive the legacy RACH configuration information and SBFD RACH configuration information through signaling from the base station. The SBFD terminal may not expect to transmit an RA preamble in a legacy RO indicated by the legacy RACH configuration information. In other words, the SBFD terminal may transmit an RA preamble in the SBFD RO indicated by the SBFD RACH configuration information, and may not transmit an RA preamble in the legacy RO indicated by the legacy RACH configuration information. The SBFD terminal may determine the SBFD RO as a valid RO, and may determine the legacy RO as an invalid RO.

[0153] To ensure fairness between SBFD terminals and legacy terminals, SBFD terminals may perform RA procedures based on SBFD RACH configuration information, and legacy terminals may perform RA procedures based on legacy RACH configuration information. In other words, SBFD terminals may not perform RA procedures based on legacy RACH configuration information, and legacy terminals may not perform RA procedures based on SBFD RACH configuration information.

[0154] A situation may arise where an SBFD RO overlaps with a legacy RO. An SBFD terminal may not expect transmission of an RA preamble in an SBFD RO that overlaps with a legacy RO. An SBFD terminal may determine an SBFD RO that overlaps with a legacy RO as an invalid RO. A legacy terminal may not expect transmission of an RA preamble in a legacy RO that overlaps with an SBFD RO. A legacy terminal may determine a legacy RO that overlaps with an SBFD RO as an invalid RO.

[0155] The number of SBFD terminals having SBFD ROs overlapping legacy ROs may be relatively small, and the SBFD terminals may not transmit RA preambles in SBFD ROs overlapping legacy ROs. Alternatively, since contention resolution operations are performed in the RA procedure, SBFD terminals and / or legacy terminals may be expected to transmit RA preambles in all ROs regardless of the RO type (e.g., SBFD RO or legacy RO). All ROs may contain overlapping RO(s).

[0156] ◆ Proposal #6

[0157] The base station can transmit legacy RACH configuration information and SBFD RACH configuration information to the terminal through signaling. The terminal can receive legacy RACH configuration information and SBFD RACH configuration information through signaling from the base station. The SBFD RACH configuration information may be valid within the UL subband. In other words, among the ROs configured by the SBFD RACH configuration information, the RO(s) belonging to the UL subband can be determined as valid RO(s), and among the ROs configured by the SBFD RACH configuration information, the RO(s) not belonging to the UL subband can be determined as invalid RO(s).

[0158] ROs according to an RO pattern based on SBFD RACH configuration information may exist not only in UL subbands but also in UL resources (e.g., UL resources other than UL subbands). SBFD ROs existing in UL resources other than UL subbands may overlap with legacy ROs. When an SBFD terminal performs PRACH transmission in an SBFD RO overlapping with a legacy RO, and a legacy terminal performs PRACH transmission in a legacy RO overlapping with an SBFD RO, interference and / or collision may occur between the PRACH transmissions. Therefore, among the ROs configured by the SBFD RACH configuration information, only RO(s) belonging to a UL subband may be determined as valid RO(s), and the SBFD terminal may perform PRACH transmission in the valid RO(s).

[0159] ◆ Proposal #7

[0160] The base station can transmit legacy RACH configuration information and SBFD RACH configuration information to the terminal through signaling. The terminal can receive the legacy RACH configuration information and SBFD RACH configuration information through signaling from the base station. The SBFD RACH configuration information can be valid not only for UL subbands but also for UL resources (e.g., UL resources other than UL subbands). The SBFD terminal can expect to transmit an RA preamble in an SBFD RO existing in UL resources other than UL subbands. The SBFD terminal can transmit an RA preamble in an SBFD RO indicated by the SBFD RACH configuration information and / or a legacy RO indicated by the legacy RACH configuration information.

[0161] Meanwhile, the terminal may determine valid RO(s) based on the validity rule, and perform SSB-RO mapping and / or preamble-SSB mapping for the valid RO(s). SSB-RO mapping may mean mapping an SSB (e.g., an SSB index) to a valid RO. Preamble-SSB mapping may mean mapping a preamble (e.g., a preamble index, an RA preamble index) to an SSB (e.g., an SSB index). The mapping rule for a valid RO (e.g., an SBFD RO) in the time and frequency domains may be the same as the mapping rule for a legacy RO. The mapping rule for a legacy RO may be a frequency-first mapping rule. When the frequency-first mapping rule is applied, the SSB (e.g., an SSB index) may be first mapped to ROs multiplexed in the frequency domain, and then the SSB (e.g., an SSB index) may be mapped to ROs multiplexed in the time domain.

[0162] Since UL subbands have limited sizes, a new mapping rule can be applied to SBFD ROs instead of the mapping rule for legacy ROs. The new mapping rule can be a time-first mapping rule. When a time-first mapping rule is applied, SSBs (e.g., SSB indices) can be first mapped to ROs multiplexed in the time domain, and then SSBs (e.g., SSB indices) can be mapped to ROs multiplexed in the frequency domain.

[0163] The base station can transmit information about mapping rules (e.g., frequency priority mapping rules or time priority mapping rules) to the terminal via signaling. The terminal can receive information about the mapping rules via signaling from the base station and perform SSB-RO mapping based on the mapping rules indicated by the information.

[0164] When ROs are consecutively present in N-SBFD symbol(s) and SBFD symbol(s), the above-described mapping rule (e.g., time-first mapping rule) can be applied to the ROs. The above-described embodiment can be applied when ROs are configured based on SBFD RACH configuration information. When legacy RACH configuration and SBFD RACH configuration are independently indicated (e.g., configured) to the UE, the UE can apply the existing mapping rule (e.g., frequency-first mapping rule) to the legacy RO(s) based on the legacy RACH configuration, and the UE can apply the new mapping rule (e.g., time-first mapping rule) to the SBFD RO(s) based on the SBFD RACH configuration. The mapping operation for the legacy RO(s) and the mapping operation for the SBFD RO(s) can be performed independently.

[0165] An SBFD terminal can transmit an RA preamble in an SBFD RO using power-related parameters included in the SBFD RACH configuration information. An SBFD terminal can transmit an RA preamble in a legacy RO using power parameters included in the legacy RACH configuration information. The above-described embodiment can be performed to ensure fairness between SBFD terminals and legacy terminals.

[0166] An SBFD terminal can transmit an RA preamble using power-related parameters associated with signaling for configuring an RO. For example, if an RO located in an N-SBFD resource is configured based on SBFD RACH configuration information, the SBFD terminal can transmit an RA preamble in the RO using power parameters included in the SBFD RACH configuration information. If an RO located in an N-SBFD resource is configured based on legacy RACH configuration information, the SBFD terminal can transmit an RA preamble in the RO using power parameters included in the legacy RACH configuration information.

[0167] Figure 11 is a flowchart illustrating an RA procedure in a communication system.

[0168] Referring to FIG. 11, a base station and / or a terminal may support an SBFD operation. The base station may generate RACH configuration information (S1101). The RACH configuration information generated in S1101 may include SBFD RACH configuration information and legacy RACH configuration information. In other words, the base station may generate SBFD RACH configuration information and legacy RACH configuration information. Each of the SBFD RACH configuration information and the legacy RACH configuration information may include at least one of RACH-configuration common, 2-step RA RACH-configuration common, RACH-configuration only, RACH-configuration general, or 2-step RA RACH-configuration general. The SBFD RACH configuration information and the legacy RACH configuration information may be generated independently of each other. Alternatively, the SBFD RACH configuration information (e.g., some parameter(s) included in the SBFD RACH configuration information) may be generated (e.g., determined) based on the parameter(s) included in the legacy RACH configuration information.

[0169] The base station can transmit a signaling message (e.g., an RRC message, MAC CE, and / or DCI) including SBFD RACH configuration information and legacy RACH configuration information to the terminal (S1102). The terminal can receive the signaling message from the base station (S1102). The terminal can check the SBFD RACH configuration information and legacy RACH configuration information included in the signaling message. The terminal can determine a valid RO based on at least one of the SBFD RACH configuration information or the legacy RACH configuration information (S1103).

[0170] At least one of the SBFD RACH configuration information or the legacy RACH configuration information may include at least one of a time offset or a frequency offset. The SBFD RO based on the SBFD RACH configuration information may be determined by applying at least one of a time offset or a frequency offset to a legacy RO configured by the legacy RACH configuration information. The mapping rule of the SSB for the SBFD RO configured by the SBFD RACH configuration information may be configured differently from the mapping rule of the SSB for the legacy RO configured by the legacy RACH configuration information. The mapping rule may be a frequency-priority mapping rule or a time-priority mapping rule.

[0171] Based on Proposal #4, a terminal (e.g., an SBFD terminal) can determine (e.g., judge) the SBFD RO configured by the SBFD RACH configuration information and the legacy RO configured by the legacy RACH configuration information as valid ROs. The terminal can perform PRACH transmission in the valid RO (S1104). In other words, the terminal can transmit an RA preamble to the base station in the valid RO. The base station can receive the RA preamble from the terminal in the RO(s) configured by the SBFD RACH configuration information and / or the legacy RACH configuration information (S1104). The base station can confirm the valid RO in the terminal based on Proposal #4 and perform a monitoring operation for reception of the RA preamble in the valid RO. Alternatively, the base station can perform a monitoring operation for reception of the RA preamble in all ROs configured by the SBFD RACH configuration information and / or the legacy RACH configuration information. The base station can estimate the RO from which the RA preamble is received as a valid RO from the terminal.

[0172] Based on Proposal #5, a UE (e.g., an SBFD UE) can determine an SBFD RO configured by SBFD RACH configuration information as a valid RO, and can determine a legacy RO configured by legacy RACH configuration information as an invalid RO. The SBFD RO can be configured in an SBFD resource (e.g., a UL subband) and / or an N-SBFD resource (e.g., a UL resource). If the SBFD RO is configured in an N-SBFD resource, the SBFD RO can overlap with a legacy RO. The UE can determine an SBFD RO overlapping with a legacy RO as an invalid RO. Alternatively, the UE can determine an SBFD RO overlapping with a legacy RO as a valid RO. The UE can perform a PRACH transmission in the valid RO (S1104). In other words, the UE can transmit an RA preamble to the base station in the valid RO. The base station can receive an RA preamble from the terminal in the RO(s) configured by the SBFD RACH configuration information and / or the legacy RACH configuration information (S1104). The base station can check a valid RO from the terminal based on Proposal #5 and perform a monitoring operation for reception of the RA preamble in the valid RO. Alternatively, the base station can perform a monitoring operation for reception of the RA preamble in all ROs configured by the SBFD RACH configuration information and / or the legacy RACH configuration information. The base station can estimate the RO in which the RA preamble is received as a valid RO from the terminal.

[0173] Based on Proposal #6, a terminal (e.g., an SBFD terminal) can determine SBFD RO(s) belonging to SBFD resources (e.g., UL subbands) among SBFD ROs configured by SBFD RACH configuration information as valid RO(s), and can determine SBFD RO(s) not belonging to SBFD resources (e.g., UL subbands) among SBFD ROs as invalid RO(s). The terminal can perform PRACH transmission in the valid RO (S1104). In other words, the terminal can transmit an RA preamble to the base station in the valid RO. The base station can receive an RA preamble from the terminal in the RO(s) configured by the SBFD RACH configuration information and / or legacy RACH configuration information (S1104). The base station can confirm a valid RO in the terminal based on Proposal #6, and can perform a monitoring operation for reception of an RA preamble in the valid RO. Alternatively, the base station may perform a monitoring operation for reception of an RA preamble in all ROs configured by the SBFD RACH configuration information and / or the legacy RACH configuration information. The base station may assume that the RO in which the RA preamble is received is a valid RO for the terminal.

[0174] Based on Proposal #7, a terminal (e.g., an SBFD terminal) can determine SBFD RO(s) belonging to SBFD resources (e.g., UL subbands) among SBFD ROs configured by SBFD RACH configuration information as valid RO(s), and can determine SBFD RO(s) not belonging to SBFD resources (e.g., UL subbands) among SBFD ROs as valid RO(s). The terminal can perform PRACH transmission in the valid RO (S1104). In other words, the terminal can transmit an RA preamble to the base station in the valid RO. The base station can receive an RA preamble from the terminal in the RO(s) configured by the SBFD RACH configuration information and / or legacy RACH configuration information (S1104). The base station can confirm a valid RO in the terminal based on Proposal #7, and can perform a monitoring operation for reception of an RA preamble in the valid RO. Alternatively, the base station may perform a monitoring operation for reception of an RA preamble in all ROs configured by the SBFD RACH configuration information and / or the legacy RACH configuration information. The base station may assume that the RO in which the RA preamble is received is a valid RO for the terminal.

[0175] In the present disclosure, a UL subband may refer to a UL subband for SBFD operation. In the present disclosure, a terminal may transmit information indicating whether it supports the function(s) proposed in the present 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 a 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)).

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

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

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

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

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

[0181] 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 SBFD (subband full duplex) RACH (random access channel) configuration information and legacy RACH configuration information from a base station; A step of determining a valid RO (RACH occasion) based on at least one of the above SBFD RACH configuration information or the above legacy RACH configuration information; and A step of transmitting a RA (random access) preamble to the base station from the above valid RO is included, The above SBFD RACH configuration information is set for an SBFD UE that supports the SBFD operation, and the above legacy RACH configuration information is set for a legacy UE that does not support the SBFD operation. UE's method.

2. In claim 1, The SBFD RO set by the above SBFD RACH setting information and the legacy RO set by the above legacy RACH setting information are determined as the valid RO. UE's method.

3. In claim 1, The SBFD RO set by the above SBFD RACH setting information is determined as the valid RO, and the legacy RO set by the above legacy RACH setting information is determined as an invalid RO. UE's method.

4. In claim 1, Among the SBFD ROs set by the above SBFD RACH setting information, one or more SBFD ROs belonging to the SBFD resource are determined as the valid RO, and among the SBFD ROs, at least one SBFD RO that does not belong to the SBFD resource is determined as an invalid RO. UE's method.

5. In claim 1, Among the SBFD ROs set by the above SBFD RACH setting information, one or more SBFD ROs belonging to the SBFD resource are determined as the valid RO, and among the SBFD ROs, at least one SBFD RO that does not belong to the SBFD resource is determined as the valid RO. UE's method.

6. In claim 1, Among the SBFD ROs set by the above SBFD RACH setting information, an SBFD RO that does not overlap with a legacy RO set by the above legacy RACH setting information is determined as the valid RO, and among the SBFD ROs, an SBFD RO that overlaps with the legacy RO is determined as the invalid RO. UE's method.

7. In claim 1, Each of the above SBFD RACH configuration information and the above legacy RACH configuration information includes at least one of RACH-configuration common, 2-step RA RACH-configuration common, RACH-configuration dedicated, RACH-configuration generic, or 2-step RA RACH-configuration generic. UE's method.

8. In claim 1, At least one of the SBFD RACH configuration information or the legacy RACH configuration information includes at least one of a time offset or a frequency offset, and the SBFD RO based on the SBFD RACH configuration information is determined by applying at least one of the time offset or the frequency offset to the legacy RO configured by the legacy RACH configuration information. UE's method.

9. In claim 1, The mapping rule of the SSB (synchronization signal block) for the SBFD RO set by the above SBFD RACH configuration information is set differently from the mapping rule of the SSB for the legacy RO set by the above legacy RACH configuration information, and the mapping rule is a frequency priority mapping rule or a time priority mapping rule. UE's method.

10. As a method of base station, A step of generating SBFD RACH (random access channel) configuration information for an SBFD UE (user equipment) supporting SBFD (subband full duplex) operation; A step of generating legacy RACH configuration information for a legacy UE that does not support the above SBFD operation; A step of transmitting the SBFD RACH configuration information and the legacy RACH configuration information to the UE; and A step of receiving an RA (random access) preamble from the UE in at least one of an SBFD RO (RACH occasion) set by the SBFD RACH setting information or a legacy RO set by the legacy RACH setting information, Base station method.

11. In claim 10, The SBFD RACH configuration information and the legacy RACH configuration information each include at least one of RACH-configuration common, 2-step RA RACH-configuration common, RACH-configuration dedicated, RACH-configuration generic, or 2-step RA RACH-configuration generic, and the SBFD RACH configuration information is generated independently from the legacy RACH configuration information. Base station method.

12. In claim 10, The above SBFD RACH configuration information is generated based on one or more parameters included in the legacy RACH configuration information. Base station method.

13. In claim 10, At least one of the SBFD RACH configuration information or the legacy RACH configuration information includes at least one of a time offset or a frequency offset, and the SBFD RO is determined by applying at least one of the time offset or the frequency offset to the legacy RO. Base station method.

14. In claim 10, The mapping rule of the SSB (synchronization signal block) for the above SBFD RO is set differently from the mapping rule of the SSB for the above legacy RO, and the mapping rule is a frequency priority mapping rule or a time priority mapping rule. Base station method.

15. As UE (user equipment), Contains at least one processor, At least one processor of the UE, Receive SBFD (subband full duplex) RACH (random access channel) configuration information and legacy RACH configuration information from a base station; Determine a valid RO (RACH occasion) based on at least one of the above SBFD RACH configuration information or the above legacy RACH configuration information; and Causes the above valid RO to transmit a RA (random access) preamble to the base station, The above SBFD RACH configuration information is set for an SBFD UE that supports the SBFD operation, and the above legacy RACH configuration information is set for a legacy UE that does not support the SBFD operation. UE.

16. In claim 15, The SBFD RO set by the above SBFD RACH setting information and the legacy RO set by the above legacy RACH setting information are determined as the valid RO. UE.

17. In claim 15, The SBFD RO set by the above SBFD RACH setting information is determined as the valid RO, and the legacy RO set by the above legacy RACH setting information is determined as an invalid RO. UE.

18. In claim 15, Among the SBFD ROs set by the above SBFD RACH setting information, one or more SBFD ROs belonging to the SBFD resource are determined as the valid RO, and among the SBFD ROs, at least one SBFD RO that does not belong to the SBFD resource is determined as an invalid RO. UE.

19. In claim 15, Among the SBFD ROs set by the above SBFD RACH setting information, one or more SBFD ROs belonging to the SBFD resource are determined as the valid RO, and among the SBFD ROs, at least one SBFD RO that does not belong to the SBFD resource is determined as the valid RO. UE.

20. In claim 15, Among the SBFD ROs set by the above SBFD RACH setting information, an SBFD RO that does not overlap with a legacy RO set by the above legacy RACH setting information is determined as the valid RO, and among the SBFD ROs, an SBFD RO that overlaps with the legacy RO is determined as the invalid RO. UE.

Images