Method and apparatus for performing random access of terminal aware of subband full duplex communication in wireless communication system

Abstract

The present disclosure relates to physical random access channel (PRACH) repetition in which a terminal receives at least one random access channel (RACH) configuration from a network and the terminal performs PRACH repetition on the basis of the at least one RACH configuration, wherein: the terminal is a subband full duplex (SBFD) aware UE that is aware of SBFD; and the PRACH repetition is performed on the basis of any one type of random access channel occasions (ROs) from among i) valid legacy ROs and ii) valid additional ROs.

Description

Method and device for performing random access of a terminal recognizing subband full-duplex communication in a wireless communication system

[0001] The present disclosure relates to a wireless communication system, and to a method and device for performing random access of a terminal recognizing subband full duplex (SBFD) communication.

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

[0004] Wireless communication systems, whether NR or later, can perform full duplex (FD) operation. In FD operation, a device can simultaneously perform downlink reception and uplink transmission within a specific time resource. This differs from half duplex (HD) operation, which can perform either downlink reception or uplink transmission within a specific time resource.

[0005] For FD operation, some frequency resources in the same time resource can be allocated as downlink subbands for downlink communication, and other frequency resources can be allocated as uplink subbands for uplink communication. This can be called subband full duplex (SBFD). Alternatively, for FD operation, frequency resources that can be used for both downlink and uplink communication can be allocated in the same time resource. This can be called spectrum-sharing full duplex (SSFD).

[0006] Meanwhile, in an environment where the aforementioned SBFD is used in a wireless communication system, it is necessary to specify how an SBFD-aware UE performs a random access process. In the conventional technology, a RACH opportunity (abbreviated as RO) for transmitting a preamble for random access was set only on HD resources. However, in NR or post-NR wireless communication systems, RO may be set not only on HD resources but also on SBFD resources. In this case, it should be taken into account that uplink resources in the frequency domain may be limited in SBFD resources compared to HD resources.

[0007] Additionally, the random access channel configuration method may vary, taking into account existing UEs (i.e., non-SBFD aware UEs) and UEs that are aware of SBFD. In this case, it is necessary to specify how SBFD aware UEs perform the random access process, particularly the PRACH transmission, which repeatedly transmits the preamble across multiple ROs (also referred to as PRACH repetition).

[0008] The technical problem to be solved by the present disclosure is to provide a method for performing random access of a terminal recognizing subband full-duplex communication (SBFD) in a wireless communication system and a device using the method.

[0009] A method for performing random access of a terminal aware of subband full duplex (SBFD) communication in a wireless communication system and a device using the method are provided. According to the method, a user equipment (UE) receives at least one random access channel (RACH) configuration from a network, and performs physical random access channel (PRACH) repetition based on the at least one RACH configuration, wherein the UE is a subband full duplex (SBFD) aware UE, and the PRACH repetition is performed based on one type of ROs among i) valid legacy ROs and ii) valid additional ROs.

[0010] In another aspect, a terminal, device, or computer-readable medium for executing the above method is provided.

[0011] In another aspect, a method of operating a base station and a base station using the method are provided. According to the method of operating the base station, the base station transmits at least one random access channel (RACH) configuration to a subband full duplex (SBFD) aware user equipment (SBFD-aware user equipment), and the base station repeatedly receives a physical random access channel (PRACH) from the SBFD-aware user equipment based on the at least one RACH configuration, wherein the repeated reception of the PRACH is performed based on one type of RO among i) valid legacy ROs and ii) valid additional ROs.

[0012] According to the present disclosure, by clearly defining a method for repeating PRACH transmission of an SBFD-aware terminal in a situation where legacy ROs and additional ROs coexist, ambiguity with the network can be prevented.

[0013] In some cases, simply increasing the number of PRACH repetitions based on channel conditions may not be sufficient for successful communication. In such cases, changing the RO type allows for efficient PRACH repetition for SBFD-aware terminals.

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

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

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

[0017] FIG. 2 illustrates the structure of a radio frame of NR according to one embodiment of the present disclosure.

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

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

[0020] FIG. 5 illustrates an example of a method for applying full duplex within a carrier (Intra-carrier) according to an embodiment of the present disclosure.

[0021] FIG. 6 illustrates 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.

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

[0023] Figure 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 2, and the number of SSBs per RO is 1 / 2.

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

[0025] FIG. 10 illustrates an example of a structure in which SBFD slots are allocated in the time and frequency axes according to one embodiment of the present disclosure.

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

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

[0028] FIG. 14 illustrates an example of a separated RO setup according to one embodiment of the present disclosure.

[0029] FIG. 15 illustrates a shared RO configuration according to one embodiment of the present disclosure.

[0030] 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 a UL slot.

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

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

[0033] Figure 19 illustrates RO settings by legacy RACH settings and RO settings by additional RACH settings.

[0034] Figure 20 is another example of RO configuration by legacy RACH configuration and RO configuration by additional RACH configuration.

[0035] Figure 21 illustrates RO configuration by a single RACH configuration.

[0036] Figure 22 illustrates terminal operation according to one embodiment of the present disclosure.

[0037] FIG. 23 illustrates an operation method of a base station according to one embodiment of the present disclosure.

[0038] FIG. 24 illustrates signaling and operation between a base station and a terminal according to one embodiment of the present disclosure.

[0039] Figure 25 illustrates valid legacy ROs (RO1) and valid additional ROs (RO2) when using RACH configuration option 1.

[0040] Figure 26 illustrates valid legacy ROs (RO1) and valid additional ROs (RO2) when using RACH configuration option 2.

[0041] Figure 27 illustrates a wireless device applicable to the present specification.

[0042] Figure 28 illustrates an example of a signal processing module structure.

[0043] Figure 29 illustrates another example of the structure of a signal processing module within a transmission device.

[0044] FIG. 30 illustrates an example of a wireless communication device according to an implementation example of the present disclosure.

[0045] Figure 31 illustrates another example of a wireless device.

[0046] Fig. 32 illustrates a communication system (1) applicable to this specification.

[0047] The following embodiments combine the 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.

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

[0049] Throughout the specification, when a part is said to "comprising" or "including" a component, this does not mean that other components may be included, but rather that other components may be excluded, unless otherwise specifically stated. 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.

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

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

[0052] 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). Hereinafter, for convenience, the terminal may be referred to as UE.

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

[0054] 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 5G (5th generation) NR (New Radio) system and 3GPP2 system, for example, 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.

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

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

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

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

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

[0060] 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 be an example of a next-generation wireless communication system. "xxx" refers to a standard document detail number. LTE / NR / 6G may be collectively referred to as a 3GPP system.

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

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

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

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

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

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

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

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

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

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

[0071] Referring to Fig. 1, when a terminal is powered on again after being powered off or when it newly enters a cell, it performs an initial cell search operation, such as synchronizing with the base station (S11). 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 obtain broadcast information within the cell by receiving a physical broadcast channel (PBCH) signal from the base station. Meanwhile, the terminal can check the downlink channel status by receiving a downlink reference signal (DL RS) during the initial cell search phase.

[0072] After completing initial cell search, the terminal performs system information reception (S12). For example, the terminal can obtain more specific system information by receiving the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Control Channel (PDSCH) based on the PDCCH information.

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

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

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

[0076] The control information transmitted from a terminal to a base station is referred to as uplink control information (UCI). UCI may include at least one of HARQ ACK / NACK (Hybrid Automatic Repeat and request Acknowledgement / Negative-ACK), SR (Scheduling Request), and CSI (Channel State Information). CSI may include at least one of CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), and RI (Rank Indication). UCI is generally transmitted periodically through PUCCH, but may be transmitted through PUSCH when control information and data must be transmitted simultaneously. Additionally, the terminal may transmit UCI aperiodically through PUSCH according to a request / instruction from the network.

[0077] Wireless Resource Structure

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

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

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

[0081] When normal CP is used, the number of symbols per slot (N) depends on the SCS setting (μ). slot symb ), number of slots per frame (N frame,μ slot ) and the number of slots per subframe (N subframe,μ slot ) may vary.

[0082] Table A below illustrates the SCS settings μ.

[0083] [Table A]

[0084]

[0085] The following table B shows the number of symbols in a slot (N) according to the SCS setting μ slot symb ), number of slots in the frame (N frame,μ slot ), number of slots in a subframe (N subframe,μ slot ) is an example.

[0086] [Table B]

[0087]

[0088] Table C below shows the number of symbols in a slot (N) according to the SCS setting μ when extended CP is used. slot symb ), number of slots in the frame (N frame,μ slot ), number of slots in a subframe (N subframe,μ slot) is an example.

[0089] [Table C]

[0090]

[0091] In an NR system, OFDM(A) numerology (e.g., SCS, CP length, etc.) may be set differently between multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., subframe, slot, or TTI) (conveniently referred to as TU (Time Unit)) set to the same number of symbols may be set differently between the merged cells.

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

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

[0094] [Table D]

[0095]

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

[0097] [Table E]

[0098]

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

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

[0101] A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) may be defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) may be defined as multiple consecutive (P)RBs ((Physical) Resource Blocks) in the frequency domain, and may correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 4 or 5) BWPs. Data communication may be performed through active BWPs. Each element may be referred to as a Resource Element (RE) in the resource grid, and one complex symbol may be mapped to it.

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

[0103] 1. DL only setting

[0104] 2. UL only setting

[0105] 3. Mixed UL-DL settings

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

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

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

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

[0110] 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, downlink control information (DCI), such as DL data scheduling information and UL data scheduling information, can be transmitted. In the PUCCH, unified control information (UCI), such as ACK / NACK (Positive Acknowledgement / Negative Acknowledgement) information for DL ​​data, CSI (Channel State Information) information, and SR (Scheduling Request), can be transmitted. A guard period (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 as GP.

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

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

[0113] Transmission Action:

[0114] Common SN;

[0115] Separate header compression for source and target cells;

[0116] Separate encryption for source and target cells.

[0117] Receiving action:

[0118] Separate decryption for source and target cells;

[0119] Individual header restoration for source and target cells;

[0120] Common PDCP reordering;

[0121] Sequential delivery and duplicate detection;

[0122] Common buffer management.

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

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

[0125] UE RF / baseband requirements

[0126] 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. This works in most cases for UEs with Dual Rx / Dual Tx chains, but may require further restrictions for UEs with Dual Rx / Single Tx RF chains or Single Rx / Single Tx RF chains.

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

[0128] 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 time division multiplexing (TDM) pattern is required, which increases additional interruption time and UL switching complexity. However, this UE option provides various 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).

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

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

[0131] Describes DAPS-HO in standard specifications (e.g. TS 38.213).

[0132] When a UE indicates capability for DAPS HO, the UE may be provided with a source Master Cell Group (MCG) and a target MCG.

[0133] When the UE is configured with MCG and SCG (Secondary Cell Group) 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.

[0134] If the UE indicates UplinkPowerSharingDAPS-HO = Semi-static-mode1 and is provided with UplinkPowerSharingDAPS-HO-mode = Semi-static-mode1, 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 MCG.

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

[0136] When the UE indicates UplinkPowerSharingDAPS-HO = Dynamic and is provided with UplinkPowerSharingDAPS-HO-mode = Dynamic, 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 MCG.

[0137] If the UE does not provide UplinkPowerSharingDAPS-HO and transmissions from the target cell and the source cell overlap, the UE performs transmissions only in the target cell.

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

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

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

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

