Method and apparatus for performing communication in wireless communication system

Abstract

Disclosed according to various embodiments are a method performed by UE and an apparatus therefor. Disclosed are a method and an apparatus for receiving configuration information including information about a first time resource related to sub-band full duplex (SBFD), receiving a first RACH configuration for a random access channel occasion (RO) and a second RACH configuration for an additional RO related to the SBFD, and transmitting a physical random access channel (PRACH) on the basis of at least one of the RO and the additional RO.

Description

Method for performing communication in a wireless communication system and device therefor

[0001] This relates to a method for a terminal to perform communication in a wireless communication system and a device therefor.

[0002] Wireless communication systems are multiple access systems that support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and multi-carrier frequency division multiple access (MC-FDMA).

[0003] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Furthermore, massive Machine Type Communications (MTC), which connects numerous devices and objects to provide various services anytime, anywhere, is also a key issue to be considered in next-generation communication. Furthermore, communication system design that considers reliability and latency-sensitive services / terminals is being discussed. The introduction of next-generation radio access technologies that take into account enhanced mobile broadband communication, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) is being discussed. For convenience, these technologies are referred to as new RAT or NR in the present invention.

[0004] The technical challenge is to provide a more accurate and efficient way to transmit and receive signals.

[0005] The technical challenges are not limited to the technical challenges mentioned above, and other technical challenges not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the description below.

[0006] A method performed by a UE according to one aspect may include: receiving configuration information including information on a first time resource associated with a Sub-band Full Duplex (SBFD); receiving a first RACH (Random Access Channel) configuration for an RO (Random Access Channel Occasion); receiving a second RACH configuration for an additional RO associated with the SBFD; and transmitting a PRACH (Physical Random Access Channel) based on at least one of the RO and the additional RO.

[0007] Alternatively, the second RACH configuration is characterized by setting the additional RO for the first time interval for a UE capable of recognizing the first time resource associated with the SBFD, and the second RACH configuration is characterized by setting the additional RO within an UL (Uplink) subband set within the first time resource.

[0008] Alternatively, the UE is characterized in that the additional RO set by the second RACH configuration is considered to be valid even if the additional RO is set in a time interval outside the first time interval.

[0009] Alternatively, the UE is characterized in that it determines the validity of the additional RO based on the first time resource.

[0010] Alternatively, the additional RO is characterized in that it is determined to be invalid based on not being set within the first time resource.

[0011] Alternatively, the additional RO is determined based on a first reference frequency and a first frequency offset, and the RO is determined based on a second reference frequency and a second frequency offset, wherein the first reference frequency is set differently from the second reference frequency based on an UL (Uplink) subband associated with the SBFD.

[0012] Alternatively, the first reference frequency is determined based on a PRB (Physical Resource Block) with the lowest index in a UL subband associated with the SBFD, and the second reference frequency is determined based on a PRB with the lowest index in an active uplink bandwidth part (BWP) for the UE.

[0013] Alternatively, the UE is characterized in that it determines the additional RO by using the second frequency offset included in the first RACH configuration as the first frequency offset.

[0014] Alternatively, based on the fact that the additional RO and the RO are set to overlap in a specific time resource within the first time resource, the UE determines that only the RO among the additional RO and the RO is valid.

[0015] Alternatively, the UE is characterized in that it performs SSB mapping for the additional RO with the same rules as the SSB mapping rules for the RO.

[0016] According to another aspect, a non-transitory computer-readable storage medium having recorded thereon instructions for performing the method by the UE described above may be provided.

[0017] According to another aspect, a UE performing the above-described method may be provided.

[0018] According to another aspect, a processing device may be provided for controlling a UE performing the above-described method.

[0019] A method by a base station according to another aspect may include: transmitting configuration information including information on a first time resource related to a Sub-band Full Duplex (SBFD); transmitting a first RACH configuration for a Random Access Channel Occasion (RO) and a second RACH configuration for an additional RO related to the SBFD; and receiving a Physical Random Access Channel (PRACH) based on at least one of the RO and the additional RO.

[0020] According to another aspect, a base station performing the above-described method may be provided.

[0021] Various embodiments enable a UE to communicate more accurately and efficiently with a base station performing SBFD operations.

[0022] The effects that can be obtained in various embodiments are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the description below.

[0023] The drawings attached to this specification are intended to provide an understanding of the present invention, illustrate various embodiments of the present invention, and together with the description of the specification serve to explain the principles of the present invention.

[0024] Figure 1 shows the structure of an LTE system.

[0025] Figure 2 shows the structure of the NR system.

[0026] Figure 3 shows the structure of a radio frame of NR.

[0027] Figure 4 shows the slot structure of an NR frame.

[0028] FIG. 5 is a diagram for explaining physical channels that can be used in various embodiments and a signal transmission method using the same.

[0029] FIG. 6 is a diagram showing the structure of an SSB (Synchronization Signal Block) to which various examples of the present disclosure can be applied.

[0030] FIG. 7 is a diagram showing an example of a transmission method of SSB to which various examples of the present disclosure are applicable.

[0031] FIG. 8 illustrates multi-beam transmission of SSB applicable to various examples of the present disclosure.

[0032] FIG. 9 illustrates a method for indicating an actually transmitted SSB (SSB_tx) applicable to various examples of the present disclosure.

[0033] FIG. 10 is a diagram illustrating a method for setting up an RO group in relation to PRACH repetition.

[0034] Figure 11 is a diagram for explaining PRACH repetition based on start frequency between RO groups.

[0035] FIG. 12 and FIG. 13 are drawings for explaining a method of performing full duplex operation in an NR system.

[0036] Figures 14 and 15 are diagrams for explaining a method of setting resources for SBFD operation.

[0037] FIGS. 16 to 19 are diagrams for explaining a method of setting up a legacy RO and a Separated RO for an SBFD slot and a non-SBFD slot.

[0038] FIG. 20 is a diagram illustrating a method for setting parameters for determining RO between SBFD slots and non-SBFD slots.

[0039] Figure 21 is a diagram for explaining an SSB-to-RO mapping method for separated RO.

[0040] Figure 22 is a diagram illustrating how a UE sets up ROs for initial connection.

[0041] Figure 23 is a diagram illustrating a method for a base station to set up ROs for initial connection to a UE.

[0042] Figure 24 illustrates a communication system applied to the present invention.

[0043] Figure 25 illustrates a wireless device applicable to the present invention.

[0044] Fig. 26 shows another example of a wireless device applied to the present invention.

[0045] A wireless communication system is a multiple access system that supports communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and multi-carrier frequency division multiple access (MC-FDMA).

[0046] Sidelink refers to a communication method that establishes a direct link between user equipment (UE), allowing voice or data to be exchanged directly between terminals without going through a base station (BS). Sidelink is being considered as a solution to address the burden on base stations due to rapidly increasing data traffic.

[0047] V2X (vehicle-to-everything) refers to a communication technology that exchanges information with other vehicles, pedestrians, and infrastructure-based objects through wired / wireless communication. V2X can be divided into four types: V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), and V2P (vehicle-to-pedestrian). V2X communication can be provided through the PC5 interface and / or Uu interface.

[0048] Meanwhile, as more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Accordingly, communication systems that consider services or terminals sensitive to reliability and latency are being discussed. Next-generation wireless access technologies that consider improved mobile broadband communication, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) can be called new radio access technology (RAT) or new radio (NR). NR can also support V2X (vehicle-to-everything) communication.

[0049] The following technologies can be used in various wireless communication systems, such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved UTRA). IEEE 802.16m is an evolution of IEEE 802.16e, providing backward compatibility with systems based on IEEE 802.16e. UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long term evolution) is a part of E-UMTS (evolved UMTS) that uses E-UTRA (evolved-UMTS terrestrial radio access), employing OFDMA in the downlink and SC-FDMA in the uplink.LTE-A (advanced) is an evolution of 3GPP LTE.

[0050] 5G NR, the successor to LTE-A, is a new clean-slate mobile communications system featuring high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, from low-frequency bands below 1 GHz, mid-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz.

[0051] For clarity, the description will focus on LTE-A or 5G NR, but the technical ideas of the embodiment(s) are not limited thereto.

[0052] Figure 1 illustrates the architecture of an applicable LTE system. This may be referred to as an Evolved-UMTS Terrestrial Radio Access Network (E-UTRAN) or a Long Term Evolution (LTE) / LTE-A system.

[0053] Referring to FIG. 1, the E-UTRAN includes a base station (20; BS) that provides a control plane and a user plane to a terminal (10). The terminal (10) may be fixed or mobile, and may be referred to by other terms such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT), a wireless device, etc. The base station (20) refers to a fixed station that communicates with the terminal (10), and may be referred to by other terms such as an evolved-NodeB (eNB), a base transceiver system (BTS), an access point, etc.

[0054] Base stations (20) can be connected to each other via the X2 interface. The base station (20) is connected to an EPC (Evolved Packet Core, 30) via the S1 interface, more specifically, to an MME (Mobility Management Entity) via the S1-MME, and to an S-GW (Serving Gateway) via the S1-U.

[0055] The EPC (30) consists of an MME, an S-GW, and a P-GW (Packet Data Network-Gateway). The MME holds information about terminal access and capabilities, and this information is primarily used for terminal mobility management. The S-GW is a gateway with the E-UTRAN as its endpoint, and the P-GW is a gateway with the PDN as its endpoint.

[0056] The layers of the radio interface protocol between the terminal and the network can be divided into L1 (Layer 1), L2 (Layer 2), and L3 (Layer 3) based on the three lower layers of the Open System Interconnection (OSI) standard model, which is widely known in communication systems. Among these, the physical layer belonging to Layer 1 provides an information transfer service using a physical channel, and the RRC (Radio Resource Control) layer located in Layer 3 controls radio resources between the terminal and the network. To this end, the RRC layer exchanges RRC messages between the terminal and the base station.

[0057] Figure 2 shows the structure of the NR system.

[0058] Referring to FIG. 2, the NG-RAN may include a gNB and / or an eNB that provides user plane and control plane protocol termination to the UE. FIG. 7 illustrates a case where only a gNB is included. The gNB and eNB are connected to each other via an Xn interface. The gNB and eNB are connected to the 5th generation core network (5G Core Network: 5GC) via the NG interface. More specifically, they are connected to the access and mobility management function (AMF) via the NG-C interface, and to the user plane function (UPF) via the NG-U interface.

[0059] Figure 3 shows the structure of a radio frame of NR.

[0060] Referring to FIG. 3, radio frames can be used for uplink and downlink transmission in NR. A radio frame has a length of 10 ms and can be defined as two 5 ms half-frames (Half-Frames, HF). A half-frame can include five 1 ms sub-frames (Subframes, SF). A sub-frame can be divided into one or more slots, and the number of slots within a sub-frame can be determined by the Subcarrier Spacing (SCS). Each slot can include 12 or 14 OFDM (A) symbols depending on the cyclic prefix (CP).

[0061] When normal CP is used, each slot can contain 14 symbols. When extended CP is used, each slot can contain 12 symbols. Here, the symbols can include OFDM symbols (or CP-OFDM symbols), SC-FDMA (Single Carrier - FDMA) symbols (or DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) symbols).

