Apparatus and method for determining validity validation rule of random access channel occasion supporting sub-band full duplex communication 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) communication in a wireless communication system, and a method may comprise the steps of: receiving a synchronization signal block (SSB) from a base station; on the basis of the SSB, receiving a system information block from the base station; determining at least one valid random access channel occasion (RO) on the basis of the system information block; transmitting, to the base station, a preamble by using the at least one valid RO; and receiving, from the base station, a response message to the preamble.

Description

Device and method for determining validation rules of 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 a device and method for determining validation rules of 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, massive machine type communications (mMTC), which connects multiple devices and objects to provide diverse services anytime and anywhere, as well as communication systems that consider reliability and latency-sensitive services / user equipment (UE), are being proposed. Various technological configurations are being proposed for these solutions.

[0004] The present disclosure relates to a device and method for determining a validation rule of 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 RO validation rules 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 performing a switching operation within an SBFD slot in a wireless communication system.

[0011] The present disclosure relates to a device and method for arranging downlink signals or channels and ROs within one SBFD slot in a wireless communication system.

[0012] The present disclosure relates to a device and method for placing an RO after a symbol of a gap symbol value from a downlink signal or channel within one SBFD slot in a wireless communication system.

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

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

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

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

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

[0018] 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 (SYSB) from the base station based on the SSB, determining at least one valid random access channel occasion (RO) based on the system information block, transmitting a preamble to the base station using the at least one valid RO, and receiving a response message to the preamble from the base station, wherein the at least one valid RO may include an RO included in uplink (UL) usable physical resource blocks (PRBs) for sub-band full duplex (SBFD) in a frequency axis among a plurality of ROs.

[0019] As an example of the present disclosure, a method includes the steps of generating configuration information related to a plurality of 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 valid RO among the plurality of ROs, and receiving a response message to the preamble from the terminal, wherein the at least one valid RO may include an RO included in uplink (UL) usable physical resource blocks (PRBs) for sub-band full duplex (SBFD) in a frequency axis among the plurality of ROs.

[0020] 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 (SYSB) from the base station based on the SSB, determine at least one valid random access channel occasion (RO) based on the system information block, transmit a preamble to the base station using the at least one valid RO, and receive a response message to the preamble from the base station, wherein the at least one valid RO may include an RO included in uplink (UL) usable physical resource blocks (PRBs) for sub-band full duplex (SBFD) in a frequency axis among a plurality of ROs.

[0021] As an example of the present disclosure, a device includes a transceiver and a processor connected to the transceiver, wherein the processor generates configuration information related to a plurality of random access channel occasions (ROs), transmits a synchronization signal block (SSB) to a terminal, transmits a system information block including configuration information related to the RO to the terminal, receives a preamble from the terminal using at least one valid RO among the plurality of ROs, and configures the terminal to receive a response message to the preamble, wherein the at least one valid RO may include an RO included in uplink (UL) usable physical resource blocks (PRBs) for sub-band full duplex (SBFD) in a frequency axis among the plurality of ROs.

[0022] 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 (SYS) from the base station based on the SSB; determining at least one valid random access channel occasion (RO) based on the system information block; transmitting a preamble to the base station using the at least one valid RO; and receiving a response message to the preamble from the base station, wherein the at least one valid RO may include an RO included in uplink (UL) usable physical resource blocks (PRBs) for sub-band full duplex (SBFD) in a frequency axis among a plurality of ROs.

[0023] 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, wherein the at least one instruction configures a device to receive a synchronization signal block (SSB) from a base station, receive a system information block (SYSB) based on the SSB from the base station, determine at least one valid random access channel occasion (RO) based on the system information block, transmit a preamble to the base station using the at least one valid RO, and receive a response message to the preamble from the base station, wherein the at least one valid RO may include an RO included in uplink (UL) usable physical resource blocks (PRBs) for sub-band full duplex (SBFD) in a frequency axis among a plurality of ROs.

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

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

[0026] According to the present disclosure, the validity of a physical random access channel opportunity supporting sub-band full-duplex communication can be efficiently determined.

[0027] The effects that can be obtained from the embodiments of the present disclosure are not limited to the effects mentioned above, and other effects 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.

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

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

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

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

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

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

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

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

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

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

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

[0039] FIG. 12 and FIG. 13 illustrate examples of a fluid slot with SBFD settings applied according to one embodiment of the present disclosure.

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

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

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

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

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

[0045] FIG. 19 illustrates an example of a RO configuration that takes into account the wideband of a UL slot based on a separated RO configuration according to one embodiment of the present disclosure.

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

[0047] FIG. 21 illustrates an example of a start OFDM symbol according to one embodiment of the present disclosure.

[0048] FIG. 22 illustrates an example of setting up RO in an SBFD environment according to one embodiment of the present disclosure.

[0049] FIG. 23 illustrates a first example in which RO is set in an SBFD environment according to one embodiment of the present disclosure.

[0050] FIG. 24 illustrates a second example in which RO is set in an SBFD environment according to one embodiment of the present disclosure.

[0051] FIG. 25 illustrates a third example in which RO is set in an SBFD environment according to one embodiment of the present disclosure.

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

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

[0054] FIG. 28 illustrates an example of a procedure for performing random access between a base station and a terminal according to one embodiment of the present disclosure.

[0055] FIG. 29 illustrates a block diagram showing setup elements of a transmitting device and a receiving device according to one embodiment of the present disclosure.

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

[0057] FIG. 31 illustrates an example of a signal processing module structure within a transmission device applicable to the present disclosure.

[0058] FIG. 32 illustrates another example of a signal processing module structure within a transmission device applicable to the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0076] 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.”

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

[0078] 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.”

[0079] 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.”

[0080] 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.” Furthermore, even when indicated as “control information (i.e., PDCCH),” “PDCCH” may be suggested as an example of “control information.”

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

[0082] 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, and 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.

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

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

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

[0086] 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 a physical random access channel (PRACH) and receive a random access response (RAR) to the preamble via a physical downlink control channel (PDCCH) and a 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 a corresponding PDSCH signal.

[0087] Meanwhile, when the random access process is performed in two stages, 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.

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

[0089] The control information transmitted from 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, the terminal can transmit UCI aperiodically over the PUSCH upon request / instruction from the network.

[0090] Wireless Resource Structure

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

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

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

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

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

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

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

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

[0099] 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. For example, the following configuration can be considered. Each section is listed in chronological order.

[0100] 1. DL only setting

[0101] 2. UL only setting

[0102] 3. Mixed UL-DL settings

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

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

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

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

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

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

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

[0110] Transmission Action:

[0111] Transmission Action:

[0112] · Common SN;

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

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

[0115] Receiving action:

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

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

[0118] · Common PDCP reordering;

[0119] · Sequential delivery and duplicate detection;

[0120] · Common buffer management.

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

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

[0123] UE RF / Baseband Requirements

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

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

[0126] For UEs with Dual Rx / Single Tx RF chains, simultaneous UL data transmission to both cells can be supported if 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 (including UEs that do not support UL CA and / or UL MIMO).

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

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

[0129] DAPS-HO according to TS 38.213 standard

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

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

[0132] 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 an MCG and the source MCG as an SCG, as described in Clause 7.6.2.

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

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

[0135] if

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

[0137] When transmissions from target cells and source cells overlap,

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

[0139] The transmissions of target cells and source cells are considered to overlap when:

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

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

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

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

[0144] Full duplex operation for NR

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

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

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

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

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

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

[0151] Base stations and terminals can perform full-duplex communication in various ways. For example, both the base station and terminal can perform full-duplex operation. That is, both the base station and terminal can simultaneously transmit and receive DL and UL signals 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 signals 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 signals with different terminals.

[0152] For convenience of explanation, it is assumed below 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.

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

[0154] RACH procedure (TS 38.213)

[0155] The physical random access procedure is triggered by a PRACH transmission request or PDCCH command from a higher layer. The higher layer configuration for PRACH transmission includes:

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

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

[0158] PRACH is a PRACH resource with a selected PRACH format and transmission power P as described in Clause 7.4. PRACH,b,f,c(i) is transmitted using .

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

[0160] For a 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. A PRACH transmission 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].

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

[0162] 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 an integer multiple of N.

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

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

[0165] 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]:

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

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

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

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

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

[0171] 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 TAAssume =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.

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

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

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

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

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

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

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

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

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

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

[0182] For unpaired spectra:

[0183] 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 transmission [15, TS 37.213].

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

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

[0186] - within the UL symbol, or

[0187] - 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 gap is 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].

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

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

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

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

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

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

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

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

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

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

[0198] 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, the UE shall not transmit 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, N=32 for μ=6, and μ 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].

[0199] Below, examples of PRACH configuration tables used in the methods proposed through the present disclosure are described.

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

[0201] 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,

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

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

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

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

[0206] 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 can be represented as shown in FIG. 7. An RO is allocated for each frame configured with 40 slots, and three ROs can be configured in each slot.

[0207] OFDM baseband signal generation for PRACH

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

[0209]

[0210] Here, And,

[0211] - : provided by Section 6.3.3.

[0212] - △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.

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

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

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

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

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

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

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

[0220] - and is provided by Section 6.3.3.

[0221] - Here

[0222] - When,

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

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

[0225]

[0226] Here

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

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

[0229] - and is provided by Section 5.3.1.

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

[0231] Here

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

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

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

[0235] - is given as follows:

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

[0237] - △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 .

[0238] - if And:

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

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

[0241] 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:

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

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

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

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

[0246] PRACH repetition

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

[0248] 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 repetition counts 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.

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

[0250] 4.7 TDD operation in 213 spec for 11.1(slot configuration) and 11.1.1 (UE procedure for determining slot format)

[0251] Below, the HD operations supported in NR are described.

[0252] Slot settings

[0253] Slot formats include downlink symbols, uplink symbols, and floating symbols.

[0254] The following applies to each serving cell:

[0255] If the UE is provided with tdd-UL-DL-ConfigurationCommon, the UE sets the slot format of each slot according to the number of slots specified by tdd-UL-DL-ConfigurationCommon.

[0256] tdd-UL-DL-ConfigurationCommon provides:

[0257] - Reference SCS set by referenceSubcarrierSpacing μ ref

[0258] - pattern1

[0259] pattern1 provides:

[0260] - Slot setting period in Pmsec by dl-UL-TransmissionPeriodicity

[0261] - Number of slots containing only downlink symbols d by nrofDownlinkSlots slots

[0262] - Number of downlink symbols d by nrofDownlinkSymbols sym

[0263] - Number of slots containing only uplink symbols u by nrofUplinkSlots slots

[0264] - Number of uplink symbols u by nrofUplinkSymbols sym

