Apparatus and method for configuring random access channel occasion supporting sub-band full duplex in wireless communication system

Abstract

The purpose of the present disclosure is to configure a physical random access channel occasion (RO) supporting sub-band full duplex (SBFD) in a wireless communication system, and a method may comprise the steps of: receiving a synchronization signal block (SSB) from a base station; receiving, from the base station, a system information block on the basis of the SSB; determining a plurality of ROs on the basis of the system information block; transmitting, to the base station, a preamble by using at least one RO among the plurality of ROs; and receiving, from the base station, a response message to the preamble.

Description

Device and method for establishing random access channel opportunities supporting sub-band full-duplex communication in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and more particularly, to an apparatus and method for establishing a physical random access channel occasion (RO) supporting sub-band full duplex (SBFD) communication in a wireless communication system.

[0002] Wireless access systems are widely deployed to provide various types of communication services, such as voice and data. Typically, wireless access systems are multiple access systems that support communications with multiple users by sharing available system resources (e.g., bandwidth, transmission power). 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), and single-carrier frequency division multiple access (SC-FDMA).

[0003] In particular, as numerous communication devices demand greater communication capacity, enhanced mobile broadband (eMBB) communication technologies are being proposed, improving upon existing radio access technology (RAT). Furthermore, communication systems that consider reliability and latency-sensitive services / user equipment (UE) as well as massive machine type communications (mMTC), which connects numerous devices and objects to provide diverse services anytime and anywhere, are being proposed. Various technological configurations are being proposed for these solutions.

[0004] The present disclosure relates to a device and method for establishing a physical random access channel occasion (RO) supporting sub-band full duplex (SBFD) communication in a wireless communication system.

[0005] The present disclosure relates to a device and method for individually setting a plurality of RO settings supporting SBFD to each terminal in a wireless communication system.

[0006] The present disclosure relates to a device and method for simultaneously setting multiple RO settings supporting SBFD to terminals in a wireless communication system.

[0007] The present disclosure relates to a device and method for determining parameters related to RO when SBFD slots and non-SBFD slots coexist in a wireless communication system.

[0008] The present disclosure relates to a device and method for determining an RO validation rule in a wireless communication system.

[0009] The present disclosure relates to a device and method for treating an RO as invalid when the RO overlaps with resources outside of a SBFD UL (uplink) subband in a frequency axis in a wireless communication system.

[0010] The present disclosure relates to a device and method for treating an RO as invalid when the RO overlaps with resources outside of UL usable physical resource blocks (PRBs) for SBFD operation in a frequency axis in a wireless communication system.

[0011] The present disclosure relates to a device and method for setting ROs to resources within SBFD UL subband frequency resources in a wireless communication system.

[0012] The present disclosure relates to a device and method for setting ROs to resources within UL available PRBs for SBFD operation in a wireless communication system.

[0013] The present disclosure relates to a device and method for setting the positions of ROs on the frequency axis in a wireless communication system based on the lowest PRB (physical resource block) of an UL subband of an SBFD slot.

[0014] The present disclosure relates to a device and method for setting the position of ROs on the frequency axis in a wireless communication system based on the lowest PRB of UL available PRBs for SBFD operation.

[0015] The present disclosure relates to a device and method for performing SSB (synchronization signal block)-to-RO mapping supporting SBFD RO in a wireless communication system.

[0016] The present disclosure relates to a device and method for preventing collision of RO configuration in an SBFD UL subband or an SBFD DL subband in a wireless communication system.

[0017] The present disclosure relates to a device and method for preventing collision of RO settings of UL available PRBs or DL ​​available PRBs for SBFD operation in a wireless communication system.

[0018] The present disclosure relates to a device and method for performing an initial connection procedure based on SBFD RO in a wireless communication system.

[0019] The technical objectives to be achieved in the present disclosure are not limited to those mentioned above, and other technical tasks not mentioned can be considered by a person having ordinary knowledge in the technical field to which the technical configuration of the present disclosure is applied from the embodiments of the present disclosure described below.

[0020] As an example of the present disclosure, a method includes the steps of receiving a synchronization signal block (SSB) from a base station, receiving a system information block from the base station based on the SSB, determining a plurality of physical random access channel occasions (ROs) based on the system information block, transmitting a preamble to the base station using at least one RO among the plurality of ROs, and receiving a response message to the preamble from the base station, wherein the plurality of ROs can be determined based on a slot pattern related to positions of a sub-band full duplex (SBFD) slot and a non-SBFD slot.

[0021] As an example of the present disclosure, the method includes the steps of receiving a synchronization signal block (SSB) from the base station, receiving a system information block from the base station based on the SSB, determining a plurality of physical random access channel occasions (ROs) based on the system information block, mapping the SSB to at least one RO, transmitting a preamble to the base station using the at least one RO, and receiving a response message to the preamble from the base station, wherein the mapping may be determined based on an association period or an association pattern period of each of separated RO configurations.

[0022] As an example of the present disclosure, a method includes the steps of generating configuration information related to a plurality of physical random access channel occasions (ROs), transmitting a synchronization signal block (SSB) to a terminal, transmitting a system information block including configuration information related to the RO to the terminal, receiving a preamble from the terminal using at least one RO among the plurality of ROs, and transmitting a response message to the preamble to the terminal, wherein the plurality of ROs can be determined based on a slot pattern related to positions of a sub-band full duplex (SBFD) slot and a non-SBFD slot.

[0023] As an example of the present disclosure, a device includes a transceiver and a processor connected to the transceiver, wherein the processor is configured to receive a synchronization signal block (SSB) from a base station, receive a system information block (SIB) from the base station based on the SSB, determine a plurality of physical random access channel occasions (ROs) based on the system information block, transmit a preamble to the base station using at least one of the SIBs, and receive a response message to the preamble from the base station, wherein the plurality of SIBs can be determined based on a slot pattern related to positions of a sub-band full duplex (SBFD) slot and a non-SBFD slot.

[0024] As an example of the present disclosure, a device includes a transceiver and a processor connected to the transceiver, wherein the processor is configured to receive a synchronization signal block (SSB) from the base station, receive a system information block (SIB) from the base station based on the SSB, determine a plurality of physical random access channel occasions (ROs) based on the SIB, perform mapping of the SSB to at least one RO, transmit a preamble to the base station using the at least one RO, and receive a response message for the preamble from the base station, wherein the mapping may be determined based on an association period or an association pattern period of each of separated RO configurations.

[0025] As an example of the present disclosure, a device includes a transceiver and a processor connected to the transceiver, wherein the processor is configured to generate configuration information related to a plurality of physical random access channel occasions (ROs), transmit a synchronization signal block (SSB) to a terminal, transmit a system information block including configuration information related to the RO to the terminal, receive a preamble from the terminal using at least one RO among the plurality of ROs, and transmit a response message to the preamble to the terminal, wherein the plurality of ROs can be determined based on a slot pattern related to positions of a sub-band full duplex (SBFD) slot and a non-SBFD slot.

[0026] As an example of the present disclosure, a terminal includes at least one processor, and at least one computer memory connected to the at least one processor and storing instructions that direct operations when executed by the at least one processor, the operations including: receiving a synchronization signal block (SSB) from a base station; receiving a system information block (SIB) from the base station based on the SSB; determining a plurality of physical random access channel occasions (ROs) based on the system information block; transmitting a preamble to the base station using at least one of the SIBs; and receiving a response message to the preamble from the base station, wherein the plurality of ROs can be determined based on a slot pattern related to positions of a sub-band full duplex (SBFD) slot and a non-SBFD slot.

[0027] As an example of the present disclosure, a non-transitory computer-readable medium storing at least one instruction includes at least one instruction executable by a processor, the at least one instruction instructing a device to receive a synchronization signal block (SSB) from a base station, receive a system information block (SYSB) from the base station based on the SSB, determine a plurality of physical random access channel occasions (ROs) based on the system information block, transmit a preamble to the base station using at least one of the ROs, and receive a response message to the preamble from the base station, wherein the plurality of ROs can be determined based on a slot pattern related to positions of a sub-band full duplex (SBFD) slot and a non-SBFD slot.

[0028] The above-described aspects of the present disclosure are only some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the present disclosure can be derived and understood by a person having ordinary skill in the art based on the detailed description of the present disclosure described below.

[0029] The following effects may be achieved by embodiments based on the present disclosure.

[0030] According to the present disclosure, it is possible to efficiently set up a physical random access channel opportunity supporting sub-band full-duplex communication.

[0031] The effects that can be obtained from the embodiments of the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly derived and understood by those skilled in the art to which the technical configuration of the present disclosure is applied, from the description of the embodiments of the present disclosure below. In other words, unintended effects resulting from implementing the configuration described in the present disclosure can also be derived from the embodiments of the present disclosure by those skilled in the art.

[0032] The accompanying drawings are intended to aid understanding of the present disclosure and, together with detailed descriptions, may provide embodiments of the present disclosure. However, the technical features of the present disclosure are not limited to specific drawings, and the features disclosed in each drawing may be combined with each other to form new embodiments. Reference numerals in each drawing may indicate structural elements.

[0033] FIG. 1 illustrates an example of signal transmission through physical channels according to an embodiment of the present disclosure.

[0034] FIG. 2 illustrates the structure of a radio frame of NR (New Radio) according to one embodiment of the present disclosure.

[0035] FIG. 3 illustrates a slot structure of an NR frame according to one embodiment of the present disclosure.

[0036] FIG. 4 illustrates the structure of a self-contained slot according to an embodiment of the present disclosure.

[0037] FIG. 5 illustrates an example of a method for applying full duplex in an intra-carrier according to an embodiment of the present disclosure.

[0038] FIG. 6A and FIG. 6B illustrate examples of a resource structure in which time resources operating in half duplex (HD) and time resources operating in full duplex (FD) coexist according to one embodiment of the present disclosure.

[0039] FIG. 7 illustrates an example of the location of a physical random access channel occasion (RO) on the time axis according to one embodiment of the present disclosure.

[0040] FIG. 8 and FIG. 9 illustrate examples of setting up an RO group according to one embodiment of the present disclosure.

[0041] FIG. 10 illustrates an example of a structure in which sub-band full duplex (SBFD) slots are allocated in the time and frequency axes according to one embodiment of the present disclosure.

[0042] FIG. 11 illustrates an example of a downlink slot to which an SBFD setting is applied according to one embodiment of the present disclosure.

[0043] FIG. 12 illustrates an example of a flexible slot with SBFD settings applied according to one embodiment of the present disclosure.

[0044] FIG. 13 illustrates an example of a RO configuration that does not consider SBFD UL subbands according to one embodiment of the present disclosure.

[0045] FIG. 14 illustrates an example of a multiple RO configuration according to one embodiment of the present disclosure.

[0046] FIG. 15 illustrates an example of a shared RO setting according to one embodiment of the present disclosure.

[0047] FIG. 16 illustrates an example in which SBFD according to one embodiment of the present disclosure is applied to a DL slot among resources consisting of a DL (downlink) slot and an UL (uplink) slot.

[0048] FIG. 17 illustrates an example in which SBFD according to one embodiment of the present disclosure is applied to all floating slots in a resource including floating slots.

[0049] FIG. 18 illustrates an example in which SBFD according to one embodiment of the present disclosure is applied to some DL slots or floating slots in a resource including floating slots.

[0050] FIG. 19 illustrates an example of setting an RO in a UL slot for a legacy UE and an SBFD-aware UE according to one embodiment of the present disclosure.

[0051] FIG. 20 illustrates an example of RO being set in a flexible slot and UL slot for a legacy UE and an SBFD-aware UE according to one embodiment of the present disclosure.

[0052] FIG. 21 illustrates an example in which RO is set using a portion of an SBFD slot, a floating slot, and a UL slot for a legacy UE and an SBFD-aware UE according to one embodiment of the present disclosure.

[0053] FIG. 22 illustrates an example of RO settings in a fluid slot according to one embodiment of the present disclosure.

[0054] FIG. 23 illustrates an example of classifying some overlapping ROs of a subband, SBFD DL subband, or SBFD UL subband as invalid ROs according to one embodiment of the present disclosure.

[0055] FIG. 24 illustrates an example in which RO is set in an SBFD symbol according to one embodiment of the present disclosure.

[0056] FIG. 25 illustrates an example of SSB-to-RO mapping according to one association period or association pattern period according to one embodiment of the present disclosure.

[0057] FIG. 26 illustrates an example of SSB-to-RO mapping according to another association period or association pattern period according to one embodiment of the present disclosure.

[0058] FIG. 27 illustrates an example of a procedure in which a terminal performs a random access procedure using ROs determined based on an SBFD slot according to one embodiment of the present disclosure.

[0059] FIG. 28 illustrates an example of a procedure in which a base station performs a random access procedure using ROs determined based on SBFD slots according to one embodiment of the present disclosure.

[0060] FIG. 29 illustrates an example of a procedure for performing a random access procedure using ROs determined based on SBFD slots according to one embodiment of the present disclosure.

[0061] FIG. 30 illustrates a block diagram showing components of a transmitting device and a receiving device according to one embodiment of the present disclosure.

[0062] FIG. 31 illustrates another example of a wireless device applicable to the present disclosure.

[0063] FIG. 32 illustrates an example of a signal processing module structure within a transmitting device applicable to the present disclosure.

[0064] FIG. 33 illustrates another example of a signal processing module structure within a transmitting device applicable to the present disclosure.

[0065] FIG. 34 illustrates an example of a wireless communication device applicable to the present disclosure.

[0066] Figure 35 illustrates an example of a communication system applicable to the present invention.

[0067] The following embodiments combine components and features of the present disclosure in a predetermined form. Each component or feature may be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, some components and / or features may be combined to form embodiments of the present disclosure. The order of operations described in the embodiments of the present disclosure 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.

[0068] In the description of the drawings, procedures or steps that may obscure the gist of the present disclosure are not described, and procedures or steps that can be understood by a person skilled in the art are also not described.

[0069] Throughout the specification, when a part is said to "comprising" (or including) a certain component, this does not mean that other components may be included, but rather that other components may be excluded, unless specifically stated otherwise. In addition, terms such as "...part," "...unit," and "module" described in the specification mean a unit that processes at least one function or operation, which may be implemented by hardware, software, or a combination of hardware and software. In addition, the words "a" or "an," "one," "the," and similar related words may be used in the context of describing the present disclosure (especially in the context of the claims below) to include both the singular and the plural, unless otherwise indicated herein or clearly contradicted by context.

[0070] Embodiments of the present disclosure described herein focus on the data transmission and reception relationship between a base station and a mobile station. Here, the base station is understood as a terminal node of a network that directly communicates with the mobile station. Certain operations described herein as being performed by the base station may, in some cases, be performed by an upper node of the base station.

[0071] That is, in a network consisting of multiple network nodes including a base station, various operations performed for communication with a mobile station may be performed by the base station or other network nodes other than the base station. In this case, the term 'base station' may be replaced by terms such as fixed station, Node B, eNB (eNode B), gNB (gNode B), ng-eNB, advanced base station (ABS), or access point.

[0072] Additionally, in the embodiments of the present disclosure, the term terminal may be replaced with terms such as user equipment (UE), mobile station (MS), subscriber station (SS), mobile subscriber station (MSS), mobile terminal, or advanced mobile station (AMS).

[0073] Additionally, a transmitter refers to a fixed and / or mobile node that provides data or voice services, and a receiver refers to a fixed and / or mobile node that receives data or voice services. Therefore, for uplink, a mobile station can be the transmitter, and a base station can be the receiver. Similarly, for downlink, a mobile station can be the receiver, and a base station can be the transmitter.

[0074] Embodiments of the present disclosure may be supported by standard documents disclosed in at least one of wireless access systems, such as IEEE 802.xx system, 3rd Generation Partnership Project (3GPP) system, 3GPP Long Term Evolution (LTE) system, 3GPP 5th generation (5G) NR (New Radio) system and 3GPP2 system, and in particular, embodiments of the present disclosure may be supported by 3GPP TS (technical specification) 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.321 and 3GPP TS 38.331 documents.

[0075] Furthermore, the embodiments of the present disclosure can be applied to other wireless access systems and are not limited to the systems described above. For example, they can be applied to systems implemented after the 3GPP 5G NR system and are not limited to a specific system.

[0076] That is, obvious steps or parts not described in the embodiments of the present disclosure can be explained by referring to the above documents. In addition, all terms disclosed in this document can be explained by the above standard documents.

[0077] Hereinafter, preferred embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to illustrate exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the technical configurations of the present disclosure may be implemented.

[0078] Additionally, specific terms used in the embodiments of the present disclosure are provided to aid in understanding of the present disclosure, and the use of such specific terms may be changed to other forms without departing from the technical spirit of the present disclosure.

[0079] The following technology can be applied to various wireless access 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).

[0080] For clarity, the following description is based on 3GPP communication systems (e.g., LTE, NR, etc.), but the technical spirit of the present disclosure is not limited thereto. LTE may refer to technology after 3GPP TS 36.xxx Release 8. Specifically, LTE technology after 3GPP TS 36.xxx Release 10 may be referred to as LTE-A, and LTE technology after 3GPP TS 36.xxx Release 13 may be referred to as LTE-A pro. 3GPP NR may refer to technology after TS 38.xxx Release 15. 3GPP 6G may refer to technology after TS Release 17 and / or Release 18. "xxx" refers to a standard document detail number. LTE / NR / 6G may be collectively referred to as a 3GPP system.

[0081] For background information, terms, abbreviations, etc. used in this disclosure, reference may be made to standard documents published prior to this disclosure. For example, reference may be made to standard documents 36.xxx and 38.xxx.

[0082] In this disclosure, “A or B” can mean “only A,” “only B,” or “both A and B.” In other words, “A or B” in this specification can be interpreted as “A and / or B.” For example, “A, B or C” in this specification can mean “only A,” “only B,” “only C,” or “any combination of A, B, and C.”

[0083] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0084] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0085] Additionally, in this specification, “at least one of A, B and C” can mean “only A,” “only B,” “only C,” or “any combination of A, B and C.” Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C.”

[0086] Additionally, parentheses used in this specification may mean “for example.” Specifically, when “control information (PDCCH)” is indicated, “PDCCH” may be suggested as an example of “control information.” In other words, “control information” in this specification is not limited to “PDCCH,” and “PDDCH” may be suggested as an example of “control information.” Additionally, even when indicated as “control information (i.e., PDCCH),” “PDCCH” may be suggested as an example of “control information.”

[0087] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.