[0142] UE is N for target MCG cells targetA 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, and N for the source MCG. cells source 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 will it have a USS set that does not have a PDCCH candidate allocated for both the target MCG and the source MCG.

[0143] Full duplex operation for NR

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

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

[0146] FIG. 5 illustrates an example of a method for applying full duplex within a carrier (Intra-carrier) according to an embodiment of the present disclosure.

[0147] Referring to Fig. 5, the structure of DL and UL allocation on the frequency axis for subband-wise full duplex (SBFD) and spectrum-sharing full duplex (SSFD) can be identified. In the case of SBFD, 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 SSFD, 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 (FD) communication can be used in conjunction with existing half-duplex (HD) 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, SBFD or SSFD operations can be performed.

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

[0150] Referring to (a) of Fig. 6, some time resources are used for SBFD-based communication, and the remaining time resources are used for HD-based communication. Referring to (b) of Fig. 6, some time resources are used for SSFD-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.

[0151] In a time resource operating in SBFD, some frequency resources are used as DL resources, and some frequency resources are used as UL resources. For convenience of explanation, in the present disclosure, among the total frequency resources in a time resource operating in FD, the frequency resources operating in DL may be referred to as DL subbands, and the frequency resources operating in UL may be referred to as UL subbands.

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

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

[0154] Below, a random access procedure / process is described. The present disclosure proposes a method for setting bandwidth part (BWP) resources for intra-carrier full duplex communication based on the following random access procedure.

[0155] RACH (random access channel) procedure

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

[0157] Settings for PRACH transmission.

[0158] Preamble Index, Preamble SCS, P PRACH,target , the corresponding RA-RNTI, and PRACH resources.

[0159] PRACH is a PRACH format and transmission power P selected from the designated PRACH resources. PRACH,b,f,c (i) is transmitted using

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

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

[0162] For Type-2 random access procedures (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.

[0163] 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 is mapped to preamble index n·N. preamble total Starting from / N, where N preamble totalis 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.

[0164] 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 n·N. preamble total Starting from / N+R, where N preamble total is provided by totalNumberOfRA-Preambles.

[0165] For link recovery, the UE is provided with N SS / PBCH block indices associated with one PRACH opportunity by ssb-perRACH-Occasion of 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 of 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.

[0166] The SS / PBCH block index is provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon and can be mapped to valid PRACH opportunities in the following order, depending on certain parameters:

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

[0168] Second, in ascending order of the frequency resource index of the frequency multiplexing PRACH opportunity.

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

[0170] Fourth, in ascending order of the PRACH slot index.

[0171] The association period for mapping SS / PBCH block indices to PRACH opportunities starts from frame 0 and is N at least once within the association period. Tx SSB The SS / PBCH block indices are the smallest value in the set determined from the PRACH configuration period so that they are mapped to PRACH opportunities. Here, the UE is N Tx SSB is obtained from the ssb-PositionsInBurst value of SIB1 or ServingCellConfigCommon. After an integer number of periods mapping SS / PBCH block indices to PRACH opportunities within the association period, N Tx SSBIf there are PRACH opportunities or sets of PRACH preambles that are not mapped to SS / PBCH block indices, no SS / PBCH block index is mapped to the PRACH opportunities or sets of PRACH preambles. 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.

[0172] For PRACH transmissions triggered by a PDCCH command, the PRACH mask index field 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 provided, the PRACH opportunity is slot n+2 of UL BWP μ ·K cell,offset Here, n is the slot of UL BWP for PRACH transmission overlapping with the end of PDCCH command reception, μ is the SCS setting for PRACH transmission, and T TA Assume =0. If a PDCCH reception for a PDCCH command includes two PDCCH candidates from two related search space sets based on searchSpaceLinking, the last symbol of the PDCCH reception is the last symbol of the PDCCH candidate that ends later. A PDCCH reception includes both PDCCH candidates even if the UE does not need to monitor either of the two PDCCH candidates.

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

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

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

[0176] First, in ascending order of the frequency resource index of the frequency multiplexing PRACH opportunities.

[0177] Second, within a PRACH slot, time multiplexing PRACH opportunities in ascending order of time resource index.

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

[0179] For PRACH transmissions triggered by a request from a higher layer, if csirs-ResourceList is provided, the value of ra-OccasionList indicates a 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.

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

[0181] [Table 1]

[0182]

[0183] For paired spectrum or supplementary uplink bands, all PRACH opportunities are valid.

[0184] For unpaired spectra:

[0185] If the UE is not provided with tdd-UL-DL-ConfigurationCommon, it is not before the SS / PBCH block in the PRACH slot and at least N symbols after the last SS / PBCH block received. gap Starting after the symbol, the PRACH opportunity within the PRACH slot is valid. The above N gap is provided in Table 2 below. 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.

[0186] The candidate SS / PBCH block index of the SS / PBCH block may correspond to the SS / PBCH block index provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon.

[0187] If the UE is provided with a TDD configuration (e.g., tdd-UL-DL-ConfigurationCommon), a PRACH opportunity within a PRACH slot is valid under the following conditions:

[0188] within the UL symbol, or

[0189] Not preceding the SS / PBCH block within the PRACH slot, and at least N blocks after the last downlink symbol. gapsymbol, and at least N symbols after the last SS / PBCH block symbol. gap If it starts after the symbol. The above N gap is provided in Table 2 below. 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 must be performed.

[0190] The candidate SS / PBCH block index of the SS / PBCH block may correspond to the SS / PBCH block index provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon.

[0191] For certain preamble formats (e.g., preamble format B4), N gap =0 may be.

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

[0193] [Table 2]

[0194]

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

[0196] N T,2 is the time corresponding to N2 symbols corresponding to the PUSCH preparation time for UE processing capability 1, and μ corresponds to the smaller SCS setting between the SCS setting of the PDCCH command and the SCS setting of the corresponding PRACH transmission.

[0197] If the active UL BWP does not change, △BWPSwitching=0, otherwise △BWPSwitching can be defined in the standard specification.

[0198] For FR1, △ Delay =0.5 msec, and for FR2, △ Delay =0.25 msec.

[0199] T switch is the switching gap duration.

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

[0201] 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, and N=32 for μ=6, where μ is the SCS setting of the active UL BWP. If the PUSCH transmission uses repetition type B, this condition applies to each actual repetition of the PUSCH transmission.

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

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

[0204] [Table 3]

[0205]

[0206]

[0207]

[0208]

[0209]

[0210]

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

[0212] [Table 4]

[0213]

[0214]

[0215]

[0216]

[0217]

[0218]

[0219]

[0220] [Table 5] shows the supported △f RA and corresponding to the combination of △f It represents.

[0221] [Table 5]

[0222]

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

[0224] Referring to Fig. 7, when the PRACH setting index is, for example, 28, the position of the RO on the time axis can be represented as in Fig. 7. The RO is allocated for each frame set to 40 slots, and three ROs can be set in each slot.

[0225] OFDM baseband signal generation for PRACH

[0226] Time-series signal s at antenna port p for PRACH l (p,u) (t) can be defined as in Equation 1.

[0227] [Formula 1]

[0228]

[0229] Here t start RA ≤t <t start RA +(N u + N CP,l RA )T c And, is provided by standard specifications.

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

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

[0232] N BWP,i start is the resource block with the lowest number in the initial uplink bandwidth portion during the initial connection, and is determined by the upper layer parameter initialUplinkBWP. If it is not the initial connection, N BWP,i start is the resource block with the lowest number in the active uplink bandwidth portion, and is determined by the upper layer parameter BWP-Uplink.

[0233] n RA startis the frequency offset of the lowest PRACH transmission opportunity in the frequency domain for physical resource block 0 of the active uplink bandwidth portion. n RA star t is provided by the upper layer parameter msgA-RO-FrequencyStart and applies if a type-2 random access procedure has been started. Otherwise, it is provided by msg1-FrequencyStart.

[0234] n RA is the frequency domain PRACH transmission opportunity index at a given time instance for a particular PRACH transmission opportunity.

[0235] N RB RA is the number of occupied resource blocks, which can be provided by parameter allocation expressed as the number of resource blocks for PUSCH.

[0236] N RB,UL,n start,μ is RB n,UL start,μ 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.

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

[0238] L RA and N u can be provided by standard specifications.

[0239] N CP,l RA = N CP RA+ n·16k, and △f RA When ∈{1.25, 5}kHz, n=0, and △f RA If ∈{15, 30, 60, 120, 480, 960}kHz, then n is the interval [t start RA , t start RA + (N u RA +N CP RA )T c ) within this subframe, time instance 0 or time instance (△f max N f / 2000)T c = The number of times it overlaps with 0.5ms.

[0240] Starting position of PRACH preamble start RA is a subframe (△f RA ∈{1.25, 5, 15, 30}kHz) or in the 60 kHz slot (△f RA ∈{60,120,480,960}kHz), which is given by [Equation 2].

[0241] [Formula 2]

[0242]

[0243] Here, we assume that the subframe or 60 kHz slot starts at t=0.

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

[0245] N u μ and N CP,l-1 μ can be provided by standard specifications.

[0246] △f RA If ∈{1.25, 5}kHz, then μ=0 should be assumed, otherwise the value of μ is △f RA ∈{15, 30, 60, 120, 480, 960}kHz, and the symbol position l is l=l0+n tRA N dur RA +14n slot RA is given as:

[0247] Here, l0 can be provided by the "starting symbol" parameter.

[0248] N t RA is the PRACH transmission opportunity within the PRACH slot, from 0 to N within the RACH slot. t RA,slot -Numbers are assigned in ascending order from 1 to 1, where N t RA,slot is L RA ∈ When {139, 571, 1151}, it can be provided by a predefined table, L RA When =839, it is fixed to 1.

[0249] N dur RA is provided by a predefined table.

[0250] n slot RA is given as follows:

[0251] △f RA If ∈{1.25,5,15,60}kHz, then n slot RA .

[0252] △f RA ∈{30,120}kHz, and if the "Number of PRACH slots in a subframe" or the "Number of PRACH slots in a 60 kHz slot" of the predetermined table is 1, then n slot RA =1; otherwise n slot RA ∈{0,1}.

[0253] If △f RA ∈{480,960} and:

[0254] If the "Number of PRACH slots in 60 kHz slots" in the predefined table is 1, △f RA = n at 480kHz slot RA =7, △f RA =n at 960kHz slot RA =15.

[0255] If the "Number of PRACH slots in 60 kHz slots" in the predefined table is 2, △f RA =n at 480kHz slot RA ∈{3,7}, △f RA =n at 960kHz slot RA ∈{7,15}.

[0256] If the preamble format provided in the predefined table is A1 / B1, A2 / B2, or A3 / B3:

[0257] n t RA =N t RA,slot If -1, the PRACH preamble is transmitted in the corresponding PRACH preamble format among B1, B2, and B3 at the PRACH transmission opportunity.

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

[0259] Supported N RB RA , △f RA , parameter combinations of △f and The corresponding values ​​can be expressed as shown in [Table 6] below.

[0260] [Table 6]

[0261]

[0262] PRACH repetition

[0263] To improve coverage, RO groups can be introduced for PRACH repetition. For example, if 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 time domain index to form an RO group. In the RO group, 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.

[0264] Figure 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 2, and the number of SSBs per RO is 1 / 2.

[0265] Figure 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.

[0266] 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, and N for all set preamble repetitions within that time period. Tx SSBFor each 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.

[0267] The association period for mapping SS / PBCH block indices to PRACH opportunities starts from frame 0, and is N Tx SSB The minimum integer value in the set determined by the PRACH configuration period 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 N Tx SSB 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.

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

[0269] <Slot Settings>

[0270] The slot format includes downlink symbols, uplink symbols, and flexible symbols.

[0271] The following applies to each serving cell:

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

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

[0274] i) Set reference SCS by referenceSubcarrierSpacing μ ref .