[0265] P=0.625 msec value is μ ref = 3, μ ref = 5 or μ ref = Valid only when 6. P=1.25 msec value is μ ref = 2, μ ref = 3, μ ref = 5 or μ ref = Valid only when 6. P=2.5 msec value is μ ref = 1, μ ref = 2, μ ref = 3, μ ref = 5 or μ ref = Valid only when 6. P=10 msec value is μ ref = 0, μ ref = 1, μ ref = 2, μ ref = 3 or μ ref = Valid only when 5.

[0266] Slot setting period P msec SCS setting μ ref Includes slots with . The first d in the S slot slots The slot contains only downlink symbols, and the last slot u slots contains only uplink symbols. The first d slots slot d sym The symbols that follow are downlink symbols. The last u slots u in front of slot sym The symbol is an uplink symbol. The rest (Sd slots -u slots )- -d sym -u sym is a fluid symbol.

[0267] In every 20 / P period, the first symbol is the first symbol of an even frame.

[0268] If tdd-UL-DL-ConfigurationCommon provides both Pattern1 and Pattern2, the UE sets the slot-per-slot format for the first slot number indicated in Pattern1, and sets the slot-per-slot format for the second slot number indicated in Pattern2.

[0269] Pattern 2 provides:

[0270] - Slot setting period of P2msec by dl-UL-TransmissionPeriodicity

[0271] - Number of slots containing only downlink symbols d by nrofDownlinkSlots slot,2

[0272] - Number of downlink symbols d by nrofDownlinkSymbols sym,2

[0273] The number of slots containing only uplink symbols u by nrofUplinkSlots slots,2

[0274] Number of uplink symbols u by nrofUplinkSymbolssym,2

[0275] The applicable values ​​of P2 are the same as the applicable values ​​of P.

[0276] The slot setting cycle P+P2mec is the first S=P·2 μref Slot and second S2=P2·2 μref Includes slots.

[0277] Among the S2 slots, the first d slots,2 The slot contains only downlink symbols, and the last u slots,2 The slot contains only uplink symbols. The first d slots,2 d after slot sym,2 The symbol is a downlink symbol. The last u slots,2 u before slot sym,2 The symbol is an uplink symbol. The remaining (S2-d slots,2 -u slots,2 )- -d sym,2 -u sym,2 is a fluid symbol.

[0278] The UE expects P+P2 to be divisible by 20 ms.

[0279] The first symbol in every 20 / (P+P2) cycle is the first symbol of an even frame.

[0280] UE sets reference SCS μ ref For this configured DL BWP or UL BWP, we expect the SCS setting μ to be less than or equal to that of the configured DL BWP or UL BWP. Each slot provided by pattern1 or pattern2 is a contiguous 2-bit slot of an active DL BWP or an active UL BWP. (μ-μref) Applicable to slots. The first slot is the reference SCS setting μ ref Starts at the same time as the first slot of the reference SCS setting μ ref Each downlink, floating or uplink symbol for SCS configuration μ is 2 (μ-μref) Corresponds to continuous downlink, dynamic or uplink symbols.

[0281] If the UE is additionally provided with tdd-UL-DL-ConfigurationDedicated, the tdd-UL-DL-ConfigurationDedicated parameter only overwrites slot-specific floating symbols according to the number of slots provided by tdd-UL-DL-ConfigurationCommon.

[0282] Provided by tdd-UL-DL-ConfigurationDedicated.

[0283] - A set of slot configurations provided by slotSpecificConfigurationsToAddModList.

[0284] - For each slot setting in the slot setting set

[0285] - Slot index of the slot provided by slotIndex

[0286] - The set of symbols for the slots provided by symbols:

[0287] - If symbols = allDownlink, all symbols in the slot are downlink

[0288] - If symbols = allUplink, all symbols in the slot are uplink

[0289] - If symbols = explicit, nrofDownlinkSymbols provides the number of the first downlink symbol in the slot, and nrofUplinkSymbols provides the number of the last uplink symbol in the slot. If nrofDownlinkSymbols is not provided, the slot has no downlink first symbol, and if nrofUplinkSymbols is not provided, the slot has no uplink last symbol. The remaining symbols in the slot are floating symbols.

[0290] For each slot with the corresponding index provided by slotIndex, the UE applies the format provided by the corresponding symbols. The UE does not expect tdd-UL-DL-ConfigurationDedicated to indicate a symbol designated for downlink by tdd-UL-DL-ConfigurationCommon as uplink, nor does it expect a symbol designated for uplink by tdd-UL-DL-ConfigurationCommon to indicate downlink.

[0291] For each slot configuration provided by tdd-UL-DL-ConfigurationDedicated, the reference SCS configuration is μ, which is the reference SCS configuration provided by tdd-UL-DL-ConfigurationCommon. ref am.

[0292] The number of downlink symbols, uplink symbols and floating symbols in each slot of the slot configuration period and the slot configuration period are determined from tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated, which are common to each configured BWP.

[0293] The UE considers symbols in slots indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated to be for reception, and symbols in slots indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated to be for transmission.

[0294] If the UE has not configured PDCCH monitoring for DCI format 2_0, it applies to the set of symbols in the slot indicated by floating symbols by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated (if provided), or if tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the UE, then it applies to the set of symbols.

[0295] - When the UE receives the corresponding instruction by DCI format, it receives PDSCH or CSI-RS in the symbol set of the slot.

[0296] - The UE transmits PUSCH, PUCCH, PRACH or SRS in the set of symbols of the slot if the UE receives the corresponding indication by DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR.

[0297] For operation in unpaired spectrum on a single carrier,

[0298] When a UE is configured by a higher layer to receive a PDCCH, a PDSCH, a CSI-RS or a DL PRS in the symbol set of a slot, if the UE does not detect a DCI format indicating an instruction to transmit a PUSCH, a PUCCH, a PRACH or an SRS in at least one symbol in the symbol set of the slot, the UE receives the PDCCH, a PDSCH, a CSI-RS or a DL PRS in the symbol set of the slot. Otherwise, the UE does not receive the PDCCH, a PDSCH, a CSI-RS or a DL PRS in the symbol set of the slot.

[0299] For shared spectrum channel access in FR1 or for operation in FR2-2 with ChannelAccessMode2 = 'enabled', if the UE is provided with csi-RS-ValidationWithDCI, and is not provided with CO-DurationsPerCell and SlotFormatCombinationsPerCell, and the UE is configured by higher layers to receive CSI-RS in the symbol set of the slot, if the UE does not detect a DCI format indicating aperiodic CSI-RS reception or scheduling PDSCH reception in the symbol set of the slot, the UE cancels CSI-RS reception in the symbol set of the slot.

[0300] If the UE is provisioned with channelAccessMode = 'dynamic' and availableRB-SetsToAddModList and availableRB-SetsToReleaseList are provided, the UE expects co-DurationsPerCellToAddModList and co-DurationsPerCellToReleaseList and / or slotFormatCombToAddModList and slotFormatCombToReleaseList to be provided.

[0301] For operation in unpaired spectrum on a single carrier,

[0302] If the UE is configured by the upper layer to transmit SRS, PUCCH, PUSCH or PRACH in a set of symbols of a slot and the UE detects a DCI format instructing it to receive CSI-RS or PDSCH in a subset of that set of symbols,

[0303] - If the UE does not indicate the [partialCancellation] function, the UE shall receive T from the last symbol of PDCCH reception. proc,2It is expected that the UE will not cancel the transmission of PUCCH, PUSCH or PRACH in the symbols occurring within. Otherwise, the UE cancels the PUCCH, PUSCH, actual repetition of PUSCH or PRACH transmission determined according to clauses 9, 9.2.5, 9.2.6 or 6.1 of [6, TS 38.214].

[0304] - If the UE indicates the [partialCancellation] capability, the UE shall receive T from the last symbol of PDCCH reception. proc,2 The UE is not expected to cancel transmissions of PUCCH, PUSCH or PRACH in symbols occurring within the remaining symbols. The UE cancels transmissions of PUCCH, PUSCH, actual repetitions of PUSCH or PRACH determined according to clauses 9, 9.2.5, 9.2.6 or 6.1 of [6, TS 38.214] in the remaining symbols.

[0305] - The UE receives T from the last symbol of PDCCH reception. proc,2 It is expected that the UE will not cancel SRS transmissions in the symbols occurring within the subset. The UE cancels SRS transmissions in the remaining symbols of the subset.

[0306] T proc,2 is d according to [6, TS 38.214] 2,1 Assuming = 1, the PUSCH preparation time for the UE processing capability that matches μ corresponding to the smallest SCS setting among the SCS settings of the SRS, PUCCH, and PUSCH and the SCS settings of the PDCCH including the DCI format. If the SCS setting of the PRACH is 15 kHz or higher, μ corresponds to the SCS setting of the PRACH, otherwise μ r =0.

[0307] If the symbol set of a slot is indicated to the UE as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and the symbol set of that slot overlaps or even partially overlaps with the PDCCH, PDSCH or CSI-RS, the UE does not receive the PDCCH, PDSCH or CSI-RS.

[0308] If the symbol set of a slot is indicated to the UE as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and the UE is not provided with a measurement gap, the UE does not receive DL PRS in the symbol set of that slot.

[0309] If the symbol set of a slot is indicated as downlink to the UE by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and the symbol set of that slot overlaps or even partially overlaps with a PUSCH, PUCCH, PRACH or SRS, the UE shall not transmit a PUSCH, PUCCH, PRACH or SRS.

[0310] If the symbol set of a slot is indicated as flexible to the UE by tdd-UL-DL-ConfigurationCommon and, if provided, tdd-UL-DL-ConfigurationDedicated, the UE shall not expect to receive both upper layer dedicated parameters configuring the UE's transmission and upper layer dedicated parameters configuring the UE's reception in the symbol set of that slot.

[0311] When operating as a single carrier in an unpaired spectrum, the UE shall not transmit a PUSCH, PUCCH or PRACH in a slot, and shall not transmit an SRS in a symbol set of a slot indicated to the UE for reception of an SS / PBCH block by ssb-PositionsInBurst of SIB1, ssb-PositionsInBurst of ServingCellConfigCommon, or, if the UE is not provided with dl-OrJointTCI-StateList, ssb-PositionsInBurst of SSB-MTCAdditionalPCI associated with an active TCI state of a PDCCH or PDSCH, or a symbol set of a slot corresponding to an SS / PBCH block configured for L1 beam measurement / reporting, if the transmission overlaps with symbols in the corresponding symbol set. The UE does not expect the set of symbols in a slot to be indicated to the UE in uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0312] UE

[0313] - If it is set to multi-serving cells and directionalCollisionHandling-r16 = 'enabled' is provided for a specific serving cell among the multi-serving cells,

[0314] - Indicates support for half-DuplexTDD-CA-SameSCS-r16 feature,