[0088] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals / messages / fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0089] The effects that can be achieved through specific examples of this specification are not limited to the effects listed. For example, a person with ordinary skill in the relevant technical field may understand or derive various technical effects from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0090] FIG. 1 illustrates an example of signal transmission via physical channels according to an embodiment of the present disclosure. Referring to FIG. 1, 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 a base station. Specifically, the terminal receives a Primary Synchronization Channel (P-SCH) and a Secondary Synchronization Channel (S-SCH) from the base station, synchronizes with the base station, and obtains information such as a cell ID. Thereafter, the terminal can receive a Physical Broadcast Channel (PBCH) signal from the base station to obtain broadcast information within the cell. Meanwhile, the terminal can check the downlink channel status by receiving a Downlink Reference Signal (DL RS) during the initial cell search phase.

[0091] After completing initial cell search, the terminal performs system information reception (SIR). By receiving the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Control Channel (PDSCH) based on the PDCCH information, the terminal can obtain more specific system information.

[0092] Thereafter, the terminal may perform a random access procedure to complete connection to the base station. To this end, the terminal may transmit a preamble via the Physical Random Access Channel (PRACH) and receive a random access response (RAR) to the preamble via the Physical Downlink Shared Channel (PDCCH) and its corresponding PDSCH. The terminal may transmit a Physical Uplink Shared Channel (PUSCH) using scheduling information in the RAR and perform a contention resolution procedure, such as receiving a PDCCH signal and its corresponding PDSCH signal.

[0093] Meanwhile, if the random access process is performed in two steps, the terminal's preamble transmission and PUSCH transmission can be performed in one operation, and the base station's RAR transmission and PDSCH transmission can be performed in one operation.

[0094] Thereafter, the terminal may perform reception of a PDCCH signal and / or a PDSCH signal, reception of a PUSCH signal and / or transmission of a PUCCH signal as a general uplink / downlink signal transmission procedure.

[0095] The control information transmitted by a terminal to a base station is referred to as uplink control information (UCI). UCI includes information such as Hybrid Automatic Repeat and Request Acknowledgement / Negative-ACK (HARQ-ACK / NACK), Scheduling Request (SR), Channel Quality Indication (CQI), Precoding Matrix Indication (PMI), and Rank Indication (RI). UCI is typically transmitted periodically over the PUCCH, but can also be transmitted over the PUSCH if control information and data must be transmitted simultaneously. Additionally, a terminal can transmit UCI aperiodically over the PUSCH upon request / instruction from the network.

[0096] Wireless Resource Structure

[0097] FIG. 2 illustrates the structure of a radio frame of NR according to an embodiment of the present disclosure. The embodiment of FIG. 2 can be combined with various embodiments of the present disclosure. Referring to FIG. 2, a radio frame 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 in a sub-frame can be determined according to the Subcarrier Spacing (SCS). Each slot can include 12 or 14 OFDM (A) symbols depending on the cyclic prefix (CP).

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

[0099] When normal CP is used, the number of symbols per slot (N) depends on the SCS setting (u). slot symb ), number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe,u slot ) can be changed. For example, SCS(=15*2 μ ), N slot symb, N frame,μ slot, N subframe,μ slot is 15KHz, 14, 10, 1 when u=0, 30KHz, 14, 20, 2 when u=1, 60KHz, 14, 40, 4 when u=2, 120KHz, 14, 80, 8 when u=3, and 240KHz, 14, 160, 16 when u=4. In contrast, when extended CP is used, SCS(=15*2 μ ), N slot symb, N frame,μ slot, N subframe,μ slotIn the case of u=2, it can be 60KHz, 12, 40, 4. In the NR system, OFDM(A) numerology (e.g., SCS, CP length, etc.) can be set differently between multiple cells that are merged into one terminal. Accordingly, the (absolute time) section of a time resource (e.g., subframe, slot, or TTI) (conveniently referred to as TU (Time Unit)) consisting of the same number of symbols can be set differently between the merged cells.

[0100] In NR, multiple numerologies, or SCSs, can be supported to support various 5G services. For example, a 15 kHz SCS can support wide areas in traditional cellular bands, while a 30 kHz / 60 kHz SCS can support dense urban areas, lower latency, and wider carrier bandwidth. A 60 kHz or higher SCS can support bandwidths greater than 24.25 GHz to overcome phase noise.

[0101] 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, for example, the corresponding frequency ranges for FR1 and FR2 can be 450MHz-6000MHz and 24250MHz-52600MHz, respectively. In addition, the supported SCS can be 15, 30, 60kHz for FR1, and 60, 120, 240kHz for FR2. Among the frequency ranges used in the NR system, FR1 can mean the "sub 6GHz range", and FR2 can mean the "above 6GHz range" and can be called millimeter wave (mmW).

[0102] As described above, the numerical value of the frequency range of the NR system can be changed. For example, compared to the frequency range example described above, FR1 can be defined as including the band from 410 MHz to 7125 MHz. That is, FR1 can include frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency bands above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 can include unlicensed bands. Unlicensed bands can be used for various purposes, such as for vehicular communications (e.g., autonomous driving).

[0103] FIG. 3 illustrates a slot structure of an NR frame according to an embodiment of the present disclosure. The embodiment of FIG. 3 can be combined with various embodiments of the present disclosure. Referring to FIG. 3, a slot includes a plurality of 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.

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

[0105] FIG. 4 illustrates the structure of a self-contained slot according to an embodiment of the present disclosure. In an NR system, a frame is characterized by a self-contained structure in which a DL control channel, DL or UL data, and a UL control channel can all be included within a single slot. For example, the first N symbols within a slot can be used to transmit a DL control channel (hereinafter, referred to as a DL control region), and the last M symbols within a slot can be used to transmit a UL control channel (hereinafter, referred to as a UL control region). N and M are each integers greater than or equal to 0. A resource region (hereinafter, referred to as a data region) between the DL control region and the UL control region can be used for DL ​​data transmission or UL data transmission. As an example, the following configuration can be considered. Each section is listed in chronological order.

[0106] 1. DL only configuration

[0107] 2. UL only configuration

[0108] 3. Mixed UL-DL configuration

[0109] - DL area + GP (Guard Period) + UL control area

[0110] - DL control area + GP + UL area

[0111] * DL area: (i) DL data area, (ii) DL control area + DL data area

[0112] * UL domain: (i) UL data domain, (ii) UL data domain + UL control domain

[0113] In the DL control region, a PDCCH can be transmitted, and in the DL data region, a PDSCH can be transmitted. In the UL control region, a PUCCH can be transmitted, and in the UL data region, a PUSCH can be transmitted. In the PDCCH, DCI (Downlink Control Information), such as DL data scheduling information and UL data scheduling information, can be transmitted. In the PUCCH, UCI, such as ACK / NACK (Positive Acknowledgement / Negative Acknowledgement) information for DL ​​data, CSI (Channel State Information) information, SR (Scheduling Request), etc., can be transmitted. GP provides a time gap when a base station (BS) and a terminal switch from transmission mode to reception mode or when switching from reception mode to transmission mode. Some symbols at the time of switching from DL to UL within a subframe can be set to GP.

[0114] DAPS-HO (Dual active protocol stack based handover)

[0115] From a UE functional perspective, DAPS can generally be characterized as follows:

[0116] Transmitting action:

[0117] Transmitting action:

[0118] · Common SN;

[0119] · Individual header compression for source and target cells;

[0120] · Separate encryption for source and target cells.

[0121] Receiving action:

[0122] · Separate decryption for source and target cells;

[0123] · Individual header restoration for source and target cells;

[0124] · Common PDCP reordering;

[0125] · Sequential delivery and duplicate detection;

[0126] · Common buffer management.

[0127] In general, the network and UE share the same processes and functions for transmission and reception operations. The only difference is whether these functions reside in the same location. On the network side, all functions except DL PDCP SN allocation and UL PDCP reordering are performed separately at the source and target eNBs, so two PDCP entities are assumed, located at the source and target eNBs.

[0128] On the UE side, on the other hand, since all functions, including SN allocation and PDCP reordering, exist in the same location, all functions for DAPS on the UE side can be modeled as a single PDCP entity. For single UL data transmission, header compression and security processing are used for either the source eNB or the target eNB.

[0129] UE RF / Baseband Requirements

[0130] To minimize interruption, the UE must continue to transmit and receive data with the source cell when performing a random access procedure to the target cell, regardless of whether SAPS or DAPS is used. This is only possible if the UE supports simultaneous transmission and reception with both cells. According to RAN4's response LS, this works in most cases for UEs with Dual Rx / Dual Tx chains, and more restrictions are required for UEs with Dual Rx / Single Tx RF chains or Single Rx / Single Tx RF chains.

[0131] Additionally, functional division of the UE is necessary for effective use of baseband and RF resources. In SAPS, coordinating UE baseband and RF resources is not straightforward, resulting in additional interruptions and UE complexity.

[0132] For UEs with dual Rx / single Tx RF chains, simultaneous UL data transmission to both cells can be supported provided that certain requirements are met, such as the bandwidth of the source cell being larger than that of the target cell. Otherwise, a UL TDM pattern is required, which increases additional interruption time and UL switching complexity. However, this UE option provides a variety of UE implementations in terms of hardware and power efficiency for low-cost devices (e.g., UEs that do not support UL CA and / or UL MIMO).

[0133] For UEs with a single Rx / Tx RF chain, simultaneous transmission and reception can be supported if certain requirements are met. Otherwise, TDM design is required for both DL and UL, which increases complexity on both the UE and network sides. Additionally, RF chain switching is required for both DL and UL, which increases HO interruption time and switching complexity.

[0134] In general, solutions should be designed for all types of UE functions, rather than being limited to specific UE functions. Therefore, solutions should be considered based on Dual Rx / Dual Tx, with Dual Rx / Single Tx and Single Rx / Single Tx alternatives.

[0135] DAPS-HO according to TS 38.213 standard

[0136] When a UE indicates capability for DAPS HO, the UE may be provided with a source MCG and a target MCG.

[0137] When the UE is configured with MCG and SCG using NR radio access in FR1 and / or FR2, the maximum power P for transmission in MCG by p-DAPS-FR1 and / or p-DAPS-FR2 MCG and maximum power P for transmission in SCG SCG is set, and the inter-CG power sharing mode by UplinkPowerSharingDAPS-HO-mode for FR1 and / or FR2 is set. The UE determines the transmit power of MCG and SCG for each frequency band.

[0138] If the UE indicates UplinkPowerSharingDAPS-HO = Semi-static-mode1 and is provided with UplinkPowerSharingDAPS-HO-mode = Semi-static-mode1, the UE determines the transmit power for the target MCG or the source MCG by considering the target MCG as MCG and the source MCG as SCG, as described in Clause 7.6.2.

[0139] If the UE indicates UplinkPowerSharingDAPS-HO = Semi-static-mode2 and is provided with UplinkPowerSharingDAPS-HO-mode = Semi-static-mode2, the UE considers the target MCG as MCG and the source MCG as SCG and determines the transmit power for the target MCG or the source SCG as described in Clause 7.6.2.

[0140] When the UE indicates UplinkPowerSharingDAPS-HO = Dynamic and is provided with UplinkPowerSharingDAPS-HO-mode = Dynamic, the UE determines the transmit power for the target MCG or the source MCG by considering the target MCG as an MCG and the source MCG as an SCG, as described in Clause 7.6.2.

[0141] if

[0142] The UE does not provide UplinkPowerSharingDAPS-HO,

[0143] If transmissions from the target cell and the source cell overlap,

[0144] The UE transmits only in the target cell.

[0145] The following cases are considered to overlap transmissions between target and source cells:

[0146] When the carrier frequencies of the target MCG and the source MCG are within the same frequency (intra-frequency) and same band (intra-band), they are within overlapping time resources.

[0147] When the carrier frequencies of the target MCG and the source MCG are not the same frequency and the same band, and are within overlapping time resources and overlapping frequency resources.

[0148] For same-frequency DAPS HO operation, the UE expects the active DL BWP and active UL BWP of the target cell to be contained within the active DL BWP and active UL BWP of the source cell, respectively.

[0149] UE is targeting MCG A pdcch-BlindDetectionMCG1-UE can be provided to indicate the ability to monitor the maximum number of PDCCH candidates per slot corresponding to a downlink cell, for the source MCG. A pdcch-BlindDetectionMCG2-UE may be provided to indicate the ability to monitor the maximum number of PDCCH candidates per slot corresponding to a downlink cell. When a UE is provided with search space sets for both the target MCG and the source MCG, the UE expects that in no slot does it have a USS set that does not have a PDCCH candidate allocated for both the target MCG and the source MCG.

[0150] Full duplex operation for NR

[0151] 5G is giving rise to new service types, such as extended reality (XR), AI-based services, and self-driving cars. These services will experience dynamic traffic changes in both downlink and uplink directions, and low latency may be required for transmitted packets. In 5G services, traffic loads are expected to increase dramatically to support a variety of new use cases.

[0152] On the other hand, existing semi-static or dynamic TDD UL / DL configurations have limitations related to transmission delay and interference between operators. Furthermore, existing FDD schemes have limitations in terms of efficient frequency resource utilization in the DL / UL directions. Therefore, in NR, the introduction of full-duplex operation within a single carrier can be discussed to achieve low latency and efficient resource utilization.

[0153] FIG. 5 illustrates an example of a method for applying full duplex in an intra-carrier according to an embodiment of the present disclosure. Referring to FIG. 5, the structure in which DL and UL are allocated on the frequency axis of subband-wise full duplex (SB-FD) and spectrum-sharing full duplex (SS-FD) can be understood. In the case of SB-FD, transmission and reception of DL and UL are performed through different frequency resources within a single carrier. That is, DL and UL have different frequency resources for the same time resource. In the case of SS-FD, transmission and reception of DL and UL are performed through the same frequency resource or overlapping frequency resources within a single carrier. That is, DL and UL can have the same or overlapping frequency resources for the same time resource.

[0154] This full-duplex communication can be combined with existing half-duplex communication. In an existing half-duplex-based TDD communication environment, some time resources can be used for full-duplex communication. In some of the time resources used for full-duplex communication, SB-FD or SS-FD operations can be performed.

[0155] Figures 6a and 6b illustrate an example of a resource structure in which time resources operating in half duplex (HD) and full duplex (FD) coexist according to one embodiment of the present disclosure. In Figure 6a, some time resources are used for SB-FD-based communication, and the remaining time resources are used for HD-based communication. In Figure 6b, some time resources are used for SS-FD-based communication, and the remaining time resources are used for HD-based communication. Here, the time resources can be set in slots, symbols, subframes, or other similar time units.

[0156] In a time resource operating as SB-FD, some frequency resources are used as DL resources, and some frequency resources are used as UL resources. Hereinafter, for convenience of explanation, in the present disclosure, among the entire frequency resources in a time resource operating as FD, frequency resources operating as DL may be referred to as DL sub-bands, DL usable PRB(s), or DL ​​PRB(s), and frequency resources operating as UL may be referred to as UL sub-bands, UL usable PRB(s), or UL PRB(s).

[0157]

[0158] Base stations and terminals can perform full-duplex communication in various ways. For example, both the base station and the terminal can perform full-duplex operation. That is, both the base station and the terminal can simultaneously transmit and receive DL and UL using the same or different frequency resources in the same time resource. Alternatively, only the base station can perform full-duplex communication, while the terminal can perform half-duplex communication. In this case, the base station can simultaneously transmit and receive DL and UL using the same or different frequency resources in the same time resource, but the terminal performs only DL reception or UL transmission in a specific time resource. In this case, the base station performs full-duplex communication by simultaneously transmitting DL and receiving UL with different terminals.

[0159] For convenience of explanation, the following description assumes that the base station performs full-duplex communication and the terminal performs half-duplex communication. However, this is not limiting. For example, the methods described in this disclosure can be applied even when both the base station and the terminal perform full-duplex communication.

[0160] Below, the random access procedure of TS 38.213 document is described. The present disclosure proposes a method for setting up bandwidth part (BWP) resources for full-duplex communication between internal carriers based on the random access procedure described below.

[0161] RACH procedure (TS 38.213)

[0162] The physical random access procedure is triggered by a PRACH transmission request or PDCCH command from a higher layer. The higher layer settings for PRACH transmission include:

[0163] - Settings for PRACH transmission [4, TS 38.211].

[0164] - Preamble index, preamble SCS, P PRACH,target , the corresponding RA-RNTI, and PRACH resources.

[0165] PRACH is transmitted with the selected PRACH format and transmission power P as described in Clause 7.4 on the designated PRACH resources. PRACH,b,f,c(i) is transmitted using .

[0166] For a Type-1 random access procedure, the UE is provided with the number N of SS / PBCH block indices associated with one PRACH opportunity and the number R of contention-based preambles per SS / PBCH block index per valid PRACH opportunity by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0167] For Type-2 random access procedure (for commonly configured PRACH opportunities), the UE is provided with the number N of SS / PBCH block indices associated with a PRACH opportunity by ssb-perRACH-OccasionAndCB-PreamblesPerSSB and the number Q of contention-based preambles per SS / PBCH block index per valid PRACH opportunity by msgA-CB-PreamblesPerSSB-PerSharedRO. PRACH transmissions can be performed according to the PRACH mask index provided by msgA-SSB-SharedRO-MaskIndex in a subset of PRACH opportunities associated with the same SS / PBCH block index within a SSB-RO mapping period [11, TS 38.321].

[0168] For Type-2 random access procedure (for separately configured PRACH opportunities), the UE is provided with the number N of SS / PBCH block indices associated with a PRACH opportunity and the number R of contention-based preambles per SS / PBCH block index per valid PRACH opportunity, if provided by msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB, otherwise provided by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0169] For a Type-1 random access procedure or a Type-2 random access procedure using a PRACH opportunity set separately from a Type-1 random access procedure, if N<1, one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH opportunities, and the R contention-based preamble associated with the SS / PBCH block index per valid PRACH opportunity starts from preamble index 0. If N≥1, the R contention-based preamble associated with the SS / PBCH block index n (0≤n≤N-1) per valid PRACH opportunity starts from preamble index 0. Starting from here, is given by totalNumberOfRA-Preambles for type-1 random access procedures, or by msgA-TotalNumberOfRA-Preambles for type-2 random access procedures, and is a multiple of N.

[0170] For a type-2 random access procedure using a common PRACH opportunity, if N<1, one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH opportunities, and the Q contention-based preamble associated with the SS / PBCH block index per valid PRACH opportunity starts from the preamble index R. If N≥1, the Q contention-based preamble associated with the SS / PBCH block index n (0≤n≤N-1) per valid PRACH opportunity starts from the preamble index R. Starting from here, is provided by totalNumberOfRA-Preambles.