[0275] ii) pattern1.

[0276] pattern1 can provide:

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

[0278] The number of slots containing only downlink symbols d by nrofDownlinkSlots slots ,

[0279] Number of downlink symbols d by nrofDownlinkSymbols sym ,

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

[0281] Number of uplink symbols u by nrofUplinkSymbols sym .

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

[0283] 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 )-N symb slot -d sym -u sym is a fluid symbol.

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

[0285] If tdd-UL-DL-ConfigurationCommon provides both Pattern 1 and Pattern 2, the UE sets the slot format per slot for the first number of slots indicated in Pattern 1, and sets the slot format per slot for the second number of slots indicated in Pattern 2.

[0286] Pattern 2 can provide:

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

[0288] The number of slots containing only downlink symbols d by nrofDownlinkSlots slot,2 ,

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

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

[0291] Number of uplink symbols u by nrofUplinkSymbols sym,2 .

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

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

[0294] 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 )-N symb slot - d sym,2 -u sym,2 is a fluid symbol.

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

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

[0297] UE sets reference SCS μ refFor 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.

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

[0299] tdd-UL-DL-ConfigurationDedicated can provide:

[0300] A set of slot settings provided by slotSpecificConfigurationsToAddModList,

[0301] For each slot configuration in the set of slot configurations, the slot index of the slot given by slotIndex, the set of symbols of the slot given by symbols: if symbols = allDownlink, all symbols in the slot are downlink, if symbols = allUplink, all symbols in the slot are uplink, if symbols = explicit, nrofDownlinkSymbols gives the number of downlink first symbols in the slot, and nrofUplinkSymbols gives the number of uplink last symbols 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.

[0302] 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 as downlink by tdd-UL-DL-ConfigurationCommon as uplink, or a symbol designated as uplink as downlink.

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

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

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

[0306] 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 tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated (if provided) as floating symbols, or if tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the UE, to the corresponding set of symbols.

[0307] The UE receives the PDSCH or CSI-RS in the set of symbols of the slot when the corresponding indication is received by the DCI format.

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

[0309] For operation in an unpaired spectrum on a single carrier, if a UE is configured by a higher layer to receive a PDCCH, a PDSCH, a CSI-RS or a DL PRS in a set of symbols of a slot, the UE receives the PDCCH, a PDSCH, a CSI-RS or a DL PRS in the set of symbols of the slot unless the UE detects a DCI format indicating an instruction to transmit a PUSCH, a PUCCH, a PRACH or an SRS in at least one symbol in the set of symbols of the slot. Otherwise, the UE does not receive the PDCCH, a PDSCH, a CSI-RS or a DL PRS in the set of symbols of the slot.

[0310] For shared spectrum channel access in FR1 or operation in FR2-2 with ChannelAccessMode2 = 'enabled', if the UE is provided with csi-RS-ValidationWithDCI, 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.

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

[0312] For operation in an unpaired spectrum on a single carrier, if the UE is configured by a higher layer to transmit an SRS, PUCCH, PUSCH or PRACH in a set of symbols of a slot, and the UE detects a DCI format instructing it to receive a CSI-RS or PDSCH in a subset of that set of symbols,

[0313] If the UE does not indicate the [partialCancellation] capability, the UE shall receive T from the last symbol of PDCCH reception. proc,2 It 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 actual repetition of PUCCH, PUSCH, PUSCH, or PRACH transmission.

[0314] If the UE indicates the [partialCancellation] capability, the UE shall receive T from the last symbol of PDCCH reception. proc,2 It is expected that transmission of PUCCH, PUSCH or PRACH will not be canceled in the symbols occurring within. The UE cancels PUCCH, PUSCH, actual repetition of PUSCH, or PRACH transmission in the remaining symbols.

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

[0316] T proc,2 is d 2,1=1, and the PUSCH preparation time for the UE processing capability that matches μ, which corresponds 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.

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

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

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

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

[0321] When operating on 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 of 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.

[0322] When a UE is configured with multiple serving cells and directionalCollisionHandling-r16 = 'enabled' is provided for a specific serving cell among the multiple serving cells, it indicates support for the half-DuplexTDD-CA-SameSCS-r16 feature, and when none of the multiple serving cells is configured for PDCCH monitoring for DCI format 2_0 detection, the 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 an SS / PBCH block configured for L1 beam measurement / reporting. For a set of symbols in a slot, if a transmission overlaps with a symbol in that set of symbols, the UE does not transmit a PUSCH, PUCCH, or PRACH in the slot, and does not transmit an SRS within the set of symbols in the slot.

[0323] i) If the UE is not capable of simultaneous transmission and reception between multiple serving cells by simultaneousRxTxInterBandCA, ii) One of the cells corresponding to the same band as the first cell, regardless of whether any of the multiple serving cells is capable of simultaneous transmission and reception by simultaneousRxTxInterBandCA.

[0324] The symbol set of the slot corresponding to a valid PRACH event and the N preceding the valid PRACH event gapFor symbols, 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.

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

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

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

[0328] If the UE is configured with multiple serving cells, directional collision handling - r16 = 'enabled' is provided for one of the configured serving cells,

[0329] Indicates that half-duplex TDD-CA-SameSCS-r16 functionality is supported,

[0330] If multiple service cells are not configured to monitor PDCCH to detect DCI format 2_0,

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

[0332] i) Multiple serving cells configured when the UE cannot transmit and receive simultaneously as indicated by simultaneous RxTxInterBandCA among multiple serving cells, ii) Multiple serving cells configured when the UE can transmit and receive simultaneously via RxTxInterBandCA, with each cell in each band individually configured.

[0333] Here the symbols are set as follows:

[0334] Downlink or uplink. This can be indicated by tdd-UL-DL-Configuration Common or tdd-UL-DL-ConfigurationDedicated.

[0335] If the symbol is flexible and the UE is configured to transmit SRS, PUCCH, PUSCH or PRACH in the symbol, it can be configured for uplink.

[0336] If the symbol is floating and the UE is configured to receive PDCCH, PDSCH or CSI-RS in the symbol, it may be configured for downlink.

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

[0338] i) 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, respectively;

[0339] ii) tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, which detects the DCI format that marks a symbol as downlink in the reference cell and schedules transmission of the symbol in other cells;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0354] UE procedure for determining slot format

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

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

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

[0358] For each serving cell in the serving cell set, the following may be provided to the UE:

[0359] 1) ID of serving cell by servingCellId

[0360] 2) SFI index field position of DCI format 2_0 by positionInDCI

[0361] 3) A set of slot format combinations by slot format combinations, wherein each slot format combination of the set of slot format combinations may include the following.

[0362] 4) 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

[0363] 5) 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

[0364] 6) Location of the available RB set indicator field of DCI format 2_0, the field by available RB-SetsPerCell is as follows.

[0365] 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, the serving cell remains available or unavailable for reception until the end of the remaining channel occupancy period. Or,

[0366] A bitmap that maps to the set of RBs of the serving cell, 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,DLIncludes 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.

[0367] The location of the Channel Occupancy Duration field indicated by CO-DurationsPerCell in DCI format 2_0, 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.

[0368] Setting reference SCS for co-DurationList by subcarrierSpacing.

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

[0370] The SFI Index field value of DCI format 2_0 indicates to the UE the slot format of each slot for the number of slots of each DL BWP or each UL BWP, starting from the slot in which the UE detects 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 value provided by the corresponding slot format combination ID. The slot format is identified by the corresponding format index as provided in Table 7, where 'D' indicates a downlink symbol, 'U' indicates an uplink symbol, and 'F' indicates a flexible symbol.

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

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

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

[0374] [Table 7]

[0375]

[0376]

[0377] For non-paired spectrum operation for the UE in the serving cell, the reference SCS for each slot format is set μ by the subcarrier spacing (SCS). SFIis 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 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 second 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 first UL carrier of the serving cell and a slot format combination for the reference second 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 first 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 +1 slotFormats value, the first of the slot format combinations The values ​​are applied to the reference 1st UL carrier, and the following values ​​are applied 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,SUL It is expected that this will be provided. Each slot format of the slot format combination indicated by the SFI-index field of the DCI format 2_0 for the reference first UL carrier shall be provided for the active DL BWP and the active UL BWP of the first UL carrier from the first slot starting at the same point in time as the first slot of the reference first UL carrier. It applies to consecutive slots of the reference 2nd UL carrier. Each slot format for the slot format combination of the reference 2nd UL carrier is applied to the active UL BWP of the 2nd UL carrier from the first slot starting at the same time as the first slot of the reference 2nd 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] The set of symbols in the slot corresponding to a valid PRACH opportunity and the N preceding 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 DCI format 2_0 providing 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 value of the SFI-index field 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] When a UE is configured by a higher layer to receive PDSCH or CSI-RS in a symbol set of a slot, the UE receives PDSCH or CSI-RS in a symbol set of a slot only when the value of the SFI-index field in DCI format 2_0 indicates the symbol set of that slot in the downlink and, if applicable, the symbol set is within the remaining channel occupancy period.

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

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

[0399] When 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, if 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 SFI-index field value 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.

[0402] The UE shall not simultaneously detect a DCI format that instructs the UE to receive a PDSCH or CSI-RS in one or more symbols of the symbol set of the slot, if 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, 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 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 the 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 the slot format 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 where the first symbol of the symbol set detects the DCI format. proc,2 If this occurs within the time period, the transmission is not canceled. Otherwise, the UE cancels the PRACH transmission in the actual repetition or symbol set of the PUCCH, PUSCH, or PUSCH.

[0408] If the UE indicates the [partialCancellation] feature, the UE shall receive T from the last symbol of the PDCCH reception in which the DCI format was detected. proc,2 The UE shall not cancel PUCCH, PUSCH or PRACH transmissions in symbols of the set of symbols occurring within the set. The UE shall cancel PRACH transmissions in symbols of the actual repetition of PUCCH, PUSCH or PUSCH or in the remaining symbol set.

[0409] The UE detects the DCI format from the last symbol of the PDCCH reception. proc,2 The 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 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 indicated dynamically (F) 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 does not detect a DCI format 2_0 providing a slot format for that slot,

[0414] 1) The UE receives a 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] 2) 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] 3) The UE receives the PDCCH.

[0417] 4) 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] 5) 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] 6) 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] 7) 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] a) If the UE does not indicate the [partialCancellation] function, the actual repetition of PUCCH, PUSCH, PUSCH, or the first symbol of PRACH is from the last symbol of PDCCH reception set to monitor DCI format 2_0. proc,2 If it occurs within a slot, the UE does not cancel the transmission. Otherwise, the UE cancels the transmission of PUCCH, PUSCH, actual repetition of PUSCH, or PRACH in the slot.

[0422] b) If the UE indicates the [partialCancellation] feature, the UE shall receive T from the last symbol of PDCCH reception configured to monitor DCI format 2_0. proc,2 The UE does not cancel PUCCH, PUSCH, actual repetition of PUSCH, or PRACH transmission in symbols of the symbol set occurring within the symbol set. The UE cancels PUCCH, PUSCH, actual repetition of PUSCH, or PRACH transmission in symbols of the remaining symbol set.