[0315] - If PDCCH monitoring for DCI format 2_0 detection is not set in any of the multiple serving cells,

[0316] For a set of slot symbols of the first serving cell indicated to the UE for SS / PBCH block reception by ssb-PositionsInBurst of SIB1, ssb-PositionsInBurst of ServingCellConfigCommon, or ssb-PositionsInBurst of SSB-MTCAdditionalPCI associated with an active TCI state of PDCCH or PDSCH if the UE is not provided with dl-OrJointTCI-StateList, or a set of symbols of a slot corresponding to an SS / PBCH block configured for L1 beam measurement / reporting, if a transmission overlaps with a symbol of the corresponding symbol set, the UE shall not transmit a PUSCH, PUCCH, or PRACH in the slot, and shall not transmit an SRS within the symbol set of the following slot.

[0317] - If the UE is not capable of simultaneous transmission and reception between multiple serving cells by simultaneousRxTxInterBandCA, any of the multiple serving cells

[0318] - One of the cells corresponding to the same band as the first cell, regardless of whether simultaneous transmission and reception are possible by simultaneousRxTxInterBandCA.

[0319] The symbol set of the slot corresponding to a valid PRACH event and the N preceding the valid PRACH event gap For symbols, as described in Section 8.1, if reception overlaps with a symbol in a symbol set, the UE does not receive PDCCH, PDSCH, or CSI-RS in the slot. The UE does not expect the symbol set in the slot to be indicated as downlink by tdd-UL-DL-Configuration Common or tdd-UL-DL-ConfigurationDedicated.

[0320] For a set of symbols in a slot indicated to the UE by pdcch-ConfigSIB1 in the MIB for a CORESET for a Type0-PDCCH CSS set, the UE does not expect that set of symbols to be indicated in the uplink by tdd-UL-DL-Configuration Common or tdd-UL-DL-ConfigurationDedicated.

[0321] If a UE is scheduled in DCI format to receive PDSCH in multiple slots, and tdd-UL-DL-Configuration Common or tdd-UL-DL-ConfigurationDedicated indicates that at least one symbol in the set of symbols for which the UE receives the scheduled PDSCH for one of the multiple slots is an uplink symbol, the UE does not receive PDSCH in the slot.

[0322] If a UE is scheduled in DCI format to transmit PUSCH over multiple slots, and tdd-UL-DL-Configuration Common or tdd-UL-DL-ConfigurationDedicated indicates that at least one symbol in a series of symbols for which the UE is scheduled for one of the multiple slots is a downlink symbol, the UE shall not transmit PUSCH in that slot.

[0323] If UE

[0324] - It is set to multiple serving cells, and directional collision handling is provided for one of the set serving cells - r16 = 'enabled',

[0325] - Indicates that half-duplex TDD-CA-SameSCS-r16 functionality is supported.

[0326] - If PDCCH is not set to be monitored to detect DCI format 2_0 in multiple service cells,

[0327] The UE determines the reference cell of the symbol as the active cell with the smallest cell index among the following.

[0328] - If the UE cannot transmit and receive simultaneously among multiple serving cells as indicated by simultaneous RxTxInterBandCA, the multiple serving cells set

[0329] - When the UE can transmit and receive simultaneously through RxTxInterBandCA, multiple serving cells are set up for each band.

[0330] Here the symbols are set as follows:

[0331] - Downlink or uplink, indicated by tdd-UL-DL-Configuration Common or tdd-UL-DL-ConfigurationDedicated

[0332] - If the symbol is floating and the UE is configured to transmit SRS, PUCCH, PUSCH or PRACH in the symbol, then the uplink

[0333] - Downlink, when the symbol is floating and the UE is configured to receive PDCCH, PDSCH or CSI-RS in the symbol.

[0334] If another cell among the cells set to directionalCollisionHandling-r16 operates in the same frequency band as the reference cell, the UE does not expect:

[0335] - A symbol that is indicated as downlink or uplink in the reference cell by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and as uplink or downlink in other cells.

[0336] - tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated to detect the DCI format that marks a symbol as downlink in the reference cell and schedules transmission of the symbol in other cells.

[0337] It is configured to receive PDCCH, PDSCH or CSI-RS on a flexible symbol in a reference cell by an upper layer and detect a DCI format for scheduling transmission in that symbol in another cell.

[0338] If the reference cell and other cells set to directionalCollisionHandling-r16 operate in different frequency bands,

[0339] UE is

[0340] - When a symbol is indicated as downlink or uplink in other cells by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and as uplink or downlink in the reference cell, the symbol is assumed to be a flexible symbol, and there is no need to receive a PDCCH, PDSCH, or CSI-RS configured in a higher layer, and there is no need to transmit an SRS, PUCCH, PUSCH, or PRACH configured in a higher layer.

[0341] If the symbol is marked as downlink in the reference cell by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the signal / channel scheduled by the DCI format is transmitted in the symbol of another cell.

[0342] If the UE detects a DCI format that schedules transmission for one or more symbols in another cell, it does not need to receive the PDCCH, PDSCH, or CSI-RS configured in the upper layer in the floating symbols of the reference cell in that symbol set.

[0343] And regardless of whether the reference cell and other cells operate in the same frequency band or in different frequency bands,

[0344] UE is

[0345] - It is not expected to detect a DCI format that indicates that the tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated symbol for the reference cell is uplink and schedules reception on that symbol in another cell.

[0346] - It is configured by the upper layer to transmit SRS, PUCCH, PUSCH or PRACH on a flexible symbol in the reference cell, and it is not expected to detect a DCI format that schedules reception on the corresponding symbol in another cell.

[0347] - If at least one symbol among the symbol sets is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the reference cell, or corresponds to PDCCH, PDSCH or CSI-RS reception, the PUCCH, PUSCH or PRACH set by the upper layer for the symbol sets of other cells is not transmitted.

[0348] - If the corresponding symbol set is indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the reference cell, or corresponds to PDCCH, PDSCH, or CSI-RS reception, the SRS set by the upper layer for the symbol set of another cell is not transmitted.

[0349] - If at least one symbol among the symbol sets is indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the reference cell, or corresponds to SRS, PUCCH, PUSCH or PRACH transmission, the PDCCH, PDSCH or CSI-RS set by the upper layer for the symbol sets of other cells is not received.

[0350] - When the reference cell is configured to transmit SRS, PUCCH, PUSCH, or PRACH respectively by the upper layer or to receive PDCCH, PDSCH, or CSI-RS, a symbol indicated as downlink or uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in another cell is regarded as a flexible symbol.

[0351] - It is not expected to detect a first DCI format that schedules transmission or reception for a particular symbol in the first cell, and a second DCI format that schedules reception or transmission for that symbol in the second cell, respectively.

[0352] - After applying the above procedure for directional collision handling within the set of cells set to directionalCollisionHandling-r16, the UE does not expect directional collisions to occur between serving cells on which the UE cannot perform simultaneous transmission and reception.

[0353] 11.1.1 UE Procedure for Slot Format Determination

[0354] This section applies to serving cells included in the serving cell set established by slotFormatCombToAddModList, slotFormatCombToReleaseList, availableRB-SetsToAddModList, availableRB-SetsToReleaseList, switchTriggerToAddModList, switchTriggerToReleaseList, co-DurationsPerCellToAddModList, and co-DurationsPerCellToReleaseList for the UE.

[0355] If the UE is configured with the SlotFormatIndicator parameter by the upper layer, the UE is provided with the SFI-RNTI by sfi-RNTI and the payload size of DCI format 2_0 by dci-PayloadSize.

[0356] Additionally, the UE may provide L for DCI format 2_0 in one or more serving cells. SFI Having a CCE aggregation level A search space set for monitoring PDCCH candidates and a setting for the corresponding CORESET p are provided as described in Section 10.1. A PDCCH candidate is a CCE aggregation level L for a search space set s in CORESET p. SFI The first one about It is a PDCCH candidate.

[0357] For each serving cell in the serving cell set, the UE may be provided with:

[0358] - ID of serving cell by servingCellId

[0359] - SFI index field position in DCI format 2_0 by positionInDCI

[0360] - A set of slot format combinations by slot format combinations, where each slot format combination of the set of slot format combinations includes:

[0361] - one or more slot formats, each indicated by slotFormats for a combination of slot formats, and

[0362] - Mapping the slot format combination to the corresponding SFI-index field value of DCI format 2_0 provided by the slot format combination Id.

[0363] - For unpaired spectrum operation, reference SCS setting μ by subcarrier spacing SFI , if a secondary UL carrier is set in the serving cell, reference SCS setting μ by subcarrierSpacing2 for the secondary UL carrier SFI,SUL

[0364] - For paired spectrum operation, reference SCS setting μ for DL ​​BWP by subcarrierSpacing SFI,DL and reference SCS setting μ for UL BWP by subcarrierSpacing2 SFI,UL

[0365] - Location of the Available RB Sets Indicator field in DCI format 2_0, the field by Available RB-SetsPerCell is as follows.

[0366] - 1 bit, if the intraCellGuardBandsDL-List for the serving cell indicates that no intra-cell guard bands are configured, where a value of '1' indicates that the serving cell is available for reception, and a value of '0' indicates that the serving cell is not available for reception, and the serving cell remains available or unavailable for reception until the end of the remaining channel occupancy period. Or,

[0367] - A bitmap that maps to the RB set of the serving cell [6, TS 38. 214], the intraCellGuardBandsDL-List for the serving cell is set if an intra-cell guard band is set or the intraCellGuardBandsDL-List for the serving cell is not provided, where the bitmap is N RB,set,DL Includes bits and N RB,set,DL is the number of RB sets of the serving cell, and a value of '1' indicates that the RB set is available for reception, and a value of '0' indicates that the RB set is not available for reception, and the RB set remains available or unavailable for reception until the remaining channel occupancy period ends.

[0368] - Location of the Channel Occupancy Duration field indicated by DCI format 2_0 by CO-DurationsPerCell, this field indicates the remaining channel occupancy duration of the serving cell starting from the first symbol of the slot in which the UE detects DCI format 2_0 by providing the value of co-DurationList. The Channel Occupancy Duration field contains: bits, where COdurationListSize is the number of values ​​provided in co-DurationList. If CO-DurationsPerCell is not provided, the remaining channel occupancy duration of the serving cell is the number of slots for which the SFI-index field value provides the corresponding slot format, starting from the slot in which the UE detects DCI format 2_0.

[0369] - Setting reference SCS for co-DurationList by subcarrierSpacing

[0370] - Location of the Search Space Set Group Switching Flag field, DCI format 2_0 by SearchSpaceSwitchTrigger, where the field indicates a group of two groups of search space sets for PDCCH monitoring for scheduling for a serving cell or a set of serving cells, and is provided by CellGroupsForSwitching as described in Section 10.4.