[0171] For link recovery, the UE is provided with N SS / PBCH block indices associated with one PRACH opportunity by ssb-perRACH-Occasion in BeamFailureRecoveryConfig. For dedicated RACH configurations provided by RACH-ConfigDedicated, if cfra is provided, the UE is provided with N SS / PBCH block indices associated with one PRACH opportunity by ssb-perRACH-Occasion in occasions. If N<1, one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH opportunities. If N≥1, all consecutive N SS / PBCH block indices are associated with one PRACH opportunity.

[0172] The SS / PBCH block indices are provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon and are mapped to valid PRACH opportunities in the following order according to the parameters described in [4, TS 38.211]:

[0173] - First, in ascending order of preamble index within a single PRACH opportunity.

[0174] - Second, in ascending order of frequency resource index of frequency multiplexing PRACH opportunities.

[0175] - Third, in ascending order of time resource index within the PRACH slot.

[0176] - Fourth, in ascending order of PRACH slot index.

[0177] The association period for mapping SS / PBCH block indices to PRACH opportunities starts from frame 0 and occurs at least once within the association period. The SS / PBCH block index is the smallest value in the set determined from the PRACH configuration period according to Table 8.1-1 so that it can be mapped to a PRACH opportunity. Here, the UE is obtained from the ssb-PositionsInBurst value of SIB1 or ServingCellConfigCommon. After an integer period of mapping SS / PBCH block indices to PRACH opportunities within the association period, If there is a PRACH opportunity or a PRACH preamble set that is not mapped to an SS / PBCH block index, the SS / PBCH block index is not mapped to the PRACH opportunity or PRACH preamble set. The association pattern period includes one or more association periods, and the pattern between the PRACH opportunity and the SS / PBCH block index is determined so that it repeats at most every 160 ms. Even after an integer number of association periods, PRACH opportunities that are not associated with an SS / PBCH block index are not used for PRACH transmission.

[0178] For PRACH transmissions triggered by a PDCCH command from a UE, the PRACH Mask Index field [5, TS 38.212] indicates the PRACH opportunity of the PRACH transmission in the PRACH opportunity associated with the SS / PBCH block index indicated by the SS / PBCH Block Index field of the PDCCH command, if the value of the Random Access Preamble Index field is not 0. The UE may select K by CellSpecific_Koffset. cell,offset If offered, the PRACH opportunity is slot n-2 of the UL BWP μ ·K cell,offset Here, n is the slot of UL BWP for PRACH transmission overlapping with the end of PDCCH command reception, μ is the SCS setting for PRACH transmission, and T TA Assume =0. If a PDCCH reception for a PDCCH command includes two PDCCH candidates from two related search space sets based on searchSpaceLinking, the last symbol of the PDCCH reception is the last symbol of the PDCCH candidate that ends later. The PDCCH reception includes both PDCCH candidates even if the UE does not need to monitor one of the two PDCCH candidates, as described in Clauses 10, 11.1, and 11.1.1.

[0179] For PRACH transmissions triggered by a request from a higher layer, if ssb-ResourceList is provided, the PRACH mask index is indicated by ra-ssb-OccasionMaskIndex, which indicates the PRACH opportunity of the PRACH transmission in the PRACH opportunity associated with the selected SS / PBCH block index.

[0180] PRACH opportunities are mapped sequentially for each SS / PBCH block index. The indexing of PRACH opportunities, indicated by the mask index value, is initialized at each mapping period of consecutive PRACH opportunities for each SS / PBCH block index. The UE selects a PRACH opportunity, indicated by the PRACH mask index value, for the SS / PBCH block index designated for PRACH transmission, from the first available mapping period.

[0181] For a given preamble index, the order of PRACH opportunities is as follows:

[0182] - First, in ascending order of frequency resource index of frequency multiplexing PRACH opportunities.

[0183] - Second, in ascending order of the time resource index of the time multiplexing PRACH opportunities within the PRACH slot.

[0184] - Third, in ascending order of the PRACH slot index.

[0185] For PRACH transmissions triggered by a request from a higher layer, if csirs-ResourceList is provided, the value of ra-OccasionList [12, TS 38.331] indicates the list of PRACH opportunities for PRACH transmission indicated by the selected CSI-RS index (csi-RS). The indexing of PRACH opportunities indicated by ra-OccasionList is initialized for each association pattern period.

[0186] [Table 1] below shows the mapping between the PRACH setup period and the PRACH opportunity association period in the SS / PBCH block.

[0187] PRACH configuration period (msec)Association period (number of PRACH configuration periods)10{1, 2, 4, 8, 16}20{1, 2, 4, 8}40{1, 2, 4}80{1, 2}160{1}

[0188] For paired spectrum or auxiliary uplink bands, all PRACH opportunities are valid.

[0189] For unpaired spectra:

[0190] If the UE is not provided with tdd-UL-DL-ConfigurationCommon, the PRACH opportunity within the PRACH slot does not precede the SS / PBCH block within the PRACH slot and is at least N after the last SS / PBCH block received symbol. gap Starting after the symbol, N gap is provided in Table 8.1-2. In addition, if channelAccessMode = "semiStatic" is provided, it must not overlap with a set of consecutive symbols before the start of the next channel occupancy time, in which case the UE does not perform a transmission [15, TS 37.213].

[0191] The candidate SS / PBCH block index of an SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon, as described in Section 4.1.

[0192] If the UE is provided with tdd-UL-DL-ConfigurationCommon, the PRACH opportunity within the PRACH slot is valid under the following conditions:

[0193] - within the UL symbol, or

[0194] - Not preceding the SS / PBCH block within the PRACH slot, and at least N blocks after the last downlink symbol. gap symbol, and at least N symbols after the last SS / PBCH block symbol. gap It must start after the symbol N gapis provided in Table 8.1-2. Additionally, if channelAccessMode = "semiStatic" is provided, it must not overlap with a set of consecutive symbols before the start of the next channel occupancy time, in which case no transmission shall be performed [15, TS 37.213].

[0195] - The candidate SS / PBCH block index of the SS / PBCH block corresponds to the SS / PBCH block index provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon, as described in Section 4.1.

[0196] For preamble format B4 [4, TS 38.211], N gap =0

[0197] Below [Table 2] shows N for preamble SCS(μ). gap Indicates a value.

[0198] Preamble SCS 1.25 kHz or 5 kHz015 kHz or 30 kHz or 60 kHz or 120 kHz2480 kHz8960 kHz16

[0199] When the random access procedure is initiated by a PDCCH command, if requested by the upper layer, the UE transmits a PRACH at the selected PRACH opportunity as described in [11, TS 38.321], and the time between the first symbol of the PRACH transmission and the last symbol of the PDCCH command reception is N. T,2 +△BWPSwitching+△ Delay + T switch It must be more than msec.

[0200] - N T,2 is the time corresponding to N2 symbols according to UE processing capability 1 [6, TS 38.214], and μ corresponds to the smaller SCS setting between the SCS setting of the PDCCH command and the SCS setting of the corresponding PRACH transmission.

[0201] - △BWPSwitching=0 is the case where the active UL BWP does not change, otherwise △BWPSwitching is defined in [10, TS 38.133].

[0202] - △ Delay =0.5 msec is for FR1, △ Delay =0.25 msec is for FR2.

[0203] - T switch is the switching gap duration defined in [6, TS 38.214].

[0204] For PRACH transmission using 1.25 kHz or 5 kHz SCS, the UE determines N2 assuming SCS setting μ=0.

[0205] For single-cell operation or carrier aggregation operation in the same frequency band, the UE shall not transmit PRACH and PUSCH / PUCCH / SRS within the same slot, or if the interval between the first or last symbol of a PRACH transmission in the first slot and the last or first symbol of a PUSCH / PUCCH / SRS transmission in the second slot is less than N symbols, respectively, where N=2 for μ=0 or μ=1, N=4 for μ=2 or μ=3, N=16 for μ=5, and N=32 for μ=6, where μ is the SCS setting of the active UL BWP. If the PUSCH transmission uses repetition type B, this condition applies to each actual repetition of the PUSCH transmission [6, TS 38.214].

[0206] Below are described examples of PRACH configuration tables used in the methods proposed by the present disclosure.

[0207] [Table 3] below shows examples of random access settings for FR1 and unpaired spectrum.

[0208] PRACHConfigurationIndexPreamble format Subframe numberStarting symbolNumber of PRACH slots within a subframe ,number of time-domain PRACH occasions within a PRACH slot ,PRACH durationxy0016190--0108190--0204190--0302090--0402190--0502040--0602140--0701090--0801080--0901070--01001060--01101050--01201040--01301030--01401020--0150101,600160101,67--0170104,90--0180103,80--0190102,70--0200108,90--0210104,8,90--0220103,4,90--0230107,8,90--0240103,4,8,90--0250106,7,8,90--0260101,4,6,90--0270101,3,5,7,90--028116170--02918170--03014170--03112070--03212170--03311070--034216160--03528160--03624160--03722067--03822167--03921067--040316190--04138190--04234190--04332090--04432190--04532040--04632140--04731090--04831080--04931070--05031060--05131050--05231040--05331030--05431020--0553101,60--0563101,67--0573104,90--0583103,80--0593102,70--0603108,90--0613104,8,90--0623103,4,90--0633107,8,90--0643103,4,8,90--0653101,4,6,90--0663101,3,5,7,90--067A11619026268A1819026269A1419016270A1219016271A1214,9713272A1217,9713273A1217,9016274A1218,9026275A1214,9026276A1212,3,4,7,8,9016277A1109026278A1109713279A1109016280A1108,9026281A1104,9016282A1107,9713283A1103,4,8,<h2 style=";text-align:left;direction:ltr">9016284A1103,4,8,9026285A1101,3,5,7,9016286A1100,1,2,3,4,5,6,7,8,9713287A21619023488A2819023489A2419013490A2217,9013491A2218 ,9023492A2217,9911493A2214,9911494A2214,9023495A2212,3,4,7,8,9013496A2102013497A2107013498A2219013499A21090234100A21099114101 A21090134102A2102,70134103A2108,90234104A2104,90134105A2107,99114106A2103,4,8,90134107A2103,4,8,90234108A2101,3,5,7,90134109 A2100,1,2,3,4,5,6,7,8,99114110A316190226111A38190226112A34190126113A3214,97116114A3217,97116115A3217,90126116A3214,90226117A3 218,90226118A3212,3,4,7,8,90126119A31020126120A31070126121A32190126122A31090226123A31097116124A31090126125A3102,70126126A310 8,90226127A3104,90126128A3107,97116129A3103,4,8,90126130A3103,4,8,90226131A3101,3,5,7,90126132A3100,1,2,3,4,5,6,7,8,97116133B 14192162134B12192162135B1217,92162136B1214,98132137B1214,92262138B11092262139B11098132140B11092162141B1108,92262142B1104,9216 2143B1107,98132144B1101,3,5,7,92162145B4161902112146B481902112 147B441921112148B421901112149B421921112150B4217,921112151B4214,921112152B4214,902112153B4218,902112154B4212,3,4,7,8,901112155B410101112156B410201112157B410401112158B410701112159B410901112160B410921112161B410902112162B4104,921112163B4107,921112164B4108,902112165B4103,4,8,921112166B4101,3,5,7,921112167B4100,1,2,3,4,5,6,7,8,902112168B4100,1,2,3,4,5,6,7,8,921112169C016192262170C08192262171C04192162172C02192162173C0218,92262174C0217,92162175C0217,98132176C0214,98132177C0214,92262178C0212,3,4,7,8,92162179C01092262180C01098132181C01092162182C0108,92262183C0104,92162184C0107,98132185C0103,4,8,92162186C0103,4,8,92262187C0101,3,5,7,92162188C0100,1,2,3,4,5,6,7,8,98132189C216192226190C28192226191C24192126192C22192126193C2218,92226194C2217,92126195C2217,98116196C2214,98116197C2214,92226198C2212,3,4,7,8,92126199C28198216200C24198116201C21092226202C21098116203C21092126204C2108,92226205C2104,92126206C2107,98116207C2103,4,8,92126208C2103,4,8,92226209C2101,3,5,7,92126210C2100,1,2,3,4,5,6,7,8,98116211A1 / B12192162212A1 / B1214,98132213A1 / B1217,98132214A1 / B1217,92162215A1 / B1214,92262216A1 / B1218,92262217A1 / B11092262218A1 / B11098132219A1 / B11092162220A1 / B1108,92262221A 1 / B1104,92162222A1 / B1107,98132223A1 / B1103,4,8,92262224A1 / B1101,3,5,7,92162225A1 / B1100,1,2,3,4,5,6,7,8,981 32226A2 / B22190134227A2 / B2214,96124228A2 / B2217,96124229A2 / B2214,90234230A2 / B2218,90234231A2 / B21090234232A2 / B21096124233A2 / B21090134234A2 / B2108,90234235A2 / B2104,90134236A2 / B2107,96124237A2 / B2103,4,8,90134238A2 / B2 103,4,8,90234239A2 / B2101,3,5,7,90134240A2 / B2100,1,2,3,4,5,6,7,8,96124241A3 / B32190126242A3 / B3214,92126243A 3 / B3217,90126244A3 / B3217,92126245A3 / B3214,90226246A3 / B3218,90226247A3 / B31090226248A3 / B31092126249A3 / B3109 0126250A3 / B3108,90226251A3 / B3104,90126252A3 / B3107,92126253A3 / B3103,4,8,90226254A3 / B3101,3,5,7,90126255A3 / B3100,1,2,3,4,5,6,7,8,92126256016170--025708170--025804170--025902070--026002170--026102020--026202120--0,

[0209] [Table 4] below shows examples of random access settings for FR2 and unpaired spectrum.