[0062] Table 1 below shows the number of symbols per slot ((N)) depending on the SCS setting (u) when normal CP is used. slot symb ), number of slots per frame ((N frame,u slot ) and the number of slots per subframe ((N subframe,u slot ) is an example.

[0063] SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot 15KHz (u=0)1410130KHz (u=1)1420260KHz (u=2)14404120KHz (u=3)14808240KHz (u=4)1416016

[0064] Table 2 illustrates the number of symbols per slot, the number of slots per frame, and the number of slots per subframe according to SCS when extended CP is used.

[0065] SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot 60KHz (u=2)12404

[0066] In an NR system, OFDM(A) numerologies (e.g., SCS, CP length, etc.) can be configured differently across multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., subframe, slot, or TTI) (conveniently referred to as a TU (Time Unit)) consisting of the same number of symbols can be configured differently across the merged cells. In NR, multiple numerologies or SCSs can be supported to support various 5G services. For example, when the SCS is 15 kHz, a wide area in traditional cellular bands can be supported, and when the SCS is 30 kHz / 60 kHz, dense-urban, lower latency, and wider carrier bandwidth can be supported. When the SCS is 60 kHz or higher, bandwidths greater than 24.25 GHz may be supported to overcome phase noise.

[0067] The NR frequency band can be defined by two types of frequency ranges. The two types of frequency ranges can be FR1 and FR2. The numerical values ​​of the frequency ranges can be changed, and for example, the two types of frequency ranges can be as shown in Table 3 below. Among the frequency ranges used in the NR system, FR1 can mean the "sub 6 GHz range", and FR2 can mean the "above 6 GHz range" and can be called millimeter wave (mmW).

[0068] Frequency Range designationCorresponding frequency rangeSubcarrier Spacing (SCS)FR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0069] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a band from 410 MHz to 7125 MHz, as shown in Table 4 below. That is, FR1 may include a frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, such as for vehicular communications (e.g., autonomous driving).

[0070] Frequency Range designationCorresponding frequency rangeSubcarrier Spacing (SCS)FR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0071] Figure 4 shows the slot structure of an NR frame.

[0072] Referring to Figure 4, a slot includes multiple symbols in the time domain. For example, in the case of a normal CP, one slot may include 14 symbols, but in the case of an extended CP, one slot may include 12 symbols. Alternatively, in the case of a normal CP, one slot may include 7 symbols, but in the case of an extended CP, one slot may include 6 symbols.

[0073] A carrier includes multiple subcarriers in the frequency domain. An RB (Resource Block) can be defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth Part) can be defined as multiple consecutive (P)RBs ((Physical) Resource Blocks) in the frequency domain, and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed through activated BWPs. Each element can be referred to as a Resource Element (RE) in the resource grid, and one complex symbol can be mapped to it.

[0074] Meanwhile, the wireless interface between terminals or between terminals and a network may be composed of an L1 layer, an L2 layer, and an L3 layer. In various embodiments of the present disclosure, the L1 layer may refer to a physical layer. Furthermore, for example, the L2 layer may refer to at least one of a MAC layer, an RLC layer, a PDCP layer, and an SDAP layer. Furthermore, for example, the L3 layer may refer to an RRC layer.

[0075] Bandwidth part (BWP)

[0076] The NR system can support up to 400 MHz per component carrier (CC). If a terminal operating in such a wideband CC always operates with the RF on for the entire CC, the terminal battery consumption may increase. Alternatively, when considering multiple use cases (e.g., eMBB, URLLC, MMTC, V2X, etc.) operating within a wideband CC, different numerologies (e.g., sub-carrier spacing) may be supported for each frequency band within the CC. Alternatively, each terminal may have different capabilities for maximum bandwidth. Considering this, the base station can instruct the terminal to operate only in a portion of the bandwidth rather than the entire bandwidth of the wideband CC, and this portion of bandwidth is conveniently defined as a bandwidth part (BWP). A BWP can be composed of consecutive resource blocks (RBs) on the frequency axis and can correspond to a single numerology (e.g., sub-carrier spacing, CP length, slot / mini-slot duration).

[0077] Meanwhile, the base station can set multiple BWPs even within a single CC configured for the UE. For example, in the PDCCH monitoring slot, a BWP occupying a relatively small frequency range can be set, and the PDSCH indicated by the PDCCH can be scheduled on a larger BWP. Alternatively, if UEs are concentrated in a specific BWP, some UEs can be set to a different BWP for load balancing. Alternatively, considering frequency domain inter-cell interference cancellation between neighboring cells, a portion of the spectrum in the middle of the total bandwidth can be excluded, and both BWPs can be set within the same slot. That is, the base station can configure at least one DL / UL BWP for a terminal associated with a wideband CC, and can activate at least one DL / UL BWP among the configured DL / UL BWP(s) at a specific point in time (by L1 signaling or MAC CE or RRC signaling, etc.), and switching to another configured DL / UL BWP can be indicated (by L1 signaling or MAC CE or RRC signaling, etc.), or switching to a predetermined DL / UL BWP when the timer value expires based on a timer. At this time, the activated DL / UL BWP is defined as the active DL / UL BWP. However, the terminal may not receive the configuration for the DL / UL BWP in situations such as when the terminal is in the initial access process or before the RRC connection is set up. In such situations, the DL / UL BWP assumed by the terminal is defined as the initial active DL / UL BWP.

[0078] FIG. 5 is a diagram for explaining physical channels that can be used in various embodiments and a signal transmission method using the same.

[0079] Referring to FIG. 5, a terminal that is powered on again after being powered off or that has newly entered a cell performs an initial cell search operation, such as synchronizing with the base station, in step S101. To this end, the terminal receives a Synchronization Signal Block (SSB) from the base station. The SSB includes a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). Based on the PSS / SSS, the terminal synchronizes with the base station and obtains information such as a cell ID (cell identity). In addition, the terminal can obtain broadcast information within the cell based on the PBCH. Meanwhile, the terminal can check the downlink channel status by receiving a Downlink Reference Signal (DL RS) during the initial cell search phase.

[0080] A terminal that has completed initial cell search can obtain more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) based on physical downlink control channel information (S12).

[0081] Thereafter, the terminal may perform a random access procedure to complete connection to the base station (S13 to S16). To this end, the terminal may transmit a preamble through a physical random access channel (PRACH) (S13) and receive a random access response (RAR) for the preamble through a physical downlink control channel and a corresponding physical downlink shared channel (S14). The terminal may transmit a physical uplink shared channel (PUSCH) using scheduling information in the RAR (S15) and perform a contention resolution procedure such as receiving a physical downlink control channel signal and a corresponding physical downlink shared channel signal (S16).

[0082] Meanwhile, in addition to the random access process performed in 4 steps as above (4-step RACH, type-1 random access procedure), when the random access process is performed in 2 steps (2-step RACH, type-2 random access procedure), S13 / S15 may be performed as one operation in which the terminal performs transmission (e.g., transmission operation of message A including PRACH preamble and / or PUSCH), and S14 / S16 may be performed as one operation in which the base station performs transmission (e.g., transmission operation of message B including RAR and / or collision resolution information).

[0083] A terminal that has performed the procedure described above can then perform general uplink / downlink signal transmission procedures, such as receiving a physical downlink control channel signal and / or a physical downlink shared channel signal (S17) and transmitting a physical uplink shared channel (PUSCH: Physical Uplink Shared Channel) signal and / or a physical uplink control channel (PUCCH: Physical Uplink Control Channel) signal (S18).

[0084] Control information transmitted from a terminal to a base station is collectively referred to as uplink control information (UCI). UCI includes information such as HARQ-ACK / NACK (Hybrid Automatic Repeat and reQuest Acknowledgement / Negative-ACK), SR (Scheduling Request), CQI (Channel Quality Indication), PMI (Precoding Matrix Indication), and RI (Rank Indication).

[0085] UCI is typically transmitted periodically over the PUCCH, but can also be transmitted over the PUSCH when control information and data must be transmitted simultaneously. Furthermore, terminals can transmit UCI aperiodically over the PUSCH at the request / instruction of the network.

[0086] FIG. 6 is a diagram showing the structure of an SSB (Synchronization Signal Block) to which various examples of the present disclosure can be applied.

[0087] The UE can perform cell search, system information acquisition, beam alignment for initial access, and DL measurements based on SSB. SSB is used interchangeably with the SS / PBCH (Synchronization Signal / Physical Broadcast channel) block.

[0088] Referring to Figure 6, SSB is composed of PSS, SSS, and PBCH. SSB is composed of four consecutive OFDM symbols, and PSS, PBCH, SSS / PBCH, and PBCH are transmitted for each OFDM symbol. PSS and SSS are each composed of one OFDM symbol and 127 subcarriers, and PBCH is composed of three OFDM symbols and 576 subcarriers. Polar coding and QPSK (Quadrature Phase Shift Keying) are applied to PBCH. PBCH is composed of data RE and DMRS (Demodulation Reference Signal) RE for each OFDM symbol. There are three DMRS REs for each RB, and three data REs exist between DMRS REs.

[0089] Cell search refers to the process by which a UE acquires time / frequency synchronization of a cell and detects the cell ID (e.g., Physical layer Cell ID, PCID) of the cell. The PSS is used to detect a cell ID within a cell ID group, and the SSS is used to detect a cell ID group. The PBCH is used for SSB (time) index detection and half-frame detection.

[0090] The cell search process of the UE can be summarized as shown in Table 5 below.

[0091]

[0092] There are 336 cell ID groups, and 3 cell IDs exist for each cell ID group. There are a total of 1008 cell IDs. Information about the cell ID group to which the cell ID of a cell belongs is provided / obtained through the SSS of the cell, and information about the cell ID among the 336 cells within the cell ID is provided / obtained through the PSS.

[0093] FIG. 7 is a diagram showing an example of a transmission method of SSB to which various examples of the present disclosure are applicable.

[0094] Referring to Fig. 7, SSB is transmitted periodically according to the SSB periodicity. The basic SSB periodicity assumed by the UE during initial cell search is defined as 20 ms. After cell access, the SSB periodicity can be set by the network (e.g., base station) to one of {5 ms, 10 ms, 20 ms, 40 ms, 80 ms, 160 ms}. An SSB burst set is configured at the beginning of the SSB period. An SSB burst set consists of a 5 ms time window (i.e., half-frame), and an SSB can be transmitted at most L times within the SSB burst set. The maximum number of SSB transmissions L can be given as follows depending on the frequency band of the carrier. One slot includes at most two SSBs.

[0095] - For frequency range up to 3 GHz, L = 4

[0096] - For frequency range from 3GHz to 6 GHz, L = 8

[0097] - For frequency range from 6 GHz to 52.6 GHz, L = 64

[0098] The temporal position of an SSB candidate within an SS burst set can be defined as follows according to the SCS. The temporal position of an SSB candidate is indexed from 0 to L-1 in temporal order within the SSB burst set (i.e., half-frame) (SSB index).

[0099] - Case A: 15 kHz SCS: The index of the starting symbol of the candidate SSB is given as {2, 8} + 14*n. When the carrier frequency is 3 GHz or less, n=0, 1. When the carrier frequency is 3 GHz to 6 GHz, n=0, 1, 2, 3.

[0100] - Case B: 30 kHz SCS: The index of the starting symbol of the candidate SSB is given as {4, 8, 16, 20} + 28*n. If the carrier frequency is 3 GHz or less, n=0. If the carrier frequency is 3 GHz to 6 GHz, n=0, 1.

[0101] - Case C: 30 kHz SCS: The index of the starting symbol of the candidate SSB is given as {2, 8} + 14*n. When the carrier frequency is 3 GHz or less, n=0, 1. When the carrier frequency is 3 GHz to 6 GHz, n=0, 1, 2, 3.

[0102] - Case D: 120 kHz SCS: The index of the starting symbol of the candidate SSB is given as {4, 8, 16, 20} + 28*n. When the carrier frequency is greater than 6 GHz, n=0, 1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, 18.

[0103] - Case E: 240 kHz SCS: The indices of the starting symbols of candidate SSBs are given as {8, 12, 16, 20, 32, 36, 40, 44} + 56*n. When the carrier frequency is greater than 6 GHz, n=0, 1, 2, 3, 5, 6, 7, 8.

[0104] FIG. 8 illustrates multi-beam transmission of SSB applicable to various examples of the present disclosure.