[0371] If CO-DurationsPerCell or SlotFormatCombinationsPerCell is not provided and channelAccessMode = “semiStatic” is provided, the procedure in this section applies, assuming that the remaining channel occupancy time is the channel occupancy time defined in section 4.3 of [15, TS 37.213], if a DL transmission burst is detected within the channel occupancy time.

[0372] The SFI Index field value of DCI format 2_0 indicates to the UE the slot format of each slot for each DL BWP or each UL BWP, starting from the slot in which the UE detected DCI format 2_0. The number of slots shall be greater than or equal to the PDCCH monitoring period for DCI format 2_0. The SFI Index field contains bits, and maxSFIindex is the maximum of the values ​​provided by the corresponding slot format combination ID. The slot format is identified by its format index as provided in Table 11.1.1-1, where 'D' indicates a downlink symbol, 'U' indicates an uplink symbol, and 'F' indicates a flexible symbol.

[0373] If the PDCCH monitoring periodicity for DCI format 2_0 provided to the UE for the search space set by the monitoring slot periodicity and offset is less than the duration of the slot format combination acquired by the UE when monitoring the PDCCH for DCI format 2_0 by the corresponding SFI index field value, and the UE detects one or more DCI formats 2_0 indicating a slot format for one slot, the UE expects that each of the one or more DCI formats 2_0 indicates the same slot format.

[0374] It is expected that the UE will not be configured to monitor PDCCH for DCI format 2_0 on a second serving cell that uses a larger SCS than the serving cell.

[0375] [Table 7] below shows an example of a slot format for a normal cyclic prefix.

[0376] FormatSymbol number in a slot0123456789101112130DDDDDDDDDDDDDD1UUUUUUUUUUUUUU2FFFFFFFFFFFFFF3DDDDDDDDDDDDDF4DDDDDDDDDDDDFF5DDDDDDDDDDDFFF6DDDDDDDDDDFFFF7DDDDDDDDDFFFFF8FFFFFFFFFFFFFU9FFFFFFFFFFFFUU10FUUUUUUUUUUUUU11FFUUUUUUUUUUUU12FFFUUUUUUUUUUU13FFFFUUUUUUUUUU14FFFFFUUUUUUUUU15FFFFFFUUUUUUUU16DFFFFFFFFFFFFF17DDFFFFFFFFFFFF18DDDFFFFFFFFFFF19DFFFFFFFFFFFFU20DDFFFFFFFFFFFU21DDDFFFFFFFFFFU22DFFFFFFFFFFFUU23DDFFFFFFFFFFUU24DDDFFFFFFFFFUU25DFFFFFFFFFFUUU26DDFFFFFFFFFUUU27DDDFFFFFFFFUUU28DDDDDDDDDDDDFU29DDDDDDDDDDDFFU30DDDDDDDDDDFFFU31DDDDDDDDDDDFUU32DDDDDDDDDDFFUU33DDDDDDDDDFFFUU34DFUUUUUUUUUUUU35DDFUUUUUUUUUUU36DDDFUUUUUUUUUU37DFFUUUUUUUUUUU38DDFFUUUUUUUUUU39DDDFFUUUUUUUUU40DFFFUUUUUUUUUU41DDFFFUUUUUUUUU42DDDFFFUUUUUUUU43DDDDDDDDDFFFFU44DDDDDDFFFFFFUU45DDDDDDFFUUUUUU46DDDDDFUDDDDDFU47DDFUUUUDDFUUUU48DFUUUUUDFUUUUU49DDDDFFUDDDDFFU50DDFFUUUDDFFUUU51DFFUUUUDFFUUUU52DFFFFFUDFFFFFU53DDFFFFUDDFFFFU54FFFFFFFDDDDDDD55DDFFFUUUDDDDDD56 - 254Reserved255UE determines the slot format for the slot basedontdd-UL-DL-ConfigurationCommon, ortdd-UL-DL-ConfigurationDedicatedand, if any, on detected DCI formats

[0377] For non-paired spectrum operation for the UE in the serving cell, the reference SCS setting μ for each slot format by subcarrier spacing SFI is provided as a combination of slot formats indicated by the SFI index field value of DCI format 2_0. The UE sets the reference SCS μ SFI For active UL BWP with active DL BWP or SCS setting μ, μ≥μ SFI is expected to be. Each slot format of the slot format combination indicated by the SFI Index field value of DCI format 2_0 is 2 of the active DL BWP or the active UL BWP. (μ-μ_SFI) Applies to consecutive slots, with the first slot being the reference SCS setting μ SFI Starts concurrently with the first slot of the reference SCS setting μ SFI Each downlink, floating or uplink symbol of corresponds to a consecutive downlink, floating or uplink symbol of the SCS configuration μ.

[0378] For paired spectrum operation for a UE of a serving cell, the SFI Index field of DCI format 2_0 indicates a combination of slot formats including a slot format combination for a reference DL BWP and a slot format combination for a reference UL BWP of the serving cell. The UE sets a reference SCS for the slot format combination indicated by the value of the SFI Index field of DCI format 2_0 for the reference DL BWP of the serving cell by subcarrier spacing μ SFI,DL is provided. subcarrierSpacing2 is the reference SCS setting μ for the slot format combination indicated by the SFI Index field value of DCI format 2_0 for the reference UL BWP of the serving cell. SFI,UL provides μ to the UE.SFI,DL ≥μ SFI,UL and each The value of the slot format provided by the value, where the value of the slot format is determined by the value of the slot format combination ID of the slot format combination, and the value of the slot format combination ID is set to the value of the SFI index field value of DCI format 2_0, and first The values ​​for the slot format combination apply to the reference DL BWP and the following values ​​apply to the reference UL BWP: μ SFI,DL <μ SFI,UL and each The first value of the slot format combination for the value is applied to the reference DL BWP, and the next The values ​​apply to the reference UL BWP.

[0379] UE sets reference SCS μ SFI,DL , and the SCS setting μ of the active DL BWP is provided. DL About μ DL ≥μ SFI,DL satisfies. The UE sets the reference SCS μ SFI,UL , and the SCS setting μ of the active UL BWP is provided. UL About μ UL ≥μ SFI,UL satisfies. Each slot format of the slot format combination indicated by the SFI-index field value of DCI format 2_0 for the reference DL BWP is indicated by the slotFormatCombinationId value mapped to the slotFormats value in slotFormatCombination, starting from the first slot starting at the same point in time as the first slot of the reference DL BWP for the active DL BWP. Applies to consecutive slots of the dog. See also SCS setting μ SFI,DL Each downlink or floating symbol of SCS setting μ DL About Corresponds to a continuous downlink or floating symbol. Each slot format for the slot format combination of the reference UL BWP starts from the first slot starting at the same time as the first slot of the reference UL BWP for the active UL BWP. Applies to consecutive slots of the dog. See also SCS setting μ SFI,UL Each uplink or floating symbol of SCS setting μ UL About It corresponds to a continuous uplink or floating symbol of a dog.

[0380] For unpaired spectrum operation where the UE uses the secondary UL carrier in the serving cell, the SFI-index field value of DCI format 2_0 indicates a slot format combination including a slot format combination for the reference primary UL carrier of the serving cell and a slot format combination for the reference secondary UL carrier of the serving cell. The UE sets the reference SCS μ by subcarrierSpacing for the slot format combination indicated by the SFI-index field value of DCI format 2_0 for the reference primary UL carrier of the serving cell. SFI is provided. The UE sets the reference SCS μ by subcarrierSpacing2 for the slot format combination indicated by the SFI-index field value of DCI format 2_0 for the reference second UL carrier of the serving cell. SFI,SUL are provided. Each For the slotFormats value, the first of the slot format combinations The values ​​apply to the reference 1st UL carrier, and the following values ​​apply to the reference 2nd UL carrier.

[0381] The UE sets the SCS μ for the active UL BWP of the second UL carrier. SUL This μ SUL ≥μ SFI,SUL Set the reference SCS to satisfy μ SFI,SULIt is expected that this will be provided. For each slot format combination indicated by the SFI-index field of DCI format 2_0 for the reference 1st UL carrier, the active DL BWP and the active UL BWP of the 1st UL carrier will be provided from the first slot starting at the same point in time as the first slot of the reference 1st UL carrier. Applies to consecutive slots. Each slot format for the slot format combination of the reference second UL carrier is applied to the active UL BWP of the second UL carrier from the first slot starting at the same point in time as the first slot of the reference second UL carrier. Applies to consecutive slots of the dog.

[0382] If the BWP of the serving cell is set to μ=2 and the extended CP, the UE is set to μ SFI =0, μ SFI =1 or μ SFI =2 is expected. The format of a slot with an extended CP is determined from the format of a slot with a normal CP. The UE determines the extended CP symbol as a downlink / uplink / floating symbol if the overlapping normal CP symbols are each a downlink / uplink / floating symbol. The UE determines the extended CP symbol as a floating symbol if one of the overlapping normal CP symbols is a floating symbol. The UE determines the extended CP symbol as a floating symbol if the overlapping normal CP symbol pair includes a downlink symbol and an uplink symbol.

[0383] Reference SCS settings μ SFI , μ SFI,DL , μ SFI,UL , or μ SFI,SUL For FR1 it is 0, 1, or 2, and for FR2 it is 2 or 3.

[0384] For a set of symbols in a slot, the UE detects a DCI format 2_0 that includes an SFI-index field value indicating the set of symbols in the slot to be uplinked, and does not simultaneously detect a DCI format indicating to receive a PDSCH or CSI-RS in the set of symbols in the same slot.

[0385] For a set of symbols in a slot, the UE detects a DCI format 2_0 that includes an SFI-index field value indicating the set of symbols in the slot to be downlinked, and does not simultaneously detect a DCI format indicating to transmit a PUSCH, PUCCH, PRACH, or SRS in the set of symbols in the same slot, a RAR UL grant, a fallbackRAR UL grant, or successRAR.

[0386] For a set of symbols in a slot that is indicated to be within the remaining channel occupancy period via the Channel Occupancy Duration field or the SFI-index field by DCI Format 2_0, the UE shall not detect DCI Format 2_0 at a later point in time that indicates via the Channel Occupancy Duration field or the SFI-index field that no symbol in that set of symbols is within the remaining channel occupancy period.

[0387] For a set of symbols in a slot indicated as downlink / uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the UE does not detect DCI format 2_0 containing an SFI-index field value indicating the set of symbols in that slot as uplink / downlink or dynamic, respectively.