[0210] PRACHConfig.IndexPreamble format Slot numberStarting symbolNumber of PRACH slots within a 60 kHz slot ,number of time-domain PRACH occasions within a PRACH slot ,PRACH durationxy0A11614,9,14,19,24,29,34,3902621A11613,7,11,15,19,23,27,31,35,3901622A181,29,19,29,3902623A1814,9,14,19,24,29,34,3902624A1813,7,11,15,19,23,27,31,35,3901625A1414,9,14,19,24,29,34,3901626A1414,9,14,19,24,29,34,3902627A1413,7,11,15,19,23,27,31,35,3901628A1217,15,23,31,3902629A1214,9,14,19,24,29,34,39016210A1214,9,14,19,24,29,34,39026211A1213,7,11,15,19,23,27,31,35,39016212A11019,39713213A1103,5,7016214A11024,29,34,39713215A1109,19,29,39723216A11017,19,37,39016217A1109,19,29,39026218A1104,9,14,19,24,29,34,39016219A1104,9,14,19,24,29,34,39713220A1103,5,7,9,11,13713221A11023,27,31,35,39713222A1107,15,23,31,39016223A11023,27,31,35,39016224A11013,14,15, 29,30,31,37,38,39723225A1103,7,11,15,19,23,27,31,35,39713226A1103,7,11,15,19,23,27,31,35,39016227A1101,3,5,7,...,37,39016228A1100,1,2,...<h2 style=";text-align:left;direction:ltr">,39713229A21614,9,14,19,24,29,34,39023430A21613,7,11,15,19,23,27,31,35,39013431A2814,9,14,19,24,29,34,39023432A2813,7,11,1 5,19,23,27,31,35,39013433A281,29,19,29,39023434A2414,9,14,19,24,29,34,39013435A2414,9,14,19,24,29,34,39023436A2413,7,11,15,19,23,27,31,35,39013437A2217,15,23,31,39023438A2214,9,14,19,24,29,34,39013439A2214,9,14,19,24,29,34,39023440A2213,7,11,15 ,19,23,27,31,35,39013441A21019,39512442A2103,5,7013443A21024,29,34,39512444A2109,19,29,39522445A21017,19,37,39013446A2109, 19, 29, 39023447A2107,15,23,31,39013448A21023,27,31,35,39512449A21023,27,31,35,39013450A2103,5,7,9,11,13512451A2103,5,7,9,11,13013452A2104,9,14,19,24,29,34,39512453A2104,9,14,19,24,29,34,39013454A21013,14,15, 29,30,31,37,38,39522455A2103,7,11,15,19,23,27,31,35,39512456A2103,7,11,15,19,23,27,31,35,39013457A2101,3,5,7,...,37,39013458A2100,1,2,...<h2 style=";text-align:left;direction:ltr">,39512459A31614,9,14,19,24,29,34,39022660A31613,7,11,15,19,23,27,31,35,39012661A3814,9,14,19,24,29,34,39022662A3813,7,11,15,19,23,27,31,35,39012663A381,29,19,29,39022664A34 14,9,14,19,24,29,34,39012665A3414,9,14,19,24,29,34,39022666A3413,7,11,15,19,23,27,31,35,39012667A3214,9,14,19,24,29,34,39012668A3214,9,14,19,24,29,34,39022669A3213,7,11,15, 19, 23, 27, 31, 35, 39012670A31019, 39711671A3103, 5, 7012672A3109, 11, 13212673A31024, 29, 34, 39711674A3109, 19, 29, 39721675A31017, 19, 37, 39012676A3109, 19, 29, 39022677A3107, 15, 23, 31, 39012 678A31023,27,31,35,39711679A31023,27,31,35,39012680A3103,5,7,9,11,13012681A3103,5,7,9,11,13711682A3104,9,14,19,24,29,34,39012683A3104,9,14,19,24,29,34,39711684A31013,14,15, 29,30,31,37,38,39721685A3103,7,11,15,19,23,27,31,35,39711686A3103,7,11,15,19,23,27,31,35,39012687A3101,3,5,7,...,37,39012688A3100,1,2,...<h2 style=";text-align:left;direction:ltr">,39711689B11614,9,14,19,24,29,34,39226290B1814,9,14,19,24,29,34,39226291B181,29,19,29,39226292B1414,9,14,19,24,29,34,39226293B1214 ,9,14,19,24,29,34,39226294B1213,7,11,15,19,23,27,31,35,39216295B11019,39813296B1103,5,7216297B11024,29,34,39813298B1109,19,29,3982 3299B11017,19,37,392162100B1109,19,29,392262101B1107,15,23,31,392162102B11023,27,31,35,398132103B11023,27,31,35,392162104B1103,5,7 ,9,11,138132105B1104,9,14,19,24,29,34,398132106B1104,9,14,19,24,2 9,34,392162107B1103,7,11,15,19,23,27,31,35,398132108B11013,14,15, 29,30,31,37,38,398232109B1103,7,11,15,19,23,27,31,35,392162110B1101,3,5,7,...,37,392162111B1100,1,2,...,398132112B4161,24,9,14,19,24,29,34,3902112113B4161,23,7,11,15,19,23,27,31,35,3901112114B481,24,9,14,19,24,29,34,3902112115B481,23,7,11,15,19,23,27,31,35,3901112116B481,29,19,29,3902112117B4414,9,14,19,24,29,34,3901112118B4414,9,14,19,24,29,34,3902112119B441,23,7,11,15,19,23,27,31,35,3901112120B4217,15,23,31,3922112121B4214,9,14,19,24,29,34,3901112122B4214,9,14,19,24,29,34,3902112123B4213,7,11,15,19,23,27,31,35,3901112124B41019, 3922112125B41017, 19, 37, 3901112126B41024,29,34,3921112127B4109,19,29,3922112128B4109,19,29,3902112129B4107,15,23,31,3901112130B4107,15,23,31,3902112131B41023,27,31,35,3901112132B41023,27,31,35,3922112133B4109,11,13,15,17,1901112134B4103,5,7,9,11,1321112135B4104,9,14,19,24,29,34,3901112136B4104,9,14,19,24,29,34,3922112137B41013,14,15, 29,30,31,37,38,3922112138B4103,7,11,15,19,23,27,31,35,3901112139B4103,7,11,15,19,23,27,31,35,3921112140B4103, 5, 7, ..., 23,2521112141B4103, 5, 7, ..., 23,2502112142B4101,3,5,7,...,37,3901112143B4100, 1, 2,...<h2 style=";text-align:left;direction:ltr">, 3921112144C01614,9,14,19,24,29,34,390272145C01613,7,11,15,19,23,27,31,35,390172146C0814 ,9,14,19,24,29,34,390172147C0813,7,11,15,19,23,27,31,35,390172148C081,29,19,29,39027214 9C0414,9,14,19,24,29,34,390172150C0414,9,14,19,24,29,34,390272151C0413,7,11,15,19,23,27 ,31,35,390172152C0217,15,23,31,390272153C0214,9,14,19,24,29,34,390172154C0214,9,14,19,2 4, 29, 34, 390272155C0213, 7, 11, 15, 19, 23, 27, 31, 35, 390172156C01019, 398132157C0103, 5, 70172158C01024, 29, 34, 398132159C0109, 19, 29, 398232160C01017, 19, 37, 390172161C0109, 19, 29, 390272162C 01023,27,31,35,398132163C0107,15,23,31,390172164C01023,27,31,35,390172165C0103,5,7,9,11 ,138132166C0104,9,14,19,24,29,34,398132167C0104,9,14,19,24,29,34,390172168C01013,14,15, 29,30,31,37,38,398232169C0103,7,11,15,19,23,27,31,35,398132170C0103,7,11,15,19,23,27,31,35,390172171C0101,3,5,7,...,37,390172172C0100,1,2,...<h2 style=";text-align:left;direction:ltr">,398132173C21614,9,14,19,24,29,34,390226174C21613,7,11,15,19,23,27,31,35,390126175C2814,9,14,19,24,29,34,390226176C2813,7,11,15,19,23,27,31,35,390126177C281,29,19,29,39022617 8C2414,9,14,19,24,29,34,390126179C2414,9,14,19,24,29,34,390226180C2413,7,11,15,19,23,27 ,31,35,390126181C2217,15,23,31,392226182C2214,9,14,19,24,29,34,390126183C2214,9,14,19,2 4, 29, 34, 390226184C2213, 7, 11, 15, 19, 23, 27, 31, 35, 390126185C21019, 392126186C2103, 5, 70126187C21024, 29, 34, 397116188C2109, 19, 29, 397216189C21017, 19, 37, 390126190C2109, 19, 29, 392226191C 2107,15,23,31,392126192C2103,5,7,9,11,137116193C21023,27,31,35,397216194C21023,27,31,35,390126195C2104,9,14,19,24,29,34,397216196C2104,9,14,19,24,29,34,392126197C21013,14,15, 29,30,31,37,38,397216198C2103,7,11,15,19,23,27,31,35,397116199C2103,7, 11,15,19,23,27,31,35,390126200C2101,3,5,7,...,37,390126201C2100,1,2,...,397116202A1 / B11614,9,14,19,24,29,34,392162203A1 / B11613,7,11,15,19,23,27,31,35,392162204A1 / B1814,9,14,19,24,29,34,392162205A1 / B1813,7,11,15,19,23,27,31,35,392162206A1 / B1414,9,14,19,24,29,34,392162207A1 / B1413,7,11,15,19,23,27,31,35,392162208A1 / B1214,9,14,19,24,29,34,392162209A1 / B11019,398132210A1 / B1109,19,29,398132211A1 / B11017,19,37,392162212A1 / B1109,19,29,392262213A1 / B11023,27,31,35,398132214A1 / B1107,15,23,31,392162215A1 / B11023,27,31,35,392162216A1 / B1104,9,14,19,24,29,34,398132217A1 / B1104,9,14,19,24,29,34,392162218A1 / B1103,7,11,15,19,23,27,31,35,392162219A1 / B1101,3,5,7,...<h2 style=";text-align:left;direction:ltr">,37,392162220A2 / B21614,9,14,19,24,29,34,392134221A2 / B21613,7,11,15,19,23,27,31,35,392134222A2 / B2814,9,14,19,24,29,34,392134223A2 / B2813,7,11,15,19 ,23,27,31,35,392134224A2 / B2414,9,14,19,24,29,34,392134225A2 / B2413,7,11,15,19,23,27,31,35,392134226A2 / B2214,9,14,19,24,29,34,392134227A2 / B21019,396 124228A2 / B2109,19,29,396124229A2 / B21017,19,37,392134230A2 / B2109,19,29,392234231A2 / B21023,27,31,35,396124232A2 / B2107,15,23,31,392134233A2 / B21023,2 7,31,35,392134234A2 / B2104,9,14,19,24,29,34,396124235A2 / B2104,9,14,19,24,29,34,392134236A2 / B2103,7,11,15,19,23,27,31,35,392134237A2 / B2101,3,5,7,...,37,392134238A3 / B31614,9,14,19,24,29,34,392126239A3 / B31613,7,11,15,19,23,2 7,31,35,392126240A3 / B3814,9,14,19,24,29,34,392126241A3 / B3813,7,11,15,19,23 ,27,31,35,392126242A3 / B3414,9,14,19,24,29,34,392126243A3 / B3413,7,11,15,19, 23,27,31,35,392126244A3 / B3214,9,14,19,24,29,34,392126245A3 / B31019,39212624 6A3 / B3109,19,29,392126247A3 / B31017,19,37,392126248A3 / B3109,19,29,392226249 A3 / B3107,15,23,31,392126250A3 / B31023,27,31,35,392126251A3 / B31023,27,31,35, 392226252A3 / B3104,9,14,19,24,29,34,392126253A3 / B3104,9,14,19,24,29,34,3922 26254A3 / B3103,7,11,15,19,23,27,31,35,392126255A3 / B3101,3,5,7,...,37,392126.

[0211] Below [Table 5] shows the supported Δf RA and corresponding combinations of Δf It represents.

[0212] Δf RA for PRACHΔf for PUSCH allocation expressed in number of RBs for PUSCH 8391.2515678391.2530318391.2560213383951524128395301210839560671391515122139153062139156032139301524213930301221393060621396060122139601206213912060242139120120122139120480311391209602231394801204821394804801221394809 6062139960120962139960480242139960960122571301596257130304825713060242571120120482571120480121571120960747571480120192257148048048257148096024211511515961115115304811151156024111511201209761151120480252311511209601345

[0213] FIG. 7 illustrates an example of the location of a physical random access channel (RO) on the time axis according to one embodiment of the present disclosure. When the PRACH configuration index is 28, the location of the RO on the time axis may be set as shown in FIG. 7. An RO is allocated for each frame set to 40 slots, and three ROs may be set in each slot.

[0214] OFDM baseband signal generation for PRACH

[0215] Antenna port p time continuous signal for PRACH is defined as follows [Mathematical Formula 1].

[0216]

[0217] Here And,

[0218] - : provided by Section 6.3.3.

[0219] - △f RA is the subcarrier spacing of the initial uplink bandwidth portion during initial access. For non-initial access, △f RA is the subcarrier spacing of the active uplink bandwidth portion.

[0220] - μ0 is the largest μ value among the subcarrier spacing settings provided by the upper layer parameter scs-SpecificCarrierListscs.

[0221] is the resource block with the lowest number in the initial uplink bandwidth portion during initial access, and is determined by the upper layer parameter initialUplinkBWP. If it is not an initial access, is the resource block with the lowest number in the active uplink bandwidth portion, and is determined by the upper layer parameter BWP-Uplink.

[0222] - is the frequency offset of the lowest PRACH transmission opportunity in the frequency domain for physical resource block 0 of the active uplink bandwidth portion. is provided by the upper layer parameter msgA-RO-FrequencyStart, if a type-2 random access procedure has been started as described in Section 8.1 [5, TS 38.213]. Otherwise, it is provided by msg1-FrequencyStart as described in Section 8.1 [5, TS 38.213].

[0223] - n RA is the frequency domain PRACH transmission opportunity index at a given time instance for a particular PRACH transmission opportunity according to Section 6.3.3.2.

[0224] - is the number of occupied resource blocks, which is provided by the parameter allocation expressed in the number of resource blocks for PUSCH in Section 6.3.3.2-1.

[0225] - Is is the starting CRB index of the uplink RB set n corresponding to the quantity. The UE assumes that the RB set is defined if IntraCellGuardBandsPerSCS is not provided for the UL carrier as described in section 7 of [6, TS 38.214].

[0226] - n0 is is the index of the RB set containing the lowest PRACH transmission opportunity in the frequency domain indicated by . The UE It can be assumed that each PRACH transmission opportunity is set to be completely contained within the RB set.

[0227] - and is provided by Section 6.3.3.

[0228] - Here

[0229] - When,

[0230] - If , n is an interval Time instance 0 or time instance within this subframe is the number of times it overlaps.

[0231] Starting position of PRACH preamble is in the subframe or in the 60 kHz slot ( ) is provided by [Mathematical Formula 2].

[0232]

[0233] Here

[0234] - Assume that a subframe or 60 kHz slot starts at t=0.

[0235] - Timing advance value N TA =0 must be assumed.

[0236] - and is provided by Section 5.3.1.

[0237] - If kHz, we must assume μ=0, otherwise the value of μ is corresponds to kHz, and the symbol position l is is given as:

[0238] Here

[0239] - is provided by the "start symbol" parameter in Tables 6.3.3.2-2 through 6.3.3.2-4.

[0240] - is a PRACH transmission opportunity within a PRACH slot, starting from 0 within a RACH slot. -The numbers are numbered in ascending order from 1 to 1. Here is L RA When ∈{139,571,1151}, it is given by tables 6.3.3.2-2 to 6.3.3.2-4, and L RA When =839, it is fixed to 1.

[0241] - are provided by Tables 6.3.3.2-2 through 6.3.3.2-4.

[0242] - is given as follows:

[0243] - △f RA If ∈{1.25,5,15,60}kHz, =0.

[0244] - △f RA ∈{30,120}kHz, and the "Number of PRACH slots in a subframe" in Tables 6.3.3.2-2 to 6.3.3.2-3 or the "Number of PRACH slots in a 60 kHz slot" in Table 6.3.3.2-4 is 1. ; otherwise .

[0245] - if And:

[0246] - If the “Number of PRACH slots in 60 kHz slots” in Table 6.3.3.2-4 is 1, At kHz , △f RA =At 960kHz .

[0247] - If the “Number of PRACH slots in 60 kHz slots” in Table 6.3.3.2-4 is 2, At kHz , △f RA =At 960kHz .

[0248] If the preamble format provided in Tables 6.3.3.2-2 through 6.3.3.2-4 is A1 / B1, A2 / B2, or A3 / B3:

[0249] - In this case, the PRACH preamble is transmitted in the corresponding PRACH preamble format among B1, B2, and B3 at the PRACH transmission opportunity.

[0250] - Otherwise, the PRACH preamble is transmitted in the corresponding PRACH preamble format among A1, A2, and A3 at the PRACH transmission opportunity.

[0251] Supported , , Combination of parameters and The corresponding values ​​can be expressed as shown in [Table 6] below.

[0252] Δf RA for PRACHΔf for PUSCH , allocation expressed in number of RBs for PUSCH 8391.2515678391.2530318391.2560213383951524128395301210839560671391515122139153062139156032139301524213930301221393060621396060122139601206213912060242139120120122139120480311391209602231394801204821394804801221394809 6062139960120962139960480242139960960122571301596257130304825713060242571120120482571120480121571120960747571480120192257148048048257148096024211511515961115115304811151156024111511201209761151120480252311511209601345

[0253] PRACH repetition

[0254] In Rel-18, RO groups for PRACH repetition were introduced to improve coverage. When a base station sets and / or indicates a repetition number of N (e.g., 2, 4, 8), N valid ROs existing on the same frequency can be grouped in ascending order of their time domain indices to form an RO group. The remaining N-1 ROs can be located on the same frequency as the first RO, as shown in FIGS. 8 and 9. In other words, among valid ROs associated with the same beam, N ROs existing on the same frequency can be grouped into one RO group. Here, FIG. 8 illustrates RO groups when the number of repetitions is 4, the number of SSBs (synchronization signal blocks) is 2, the number of FDMed (frequency domain multiplexed) ROs is 4, and the number of SSBs per RO is 1 / 2, and FIG. 9 illustrates RO groups when the number of repetitions is 4, the number of SSBs is 3, the number of FDMed ROs is 4, and the number of SSBs per RO is 1.

[0255] When PRACH transmission is performed with preamble repetition, the time period starting from frame 0 is defined as the minimum integer number of associated pattern periods, for all set preamble repetitions within that time period. For each SS SS / PBCH block index, at least one valid PRACH opportunity set must be determined. For each configured preamble repetition count, the set of valid PRACH opportunities is repeated at the corresponding time period, where the time period is defined as the minimum integer number of association pattern periods. Here, the association pattern period can be configured as one or more association periods, and for each SSB index, an association pattern having at least one valid PRACH opportunity set is repeated at most every 160 ms.

[0256] The association period for mapping SS / PBCH block indices to PRACH opportunities starts from frame 0. The minimum integer value in the set determined by the PRACH setup period according to Table 8.1-2 (Section 3.5, RACH Procedure) such that the SS / PBCH block index is mapped to a PRACH opportunity at least once within the corresponding association period, where the UE is obtained from the ssb-PositionsInBurstssb-PositionsInBurstssb-PositionsInBurst value of SIB1 or ServingCellConfigCommon. The association pattern period includes one or more association periods, and the pattern between the PRACH opportunity and the SS / PBCH block index is determined to repeat at most every 160 ms.

[0257]

[0258] Specific embodiments of the present disclosure

[0259] The present disclosure proposes a technique for determining RO configurations that support sub-band full-duplex communication. Furthermore, the present disclosure proposes a technique for communicating RO configurations to UEs in a wireless communication system. Specifically, information related to RO configurations can be communicated to multiple UEs using common parameters based on shared RO configurations, or can be communicated to each of the multiple UEs using individual parameters based on individual RO configurations. Furthermore, the present disclosure proposes a technique for determining the validity of ROs when they collide. Specifically, RO validity rules can be defined such that existing RO configurations are set as default values ​​and additional ROs are configured for SBFD-aware UEs. Furthermore, ROs can be configured based on rules separate from existing rules.

[0260] TDD slot and / or symbol configuration can be determined in various ways. For example, the UE can receive an allocation for a cell-specific DL / UL pattern via tdd-UL-DL-ConfigurationCommon. As another example, the UE can receive a UE-specific allocation for resources that were left as flexible slots and / or symbols via a dedicated RRC signal, tdd-UL-DL-ConfigurationDedicated. tdd-UL-DL-ConfigurationCommon can be transmitted via SIB1 or dedicated RRC signaling. In order for a specific slot and / or symbol to be configured as a flexible slot and / or symbol, both must be configured flexibly via UE- and / or cell-specific slot configurations. Since tdd-UL-DL-ConfigurationDedicated is optional, the network may not configure slots and / or symbols UE-specifically. Therefore, in this case, a DL / UL pattern configured based on tdd-UL-DL-ConfigurationCommon can be used. At this time, if the UE does not receive the configuration of SlotFormatIndicator, the UE can receive PDSCH or CSI-RS in some or all symbols of the slot according to the indication of DCI format 1_0, DCI format 1_1, or DCI format 0_1. In addition, if the UE does not receive the configuration of SlotFormatIndicator, the UE can transmit PUSCH, PUCCH, PRACH, or SRS in some or all symbols of the slot according to the indication of DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, or DCI format 2_3.

[0261] In the configuration of RO, the base station may not configure RO in resources allocated in slot and / or symbol units for HD DL transmission, and the UE may not expect RO configuration. For resources allocated in HD flexible mode, RO configuration may be performed based on several constraints. For example, if RO is not configured through tdd-UL-DL-ConfigurationCommon, the PRACH occasion of the resource configured as the PRACH slot may not be located before the SS / PBCH block resource or may not be at least N times the last SS / PBCH block repetition symbol. gap If the PRACH opportunity is located after the number of symbols of , the corresponding PRACH opportunity can be treated as a valid RO. If tdd-UL-DL-ConfigurationCommon is set, the PRACH opportunity of a resource set to a UL symbol or a PRACH slot is not located before an SS / PBCH block resource, or is located after at least N symbols of the last SS / PBCH block repetition symbol. gap If it is located after the number of symbols of , the corresponding PRACH opportunity can be treated as a valid RO. In the present disclosure, an RO that cannot be used due to the aforementioned constraints is referred to as an invalid RO. Hereinafter, what is designated as a slot and / or symbol can also be interpreted as a unit of slot and symbol. In addition, what is designated as SBFD (sub-band full duplex) and / or non-SBFD can be understood as an SBFD slot / symbol and / or a non-SBFD slot / symbol.

[0262] FIG. 10 illustrates an example of a structure in which SBFD slots are allocated in the time and frequency axes according to an embodiment of the present disclosure. Referring to FIG. 10, when an SBFD configuration is applied to a resource set as a DL slot or a dynamic slot by a higher layer, some frequency resources of the SBFD slot may be set as DL, i.e., SBFD DL subbands, and some frequency resources may be set as UL, i.e., SBFD UL subbands. Here, a frequency gap may be set between the frequency resources of the SBFD DL subband and the frequency resources of the SBFD UL subband. Meanwhile, the direction of each SBFD subband may be indicated through a dynamic indication (e.g., DCI format 2_0 or SFI (slot format indicator)).