[0105] Beam sweeping means that a Transmission Reception Point (TRP) (e.g., a base station / cell) varies the beam (direction) of a wireless signal over time (hereinafter, beam and beam direction can be used interchangeably). SSBs can be transmitted periodically using beam sweeping. In this case, the SSB index is implicitly linked to the SSB beam. The SSB beam can be changed on an SSB (index) basis or on an SSB (index) group basis. In the latter case, the SSB beam remains the same within the SSB (index) group. That is, the SSB transmission beam echo is repeated in multiple consecutive SSBs. The maximum number of SSB transmissions L within an SSB burst set has a value of 4, 8, or 64 depending on the frequency band to which the carrier belongs. Therefore, the maximum number of SSB beams within an SSB burst set can also be given as follows depending on the frequency band of the carrier.

[0106] - For frequency range up to 3 GHz, Max number of beams = 4

[0107] - For frequency range from 3GHz to 6 GHz, Max number of beams = 8

[0108] - For frequency range from 6 GHz to 52.6 GHz, Max number of beams = 64

[0109] * If multi-beam transmission is not applied, the number of SSB beams is 1.

[0110] When a UE attempts initial access to a base station, the UE can align beams with the base station based on SSB. For example, the UE performs SSB detection and then identifies the best SSB. The UE can then transmit a RACH preamble to the base station using the PRACH resource linked to / corresponding to the index (i.e., beam) of the best SSB. SSB can also be used to align beams between the base station and the UE after initial access.

[0111] FIG. 9 illustrates a method for indicating an actually transmitted SSB (SSB_tx) applicable to various examples of the present disclosure.

[0112] Within an SSB burst set, up to L SSBs can be transmitted, and the actual number and locations of SSBs transmitted may vary by base station / cell. The actual number and locations of SSBs transmitted are used for rate matching and measurement, and information about the actually transmitted SSBs is indicated as follows.

[0113] - In case of rate-matching: It can be indicated via UE-specific RRC signaling or RMSI. UE-specific RRC signaling includes full (e.g., length L) bitmaps in both FR1 and FR2 frequency ranges. On the other hand, RMSI includes full bitmaps in FR1 and bitmaps in compressed form in FR2 as illustrated. Specifically, information about actually transmitted SSB can be indicated using a group bitmap (8 bits) + intra-group bitmap (8 bits). Here, resources (e.g., REs) indicated via UE-specific RRC signaling or RMSI are reserved for SSB transmission, and PDSCH / PUSCH, etc. can be rate-matched considering SSB resources.

[0114] - For measurement purposes: When in RRC connected mode, the network (e.g., base station) can indicate the SSB set to be measured within the measurement interval. The SSB set can be indicated per frequency layer. If there is no indication regarding the SSB set, the default SSB set is used. The default SSB set includes all SSBs within the measurement interval. The SSB set can be indicated using a full (e.g., length L) bitmap in RRC signaling. When in RRC idle mode, the default SSB set is used.

[0115] Meanwhile, the specific PRACH-related procedures and details of PRACH configuration may be performed identically or similarly to those defined in 3GPP TS 38.213 Section 8.1 and 3GPP TS 38.211. For example, PRACH configuration may be configured based on the tables in "Table 6.3.3.2-3" and "Table 6.3.3.2-4" of 3GPP TS 38.211.

[0116] PRACH repetition

[0117] FIG. 10 is a diagram illustrating a method for setting up an RO group in relation to PRACH repetition.

[0118] In Rel-18 coverage enhancement, RO groups for PRACH repetition were introduced. For example, as illustrated in Fig. 10 (a) and (b), if the base station sets / indicates the number of repetitions to N (e.g., 2, 4, 8), it is agreed that among valid ROs existing at the same frequency, N ROs are grouped in ascending order of time domain index to form an RO group. At this time, the remaining N-1 ROs are located at the same frequency as the first RO. For example, among valid ROs associated with the same beam, N ROs existing at the same frequency can belong to one RO group.

[0119] If there are preamble repetitions in a PRACH transmission, the time period starts from frame 0 and provides at least one valid PRACH opportunity set for each configured number of preamble repetitions. It can be the smallest integer multiple of the association pattern period that can be determined for the SS / PBCH block index. A valid PRACH opportunity set for each configured preamble repetition count is repeated every this time period, and the time period can be the smallest integer multiple of the association pattern period that can have at least one valid PRACH opportunity set for each SSB index. Here, the association pattern period can be composed of one or more association periods, and the pattern can be repeated at most every 160 ms.

[0120] The association period may be defined as the minimum integer value in a set of values ​​determined according to the PRACH configuration period specified in the RACH procedure of 3GPP TS 38.211 (e.g., Table 8.1-2), starting from frame 0. At least once within this association period. The SS / PBCH block index can be mapped to a PRACH opportunity, where the UE can determine this via the ssb-PositionsInBurst value in SIB1 or ServingCellConfigCommon. SS / PBCH values ​​can be obtained. The association pattern period consists of one or more association periods, and the pattern between the PRACH opportunity and the SS / PBCH block index can be determined to repeat at most every 160 ms.

[0121] ROs at different frequencies (referred from R1-2308310)

[0122] Figure 11 is a diagram for explaining PRACH repetition based on start frequency between RO groups.

[0123] The association pattern of SSB-R based on the existing mapping rule can be as illustrated in Fig. 11 (a). For a group of ROs repeated twice when the starting RBs are different between ROs, it is illustrated in Fig. 11 (b), and for a group of ROs repeated twice when the starting RBs are the same between ROs, it is illustrated in Fig. 11 (c).

[0124] In this regard, under the assumption of N repeated PRACH transmissions, 3GPP RAN1#114 (August 23) proposed and agreed on the starting RB of the first RO and the RB positions of the remaining N-1 ROs, which are organized into RO groups, as follows. The conclusion was that only ROs with the same frequency position of the starting RB would be used for repetition, but there was no specific discussion on ROs with different frequency positions of the starting RB.

[0125] The contents related to the above discussion are as shown in Table 6.

[0126] Issue #2-3: Whether / how the starting RB of ROs can be different at different time instances for multiple PRACH transmissionsBased on companies' contribution, this issue includes two cases: the first one is, whether explicitly hopping offset configuration is supported during multiple PRACH transmission, similar to traditional frequency hopping; the second one is, whether the ROs within the RO group can have different starting RB w / o a configured hopping offset. Companies' views are summarized as follows:쪦The starting RB of ROs within a RO group can be different at different time instances.Support (11): Spreadtrum (w / o addition configuration), Huawei, HiSilicon (ROs in non-adjacent slots), Nokia, NSB, Intel, LG, Quectel, OPPO, Qualcomm, EricssonNot Support / low priority (7): CMCC, Fujitsu, Xiaomi, Lenovo, China Telecom, ETRI, NTT DOCOMODetailed companies' views are summarized as follows:[NTT DOCOMO] If frequency hopping within one RO group is supported, a frequency index offset among different ROs within one RO group can be defined / indicated.[Ericsson] In the case that for a selected SSB / CSI-RS the same set of frequency domain ROs occur at different time instances, the configuration of PRACH frequency hopping can be similar to PUSCH frequency hopping, for instance with a frequency hopping offset.In a case, where for a selected SSB / CSI-RS there are the same number of frequency domain RO(s) at different time instances, which locate in different frequency resources over time, a UE can transmit in the same RO relative to the one with the lowest frequency resource among those associated with the same SSB, and the gNB configured frequency hopping offset is not necessary.[Spreadtrum] The starting RB of ROs in one RO group can be different at different time instances for multiple PRACH transmissions. RO group without frequency hopping should be discussed first, and then multiple PRACH transmission with frequency hopping can be studied if time permits.[Nokia] Support different starting RBs across the multiple PRACH transmissions. Frequency hopping across the multiple PRACH transmissions is implicitly activated and configured by gNB via configuration of the RO groups.[vivo] If frequency hopping is supported, the RO group for frequency hopping is determined by hopping step in time domain and hopping offset in frequency domain considering new frequency indexes additionally defined among the selected FDMed ROs mapped to the same SSB. [Intel] For multiple PRACH transmission with same Tx beam, RO offset can be configured or implicitly determined for frequency hopping.

[0127] Background of FDR

[0128] FIG. 12 and FIG. 13 are drawings for explaining a method of performing full duplex operation in an NR system.

[0129] 5G is giving rise to new service types, such as XR (Extended Reality), AI-based services, and self-driving cars. These services feature dynamic traffic in both DL and UL directions, and require low latency for packet transmission. To support these diverse new use cases, 5G services could experience explosive growth in traffic load. Meanwhile, existing semi-static or dynamic TDD UL / DL configurations may face limitations in transmission delays and interference between operators. Existing FDD schemes may also face limitations in efficient frequency resource utilization in the DL / UL directions. Therefore, the introduction of full-duplex operation within a single carrier is being discussed to achieve low latency and efficient resource utilization in NR.

[0130] Referring to Fig. 12, a method of applying full-duplex operation in an intra-carrier is illustrated. Specifically, the full-duplex operation may be considered as the subband-wise full duplex (SB-FD) method illustrated in Fig. 12 (a) and the spectrum-sharing full duplex (SS-FD) method illustrated in Fig. 12 (b).

[0131] In the case of SB-FD, transmission and reception of DL and UL can be performed using different frequency resources on the same carrier. That is, DL and UL can have different frequency resources for the same time resource. In the case of SS-FD, transmission and reception of DL and UL are performed using the same frequency resources or overlapping frequency resources on the same carrier. That is, DL and UL can be assigned the same or overlapping frequency resources for the same time resource.

[0132] This full-duplex operation can be combined with existing half-duplex operation. For example, in existing half-duplex-based TDD operation, only some time resources can be used for full-duplex operation. In the time resources where full-duplex operation is performed, SB-FD or SS-FD operation can be performed.

[0133] Specifically, referring to FIG. 12, time resources may exist together as time resources operating in HD (half duplex) and as time resources operating in FD (full duplex) such as SB-FD or SS-FD. As illustrated in FIG. 13 (a), the time resources may include some time resources for SB-FD operation and the remaining time resources for HD operation. Alternatively, as illustrated in FIG. 13 (b), the time resources may include time resources for SS-FD operation and the remaining time resources for HD operation. In this case, the unit of the time resources (for SS-FD operation, SB-FD operation, or HD operation) may be a slot or a symbol unit. Meanwhile, in the time resources operating in SB-FD, some frequency resources may be used as DL resources, and some frequency resources may be used as UL resources.

[0134] In the following, frequency resources operating as DL among the entire frequency resources in a time resource operating as FD (e.g., SB-FD operation or SS-FD operation) are defined as DL sub-bands, and frequency resources operating as UL are defined as UL sub-bands.

[0135] In the case of the full-duplex (hereinafter, FD) operation as described above, the FD operation can be performed from both the gNB perspective and the UE perspective. For example, both the gNB and the UE can simultaneously transmit and receive DL / UL using the same or different frequency resources in the same time resource. Alternatively, only the gNB can perform the FD operation (in the same time resource), and the UE can perform the HD operation. The gNB can simultaneously transmit and receive DL and UL using the same or different frequency resources in the same time resource, but the UE can perform only DL reception or UL transmission in a specific time resource. In this case, the gNB can perform the FD operation in a way that performs DL transmission and UL reception for different UEs at the same time point (or, the same time resource).