[0388] For the set of symbols of a slot corresponding to a candidate SS / PBCH block index of an SS / PBCH block, if the index is indicated in the physical cell ID associated with the active TCI state for PDCCH or PDSCH via ssb-PositionsInBurst of SIB1, ssb-PositionsInBurst of ServingCellConfigCommon, NonCellDefiningSSB, or ssb-PositionsInBurst of SSB-MTCAdditionalPCI if the UE is not provided with dl-OrJointTCI-StateList as described in Section 4.1, or for the set of symbols of a slot corresponding to an SS / PBCH block configured for L1 beam measurement / reporting, the UE does not detect a DCI format 2_0 containing an SFI-index field value indicating the set of symbols of the corresponding slot to uplink.

[0389] As described in Section 8.1, the set of symbols in a slot corresponding to a valid PRACH opportunity and the N symbols before the valid PRACH opportunity gap For the symbol, the UE does not detect DCI format 2_0 containing an SFI-index field value indicating the set of symbols for that slot to be downlinked.

[0390] For the symbol set of a slot indicated to the UE as CORESET for the Type0-PDCCH CSS set by pdcch-ConfigSIB1 of the MIB, the UE does not detect a DCI format 2_0 containing an SFI-index field value indicating the symbol set of that slot to the uplink.

[0391] For the set of symbols of a slot dynamically indicated to the UE by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated (if provided), or if tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the UE, if the UE detects a DCI format 2_0 that provides a format for a slot using a slot format value other than 255.

[0392] - If one or more symbols in the symbol set are symbols of a CORESET configured for PDCCH monitoring by the UE, the UE receives the PDCCH in the CORESET only if the SFI-index field value of DCI format 2_0 indicates that one or more of the symbols is a downlink symbol.

[0393] - If the SFI-index field value of DCI format 2_0 dynamically indicates a set of symbols of a slot and a DCI format is detected that instructs the UE to receive PDSCH or CSI-RS in the set of symbols of the slot, the UE receives PDSCH or CSI-RS in the set of symbols of the slot.

[0394] - If the SFI-index field value of DCI format 2_0 dynamically indicates the symbol set of a slot and the UE detects a DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR that instructs the UE to transmit PUSCH, PUCCH, PRACH, or SRS in the symbol set of the slot, the UE transmits PUSCH, PUCCH, PRACH, or SRS in the symbol set of the slot.

[0395] - If the SFI-index field value of DCI format 2_0 dynamically indicates the symbol set of the slot and the UE does not detect a DCI format that instructs the UE to receive PDSCH or CSI-RS in the symbol set of the slot, or if the UE does not detect a DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR that instructs the UE to transmit PUSCH, PUCCH, PRACH, or SRS in the symbol set of the slot, the UE does not transmit or receive in the symbol set of the slot.

[0396] - If the UE is configured by the upper layer to receive PDSCH or CSI-RS in the symbol set of a slot, the UE receives PDSCH or CSI-RS in the symbol set of the slot only when the value of the SFI-index field of DCI format 2_0 indicates the symbol set of the slot in the downlink and, if applicable, the symbol set is within the remaining channel occupancy period.

[0397] - If the UE is configured by the upper layer to receive DL PRS in the symbol set of a slot, the UE receives DL PRS in the symbol set of that slot only when the value of the SFI-index field of DCI format 2_0 downlink or dynamically indicates the symbol set of that slot.

[0398] - When the UE is configured by the upper layer to transmit PUCCH, PUSCH or PRACH in the symbol set of a slot, the UE transmits PUCCH, PUSCH or PRACH in the symbol set of a slot only when the value of the SFI-index field of DCI format 2_0 indicates the symbol set of the corresponding slot in the uplink.

[0399] - If the UE is configured by the upper layer to transmit SRS in the set of symbols of a slot, the UE transmits SRS only in a subset of the set of symbols of the slot indicated by the SFI-index field value of the DCI format 2_0 as uplink symbols.

[0400] - The UE shall not simultaneously detect a DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR that instructs the UE to transmit SRS, PUSCH, PUCCH, or PRACH in one or more symbols of the symbol set of the slot when the SFI-index field value of DCI format 2_0 indicates a set of symbols of the slot for downlink.

[0401] - The UE does not detect a case where the value of the SFI-index field of DCI format 2_0 indicates a downlink or dynamic symbol set of a slot containing symbols corresponding to a repetition of a PUSCH transmission activated by a UL Type 2 grant PDCCH as described in Section 10.2.

[0402] - The UE does not simultaneously detect a DCI format that instructs the UE to receive PDSCH or CSI-RS in one or more symbols of the symbol set of the slot when the SFI-index field value of DCI format 2_0 indicates a set of symbols of the slot for uplink.

[0403] When a UE is configured by a higher layer to receive CSI-RS or PDSCH in a set of symbols of a slot, if the UE detects a DCI format 2_0 indicating a slot format whose slot format value is not 255 and the slot format indicates a subset of the set of symbols to be uplink or flexibly transmitted, or a DCI format indicating that the UE transmits PUSCH, PUCCH, SRS or PRACH in at least one symbol of the set of symbols, the UE cancels reception of CSI-RS in the set of symbols of the slot or cancels reception of PDSCH in the slot.

[0404] For UE operation using shared spectrum channel access in FR1 or in FR2-2 with ChannelAccessMode2 = 'enabled', if the UE is configured by higher layers to receive CSI-RS and CO-DurationsPerCell is provided, the UE cancels CSI-RS reception for the set of symbols of slots indicated in downlink or dynamically by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, or if tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided, the UE cancels CSI-RS reception for the set of symbols of the corresponding slots that are not included in the remaining channel occupancy period.

[0405] If a UE is configured by a higher layer to receive DL PRS in a symbol set of a slot, and the UE detects a DCI format 2_0 indicating a slot format whose slot format value is not 255 and which indicates a subset of the symbol set for uplink, or a DCI format indicating that the UE transmits PUSCH, PUCCH, SRS or PRACH in at least one symbol of the symbol set, the UE cancels reception of DL PRS in the symbol set of the slot.

[0406] If the UE is configured by a higher layer to transmit SRS, PUCCH, PUSCH or PRACH in a set of symbols of a slot, and the UE detects DCI format 2_0 indicating a slot format whose slot format value is not 255 and the slot format indicates a subset of the set of symbols for downlink or flexibly, or if the UE detects a DCI format indicating that the UE receives CSI-RS or PDSCH in a subset of the set of symbols, then

[0407] - If the UE does not indicate the [partialCancellation] function, the UE shall transmit PUCCH, PUSCH or PRACH from the last symbol of the PDCCH reception in which the first symbol of the symbol set detects the DCI format. proc,2 If this occurs within the UE, the transmission is not canceled. Otherwise, the UE cancels the PRACH transmission on the actual repetition of the PUCCH, PUSCH, or PUSCH [6, TS 38.214] (determined according to clauses 9, 9.2.5 and 9.2.6 or clause 6.1 of [6, TS 38.214]) or symbol set.

[0408] - If the UE indicates the [partialCancellation] function, the UE shall receive T from the last symbol of the PDCCH reception that detected the DCI format. proc,2 The UE shall not cancel PUCCH, PUSCH or PRACH transmissions in symbols of the set of symbols occurring within the set of symbols. The UE shall cancel PRACH transmissions in symbols of the actual repetition of PUCCH, PUSCH or PUSCH [6, TS 38.214] or the remaining symbol set as determined by clauses 9, 9.2.5 and 9.2.6 or clause 6.1 of [6, TS 38.214].

[0409] - The UE receives T from the last symbol of the PDCCH reception that detected the DCI format. proc,2The UE does not cancel SRS transmissions in symbols in the subset of symbols that occur within the UE. The UE cancels SRS transmissions in symbols in the remaining subset of symbols.

[0410] - T proc,2 is the PUSCH preparation time for the corresponding UE processing capability, and d according to [6, TS 38.214]. 2,1 =1, μ is the SCS setting of PDCCH including DCI format and SCS setting of SRS, PUCCH, PUSCH or μ r corresponds to the smallest SCS setting among them. Here, μ r If the SCS setting of PRACH is 15 kHz or higher, it corresponds to the SCS setting of PRACH, otherwise μ r =0.

[0411] If the UE is configured by a higher layer to receive CSI-RS or is instructed to receive CSI-RS in one or more RB sets and symbol sets of a slot by detecting DCI format 0_1, and if the UE detects DCI format 2_0 and the bitmap indicates that any one or more of the RB sets is not receivable, the UE cancels CSI-RS reception in the symbol sets of the corresponding slot.

[0412] The UE considers a floating symbol of the CORESET configured in the UE for PDCCH monitoring as a downlink symbol if the UE does not detect an SFI-index field value of DCI format 2_0 indicating that the set of symbols in the slot is floating or uplink, and also does not detect a DCI format indicating that SRS, PUSCH, PUCCH or PRACH should be transmitted in the corresponding set of symbols.

[0413] For the set of symbols of a slot dynamically indicated by tdd-UL-DL-ConfigurationCommon and, if provided, tdd-UL-DL-ConfigurationDedicated, or if tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the UE, if the UE does not detect a DCI format 2_0 providing the slot format for that slot.

[0414] - The UE receives the PDSCH or CSI-RS in the symbol set of the corresponding slot, and this is done only if the UE has received a DCI format containing an indication for it.

[0415] - The UE transmits PUSCH, PUCCH, PRACH, or SRS in the symbol set of the corresponding slot, only if the UE has received a DCI format containing an indication for the same, a RAR UL grant, a fallbackRAR UL grant, or a successRAR.

[0416] - The UE receives the PDCCH as described in section 10.1.

[0417] - If the UE is configured by the upper layer to receive PDSCH in the symbol set of the slot, the UE does not receive PDSCH in the symbol set of the slot.

[0418] - If the UE is configured by the upper layer to receive CSI-RS in the symbol set of a slot, the UE shall not receive CSI-RS in the symbol set of that slot, except when CO-DurationsPerCell is provided and the symbol set of the slot is within the remaining channel occupancy period.

[0419] - If the UE is configured by the upper layer to receive DL PRS in the symbol set of the slot, the UE receives DL PRS in the symbol set of the slot.

[0420] - If the UE is configured by the upper layer to transmit SRS, PUCCH, PUSCH, or PRACH in the symbol set of the slot, but enableConfiguredUL is not provided,

[0421] - If the UE does not indicate the [partialCancellation] capability, the UE shall not cancel a transmission if the first symbol of a PUCCH, a PUSCH, an actual repetition of a PUSCH [6, TS 38.214] (determined according to clause 9, 9.2.5, 9.2.6 or clause 6.1 of [6, TS 38.214]), or a PRACH occurs in a slot within T_(proc,2) from the last symbol of a PDCCH reception configured to monitor DCI format 2_0. Otherwise, the UE shall cancel a transmission of a PUCCH, a PUSCH, an actual repetition of a PUSCH [6, TS 38.214], or a PRACH in the slot.