[0423] The UE receives T from the last symbol of PDCCH reception configured to monitor DCI format 2_0. proc,2 The 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 2,1 =1 can be assumed. μ is the SCS setting of PDCCH including DCI format 2_0 and the 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 a higher layer to transmit SRS, PUCCH, PUSCH or PRACH in the symbol set of a 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 the FR1 frequency band and scheduling restrictions based on RRM measurements are not applied, and if the UE detects a DCI format that indicates to transmit in a symbol set, there is no need to perform RRM measurements in other cells based on SS / PBCH block or CSI-RS reception that includes at least one symbol in the symbol set.

[0427] TDD slot and / or symbol configuration can be determined through multiple operations. 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 resources that were left as flexible slots and / or symbols as UE-specific allocations 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 occasion of the resource configured as the PRACH slot may not be located before the SS / PBCH block resource or may not be at least N times the last SS / PBCH block reception symbol. gap If the number of symbols in the PRACH opportunity is greater than or equal to the number of symbols in the RO, the PRACH opportunity can be treated as a valid RO.

[0429] On the other hand, when RO is set via tdd-UL-DL-ConfigurationCommon, the PRACH opportunity of the resource set to UL symbol or PRACH slot is not located before SS / PBCH block resource or is at least N times the last SS / PBCH block repetition symbol. gap If the PRACH opportunity is positioned after the number of symbols of , the corresponding PRACH opportunity can be treated as a valid RO.

[0430] In this disclosure, an RO that cannot be used due to the aforementioned restrictions is referred to as an invalid RO. Hereinafter, what is designated as a slot and / or symbol may be interpreted as a unit of slots and symbols. In addition, what is designated as SBFD (subband full duplex) and / or non-SBFD may be understood as an SBFD slot / symbol and / or a non-SBFD slot / symbol.

[0431] FIG. 10 illustrates an example of a structure in which SBFD slots are allocated in the time and frequency axes according to one embodiment of the present disclosure.

[0432] Referring to Fig. 10, when the SBFD configuration is applied to a resource for which a DL slot or a dynamic (F) slot is configured by a higher layer, some frequency resources of the SBFD slot may be configured as DL, i.e., SBFD DL subbands, and some frequency resources may be configured as UL, i.e., SBFD UL subbands. 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)).

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

[0434] Referring to FIG. 11, the legacy UE (1120) recognizes the downlink slot resource to which the SBFD setting is applied as a DL resource (e.g., a DL symbol). Therefore, the legacy UE (1120) does not expect RO configuration for the downlink slot to which the SBFD setting is applied, as in the existing operation.

[0435] However, since the SBFD-aware UE (1110) recognizes the downlink slot resource with the SBFD configuration applied as an SBFD resource (e.g., an SBFD symbol), it 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 (1110).

[0436] When determining the RO configuration index, the base station may enable the RO to be configured for an SBFD symbol configured for downlink by the TDD configuration. For example, the base station may inform the terminal of the SBFD symbol through information included in the system information block (SIB). In addition, the TDD configuration may indicate whether the symbols in the slot are downlink symbols, uplink symbols, or flexible symbols. In this case, a symbol indicated as a downlink symbol by the TDD configuration may be a symbol indicated as an SBFD symbol by the SIB. In this case, the SBFD symbol may be referred to as an SBFD symbol configured for downlink by the TDD configuration.

[0437] Similarly, a symbol designated as a flexible symbol by the TDD configuration may be designated as an SBFD symbol by the SIB. In this case, the SBFD symbol may be referred to as an SBFD symbol designated as flexible (F) by the TDD configuration.

[0438] Based on parameters related to the signaled RO configuration index, ROs can be located in SBFD symbols and non-SBFD symbols. At this time, ROs in which legacy UEs and SBFD-aware UEs can transmit PRACH are referred to as legacy ROs, and ROs in which only SBFD-aware UEs can transmit PRACH are referred to as SBFD ROs. Legacy UEs can determine legacy ROs located in non-SBFD symbols and flexible symbols (e.g., SBFD symbols configured as flexible (F) by TDD configuration) as valid ROs, and SBFD-aware UEs can determine legacy ROs and SBFD ROs located in non-SBFD symbols and SBFD symbols as valid ROs.

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

[0440] Fig. 12 illustrates an example of a flexible slot when an RO is configured by a legacy RO configuration, and Fig. 13 illustrates an example of a flexible slot when an RO is configured by a separate RO configuration. Since a legacy UE (1220) treats the allocated resource as a flexible slot, it determines the RO configuration based on existing rules and determines whether the RO is valid or invalid. On the other hand, an SBFD-aware UE (1210) recognizes the resource as an SBFD resource, and thus can expect RO configuration in an SBFD UL subband (the SBFD UL subband may also be expressed as 'UL usable PRBs'. Hereinafter, the SBFD UL subband may be replaced with UL usable PRBs) according to the new rules. When both legacy UEs (1220) and SBFD-aware UEs (1210) are present, when configuring an RO or RO group, the location of the RO's time and frequency resources can be determined by considering SBFD and non-SBFD. The settings and methods applied to the RO below can also be applied to the RO group.

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

[0442] Legacy ROs can be understood as resources that can be used by legacy UEs and SBFD-aware UEs for PRACH transmission, while SBFD-dedicated ROs can be understood as resources that can be used only by SBFD-aware UEs for PRACH transmission. SBFD-dedicated ROs may also be simply referred to as SBFD ROs hereinafter.

[0443] The following two methods can be proposed as a way to set up legacy RO and SBFD-only RO.

[0444] First, a method may be used in which legacy ROs and SBFD-dedicated ROs are supported through separate RO configurations. For this purpose, multiple (e.g., two) RO configurations may be configured. In the present disclosure, a configuration in which multiple ROs are individually configured is referred to as a separate RO configuration.

[0445] FIG. 14 illustrates an example of a separated RO setup according to one embodiment of the present disclosure.

[0446] Referring to Figure 14, it can be seen that RO1 and RO2 can be configured at different frequencies by separate RO configurations. For example, ROs can be configured by two separate RACH configurations. For convenience, let us say that the two separate RACH configurations are a legacy RACH configuration and an additional RACH configuration. The legacy RACH configuration can be a RACH configuration that can be interpreted by both legacy UEs and SBFD-aware UEs, and the additional RACH configuration can be a RACH configuration that can be interpreted only by SBFD-aware UEs. In this case, RO1 can be configured by the additional RACH configuration, and RO2 can be configured by the legacy RACH configuration.

[0447] Second, a method can be used in which legacy ROs and SBFD-specific ROs are supported through a single RO configuration. A configuration in which legacy ROs and SBFD-specific ROs are configured simultaneously can be referred to as a shared RO configuration or a single RACH configuration. A single RACH configuration allows both legacy UEs and SBFD-aware UEs to be configured with the location of the RO.

[0448] FIG. 15 illustrates a shared RO configuration according to one embodiment of the present disclosure.

[0449] Referring to Figure 15, the RO of a non-SBFD slot and the RO of an SBFD slot can be configured to the same frequency resource. When a shared RO configuration is used, an SBFD-aware UE can be configured to have the location of the RO set together with a legacy UE.

[0450] Hereinafter, for convenience of explanation, using a single RACH configuration is referred to as RACH configuration option 1, and using two separate RACH configurations is referred to as RACH configuration option 2.

[0451] In RACH configuration option 1, RACH configuration (e.g., RO configuration) is performed based on existing parameters of one RACH configuration, and the existing parameters can be extended for SBFD-aware terminals.

[0452] In RACH configuration option 2, RACH configuration (e.g., RO configuration) is performed using two separate RACH configurations, which include a legacy RACH configuration and an additional RACH configuration. The legacy RACH configuration may be a RACH configuration that can be interpreted by both legacy UEs and SBFD-aware UEs, and the additional RACH configuration may be a RACH configuration that can be interpreted only by SBFD-aware UEs.

[0453] An SBFD-aware UE may support both RACH Configuration Option 1 and RACH Configuration Option 2. Simultaneous activation of both options for a single UE may not be supported.

[0454] SBFD-aware UEs can perform PRACH transmissions through ROs in SBFD slots and UL slots. Legacy UEs can perform PRACH transmissions through ROs in floating slots and UL slots (which can be used as SBFD slots or non-SBFD slots).

[0455] If both RACH configuration options 1 and 2 are supported by the UE, upper layer signaling may be performed to indicate which RACH configuration option is used. If no specific RACH configuration option is explicitly indicated to be used, the UE may assume that RACH configuration option 1 is used by default.

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

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

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

[0459] Referring to Figure 16, the following four methods can be applied.

[0460] 1) Applying shared RO settings: The base station (e.g., gNB) configures RO only in UL slots that are non-SBFD slots, following the existing RO settings. This is to take into account that legacy UEs cannot expect RO in DL slots because SBFD slots are DL slots from their perspective.

[0461] 2) When separate RO settings are applied: The base station may set RO for SBFD-aware UEs in SBFD slots and / or UL slots by RO setting 1, and set RO for legacy UEs in UL slots by RO setting 2.

[0462] 3) If SBFD resources do not require ROs for SBFD-aware UEs: RO(s) can be configured with only shared RO configuration.

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

[0464] Case 2: When SBFD is applied to a floating slot

[0465] 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. A slot treated as an SBFD slot by an SBFD-aware UE is a slot that is also treated as a floating (F) slot by a legacy UE.

[0466] 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 perspective of the legacy UE, ROs can be configured for both SBFD and non-SBFD slots through the shared RO configuration. In the shared RO configuration, it should be considered that SBFD-aware UEs can perform PRACH transmissions in the RO of the SBFD UL subband.

[0467] When a legacy RO is set in an SBFD symbol dynamically set by tdd-UL-DL-ConfigurationCommon, the network can ensure that the RO is included within the UL available PRB.

[0468] When separate RO configurations are applied: The base station may configure RO for SBFD-aware UEs in SBFD slots and / or UL slots by RO configuration 2, and configure RO for legacy UEs in flexible slots (SBFD slots) and / or UL slots by RO configuration 1. In this case, for RO configuration 1 and RO configuration 2, the base station may configure RO only for SBFD UL subbands of flexible slots to consider SBFD-aware UEs. However, if RO is configured to overlap with resources outside of SBFD UL subbands by RO configuration 1, the SBFD-aware UE may follow the configuration of RO in RO configuration 2.

[0469] 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, ROs can be set in the same way as in Case 1, which is the case without dynamic slots. That is, through separate ROs, 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.

[0470] Case 3: When part of SBFD applies to DL slots or floating slots.

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

[0472] Specific embodiments of the present disclosure

[0473] When transmitting PRACH repetitions over resources consisting of SBFD and non-SBFD symbols, the following two options can be considered:

[0474] Option 1) Send only through SBFD RO or only through legacy RO

[0475] Option 2) Send through both SBFD RO and Legacy RO.

[0476] <PRACH 반복 시, 레거시 RO 혹은 SBFD RO 중 하나를 선택해서 사용하는 방법>