[0136] Hereinafter, in the description of the proposed invention, even if it is expressed only as a slot or symbol, it can be applied to both slots and symbols as a single time resource unit. In addition, for the convenience of explanation, SBFD slots / symbols or non-SBFD slots / symbols can be described by specifying them only as SBFD or non-SBFD. Until the last Rel-18, 3GPP discussed that DL slots and flexible slots of legacy systems can be used as SBFD slots. Looking at the legacy operation, the current TDD slot / symbol configuration can be done through the following two operations. The first operation is that all UEs located in a cell can be assigned a cell-specific DL / UL pattern through tdd-UL-DL-ConfigurationCommon. The second action can be UE-specific configuration of a slot / symbol (or resource) indicated as a flexible slot / symbol via a dedicated RRC signal tdd-UL-DL-ConfigurationDedicated. tdd-UL-DL-ConfigurationCommon can be carried via SIB1 or dedicated RRC signaling. To be configured as a flexible slot / symbol, it must be configured / indicated as flexible both via the UE and cell-specific slot configurations. Since tdd-UL-DL-ConfigurationDedicated is optional, there is no obligation for the cell / base station / network to perform the second action described above. In this case, the cell / base station / network can use the DL / UP pattern configured in tdd-UL-DL-ConfigurationCommon.At this time, if the UE does not set SlotFormatIndicator, the UE can receive PDSCH or CSI-RS in some / all symbols of the slot (e.g., some / all symbols of a flexible slot) according to the instructions of DCI format 1_0, DCI format 1_1, and DCI format 0_1. If the UE does not set SlotFormatIndicator, the UE can transmit PUSCH, PUCCH, PRACH, and SRS in some / all symbols of the slot (e.g., some / all symbols of a flexible slot) according to the instructions of DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, and DCI format 2_3.

[0137] Figures 14 and 15 are diagrams for explaining a method of setting resources for SBFD operation.

[0138] Referring to FIG. 14, SBFD operation can be applied to DL slots and / or flexible slots via upper layer signals. In this case, some frequency resources of the SBFD slots can be set to DL (or SBFD DL subbands), and other some frequency resources can be set to UL (or SBFD UL subbands). Meanwhile, the direction (e.g., DL or UL) of each SBFD subband can also be indicated via dynamic indication (e.g., DCI format 2_0, SFI).

[0139] Meanwhile, in the SBFD system, even ROs that were unusable or invalid in the legacy system may be used validly. Therefore, it is necessary to redefine the RO setting-related operations of the SBFD system so that it can operate together with the legacy system. In the following, to define the new operations related to such RO setting, a method for setting the RO setting independent from the RO setting of the legacy system (hereinafter, separated RO setting) is described in detail, focusing on the SBFD system. In addition, the RO setting corresponds to the RACH setting for determining / setting the RO, and for the convenience of explanation, it is defined as the RO setting in the following description.

[0140] First, the existing operation and limitations of the RO of the legacy system (hereinafter, legacy RO) are described. Legacy RO can operate differently in DL / flexible / UL slots. First, although not described in the 3GPP standard document, both the base station and the terminal can implicitly expect that the legacy RO will not be configured in the downlink. In the case of slots in other link directions (e.g., UL), the legacy RO can be configured, but the base station and the terminal can implicitly determine whether the use of the legacy RO is valid based on the same criteria based on other high-priority signaling. For example, a PRACH opportunity of a resource configured as a PRACH slot can be determined as a valid RO if it is not located before the SS / PBCH block resource or is located after the last repeated symbol of the SS / PBCH block by at least N_gap symbols. Alternatively, if tdd-UL-DL-ConfigurationCommon is set, a PRACH opportunity for a resource set to a UL symbol or a PRACH slot may be considered a valid RO if it is not located before an SS / PBCH block resource or is located after the last SS / PBCH block repetition symbol by at least N_gap symbols. An RO that cannot be used due to such restrictions may be considered an invalid RO.

[0141] Referring to Fig. 15 (a), the SBFD setting can be applied to a DL slot (and / or a flexible slot). In this case, the validity of the RO related to the SBFD setting can be determined through the following methods.

[0142] Method 1 can enable RO to be configured in a SBFD symbol configured for TDD as downlink when the gNB determines the RO configuration index (or PRACH configuration index). The RO can be positioned in an SBFD symbol and / or a non-SBFD symbol based on parameters related to the signaled RO configuration index (or PRACH configuration index). At this time, a RO in which legacy UEs and SBFD aware UEs can transmit PRACH can be assumed / defined as a legacy RO, and a RO in which only SBFD aware UEs can transmit PRACH can be assumed / defined as a SBFD RO or Separated RO (hereinafter, separated RO). Based on this, a legacy UE can determine a legacy RO located in a non-SBFD symbol as a valid RO (or determine a legacy RO located in an SBFD symbol as an invalid RO), and a SBFD aware UE can determine a legacy RO and an SBFD RO located in a non-SBFD symbol and an SBFD symbol as valid ROs.

[0143] Alternatively, as method 2, since the legacy UE recognizes the time resource to which the SBFD slot / symbol is set as a DL time resource, it may not expect RO configuration in the time resource to which the SBFD slot / symbol is set according to the existing rule. In contrast, the SBFD-aware UE can recognize the time resource to which the SBFD slot / symbol is set, and thus may expect RO configuration (e.g., separated RO configuration) in the SBFD UL subband according to the new rule. Here, the new rule may mean that the SBFD symbol is viewed as a flexible symbol, which means that both UL / DL directions are possible in one symbol. In this case, the configured RO (or RO group) may only be used by SBFD aware UEs. For example, the RO or RO group configured for the time resource to which the SBFD slot / symbol is set may only be used by SBFD-aware UEs.

[0144] Specifically, referring to FIGS. 15 (b) and (c), SBFD configuration can be applied to a flexible slot. In this case, since the legacy UE recognizes the slot or resource as flexible, it can be expected that the RO configuration is valid (FIG. 15 (b)) or invalid (FIG. 15 (c)) based on the existing rules. On the other hand, since the SBFD-aware UE recognizes the flexible slot as a slot for SBFD, it can expect RO configuration (e.g., separated RO configuration) in the SBFD UL subband according to the new rules. In this way, in the case of a flexible slot, since both legacy UEs and SBFD aware UEs may use it, when configuring RO (or RO group, hereinafter RO includes the concept of RO group), it is necessary to determine the location of the time / frequency resources of the RO by considering SBFD and non-SBFD.

[0145] Meanwhile, one of the reasons why multiple ROs are set is to perform an SSB-to-RO mapping operation. The base station can transmit multiple SSBs corresponding to each beam to find the most suitable beam for the terminal. The terminal can find the most suitable SSB for itself (e.g., the SSB with the best signal quality) through each SSB. The terminal can transmit a PRACH / PRACH preamble in the RO corresponding to the SSB found by the terminal through SSB-to-RO mapping. The base station can find out through which RO among the multiple ROs the terminal sent the PRACH, which SSB the RO through which the PRACH was transmitted corresponds to / maps, and which beam the SSB corresponding to / mapped with the RO corresponds to / maps, and can transmit and receive a signal with the terminal based on the determined beam direction based on the determined RO, through the PRACH received from the terminal. However, such an operation requires that both the base station and the terminal know the SSB-to-RO mapping method. Therefore, when the SSB-to-RO mapping changes due to separated ROs, the SBFD system must operate within a range that does not impair the operation of legacy terminals. For example, even if at least one separated RO is configured, the existing SSB-to-RO mapping result must be maintained for legacy terminals.

[0146] Based on the above (e.g., Method 1 and / or Method 2), the form / configuration method of RO in SBFD slots and non-SBFD slots in the SBFD system needs to be considered. Specifically, the UL BW (bandwidth) of the non-SBFD slot can use a wideband, and the UL subband of the SBFD slot is divided into a DL subband, a guard band, and a UL subband. Therefore, the UL frequency resources in the non-SBFD slot may be relatively more than the frequency resources of the UL subband of the SBFD slot. If a separated RO is designed / configured based on a non-SBFD slot without considering the characteristics of the SBFD slot (e.g., if a separated RO is defined like a legacy RO), the separated RO may be configured outside the UL subband of the SBFD slot. In this case, an SBFD-aware UE may not be able to use the separated RO. Therefore, it is necessary to ensure that RO (or separated RO) is configured within the UL subband for SBFD-aware UEs (considering the characteristics of the SBFD slot described above). For example, it is necessary to differentiate the frequency configuration of ROs between SBFD slots and non-SBFD slots, considering the difference in frequency resources or number of frequency resources between SBFD slots and non-SBFD slots. SSB-to-RO mapping and frequency resource offset can be considered as the main methods for this.

[0147] Additionally, there may be differences not only in the frequency configuration of the RO but also in the time configuration of the RO. For example, the period configuration of the RO may also be applied differently between SBFD slots and non-SBFD slots. As described above, as defined in the standard document ("6.3.3.2 Mapping to physical resources", "Table 6.3.3.2-3" and / or "Table 6.3.3.2-4" of TS 38.211), in an unpaired spectrum (TDD) environment, the PRACH configuration index may indicate / determine which time resource the RO will be configured to at the frame / slot / symbol level. In this case, if the legacy RO and the separated RO (or the separated RO or the additional RO) have different PRACH configuration indices, the time resources between the legacy RO and the separated RO (or the separated RO or the additional RO) may be different. However, just as SBFD slots and non-SBFD slots cannot be considered as separate time resources, separated ROs (or Separated ROs or Additional ROs) and legacy ROs cannot be considered as separate time resources.

[0148] Below, we describe in detail how to apply different frequency settings / time settings of RO between SBFD slots and non-SBFD slots.

[0149] FIGS. 16 to 19 are diagrams for explaining a method of setting up legacy RO and separated RO for SBFD slots and non-SBFD slots.

[0150] First, at least one of the three methods described below can be considered for timing between the legacy RO and the separated RO. The first method is when both the legacy RO and the separated RO have the same frame period set by the PRACH configuration index (frame periods according to Table 6.3.3.2-3 and Table 6.3.3.2-4 of TS 38.211), the separated RO can be positioned before the legacy RO in time. For example, if the legacy RO slots are slots 9, 19, 29, and 39 in four frames in a 15 kHz subcarrier, the separated RO can be slots 7, 8, 17, 18, 27, 28, 37, and 38, which are the two slots before the legacy RO slots. The second method is when, conversely, the legacy RO is positioned before the separated RO in time. At this time, when the SBFD setting is applied to the flexible slot, it may be necessary to assume that the legacy RO is also set in the flexible slot. Under this assumption, the legacy RO may be set to precede the separated RO in time between the intra slot / inter slot. Referring to Fig. 16 (a), the legacy RO and / or the separated RO may be set between the inter slots. In this case, there is an advantage that the legacy RO (e.g., RO1) may be set first, and the separated RO may use the SSB-to-RO mapping rule of the immediately preceding legacy RO. The third method is to make the period of the RACH slot in which the separated RO is located have a linkage with the period of the RACH slot in which the legacy RO is located. For example, if the legacy RACH slot is set k times in 160 ms, a new RACH slot in which the separated RO is added may be set n*k times in 160 ms.

[0151] As described above, the legacy RO may be a resource that both legacy UEs and SBFD aware UEs can use for PRACH transmission, and the separated RO may be a resource that only SBFD aware UEs can use for PRACH transmission. At this time, as a method for configuring the legacy RO and the separated RO, it may be considered that RO configurations are provided for each of the legacy RO and the separated RO. In this case, at least two or more RO configurations may be provided to the UE, and at least one of the at least two or more RO configurations may be a separated RO configuration. For example, as illustrated in FIG. 16 (b), a legacy RO configuration (e.g., configuration information for configuring R01 in FIG. 16 (b)) and a separated RO configuration (e.g., configuration information for configuring RO2 in FIG. 16 (b)) may be provided (e.g., multiple RO configurations may be provided) to an SBFD aware UE.

[0152] 1. Case of Separated RO setup