[0422] - If the UE indicates the [partialCancellation] feature, the UE shall receive T from the last symbol of PDCCH reception set to monitor DCI format 2_0. proc,2 The UE shall not cancel PUCCH, PUSCH, actual repetition of PUSCH [6, TS 38.214] (as determined by clauses 9, 9.2.5 and 9.2.6 or clause 6.1 of [6, TS 38.214]), or PRACH transmissions in symbols of the set of symbols occurring within the set of symbols. The UE shall cancel PUCCH, PUSCH, actual repetition of PUSCH [6, TS 38.214], or PRACH transmissions in symbols of the remaining set of symbols.

[0423] - The UE receives T from the last symbol of PDCCH reception set to monitor DCI format 2_0. proc,2The UE does not cancel SRS transmission in symbols of the set of symbols occurring within the set. The UE cancels SRS transmission in symbols of the remaining set of symbols.

[0424] - T proc,2 is the PUSCH preparation time for the corresponding UE processing capability, and d according to [6, TS 38.214]. 2,1 =1. μ is the SCS setting of PDCCH including DCI format 2_0 and SCS setting of SRS, PUCCH, PUSCH or μ r corresponds to the smallest SCS setting among them. Here, μ r If the SCS setting of PRACH is 15 kHz or higher, it corresponds to the SCS setting of PRACH, otherwise μ r =0.

[0425] - If the UE is configured by the upper layer to transmit SRS, PUCCH, PUSCH or PRACH in the symbol set of the slot and enableConfiguredUL is provided, the UE may transmit SRS, PUCCH, PUSCH or PRACH, respectively.

[0426] If a UE is performing unpaired spectrum operation in a cell of FR1 frequency band and scheduling restrictions according to RRM measurement [10, TS 38.133] do not apply, and if the UE detects a DCI format that indicates to transmit in a symbol set, there is no need to perform RRM measurement [10, TS 38.133] in another cell based on SS / PBCH block or CSI-RS reception containing at least one symbol of the symbol set.

[0427] TDD slot and / or symbol configuration can be determined through multiple technologies. For example, all UEs in a cell can be allocated a cell-specific DL / UL pattern through tdd-UL-DL-ConfigurationCommon. Additionally, the UE can receive UE-specific allocation of resources that were previously reserved as flexible slots and / or symbols through a dedicated RRC signal, tdd-UL-DL-ConfigurationDedicated. tdd-UL-DL-ConfigurationCommon can be transmitted through SIB1 or dedicated RRC signaling. In order for a specific slot and / or symbol to be configured as a flexible slot and / or symbol, it must be configured flexibly through both UE- and / or cell-specific slot configurations. In this case, since tdd-UL-DL-ConfigurationDedicated is optional, the network may not configure UE-specific slots and / or symbols. In this case, the DL / UL pattern configured based on tdd-UL-DL-ConfigurationCommon is used. If the UE does not receive the SlotFormatIndicator configuration, it may 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 SlotFormatIndicator configuration, the UE may 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.

[0428] In addition, the base station may not configure RO in resources allocated in slots and / or symbols for HD DL transmission, and the UE may not expect RO to be configured. 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 opportunity 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 reception symbol. gap If the number of symbols is greater than or equal to the number of symbols of the PRACH opportunity, the corresponding PRACH opportunity can be treated as a valid RO. On the other hand, if the RO is set through tdd-UL-DL-ConfigurationCommon, the PRACH opportunity of the resource set as the UL symbol or PRACH slot is not located before the SS / PBCH block resource or is located at least N times after the last SS / PBCH block repetition symbol. gap If the number of symbols is located after the RO, 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 restrictions is referred to as an invalid RO. Hereinafter, what is specified as a slot and / or symbol can be interpreted as a unit of slot and symbol. In addition, what is specified 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.

[0429] FIG. 10 illustrates an example of a structure for allocating SBFD slots 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 for which a DL slot or a dynamic slot is configured by a higher layer, some frequency resources of the SBFD slot may be configured as DL, i.e., SBFD DL subbands or DL ​​available PRB(s), and some frequency resources may be configured as UL, i.e., SBFD UL subbands or UL available PRB(s). Here, a frequency gap may be configured 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)).

[0430] 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 as a terminal capable of performing SBFD operations, and a legacy UE (1120) may be understood as a terminal capable of performing HD communication.

[0431] The legacy UE (1110) recognizes the allocated resource as a DL resource. Therefore, the legacy UE (1110) does not expect RO configuration as in the existing operation. However, the SBFD-aware UE (1120) recognizes the allocated resource as an SBFD resource, and therefore can expect RO configuration in the SBFD UL subband according to the new rule. The new rule regards the SBFD symbol as a floating symbol, which specifically means the condition 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 (1120).

[0432] FIG. 12 and FIG. 13 illustrate examples of flexible slots with SBFD configurations applied according to one embodiment of the present disclosure. FIG. 12 illustrates an example of a flexible slot when an RO is configured with a legacy RO configuration, and FIG. 13 illustrates an example of a flexible slot when an RO is configured with a separate RO configuration. A legacy UE (1220) treats the allocated resource as a flexible slot and therefore expects to 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 SBFD and therefore can expect RO configuration in the SBFD UL subband according to the new rules. Since both a legacy UE (1220) and an 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 settings and methods applied to RO are described below, but can be equally applied to the RO group.

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

[0434] In the present disclosure, a legacy RO may be understood as a resource that can be used by both 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. The following two methods may be proposed as methods for setting up a legacy RO and an SBFD-dedicated RO.

[0435] First, a method can be used in which legacy ROs and SBFD-dedicated ROs are supported through separate RO configurations. For this purpose, multiple RO configurations can be configured. In the present disclosure, a configuration in which multiple ROs are individually configured is referred to as a separate RO configuration. Fig. 14 illustrates an example of a multiple RO configuration according to an embodiment of the present disclosure. Referring to Fig. 14, it can be seen that the separate RO configurations RO1 and RO2 can be configured at different frequencies.

[0436] Second, a method may be used in which legacy ROs and SBFD-only ROs are supported through a single RO configuration. 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.

[0437] In the RRC CONNECTED state, an SBFD-aware UE can support both RACH configuration option 1 including Alternative 1-1 and RACH configuration option 2. Here, RACH configuration option 1 including Alternative 1-1 can be understood as including a configuration based only on existing parameters of a single RACH configuration using a single RACH configuration. For example, parameters related to PRACH transmit power control parameters or PRACH repetition can be defined separately for each RO type. RACH configuration option 2 can be understood as including an existing RACH configuration and an additional RACH configuration, i.e., two separate RACH configurations. Simultaneous activation of both options for a single UE is not supported.

[0438] For Option 1, including Alternative 1-1, whether and how to reinterpret msg1-FrequencyStart in rach-ConfigCommon, RO validation rules, or SSB-RO mapping rules may be reviewed.

[0439] For option 2, RO validation rules, SSB-RO mapping rules, and whether all parameters currently included in rach-ConfigCommon need to be included in additional RACH configurations can be reviewed.

[0440] Here, the UE does not need to support both options.

[0441] SBFD-aware UEs can perform PRACH transmissions via ROs of SBFD slots and UL slots. Legacy UEs can perform PRACH transmissions via ROs of UL slots and flexible slots that can be used as SBFD slots or non-SBFD slots. In this case, either separate RO configurations or shared RO configurations can be used. If both configurations are supported for the UE, upper layer signaling can be performed to indicate which RO configuration is used. For example, information on which of the two RO configurations to use can be conveyed via messages designed to convey information related to UL and / or DL ​​configurations (e.g., tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated). Therefore, whether SBFD is supported can be configured together with information related to RO configurations. If a specific configuration value is not configured, the shared RO configuration can be assumed as the default value.

[0442] The network explicitly indicates whether RACH configuration option 1 for SBFD random access operations is enabled on the network side.

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

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

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

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

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

[0448] - If the SBFD-aware UE has UL latency or UL coverage issues: A dedicated SBFD RO can be allocated to the SBFD slot and / or UL slot with separate RO configuration.

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

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

[0451] - 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. In this case, it should be considered that SBFD-aware UEs can perform PRACH transmissions in the RO of the SBFD UL subband.

[0452] - For RACH configuration option 1 including SBFD-aware UEs and Alternative 1-1: Existing ROs valid for non-SBFD UEs may be treated as valid for SBFD-aware UEs as well. The network determines whether to configure an RO in an SBFD symbol dynamically configured by tdd-UL-DL-ConfigurationCommon. If an existing RO is configured in an SBFD symbol dynamically configured by tdd-UL-DL-ConfigurationCommon, the network ensures that the RO is included within the UL available PRB.

[0453] - When separate RO configurations are applied: The base station sets the RO for SBFD-aware UEs in the SBFD slot and / or UL slot to RO configuration 2, and sets the RO for legacy UEs in the flexible slot, i.e., the SBFD slot and / or UL slot to RO configuration 1. At this time, for RO configuration 1 and RO configuration 2, the base station may configure RO only for the SBFD UL subband of the flexible slot to consider the SBFD-aware UE. However, if the RO is configured to overlap with resources outside the SBFD UL subband according to RO configuration 1, the SBFD-aware UE may follow the configuration of the RO in RO configuration 2.

[0454] - When the base station supports legacy UEs to transmit PRACH using only ROs allocated to non-SBFD slots: The base station sets all dynamic slots to DL before SBFD is applied. Afterwards, 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 allocated to UL slots.

[0455] Case 1-3: When part of SBFD is applied to DL slots or floating slots

[0456] FIG. 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. Therefore, the RO configuration can be configured by combining Case 1-1 and Case 1-2.

[0457] FIG. 19 illustrates an example of a RO configuration that considers the wideband of a UL slot based on a separate RO configuration according to one embodiment of the present disclosure. Referring to FIG. 19 , in the case of an SBFD slot, an SBFD-aware UE can only use the RO allocated to the SBFD UL subband. Therefore, as shown in FIG. 19 , new rules may be considered for how to handle ROs that overlap with gap subbands, SBFD DL subbands, or portions of the SBFD UL subband.

[0458] In an HD TDD environment, it may be assumed that SBFD is applied to some or all of the non-SBFD slots configured with DL symbols and floating symbols. The new PRACH configuration that can be applied to the RO of the non-SBFD slot and the RO of the SBFD slot needs to be distinguished from the existing RO configuration that is applied to the HD configured only with the non-SBFD slot. This is because in the case of the legacy RO used for the legacy UE, it is assumed that the wideband UL is used in the non-SBFD slot, but when the SBFD-aware UE uses the SBFD slot, it is assumed that the SBFD UL subband, not the wideband UL, is used. In the case of the RO configured for a resource other than the SBFD UL subband, it may be treated as invalid for the SBFD-aware UE. Even if the resource configured as the HD UL does not apply SBFD, the SBFD-aware UE follows the existing method in using the entire frequency resource of the HD UL, so the legacy RO does not cause a problem for the SBFD-aware UE according to the rules applicable to the non-SBFD. However, for ROs configurable in SBFD UL subbands, the behavior of legacy UEs must also be considered, as legacy UEs may treat the ROs as DL or floating slots.