[0477] When PRACH repetition is applied, the UE can select and use only one type of ROs among legacy ROs or SBFD ROs (i.e., use Option 1 above). In this case, the RO configuration can be based on separate RO configurations (i.e., two separate RACH configurations). For example, the legacy RO can be separately configured / indicated as a legacy RO configuration (which can be referred to as a legacy RACH configuration), and the SBFD RO can be separately configured / indicated as an additional RO configuration (which can be referred to as an additional RACH configuration). The SBFD RO is configured by an additional RACH configuration and can be referred to as an additional RO. SBFD ROs include ROs within SBFD symbols configured as downlink by a time division duplex (TDD) configuration (e.g., tdd-UL-DL-ConfigurationCommon) and ROs spanning SBFD symbols configured as downlink by the TDD configuration and SBFD symbols configured as flexible when configured by a single RACH configuration.

[0478] Legacy UEs can use only legacy ROs, while SBFD-aware UEs can use either legacy ROs or SBFD ROs (additional ROs).

[0479] Meanwhile, the legacy RO can be assumed to be a shared RO that can be selected by legacy UEs and SBFD-aware UEs for PRACH transmission, and the legacy RO configuration can be achieved through one single RACH configuration or multiple RACH configurations.

[0480] An SBFD-aware UE can either directly select which RO type (i.e., legacy RO or additional RO) to use, or can be determined by a higher layer (upper layer) configuration / instruction. For example, if an SBFD-aware UE is determined to have the capability to perform beamforming considering UE-to-UE cross link interference (CLI), the base station (e.g., gNB) can configure / instruct an upper layer signal to the UE to use an SBFD RO (additional RO). When the configuration / instruction is received from the upper layer, the UE selects the configured / instructed RO and (repeatedly) transmits a PRACH. The upper layer can be a SIB1 (system information block type 1) configuration.

[0481] Alternatively, if certain conditions are met, an SBFD-aware UE can switch the RO for transmitting PRACH between the legacy RO and the SBFD RO (additional RO). Selection and switching can be applied to both single and multiple PRACH transmissions.

[0482] Meanwhile, if switching is applied to PRACH repetition (multiple PRACH transmissions), it can occur within a set of ROs that form an RO group.

[0483] An SBFD-aware UE can support PRACH transmission with preamble repetitions within additional ROs. An SBFD-aware UE can also support PRACH transmission with preamble repetitions within legacy ROs. However, an SBFD-aware UE does not support PRACH transmission with preamble repetitions across additional ROs and legacy ROs.

[0484] When an SBFD-aware UE selects an RO type, it may consider at least one of the following conditions: RO selection may be performed before retransmission. Selection and switching may apply to both single PRACH transmissions and multi-PRACH transmissions. The methods for applying the conditions below to RO selection are applicable to both CBRA and CFRA.

[0485] In a legacy RACH configuration, when i) RO within a non-SBFD symbol and ii) RO within a SBFD symbol are indicated, SSB-to-RO mapping may be performed independently for RO within a non-SBFD symbol and RO within a SBFD symbol. For example, a certain SSB index may be mapped to RO within a non-SBFD symbol and RO within a SBFD symbol.

[0486] In the Additional RACH configuration, when RO within a non-SBFD symbol and RO within a SBFD symbol are indicated, SSB-to-RO mapping may be performed across RO within a non-SBFD symbol and RO within a SBFD symbol, or SSB-to-RO mapping may be performed independently across RO within a non-SBFD symbol and RO within a SBFD symbol.

[0487] If RO within the SBFD symbol is indicated in the additional RACH configuration, SSB-to-RO mapping is performed in the RO within the SBFD symbol.

[0488] When RACH is indicated in the legacy RACH configuration and the additional RACH configuration, a certain SSB index may be mapped to an RO in a non-SBFD symbol of the legacy RACH configuration, and the SSB index may be mapped to an RO in an SBFD symbol / RO in a non-SBFD symbol indicated by the additional RACH configuration.

[0489] 1) When an SBFD-aware UE selects an RO type, it selects an SSB (hereafter referred to as SSB_) with SS-RSRP greater than a specific threshold (rsrp-ThresholdSSB) based on the legacy RO. legacyRO ) and SSB (SSB_) with SS-RSRP greater than a certain threshold (rsrp-ThresholdSSB) based on SBFD RO. SBFDRO ) can be compared to select RO.

[0490] The above specific threshold (rsrp-ThresholdSSB) can be set / instructed from a higher layer.

[0491] The specific thresholds (rsrp-ThresholdSSB) applied to legacy ROs and the specific thresholds (rsrp-ThresholdSSB) applied to SBFD ROs can be set / indicated differently. This is to prevent UEs from concentrating on a single RO type, and can reduce RACH collision probability by distributing UEs using legacy ROs and UEs using SBFD ROs, depending on the base station's settings.

[0492] If the SSB satisfies two threshold (rsrp-ThresholdSSB) values, the UE can select the RO type with the higher threshold (rsrp-ThresholdSSB) value set.

[0493] Alternatively, if the SSB satisfies two threshold (rsrp-ThresholdSSB) values, the UE can randomly select the RO type.

[0494] Alternatively, if the SSB satisfies two threshold (rsrp-ThresholdSSB) values, the UE may select an RO type with a smaller association period or association pattern period.

[0495] Alternatively, if the SSB satisfies two thresholds (rsrp-ThresholdSSB), the UE selects the SBFD RO or an additional RO. This can aid in early detection and allow subsequent transmissions related to msg2 / 3 / 4 to be performed in the SBFD symbol.

[0496] Additional ROs can be ROs within an SBFD symbol in a single legacy RACH configuration or ROs configured by an additional RACH configuration in two separate RACH configurations. In the case of an additional RACH configuration, it can consist of i) ROs within an SBFD symbol or ii) ROs within an SBFD symbol / non-SBFD symbol.

[0497] For example, when an SBFD-aware UE is given an SSB associated with a legacy RO and an SSB associated with an SBFD RO, if beamforming considering UE-to-UE CLI works well, the UE may be more likely to select the SSB associated with the SBFD RO.

[0498] 2) When selecting an RO type, an SBFD-aware UE can select one based on the association period or association pattern period of the legacy RO and the SBFD RO. For example, the selection can be based on a smaller association period or association pattern period. This method can provide benefits in terms of PRACH latency.

[0499] SBFD-aware UEs may be given the opportunity to switch between RO types they have already selected and are using. Selection and switching can be applied to both single PRACH transmissions and multi-PRACH transmissions.

[0500] If switching is performed in multiple PRACH transmissions, it can occur within a set of ROs forming an RO group. Assuming that the number of ROs forming an RO group is 2, 4, 8, or N, switching can be applied only when a PRACH transmission is repeatedly transmitted more than a certain number of times. For example, if the standard number of repeated transmissions is given as 8, switching is not applied when the number of ROs forming an RO group is 2 or 4, but can be applied only when the number of ROs forming an RO group is 8 or more.

[0501] The above N value can be indicated / set by the base station. At this time, at least one of the following conditions may be considered. For example, if PRACH transmission fails with the selected RO type, the step of selecting a legacy RO and an SBFD RO based on a specific reference point may be re-executed. At this time, if the SSB-related value of the currently unused RO is better, switching may be applied.

[0502] i) A specific reference point may be a predefined point in time.

[0503] ii) Specific reference points can be set / indicated from higher layers.

[0504] iii) A specific reference point may be the point at which retransmission is applied.

[0505] iv) A specific reference point may be immediately before the relevant power ramping is applied after a specific retransmission repetition. For example, an opportunity may be given to switch the RO type before the power ramping is applied.

[0506] v) A specific reference point may be immediately before the relevant power ramping is applied after a specific number of iterations. An opportunity may be given to switch the RO type before the power ramping is applied.

[0507] vi) A specific threshold may be just before the iteration count is increased after all iterations have failed to reach a certain threshold. For example, an opportunity to switch the RO type may be given before the number of iterations increases from 2 to 4.

[0508] In the case of legacy RO, since legacy RO is not allocated to SBFD symbols allocated to DL through cell-specific TDD UL / DL configuration (e.g., tdd-UL-DL-ConfigurationCommon) or tdd-UL-DL-ConfigurationDedicated, if the number of legacy ROs is insufficient and PRACH repetition is applied, the PRACH delay may be relatively long. In the case where SBFD with PRACH repetition is applied, the resource to which the SBFD symbol is applied is set / indicated as F (flexible) among DL (downlink), UL (uplink), and F (flexible) by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0509] For SBFD ROs, separate RO configurations allow for additional RO allocations not only for SBFD symbols but also for UL symbols. To increase the number of SBFD ROs, their frequency locations can be assigned / instructed to not overlap with those of legacy ROs. If overlap occurs, the SSB-to-RO mapping value of the legacy RO is assigned.

[0510] The options discussed in the RO selection and switching method described above may be applied, in whole or in part, to at least one of the following Cases 1, 2, and 3.

[0511] Case 1) Selection and switching between single RO transmission (Legacy RO) and single RO transmission (SBFD RO).

[0512] Case 2) Selection and switching between multi-RO transmission (legacy RO) and multi-RO transmission (legacy RO and SBFD RO) and multi-RO transmission (SBFD RO).

[0513] Case 3) Selection and switching between single RO transmission and multi-RO transmission.

[0514] <non-SBFD 심볼과 SBFD 심볼에 유효한 RO가 모두 설정되어 있을 때, SBFD 심볼 내의 RO만(only RO in SBFD symbol) 혹은 non-SBFD 심볼 내의 RO만(only RO in non-SBFD symbol)으로 구성된 RO 그룹을 설정하는 방법>

[0515] As mentioned above, for random access operation for SBFD-aware UEs in RRC CONNECTED state, the following options may be considered.

[0516] Option 1: Option to use a single RACH configuration.

[0517] At this time, ROs within the UL subbands of SBFD symbols may be valid for SBFD-aware UEs.

[0518] Option 2: Option to use two separate RACH configurations, one legacy RACH configuration and one additional RACH configuration.

[0519] At this time, ROs within the UL subband of SBFD symbols set by the additional RACH configuration may be valid for SBFD-aware UEs.

[0520] For SBFD-aware UEs in RRC CONNECTED state, at least non-repetitive PRACH is supported in SBFD symbols.

[0521] Additional RO can be defined as follows:

[0522] For RACH configuration Option 1, additional-ROs include i) ROs in SBFD symbols configured as downlink by tdd-UL-DL-ConfigurationCommon, and the ROs across SBFD symbols configured as downlink by tdd-UL-DL-ConfigurationCommon and SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon.

[0523] For RACH configuration Option 2, additional ROs are the ROs configured by the additional RACH configuration.

[0524] The network can explicitly indicate whether RACH configuration option 1 for SBFD random access operation is enabled on the network side.

[0525] For example, the network side could explicitly indicate whether RACH configuration option 1 for SBFD random access operation is enabled by i) indicating it via SIB1 and / or ii) via dedicated signaling conveying cell-specific configuration.

[0526] Hereinafter, for convenience of explanation, if an RO group is formed only with ROs in an SBFD symbol or only with ROs in a non-SBFD symbol, the RO group is called RO group type 1. On the other hand, if an RO group is formed with ROs in an SBFD symbol and a non-SBFD symbol, the RO group is called RO group type 2. That is, in RO group type 1, only the same type of ROs (ROs in an SBFD symbol or ROs in a non-SBFD symbol) are included in one RO group, and in RO group type 2, different types of ROs (ROs in an SBFD symbol and ROs in a non-SBFD symbol) are included in one RO group.