[0153] A legacy RO configuration that sets a legacy RO and a separated RO configuration that sets a separated RO (or, additional-RO, SBFD RO) may be provided individually / separately. Alternatively, two or more legacy RO configurations and / or PRACH configurations of two or more separated ROs may be provided separately as needed. An SBFD aware UE can perform PRACH transmission in the legacy RO and the separated RO, and a legacy UE can perform PRACH transmission in the legacy RO. As described above, when the separated RO configuration is applied, the RO validity rule can be defined as the cases described below. In this case, an overlap may occur between the RO configured for the legacy UE and the separated RO additionally configured for the SBFD aware UE. For example, when the legacy RO and the separated RO overlap at a specific RO location, an SBFD-aware UE may assume / judge that only the legacy RO is valid (the SBFD RO is invalid) at the RO location where the two ROs overlap, and perform a PRACH transmission. Specifically, for the above ROs where the legacy RO and separated RO overlap, the SSB index determined through application of the SSB-to-RO mapping on the legacy RO setting (not the separated RO setting) can be associated.

[0154] For example, if an SBFD slot is set for a flexible slot, the legacy RO according to the legacy RO setting and the separated RO according to the separated RO setting may overlap with each other. In this case, the UE may determine / consider only the legacy RO to be valid, and determine / consider the separated RO to be invalid.

[0155] For example, for random access operation of an SBFD aware UE in RRC connected state (or RRC idle, RRC inactive state), two separate RACH configurations (providing two RO patterns) may be provided, including one legacy RACH configuration and one additional RACH configuration. In this case, the additional / separated RO in the UL subband of the SBFD symbol configured with the additional RACH configuration may be valid (only) for the SBFD aware UE. For example, the two separate RACH configurations may be provided to a UE in RRC connected state, a UE in RRC idle state, and / or a UE in RRC inactive state.

[0156] (1) Case 1

[0157] In case 1, the base station may instruct / configure an SBFD slot for at least one specific slot for SBFD aware UEs, and instruct / configure the SBFD slot as a DL slot for legacy UEs. In this case, when setting RO for legacy UEs and SBFD aware UEs with separated RO settings and / or legacy RO settings, the detailed cases can be distinguished as Case 1-1 (Fig. 17 (a)), Case 1-2 (Fig. 17 (b)), and Case 1-3 (Fig. 17 (C)). Since legacy UEs do not expect RO in DL slots, RO settings such as Case 1-1 (Case 1-1 Legacy UE in Fig. 17 (a)), Case 1-2 (Case 1-2 Legacy UE in Fig. 17 (b)), and Case 1-3 (Case 1-2 Legacy UE in Fig. 17 (c)) may be possible. For example, Case 1-1, Case 1-2, and Case 1-3 are all valid ROs, but no RO is configured in the SBFD slot. For example, in Case 1-1, Case 1-2, and Case 1-3, for legacy UEs, no RO is configured in the SBFD slot, and only an RO (e.g., RO1) can be configured in the non-SBFD slot. Hereinafter, RO configuration 1 may be a legacy RO configuration according to the existing method, and RO configuration 2 may be a separated RO configuration related to the SBFD configuration.

[0158] Meanwhile, in the proposed invention, a separated RO set for an SBFD slot may be expressed / defined as an SBFD dedicated RO, an SBFD RO, or an additional RO, and if it is an RO additionally set in relation to an SBFD setting / slot, the proposed invention can be naturally applied even if it is expressed with terms other than these.

[0159] 1) Case 1-1 (in the case of Fig. 17 (a))

[0160] In case 1-1, RO configuration 1 can configure a legacy RO (e.g., RO1) only for the UL slot, and RO configuration 2 can configure a Separated RO for the SBFD UL subband. In this case, the legacy RO and the Separated RO can use a preamble of the same format, and an RO that matches the frequency resource size of the Separated RO can be allocated. For example, as illustrated in Fig. 17 (a), the Separated RO can be configured to have a preamble of the same format and the same frequency resources as the legacy RO. In this case, there is an advantage in that an SBFD aware UE can apply PRACH repetition to both the legacy RO and the Separated RO.

[0161] For example, a legacy RO1 set based on RO configuration 1 may be determined / considered as a valid RO if it is located in a UL slot (e.g., an HD slot or a non-SBFD slot), and may be determined / considered as an invalid RO if it is located in a DL slot (or an SBFD slot). Similarly, a RO2 set based on RO configuration 2 may be determined / considered as a valid RO if it is located in an SBFD slot or a UL subband of an SBFD slot, and may be determined / considered as an invalid RO if it is located in a non-SBFD slot other than an SBFD slot. In addition, as illustrated in FIG. 17 (a), a RO2 set based on the RO configuration 2 may have the same size, location, and / or preamble sequence of frequency resources as a RO1 set based on the RO configuration 1.

[0162] 2) Case 1-2 (for Fig. 17 (b))

[0163] For Case 1-2, RO Setting 1 sets the legacy RO only in the UL slot, and RO Setting 2 can set the Separated RO in the SBFD UL subband and the UL slot. In this way, when the legacy RO and the Separated RO are set in one slot (e.g., in a non-SBFD slot that is an HD slot), the legacy RO and the Separated RO can be set not to overlap each other in the frequency resource axis.

[0164] 3 Case 1-3 (for Fig. 17 (c))

[0165] For cases 1-3, RO configuration 1 may configure legacy ROs only in UL slots, and RO configuration 2 may configure Separated ROs in SBFD UL subbands. In this case, RO configuration 2 may configure Separated ROs with a different preamble format from RO configuration 1. In addition, the Separated ROs need to be configured so as not to overlap with legacy ROs. RO configuration 2 may have a different number of FDMed ROs from RO configuration 1. For example, as illustrated in FIG. 17 (c), RO configuration 2 may configure RO2 in the SBFD UL subband to have a different frequency size and preamble format from RO1 (e.g., configured by RO configuration 1).

[0166] For example, a legacy RO1 set based on RO configuration 1 may be determined / considered as a valid RO if it is located in a UL slot (e.g., an HD slot or a non-SBFD slot), and may be determined / considered as an invalid RO if it is located in a DL slot (or an SBFD slot). Similarly, an RO2 set based on RO configuration 2 may be determined / considered as a valid RO if it is located in an SBFD slot or a UL subband of an SBFD slot, and may be determined / considered as an invalid RO if it is located in a non-SBFD slot other than an SBFD slot. In addition, as illustrated in FIG. 17 (b), an RO2 set based on the RO configuration 2 may have different frequency resource sizes, locations, and / or preamble sequences from an RO1 set based on the RO configuration 1.

[0167] For example, in Case 1-1 and / or Case 1-3, a RACH configuration including one legacy RACH configuration and one separate additional RACH configuration may support random access operation for an SBFD aware UE in RRC idle state, RRC inactive state, or RRC connected state.

[0168] - Additional ROs in non-SBFD symbols configured with additional RACH settings may be judged / considered invalid for SBFD aware UEs.

[0169] (2) Case 2 (see Fig. 18)

[0170] For Case 2, the base station may instruct / configure at least one slot as an SBFD slot for SBFD-aware UEs and as a flexible slot for legacy UEs. The detailed cases may be distinguished based on how ROs are handled for legacy UEs and SBFD-aware UEs with separate RO configuration / legacy RO configuration. Since legacy UEs may expect RO configuration in flexible slots, configuration of ROs such as Case 2-1, Case 2-2, and Case 2-3 may be possible.

[0171] 1) Case 2-1 (Fig. 18 (a))

[0172] In case 2-1, since SBFD UL subband frequency resources are also considered in RO configuration 1, RO may be valid for a specific slot configured as an SBFD slot. For example, as illustrated in Fig. 18 (a), RO1 configured according to RO configuration 1 may be valid for an SBFD aware UE. Since the number of FDMed ROs in a UL slot is limited from the perspective of a legacy UE, UL coverage or delay issues may become relatively large after SBFD is applied. If a separated RO (e.g., RO2) is configured in the SBFD slot / UL slot through RO configuration 2, an SBFD aware UE can transmit PRACH in more ROs than a legacy UE.

[0173] 2) Case 2-2 (Fig. 18 (b))

[0174] In case 2-2, legacy RO configuration and separated RO configuration may be performed considering the location / size of frequency resources of the SBFD UL subband. In this case, all ROs (e.g., RO1s) may be valid for the legacy UE (or, since the SBFD UL subband frequency resources are considered, all ROs become valid ROs). From the legacy UE's perspective, since the number of FDMed ROs in a UL slot is limited, UL coverage or delay issues may become relatively greater after SBFD is applied. If a separated RO (e.g., RO2) is configured in the SBFD slot / UL slot through RO configuration 2, the SBFD aware UE can transmit PRACHs in more ROs (e.g., RO1 and RO2) than the legacy UE. In this case, overlap may occur between the legacy RO configured by RO configuration 1 and the separated RO configured by RO configuration 2.

[0175] 3) Case 2-3 (Fig. 18 (c))

[0176] For case 2-3, RO configuration 1 can set legacy RO only in UL slots, and RO configuration 2 can set Separated RO within the SBFD UL subband. For example, RO configuration 1 can set RO (e.g., RO1) only for UL slots even if the slots with SBFD configured are flexible slots, and RO configuration 2 can set RO (e.g., RO2) only within the SBFD UL subband. Here, RO configuration 2 can set a different preamble format from RO configuration 1. In this case, overlap between legacy RO and Separated RO must not occur. Alternatively, RO configuration 2 can have a different number of FDMed ROs from RO configuration 1.

[0177] For example, a legacy RO1 configured based on RO configuration 1 may be determined / considered as a valid RO if it is located in a UL slot (e.g., an HD slot or a non-SBFD slot), and may be determined / considered as an invalid RO if it is located in a DL slot (or an SBFD slot). Similarly, a RO2 configured based on RO configuration 2 may be determined / considered as a valid RO if it is located in an SBFD slot or within a UL subband of an SBFD slot, and may be determined / considered as an invalid RO if it is located in a non-SBFD slot other than an SBFD slot.

[0178] (3) Case 3 (Fig. 19)

[0179] In Case 3, the base station may designate slots designated as SBFD slots to SBFD-aware UEs, while designating them as DL slots and / or flexible slots to legacy UEs. This example illustrates separate RO configurations for legacy UEs and SBFD-aware UEs. Since legacy UEs expect ROs in flexible slots, a RO configuration similar to Case 3-1 may be possible.

[0180] In case 3-1, all ROs become valid because the SBFD UL subband frequency resources are considered. For example, since both RO configuration 1 and RO configuration 2 configure ROs considering the frequency location / size of the SBFD UL subband, all ROs configured in the flexible slot and UL slot according to RO configuration 1 can be valid. Since the number of FDMed ROs in the flexible slot / UL slot is limited, legacy UEs may experience relatively greater UL coverage or delay issues after SBFD is applied. When separated ROs are configured in the SBFD slot / UL slot through RO configuration 2, SBFD aware UEs can transmit PRACHs based on more ROs than legacy UEs.

[0181] Below, we focus on the changes in associated items that occur due to differences in how the frequency reference point and / or frequency offset of the RO are indicated for each of the separated RO configuration and the legacy RO configuration.

[0182] RO frequency offset

[0183] FIG. 20 is a diagram illustrating a method for setting parameters for determining RO between SBFD slots and non-SBFD slots.

[0184] The first method described below describes how to set separate parameters for SBFD / non-SBFD. In the first method, the position of the RO can be specified / set by applying a frequency offset with a reference point for the SBFD UL subband, or the position of the SBFD RO can be specified / set by applying a (separated) frequency offset with a reference point for the non-SBFD UL wideband. For example, the first method can be a method that shares the frequency offset between the SBFD slot and the non-SBFD slot (or, the legacy RO and the separated RO), but sets the legacy RO and the separated RO using different reference points. The second method is a method that indicates a (separated) additional offset for the SBFD slot. In this case, the base station can convey information about the additional offset to the UE based on the frequency / time offset of the indicated RO in the non-SBFD UL BW. At this time, the base station (or SBFD aware UE) can calculate the difference in RO frequency resource locations between the SBFD slot and the non-SBFD slot, and use the calculated difference as the time / frequency offset of the RO in the SBFD slot.