[0263] FIG. 11 illustrates an example of a downlink slot to which an SBFD setting is applied according to one embodiment of the present disclosure. In the following disclosure, an SBFD-aware UE (1110) may be understood to mean a terminal capable of performing SBFD operations, and a legacy UE may be understood to mean a terminal performing HD communication.

[0264] The legacy UE (1120) recognizes the allocated resources as DL resources. Therefore, the legacy UE (1110) does not expect RO configuration based on the existing rules. However, the SBFD-aware UE (1110) recognizes the allocated resources as SBFD resources, and therefore can expect RO configuration in the SBFD UL subband according to the new rules. The new rules view the SBFD symbol as a floating symbol, and specifically, this means that configuration is possible in both the UL direction and the DL direction in one symbol. In this case, the configured RO or RO group can only be used by the SBFD-aware UE (1110).

[0265] When the RO configuration index is determined by the base station, the RO may also be configured in the SBFD symbol configured for TDD as downlink. The RO may be located in the SBFD symbol and the non-SBFD symbol based on the parameters related to the RO configuration index. For the convenience of the following description, the RO in which both the legacy UE (1120) and the SBFD-aware UE (1110) can transmit PRACH is referred to as a legacy RO, and the RO in which only the SBFD-aware UE can transmit PRACH is referred to as an SBFD RO. The legacy UE (1120) determines the legacy RO(s) located in the non-SBFD symbol as a valid RO, and the SBFD-aware UE (1110) determines the legacy RO and the SBFD RO located in the non-SBFD symbol and the SBFD symbol as a valid RO(s). Since different valid RO(s) are set for each of the legacy UE (1120) and the SBFD-aware UE (1110), a new SSB-to-RO mapping rule must be defined.

[0266] FIG. 12 illustrates an example of a flexible slot with SBFD configuration applied according to an embodiment of the present disclosure. Since a legacy UE (1220) treats the resource as a flexible slot, it can determine the RO configuration based on existing rules and determine whether the RO is valid or invalid. On the other hand, an SBFD-aware UE (1210) recognizes the resource as an SBFD slot, and thus can expect an RO configuration in the SBFD UL subband according to the new rules. Since both the legacy UE (1220) and the SBFD-aware UE (1210) can use the resource, when an RO or an RO group is configured, the location of the time and frequency resources of the RO can be determined by considering SBFD and non-SBFD. For convenience of explanation, the configurations and methods applicable to the RO are described below, but the embodiments described below can be similarly applied to the RO group.

[0267] FIG. 13 illustrates an example of an RO configuration that does not consider an SBFD UL subband according to an embodiment of the present disclosure. In the case of an SBFD slot, an SBFD-aware UE can only use an RO allocated to an SBFD UL subband. As shown in FIG. 13, rules may be needed regarding how to configure and utilize an RO that overlaps a gap subband, an SBFD DL subband, or a portion of an SBFD UL subband. Furthermore, when the SBFD and RACH are configured semi-statically, the base station can determine an RO configuration that simultaneously considers legacy UEs and SBFD-aware UEs. In particular, a legacy UE may treat an SBFD symbol as a flexible symbol rather than an SBFD DL subband, and may determine that an RO can be configured for the flexible symbol. Therefore, an RO configuration that takes this into account is needed.

[0268] In an HD TDD environment, SBFD can be applied to some or all of the non-SBFD symbols configured as DL symbols and floating symbols. The new PRACH configurations that can be applied to the ROs of non-SBFD slots and the ROs of SBFD slots need to be distinguished from the legacy RO configurations that apply to HDs configured only as non-SBFD slots. This is because the existing ROs used by legacy UEs assume wideband UL as seen in non-SBFD slots, but SBFD-aware UEs assume SBFD UL subbands, not wideband UL, when using SBFD slots. ROs configured for resources other than SBFD UL subbands are treated as invalid ROs by SBFD-aware UEs. Even if SBFD is not applied to resources currently configured as HD UL, SBFD-aware UEs follow the existing method in utilizing the entire frequency resources of HD UL, so legacy ROs do not pose a problem to SBFD-aware UEs according to the rules applicable to non-SBFD. However, since slots containing configurable ROs in SBFD UL subbands can be used as DL and / or floating slots by legacy UEs, the behavior of legacy UEs needs to be taken into consideration.

[0269] A. RO setup and collision in SBFD DL subband

[0270] In the present disclosure, a legacy RO may be understood as a resource that can be used by legacy UEs and SBFD-aware UEs for PRACH transmission, and an SBFD-dedicated RO may be understood as a resource that can be used only by SBFD-aware UEs for PRACH transmission. As a method for setting a legacy RO and an SBFD-dedicated RO, the following two methods may be applied.

[0271] First, a method in which legacy RO and SBFD-dedicated RO are supported through separate RO configurations may be used. For this purpose, multiple RO configurations may be configured. In the present disclosure, a configuration in which multiple RO configurations are configured individually is referred to as a separated RO configuration. Fig. 14 illustrates an example of multiple RO configurations according to an embodiment of the present disclosure. Referring to Fig. 14, RO1 and RO2 based on the separated RO configuration may be configured at different frequencies. In another embodiment, RO1 and RO2 based on the separated RO configuration may be configured at the same frequency.

[0272] Second, a method in which legacy ROs and SBFD-only ROs are supported through a single RO configuration may be used. Hereinafter, a configuration in which legacy ROs and SBFD-only ROs are configured simultaneously is referred to as a shared RO configuration. FIG. 15 illustrates an example of a shared RO configuration according to an embodiment of the present disclosure. Referring to FIG. 15, the ROs of a non-SBFD slot and the ROs of an SBFD slot may be configured on the same frequency resource. Therefore, when a shared RO configuration is used, an SBFD-aware UE can be configured with the location of the RO together with a legacy UE.

[0273] SBFD-aware UEs can perform PRACH transmissions in ROs of SBFD slots and UL slots. Legacy UEs can perform PRACH transmissions in ROs of UL slots and flexible slots that can be used as SBFD slots or non-SBFD slots. In this case, either a separate RO configuration or a shared RO configuration may be used. If both schemes are supported, upper layer signaling may be performed to indicate which RO configuration is used. For example, information on which of the two RO configuration schemes to use may be conveyed via a message designed to convey information related to UL and / or DL ​​configuration (e.g., tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated). That is, information related to RO configuration may be conveyed together with the setting of whether SBFD is supported. In this case, if a specific setting value is not set, the separate RO configuration may be assumed as the default value. As another example, information regarding which RO configuration method to use may be indicated via RACH configuration for SBFD, which is independent of messages designed to convey information regarding the configuration of UL and / or DL. Specifically, information regarding which RO configuration method to use may be indicated via a new IE, such as rach-ConfigCommonSBFD-r19, in rach-ConfigCommon included in information regarding uplink BWP. rach-ConfigCommonSBFD-r19 may indicate or include a shared RO configuration and / or a separate RO configuration, and may include parameters, parameter groups for configuring the shared RO configuration and / or the separate RO configuration. Here, the parameter group may mean a set(s) of parameters related to the shared RO and / or the dedicated RO.For example, parameter group A may include a set of parameters that can be used in common by both shared ROs and dedicated ROs. Furthermore, parameter group B may include a set of parameters that can only be used by dedicated ROs. Furthermore, parameter group C may include a set of parameters that can only be used by shared ROs.

[0274] The network explicitly indicates whether RACH Configuration Option 1 for SBFD random access operation is enabled. Specifically, the BWP-UplinkCommon IE related to uplink BWP can be used to configure common parameters of the uplink BWP. The common parameters are "cell-specific," and the network ensures the necessary alignment with the corresponding parameters of other UEs. The common parameters for the initial bandwidth portion of the PCell are provided via system information. For all other serving cells, the network provides the common parameters via dedicated signaling. The BWP-UplinkCommon IE, which is information related to uplink BWP, can be defined as shown in [Table 7] below.

[0275] -- ASN1START-- TAG-BWP-UPLINKCOMMON-STARTBWP-UplinkCommon ::= SEQUENCE {genericParameters BWP,rach-ConfigCommon SetupRelease { RACH-ConfigCommon} OPTIONAL, -- Need Mpusch-ConfigCommon SetupRelease { PUSCH-ConfigCommon} OPTIONAL, -- Need Mpucch-ConfigCommon SetupRelease { PUCCH-ConfigCommon} OPTIONAL, -- Need M...,[[rach-ConfigCommonIAB-r16 SetupRelease { RACH-ConfigCommon} OPTIONAL, -- Need MuseInterlacePUCCH-PUSCH-r16 ENUMERATED {enabled} OPTIONAL, -- Need RmsgA-ConfigCommon-r16 SetupRelease { MsgA-ConfigCommon-r16} OPTIONAL -- Cond SpCellOnly2]],[[enableRA-PrioritizationForSlicing-r17 BOOLEAN OPTIONAL, -- Cond RAPrioSliceAIadditionalRACH-ConfigList-r17 SetupRelease { AdditionalRACH-ConfigList-r17} OPTIONAL, -- Cond SpCellOnly2rsrp-ThresholdMsg3-r17 RSRP-Range OPTIONAL, -- Need RnumberOfMsg3-RepetitionsList-r17 SEQUENCE (SIZE (4)) OF NumberOfMsg3-Repetitions-r17 OPTIONAL, -- Cond Msg3Repmcs-Msg3-Repetitions-r17 SEQUENCE (SIZE (8)) OF INTEGER (0..31) OPTIONAL -- Cond Msg3Rep]][[rach-ConfigCommonSBFD-ConfigList-r19 SetupRelease { rach-ConfigCommonSBFD-ConfigList-r19}...]]}AdditionalRACH-ConfigList-r17 ::= SEQUENCE (SIZE(1..maxAdditionalRACH-r17)) OF AdditionalRACH-Config-r17AdditionalRACH-Config-r17 ::= SEQUENCE {rach-ConfigCommon-r17 RACH-ConfigCommon OPTIONAL, -- Need RmsgA-ConfigCommon-r17 MsgA-ConfigCommon-r16 OPTIONAL, -- Need R...rach-ConfigCommonSBFD-r19 rach-ConfigCommonSBFD-r19}rach-ConfigCommonSBFD-r19 :: SEQUENCE {rach-ConfigCommon-Shared-r19rach-ConfigCommon-Separated-r19OrAdditionalRACH-ConfigList-r19 ::= SEQUENCE (SIZE(1..maxAdditionalRACH-r19)) OF AdditionalRACH-Config-r19AdditionalRACH-Config-r19 ::= SEQUENCE {rach-ConfigCommon-r19 RACH-ConfigCommon OPTIONAL, -- Need RmsgA-ConfigCommon-r19 MsgA-ConfigCommon-r19 OPTIONAL, -- Need R...}}NumberOfMsg3-Repetitions-r17::= ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16}-- TAG-BWP-UPLINKCOMMON-STOP-- ASN1STOP.

[0276] In case of 2-step RACH, RACH-ConfigCommonTwoStepRA may be defined to include or update parameters applicable to SBFD. For example, msgA-RO-FDM-r19 or msgA-RO-FrequencyStart-r19 may be set to values ​​related to SBFD UL subbands.

[0277] The MsgA-Config Common IE is used to configure PRACH and PUSCH resources for MsgA transmission in a two-step random access type procedure. Specifically, the MsgA-Config Common IE can be defined as shown in [Table 8] below.

[0278] -- ASN1START-- TAG-MSGACONFIGCOMMON-STARTMsgA-ConfigCommon-r19 ::= SEQUENCE {rach-ConfigCommonTwoStepRA-r19 RACH-ConfigCommonTwoStepRA-r19,msgA-PUSCH-Config-r19 MsgA-PUSCH-Config-r19 OPTIONAL --Cond InitialBWPConfig}-- TAG-MSGACONFIGCOMMON-STOP-- ASN1STOP

[0279] The RACH-Config CommonTwoStepRA IE is used to specify cell-specific two-step random access type parameters. Specifically, the RACH-Config CommonTwoStepRA IE can be defined as shown in [Table 9] below.

[0280] -- ASN1START-- TAG-RACH-CONFIGCOMMONTWOSTEPRA-STARTRACH-ConfigCommonTwoStepRA-r19 ::= SEQUENCE {rach-ConfigGenericTwoStepRA-r19 RACH-ConfigGenericTwoStepRA-r19,msgA-TotalNumberOfRA-Preambles-r16 INTEGER (1..63) OPTIONAL, -- Need SmsgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB-r19 CHOICE {oneEighth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},oneFourth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},oneHalf ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},one ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64},two ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32},four INTEGER (1..16),eight INTEGER (1..8),sixteen INTEGER (1..4)} OPTIONAL, -- Cond SBFDOnlymsgA-CB-PreamblesPerSSB-PerSharedRO-r16 INTEGER (1..60) OPTIONAL, -- Cond SharedROmsgA-SSB-SharedRO-MaskIndex-r16 INTEGER (1..15) OPTIONAL, -- Need SgroupB-ConfiguredTwoStepRA-r16 GroupB-ConfiguredTwoStepRA-r16 OPTIONAL, -- Need SmsgA-PRACH-RootSequenceIndex-r16 CHOICE {l839 INTEGER (0..837),l139 INTEGER (0..137),l571 INTEGER (0..569),l1151 INTEGER (0..1149)} OPTIONAL, -- Cond 2StepOnlymsgA-TransMax-r16 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL, -- Need RmsgA-RSRP-Threshold-r16 RSRP-Range OPTIONAL, -- Cond 2Step4StepmsgA-RSRP-ThresholdSSB-r16 RSRP-Range OPTIONAL, -- Need RmsgA-SubcarrierSpacing-r16 SubcarrierSpacing OPTIONAL, -- Cond 2StepOnlyL139msgA-RestrictedSetConfig-r16 ENUMERATED {unrestrictedSet, restrictedSetTypeA,restrictedSetTypeB} OPTIONAL, -- Cond 2StepOnlyra-PrioritizationForAccessIdentityTwoStep-r16 SEQUENCE {ra-Prioritization-r16 RA-Prioritization,ra-PrioritizationForAI-r16 BIT STRING (SIZE (2))} OPTIONAL, -- Cond InitialBWP-Onlyra-ContentionResolutionTimer-r16 ENUMERATED {sf8, sf16, sf24, sf32, sf40, sf48, sf56, sf64} OPTIONAL, -- Cond 2StepOnly...,[[ra-PrioritizationForSlicingTwoStep-r17 RA-PrioritizationForSlicing-r17 OPTIONAL, -- Cond InitialBWP-OnlyfeatureCombinationPreamblesList-r17 SEQUENCE (SIZE(1..maxFeatureCombPreamblesPerRACHResource-r17)) OF FeatureCombinationPreambles-r17 OPTIONAL -- Need R]]}GroupB-ConfiguredTwoStepRA-r16 ::= SEQUENCE {ra-MsgA-SizeGroupA ENUMERATED {b56, b144, b208, b256, b282, b480, b640, b800,b1000, b72, spare6, spare5, spare4, spare3, spare2, spare1},messagePowerOffsetGroupB ENUMERATED {minusinfinity, dB0, dB5, dB8, dB10, dB12, dB15, dB18},numberOfRA-PreamblesGroupA INTEGER (1..64)}-- TAG-RACH-CONFIGCOMMONTWOSTEPRA-STOP-- ASN1STOP.

[0281] The RACH-ConfigGenericTwoStepRA IE is used to specify two-step random access type parameters. Specifically, the RACH-ConfigGenericTwoStepRA IE can be defined as shown in [Table 10] below.

[0282] -- ASN1START-- TAG-RACH-CONFIGGENERICTWOSTEPRA-STARTRACH-ConfigGenericTwoStepRA-r19 ::= SEQUENCE {msgA-PRACH-ConfigurationIndex-r19 INTEGER (0..262) OPTIONAL, -- Cond SBFDOnlymsgA-RO-FDM-r19 ENUMERATED {one, two, four, eight} OPTIONAL, -- Cond SBFDOnlymsgA-RO-FrequencyStart-r19 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Cond SBFDOnlymsgA-ZeroCorrelationZoneConfig-r16 INTEGER (0..15) OPTIONAL, -- Cond 2StepOnlymsgA-PreamblePowerRampingStep-r19 ENUMERATED {dB0, dB2, dB4, dB6} OPTIONAL, -- Cond SBFDOnlymsgA-PreambleReceivedTargetPower-r19 INTEGER (-202..-60) OPTIONAL, -- Cond SBFDOnlymsgB-ResponseWindow-r16 ENUMERATED {sl1, sl2, sl4, sl8, sl10, sl20, sl40, sl80, sl160, sl320}OPTIONAL, -- Cond NoCFRApreambleTransMax-r16 ENUMERATED {n3, n4, n5, n6, n7, n8, n10, n20, n50, n100, n200} OPTIONAL, -- Cond 2StepOnlyNoCFRA...,[[msgB-ResponseWindow-v1700 ENUMERATED {sl240, sl640, sl960, sl1280, sl1920, sl2560} OPTIONAL -- Cond NoCFRA2]]}-- TAG-RACH-CONFIGGENERICTWOSTEPRA-STOP-- ASN1STOP.

[0283] Case 1-1: When SBFD is applied to DL slots

[0284] FIG. 16 illustrates an example in which SBFD, according to one embodiment of the present disclosure, is applied to a DL slot among resources consisting of a DL slot and an UL slot. In FIG. 16, a slot treated as an SBFD slot by an SBFD-aware UE is treated as a DL slot by a legacy UE. Referring to FIG. 16, the following four RO settings can be applied.

[0285] - When the shared RO setting is applied: The base station (e.g., gNB) configures RO only in UL slots that are non-SBFD slots according to the existing RO setting. This is because, from the perspective of the legacy UE, the SBFD slot is a DL slot, so if the SBFD slot and non-SBFD slot are configured based on the shared RO setting, the legacy UE cannot expect RO in the DL slot.

[0286] - When separate RO settings are applied: The base station sets the RO for SBFD-aware UEs in the SBFD slot and / or UL slot to RO setting 1, and sets the RO for legacy UEs in the UL slot to RO setting 2.

[0287] - If SBFD does not require RO for SBFD-aware UE: RO(s) can be configured with only shared RO configuration.

[0288] - When an SBFD-aware UE has UL latency or UL coverage issues: SBFD-dedicated ROs may be allocated to SBFD slots and / or UL slots based on separate RO configuration.

[0289] Case 1-2: When SBFD is applied to a floating slot

[0290] FIG. 17 illustrates an example in which SBFD is applied to all floating slots in a resource including floating slots according to one embodiment of the present disclosure. Slots treated as SBFD slots by SBFD-aware UEs are treated as floating slots by legacy UEs.