[0527] Figure 19 illustrates RO settings by legacy RACH settings and RO settings by additional RACH settings.

[0528] Referring to FIG. 19, legacy ROs (ROs within non-SBFD symbols and / or ROs within SBFD symbols indicated by F (flexible)) are set / indicated by legacy RACH settings, and additional ROs (ROs within SBFD symbols) are set / indicated by additional RACH settings.

[0529] According to the legacy RO group rules, if an RO group is formed based on a rule that specifies a valid RO, it naturally becomes RO group type 1. If the SBFD operation is performed by combining two RO sets configured / indicated through the legacy RACH setting and the additional RACH setting, RO group type 2 is formed / indicated according to the legacy RO group rules.

[0530] Additionally, AdditionalRACH-Config and RACH-Config / RACH-ConfigCommonTwoStepRA_R19 can indicate feature combinations via the FeatureCombinationPreamble IE.

[0531] Since RACH partition configuration through RO configuration is performed through AdditionalRACH-Config and FeatureCombinationPreamble IE, and RACH partition configuration through preamble partitioning is performed through FeatureCombinationPreamble IE, AdditionalRACH-Config is grouped into Feature Combination.

[0532] The preamble splitting operation can be performed, for example, as follows:

[0533] Let us assume that preambles 0 to X (e.g., 31) are used by legacy UEs, and preambles X+1 (e.g., 32) to 63 are used by SBFD UEs. In this case, when SBFD operation and PRACH transmission (including PRACH repetition) are applied, the legacy UE performs PRACH transmission (including PRACH repetition) using only ROs in non-SBFD symbols with preambles 0 to X (e.g., 31). On the other hand, the SBFD UE performs PRACH transmission (including PRACH repetition) using only ROs configured in SBFD symbols with preambles X+1 (e.g., 32) to 63.

[0534] Figure 20 is another example of RO configuration by legacy RACH configuration and RO configuration by additional RACH configuration.

[0535] Referring to FIG. 20, legacy ROs (ROs within non-SBFD symbols and / or ROs within SBFD symbols indicated by F (flexible)) are set / indicated by legacy RACH settings, and additional ROs (ROs within SBFD symbols and non-SBFD symbols) are set / indicated by additional RACH settings.

[0536] When an RO group is formed based on a rule designated as a valid RO according to the legacy RO group rules, it naturally becomes RO group type 2. However, both RO group type 1 and RO group type 2 may be applied if necessary. For example, depending on the implementation method of the UE and the base station, there may be cases where PRACH transmission / reception must be performed as RO group type 1. In addition, AdditionalRACH-Config and RACH-Config / RACH-ConfigCommonTwoStepRA_R19 can indicate feature combinations through the FeatureCombinationPreamble IE.

[0537] Since RACH segmentation configuration through RO configuration is performed through AdditionalRACH-Config and FeatureCombinationPreamble IE, and RACH segmentation configuration through preamble segmentation is performed through FeatureCombinationPreamble IE, AdditionalRACH-Config is grouped into Feature Combination. The preamble segmentation operation can operate as follows, for example. Assuming that preambles 0 to X (e.g., 31) are used by legacy UEs and X+1 (e.g., 32) to 63 are used by SBFD UEs, when SBFD operation and PRACH transmission (including PRACH repetition) are applied, the legacy UE performs PRACH transmission (including PRACH repetition) using only ROs in non-SBFD symbols with preambles 0 to X (e.g., 31), and the SBFD UE performs PRACH transmission (including PRACH repetition) using only ROs set in SBFD symbols with preambles X+1 (e.g., 32) to 63.

[0538] Figure 21 illustrates RO configuration by a single RACH configuration.

[0539] Referring to Figure 21, ROs can be configured by a single RACH configuration. When configuring RO groups according to legacy RO group rules, RO group type 2 is naturally applied. However, both RO group type 1 and RO group type 2 can be applied if necessary. For example, depending on the implementation method of the UE and base station, there may be cases where PRACH transmission / reception must be performed using RO group type 1.

[0540] When an SBFD-aware UE performs repeated operation on ROs spanning SBFD symbols and non-SBFD symbols, ROs in non-SBFD symbols are shared by legacy UEs and SBFD UEs because they are shared ROs. Operation is possible based on preamble partitioning, and assuming that preambles 0 to X (e.g., 31) are used by legacy UEs and X+1 (e.g., 32) to 63 are used by SBFD UEs, when SBFD operation and PRACH transmission (including PRACH repetition) are applied, the legacy UE performs PRACH transmission (including PRACH repetition) using only ROs in non-SBFD symbols with preambles 0 to X (e.g., 31), and the SBFD UE performs PRACH transmission (including PRACH repetition) using all ROs configured in non-SBFD symbols and SBFD symbols with preambles X+1 (e.g., 32) to 63.

[0541] PRACH repetition can be supported in the following manner so that RO group type 1 or RO group type 2 can be set by various conditions regardless of the given RACH configuration.

[0542] Option 1) Set up the RO group using the legacy method. This will naturally set up RO group type 1 or RO group type 2.

[0543] To enable the UE and base station to use a specific type of RO group, the UE communicates its capabilities to the base station.

[0544] To enable the UE and the base station to use a specific type of RO group, the base station sets up / instructs relevant signaling.

[0545] For example, some RO groups configured in the legacy method can be selected for PRACH repetition. Depending on the configuration / instruction, certain RO groups are classified as valid RO groups.

[0546] The UE performs PRACH repetition by selecting one of the valid multi-RO groups formed in this way.

[0547] The base station can directly indicate when a specific type of RO group is formed. For example, a PRACH mask can be used.

[0548] Option 2) Configure the RO group using the legacy method. In this case, the base station can configure the PRACH configuration index and / or the number of PRACH repetitions so that the RO group is configured as type 1. This also includes cases where the existing random access configuration table is applied for SBFD operation (e.g., when introducing new parameters).

[0549] To enable the UE and base station to use a specific type of RO group, the UE can communicate its capabilities to the base station.

[0550] The UE selects one type of multiple RO groups formed in this way and performs PRACH repetition.

[0551] The base station can directly indicate when a specific type of RO group is formed. For example, a PRACH mask can be used.

[0552] Option 3) By the rules of the improved RO group, either RO group type 1 or RO group type 2 can be set.

[0553] Depending on the capability of the UE or the implementation of the base station, the RO group is configured / instructed to be composed of RO group type 1 or RO group type 2 so that a specific type of RO group can be used.

[0554] The base station sets / instructs whether to form an RO group as RO group type 1 or RO group type 2. The UE selects one of the multiple RO groups of one type formed in this way and performs PRACH repetition.

[0555] The base station can directly indicate when a specific type of RO group is formed. For example, a PRACH mask can be used.

[0556] For example, if the base station sets / indicates the repetition count as N (e.g., 2, 4, 8), among the valid ROs located in the SBFD symbol, the ROs existing at the same frequency are grouped in ascending order of their time domain indices and set as RO group type 1. At this time, the remaining N-1 ROs are located at the same frequency as the first RO. In other words, among the valid ROs located in the SBFD symbol associated with the same beam, the N ROs existing at the same frequency can be grouped into one RO group type 1.

[0557] For example, if the base station sets / indicates the repetition count as N (e.g., 2, 4, 8), among the valid ROs located in the non-SBFD symbol, the ROs existing at the same frequency are grouped in ascending order of their time domain indices into N groups and set as RO group type 1. At this time, the remaining N-1 ROs are located at the same frequency as the first RO. In other words, among the valid ROs located at the non-SBFD symbol associated with the same beam, the N ROs existing at the same frequency can be grouped into one RO group type 1.

[0558] <When using legacy RO and SBFD RO simultaneously>

[0559] When PRACH repetition is applied, the UE can select and use both legacy RO and SBFD RO to secure more UL transmission opportunities. For these options, RO configuration is based on shared RO configurations. That is, ROs are configured / indicated through a single common RACH configuration.

[0560] However, since shared RO is not allocated to SBFD symbols allocated to DL through tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, PRACH delay may be relatively long when PRACH repetition is applied. When SBFD is applied to PRACH repetition, the resource to which the SBFD symbol is applied can be set / indicated as F(flexible) by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[0561] Meanwhile, when the base station determines the RO configuration index, it may be configured so that the RO can also be configured for the SBFD symbol configured for TDD in the downlink. In this case, the RO can be located in the SBFD symbol and non-SBFD symbol based on parameters related to the signaled RO configuration index.

[0562] At this time, it is assumed that the RO in which the legacy UE and the SBFD-aware UE can transmit PRACH is the legacy RO, and the RO in which only the SBFD-aware UE can transmit PRACH is the SBFD RO. Based on this, the legacy UE can determine the legacy RO located in the non-SBFD symbol as a valid RO, and the SBFD-aware UE can determine the legacy RO and SBFD RO located in the non-SBFD symbol and the SBFD symbol as valid ROs.

[0563] Even in this case, the SBFD-aware UE can use both legacy RO and SBFD RO simultaneously, and such RO configuration can be configured through one single RACH configuration (e.g., one legacy RACH configuration) or separate RACH configurations (e.g., one legacy RACH configuration and an additional RACH configuration).

[0564] For shared RO configurations that can be used when SBFD is applied, features of IE FeatureCombination, such as reduced capacity (redCap), small data, nsag (Network Slice Access), and msg3 repetitions, can be included in IE FeatureCombination as new features (e.g., msg1-Repetitions-SBFD-r19).

[0565] For example, it may be considered to set a separate PRACH preamble index only for SBFD-aware UEs. For example, if a PRACH preamble index is selected only for SBFD-aware UEs transmitting PRACH on a shared RO, the capability of the SBFD-aware UE may be indicated early. If a PRACH preamble index is selected for legacy UEs on a shared RO, msg3 and msg4 HARQ-ACK transmission over full UL may be applied to reflect the behavior of the legacy UE.

[0566] For example, when 64 preamble indices are set within an RO, preamble splitting can be performed such that X preamble indices are allocated to legacy UEs and the remaining 64-X can be used by SBFD-aware UEs for SBFD-specific purposes. SBFD-aware UEs can use all 64 preamble indices, but X preamble indices can be shared with legacy UEs and the remaining 64-x can be reserved for SBFD operation.

[0567] The following table provides an example of an IE FeatureCombination. An IE FeatureCombination may be an information element that indicates a feature or combination of features to be associated with a set of random access resources.

[0568] [Table 8]

[0569]

[0570] In Table 8, 'redCap', if present, indicates that RedCap is part of this feature set.

[0571] 'smallData' indicates that small data is part of this feature set when this field is present.

[0572] 'nsag', if present, indicates that this field is part of the NSAG of this feature set.

[0573] 'msg3-Repetitions', if present, indicates that msg3 repetition signaling is part of this feature set. This field is not set for preamble sets that are set to the two-phase random access type.

[0574] 'SBFD', if present, indicates that this field is part of the SBFD of this feature set.

[0575] Because the SBFD-aware UE receives the same RO settings as the legacy UE, it may be difficult to distinguish between a PRACH transmission of a legacy UE and a PRACH transmission of an SBFD-aware UE based solely on the selected RO location when sending PRACH.

[0576] Alternatively, if the RO is configured to allow legacy UEs and SBFD-aware UEs to send PRACHs through a shared RO, it is difficult for the base station to know the capability of the UE transmitting the PRACH based solely on the location of the RO resource through which the SBFD-aware UE transmitted the PRACH.