[0185] 2. Separated RO with separated parameters

[0186] The first method may be to define a new parameter separate from the legacy operation. For example, the position of the separated RO (or Separated RO) may be specified / set by applying a frequency offset to the reference point in the SBFD UL subband. Alternatively, the reference point may be set based on a wideband (e.g., a frequency band of a UL slot), similar to the legacy operation, and a separate frequency offset may be set. For example, since a frequency offset for specifying / setting the position of a legacy RO is defined in the existing method using the wideband as the reference point, a separated frequency offset may be defined for specifying / setting the frequency position of the separated RO that is distinct from this.

[0187] In the first method, the operation of the existing system sets the location of the lowest resource of the UL BW (e.g., PRB0 with the lowest index) as a reference point, and the RO can be set by applying a predetermined offset from the reference point (e.g., reference point + predetermined offset = frequency location of RO). However, since the UL subband of the SBFD slot and the UL BW of the non-SBFD slot are different from each other, it is necessary to set different reference points for each slot. For example, since the location of the PRB with the lowest index of the UL subband of the SBFD slot and the location of the PRB with the lowest index of the UL wideband of the non-SBFD slot are different, it is necessary to redefine the reference point for the SBFD slot. In this case, the proposed method may be a method of setting the starting points of different UL frequency resources of the SBFD slot and the non-SBFD slot as reference points.

[0188] For example, for the first method, the following may be considered to determine the lowest frequency RO of the separated RO or additional RO in the SBFD symbol / slot.

[0189] - The parameter msg1-FrequencyStart of rach-ConfigCommon can be reinterpreted as the frequency offset of the lowest RO in the frequency domain with respect to the lowest PRB of UL usable PRBs.

[0190] - Meanwhile, ROs outside of UL usable PRBs are invalid.

[0191] Alternatively, if the separated RO configuration and the legacy RO configuration are provided separately, parameters such as msg1-FrequencyStart may be provided individually between the separated RO configuration and the legacy RO configuration. Meanwhile, as described above, the values ​​of msg1-FrequencyStart included in each of the separated RO configuration and the legacy RO configuration may be shared or identical. Alternatively, the values ​​of msg1-FrequencyStart for each of the separated RO configuration and the legacy RO configuration may be different.

[0192] Referring to Fig. 20 (a), the reference point of the separated RO can be determined / set differently from the reference point of the legacy RO. At this time, as illustrated in Fig. 20 (b), the frequency offset for setting the separated RO can be the same as the frequency offset for setting the legacy RO. Here, the value of the frequency offset can be a value that has been reused from a value used in legacy operation. For example, the frequency position of the separated RO with the lowest frequency can have a reference point different from the reference point of the legacy RO, but can be determined / set by reusing the frequency offset indicated for the legacy RO.

[0193] The first example (e.g., the configuration of separated RO according to FIGS. 20 (a) and (b)) has the advantage that less information needs to be additionally indicated for configuring separated RO. The lowest frequency resource of the UL subband in the SBFD slot is information provided for other operations (e.g., PUCCH / PUSCH / SRS), and therefore is not additional information provided to the UE. Therefore, if there is a prior agreement between the base station and the UE, the UE can reuse the information about the lowest frequency resource of the UL subband received for other operations (e.g., PUCCH / PUSCH / SRS), use that resource as a reference point, and determine a frequency resource offset from the reference point as the starting point of the RO. For example, the UE may determine the reference point of the separated RO based on the lowest resource (e.g., PRB with the lowest index) of the UL subband provided to determine / set the frequency location of PUCCH / PUSCH / SRS, etc., and may determine the separated RO by reusing the frequency offset applied for determining the legacy RO.

[0194] Furthermore, the first example has the additional advantage of allowing other existing features to be easily used in SBFD as well. While the focus is on RO in the following description, the proposed approach can also address the gap in bandwidth between SBFD and non-SBFD slots for other technologies (e.g., frequency hopping). For example, a reference point for frequency resources may be required even when frequency hopping is performed in PUSCH / PUCCH / SRS. In this case, if the lowest frequency in SBFD / non-SBFD slots is used as the reference point for frequency resources, as proposed, the UL subband in the SBFD slot can be perceived as having the same BW as the non-SBFD slot.

[0195] OFDM baseband signal generation related to PRACH of non-SBFD slots / symbols can be determined / defined as shown in Table 7 below.

[0196]

[0197] For example, in relation to the first example, for the SBFD slot / symbol can be reused. However, at this time, the reference point may be the lowest PRB of the SBFD UL subband, not PRB 0 of the active UL BWP. For example, in Table 7 The definition for SBFD slots / symbols is " It can be modified to “is the frequency offset of the lowest PRACH transmission occasion in frequency domain with respect to lowest physical resource block of SBFD UL subband within the active uplink bandwidth part”.

[0198] The RRC parameters for the reference points related to such SBFD slots / symbols can be defined as in Table 8 below, and “locationAndBandwidth” can be defined as in Table 9.

[0199] BWPinformation element-- ASN1START-- TAG-BWP-STARTBWP ::= SEQUENCE {locationAndBandwidth INTEGER (0..37949),locationAndBandwidth_SBFD-r19INTEGER (0..37949),subcarrierSpacing SubcarrierSpacing,cyclicPrefix ENUMERATED { extended} OPTIONAL -- Need R}-- TAG-BWP-STOP-- ASN1STOP

[0200]

[0201] As described above, the starting point and bandwidth of BWP in the frequency domain can be calculated based on the indicated resource indicator value (RIV). The BWP (bandwidth part) for the subband of SBFD can be explicitly indicated through the new (RRC) parameter as shown in Table 8, or the BWP or subband of SBFD can be determined / judged implicitly through the value of the existing locationAndBandwidth. If explicitly indicated, the reference point in the separated RO configuration is determined based on locationAndBandwidth_SBFD-r19, and if implicitly indicated, the reference point in the separated RO configuration can be determined based on locationAndBandwidth.

[0202] The second example is that in the operation of the existing system, after designating the lowest frequency resource (e.g., the lowest PRB index) of the UL BW (bandwidth) as a reference point, the RO (or the lowest frequency RO or the start frequency of the RO) can be set at a frequency position increased by a predetermined offset from the reference point. However, since the UL subband of the SBFD slot and the UL BW of the non-SBFD slot are set differently, it is necessary to define different reference points for the SBFD slot and the non-SBFD slot, respectively. At this time, the method proposed in the second example may be a method of indicating different legacy frequency offsets and separated frequency offsets of the SBFD slot and the non-SBFD slot. For example, as illustrated in FIG. 20 (c), the UE can be instructed / set the frequency offset of the separated RO and the frequency offset of the legacy RO, respectively. For example, the separated RO (or the lowest frequency separated RO) may have its frequency position set / determined using the same reference point as the legacy RO, but with a frequency offset different from the frequency offset of the legacy RO.

[0203] A second example like this may be advantageous in terms of the degree of freedom in setting the frequency location of ROs (e.g., separated ROs). Since SBFD operation causes Cross Link Interference (CLI) between inter-subbands compared to HD (e.g., non-SBFD), there may be a need to reduce CLI occurring between UEs for PRACH transmission. Therefore, there may be a need for a different location in the SBFD UL subband compared to the existing HD RO setting location, and this can be freely changed through a separated frequency offset. For example, since the location of the separated RO (or the separated RO with the lowest frequency) can be freely set through a separated frequency offset, the location change / setting of the SBFD UL subband can be facilitated.

[0204] OFDM baseband signal generation related to PRACH of non-SBFD slots / symbols can be determined / defined as shown in Table 10 below.

[0205]

[0206] In the second example, for the SBFD slot / symbol instead can be used. Here, may be a frequency offset value based on PRB0 of the active uplink BWP of the UL wideband on the frequency axis. When is 0, the lowest PRACH transmission occasion can be set at PRB0 of the active uplink BWP of the UL wideband, for example, for the second example, the last sentence of Table 10 is " is the frequency offset of the lowest PRACH transmission occasion in frequency domain with respect to physical resource block 0 of the active uplink bandwidth part. The quantity It can be defined as "is given by the higher-layer parametermsgA-RO-FrequencyStart_SBFD-r19if configured and a type-2 random-access procedure is initiated as described in clause 8.1 of [5, TS 38.213], otherwise bymsg1-FrequencyStart_SBFD-r19 as described in clause 8.1 of [5 TS 38.213]".

[0207] Above The RRC parameters related to can be defined as shown in Table 11.

[0208] RACH-ConfigGeneric ::= SEQUENCE {prach-ConfigurationIndex INTEGER (0..255),msg1-FDM ENUMERATED {one, two, four, eight},msg1-FrequencyStart INTEGER (0..maxNrofPhysicalResourceBlocks-1),zeroCorrelationZoneConfig INTEGER(0..15),preambleReceivedTargetPower INTEGER (-202..-60),preambleTransMax ENUMERATED {n3, n4, n5, n6, n7, n8, n10, n20, n50, n100, n200},powerRampingStep ENUMERATED {dB0, dB2, dB4, dB6},ra-ResponseWindow ENUMERATED {sl1, sl2, sl4, sl8, sl10, sl20, sl40, sl80},...,[[prach-ConfigurationPeriodScaling-IAB-r16 ENUMERATED {scf1,scf2,scf4,scf8,scf16,scf32,scf64} OPTIONAL, -- Need Rprach-ConfigurationFrameOffset-IAB-r16 INTEGER (0..63) OPTIONAL, -- Need Rprach-ConfigurationSOffset-IAB-r16 INTEGER (0..39) OPTIONAL, -- Need Rra-ResponseWindow-v1610 ENUMERATED { sl60, sl160} OPTIONAL, -- Need Rprach-ConfigurationIndex-v1610 INTEGER (256..262) OPTIONAL -- Need R]],[[ra-ResponseWindow-v1700 ENUMERATED {sl240, sl320, sl640, sl960, sl1280, sl1920, sl2560} OPTIONAL -- Need R]]msg1-FrequencyStart_SBFD-r19}.

[0209] In the first and / or second examples described above, different RO periods can be set for SBFD and non-SBFD slots. Since independent parameters are used for SBFD and / or non-SBFD, additional considerations must be given to SSB-to-RO mapping. Since the following discusses separated ROs, which are indicated separately from legacy ROs, a different mapping can be used for SSB-to-RO mapping as well.

[0210] Figure 21 is a diagram for explaining an SSB-to-RO mapping method for separated RO.

[0211] In legacy operation, the steps of the SSB-to-RO mapping operation are as follows:

[0212] - Different SSB-to-RO mappings within a single RO.

[0213] - SSB-to-RO mapping between Multiplexed ROs with different frequency resources.

[0214] - SSB-to-RO mapping between multiplexed ROs with different time resources.

[0215] - Next PRACH slot

[0216] For example, referring to Fig. 21 (a), when four ROs are given and three SSBs are mapped each, a duplicate SSB may be mapped to one of the four ROs (RO1 or R04).

[0217] If the same mapping method is used in other slots (e.g., slot 2 in FIG. 21 (a)), the SSB-to-RO mapping in each slot will be a different mapping for each time / frequency resource. Therefore, if additional resources for the RO are used, the SSB-to-RO mapping may be different, which may indicate that the mapping method for the separated RO may use a different SSB-to-RO mapping compared to the legacy RO. Since the system transmits and receives signals not only to SBFD aware terminals but also to legacy terminals, if the SSB-to-RO mapping is different, the two ROs (e.g., the legacy RO and the separated RO) cannot be configured on the same frequency resource at the same time. Therefore, the separated RO and the legacy RO need to be configured / allocated on different time / frequency resources. However, if the two ROs overlap each other under some special circumstances, the overlapped RO may follow the legacy SSB-to-RO mapping.