[0291] - When a shared RO configuration is applied: The base station (e.g., gNB) configures ROs for flexible slots and UL slots according to the existing RO configuration. Since the SBFD slot is treated as a flexible slot from the legacy UE's perspective, both SBFD slots and non-SBFD slots can be configured with the shared RO configuration. Here, it should be considered that, in the shared RO configuration, an SBFD-aware UE can perform PRACH transmission on the RO of the SBFD UL subband.

[0292] - When separate RO configurations are applied: The base station may set the RO for an SBFD-aware UE in an SBFD slot and / or an UL slot to RO configuration 2. The RO for a legacy UE in a flexible slot, i.e., an SBFD slot and / or an UL slot, may be set to RO configuration 1. At this time, for RO configuration 1 and RO configuration 2, the base station may set the RO only for the SBFD UL subband of the flexible slot, considering the SBFD-aware UE. However, if the RO according to RO configuration 1 overlaps with a resource outside of the SBFD UL subband, the SBFD-aware UE may follow the RO configuration of RO configuration 2.

[0293] - When the base station supports legacy UEs to perform PRACH transmission using only ROs allocated to non-SBFD slots: The base station sets all dynamic slots to DL before SBFD is applied. Afterwards, the RO settings can be set in the same way as Case 1-1, which is the case without dynamic slots. That is, through separate RO settings, SBFD-aware UEs can use both ROs allocated to SBFD slots and UL slots, while legacy UEs can use only ROs in UL slots.

[0294] Case 1-3: When SBFD is applied to some of the DL slots or floating slots.

[0295] Figure 18 illustrates an example in which SBFD is applied to some DL slots or flexible slots in a resource including flexible slots according to one embodiment of the present disclosure. In this case, slots treated as SBFD slots by SBFD-aware UEs are treated as DL slots or flexible slots by legacy UEs. Accordingly, the RO configuration can be configured by combining Case 1-1 and Case 1-2.

[0296]

[0297] The present disclosure below describes specific examples of shared RO configurations. Based on the shared RO configurations, SBFD-aware UEs and legacy UEs can receive the same RACH configurations and be provided with both legacy ROs and SBFD-specific ROs within the same RACH configuration.

[0298] For a SBFD-aware UE, both RACH configuration option 1, which uses a single RACH configuration and is based solely on existing parameters of the single RACH configuration, and RACH configuration option 2, which uses two separate RACH configurations, one existing RACH configuration and one additional RACH configuration, may be supported. In this case, only at least one parameter related to resource configuration may be used in common or partially reinterpreted, and at least one parameter related to each of the dedicated RO and the legacy RO, such as the PRACH transmit power parameter, may be given. However, activating both options simultaneously for a UE may not be supported.

[0299] For RACH configuration option 1, whether and how to reinterpret msg1-FrequencyStart in rach-ConfigCommon, RO validity rules, or SSB-to-RO mapping rules, etc. may be further studied. For option 2, RO validity rules, SSB-to-RO mapping rules, or whether all parameters currently included in rach-ConfigCommon need to be included in the additional RACH configuration may be further studied.

[0300] When the shared RO settings described in Case 1-1, Case 1-2, and Case 1-3 are applied, the RO validation rule can be defined as follows.

[0301] Case 2-1: When RO is configured using only UL slots for legacy UEs and SBFD-aware UEs with shared RO configuration.

[0302] FIG. 19 illustrates an example of setting ROs in UL slots for legacy UEs and SBFD-aware UEs according to one embodiment of the present disclosure. Referring to FIG. 19, since legacy UEs do not expect ROs in DL slots, RO settings can be set validly, as in Case 2-1-1 and Case 2-1-2. That is, since ROs exist in UL slots, as in Cases 2-1-1 and 2-1-2, they are all valid ROs, and no ROs are set in SBFD slots.

[0303] Case 2-2: When RO is configured using dynamic slots and UL slots for legacy UEs and SBFD-aware UEs with shared RO configuration.

[0304] FIG. 20 illustrates an example of setting ROs in flexible slots and UL slots for a legacy UE and an SBFD-aware UE according to an embodiment of the present disclosure. Referring to FIG. 20 , since a legacy UE expects ROs in flexible slots, RO settings such as Case 2-2-1 and Case 2-2-2 can be validly set.

[0305] All ROs configured as in Case 2-2-1 are valid because the SBFD UL subband frequency resources are taken into account. However, because the SBFD UL subband frequency is taken into account, the number of FDMed ROs in a UL slot may be limited. Consequently, UL coverage or latency issues may arise after SBFD is applied.

[0306] Since ROs configured as in Case 2-2-2 do not consider SBFD UL subband frequency resources, new validation rules may be applied to SBFD-capable UEs to determine which ROs are valid based on the SBFD subband location. A rule is needed regarding how to handle ROs that overlap with gap subbands, SBFD DL subbands, or parts of SBFD UL subbands. This rule is specifically described in the SSB-to-RO mapping technique below.

[0307] Case 2-3: When RO is configured using some of the SBFD slots, floating slots, and UL slots for legacy UEs and SBFD-aware UEs with shared RO configuration.

[0308] FIG. 21 illustrates an example of configuring RO using a portion of an SBFD slot, a flexible slot, and a UL slot for a legacy UE and an SBFD-aware UE according to an embodiment of the present disclosure. Referring to FIG. 21, since a legacy UE expects RO in a flexible slot, RO configurations such as Case 2-3-1 and Case 2-3-2 can be validly configured.

[0309] ROs configured as in Case 2-3-1 are all valid because they consider SBFD UL subband frequency resources. However, the number of FDMed ROs in a UL slot may be limited due to the consideration of flexible slots and / or SBFD UL subband frequencies. Consequently, UL coverage or latency issues may arise after SBFD is applied.

[0310] Since ROs configured as in Case 2-3-2 do not consider SBFD UL subband frequency resources, new validation rules may be applied to SBFD-capable UEs to determine which ROs are valid based on the SBFD subband location. A rule is needed regarding how to handle ROs that overlap with gap subbands, SBFD DL subbands, or parts of SBFD UL subbands. This rule is specifically described in the SSB-to-RO mapping technique.

[0311] The following describes a collision of SBFD DL subband or SBFD UL subband resources that may occur in Case 2-2-2 or Case 2-3-2 described above. The techniques related to resource collision described below are applicable not only to shared RO configurations but also to separate RO configurations. This is because even in the case of separate RO configurations, available ROs can be allocated to legacy UEs in SBFD slots.

[0312] Figure 22 illustrates an example of RO configuration in a flexible slot according to an embodiment of the present disclosure. A legacy UE can transmit a PRACH through the RO of a flexible slot because the SBFD slot recognized by the SBFD-aware UE is recognized as a flexible slot. Furthermore, the legacy UE expects that the slot with the RO configured is a TDD configuration or is not indicated as DL by SFI. The legacy UE does not receive DL signals and / or channels in the time resources of the slot with the RO configured. That is, the resource can be indicated as UL to the legacy UE, and even if the slot remains a flexible slot, the legacy UE performs UL operations. At the same time, the base station can use part or all of the resources assigned the RO for DL ​​or UL purposes for the SBFD-aware UE. Therefore, when a legacy UE transmits a PRACH, the base station must consider collisions. The rules related to collisions can be defined as follows.

[0313] - The base station does not perform DL transmission to an SBFD-aware UE on SBFD DL subband frequency resources that overlap with RO resources. That is, the SBFD-aware UE does not expect to receive DL channels and / or signals on those resources.

[0314] - SBFD-aware UEs do not perform UL transmissions on SBFD UL subband frequency resources that overlap with RO resources. That is, SBFD-aware UEs do not expect UL channel and / or signal transmissions on those resources. As a result, UL channels and / or signals and ROs are not allocated simultaneously within the same slot. Therefore, from the perspective of SBFD-aware UEs, additional RO drops may not occur.

[0315] RO location considering SBFD sub-band

[0316] In the aforementioned cases and various situations, the following two options can be considered when determining the RO location by considering the SBFD subband.

[0317] Option 1: When SBFD is applied, the starting position of the RO in the frequency domain and the number of FDMed ROs can be set based on the SBFD UL subband. The starting PRB of the lowest RO in the frequency domain can be determined as the lowest PRB of the SBFD UL subband + an offset. Therefore, if the offset value is 0, the starting PRB of the lowest RO in the frequency domain matches the lowest PRB of the SBFD UL subband. If there is no offset value, a default value (e.g., 0) can be used. If the lowest RO value in the frequency domain is not set, the lowest PRB of the SBFD UL subband can be defined as the default value. Here, the number of FDMed ROs can be defined such that the highest RO of the ROs set based on the lowest RO and the number of FDMed ROs matches the frequency resource boundary of the SBFD UL subband or exists within the frequency resource.

[0318] For RACH configuration option 1, one of the following alternatives may be selected to determine the lowest RO of the additional RO in the SBFD symbol.

[0319] - Alternative 1: Apply the msg1-FrequencyStart parameter of rach-ConfigCommon without reinterpretation.

[0320] - Alternative 2-1: Reinterpret the msg1-FrequencyStart parameter of rach-ConfigCommon as the frequency offset of the lowest RO in the frequency domain for the lowest PRB of UL available PRBs.

[0321] - Alternative 2-2: Use a fixed value (e.g. 0) as the frequency offset of the lowest RO in the frequency domain for the lowest PRB of the UL available PRBs.

[0322] - Alternative 2-3: The frequency offset of the lowest RO in the frequency domain for the lowest PRB of UL usable PRBs is set to mod(msg1-FrequencyStart, bandwidth of UL usable PRBs).

[0323] - Alternative 2-4: The frequency offset of the lowest RO in the frequency domain for the lowest PRB of the UL available PRBs is is set to . Here, the scaling factor is It means.

[0324] Here, ROs outside the UL-available PRB are invalid. Furthermore, the method for determining the lowest RO does not exclude other alternatives.

[0325] Option 2: When SBFD is applied, the SBFD UL subband size can be set based on the RO configuration. By defining the SBFD UL subband size as n times the PRB size occupied by the RO (e.g., 12, 24, 48, 96, etc.), the RO positions can be set so that as many ROs as possible can be included when SBFD is applied.

[0326] SSB-to-RO mapping technique

[0327] The base station may perform SSB-to-RO mapping to configure shared RO settings. When performing SSB-to-RO mapping, the base station may configure the beam directions of ROs available to SBFD-aware UEs to include the beam directions of ROs available to legacy UEs.

[0328] The existing SSB-to-RO mapping can be performed in the following four steps.

[0329] - Different SSB-to-RO mappings within a single RO

[0330] - SSB-to-RO mapping between multiplexed ROs with different frequency resources

[0331] - SSB-to-RO mapping between multiple ROs with different time resources

[0332] - Next PRACH slot

[0333] For SBFD-aware UEs, one single RACH configuration is used, and for RACH configuration option 1 based only on the existing parameters of the single RACH configuration, ROs can be configured as follows. For existing ROs, including non-SBFD symbols and ROs of SBFD symbols variably configured by tdd-UL-DL-ConfigurationCommon, the existing SSB-RO mapping is applied. For ROs of SBFD symbols configured for downlink by tdd-UL-DL-ConfigurationCommon, a separate SSB-RO mapping is used.

[0334] New rules may be considered for how to handle overlapping ROs in gap subbands, SBFD DL subbands, or SBFD UL subbands. Since the shared RO configuration applies a single common RO configuration to both legacy UEs and SBFD-aware UEs, the legacy SSB-to-RO mapping should be applied identically to valid ROs. Therefore, the same association period or association pattern period may be provided to both legacy UEs and SBFD-aware UEs. If the SBFD symbol is configured as a floating symbol and a downlink symbol in TDD, the existing legacy SSB-to-RO mapping may be applied.

[0335] Option 1: Classify ROs that overlap some subbands, SBFD DL subbands, or SBFD UL subbands as invalid ROs.

[0336] FIG. 23 illustrates an example of classifying some overlapping ROs of a subband, SBFD DL subband, or SBFD UL subband as invalid ROs according to an embodiment of the present disclosure. Referring to FIG. 23 , the number of valid ROs for legacy UEs and the number of valid ROs for SBFD-aware UEs may differ depending on the shared RO configuration. In this case, the same SSB-to-RO mapping cannot be supported for legacy UEs and SBFD-aware UEs. Therefore, the following rules may be used.

[0337] - Option 1-1: As in Case 2-2-1 of Figure 20, ROs in SBFD slots are always set to be located in the SBFD UL subband. In this case, since there are no invalid ROs, legacy UEs and SBFD-aware UEs are given the same number and location of ROs.

[0338] - Option 1-2: As shown in Figure 16, the SBFD slot is set to be applied only to the DL slot. The base station sets resources without a dynamic slot in the TDD configuration, or sets a dynamic slot to which SBFD is applied as a DL slot for legacy UEs.

[0339] Option 2: Restricting the behavior of SBFD-aware UEs

[0340] Overlapping ROs within a subband, SBFD DL subband, or SBFD UL subband are considered valid ROs, and SSB-to-RO mapping is performed. In this case, the existing SSB-to-RO mapping rules can be used as is. Accordingly, the following rules can be used.

[0341] - Option 2-1: An SBFD-aware UE can perform PRACH transmission by selecting only ROs located in the SBFD UL subband for PRACH transmission.

[0342] - Option 2-2: SBFD-aware UE drops ROs configured other than SBFD UL subbands.

[0343] Option 3: How ROs are mapped based on legacy UEs

[0344] Because legacy UEs and SBFD-aware UEs are assigned the same shared RO, it is important that the SSB-to-RO mapping is aligned. Therefore, SSB-to-RO mapping is performed first for legacy UEs, followed by validation of the SBFD-aware UE RO. Here, ROs are considered invalid if they overlap with guard bands, DL subbands, or partially overlap with UL subbands.

[0345] FIG. 24 illustrates an example of setting an RO in an SBFD symbol according to an embodiment of the present disclosure. In determining an RO setting index, the base station may determine that an RO can also be set in an SBFD symbol configured for downlink TDD. That is, an RO may be located in an SBFD symbol and a non-SBFD symbol based on a parameter associated with the signaled RO setting index. Here, a legacy UE determines a legacy RO located in a non-SBFD symbol as a valid RO, and an SBFD-aware UE determines a legacy RO and an SBFD RO located in a non-SBFD symbol and an SBFD symbol as a valid RO. Since different valid ROs are set for the legacy UE and the SBFD-aware UE, a new SSB-to-RO mapping rule must be defined. FIG. 25 illustrates an example of SSB-to-RO mapping according to one association period or association pattern period according to an embodiment of the present disclosure.

[0346] Option 3-1) SSB-to-RO mapping may be performed on a valid legacy RO where both legacy UEs and SBFD-aware UEs can transmit PRACH, and SSB-to-RO mapping may be performed on a valid SBFD RO where only SBFD-aware UEs can transmit PRACH. In this case, SSB-to-RO mapping may be performed based on common parameters for the legacy RO and SBFD RO.

[0347] Option 3-2) It can be assumed that the channel environments of non-SBFD symbols and SBFD symbols are different. SSB-to-RO mapping can be performed based on common parameters for valid legacy ROs where legacy UEs and SBFD-aware UEs can transmit PRACHs, and SSB-to-RO mapping can be performed based on additional parameters for valid SBFD ROs where only SBFD-aware UEs can transmit PRACHs.

[0348] For example, a part of the SSB-to-RO mapping given to a legacy RO can be used for the SSB-to-RO mapping applied to a SBFD RO. For example, if SSB_0 - SSB_(n-1) are mapped to the legacy ROs, SSB_0 / 2 / 4, SSB_1 / 3 / 5, SSB_0 to SSB_x, or SSB_x to SSB_(n-1) can be mapped to the SBFD ROs. At this time, the base station can consider beamforming considering power control applied to the SBFD symbol, etc. Here, the selected SSB index can be set or indicated by the base station (e.g., gNB). For example, if the mediumBitmap of ssb-PositionsInBurst is set to '11111111', the additional parameter can be set to '10101010' as ssb-PositionsInBurst_SBFD. Therefore, different association periods or association pattern periods may be provided to legacy UEs and SBFD-aware UEs.

[0349] If a legacy UE and an SBFD-aware UE are instructed or set to the same parameter for RO configuration, the legacy UE and the SBFD-aware UE may interpret one parameter differently based on implicit or explicit signaling. This may be applied to Option 3-2 described above.

[0350] For example, instead of separately providing ssb-perRACH-OccasionAndCB-PreamblesPerSSB and msg1-FDM values ​​for SBFD ROs only, a method may be used to reinterpret the given values ​​with respect to legacy ROs by predefined rules, base station instructions, or settings. The reinterpreted values ​​may be used for SSB-to-RO mapping applied to SBFD ROs. For example, if msg1-FDM for legacy ROs is given as X, msg1-FDM for SBFD ROs may be reinterpreted as floor(X / 2) or floor(X / n), etc. In this case, ROs may be configured to exist within the SBFD UL subband in the frequency domain.

[0351] As another example, assuming that part of the SSB-to-RO mapping given to a legacy RO is used for the SSB-to-RO mapping applied to a SBFD RO, based on the values ​​given to the legacy RO as ssb-PositionsInBurst (e.g., SSB_0 to SSB_(n-1)) by a predefined rule or an instruction or setting of the base station, SSB_0 / 2 / 4, SSB_1 / 3 / 5, SSB_0 to SSB_x or SSB_x to SSB_(n-1) etc. can be mapped to the SBFD RO.

[0352] As another example, the ssb-perRACH-OccasionAndCB-PreamblesPerSSB and msg1-FDM values ​​may be signaled separately for SBFD ROs only. That is, for SBFD ROs and legacy ROs, the RACH configuration is signaled uniformly, but the configuration for the association period or association pattern period may be signaled separately. In other words, first configuration information for the association period or association pattern period for SBFD ROs, i.e., additional ROs, and second configuration information for the association period or association pattern period for legacy ROs may be provided.

[0353] Option 3-3) Each SSB-to-RO mapping may be performed on the legacy RO and SBFD RO. At this time, the relationship between the first association period or the first association pattern period applied to the legacy RO and the second association period or the second association pattern period applied to the SBFD RO must be defined. Here, the legacy RO means the RO in the non-SBFD symbol and the RO in the SBFD symbol indicated as F, and the SBFD RO means the RO in the SBFD symbol indicated as downlink. The legacy association period starts from frame 0 and is defined as the minimum integer value in the set determined by the PRACH configuration period for mapping the SS / PBCH block index to the PRACH opportunity, and within the association period. An SS / PBCH block index is mapped to a PRACH opportunity at least once. The legacy SSB-to-RO mapping rule may be configured such that if a PRACH opportunity or a PRACH preamble set that is not mapped to an SS / PBCH block index exists even after an integer number of periods in which an SS / PBCH block index is mapped to a PRACH opportunity within an association period, the SS / PBCH block index is not mapped to the corresponding PRACH opportunity or PRACH preamble set.