[0459]

[0460] Specific embodiments of the present disclosure

[0461] 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 terminals in a wireless communication system. The present disclosure proposes a technique for determining the validity of ROs determined by terminals based on RO configurations. Specifically, a validation rule for an RO may be such that among the determined ROs, an RO included in the SBFD UL subband may be considered valid. Furthermore, resources for downlink signals and an RO may be simultaneously allocated within a single slot. Below, the RO configuration and validation rules will be discussed first.

[0462] RO setup and validation

[0463] In the present disclosure below, a legacy RO may be understood as a resource that both a legacy UE and an SBFD-aware UE can use for PRACH transmission, and an SBFD-dedicated RO may be understood as a resource that only an SBFD-aware UE can use for PRACH transmission. A description will be given of separate RO configurations below.

[0464] To configure legacy ROs and SBFD-dedicated ROs, at least one PRACH configuration may be configured for each of a plurality of terminals. At this time, an SBFD-aware UE may transmit PRACHs to the legacy ROs and SBFD-dedicated ROs, and a legacy UE may transmit PRACHs to the legacy ROs. The legacy ROs may be configured in UL slots and flexible slots configured via tdd-UL-DL-ConfigurationCommon carried by common RRC signaling and / or tdd-UL-DL-ConfigurationDedicated carried by dedicated RRC signaling. The SBFD-dedicated ROs may be configured in UL slots and SBFD slots configured via tdd-UL-DL-ConfigurationCommon carried by common RRC signaling and / or tdd-UL-DL-ConfigurationDedicated carried by dedicated RRC signaling.

[0465] FIG. 20 illustrates an example of ROs being configured in SBFD slots and UL slots for a legacy UE and an SBFD-aware UE according to one embodiment of the present disclosure. Referring to FIG. 20 , ROs can be configured with a degree of freedom equal to the bandwidth of a non-SBFD slot. In FIG. 20 , RO1 can be understood as a legacy RO, and RO2 can be understood as an SBFD-only RO.

[0466] Rules may be needed on how to handle ROs that overlap with a gap subband, a SBFD DL subband, or part of a SBFD UL subband. When SBFD is configured and / or indicated for DL ​​or dynamically configured time resources by tdd-UL-DL-ConfigurationCommon and / or tdd-UL-DL-ConfigurationDedicated, among the ROs configured by the separated RO configuration, the ROs included in the UL subbands are set as valid, and the other ROs may be set as invalid as follows.

[0467] - ROs that overlap with gap subbands are set to invalid.

[0468] - ROs that overlap with SBFD DL subbands are set to invalid.

[0469] - ROs that overlap with part of the SBFD UL subband are set to invalid.

[0470] Alternatively, the UE does not expect RO configuration under the above conditions. The above rule is based on the separate RO configuration for SBFD-only ROs, but is not limited thereto. For example, it can also be applied when the base station supports SBFD and the UE is a full duplex-aware UE.

[0471] For random access operations of SBFD-aware UEs, the following methods may be considered.

[0472] - How to use a single RACH configuration including enhancements: In this case, ROs in UL subbands within SBFD symbols may be valid for SBFD-aware UEs.

[0473] - Use of two separate RACH configurations (existing RACH configuration + additional RACH configuration): ROs in UL subbands within SBFD symbols configured by the additional RACH configuration may be valid for SBFD-aware UEs.

[0474] If the base station supports SBFD and supports the operation that allows the configured SBFD slots / symbols to fallback or convert to HD flexible slots and / or symbols or HD UL slots and / or symbols by specific signaling, the existing legacy RO validation, i.e., the RO validation rules used in TDD HD, can be applied as is.

[0475] When the base station and UE support SBFD, all or part of the DL resources and UL resources used by the base station may overlap. In this case, the ROs contained within the UL band or UL subband may overlap with the DL band or DL ​​subband. A full-duplex-aware UE can treat the ROs located within the UL band or UL subband as valid.

[0476] If the base station supports SBFD and the UE supports HD, all or part of the DL and UL resources used by the base station may overlap. In this case, the ROs contained within the UL band or UL subband may overlap with the DL band or DL ​​subband. The HD UE may treat the ROs located within the UL band or UL subband as valid.

[0477] Fig. 21 illustrates an example of a start OFDM symbol according to an embodiment of the present disclosure. As shown in Fig. 21, in a TDD HD environment, an RO that is not set before an SS / PBCH symbol in a RACH slot, i.e., an RO set after an SS / PBCH symbol in a RACH slot, may be treated as valid. On the other hand, after receiving a DL symbol or an SS / PBCH symbol, at least N gap RO set after the symbol can be treated as valid.

[0478] Fig. 22 illustrates an example of setting ROs in an SBFD environment according to an embodiment of the present disclosure. Referring to Fig. 22, when a validation rule applicable to a TDD HD environment is applied in an SBFD environment, ROs can be set based on SS / PHCH. Specifically, PRACH is set at least N times after SS / PBCH or DL ​​channel is transmitted. gap It can be transmitted via RO after the symbol. At this time, a new validation rule can be proposed based on the allocation of SBFD DL subbands and SBFD UL subbands to different UEs, respectively.

[0479] Fig. 23 illustrates a first example of configuring an RO in an SBFD environment according to an embodiment of the present disclosure. Fig. 24 illustrates a second example of configuring an RO in an SBFD environment according to an embodiment of the present disclosure. Referring to Fig. 23, in an SBFD environment, an RO may be considered valid even if it overlaps with an SS / PBCH, a DL channel, or a DL signal in time. Referring to Fig. 24, an RO may be considered valid even if it is located in a symbol ahead of an SS / PBCH. In an SBFD environment, a base station may transmit an SS / PBCH to a first UE and simultaneously receive a PRACH from a second UE through an RO (e.g., RO2 in Fig. 23, RO2 in Fig. 24). N gap,SBFD If this is set, N gap,SBFD Silver N gap and can be set to other values. For example, N gap,SBFD Silver N gap Set to a value less than or equal to N gap and can be set based on other parameter values. Specifically, N gap,SBFD Silver N gap and can be set to the sum of the offset values, and the offset values ​​can be set to negative values.

[0480] SBFD-aware UEs receive N from SS / PBCH or DL ​​channels and / or signals configured / indicated within non-SBFD slots according to the existing method. gap The RO set thereafter can be assumed or judged as valid. That is, a valid RO is at least N from the last DL non-SBFD symbol. gap can start after. Also, a valid RO must have at least N from SSB. gap You can start later.

[0481] Meanwhile, the SBFD-aware UE may configure and / or instruct the SS / PBCH, DL channel or DL ​​signal within the SBFD slot and the N gapRO set to an interval less than or equal to 1 can be treated as valid or assumed. Here, N gap An RO set to an interval less than 100 ms may be treated or assumed to be valid even if it overlaps with an SS / PBCH, DL channel, or DL ​​signal.

[0482] When transmission or reception of resources of SBFD DL subband and SBFD UL subband is allowed to overlap, the following operations may be allowed.

[0483] About Unpaired Spectrum

[0484] When SBFD is set:

[0485] - If the UE is not provided with tdd-UL-DL-ConfigurationCommon

[0486] - PRACH opportunities within the PRACH slot are valid within the flexible symbols.

[0487] - If the UE provides tdd-UL-DL-ConfigurationCommon, a PRACH opportunity within a PRACH slot is valid if the following conditions are met:

[0488] - within the UL symbol. or

[0489] - It is within the fluid symbol.

[0490] In other cases:

[0491] - 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 in that PRACH slot and is at least N after the last SS / PBCH block received symbol. gap Valid if it starts after the symbol, where N gapThe values ​​are given in Table 8.1-2, and if channelAccessMode = "semiStatic" is provided, it must not overlap with a set of consecutive symbols before the start of the next channel occupancy time, during which the UE shall not transmit. [15, TS 37.213]

[0492] - The candidate 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.

[0493] - If the UE is provided with tdd-UL-DL-ConfigurationCommon, a PRACH opportunity within a PRACH slot is valid if the following conditions are met:

[0494] - within the UL symbol, or

[0495] - Not preceding the SS / PBCH block in the PRACH slot, and at least N blocks after the last downlink symbol. gap symbol and at least N after the last SS / PBCH block symbol gap If it starts after the symbol. Here N gap The values ​​are given in Table 8.1-2, and if channelAccessMode = "semiStatic" is provided, it must not overlap with a set of consecutive symbols before the start of the next channel occupancy time, and there must be no transmission during that time. [15, TS 37.213]

[0496] - The candidate 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.

[0497] Therefore, during the time period in which SBFD is applied while TDD operation is performed, some FDD operations can be performed through DL subband resources and UL subband resources.

[0498] Fig. 25 illustrates a third example in which RO is set in an SBFD environment according to an embodiment of the present disclosure. Referring to Fig. 25, in an SBFD environment, when RO is set in the same manner as in a TDD environment in the same manner as in Fig. 21, at least N after SS / PBCH or DL ​​channel is transmitted gap,switch PRACH transmission can be performed through subsequent ROs (e.g., RO2 in Fig. 25). After receiving SS / PBCH, the terminal transmits at least N gap,switch PRACH can be transmitted to the subsequent RO (e.g., RO2 in Fig. 25).

[0499] Referring to Fig. 25, switching operations can be performed within an SBFD slot. At this time, switching operations can be allowed up to a predefined number. The predefined number can be set by the gNB through a higher layer. Switching operations can be set based on the capabilities of the UE. The base station can be N gap,switch Whether to support switching operations considering N can be set via higher-level signaling. For example, N gap,switch If the switching operation considering RO is supported, the SBFD-aware UE can perform SSB-to-RO mapping to the RO configured by the RO configuration, and then receive DL information in the SBFD DL subband of the SBFD symbol configured as the RO slot. After that, the UE capability is N gap,switch If the conditions for are satisfied, the UE can transmit the PRACH through a switching operation. The UE capability is N gap,switch If the conditions related to the switching operation are not satisfied, the UE cannot transmit the PRACH.

[0500] For RACH configuration option 1 including Alternative 1-1, for ROs within SBFD symbols configured for downlink by tdd-UL-DL-ConfigurationCommon, the following conditions may be supported in addition to the RO validation rules agreed upon in RAN1#116bis.

[0501] Condition 1: A valid RO is at least N from the last downlink non-SBFD symbol. gap Starts after the symbol(s).

[0502] Condition 2: A valid RO must have at least N from the SSB. gap Starts after the symbol(s).

[0503] Note: N here gap The value is N as specified in the current specification. gap is the same as