[0218] This approach can offer a high degree of freedom, as the separated RO uses different time / frequency resources than the legacy RO. This high degree of freedom means that SBFD terminals can perform operations that are completely different from those of legacy terminals. For example, these different operations may include the sequences that constitute the PRACH.

[0219] As described above, the starting point of the frequency position of the RO in the SBFD slot in the separated RO instruction needs to be changed to suit the SBFD UL subband configuration. Accordingly, as described above, the first method is characterized by setting the lowest frequency resource or reference point differently depending on the SBFD / non-SBFD slot.

[0220] 3. Separated RO with additional frequency offset

[0221] The second method may be to define and use an additional offset separately for the SBFD slot in addition to the existing frequency offset (hereinafter, legacy offset). As explained in Section '2', the legacy operation is to set the RO in the frequency resource with a difference of the frequency offset from the reference point. Since the BW of the SBFD / non-SBFD slots are different, a method may be needed to indicate that the RO can be included in the UL subband in the SBFD slot. Hereinafter, when the configured legacy RO is set outside the SBFD UL subband, a method is proposed to set the frequency resource location of the Separated RO (or SBFD RO) based on the location of the legacy RO resource (e.g., the start frequency of the legacy RO or the frequency location of the legacy RO with the lowest frequency) by indicating an additional offset (hereinafter, additional offset) (see Fig. 21 (b)). Depending on the location of the frequency resource of the existing legacy RO, the additional offset can be indicated / set to a value within the range of negative or positive.

[0222] OFDM baseband signal generation related to PRACH of non-SBFD slots / symbols can be determined / defined as shown in Table 12 below.

[0223]

[0224] For example, for SBFD slots / symbols, in Table 12 instead + can be used. Here, is an additional offset for RO to be positioned within the SBFD UL subband. If is 0, it may be the location of the frequency resource of RO in the Non-SBFD slot.

[0225] Above The RRC parameters for can be defined as shown in Table 13.

[0226] RACH-ConfigGeneric ::= SEQUENCE {prach-ConfigurationIndex INTEGER (0..255),msg1-FDM ENUMERATED {one, two, four, eight},msg1-FrequencyStart INTEGER (0..maxNrofPhysicalResourceBlocks-1),zeroCorrelationZoneConfig INTEGER(0..15),preambleReceivedTargetPower INTEGER (-202..-60),preambleTransMax ENUMERATED {n3, n4, n5, n6, n7, n8, n10, n20, n50, n100, n200},powerRampingStep ENUMERATED {dB0, dB2, dB4, dB6},ra-ResponseWindow ENUMERATED {sl1, sl2, sl4, sl8, sl10, sl20, sl40, sl80},...,[[prach-ConfigurationPeriodScaling-IAB-r16 ENUMERATED {scf1,scf2,scf4,scf8,scf16,scf32,scf64} OPTIONAL, -- Need Rprach-ConfigurationFrameOffset-IAB-r16 INTEGER (0..63) OPTIONAL, -- Need Rprach-ConfigurationSOffset-IAB-r16 INTEGER (0..39) OPTIONAL, -- Need Rra-ResponseWindow-v1610 ENUMERATED { sl60, sl160} OPTIONAL, -- Need Rprach-ConfigurationIndex-v1610 INTEGER (256..262) OPTIONAL -- Need R]],[[ra-ResponseWindow-v1700 ENUMERATED {sl240, sl320, sl640, sl960, sl1280, sl1920, sl2560} OPTIONAL -- Need R]]msg1-FrequencyStart_offset_SBFD-r19}.

[0227] At this time, the frequency offset for the SBFD RO can be set / defined as msg1-FrequencyStart+msg1-FrequencyStart_offset_SBFD-r19. For example, as illustrated in Fig. 21 (b), the additional RO can be determined based on an offset value obtained by adding the value of "msg1-FrequencyStart_offset_SBFD-r19" to the offset (msg1-FrequencyStart) for the default RO.

[0228] The proposed method described above is effective in SBFD slots, and even SBFD UEs can use legacy ROs in slots other than SBFD slots (e.g., non-SBFD slots). Therefore, multiple ROs can exist across SBFD slots and legacy slots (e.g., non-SBFD slots). SBFD UEs can use legacy / SBFD ROs organically connected rather than operating separately. For example, there is the case of PRACH repetition. For example, SBFD UEs can use both legacy ROs and separated ROs in repeated transmission of a specific PRACH.

[0229] According to legacy rules, PRACH repetition can only be performed using ROs within the same frequency band. According to the SSB-RO-mapping rule described above, the types of SSBs and the number of ROs can differ, so even SSBs of the same type can be mapped to different frequencies when mapping is performed sequentially. However, PRACH repetition does not use SSBs mapped to different frequencies, but only SSBs mapped to the same frequency. This is to simplify operations due to factors such as terminal complexity.

[0230] The frequency resource difference caused by the additional offset described in Section '3' takes a somewhat different form. The frequency resource difference caused by the above SSB-to-RO mapping can occur even within the same slot, and in this case, the terminal must quickly change the RO. However, in the case of the additional RO (Separated RO, or SBFD RO), it is generated / configured across multiple connected SBFD slots, and the cycle of changing from an SBFD slot to a UL wideband slot can occur after at least a few slots. Therefore, the frequency change due to the additional offset is expected to not impose a large burden on the terminal and seems to be sufficiently usable.

[0231] Alternatively, the use of the additional offset described in Section '3' has the advantage that the parameters used in the legacy RO can be inherited or used as is. Since the additional RO (Separated RO) is set / indicated by applying only a separate additional offset based on the existing legacy RO, the parameters of the legacy RO can be reused (inherited) as they are for the remaining parameters. There may be an SSB-to-RO mapping in this reuse (inheritance) range. Since the first method uses a separated frequency offset, the SSB-to-RO mapping may be different. Thus, since the second method (and / or the first method) in Section '3' shares the legacy SSB-to-RO mapping method, the second method has the advantage that there is no need for the restriction that the location of the resource should not overlap with the legacy RO. Additionally, since the second method shares the SSB-to-RO mapping, the sequence of the PRACH preamble may also be shared, and it may be possible to overlap the frequency / time resources with legacy ROs in non-SBFD slots. Therefore, the use of additional offsets can be restricted to only SBFD slots.

[0232] For example, when mapping SSB to the separated RO, the UE may use the existing SSB-to-RO mapping rule to map the separated RO and SSB. Specifically, the legacy SSB-RO mapping rule may be used for the separated RO set by the second RACH configuration, but the SSB-RO mapping for the separated RO may be performed separately or independently from the legacy RO set by the legacy RACH configuration.

[0233] Meanwhile, as described above, the proposed invention relates to a method by which a UE, which can recognize when a base station performs an FD (full duplex) operation, can effectively set / allocate an RO in the UL band for the time period in which the base station performs an FD-related operation. Accordingly, the proposed methods described above can be naturally applied to any time period in which the base station performs an FD-related operation, and can also be naturally applied to SSFD (spectrum sharing full duplex) that is not divided into UL / DL subbands.

[0234] Figure 22 is a diagram illustrating how a UE sets up ROs for initial connection.

[0235] As described above, the UE may be an SBFD aware UE that can recognize the SBFD time interval during which the SBFD operation is performed at the base station. Meanwhile, the UE may receive from the base station a configuration for an additional RO applicable to an SBFD slot related to the SBFD operation, and may perform an initial access procedure for the base station by additionally considering the additional RO. As described above, the additional RO is an RO additionally configured / allocated for a UL subband related to the SBFD operation, and may have the same configuration as a Separated RO, an SBFD dedicated RO, or an SBFD RO with only different terminology. Hereinafter, a method for a UE to configure an additional RO will be described, but it is naturally assumed that the methods described in FIGS. 14 to 21 are applied in the proposed contents described below.

[0236] Referring to FIG. 22, a UE may receive configuration information including information on a first time resource related to SBFD (Sub-band Full Duplex) (S221). Here, the first time resource is a time resource for at least one slot / symbol in which the base station performs the above-described SBFD operation, and a UL subband and a DL subband may be configured for at least one slot / symbol. For example, the first time resource may be the above-described SBFD slots / symbols. In addition, the configuration information may further include information for specifying a DL subband and a UL subband related to the SBFD operation, in addition to the information on the first time resource.

[0237] Next, the UE may receive a first RACH configuration for a Random Access Channel Occasion (RO) and a second RACH configuration for an additional RO related to the SBFD that is transmitted separately from the first RACH configuration (S223). As described above, the first RACH configuration may include a first PRACH configuration index that configures a legacy RO in a time resource other than the first time resource (e.g., a non-SBFD slot), and the second RACH configuration may include a second PRACH configuration index that configures an additional RO in the first time resource where the SBFD operation is performed. For example, the first RACH configuration and the second RACH configuration may include different PRACH configuration indices.

[0238] Alternatively, the first RACH configuration may be for configuring a legacy RO as described above, and may include information for configuring / allocating at least one legacy RO within an active UL BWP in a UL slot. The second RACH configuration may be for configuring an additional RO for an SBFD slot as described above, and may include information for configuring / allocating the additional RO within a UL subband within the SBFD slot.

[0239] Alternatively, the UE may determine the validity of the additional RO based on the first time resource. For example, the UE may determine the ROs configured / allocated within the first time resource among the additional ROs configured with the second RACH configuration as valid ROs, and determine the ROs configured / allocated in a time interval (e.g., a non-SBFD slot / symbol) other than the first time resource as invalid ROs. Meanwhile, when the first time resource is configured for a DL slot, the ROs configured / allocated within the first time resource among the ROs configured with the first RACH configuration may be determined / considered as invalid ROs.

[0240] Alternatively, among the additional ROs configured by the second RACH configuration, a specific additional RO may overlap with a specific RO configured in the first RACH configuration in the time domain. For example, if the first time resource includes a flexible slot / symbol, the specific additional RO and the specific RO may overlap in the time domain in the flexible slot / symbol. In this case, the UE may determine / consider only the specific RO among the specific additional RO and the specific RO as valid, and may determine / consider the specific additional RO as an invalid RO.

[0241] Alternatively, as described above, the UE may specify the additional RO and the legacy RO based on the first RACH configuration and the second RACH configuration (see FIG. 20 (a), (b)). For example, the UE may determine the start frequency of the additional RO (or the start frequency of the additional RO having the lowest frequency among the additional ROs) by applying a first frequency offset to a first reference frequency separately configured for the UL subband on which the SBFD operation is performed. Furthermore, the UE may determine the start frequency of the RO (or the start frequency of the RO having the lowest frequency among the ROs) by applying a second frequency offset to a second reference frequency for an active UL BWP for a UL slot on which the SBFD operation is not performed. Here, the first reference frequency may be a PRB (Physical Resource Block) having a lowest index in the UL subband associated with the SBFD, or may be determined / indicated based on the lowest PRB. The second reference frequency may be a PRB having a lowest index in an active uplink bandwidth part (BWP) for the UE, or may be determined / indicated based on the lowest PRB. In addition, as described above, the first frequency offset may have the same value as the second frequency offset. For example, as described above, the UE may reuse the second frequency offset included in the first RACH configuration (rach-ConfigCommon) (e.g., the value of msg1-FrequencyStart included in rach-ConfigCommon) as a frequency offset for determining the additional ROs.

[0242] Alternatively, the UE may use existing SSB-to-RO mapping rules to map the additional RO and SSB. For example, the legacy SSB-to-RO mapping rules may be used for the additional RO configured by the second RACH configuration, but the SSB-to-RO may be mapped separately from the legacy RO configured by the legacy RACH configuration.