[0354] Option 3-3-1) Two SSB-to-RO mappings can be defined as one association period or association pattern period. Legacy SSB-to-RO mapping is performed according to the association period or association pattern period of the legacy RO, and SBFD RO can perform SSB-to-RO mapping within the same association period or association pattern period. In this case, the SSB-to-RO mapping rule needs to be newly defined in a case such as Option 3-2-a of FIG. 25.

[0355] Option 3-3-2) Two SSB-to-RO mappings can be defined for each association period or association pattern period. SSB-to-RO mapping can be newly defined for ROs in SBFD symbols within the association period or association pattern period. Fig. 26 illustrates an example of SSB-to-RO mapping according to another association period or association pattern period according to an embodiment of the present disclosure. Referring to Fig. 26, in option 3-2-b, when performing SSB-to-RO mapping for an SBFD RO, an SBFD-aware UE is configured to follow the association period corresponding to the SBFD RO. At this time, extra ROs are dropped according to the legacy mapping rule. Here, the association period for the legacy RO can be determined as a multiple of the association period for the RO for the SBFD RO, as shown in Fig. 26.

[0356] The existing SSB-RO mapping rules are also reused for additional ROs. For RACH configuration option 2, the existing SSB-RO mapping rules are used for additional ROs configured by additional RACH configurations, separate from the SSB-RO mapping rules for existing ROs configured by existing RACH configurations. Whether and how to handle cases where legacy ROs and additional ROs overlap will be studied in future research.

[0357] When an RO group is formed, the RO group may include legacy ROs and SBFD ROs based on two SSB-to-RO mappings. PRACH repetition may be performed based on preamble partition. For example, preambles 0 to 31 may be used by legacy UEs, and preambles 32 to 63 may be used by SBFD-aware UEs. In this case, when PRACH repetition is performed, the legacy UE may perform PRACH repetition using only ROs in non-SBFD symbols using preambles 0 to 31. The SBFD-aware UE may perform PRACH repetition using both ROs in non-SBFD and SBFD symbols using preambles 32 to 63.

[0358] In relation to PRACH transmission using preamble repetition, a time period associated with PRACH repetition may be defined according to the RO type (e.g., legacy RO, dedicated RO, etc.). In this case, the time period may be determined based on the associated pattern period of each RO type. Accordingly, the UE may determine the time period for PRACH repetition based on the associated period or associated pattern period of the RO type to be used, and transmit the PRACH preamble based on the determined time period.

[0359] In other words, for a PRACH transmission with preamble repetitions, a time period starting from frame 0 may be the smallest integer number of association pattern periods such that at least one set of valid PRACH occasions for each of the SS / PBCH block indexes can be determined within the time period for all configured numbers of preamble repetitions. The set(s) of valid PRACH occasions for each configured number of preamble repetitions per RO type may repeat in every time period.

[0360] The present disclosure below describes operations of a terminal and a base station performing a random access procedure based on the various embodiments described above related to RO.

[0361] FIG. 27 illustrates an example of a terminal performing a random access procedure using ROs determined based on an SBFD slot according to an embodiment of the present disclosure. FIG. 27 illustrates a method performed by a terminal (e.g., an SBFD-aware UE (1110) of FIG. 11 and an SBFD-aware UE (1210) of FIG. 12). The terminal of FIG. 27 may be understood as an SBFD terminal capable of performing an SBFD operation. Conversely, a terminal that cannot perform an SBFD operation is referred to as a non-SBFD terminal. In FIG. 27, the ROs may be determined based on slot patterns associated with the positions of SBFD slots and non-SBFD slots.

[0362] Referring to Figure 27, in step S2701, the terminal receives a Synchronization Signal Block (SSB) from the base station. The SSB may include information to support synchronization and connection of the base station. Based on the synchronization signal included in the SSB, the terminal can obtain frequency resource and time information of the base station. The terminal can obtain system information (e.g., MIB) included in the SSB and information related to other system information (e.g., system information block (SIB)).

[0363] In step S2703, the terminal receives a system information block (SIB) from the base station based on SSB. The SIB may include network configuration information, frequency allocation information, or parameters necessary for terminal operation. The SIB may also include RACH configuration information required for the RACH process. The RACH configuration information may include information related to radio access points (ROs).

[0364] In step S2705, the terminal determines a plurality of ROs based on the system information block. The terminal can receive configuration information for the plurality of ROs directly through parameters included in the system information block or by receiving another message based on the system information block. Here, the configuration information for the plurality of ROs can include at least one of first configuration information related to TDD, second configuration information related to SBFD, and third configuration information related to the RO. Through this, the terminal can determine a first RO group within an SBFD slot and a second RO group within a non-SBFD slot based on the configuration information for the plurality of ROs.

[0365] For example, a terminal can obtain information related to a slot pattern to which multiple ROs can be allocated (e.g., tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated). Here, the slot pattern can be configured as a combination of an uplink slot, a downlink slot, a dynamic slot, or an SBFD slot. In this case, a non-SBFD terminal can be configured not to be assigned an SBFD slot. A slot treated as an SBFD slot to the terminal can be treated as a DL slot, a UL slot, or a dynamic slot to the non-SBFD terminal. Accordingly, ROs can be configured based on different slot patterns handled by the terminal and the non-SBFD terminal. This configuration can be determined so that the same ROs are configured for all non-SBFD terminals and SBFD terminals through a shared RO configuration, or so that different ROs are configured for each terminal through a separate RO configuration. Information related to which RO configuration to use can be included in the RACH configuration information.

[0366] In step S2707, the terminal transmits a preamble using at least one RO among the plurality of ROs. The preamble may be transmitted through the RO corresponding to the received SSB. Here, the terminal may perform mapping of the SSB to at least one RO to determine the RO corresponding to the SSB. The SSB-to-RO mapping may be determined based on at least one of a slot pattern, a UL subband frequency, or a DL subband frequency, and may be performed according to various embodiments described above. According to one embodiment, the terminal may determine that only ROs existing within the UL subband frequency resources of the SBFD slot are valid, and perform mapping based on the valid ROs. As another example, the terminal may apply a part of the RO mapping applied to a non-SBFD terminal to the SBFD RO.

[0367] At step S2709, the terminal receives a response message (e.g., a random access response message or message 2) to the preamble from the base station. The response message may include additional information about the cell, and specifically, the response message may include at least one of a timing advance command, an uplink grant, and a temporary C-RNTI. Subsequently, although not illustrated in FIG. 27, the terminal may transmit or receive at least one other message (e.g., message 3, message 4, etc.) for random access with the base station.

[0368] Although it has been described in Figure 27 that the RACH configuration information includes information related to ROs, it is not limited thereto. Information related to ROs may be conveyed in a dedicated RRC message or a message of another layer.

[0369]

[0370] FIG. 28 illustrates an example of a base station performing a random access procedure using ROs determined based on an SBFD slot according to an embodiment of the present disclosure. FIG. 28 illustrates a method performed by a device included in a communication system. In the description referring to FIG. 28, the operating entity is referred to as the base station. In FIG. 28, the terminal refers to an SBFD terminal capable of performing an SBFD operation. In contrast, a terminal that cannot perform an SBFD operation is referred to as a non-SBFD terminal. In FIG. 28, the ROs can be determined based on slot patterns related to the positions of the SBFD slot and the non-SBFD slot.

[0371] Referring to FIG. 28, in step S2801, the base station generates configuration information related to ROs. The configuration information related to ROs may include information related to slot patterns or information related to SSB-to-RO mapping. Here, the base station may configure the terminal and non-SBFD terminals to handle different slot patterns. Accordingly, the base station may configure ROs. These configurations may be determined so that the same ROs are configured for all non-SBFD terminals and SBFD terminals through shared RO configurations, or so that different ROs are configured for each terminal through separate RO configurations. In addition, information related to the frequencies at which the ROs will be located, association periods, or association pattern periods may also be determined.

[0372] In step S2803, the base station transmits an SSB to the terminal. The SSB may contain information to support synchronization and connection of the base station. The base station can transmit system information (e.g., MIB) to the terminal via the SSB, and through this, information related to other system information (e.g., SIB) to the terminal.

[0373] In step S2805, the base station transmits to the terminal a system information block including configuration information related to the RO. Here, the base station can transmit the configuration information for the plurality of ROs directly through parameters included in the system information block or by transmitting another message obtainable based on the system information block. Here, the configuration information for the plurality of ROs can include at least one of first configuration information related to TDD, second configuration information related to SBFD, and third configuration information related to the RO. Through this, the terminal can determine a first RO group in an SBFD slot and a second RO group in a non-SBFD slot based on the configuration information for the plurality of ROs.

[0374]

[0375] In step S2807, the base station receives a preamble from the terminal using at least one RO. Since the preamble is transmitted through the RO corresponding to the received SSB, the base station can handle the SSB received by the terminal based on the RO in which the preamble was received. The base station can form a beam based on the handled SSB and transmit data.

[0376] In step S2809, the base station transmits a response message (e.g., a random access response message or message 2) to the terminal for the received preamble. The response message may include additional information about the cell, and specifically, may include at least one of a timing advance command, an uplink grant temporary C-RNTI, and the like. Subsequently, although not illustrated in FIG. 28, the base station may transmit or receive at least one other message (e.g., message 3, message 4, etc.) for random access with the terminal.

[0377] Although SBFD terminals are described in FIG. 28, the base station may perform additional configurations or operations to enable non-SBFD terminals to determine ROs using existing techniques regardless of the presence of SBFD terminals. For example, non-SBFD terminals may receive information related to the allocation of ROs included in UL slots or flexible slots. Accordingly, to enable non-SBFD terminals and SBFD terminals to seamlessly transmit PRACHs, the base station may consider SBFD subbands to determine RO locations, or may configure some ROs to be classified as invalid.

[0378]

[0379] FIG. 29 illustrates an example of signaling for performing a random access procedure using ROs determined based on SBFD slots according to one embodiment of the present disclosure. In FIG. 29, a UE operating in HD is referred to as a legacy UE (2920), and a UE operating in SBFD is referred to as an SBFD-aware UE (2930). Referring to FIG. 29, UEs with different RO configurations can perform a random access procedure without collision.

[0380] In step S2901, the base station (2910) transmits SSBs to the legacy UE (2920) and the SBFD-aware UE (2930). The legacy UE (2920) and the SBFD-aware UE (2930) may receive some of the SSBs. In the following, it is assumed that the legacy UE (2920) receives the first SSB, and the SBFD-aware UE (2930) receives the second SSB. The legacy UE (2920) and the SBFD-aware UE (2930) may obtain a MIB based on the received SSB, and may obtain information for receiving a SIB based on the MIB.

[0381] In step S2903, the base station (2910) transmits SIB1 to the legacy UE (2920) and the SBFD-aware UE (2930). SIB1 may include cell-related information and configuration information related to the communication system. SIB1 may be periodically transmitted within the cell via a broadcast channel (e.g., BCCH). SIB1 may include cell timing information, frequency information, random access configuration information, etc. The legacy UE (2920) may receive SIB1 after performing synchronization with the base station (2910) based on the first SSB.

[0382] In step S2905, the legacy UE (2920) transmits a preamble using the first RO to the base station (2910). The legacy UE (2920) can receive information related to the RO to determine the first RO. The information related to the RO can be included in SIB1 or delivered to the legacy UE (2920) via a separate message. The legacy UE (2920) can perform mapping of the first SSB to at least one RO to determine the RO corresponding to the first SSB, and determine the first RO corresponding to the first SSB.

[0383] In step S2907, the legacy UE (2920) receives a random access response from the base station (2910). After transmitting the preamble, the legacy UE (2920) may expect to receive a random access response within a specific time interval. The random access response may include a timing advance, a temporary cell-radio network temporary identifier (C-RNTI), and uplink resource allocation information.

[0384] In step S2909, the SBFD-aware UE (2930) transmits a preamble using the second RO to the base station (2910). The SBFD-aware UE (2930) may receive information related to the RO to determine the second RO. The information related to the RO may be included in SIB1 or may be delivered to the SBFD-aware UE (2930) via a separate message. The SBFD-aware UE (2930) may perform mapping of the second SSB to at least one RO to determine the RO corresponding to the second SSB, and may determine the second RO corresponding to the second SSB. At this time, the RO configuration for the SBFD-aware UE (2930) may be configured to avoid conflict with the RO configuration for the legacy UE (2920). For example, ROs may be set to be valid for a legacy UE (2920), and an SBFD-aware UE (2930) may be set to use only ROs that are valid for the SBFD-aware UE (2930) among the set ROs. Specifically, the SBFD-aware UE (2930) may treat only ROs that are all included within the UL subband frequency resources of the SBFD slot among the set ROs as valid ROs.

[0385] In step S2911, the SBFD-aware UE (2930) receives a random access response from the base station (2910). After transmitting the preamble, the SBFD-aware UE (2930) may expect to receive a random access response within a specific time interval. The random access response may include a timing advance, a temporary cell-radio network temporary identifier (C-RNTI), and uplink resource allocation information.

[0386] Using the aforementioned methods, communication can be simultaneously supported for both SBFD-capable terminals and non-SBFD-capable terminals. Furthermore, because conflicts between SBFD terminals and ROs for SBFD terminals can be resolved, operators can operate base stations appropriately for their communication purposes.

[0387] FIG. 30 illustrates a block diagram showing components of a transmission device (10) and a reception device (20) according to one embodiment of the present disclosure. Here, the transmission device and the reception device may each be a base station or a terminal.

[0388] The transmitting device (10) and the receiving device (20) may each include a transceiver (13, 23) capable of transmitting or receiving a wireless signal carrying information and / or data, signals, messages, etc., a memory (12, 22) storing various information related to communication within a wireless communication system, and a processor (11, 21) configured to control the memory (12, 22) and / or the transceiver (13, 23) and / or the transceiver (13, 23) by connecting to components such as the transceiver (13, 23) and the memory (12, 22) to control the components so that the device performs at least one of the embodiments of the present invention described above.

[0389] The memory (12, 22) can store a program for processing and controlling the processor (11, 21) and temporarily store input / output information. The memory (12, 22) can be utilized as a buffer.

[0390] The processor (11, 21) typically controls the overall operation of various modules in a transmitting device or a receiving device. In particular, the processor (11, 21) may perform various control functions for carrying out the present invention. The processor (11, 21) may also be called a controller, a microcontroller, a microprocessor, a microcomputer, etc. The processor (11, 21) may be implemented by hardware, firmware, software, or a combination thereof. When the present invention is implemented using hardware, ASICs (Application Specific Integrated Circuits) or DSPs (Digital Signal Processors), DSPDs (Digital Signal Processing Devices), PLDs (Programmable Logic Devices), FPGAs (Field Programmable Gate Arrays), etc. configured to carry out the present invention may be provided in the processor (11, 21). Meanwhile, when implementing the present invention using firmware or software, the firmware or software may be configured to include modules, procedures, or functions that perform the functions or operations of the present invention, and the firmware or software configured to perform the present invention may be provided in the processor (11, 21) or stored in the memory (12, 22) and driven by the processor (11, 21).

[0391] The processor (11) of the transmission device (10) can perform a predetermined coding and modulation on a signal and / or data to be transmitted externally and then transmit the same to the transceiver (13). For example, the processor (11) can generate a codeword by performing demultiplexing, channel coding, scrambling, modulation, etc. on a data string to be transmitted. The codeword can include information equivalent to a transport block, which is a data block provided by the MAC layer. One transport block (TB) can be encoded into one codeword. Each codeword can be transmitted to a receiving device through one or more layers. The transceiver (13) can include an oscillator for frequency up-converting. The transceiver (13) can include one or more transmission antennas.

[0392] The signal processing process of the receiving device (20) may be configured in reverse order to the signal processing process of the transmitting device (10). Under the control of the processor (21), the transceiver (23) of the receiving device (20) may receive a wireless signal transmitted by the transmitting device (10). The transceiver (23) may include one or more receiving antennas. The transceiver (23) may down-convert each signal received through the receiving antennas to restore it to a baseband signal. The transceiver (23) may include an oscillator for frequency down-conversion. The processor (21) may perform decoding and demodulation on the wireless signal received through the receiving antennas, thereby restoring data that the transmitting device (10) originally intended to transmit.

[0393] The transceiver (13, 23) may be equipped with one or more antennas. The antennas, under the control of the processor (11, 21), may perform a function of transmitting a signal processed by the transceiver (13, 23) to the outside or receiving a wireless signal from the outside and transmitting it to the transceiver (13, 23) according to one embodiment of the present invention. The antennas may also be referred to as antenna ports. Each antenna may correspond to one physical antenna or may be configured by a combination of more than one physical antenna element. The signal transmitted from each antenna cannot be further decomposed by the receiving device (20). A reference signal (RS) transmitted corresponding to a corresponding antenna defines the antenna from the perspective of a receiving device (20), and enables the receiving device (20) to estimate a channel for the antenna, regardless of whether the channel is a single wireless channel from a physical antenna or a composite channel from a plurality of physical antenna elements including the antenna. That is, the antenna may be defined such that a channel transmitting a symbol on the antenna can be derived from the channel transmitting another symbol on the same antenna. In the case of a transceiver supporting a multi-input multi-output (MIMO) function for transmitting and receiving data using a plurality of antennas, it may be connected to two or more antennas.

[0394] FIG. 31 illustrates another example of a wireless device applicable to the present disclosure.

[0395] According to FIG. 31, the wireless device may include at least one processor (102, 202), at least one memory (104, 204), at least one transceiver (106, 206), and one or more antennas (108, 208).

[0396] As a difference between the example of the wireless device described in FIG. 30 and the example of the wireless device in FIG. 31, in FIG. 30, the processor (102, 202) and the memory (104, 204) are separated, but in the example of FIG. 31, the memory (104, 204) is included in the processor (102, 202).

[0397] The device proposed in this disclosure may be implemented not only as a terminal but also as a chipset. Furthermore, the configuration proposed in this disclosure may be implemented as a Computer-Readable Medium (CRM).

[0398] FIG. 32 illustrates an example of a signal processing module structure within a transmission device (10) applicable to the present disclosure. Here, signal processing may be performed in a processor of a base station / terminal, such as the processor (11) of FIG. A.