[0577] Considering the possibility that UL transmissions included in the random access process following PRACH transmission (e.g., PRACH, msg3, msg4 ACK / NACK transmitted from the remaining ROs included in the RO group) may also be performed within the UL subband, it is possible to support distinguishing the capabilities of SBFD-aware UEs through featureCombinationPreambles.

[0578] For example, if an SBFD-aware UE transmits on a legacy RO (or an RO within non-SBFD symbols), it expects msg3 and / or msg4 ACK / NACK to be scheduled on the full UL (non-SBFD symbol), and if an SBFD UE transmits on a SBFD RO (or an RO within SBFD symbols), it expects msg3 and / or msg4 ACK / NACK to be scheduled on either the full UL (non-SBFD symbol) or a UL subband (an SBFD UL subband).

[0579] Meanwhile, when an SBFD-aware UE transmits a PRACH through a legacy RO or transmits a PRACH by selecting a preamble index that is not configured for an SBFD-aware UE in a legacy RO, the UE's capability related to whether it supports SBFD can be conveyed through the information included in Msg3.

[0580] An SBFD-aware UE expects msg4 ACK / NACK to be scheduled on full UL (non-SBFD symbol) or on one of the full UL (non-SBFD symbol) or UL subbands (SBFD UL subbands) based on the UE capability information carried in Msg3.

[0581] Meanwhile, the method of implicitly / explicitly transmitting to the base station the UE capability related to supporting the aforementioned SBFD operation can be applied not only to the random access process supporting PRACH repetition, but also to the case of a single PRACH transmission.

[0582] The IE FeatureCombinationPreambles can associate a set of preambles with a feature combination. For parameters that can be provided in this IE, the UE applies the value of this field when performing a random access using the preamble of this FeatureCombinationPreambles. Otherwise, the UE applies the corresponding value determined by the applicable Need Code (e.g., Need S). In a specific BWP, there can be at most one set of preambles associated with a specific feature combination per RA type (e.g., 4-step RACH or 2-step RACH).

[0583] The following table illustrates IE FeatureCombinationPreambles.

[0584] [Table 9]

[0585]

[0586] If multiple features are supported in a feature combination, multiple random access responses will exist.

[0587] The MAC entity identifies, among the set of random access resources available for this random access procedure, the feature with the highest priority assigned to featurePriorities among all features applicable to this random access procedure.

[0588] If a single random access resource set is identified, this random access resource set is selected.

[0589] Otherwise, if more than one random access resource set is identified, the procedure is repeated using as input the identified random access resource set and the feature applicable to the current random access procedure with the highest priority assigned to featurePriorities, excluding the features already considered among all features applicable to this random access procedure.

[0590] Otherwise (i.e., if no random access resource set is identified), the procedure is repeated using as input the previously identified set of available random access resources and the feature with the highest priority assigned to featurePriorities among the features applicable to this random access procedure, excluding the features already considered.

[0591] At this time, the priority for each feature can be set / indicated through featurePriorities.

[0592] The following table illustrates SIB1. SIB1 may include information relevant to assessing whether a UE is allowed cell access, as well as information defining the scheduling of other system information. It also includes radio resource configuration information common to all UEs and barring information applicable to unified access control.

[0593] [Table 10]

[0594]

[0595] Meanwhile, if SBFD does not support shared RO configuration, a new SSB-to-RO mapping rule can be applied based on the separated RO configuration. For example, after SSB-to-RO mapping is performed on the legacy RO, the same SSB-to-RO mapping is applied to both the legacy UE and the SBFD UE, and then the SSB-to-RO mapping is continued on the SBFD RO. To increase the number of SBFD ROs, the frequency positions can be allocated / instructed to not overlap with the legacy ROs. If there is an overlap, the SSB-to-RO mapping value of the legacy RO is given.

[0596] As mentioned above, SBFD may be used in future wireless communication systems, but in such an environment, it is not clearly defined in the prior art how an SBFD-aware UE performs a random access process, particularly PRACH repetition. For example, in the prior art, a random access channel occasion (RO) for transmitting a preamble for random access is set only on HD resources. However, in NR or post-NR wireless communication systems, RO may be set not only on HD resources but also on SBFD resources. In this case, it should be considered that uplink resources in the frequency domain may be limited in SBFD resources compared to HD resources. Furthermore, in a situation where legacy UEs and SBFD-aware UEs coexist, ROs may be set in various ways, and in such a case, it is not clearly defined how an SBFD-aware UE will perform PRACH repetition.

[0597] Figure 22 illustrates terminal operation according to one embodiment of the present disclosure.

[0598] Referring to FIG. 22, a subband full duplex (SBFD) aware UE (hereinafter, simply referred to as a UE) that recognizes SBFD receives at least one random access channel (RACH) setting from a network (S221).

[0599] For example, the terminal may be provided with a single RACH configuration from the network, such as RACH configuration option 1, or may be provided with two separate RACH configurations from the network, such as RACH configuration option 2. The two separate RACH configurations may include one legacy RACH configuration and one additional RACH configuration.

[0600] The terminal performs PRACH (physical random access channel) repetition based on at least one RACH setting, wherein the PRACH repetition is performed based on one type of ROs among i) valid legacy ROs (random access channel occasions) and ii) valid additional ROs (S222).

[0601] The above terminal supports PRACH transmission that repeatedly transmits a preamble only in the valid legacy ROs and PRACH transmission that repeatedly transmits a preamble only in the valid additional ROs.

[0602] On the other hand, the terminal does not support PRACH transmission that repeatedly transmits the preamble in ROs spanning at least one valid additional RO and at least one valid legacy RO.

[0603] Legacy ROs valid for non-SBFD aware UEs are also valid for the UEs (SBFD aware UEs).

[0604] If at least one of the above RACH configurations is a single RACH configuration, ROs within the uplink subband in the SBFD symbols may be included in the valid ROs for the terminal.

[0605] If the at least one RACH configuration is two separate RACH configurations including a legacy RACH configuration and an additional RACH configuration, ROs within the uplink subband in the SBFD symbols configured by the additional RACH configuration may be included in the valid ROs for the terminal.

[0606] If the at least one RACH configuration is two separate RACH configurations including the legacy RACH configuration and the additional RACH configuration, the additional ROs in non-SBFD symbols configured by the additional RACH configuration become invalid ROs for the terminal.

[0607] Here, the additional ROs include: i) ROs within SBFD symbols configured for downlink by a time division duplex (TDD) configuration when the at least one RACH configuration is a single RACH configuration and ROs spanning SBFD symbols configured for downlink by the TDD configuration and SBFD symbols configured as flexible, and ii) ROs configured by the additional RACH configuration when the at least one RACH configuration is two separate RACH configurations including a legacy RACH configuration and an additional RACH configuration.

[0608] In some embodiments, when a terminal receives a configured repetition number N from a network and fails to transmit a PRACH using an additional RO group including the N valid additional ROs, switching to a PRACH transmission using a legacy RO group including valid legacy ROs may be permitted.

[0609] Here, if the PRACH transmission using the additional RO group is attempted a set number of times (i.e., multiple times) and fails, the PRACH transmission can be switched to the PRACH transmission using the legacy RO group.

[0610] For example, if a PRACH transmission using an additional RO group including, for example, two valid additional ROs has been retransmitted a certain number of times but ultimately failed, it is common to attempt a PRACH transmission using an additional RO group including increased valid additional ROs (i.e., four valid additional ROs) by increasing the number of valid additional ROs (e.g., four). However, in the method according to the present disclosure, by introducing a parameter called the 'set repetition count', if the network sets, for example, 2 through the parameter (i.e., sets N=2), if the PRACH transmission using an additional RO group including two valid additional ROs ultimately fails, the method can switch to a PRACH transmission using a legacy RO group including valid legacy ROs.

[0611] The above N value and the above set number of times can be set by the network.

[0612] The configured repetition number N may be one of multiple candidate values. For example, N may be one of multiple candidate values ​​such as 2, 4, or 8. In the case where PRACH transmission using the additional RO group is attempted a set number of times, the set number may be one of the multiple candidate values.

[0613] In some embodiments, the terminal may be allowed to switch to PRACH transmission using a legacy RO group containing valid legacy ROs before applying power ramping after failing to transmit PRACH using an additional RO group containing valid additional ROs.

[0614] For example, after attempting PRACH transmission using the additional RO group a predetermined number of times and failing to transmit the PRACH, switching to PRACH transmission using the legacy RO group can be performed before applying the power ramping.

[0615] When a CBRA RACH procedure is initiated for an SBFD-aware UE, the UE may select one type of RO between the legacy RO and the additional RO based on certain specified / configured conditions / priorities, unless further instructions are given by the network. In case of PRACH transmission retries in a RACH procedure, the UE is allowed to switch to the legacy ROs (legacy RO groups) after attempting RACH in SBFD ROs (SBFD RO groups) for a certain (configured) number of times.

[0616] According to the method of Fig. 22, ambiguity with the network can be prevented by clearly defining the PRACH repetition transmission method of an SBFD-aware terminal in a situation where legacy RO and additional RO are mixed.

[0617] Furthermore, when repeatedly transmitting PRACHs using an RO group, there may be cases where communication is not successfully performed simply by increasing the number of valid ROs included in the RO group depending on the channel conditions. In such cases, the method according to the present disclosure allows for changing the RO types of valid ROs included in the RO group, thereby efficiently performing PRACH repetitions for SBFD-aware terminals.

[0618] FIG. 23 illustrates an operation method of a base station according to one embodiment of the present disclosure.

[0619] Referring to FIG. 23, a base station transmits at least one random access channel (RACH) setting to a subband full duplex (SBFD) aware user equipment (SBFD aware user equipment) that recognizes subband full duplex (SBFD) (S231).

[0620] The base station repeatedly receives a PRACH (physical random access channel) from the SBFD-aware terminal based on at least one RACH setting, wherein the repeated reception of the PRACH is performed based on one type of RO among i) valid legacy ROs (random access channel occasions) and ii) valid additional ROs (S232).

[0621] FIG. 24 illustrates signaling and operation between a base station and a terminal according to one embodiment of the present disclosure.

[0622] Referring to FIG. 24, the base station provides a TDD configuration to a terminal (SBFD-aware terminal, hereinafter the same) (S241). The TDD configuration (e.g., tdd-UL-DL-Configuration Common and / or tdd-UL-DL-ConfigurationDedicated) may set any one of downlink, uplink, and flexible for a communication time unit (e.g., at least one slot or at least one symbol).

[0623] The base station provides the terminal with SBFD settings (S242). The SBFD settings can inform the terminal of the time resources and / or frequency resources that operate in SBFD.

[0624] Here, the base station is exemplified as informing the terminal of SBFD configuration and TDD configuration through separate signaling, but this is not a limitation. That is, the base station can also inform the terminal of SBFD configuration and TDD configuration through a one-time signaling using the same message.

[0625] The base station provides at least one RACH configuration to the terminal (S243). For example, a single RACH configuration may be provided, such as RACH configuration option 1, or two separate RACH configurations may be provided, such as RACH configuration option 2. The two separate RACH configurations may include one legacy RACH configuration and one additional RACH configuration.

[0626] The terminal determines valid legacy ROs and valid additional ROs (S244). The rules for determining valid legacy ROs and valid additional ROs have already been described above (e.g., described in the method of FIG. 22).