[0243] Next, the UE may transmit a PRACH or a PRACH preamble using at least one RO among the additional ROs and the ROs (S225). For example, the UE may randomly select at least one RO among the legacy ROs configured through the first RACH configuration and the additional ROs configured through the second RACH configuration to transmit the PRACH or a PRACH preamble, or may select an RO mapped to an index of an SSB selected based on the reception quality of the received SSB among the legacy ROs and the additional ROs to transmit the PRACH or a PRACH preamble.

[0244] Figure 23 is a diagram illustrating a method for a base station to set up ROs for initial connection to a UE.

[0245] Referring to FIG. 23, the base station may transmit configuration information including information on a first time resource related to SBFD (Sub-band Full Duplex) to the UE (S231). Here, the first time resource is a time resource for at least one slot / symbol in which the base station performs the above-described SBFD operation, and a UL subband and a DL subband may be configured for at least one slot / symbol. For example, the first time resource may be the above-described SBFD slots / symbols. In addition, the configuration information may further include information for specifying a DL subband and a UL subband related to the SBFD operation in addition to the information on the first time resource.

[0246] Next, the base station may transmit a first RACH configuration for configuring an RO (e.g., a legacy RO) and a second RACH configuration for configuring an additional RO related to the SBFD (S233). For example, the base station may determine a second PRACH configuration index for which an additional RO may be configured in the first time resource in which the SBFD operation is performed, and transmit a second RACH configuration including the determined second PRACH configuration index. In addition, the base station may determine a first PRACH configuration index for which a legacy RO may be configured in a time resource other than the first time resource (e.g., a non-SBFD slot), and transmit a first RACH configuration including the first PRACH configuration index.

[0247] Next, the base station can receive the PRACH or PRACH preamble based on the additional RO and the RO (S235). The base station can perform the RACH procedure described above, considering the SSB index mapped to the RO where the PRACH or PRACH preamble is received. For example, the base station can transmit an RAR including a RAPID (Random Access Preamble ID) corresponding to the PRACH or PRACH preamble to the UE, and perform the RACH procedure described above to transmit and receive data with the UE.

[0248] In this way, the proposed invention can efficiently configure additional ROs for UEs that can recognize SBFD slots. Alternatively, the proposed invention can ensure faster RACH procedure execution by UEs by configuring additional ROs for SBFD slots. Alternatively, the proposed invention can ensure that additional ROs are effectively configured within the UL subband of the SBFD slot by separately setting the reference frequency of the additional ROs for the SBFD slots. Alternatively, the proposed invention can minimize the signaling load caused by introducing additional RO configurations related to SBFD by configuring additional ROs that reuse the frequency offsets of existing legacy ROs.

[0249] Examples of communication systems to which the invention applies

[0250] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts of the present invention disclosed in this document may be applied to various fields requiring wireless communication / connection (e.g., 5G) between devices.

[0251] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.

[0252] Figure 24 illustrates a communication system applied to the present invention.

[0253] Referring to FIG. 24, a communication system (1) applied to the present invention includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and can be implemented in the form of HMD (Head-Mounted Device), HUD (Head-Up Display) installed in a vehicle, television, smartphone, computer, wearable device, home appliance, digital signage, vehicle, robot, etc. Mobile devices can include smartphone, smart pad, wearable device (e.g., smart watch, smart glass), computer (e.g., laptop, etc.), etc. Home appliances can include TV, refrigerator, washing machine, etc. IoT devices can include sensors, smart meters, etc. For example, base stations and networks can also be implemented as wireless devices, and a specific wireless device (200a) can act as a base station / network node to other wireless devices.

[0254] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, etc. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0255] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or, D2D communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present invention.

[0256] Examples of wireless devices to which the present invention is applied

[0257] Figure 25 illustrates a wireless device applicable to the present invention.

[0258] Referring to FIG. 25, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals via various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the base station (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 24.

[0259] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chipset designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present invention, a wireless device may also mean a communication modem / circuit / chipset.

[0260] According to one example, the first wireless device (100) or terminal may include a processor (102) and a memory (104) connected to the RF transceiver. The memory (104) may include at least one program capable of performing operations related to the embodiments described in FIGS. 14 to 23.

[0261] Specifically, the processor (102) controls the RF transceiver (106) to receive configuration information including information on a first time resource related to a Sub-band Full Duplex (SBFD), receive a first RACH configuration for a Random Access Channel Occasion (RO) and a second RACH configuration for an additional RO related to the SBFD, and transmit a Physical Random Access Channel (PRACH) based on at least one of the RO and the additional RO.

[0262] Alternatively, a processing device including a processor (102) and a memory (104) may be configured. In this case, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions, wherein the instructions, based on being executed by the at least one processor, cause the terminal (100) to: receive configuration information including information on a first time resource related to a Sub-band Full Duplex (SBFD), receive a first RACH configuration for a Random Access Channel Occasion (RO) and a second RACH configuration for an additional RO related to the SBFD, and transmit a PRACH (Physical Random Access Channel) based on at least one of the RO and the additional RO.

[0263] Alternatively, a non-transitory computer-readable storage medium having recorded thereon instructions for performing the proposed methods described with reference to FIGS. 14 to 23 may be configured.

[0264] The second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). Furthermore, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present invention, a wireless device may also mean a communication modem / circuit / chip.

[0265] According to one example, the second wireless device (200) or base station may include a processor (202) and a memory (204) connected to the RF transceiver. The memory (204) may include at least one program capable of performing operations related to the embodiments described in FIGS. 14 to 23.

[0266] Specifically, the processor (202) controls the transceiver (206) or the RF transceiver to transmit configuration information including information on a first time resource related to a Sub-band Full Duplex (SBFD), transmit a first RACH configuration for a Random Access Channel Occasion (RO) and a second RACH configuration for an additional RO related to the SBFD, and receive a Physical Random Access Channel (PRACH) based on at least one of the RO and the additional RO.

[0267] Hereinafter, the hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed herein, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0268] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0269] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0270] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0271] Examples of wireless devices to which the present invention is applied

[0272] Figure 26 illustrates another example of a wireless device applicable to the present invention. The wireless device may be implemented in various forms depending on the use case / service.

[0273] Referring to FIG. 26, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 25 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 26. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 25. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0274] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 24, 100a), a vehicle (Fig. 24, 100b-1, 100b-2), an XR device (Fig. 24, 100c), a portable device (Fig. 24, 100d), a home appliance (Fig. 24, 100e), an IoT device (Fig. 24, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 24, 400), a base station (Fig. 24, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0275] In FIG. 26, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and a first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of a set of one or more processors. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0276] Here, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PAN (personal area networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0277] The embodiments described above are combinations of components and features of the present invention in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form an embodiment of the present invention by combining some components and / or features. The order of operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form an embodiment or may be incorporated as a new claim through a post-application amendment.

[0278] In this document, embodiments of the present invention have been described primarily focusing on the signal transmission and reception relationship between a terminal and a base station. This transmission and reception relationship is equally / similarly extended to signal transmission and reception between a terminal and a relay or a base station and a relay. Certain operations described as being performed by a base station in this document may, in some cases, be performed by its upper node. That is, it is obvious that various operations performed for communication with a terminal in a network composed of multiple network nodes including a base station may be performed by the base station or other network nodes other than the base station. The base station may be replaced by terms such as fixed station, Node B, eNode B (eNB), and access point. In addition, the terminal may be replaced by terms such as UE (User Equipment), MS (Mobile Station), MSS (Mobile Subscriber Station).

[0279] Embodiments of the present invention may be implemented by various means, for example, hardware, firmware, software, or a combination thereof. In the case of hardware implementation, an embodiment of the present invention may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.

[0280] When implemented via firmware or software, an embodiment of the present invention may be implemented in the form of modules, procedures, functions, etc. that perform the functions or operations described above. The software code may be stored in a memory unit and executed by a processor. The memory unit may be located within or outside the processor and may exchange data with the processor via various known means.

[0281] It will be apparent to those skilled in the art that the present invention can be embodied in other specific forms without departing from the scope of the invention. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present invention should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present invention are intended to be included within the scope of the present invention.

[0282] The embodiments of the present invention as described above can be applied to various mobile communication systems.

Claims

1. In the method by UE (user equipment), A step of receiving configuration information including information on a first time resource related to SBFD (Sub-band Full Duplex); A step of receiving a first RACH (Random Access Channel) setting for a RO (Random Access Channel Occasion); A step of receiving a second RACH configuration for an additional RO associated with the above SBFD; and A method comprising: transmitting a PRACH (Physical Random Access Channel) based on at least one of the above RO and an additional RO.

2. In paragraph 1, The above second RACH setting sets the additional RO for the first time interval for a UE that can recognize the first time resource associated with the SBFD, A method characterized in that the second RACH configuration sets the additional RO within the UL (Uplink) subband set within the first time resource.

3. In paragraph 1, A method characterized in that the UE considers the additional RO set by the second RACH setting to be valid even if the additional RO is set in a time interval outside the first time interval.

4. In paragraph 1 A method, characterized in that the UE determines the validity of the additional RO based on the first time resource.

5. In paragraph 1, A method characterized in that the additional RO is determined to be invalid based on not being set within the first time resource.

6. In paragraph 1, The above additional RO is determined based on a first reference frequency and a first frequency offset, and the RO is determined based on a second reference frequency and a second frequency offset, A method, characterized in that the first reference frequency is set differently from the second reference frequency based on an UL (Uplink) subband associated with the SBFD.

7. In paragraph 6, The first reference frequency is determined based on the PRB (Physical Resource Block) with the lowest index in the UL subband associated with the SBFD, A method, characterized in that the second reference frequency is determined based on a PRB having the lowest index in an active uplink bandwidth part (BWP) for the UE.

8. In paragraph 6, A method characterized in that the UE determines the additional RO by using the second frequency offset included in the first RACH configuration as the first frequency offset.

9. In paragraph 1, A method characterized in that, based on the fact that the additional RO and the RO are set to overlap in a specific time resource within the first time resource, the UE determines that only the RO among the additional RO and the RO is valid.

10. In paragraph 1, A method characterized in that the UE performs SSB mapping for the additional RO with the same rules as the SSB mapping rules for the RO.

11. A non-transitory computer-readable storage medium recording commands for performing the method described in paragraph 1.

12. In UE (user equipment), RF (Radio Frequency) transmitter and receiver; and A processor connected to the RF transceiver, A UE in which the processor controls the RF transceiver to receive configuration information including information on a first time resource related to a Sub-band Full Duplex (SBFD), receives a first RACH configuration for a Random Access Channel Occasion (RO) and a second RACH configuration for an additional RO related to the SBFD, and transmits a Physical Random Access Channel (PRACH) based on at least one of the RO and the additional RO.

13. In a processing device that controls UE (user equipment), at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said UE: A processing device that receives configuration information including information on a first time resource related to a Sub-band Full Duplex (SBFD), receives a first RACH configuration for a Random Access Channel Occasion (RO) and a second RACH configuration for an additional RO related to the SBFD, and transmits a Physical Random Access Channel (PRACH) based on at least one of the RO and the additional RO.

14. In the method by the base station, A step of transmitting configuration information including information on a first time resource related to SBFD (Sub-band Full Duplex); A step of transmitting a first RACH configuration for a RO (Random Access Channel Occasion) and a second RACH configuration for an additional RO associated with the SBFD; and A method comprising: receiving a PRACH (Physical Random Access Channel) based on at least one of the above RO and an additional RO.

15. At the base station, RF (Radio Frequency) transmitter and receiver; and A processor connected to the RF transceiver, A base station, wherein the processor controls the RF transceiver to transmit configuration information including information on a first time resource related to a Sub-band Full Duplex (SBFD), transmit a first RACH configuration for a Random Access Channel Occasion (RO) and a second RACH configuration for an additional RO related to the SBFD, and receive a Physical Random Access Channel (PRACH) based on at least one of the RO and the additional RO.

Images