[0399] Referring to FIG. 32, a transmission device (10) within a terminal or base station may include a scrambler (301), a modulator (302), a layer mapper (303), an antenna port mapper (304), a resource block mapper (305), and a signal generator (306).

[0400] A transmission device (10) can transmit one or more codewords. The coded bits within each codeword are scrambled by a scrambler (301) and transmitted on a physical channel. A codeword may also be referred to as a data string and may be equivalent to a transmission block, which is a data block provided by the MAC layer.

[0401] The scrambled bits are modulated into complex-valued modulation symbols by a modulator (302). The modulator (302) can modulate the scrambled bits according to a modulation scheme and arrange them into complex-valued modulation symbols that represent positions on a signal constellation. There is no limitation on the modulation scheme, and m-PSK (m-Phase Shift Keying) or m-QAM (m-Quadrature Amplitude Modulation) can be used to modulate the encoded data. The modulator may be referred to as a modulation mapper.

[0402] The complex modulation symbols may be mapped to one or more transmission layers by a layer mapper (303). The complex modulation symbols on each layer may be mapped by an antenna port mapper (304) for transmission on an antenna port.

[0403] The resource block mapper (305) can map the complex modulation symbol for each antenna port to an appropriate resource element within a virtual resource block (VRB) allocated for transmission. The resource block mapper can map the VRB to a physical resource block (PRB) according to an appropriate mapping scheme. The resource block mapper (305) can assign the complex modulation symbol for each antenna port to an appropriate subcarrier and multiplex it according to the user.

[0404] The signal generator (306) can generate a complex-valued time domain OFDM symbol signal by modulating a complex modulation symbol for each antenna port, i.e., an antenna-specific symbol, with a specific modulation method, for example, an Orthogonal Frequency Division Multiplexing (OFDM) method. The signal generator can perform an Inverse Fast Fourier Transform (IFFT) on the antenna-specific symbol, and a Cyclic Prefix (CP) can be inserted into the time domain symbol on which the IFFT is performed. The OFDM symbol is transmitted to a receiving device through each transmitting antenna through digital-to-analog conversion, frequency uplink conversion, etc. The signal generator can include an IFFT module, a CP inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc.

[0405] Fig. 33 illustrates another example of a signal processing module structure within a transmission device (10) applicable to the present disclosure. Here, signal processing may be performed in a processor of a terminal / base station, such as the processor (11) of Fig. A.

[0406] Referring to FIG. 33, a transmission device (10) in a terminal or base station may include a scrambler (401), a modulator (402), a layer mapper (403), a precoder (404), a resource block mapper (405), and a signal generator (406).

[0407] The transmission device (10) can transmit coded bits within a codeword through a physical channel after scrambling the coded bits within the codeword by a scrambler (401).

[0408] The scrambled bits are modulated into complex modulation symbols by a modulator (402). The modulator can modulate the scrambled bits according to a predetermined modulation scheme and arrange them into complex modulation symbols representing positions on a signal constellation. There is no limitation on the modulation scheme, and pi / 2-BPSK (pi / 2-Binary Phase Shift Keying), m-PSK (m-Phase Shift Keying), or m-QAM (m-Quadrature Amplitude Modulation) can be used to modulate the encoded data.

[0409] The above complex modulation symbol can be mapped to one or more transmission layers by the layer mapper (403).

[0410] The complex modulation symbols on each layer can be precoded by the precoder (404) for transmission on the antenna ports. Here, the precoder may perform precoding after performing transform precoding on the complex modulation symbols. Alternatively, the precoder may perform precoding without performing transform precoding. The precoder (404) may process the complex modulation symbols in a MIMO manner according to multiple transmission antennas to output antenna-specific symbols and distribute the antenna-specific symbols to the corresponding resource block mapper (405). The output z of the precoder (404) can be obtained by multiplying the output y of the layer mapper (403) by an N×M precoding matrix W. Here, N is the number of antenna ports and M is the number of layers.

[0411] The resource block mapper (405) maps the demodulation modulation symbol for each antenna port to the appropriate resource element within the virtual resource block allocated for transmission.

[0412] The resource block mapper (405) can assign complex modulation symbols to appropriate subcarriers and multiplex them according to the user.

[0413] The signal generator (406) can generate a complex-valued time domain OFDM (Orthogonal Frequency Division Multiplexing) symbol signal by modulating a complex modulation symbol with a specific modulation method, for example, OFDM. The signal generator (406) can perform an Inverse Fast Fourier Transform (IFFT) on an antenna-specific symbol, and a Cyclic Prefix (CP) can be inserted into the time domain symbol on which the IFFT has been performed. The OFDM symbol is transmitted to a receiving device through each transmitting antenna after going through digital-to-analog conversion, frequency upconversion, etc. The signal generator (406) can include an IFFT module, a CP inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc.

[0414] The signal processing process of the receiving device (20) may be configured in reverse order to the signal processing process of the transmitter. Specifically, the processor (21) of the transmitting device (10) performs decoding and demodulation on a wireless signal received externally through the antenna port(s) of the transceiver (23). The receiving device (20) may include a plurality of multiple receiving antennas, and each signal received through the receiving antenna is restored to a baseband signal and then multiplexed and MIMO demodulated to be restored to a data sequence that the transmitting device (10) originally intended to transmit. The receiving device (20) may include a signal restorer for restoring a received signal to a baseband signal, a multiplexer for combining and multiplexing received and processed signals, and a channel demodulator for demodulating the multiplexed signal sequence into a corresponding codeword. The signal restorer, the multiplexer, and the channel demodulator may be configured as an integrated module that performs their functions or as independent modules. More specifically, the signal restorer may include an analog-to-digital converter (ADC) that converts an analog signal into a digital signal, a CP remover that removes a CP from the digital signal, an FFT module that applies an FFT (fast Fourier transform) to a signal from which the CP has been removed to output a frequency domain symbol, and a resource element demapper / equalizer that restores the frequency domain symbol to an antenna-specific symbol. The antenna-specific symbol is restored to a transmission layer by a multiplexer, and the transmission layer is restored to a codeword that the transmitter intended to transmit by a channel demodulator.

[0415] FIG. 34 illustrates an example of a wireless communication device applicable to the present disclosure.

[0416] According to FIG. 34, a wireless communication device, for example, a terminal, may include at least one of a processor (2310) such as a digital signal processor (DSP) or a microprocessor, a transceiver (2335), a power management module (2305), an antenna (2340), a battery (2355), a display (2315), a keypad (2320), a global positioning system (GPS) chip (2360), a sensor (2365), a memory (2330), a subscriber identification module (SIM) card (2325), a speaker (2345), and a microphone (2350). There may be a plurality of antennas and processors.

[0417] The processor (2310) can implement the functions, procedures, and methods described in this specification. The processor (2310) of FIG. 34 may be the processor (11, 21) of FIG. A.

[0418] Memory (2330) is connected to the processor (2310) and stores information related to the processor's operation. The memory may be located internally or externally to the processor and may be connected to the processor via various technologies, such as wired or wireless connections. The memory (2330) of FIG. 34 may be the memory (12, 22) of FIG. A.

[0419] A user may input various types of information, such as a phone number, using various techniques, such as pressing buttons on a keypad (2320) or activating sound using a microphone (2350). The processor (2310) may receive and process the user's information and perform an appropriate function, such as dialing the entered phone number. In some scenarios, data may be retrieved from a SIM card (2325) or memory (2330) to perform the appropriate function. In some scenarios, the processor (2310) may display various types of information and data on a display (2315) for the user's convenience.

[0420] A transceiver (2335) is coupled to a processor (2310) and transmits and / or receives wireless signals, such as radio frequency (RF) signals. The processor may control the transceiver to initiate communication or transmit wireless signals containing various types of information or data, such as voice communication data. The transceiver includes a transmitter and a receiver for transmitting and receiving wireless signals. An antenna (2340) may facilitate the transmission and reception of wireless signals. In some implementations, upon receiving a wireless signal, the transceiver may forward and convert the signal to a baseband frequency for processing by the processor. The processed signal may be processed by various techniques, such as being converted into audible or readable information for output through a speaker (2345). The transceiver of FIG. 34 may be the transceiver (13, 23) of FIG. A.

[0421] Although not shown in FIG. 34, various components, such as a camera and a Universal Serial Bus (USB) port, may be additionally included in the terminal. For example, the camera may be connected to the processor (2310).

[0422] Fig. 34 is only one implementation example for a terminal, and the implementation examples are not limited thereto. The terminal does not necessarily have to include all the elements of Fig. 34. That is, some components, such as a keypad (2320), a Global Positioning System (GPS) chip (2360), a sensor (2365), a SIM card (2325), etc., may not be essential elements, and in this case, may not be included in the terminal.

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

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

[0425] Figure 35 shows an example of a communication system (1) that can be applied to the present invention.

[0426] Referring to FIG. 35, 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.

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

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

[0429] 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 are not explicitly cited in the scope of the patent may be combined to form an embodiment or may be incorporated as a new claim through a post-application amendment.

[0430] 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 self-evident that various operations performed for communication with a terminal in a network comprised of multiple network nodes including a base station may be performed by the base station or 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.

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

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

[0433] Meanwhile, although this specification describes embodiments of the present invention using LTE systems, LTE-A systems, and NR systems, these are examples and the embodiments of the present invention can be applied to any communication system corresponding to the above definition.

[0434] In addition, the specific operations described in this document as being performed by the base station 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 a plurality of network nodes including a base station may be performed by the base station or 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, and the name of the base station may be used as a comprehensive term including remote radio head (RRH), eNB, transmission point (TP), reception point (RP), and relay.

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

[0436] The proposed methods described above can be implemented independently, but they can also be implemented as a combination (or merge) of some of the proposed methods. Rules can be defined so that the base station notifies the terminal of the applicability of the proposed methods (or information about the rules of the proposed methods) through a predefined signal (e.g., a physical layer signal or a higher layer signal).

[0437] The present disclosure may be embodied in other specific forms without departing from the technical ideas and essential features described herein. Therefore, the above detailed description should not be construed as limiting in all respects but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present disclosure are intended to be included within the scope of the present disclosure. Furthermore, claims that are not explicitly cited in the claims may be combined to form an embodiment or incorporated into a new claim through a post-filing amendment.

[0438] Embodiments of the present disclosure can be applied to various wireless access systems. Examples of various wireless access systems include the 3rd Generation Partnership Project (3GPP) or 3GPP2 systems.

[0439] The embodiments of the present disclosure can be applied not only to the various wireless access systems described above, but also to all technical fields that utilize these various wireless access systems. Furthermore, the proposed method can also be applied to mmWave and THz communication systems utilizing ultra-high frequency bands.

[0440] Additionally, embodiments of the present disclosure can be applied to various applications such as autonomous vehicles and drones.

Claims

1. In the method, A step of receiving a SSB (synchronization signal block) from a base station; A step of receiving a system information block based on the SSB from the base station; A step of determining a plurality of random access channel occasions (ROs) based on the above system information block; a step of transmitting a preamble to the base station using at least one of the plurality of ROs; and A step of receiving a response message to the preamble from the base station, A method in which the above multiple ROs are determined based on a slot pattern related to the positions of SBFD (sub-band full duplex) slots and non-SBFD slots.

2. In paragraph 1, The above SBFD slot is treated as a DL (downlink) slot by non-SBFD terminals, A method in which the above plurality of ROs are allocated to UL (uplink) usable physical resource blocks (PRBs) of the non-SBFD slot and the SBFD slot.

3. In claim 2, A method in which the above plurality of ROs are allocated to the UL (uplink) subband frequency resources of the SBFD slot.

4. In claim 1, The above SBFD slot is treated as a flexible slot by non-SBFD terminals, A method in which the above plurality of ROs are allocated to the SBFD slot and the non-SBFD slot.

5. In claim 4, A method in which the above plurality of ROs are set within the UL subband frequency resources of the SBFD slot.

6. In claim 1, The above system information block includes separated RO configurations, The ROs set by the above separated RO settings are a method of indicating different RO types.

7. In claim 1, The above system information block includes a shared RO configuration, The above shared RO setting is a method commonly used to identify additional ROs included in the DL SBFD slot and legacy ROs included in the flexible SBFD slot and non-SBFD slot.

8. In claim 7, The step of determining the above multiple ROs is: A method comprising the step of determining additional ROs to be included in the DL SBFD slot based on the shared RO settings.

9. In claim 1, A method wherein the above system information block includes information regarding which RO configuration to use, either separated RO configurations or shared RO configurations.

10. In claim 1, A method in which the above multiple ROs are determined based on the shared RO configuration, when the system information block does not include information regarding which RO configuration to use among the separated RO configurations or the shared RO configuration.

11. In claim 1, A method in which the starting PRB (physical resource block) of the lowest RO on the frequency axis among the above multiple ROs is determined as the sum of the lowest PRB of the UL (uplink) subband of the SBFD slot and an offset.

12. In claim 11, A method in which the size of the UL subband on the frequency axis is determined as an integer multiple of the size of the PRB occupied by each of the plurality of ROs.

13. In claim 1, Further comprising a step of mapping the SSB to at least one RO, The above mapping is performed in the same way as the RO mapping applied to non-SBFD terminals.

14. In claim 13, Further comprising a step of performing validation of the above multiple ROs, The above validation is a method of determining that only ROs existing within the UL (uplink) subband frequency resources of the SBFD slot are valid.

15. In claim 13, The above mapping is a method in which SSBs are additionally mapped to SBFD ROs that are valid only for SBFD terminals.

16. In claim 1, Further comprising a step of mapping the SSB to at least one RO, The above mapping is a method of applying a part of the RO mapping applied to a non-SBFD terminal to an SBFD RO.

17. In claim 1, Further comprising a step of performing a first mapping of the SSB to the at least one RO, The above first mapping is applied independently from the second RO mapping applied to a non-SBFD terminal.

18. In claim 1, Additional ROs among the above plurality of ROs correspond to the index of the SSB within the first association period or the first association pattern period, A method in which legacy ROs among the above plurality of ROs correspond to the index of the SSB within the second association period or the second association pattern period.

19. In claim 18, A method wherein the first association period or the first association pattern period is indicated by a setting related to additional ROs for SBFD-aware UEs among the separated RO settings.

20. In claim 18, A method wherein the first association period or the first association pattern period is indicated by a setting related to additional ROs for the SBFD-aware UE received in addition to the shared RO setting.

21. In claim 18, A method wherein the first association period or the first association pattern period is determined as a multiple of the second association period or the second association pattern period.

22. In claim 1, The step of transmitting the above preamble is: Step for checking the associated pattern cycle of the RO type to be used; A step of determining a time period for PRACH repetition based on the above-mentioned association pattern period; A method comprising the step of performing PRACH transmission using preamble repetition based on the above time period.

23. In the method, A step of receiving a SSB (synchronization signal block) from the base station; A step of receiving a system information block based on the SSB from the base station; A step of determining a plurality of random access channel occasions (ROs) based on the above system information block; A step of performing mapping of the above SSB to at least one RO; A step of transmitting a preamble to the base station using at least one RO; and A step of receiving a response message to the preamble from the base station, A method in which the starting PRB (physical resource block) of the lowest RO on the frequency axis among the above multiple ROs is determined as the sum of the lowest PRB of the UL (uplink) subband of the SBFD slot and an offset.

24. In the method, A step of generating configuration information related to multiple ROs (random access channel occasions); A step of transmitting an SSB (synchronization signal block) to a terminal; A step of transmitting a system information block including setting information related to RO to the terminal; A step of receiving a preamble from the terminal using at least one RO among the plurality of ROs; and A step of transmitting a response message to the preamble to the terminal, A method in which the above multiple ROs are determined based on a slot pattern related to the positions of SBFD (sub-band full duplex) slots and non-SBFD slots.

25. In claim 21, A method in which the configuration information related to the above RO includes information related to separated RO configurations or information related to shared RO configurations.

26. In the device, Transmitter and receiver; and A processor connected to the above transmitter and receiver is included, The above processor, Receives SSB (synchronization signal block) from the base station, Receive a system information block based on the SSB from the base station, Determine multiple ROs (random access channel occasions) based on the above system information block, Transmitting a preamble to the base station using at least one RO among the plurality of ROs, configured to receive a response message to the preamble from the base station, A device in which the above multiple ROs are determined based on a slot pattern related to the positions of SBFD (sub-band full duplex) slots and non-SBFD slots.

27. In the device, Transmitter and receiver; and A processor connected to the above transmitter and receiver is included, The above processor, Receives a SSB (synchronization signal block) from the above base station, Receive a system information block based on the SSB from the base station, Determine multiple ROs (random access channel occasions) based on the above system information block, Mapping the above SSB to at least one RO, Transmitting a preamble to the base station using at least one RO, configured to receive a response message to the preamble from the base station, A device in which the starting PRB (physical resource block) of the lowest RO on the frequency axis among the above multiple ROs is determined by the sum of the lowest PRB of the UL (uplink) subband of the SBFD slot and an offset.

28. In the device, Transmitter and receiver; and A processor connected to the above transmitter and receiver is included, The above processor, Generate configuration information related to multiple ROs (random access channel occasions), Transmits SSB (synchronization signal block) to the terminal, Transmitting a system information block containing configuration information related to RO to the terminal, Receive a preamble from the terminal using at least one of the plurality of ROs, It is configured to transmit a response message to the preamble to the terminal, A device in which the above multiple ROs are determined based on a slot pattern related to the positions of SBFD (sub-band full duplex) slots and non-SBFD slots.

29. At the terminal, At least one processor; At least one computer memory connected to said at least one processor and storing instructions that direct operations when executed by said at least one processor, The above actions are, A step of receiving a SSB (synchronization signal block) from a base station; A step of receiving a system information block based on the SSB from the base station; A step of determining a plurality of random access channel occasions (ROs) based on the above system information block; a step of transmitting a preamble to the base station using at least one of the plurality of ROs; and A step of receiving a response message to the preamble from the base station, The above multiple ROs are terminals determined based on slot patterns related to the positions of SBFD (sub-band full duplex) slots and non-SBFD slots.

30. In a non-transitory computer-readable medium storing at least one instruction, comprising at least one instruction executable by the processor, At least one of the above commands causes the device to: Receives SSB (synchronization signal block) from the base station, Receive a system information block based on the SSB from the base station, Determine multiple ROs (random access channel occasions) based on the above system information block, Transmitting a preamble to the base station using at least one RO among the plurality of ROs, Instructs to receive a response message to the preamble from the base station, A computer-readable medium in which the above plurality of ROs are determined based on a slot pattern related to the positions of SBFD (sub-band full duplex) slots and non-SBFD slots.

Images