[0627] The terminal performs PRACH repetition transmission to the base station (this may also be referred to as PRACH transmission with preamble repetition or PRACH transmission repeating the preamble) (S245).

[0628] Figure 25 illustrates valid legacy ROs (RO1) and valid additional ROs (RO2) when using RACH configuration option 1.

[0629] Referring to FIG. 25, RO1 and RO2 can be configured by a single RACH configuration. For example, a legacy UE can recognize RO1 by a single RACH configuration (existing parameters of the RACH configuration), and an SBFD-aware UE can recognize RO1 and RO2 by the single RACH configuration (extended parameters of the RACH configuration).

[0630] Figure 26 illustrates valid legacy ROs (RO1) and valid additional ROs (RO2) when using RACH configuration option 2.

[0631] Referring to FIG. 26, legacy ROs are set by legacy RACH settings, and additional ROs can be set by additional RACH settings.

[0632] Figure 27 illustrates a wireless device applicable to the present specification.

[0633] Referring to FIG. 27, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR).

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

[0635] A processor (102) receives at least one random access channel (RACH) configuration from a network, and performs PRACH (physical random access channel) repetition based on the at least one RACH configuration, wherein the processor is included in a subband full duplex (SBFD) aware UE, and the PRACH repetition is performed based on one type of ROs among i) valid legacy ROs (random access channel occasions) and ii) valid additional ROs. The specific operation thereof has been described above with reference to FIGS. 22 to 26.

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

[0637] The processor (202) transmits at least one random access channel (RACH) configuration to an SBFD-aware user equipment (UE) that is aware of subband full duplex (SBFD), and the base station repeatedly receives a physical random access channel (PRACH) from the SBFD-aware UE based on the at least one RACH configuration, wherein the repeated reception of the PRACH is performed based on one type of ROs among i) valid legacy ROs (random access channel occasions) and ii) valid additional ROs. The specific operation thereof has been described above with reference to FIGS. 22 to 26.

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

[0639] The one or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. The one or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors (102, 202). The one or more processors (102, 202) may also be implemented by at least one computer-readable medium (CRM) containing instructions based on which at least one processor is executed.

[0640] For example, at least one computer readable medium (CRM) including instructions that are executed by at least one processor to receive at least one random access channel (RACH) configuration from a network and perform physical random access channel (PRACH) repetition based on the at least one RACH configuration, wherein the CRM is included in a subband full duplex (SBFD) aware UE, and the PRACH repetition is performed based on one type of i) valid legacy random access channel occasions (ROs) and ii) valid additional ROs. The specific operation thereof has been described with reference to FIGS. 22 to 26.

[0641] The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions. The firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be included in one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

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

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

[0644] Fig. 28 illustrates an example of a signal processing module structure. Here, signal processing may be performed in the processor (102, 202) of Fig. 27.

[0645] Referring to FIG. 28, a transmission device (e.g., a processor, a processor and a memory, or a processor and a transceiver) within a terminal or a 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).

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

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

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

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

[0650] The signal generator (306) can generate a complex-valued time domain OFDM symbol signal by modulating a complex modulation symbol, for example, an antenna-specific symbol, for each antenna port, 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.

[0651] Fig. 29 illustrates another example of the signal processing module structure within a transmission device. Here, signal processing may be performed in a processor of a terminal / base station, such as the processor (102, 202) of Fig. 27.

[0652] Referring to FIG. 29, a transmission device (e.g., a processor, a processor and a memory, or a processor and a transceiver) in a terminal or a 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).

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

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

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

[0656] 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 the precoding matrix W of NХM. Here, N is the number of antenna ports and M is the number of layers.

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

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

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

[0660] The signal processing process of the receiving device may be configured in reverse order of the signal processing process of the transmitter. Specifically, the processor of the receiving device performs decoding and demodulation on a wireless signal received externally through the antenna port(s) of the transceiver. The receiving device 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 originally intended to be transmitted by the transmitting device. The receiving device (1820) may include a signal restorer for restoring the received signal to a baseband signal, a multiplexer for combining and multiplexing the 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 performing their functions or as individual 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.

[0661] FIG. 30 illustrates an example of a wireless communication device according to an implementation example of the present disclosure.

[0662] Referring to FIG. 30, 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 GPS (Global Positioning System) chip (2360), a sensor (2365), a memory (2330), a SIM (Subscriber Identification Module) card (2325), a speaker (2345), and a microphone (2350). There may be a plurality of antennas and processors.

[0663] The processor (2310) can implement the functions, procedures, and methods described in this specification. The processor (2310) of FIG. 30 may be the processor (102, 202) of FIG. 27.

[0664] 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. 30 may be the memory (104, 204) of FIG. 27.

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

[0666] 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. 30 may be the transceiver (106, 206) of FIG. 29.

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

[0668] Fig. 30 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. 30. For example, 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.

[0669] Figure 31 illustrates another example of a wireless device.

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

[0671] The difference between the example of the wireless device described in FIG. 27 and the example of the wireless device in FIG. 31 is that in FIG. 27, the processor (102, 202) and the memory (104, 204) are separated, whereas in the example of FIG. 31, the memory (104, 204) is included in the processor (102, 202). For example, the processor and the memory may constitute a single chipset.

[0672] Fig. 32 illustrates a communication system (1) applicable to this specification.

[0673] Referring to FIG. 32, a communication system (1) applied to the present specification 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.

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

[0675] 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 specification.

[0676] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined and implemented as a device, and the technical features of the device claims of this specification may be combined and implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a method.

Claims

1. In the method, A terminal (user equipment: UE) receives at least one random access channel (RACH) configuration from a network, and The terminal performs PRACH (physical random access channel) repetition based on at least one RACH setting, The above terminal is a subband full duplex (SBFD) aware UE that recognizes subband full duplex (SBFD). A method characterized in that the above PRACH repetition is performed based on one type of ROs among i) valid legacy ROs (random access channel occasions) and ii) valid additional ROs.

2. In paragraph 1, A method characterized in that the terminal supports PRACH transmission that repeatedly transmits a preamble only in the valid legacy ROs and PRACH transmission that repeatedly transmits a preamble only in the valid additional ROs.

3. A method according to claim 1, characterized in that the PRACH repetition is performed based on one of a legacy RO group consisting of the valid legacy ROs and an additional RO group consisting of the valid additional ROs.

4. A method according to claim 1, characterized in that legacy ROs valid for a non-SBFD aware UE are also valid for the UE.

5. In paragraph 1, A method characterized in that, when at least one RACH configuration is a single RACH configuration, ROs within an uplink subband in SBFD symbols are included in valid ROs for the terminal.

6. In paragraph 1, A method characterized in that, when the at least one RACH configuration is two separate RACH configurations including a legacy RACH configuration and an additional RACH configuration, ROs within the uplink subband in SBFD symbols configured by the additional RACH configuration are included in the valid ROs for the terminal.

7. In paragraph 6, A method characterized in that, if the at least one RACH configuration is two separate RACH configurations including the legacy RACH configuration and the additional RACH configuration, additional ROs in non-SBFD symbols configured by the additional RACH configuration are invalid ROs for the terminal.

8. In paragraph 1, A method characterized in that the additional ROs include: i) ROs within SBFD symbols configured as downlink by a time division duplex (TDD) configuration and ROs spanning SBFD symbols configured as downlink by the TDD configuration and SBFD symbols configured as flexible, when the at least one RACH configuration is a single RACH configuration; and ii) ROs configured by the additional RACH configuration, when the at least one RACH configuration is two separate RACH configurations including a legacy RACH configuration and an additional RACH configuration.

9. In paragraph 1, The terminal receives a configured repetition number N from the network, A method characterized in that, if PRACH transmission using an additional RO group including the above N valid additional ROs fails, switching to PRACH transmission using a legacy RO group including valid legacy ROs is allowed.

10. In paragraph 9, A method characterized in that, if the PRACH transmission using the additional RO group fails after attempting the PRACH transmission a set number of times, switching to the PRACH transmission using the legacy RO group.

11. In paragraph 10, A method characterized in that the above N value and the above determined number of times are set by the network.

12. In paragraph 10, A method characterized in that the configured repetition number N is one of a plurality of candidate values, and the determined number of repetitions is one of the plurality of candidate values.

13. In paragraph 1, A method characterized in that, before applying power ramping after the terminal fails to transmit PRACH using an additional RO group including valid additional ROs, it is allowed to switch to PRACH transmission using a legacy RO group including valid legacy ROs.

14. In paragraph 13, A method characterized in that, after attempting PRACH transmission using the additional RO group a predetermined number of times and failing to transmit the PRACH, switching to PRACH transmission using the legacy RO group before applying the power ramping.

15. In paragraph 1, A method characterized by receiving downlink control information (DCI) from the network, the DCI including a 1-bit field that informs the terminal to use an additional RO or legacy RO in the PRACH repetition.

16. The terminal (user equipment: UE) is At least one transmitter / receiver; At least one memory; and At least one processor connected to at least one transceiver and at least one memory, wherein said at least one memory comprises instructions that are executed by said at least one processor to perform operations, The above actions are, The terminal receives at least one random access channel (RACH) setting from the network, and The terminal performs PRACH (physical random access channel) repetition based on at least one RACH setting, The above terminal is a subband full duplex (SBFD) aware UE that recognizes subband full duplex (SBFD). A terminal characterized in that the above PRACH repetition is performed based on one type of ROs among i) valid legacy ROs (random access channel occasions) and ii) valid additional ROs.

17. The device, At least one memory; and At least one processor operably coupled to at least one memory, wherein said at least one memory comprises instructions that are executed by said at least one processor to perform operations, The above actions are, Receive at least one random access channel (RACH) configuration from the network, and Perform PRACH (physical random access channel) repetition based on at least one RACH setting, The above device is included in a subband full duplex (SBFD) aware UE that recognizes SBFD, A device characterized in that the above PRACH repetition is performed based on one type of ROs among i) valid legacy ROs (random access channel occasions) and ii) valid additional ROs.

18. At least one computer readable medium (CRM) containing instructions based on being executed by at least one processor, Receive at least one random access channel (RACH) configuration from the network, and Perform PRACH (physical random access channel) repetition based on at least one RACH setting, The above CRM is included in a subband full duplex (SBFD) aware UE that recognizes SBFD, A CRM characterized in that the above PRACH repetition is performed based on one type of ROs among i) valid legacy ROs (random access channel occasions) and ii) valid additional ROs.

19. In the method, A base station transmits at least one random access channel (RACH) configuration to a SBFD aware user equipment (UE) that is aware of subband full duplex (SBFD), and The base station repeatedly receives a PRACH (physical random access channel) from the SBFD-aware terminal based on at least one RACH setting, A method characterized in that the repeated reception of the above PRACH is performed based on one type of RO among i) valid legacy ROs (random access channel occasions) and ii) valid additional ROs.

20. The base station, At least one transmitter / receiver; At least one memory; and At least one processor connected to at least one transceiver and at least one memory, wherein said at least one memory comprises instructions that are executed by said at least one processor to perform operations, The above actions are, Transmit at least one random access channel (RACH) configuration to a subband full duplex (SBFD) aware user equipment (SBFD aware user equipment), and Receiving a PRACH (physical random access channel) repeatedly from the SBFD-aware terminal based on at least one RACH setting, A base station characterized in that the repeated reception of the above PRACH is performed based on one type of RO among i) valid legacy ROs (random access channel occasions) and ii) valid additional ROs.

Images