[0504] For RACH configuration option 2, a dedicated RO is valid if the following conditions are met. Here, a dedicated RO can be understood as an additional RO configured by the RO configuration added for SBFD.

[0505] - A dedicated RO may be within an SBFD symbol, or the network may be configured to start at an SBFD symbol and end at a non-SBFD symbol within the same slot or across different slots.

[0506] - A dedicated RO must be at least N after the last downlink non-SBFD symbol. gap It starts after the symbol passes.

[0507] -Dedicated RO is at least N after the latest SSB gap It starts after the symbol passes.

[0508] - Dedicated RO does not overlap with SSB in the time domain.

[0509] Note 1: Here N gap The value is N as specified in the current specification. gap is the same as

[0510] Note 2: It is the network's responsibility to ensure that dedicated ROs are configured within the bandwidth of the UL available PRBs.

[0511]

[0512] FIG. 26 illustrates an example of a procedure in which a terminal performs random access using ROs determined based on an SBFD slot according to an embodiment of the present disclosure. FIG. 26 illustrates a method performed by a device included in a communication system (e.g., an SBFD-aware UE (1110) of FIG. 11 , an SBFD-aware UE (1210) of FIG. 12 , and an SBFD-aware UE (1310) of FIG. 13 ). The terminal, which is the operating subject of FIG. 26 , can be understood as an SBFD terminal capable of performing an SBFD operation.

[0513] Referring to Figure 26, in step S2601, 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)).

[0514] In step S2603, 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).

[0515] In step S2605, the terminal verifies at least one valid RO based on the system information block. To this end, the terminal can receive configuration information for multiple 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 multiple 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 ROs. 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 multiple ROs.

[0516] For example, information related to multiple ROs can be determined or obtained based on information related to a slot pattern (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. 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.

[0517] The terminal may determine a plurality of ROs based on the RO configuration, determine whether the plurality of ROs are valid, and confirm or determine at least one valid RO. Here, the at least one valid RO may be determined based on at least one of a slot pattern, a UL subband frequency, or a DL subband frequency. For example, among the plurality of ROs, an RO included in the SBFD UL subband in the frequency axis may be determined to be valid. On the other hand, among the plurality of ROs, an RO that overlaps with a gap subband or an SBFD DL subband in the frequency axis may be treated as invalid. In addition, the terminal may treat as valid only an RO existing within the UL subband frequency resource of the SBFD slot. In addition, when a switching operation in which transmission of a downlink signal and a preamble is performed simultaneously within one SBFD slot, only ROs starting after symbols of a specific gap symbol value than the downlink signal may be treated as valid. Here, the downlink signal may include an SSB.

[0518] In step S2607, the terminal transmits a preamble using at least one of the multiple 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, an UL subband frequency, or a DL subband frequency, and may be performed according to various embodiments described above.

[0519] At step S2609, 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 specifically include at least one of a timing advance command, an uplink grant, and a temporary C-RNTI. Subsequently, although not illustrated in FIG. 26, 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.

[0520] Although it has been described in FIG. 26 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.

[0521]

[0522] FIG. 27 illustrates an example of a procedure in which a base station performs random access using ROs determined based on an SBFD slot, according to one embodiment of the present disclosure. FIG. 27 illustrates the method performed by the base station. In FIG. 27, the terminal can be understood as an SBFD terminal capable of performing SBFD operations.

[0523] Referring to FIG. 27, in step S2701, 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. Here, the configured ROs may include ROs included in the SBFD UL subband on the frequency axis.

[0524] In step S2703, 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.

[0525] In step S2705, 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.

[0526] In step S2707, 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.

[0527] In step S2709, 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. 27, 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.

[0528] Although SBFD terminals are described in FIG. 27, 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. To enable non-SBFD terminals and SBFD terminals to seamlessly transmit PRACHs, the base station may consider SBFD subbands to determine RO locations or configure some ROs to be classified as invalid. Accordingly, each RO configured by separate RO configurations may be configured in a different frequency band.

[0529]

[0530] FIG. 28 illustrates an example of a procedure for performing random access between a base station and a terminal according to one embodiment of the present disclosure. In FIG. 28, a UE operating in HD is referred to as a legacy UE (2820), and a UE operating in SBFD is referred to as an SBFD-aware UE (2830). Referring to FIG. 28, UEs with different RO settings can perform a random access procedure without collision.

[0531] In step S2801, the base station (2810) transmits SSBs to the legacy UE (2820) and the SBFD-aware UE (2830). The legacy UE (2820) and the SBFD-aware UE (2830) may receive some of the SSBs. In this embodiment, it is assumed that the legacy UE (2820) receives the first SSB, and the SBFD-aware UE (2830) receives the second SSB. The legacy UE (2820) and the SBFD-aware UE (2830) may obtain information that allows them to receive system information (e.g., SIB) based on the received SSBs.

[0532] In step S2803, the base station (2810) transmits SIB1 to the legacy UE (2820) and the SBFD-aware UE (2830). 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 (2820) may receive SIB1 after performing synchronization with the base station (2810) based on the first SSB.

[0533] In step S2805, the legacy UE (2820) transmits a preamble using the first RO to the base station (2810). The legacy UE (2820) 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 (2820) via a separate message. The legacy UE (2820) can determine the first RO corresponding to the first SSB by performing SSB-to-RO mapping.

[0534] At step S2807, the legacy UE (2820) receives a random access response from the base station (2810). After transmitting the preamble, the legacy UE (2820) 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.

[0535] In step S2809, the SBFD-aware UE (2830) transmits a preamble using the second RO to the base station (2810). The SBFD-aware UE (2830) 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 (2830) via a separate message. The SBFD-aware UE (2830) 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 (2830) may be configured to avoid conflict with the RO configuration for the legacy UE (2820). For example, ROs may first be configured to be valid for a legacy UE (2820), and then a SBFD-aware UE (2830) may be configured to use only ROs valid for the SBFD-aware UE (2830) among the configured ROs. In this case, some FDD operations may be performed via DL subband resources and UL subband resources. For example, the second RO may overlap with the first SSB or the second SSB within one SBFD slot. Additionally, the second RO may be configured to start later than a specific downlink signal by a gap symbol value in time.

[0536] In step S2811, the SBFD-aware UE (2830) receives a random access response from the base station (2810). After transmitting the preamble, the SBFD-aware UE (2830) 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.

[0537]

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

[0539]

[0540] Fig. 29 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.

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

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

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

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

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

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

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

[0548] According to FIG. 30, 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).

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

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

[0551] FIG. 31 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.

[0552] Referring to FIG. 31, 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).

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

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

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

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

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

[0558] Fig. 32 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.

[0559] Referring to FIG. 32, 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).

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

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

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

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

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

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

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

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

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

[0569] According to FIG. 33, 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.

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

[0571] 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. 33 may be the memory (12, 22) of FIG. A.

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

[0573] 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. 33 may be the transceiver (13, 23) of FIG. A.

[0574] Although not shown in FIG. 33, 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).

[0575] Fig. 33 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. 33. That is, some components, such as a keypad (2320), a Global Positioning System (GPS) chip (2360), a sensor (2365), and a SIM card (2325), may not be essential elements, and in this case, may not be included in the terminal.

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

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

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

[0579] Referring to FIG. 34, 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0593] 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 at least one valid random access channel occasion (RO) based on the above system information block; a step of transmitting a preamble to the base station using the at least one valid RO; and A step of receiving a response message to the preamble from the base station, A method wherein the at least one valid RO includes an RO included in uplink (UL) usable physical resource blocks (PRBs) for sub-band full duplex (SBFD) in the frequency axis among a plurality of ROs.

2. In claim 1, A method in which among the above multiple ROs, an RO that overlaps with a gap subband on the frequency axis is set to be invalid.

3. In claim 1, A method in which among the above multiple ROs, ROs that overlap with DL (downlink) available PRBs for SBFD on the frequency axis are set to be invalid.

4. In claim 1, A method wherein at least one valid RO starts after a predefined number of symbols from the last non-SBFD symbol.

5. In claim 1, A method wherein at least one valid RO starts after a predefined number of symbols from the SSB.

6. In claim 1, A method wherein at least one valid RO starts from a symbol in the same slot as a signal received in DL available PRBs for SBFD.

7. In claim 1, A method wherein at least one valid RO starts after a predefined number of symbols from an SSB received in DL available PRBs for SBFD.

8. In claim 7, The above predefined number is determined based on terminal capability or offset value.

9. In claim 8, The above offset value is determined as a negative integer.

10. In claim 1, The above system information block comprises separated RO configurations.

11. In paragraph 10, The above separated RO settings include a first RO setting and a second RO setting, The RO valid for a non-SBFD terminal is determined based on the first RO setting, A method in which a valid RO for an SBFD terminal is determined based on the first RO setting and the second RO setting.

12. In paragraph 11, A valid RO for the above SBFD terminal is a method that starts from an SBFD symbol and ends with a non-SBFD symbol.

13. In claim 1, It further includes 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.

14. 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 using at least one valid RO among the plurality of ROs from the terminal; and A step of receiving a response message to the preamble from the terminal, A method wherein the at least one valid RO includes an RO included in uplink (UL) usable physical resource blocks (PRBs) for sub-band full duplex (SBFD) in the frequency axis among a plurality of ROs.

15. In claim 14, The above system information block includes separated RO configurations, A method in which each of the ROs set by the above separated RO settings is set in a different frequency band.

16. 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 at least one valid RO (random access channel occasion) based on the above system information block, Transmitting a preamble to the base station using at least one valid RO, Set to receive a response message to the preamble from the base station, A device in which at least one valid RO is included in uplink (UL) usable physical resource blocks (PRBs) for sub-band full duplex (SBFD) on the frequency axis among a plurality of ROs.

17. 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 valid RO among the plurality of ROs, Set the terminal to receive a response message to the preamble, A device in which at least one valid RO is included in uplink (UL) usable physical resource blocks (PRBs) for sub-band full duplex (SBFD) on the frequency axis among a plurality of ROs.

18. 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 at least one valid random access channel occasion (RO) based on the above system information block; a step of transmitting a preamble to the base station using the at least one valid RO; and A step of receiving a response message to the preamble from the base station, A terminal including at least one valid RO, wherein the RO is included in uplink (UL) usable physical resource blocks (PRBs) for sub-band full duplex (SBFD) on the frequency axis among a plurality of ROs.

19. 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 at least one valid RO (random access channel occasion) based on the above system information block, Transmitting a preamble to the base station using at least one valid RO, Set to receive a response message to the preamble from the base station, A computer-readable medium comprising at least one valid RO, wherein the RO is included in uplink (UL) usable physical resource blocks (PRBs) for sub-band full duplex (SBFD) in the frequency axis among a plurality of ROs.

Images