Method and apparatus for controlling power of random access process in sub-band full duplex communication system

Abstract

The present disclosure relates to PRACH transmission, wherein a terminal determines power for transmission of a PRACH, and transmits the PRACH using the power through ROs of any one type from among legacy ROs and additional ROs. The terminal: receives, from a network, individual power control parameters for transmission of the PRACH in the legacy ROs and the additional ROs; on the basis that the terminal is provided with information related to an RO type from the network, transmits the PRACH through an RO of the RO type; and on the basis that the terminal is not provided with the information from the network, transmits the PRACH by selecting an RO of a specific RO type on the basis of an SSB RSRP threshold.

Description

Power control method and device for random access process in subband full-duplex communication system

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

[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 prior art, a RACH opportunity (abbreviated as RO) for transmitting a preamble for random access was set only on HD resources. However, in NR or a wireless communication system after NR, RO may be set not only on HD resources but also on SBFD resources.

[0007] At this time, SBFD and non-SBFD time resources may have different channel conditions and interference characteristics. Therefore, considering these factors, it is necessary to define a method for performing the random access process, and more specifically, a power control method for the random access process.

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

[0009] A method for controlling power in a random access process of a terminal recognizing subband full-duplex communication (SBFD) in a wireless communication system and a device using the method are provided. According to the method, the terminal determines power for transmission of a PRACH, and transmits the PRACH at the power in one type of legacy random access channel occasions (ROs) and additional ROs, wherein the terminal receives individual power control parameters for transmission of the PRACH in the legacy ROs and the additional ROs from a network, and transmits the PRACH through an RO of the RO type based on the terminal having received information related to the RO type from the network, and transmits the PRACH based on the terminal not having received the information from the network, and selects a specific RO type based on an SSB (Synchronization Signal / PBCH block) RSRP (Reference Signal Received Power) threshold and transmits the PRACH.

[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 provides individual power control parameters for transmission of a physical random access channel (PRACH) in legacy random access channel occasions (ROs) and additional ROs to a terminal, and the base station receives a PRACH having a specific power from the terminal in one type of ROs among the legacy ROs and the additional ROs, wherein the base station provides information indicating one type to the terminal.

[0012] According to the present disclosure, the purpose of PRACH transmission can be set differently according to different RO types, and the terminal can effectively transmit PRACH by selecting an RO type suitable for the setting.

[0013] In addition, separate power control parameters are provided for different RO types, so that appropriate power control can be performed for different RO types that are likely to have different channel characteristics or interference amounts, thereby enabling efficient PRACH transmission.

[0014] In addition, the conditions for performing PRACH transmission by switching the RO type in a situation where different RO types are mixed are clearly defined, so that ambiguity does not occur between the network and the terminal.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0034] Figure 19 illustrates an association pattern according to the mapping rules of SSB and RO.

[0035] Figure 20 illustrates an operation method of a terminal according to one embodiment of the present disclosure.

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

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

[0038] Figure 23 illustrates a wireless device applicable to the present specification.

[0039] Figure 24 illustrates another example of a wireless device.

[0040] Figure 25 illustrates an example of a signal processing module structure.

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

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

[0043] Fig. 28 illustrates a communication system (1) applicable to this specification.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0064] In this specification, transmitting a specific channel (e.g., a terminal transmitting a PRACH) may mean transmitting related information / data / signal (e.g., a preamble) via the specific channel (e.g., a PRACH). Similarly, receiving a specific channel (e.g., a base station receiving a PRACH) may mean receiving related information / data / signal (e.g., a preamble) via the specific channel (e.g., a PRACH).

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

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

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

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

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

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

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

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

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

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

[0075] Wireless Resource Structure

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

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

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

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

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

[0081] [Table A]

[0082]

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

[0084] [Table B]

[0085]

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

[0087] [Table C]

[0088]

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

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

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

[0092] [Table D]

[0093]

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

[0095] [Table E]

[0096]

[0097] FIG. 3 illustrates a slot structure of an NR frame according to an embodiment of the present disclosure. The embodiment of FIG. 3 can be combined with various embodiments of the present disclosure.

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

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

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

[0101] 1. DL only setting

[0102] 2. UL only setting

[0103] 3. Mixed UL-DL settings

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

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

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

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

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

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

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

[0111] Transmission Action:

[0112] Common SN;

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

[0114] Separate encryption for source and target cells.

[0115] Receiving action:

[0116] Separate decryption for source and target cells;

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

[0118] Common PDCP reordering;

[0119] Sequential delivery and duplicate detection;

[0120] Common buffer management.

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

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

[0123] UE RF / baseband requirements

[0124] To minimize interruption, the UE must continue to transmit and receive data with the source cell when performing a random access procedure to the target cell, regardless of whether SAPS or DAPS is used. This is only possible if the UE supports simultaneous transmission and reception with both cells. 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.

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

[0126] For UEs with Dual Rx / Single Tx RF chains, simultaneous UL data transmission to both cells can be supported if certain requirements are met, such as the bandwidth of the source cell being larger than that of the target cell. Otherwise, a UL 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0141] Full duplex operation for NR

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

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

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

[0145] Referring to Fig. 5, the structure in which DL and UL are allocated on the frequency axis of subband-wise full duplex (SBFD) and spectrum-sharing full duplex (SSFD) can be understood. In the case of SBFD as in Fig. 5 (a), 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 as in Fig. 5 (b), 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.

[0146] This full-duplex (FD) communication can be combined 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.

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

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

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

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

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

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

[0153] RACH (random access channel) procedure

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

[0155] Settings for PRACH transmission.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0179] [Table 1]

[0180]

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

[0182] For unpaired spectra:

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

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

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

[0186] within the UL symbol, or

[0187] Not preceding the SS / PBCH block within the PRACH slot, and at least N blocks after the last downlink symbol. 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.

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

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

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

[0191] [Table 2]

[0192]

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

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

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

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

[0197] T switch is the switching gap duration.

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

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

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

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

[0202] [Table 3]

[0203]

[0204]

[0205]

[0206]

[0207]

[0208]

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

[0210] [Table 4]

[0211]

[0212]

[0213]

[0214]

[0215]

[0216]

[0217]

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

[0219] [Table 5]

[0220]

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

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

[0223] OFDM baseband signal generation for PRACH

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

[0225] [Formula 1]

[0226]

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

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

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

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

[0231] 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 is started. Otherwise, it is provided by msg1-FrequencyStart.

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

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

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

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

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

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

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

[0239] [Formula 2]

[0240]

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

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

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

[0244] △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:

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

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

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

[0248] n slot RA is given as follows:

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

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

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

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

[0253] 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}.

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

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

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

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

[0258] [Table 6]

[0259]

[0260] PRACH repetition

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

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

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

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

[0265] The association period for mapping SS / PBCH block indices to PRACH opportunities starts from frame 0, and 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.

[0266] Below, we describe the HD operations supported in NR.

[0267] <Slot Settings>

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

[0269] The following applies to each serving cell:

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

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

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

[0273] ii) pattern1.

[0274] pattern1 can provide:

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

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

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

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

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

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

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

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

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

[0284] Pattern 2 can provide:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0331] Here the symbols are set as follows:

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

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

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

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

[0336] 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;

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

[0338] iii) A PDCCH, PDSCH or CSI-RS on a flexible symbol is received in a reference cell by a higher layer, and a DCI format is set to be detected for scheduling transmission in that symbol in another cell.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0352] UE procedure for determining slot format

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

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

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

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

[0357] 1) ID of serving cell by servingCellId

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

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

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

[0361] 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

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

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

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

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

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

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

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

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

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

[0371] [Table 9] shows an example of a slot format for a normal cyclic prefix.

[0372] [Table 9]

[0373]

[0374]

[0375] 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 μ.

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

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

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

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

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

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

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

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

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

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

[0386] 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, 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 including an SFI-index field value indicating the set of symbols of the corresponding slot to uplink.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0404] 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

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

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

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

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

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

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

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

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

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

[0414] 3) The UE receives the PDCCH.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0437] FIG. 12 and FIG. 13 illustrate examples of flexible slots with SBFD settings applied according to one embodiment of the present disclosure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0470] Figure 19 illustrates an association pattern according to the mapping rules of SSB and RO.

[0471] Figure 19 (a) illustrates an association pattern of SSB-to-RO based on legacy mapping rules.

[0472] Figure 19 (b) illustrates an RO group of two repeated ROs having different starting RBs.

[0473] Figure 19 (c) illustrates an RO group of two repeated ROs having the same starting RB diagram.

[0474] In some embodiments, only ROs in which the starting RB (resource block: resource block) of the first RO set as an RO group in a PRACH repeatedly transmitted N times and the RB positions of the remaining N-1 ROs are the same can be used for repetition.

[0475] It may be questionable whether the starting RBs of ROs can be set differently at different times for multiple PRACH transmissions. For example, similar to conventional frequency hopping, whether explicit hopping offset settings are supported for multiple PRACH transmissions, and whether ROs within an RO group can have different starting RBs without hopping offset settings, may be a concern.

[0476] In this regard, the starting RB of ROs within the RO group may vary over time.

[0477] For example, if frequency hopping is supported within a RO group, frequency index offsets can be defined / indicated between different ROs within a RO group.

[0478] Alternatively, if the same set of frequency domain ROs for the selected SSB / CSI-RS occur at different times, the configuration of PRACH frequency hopping can be similar to PUSCH frequency hopping, for example, using a frequency hopping offset. If the same number of frequency domain ROs for the selected SSB / CSI-RS occur at different times and are located on different frequency resources over time, the UE can transmit on the same RO based on the RO with the lowest frequency resource among the ROs associated with the same SSB.

[0479] Alternatively, the starting RBs of ROs in one RO group may be different for different time zones in case of multiple PRACH transmissions.

[0480] Depending on the embodiment, different starting RBs may be supported across multiple PRACH transmissions. Frequency hopping across multiple PRACH transmissions may be implicitly enabled and configured by the gNB via RO group configuration.

[0481] When frequency hopping is supported, the RO group for frequency hopping can be determined through a hopping step in the time domain and a hopping offset in the frequency domain by considering additionally defined new frequency indices among the selected FDMed ROs mapped to the same SSB.

[0482] For multiple PRACH transmissions using the same Tx beam, the RO offset can be set or implicitly determined for frequency hopping.

[0483] Specific embodiments of the present disclosure

[0484] In an environment where 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, SBFD time resources and non-SBFD time resources may have different channel conditions and interference characteristics. Therefore, it is necessary to specify a method for performing a random access process, and more specifically, a power control method for the random access process, taking these factors into account.

[0485] When attempting to set PRACH power control for SBFD and non-SBFD symbols, two main methods can be considered. This disclosure describes detailed parameter adjustments for the two methods.

[0486] The first method is a method in which parameters indicated by a higher layer (e.g., RRC) are independently indicated for SBFD / non-SBFD symbols, and the second method is a method in which parameters indicated by a higher layer (RRC) are indicated with the same value for SBFD / non-SBFD symbols, but the terminal interprets and uses / applies the SBFD / non-SBFD symbols in different ways.

[0487] First, the overall process of the methods according to the present disclosure is outlined.

[0488] Option 1) One single RACH configuration. As described above, using a single RACH configuration may be referred to as RACH configuration option 1. According to RACH configuration option 1, legacy ROs and additional ROs may be configured. In this case, legacy ROs may be ROs that non-SBFD aware UEs and SBFD aware UEs can recognize, and may be configured in non-SBFD symbols and / or SBFD symbols (e.g., SBFD symbols configured as F (flexible) by tdd-UL-DL-ConfigurationCommon). When legacy ROs are configured in SBFD symbols configured as F (flexible) by tdd-UL-DL-ConfigurationCommon, the network may configure the ROs to be within UL usable PRBs. Additional ROs include i) ROs of SBFD symbols set to downlink by tdd-UL-DL-ConfigurationCommon and ii) ROs spanning SBFD symbols set to downlink by tdd-UL-DL-ConfigurationCommon and SBFD symbols set to F (flexible) by tdd-UL-DL-ConfigurationCommon.

[0489] Alt 1-1) No priority,

[0490] In general, it is necessary to determine whether to keep the same type of RO during retransmission.

[0491] ROs in the same SSB have no priority, and if ROs are selected based on certain criteria (such as RSRO), any type of RO combination can be used for retransmission.

[0492] If there is room for the RO type to change during retransmission, it may be necessary to measure RSRP.

[0493] Legacy rule: SSB_ with SS-RSRP legacyRO > SSB_ with rsrp-ThresholdSSB or SS-RSRP SBFDRO > rsrp-ThresholdSSB

[0494] SSB can be given differently depending on each RO type.

[0495] The rsrp-ThresholdSSB value can vary depending on the RO type. In this case, the gNB can implicitly influence the selection of additional or legacy ROs, with minimal impact on the standard. If not specifically defined, the same value can be used.

[0496] During retransmission, at least one of the following actions may be considered:

[0497] alt 1-1-1: After a previous transmission failure, you can retransmit by selecting the RO type that satisfies the given conditions without priority.

[0498] alt 1-1-2: Can keep the same RO type during retransmission.

[0499] alt 1-1-3: If the previous transmission fails after a legacy RO transmission, the retransmission can be limited to a legacy RO retransmission.

[0500] alt 1-1-4: If a previous transmission fails after a SBFD RO transmission, retransmissions can be limited to legacy RO retransmissions.

[0501] alt 1-1-5: If the previous transmission fails, retransmission can be limited to legacy RO retransmission.

[0502] alt 1-1-6: You can limit legacy RO retransmissions after a certain number of failed transmissions.

[0503] After all retransmissions fail, you may consider at least one of the following actions:

[0504] alt 1-1-1: After a previous transmission failure, you can select and transmit the RO type that satisfies the given conditions without priority.

[0505] alt 1-1-2: If the previous transmission fails after a legacy RO transmission, the next first transmission can be limited to a legacy RO transmission.

[0506] alt 1-1-3: If the previous transmission fails after a SBFD RO transmission, the next first transmission can be limited to a legacy RO transmission.

[0507] alt 1-1-4: If the previous transmission fails, the next first transmission can be limited to a legacy RO transmission.

[0508] Alt 1-2) Prioritize

[0509] Alt 1-2-1) Priority can be signaled through upper layer signaling.

[0510] Alt 1-2-2) You can select additional ROs first.

[0511] SSB_ with SS-RSRP SBFDRO > rsrp-ThresholdSSB

[0512] During retransmission, the following actions can be considered:

[0513] alt 1-2-2-1: After a previous transmission failure, you can retransmit by selecting the RO type that satisfies the given conditions without priority.

[0514] alt 1-2-2-2: Can keep the same additional RO type during retransmission.

[0515] alt 1-2-2-3: If the previous transmission fails, retransmission can be limited to legacy RO retransmission.

[0516] After all retransmissions have failed, the following actions can be considered:

[0517] alt 1-2-2-1: After a previous transmission failure, the first transmission can be performed by selecting the RO type that satisfies the given conditions without priority.

[0518] alt 1-2-2-2: If the previous transmission fails, the next first transmission can be limited to a legacy RO transmission.

[0519] The rsrp-ThresholdSSB value can be given to each RO type.

[0520] Alt 1-2-3) How to select legacy ROs first.

[0521] SSB_ with SS-RSRP legacyRO > rsrp-ThresholdSSB

[0522] The following actions can be considered during retransmission:

[0523] alt 1-2-3-1: After a previous transmission failure, you can retransmit by selecting the RO type that satisfies the given conditions without priority.

[0524] alt 1-2-3-2: Can keep the same RO type during retransmission.

[0525] After all retransmissions have failed, the following actions can be considered:

[0526] alt 1-2-3-1: After a previous transmission failure, you can select and transmit the RO type that satisfies the given conditions without priority.

[0527] alt 1-2-3-2: If the previous transmission fails, the next first transmission can be limited to a legacy RO transmission.

[0528] The rsrp-ThresholdSSB value can be given to each RO type.

[0529] Alt 1-3) It is possible to signal to higher layers whether to support Alt 1-1) or Alt 1-2).

[0530] Option 2) Two separate RACH configurations. As described above, two separate RACH configurations may be referred to as RACH configuration option 2, for example, one legacy RACH configuration and one additional RACH configuration may be used. RACH configuration option 2 may configure a legacy RO and an additional RO. A legacy RO may be an RO that is recognizable by a non-SBFD aware UE and an SBFD aware UE. A legacy RO may be configured by a legacy RACH configuration. An additional RO may refer to an RO configured by an additional RACH configuration.

[0531] Alt 2-1) Without priority,

[0532] SSB_ with SS-RSRP legacyRO > SSB_ with rsrp-ThresholdSSB and SS-RSRP SBFDRO > rsrp-ThresholdSSB

[0533] rsrp-ThresholdSSB values ​​can be given respectively.

[0534] The UE can select a set of ROs based on SSB measurements.

[0535] The same set of ROs can be maintained during retransmission.

[0536] If retransmission fails in the selected RACH settings,

[0537] Alt 2-1-1) It can work in the old way again without priority.

[0538] Alt 2-1-2) Fallback to legacy

[0539] Alt 2-2) Prioritize

[0540] Alt 2-2-1) You can select from RO by additional RACH settings.

[0541] During retransmission, the RO set is maintained, and if retransmission fails, Alt 2-2-1-1) can fall back to the legacy ROs without priority (additional ROs or legacy ROs can be selected depending on the situation), or Alt 2-2-1-2) can fall back to the legacy ROs.

[0542] rsrp-ThresholdSSB values ​​can be given respectively.

[0543] Alt 2-2-2) It can be selected from ROs by legacy RACH settings. During retransmission, the RO set is maintained, and if retransmission fails, Alt 2-2-2-1) It can operate in the conventional way without priority (additional ROs or legacy ROs can be selected depending on the situation), or Alt 2-2-2-2) It can operate in the legacy ROs. The rsrp-ThresholdSSB value can be given for each.

[0544] Alt 2-2-3) can signal priority to higher layers.

[0545] SBFD can exhibit lower latency in uplink transmission than non-SBFD. Furthermore, compared to non-SBFD configurations of DDDSUDDDSU, SBFD can allocate longer uplink time resources to the UE, and can increase cell range or coverage through long PRACHs or PRACH repetitions.

[0546] However, SBFD may cause cross link interference (CLI) between subbands, and antenna configurations may be used differently in SBFD than in non-SBFD, so system conditions may differ between SBFD and non-SBFD.

[0547] Furthermore, increasing PRACH power in SBFD may improve PRACH reception performance, but may cause significant interference to neighboring UEs. Lowering PRACH power in SBFD may reduce interference to neighboring UEs, but PRACH reception performance will deteriorate. Reception performance in this case may be worse than in non-SBFD, as interference from neighboring base stations or self-interference may also occur.

[0548] Accordingly, power control in SBFD and non-SBFD also needs to be set up through different methods.

[0549] Below, the power control method in SBFD and non-SBFD symbols is described in terms of the operation method according to the characteristics and the detailed parameters of each.

[0550] First, we can analyze the power control parameters in existing standards. The existing PRACH power control formula is as follows. This can be referenced in Section 7.4 of 3GPP TS 38.213.

[0551] [Formula 3]

[0552]

[0553] In Equation 3, P PRACH,b,f,c is the PRACH target received power provided by the upper layer for the active UL BWP b of carrier f of serving cell c, PREAMBLE_RECEIVED_TARGET_POWER.

[0554] P CMAX,f,c (i) is the UE configured maximum output power for carrier f of serving cell c within transmission occasion i.

[0555] PL b,f,cis the path loss for the active UL BWP b of carrier f based on the DL RS associated with the PRACH transmission in the active DL BWP of serving cell c.

[0556] If the active DL BWP is the initial DL BWP and has an SS / PBCH block and a specific CORESET multiplexing pattern (e.g., CORESET multiplexing pattern 2 or 3), the UE may select a PL based on the SS / PBCH block associated with the PRACH transmission. b,f,c can decide.

[0557] P in Equation 3 PRACH,target,f,c The parameter is provided by the upper layer parameter PREAMBLE_RECEIVED_TARGET_POWER, and PREAMBLE_RECEIVED_TARGET_POWER is set as follows.

[0558] PREAMBLE_RECEIVED_TARGET_POWER is set to preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) Х PREAMBLE_POWER_RAMPING_STEP + POWER_OFFSET_2STEP_RA.

[0559] Section 5.1.3 of 3GPP TS 38.321 describes how PREAMBLE_RECEIVED_TARGET_POWER is calculated.

[0560] For example, the MAC entity: for each random access preamble:

[0561] 1> If PREAMBLE_TRANSMISSION_COUNTER is greater than 1; and

[0562] 1> If no power ramping counter interruption notification is received from the lower layer; and

[0563] 1> If no LBT failure indication is received from the lower layer for the last random access preamble transmission; and

[0564] 1> If the selected SSB or CSI-RS is unchanged from the one selected in the last random access preamble transmission:

[0565] 2> Increase PREAMBLE_POWER_RAMPING_COUNTER by 1.

[0566] 1> Select the value of DELTA_PREAMBLE.

[0567] 1> Set PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP + POWER_OFFSET_2STEP_RA.

[0568] In this disclosure, P cmax , preambleReceivedTargetPower, PREAMBLE_POWER_RAMPING_COUNTER, PREAMBLE_POWER_RAMPING_STEP, POWER_OFFSET, etc., are individually set in SBFD and non-SBFD / shared, and the operation is explained.

[0569] I. Separated PRACH power control.

[0570] The simplest approach is to use separate parameters for power control in SBFD and non-SBFD symbols. However, providing terminals with independent information for each symbol for all parameters would incur significant signaling overhead and require a large amount of information. Therefore, parameters can be selectively and independently indicated as needed.

[0571] PRACH transmission is performed on available ROs, determined as valid or invalid, based on the validity rules agreed upon between the base station and the UE among all ROs designated by the base station. Among these available ROs, PRACH transmission is performed on ROs with SSB mapping that meets the UE's requirements.

[0572] Since this operation can occur across multiple frames, PRACH transmissions can occur across SBFD and non-SBFD due to the nature of SBFD systems where switching between SBFD / non-SBFD can occur within a single frame.

[0573] Accordingly, the terminal may transmit the PRACH only in SBFD symbols during PRACH transmission (case 1), may transmit the PRACH only in non-SBFD symbols (case 2), or may transmit the PRACH across SBFD symbols and non-SBFD symbols (case 3).

[0574] In this disclosure, the methods (scenarios) can be broadly divided into two types depending on the characteristics of each parameter. The first method can be used when independently controlling power between SBFD / non-SBFD within multiple cycles, and the second method can be used when organically controlling power between SBFD / non-SBFD within multiple cycles.

[0575] The first method is one that can be used without being restricted by any of the three cases mentioned above (PRACH transmission only in SBFD symbols, PRACH transmission only in non-SBFD symbols, and PRACH transmission across two types of symbols).

[0576] The second method is applicable if any of the three cases mentioned above (PRACH transmission only in SBFD symbols, PRACH transmission only in non-SBFD symbols, PRACH transmission across two types of symbols) are met.

[0577] Each method can operate independently, and one method may be to make power control in SBFD symbols identical to power control in non-SBFD symbols, depending on the purpose of the SBFD system operation. In the present disclosure, the following multiple methods may be used for the same PRACH transmission.

[0578] <Scenario 1. How to independently control power between SBFD and non-SBFD>

[0579] Method 1. How to set preambleReceivedTargetPower independently.

[0580] In PRACH transmission, receive power is one of the most important factors in determining whether the PRACH is successfully received. The base station requires a minimum receive power for successful PRACH reception, and the base station indicates to the UE its desired initial random access preamble receive power using a parameter called preambleReceivedTargetPower. PreambleReceivedTargetPower is used in step 4 RA (random access), and msgA-PreambleReceivedTargetPower is used in step 2 RA.

[0581] The advantage of this method is that the power of the entire SBFD / non-SBFD symbol can be adjusted by adjusting the underlying received target power, and the SBFD and non-SBFD operate independently, allowing relatively free power adjustment. The two parameters can be found in the RACH-ConfigGeneric and RACH-ConfigGenericTwoStepRA information elements (IEs), respectively, and in each case, the separate parameters can be provided as shown in Tables 10 and 11 below.

[0582] [Table 10]

[0583]

[0584] [Table 11]

[0585]

[0586] Method 2. How to independently set the parameters that determine maximum power.

[0587] The CLI generated by transmitting PRACH in SBFD symbol can degrade the reception performance of adjacent DL terminals. Therefore, to prevent CLI from occurring above a certain level, the maximum power of the PRACH of the terminal can be limited. The parameter related to this method is P, which explicitly determines the maximum power. cmax , there is preambleTransMax, which determines the maximum number of retransmissions of the terminal. The advantage of this method is that since the SBFD / non-SBFD power is controlled only for power above a certain level, there is no restriction for power below a certain level, and thus link quality can be maintained.

[0588] P cmax can be calculated by Equation 4 defined in 3GPP TS 38.101-1 Section 6.2.4.

[0589] [Formula 4]

[0590]

[0591] Each value that constitutes the above formula varies depending on the predefined power class of the terminal (see 3GPP TS 38.101-2 Table 6.2.1.0-1), the frequency used (FR1, FR2, etc.), or the waveform used (see TS 38.101-1 Section 6.2.2).

[0592] However, additionally, the base station may indicate additionalPmax to the terminal for CLI, such as NR-NS-PmaxList IE. In this case, a new additionalPmax may be indicated only for the SBFD symbol, as shown in Table 12 below.

[0593] [Table 12]

[0594]

[0595] You may define separate / separate parameters for SBFD in the NR-NS-PmaxList IE, or you may point to a new IE such as a separate NR-SBFD-PmaxList IE.

[0596] In PRACH transmission, when retransmission is performed multiple times, there is a function to increase the transmission power so that the base station can receive it better. At this time, there are two cases in which the retransmission power reaches its maximum. The first is the P described above. cmax The first is when the number of retransmissions reaches the maximum, and the second is when the number of retransmissions reaches the maximum. The parameter related to this is preambleTransMax, and the maximum number of retransmissions can be used to control the maximum power in SBFD / non-SBFD.

[0597] preambleTramsMax can be included in, for example, RACH-ConfigGeneric IE (Table 13) and RACH-ConfigGenericTwoStepRA IE (Table 14), and examples of application of separated parameters are as follows.

[0598] [Table 13]

[0599]

[0600] [Table 14]

[0601]

[0602] Among the PRACH transmission methods in SBFD systems, the feasibility of using a PRACH with a long preamble to increase cell coverage is being discussed. In the long preamble sequence configuration method, the subcarriers of the long preamble are 1.25 or 5 kHz, unlike the 15, 30, 60, and 120 kHz subcarriers of NR.

[0603] Accordingly, the maximum power of the terminal needs to be changed, and this can be reflected in Pmax. Changes in Pmax due to changes in the existing waveform or subcarriers are reflected in the maximum power reduction (MPR) or additional maximum power reduction (A-MPR). However, separately from these values, the MPR and A-MPR related to SBFD can be transmitted from the base station through upper layer signaling along with the power indication in the SBFD symbol related to PRACH. In addition, since the long preamble must be transmitted across SBFD and non-SBFD symbols, this indication method is not limited to SBFD symbols and does not restrict its use in non-SBFD symbols.

[0604] Method 3. How to independently set the parameters that determine the ramping counter.

[0605] If the base station fails to receive a PRACH transmission from a terminal, the terminal retransmits the PRACH. At this time, the retransmission is performed with a certain amount of increased power based on the previous transmission failure. The parameters related to this include the power ramping counter and the power ramping step.

[0606] The power ramping counter is a terminal parameter that records the number of times power ramping has been performed for a given retransmission. The terminal can set this parameter differently depending on the symbol type. The advantage of this method is that ramping-related information can be stored and managed separately, as antenna configuration, channel quality, and beaming can vary between SBFD and non-SBFD symbols.

[0607] For example, the terminal can store information about PREAMBLE_POWER_RAMPING_COUNTER_SBFD / PREAMBLE_POWER_RAMPING_COUNTER separately according to SBFD / non-SBFD symbols.

[0608] Method 4. How to independently set the parameters that determine the ramping step.

[0609] If reception at the base station fails during PRACH transmission, the terminal retransmits the PRACH. At this time, the retransmission is performed with a certain amount of power increased based on the previous transmission failure. The relevant parameters for this are the power ramping counter and the power ramping step. The power ramping step is a parameter that indicates the degree of power ramping for each transmission for this retransmission. The base station can set this parameter differently depending on the symbol type. The advantage of this method is that even if the initial power is the same in SBFD / non-SBFD symbols, the number of retransmissions to reach maximum power is differentiated, allowing the terminal to reach maximum power more quickly with fewer transmissions. For example, the base station can use the power ramping step separately in the RACH-ConfigGeneric IE (Table 15) and RACH-ConfigGenericTwoStepRA IE (Table 16) as shown below.

[0610] [Table 15]

[0611]

[0612] [Table 16]

[0613]

[0614] Scenario 2: How to organically control power between SBFD and non-SBFD

[0615] Method 1. How to organically set preambleReceivedTargetPower.

[0616] As mentioned above, in PRACH transmission, receive power is one of the most important factors in determining whether PRACH reception is successful. The base station requires a minimum receive power for successful PRACH reception, and the base station indicates to the UE the desired initial random access preamble receive power through a parameter called preambleReceivedTargetPower.

[0617] For example, in step 4 RA, preambleReceivedTargetPower is used, and in step 2 RA, msgA-PreambleReceivedTargetPower is used to indicate the desired first random access preamble reception power at the base station.

[0618] The two parameters mentioned above can be found in the RACH-ConfigGeneric IE (Table 17) and the RACH-ConfigGenericTwoStepRA IE (Table 18), respectively, and in each case, the power to be used in the SBFD symbol compared to the non-SBFD can be expressed through an offset for the corresponding parameter. The advantage of this method is that the power in the overall SBFD / non-SBFD symbol can be adjusted by adjusting the underlying received target power, and the SBFD and non-SBFD operate independently, allowing for relatively free power adjustment.

[0619] [Table 17]

[0620]

[0621] [Table 18]

[0622]

[0623] Method 2. How to organically set the parameters that determine maximum power.

[0624] The CLI generated by transmitting PRACH in SBFD symbol can degrade the reception performance of adjacent DL terminals. Therefore, to prevent CLI from occurring above a certain level, a limit can be placed on the maximum power of the PRACH of the terminal. The parameter related to this method is P, which explicitly determines the maximum power. cmax , there is preambleTransMax, which determines the maximum number of retransmissions of the terminal. The advantage of this method is that since the SBFD / non-SBFD power is controlled only for power above a certain level, there is no restriction for power below a certain level, and thus link quality can be maintained.

[0625] P cmax can be calculated by the formula defined in 3GPP TS 38.101-1 Section 6.2.4. Each value constituting the formula may vary depending on the predefined power class of the terminal (see 3GPP TS 38.101-2 Table 6.2.1.0-1), the frequency used (FR1, FR2, etc.), or the waveform used (see 3GPP TS 38.101-1 Section 6.2.2). However, the base station may additionally indicate additionalPmax to the terminal for CLI, such as NR-NS-PmaxList IE. In this case, a new PmaxOffset can be indicated only for the SBFD symbol, as in the formula below.

[0626] [Formula 5]

[0627] P CMax_SBFD =P CMax +P Offset_SBFD

[0628] PmaxOffset may define a separate parameter for SBFD in the above NR-NS-PmaxList IE, or it may point to a new IE such as NR-SBFD-PmaxList IE.

[0629] Method 4. How to organically set the parameters that determine the ramping step.

[0630] If the base station fails to receive a PRACH transmission from a terminal, the terminal retransmits the PRACH. At this time, the transmission is performed with a certain amount of increased power based on the previous transmission failure. The parameters related to this are the power ramping counter and the power ramping step. The power ramping step is a parameter that indicates the degree of power ramping for each retransmission. The base station can set this parameter differently depending on the symbol type. The advantage of this method is that even if the initial power is the same for SBFD / non-SBFD symbols, the number of retransmissions to reach maximum power is differentiated, allowing the terminal to reach maximum power more quickly with fewer transmissions. For example, the base station can use an offset for the power ramping step as shown in the equation below.

[0631] [Formula 6]

[0632] POWER_OFFSET_SBFD = (PREAMBLE_POWER_RAMPING_COUNTER - 1) Х (SBFD_PREAMBLE_POWER_RAMPING_STEP - PREAMBLE_POWER_RAMPING_STEP)

[0633] As an example of how to use the above offset, it can be applied to the formula below to obtain PREAMBLE_RECEIVED_TARGET_POWER. This formula can be applied when changing from an SBFD symbol to a non-SBFD symbol.

[0634] [Formula 7]

[0635] PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) Х PREAMBLE_POWER_RAMPING_STEP + POWER_OFFSET_SBFD

[0636] When changing from a non-SBFD symbol to an SBFD symbol, the formula below can be applied.

[0637] [Formula 8]

[0638] PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) Х PREAMBLE_POWER_RAMPING_STEP - POWER_OFFSET_SBFD

[0639] Alternatively, the offset can be directly instructed to the base station. For example, SBFD_PREAMBLE_POWER_RAMPING_STEP can be instructed through the RACH-ConfigGeneric IE (Table 19) and RACH-ConfigGenericTwoStepRA IE (Table 20). In this case, the method of storing it in PREAMBLE_RECEIVED_TARGET_POWER is the same as the above formula.

[0640] [Table 19]

[0641]

[0642] [Table 20]

[0643]

[0644] Since antenna configurations, channel quality, and beams may vary between SBFD and non-SBFD symbols, the ramping counter can be stopped for a single transmission rather than immediately ramping power when the symbol type changes during retransmission. The advantage of this method is that it can cover beams that may vary depending on each symbol type.

[0645] II. Shared PRACH Power Control

[0646] Shared PRACH power control is a method in which the UE performs different power control operations (reinterpretations) for each SBFD / non-SBFD symbol based on parameters instructed by the base station. In this case, since the base station only needs to receive instructions for one symbol type, the amount of data that the base station must transmit is reduced. For example, if a parameter is set / instructed to a value related to a non-SBFD symbol, when applied to an SBFD symbol, this parameter value can be set / instructed based on a specific rule or a reinterpreted value given in advance.

[0647] <Scenario 1. Independent power control between SBFD and non-SBFD>

[0648] Method 1. Independently setting the parameters that determine maximum power.

[0649] The CLI generated by transmitting PRACH in SBFD symbol can degrade the reception performance of adjacent DL terminals. Therefore, to prevent CLI from occurring above a certain level, a limit can be placed on the maximum power of the PRACH of the terminal. The parameter related to this method is P, which explicitly determines the maximum power. cmax, there is preambleTransMax, which determines the maximum number of retransmissions of the terminal. The advantage of this method is that since the SBFD / non-SBFD power is controlled only for power above a certain level, there is no restriction for power below a certain level, and therefore link quality can be maintained. The two parameters mentioned above can be found in the RACH-ConfigGeneric IE and RACH-ConfigGenericTwoStepRA IE, respectively, and the interpretation of the indicated parameters in each case is as shown in the examples described below.

[0650] P cmax can be calculated by the formula defined in 3GPP TS 38.101-1 Section 6.2.4. Each value constituting the formula varies depending on the predefined power class of the terminal (3GPP TS 38.101-2 Table 6.2.1.0-1), the frequency used (FR1, FR2, etc.), or the waveform used (3GPP TS 38.101-1 Section 6.2.2). At this time, a new power class can be registered for the SBFD symbol. In this case, P powerclass will change and the formulas affected by this are as follows:

[0651] [Formula 9]

[0652]

[0653] Each parameter in Equation 9 can refer to 3GPP TS 38.101-1 Section 6.2.4. For example, P EMAX,c is the value given by one of the additionalPmax fields of the p-Max IE or the NR-NS-PmaxList IE. P PowerClass is the maximum UE power without considering tolerance. ΔT IB,c is an additional tolerance for cell c. ΔP PowerBoost can be defined as 1 dB for power class 3 and 0.5 dB for power class 2.

[0654] P for SBFD symbol PowerClass - ΔP PowerClass The value can be changed. For example, when an SBFD aware UE is operating at 26 dB in non-SBFD symbols, ΔP can be changed to operate at 23 dB in SBFD symbols. PowerClass Set to 3dB and apply P in SBFD symbol CMAX can operate at 3 dB lower power. This is equivalent to the UE operating at power class 2 in non-SBFD symbols and power class 3 in SBFD symbols, which is a way to reuse existing power classes.

[0655] For example, ΔP PowerClass For a power class 2 capable UE, it may be X1 dB, and for a power class 1.5 capable UE, it may be X2 dB, when a SBFD-aware UE performs SBFD operation in SBFD symbols. Here, X1 may be 3 dB, and X2 may be 6 dB. Alternatively, it may be 3 dB, and for a power class 2 capable UE, it may be 6 dB, when P-max is indicated to be less than or equal to 23 dBm. Alternatively, it may be 3 dB, and for a power class 1.5 capable UE, it may be 3 dB, when P-max is indicated to be between 23 dBm and 26 dB. Alternatively, it may be 3 dB, when the requirement of the default power class applies in the band where the UE indicates power class 2, and the terminal has SUL settings configured. ΔP PowerClass In some cases it may be 0 dB.

[0656] As mentioned above, among the PRACH transmission methods using the SBFD system, the possibility of using a PRACH using a long preamble to increase the cell range is being discussed. However, in the sequence configuration method of the long preamble, the subcarrier of the long preamble uses 1.25 or 5 kHz, unlike the 15, 30, 60, and 120 kHz subcarriers of NR. Accordingly, the maximum power of the terminal needs to be changed, which is P max can be reflected in P according to changes in the existing waveform or changes in the subcarrier. max The change is reflected in the maximum power reduction (MPR) or additional maximum power reduction (A-MPR). Therefore, when transmitting using a long preamble, the case of a long preamble in an SBFD symbol can be additionally defined and used in advance in relation to MPR and A-MPR. In addition, since the long preamble must be transmitted across SBFD symbols and non-SBFD symbols, this indication method is not limited to SBFD symbols and can also be used in non-SBFD symbols.

[0657] Scenario 2: How to organically control power between SBFD and non-SBFD

[0658] Method 1. How to set preambleReceivedTargetPower through offset.

[0659] In PRACH transmission by a UE, the received power is one of the most important factors in determining whether the base station successfully receives the PRACH. The base station requires the minimum received power for successful PRACH reception, and the base station instructs the UE on the desired initial random access preamble received power through a parameter called preambleReceivedTargetPower. In step 4 RA, preambleReceivedTargetPower is used, and in step 2 RA, msgA-PreambleReceivedTargetPower is used. At this time, the UE stores the instructed power in a terminal variable called PREAMBLE_RECEIVED_TARGET_POWER. In the SBFD symbol, a predefined offset is added to the stored value to calculate the value for SBFD operation. For example, a terminal variable such as PREAMBLE_RECEIVED_TARGET_POWER_SBFD_OFFSET can be set. The terminal variable set here does not mean a parameter additionally instructed by the base station, but rather a value that is predetermined as an agreement for SBFD operation based on non-SBFD operation.

[0660] The terminal can calculate the preambleReceivedTargetPower in SBFD by adding a predefined PREAMBLE_RECEIVED_TARGET_POWER_SBFD_OFFSET to parameters such as preambleReceivedTargetPower instructed by the base station.

[0661] The advantages of this method include the ability to adjust the power of the entire SBFD / non-SBFD symbol by adjusting the underlying received target power, and the ability to control power with relatively few instructions as SBFD and non-SBFD work organically. The value of PREAMBLE_RECEIVED_TARGET_POWER_SBFD_OFFSET can be positive or negative.

[0662] Method 2. How to organically set the parameters that determine maximum power.

[0663] The CLI generated by transmitting PRACH in SBFD symbol can degrade the reception performance of adjacent DL terminals. Therefore, to prevent CLI from occurring above a certain level, a limit can be placed on the maximum power of the PRACH of the terminal. The parameter related to this method is P, which explicitly determines the maximum power. cmax , there is preambleTransMax which determines the maximum number of retransmissions of the terminal.

[0664] P cmax If PCMAX_SBFD_offset is predefined or instructed to the terminal, it is stored in a terminal variable called PCMAX. In the SBFD symbol, a predefined offset is added to the stored value related to non-SBFD to produce a value in SBFD operation. For example, a terminal variable such as PCMAX_SBFD_offset can be set. The terminal variable set here does not mean a parameter additionally instructed by the base station, but a value determined in advance as a promise for SBFD operation. The PCMAX_SBFD_offset value can be positive / negative. The terminal can use the P that is preset or instructed by the base station. cmax The PCMAX at SBFD can be calculated by adding a predefined PCMAX_SBFD_offset to parameters such as .

[0665] When preambleTransMax is indicated to the terminal, the SBFD symbol calculates the value in SBFD operation by adding a predefined offset to the value stored in relation to non-SBFD. For example, a terminal variable such as preambleTransMax_SBFD_offset can be set. The terminal variable set here does not mean a parameter additionally indicated by the base station, but rather a value determined in advance as a promise for SBFD operation. The terminal can calculate preambleTransMax in SBFD by adding the predefined preambleTransMax_SBFD_offset to a parameter such as the preset preambleTransMax.

[0666] The advantage of this method is that since the SBFD / non-SBFD power is controlled only for power above a certain level, there is no restriction for power below a certain level, and thus link quality can be maintained.

[0667] Method 3. How to organically set the parameters that determine the ramping counter.

[0668] If the base station fails to receive a PRACH transmission from a terminal, the terminal retransmits the PRACH. At this time, the retransmission is performed with a certain amount of increased power based on the previous transmission failure. The parameters related to this include the power ramping counter, preambleTransMax, and power ramping step.

[0669] The power ramping counter is a parameter in the terminal that records the number of times power ramping has been performed for this retransmission. The terminal can set this parameter differently depending on the symbol type. The power ramping counter starts from 1 and increases by 1 for each retransmission. It is stored in the terminal variable called PREAMBLE_POWER_RAMPING_COUNTER. In the SBFD symbol, the value for the SBFD operation is calculated by adding a predefined offset to the stored value. For example, a terminal variable such as PREAMBLE_POWER_RAMPING_COUNTER_OFFSET can be set. The terminal variable set here does not mean a parameter additionally indicated by the base station, but rather a value determined in advance as an agreement for the SBFD operation. The terminal can calculate the PREAMBLE_POWER_RAMPING_COUNTER in SBFD by adding a predefined PREAMBLE_POWER_RAMPING_COUNTER_OFFSET to parameters such as PREAMBLE_POWER_RAMPING_COUNTER.

[0670] When preambleTransMax is indicated to the terminal, the SBFD symbol calculates the value in SBFD operation by adding a predefined offset to the stored value. For example, a terminal variable such as preambleTransMax_SBFD_offset can be set. The terminal variable set here does not mean a parameter additionally indicated by the base station, but rather a value determined in advance as a promise for SBFD operation. The terminal can calculate preambleTransMax in SBFD by adding the predefined preambleTransMax_SBFD_offset to a parameter such as the preset preambleTransMax. The preambleTransMax_SBFD_offset value can be a positive / negative value.

[0671] When a power ramping step is instructed to the terminal, it is stored in the terminal variable called PREAMBLE_POWER_RAMPING_STEP by msgA-PreamblePowerRampingStep or powerRampingStepHighPriority or powerRampingStep. In the SBFD symbol, a predefined offset is added to the stored value to calculate the value in the SBFD operation. For example, a terminal variable such as PREAMBLE_POWER_RAMPING_STEP_OFFSET can be set. The terminal variable set here does not mean a parameter additionally instructed by the base station, but a value that is predetermined as an agreement for the SBFD operation. The terminal can calculate the PREAMBLE_POWER_RAMPING_STEP in SBFD by adding the predefined PREAMBLE_POWER_RAMPING_STEP_OFFSET to a parameter such as PREAMBLE_POWER_RAMPING_STEP preset by the base station. The PREAMBLE_POWER_RAMPING_STEP_OFFSET value can be positive or negative.

[0672] The advantage of this method is that ramping-related information can be stored and managed separately, as antenna configuration, channel quality, beam, and other factors can vary depending on the situation in SBFD and non-SBFD symbols. For example, terminals can organically store ramping counter information according to SBFD and non-SBFD symbols.

[0673] In SBFD symbols, the ramping counter may not need to start from 1. This is due to the characteristics of SBFD systems, which can generate numerous CLIs in the surrounding area and the transmitting terminal itself. Therefore, to overcome or reduce CLIs, it may be necessary to quickly reach maximum power and terminate transmission. Therefore, for SBFD symbols, an offset, such as RAMPING_COUNTER_Offset_SBFD, can be added to reach maximum power more quickly than for non-SBFD symbols. In this case, the ramping counter in SBFD symbols can be calculated as follows.

[0674] [Formula 10]

[0675] RAMPING_COUNTER_SBFD = RAMPING_COUNTER + RAMPING_COUNTER_OFFSET_SBFD

[0676] Additionally, since antenna configurations, channel quality, beams, etc. may vary depending on the situation in SBFD and non-SBFD symbols, the ramping counter can be stopped for a single transmission rather than immediately ramping power when the symbol type changes during retransmission. The advantage of this method is that it can cover beams that may vary depending on each symbol type.

[0677] III. General procedure

[0678] Below, we describe the overall procedure for using the aforementioned methods. This section merely exemplifies the use of the aforementioned methods and does not limit their potential uses.

[0679] First, due to the characteristics of the SBFD symbol, uplink transmission can be performed through the uplink subband in the SBFD symbol even when downlink transmission is performed in a non-SBFD symbol. At this time, when RACH transmission is triggered, it is necessary to wait until the uplink symbol is set in the non-SBFD symbol, but transmission can be performed through the uplink subband in the SBFD symbol. Therefore, performing PRACH transmission in the SBFD symbol compared to the non-SBFD symbol has the advantage of enabling faster PRACH transmission with less delay.

[0680] Based on the above advantages, in order to obtain transmission gains through less delay in a system where SBFD and non-SBFD symbols are mixed, when PRACH transmission is triggered and non-SBFD symbols are set to downlink or flexible, transmission can be attempted first through SBFD symbols.

[0681] The advantage of this method is that it reduces the additional delay required to wait for uplink configuration when non-SBFD symbols are configured as downlink or flexible.

[0682] This method can continuously attempt to transmit PRACH through non-SBFD symbols until a certain number of retransmissions is reached, i.e., until the PREAMBLE_TRANSMISSION_COUNTER variable of the terminal reaches a certain constant. At this time, the terminal can attempt to transmit PRACH through non-SBFD symbols without excluding the possibility of attempting PRACH transmission through non-SBFD symbols if a non-SBFD symbol is set to uplink during the continuous attempt.

[0683] However, when attempting to transmit via the SBFD symbol, as the PREAMBLE_TRANSMISSION_COUNTER increases, the PRACH transmission power also increases, which may cause CLI to surrounding terminals.

[0684] To address this issue, preambleReceivedTargetPower can be adjusted. For example, in the case of repetition, PRACHs transmitted from the base station can be combined and received. Therefore, the minimum preambleReceivedTargetPower required for successful reception may vary. The base station can consider this and lower preambleReceivedTargetPower by the number of repetitions, or arbitrarily lower the preambleReceivedTargetPower indicated from the terminal's perspective.

[0685] Alternatively, when the PREAMBLE_TRANSMISSION_COUNTER variable of the terminal reaches a certain constant, the terminal may stop transmitting PRACH via SBFD symbols and attempt only PRACH transmission via non-SBFD symbols.

[0686] For example, the maximum number of transmissions of the entire retransmission can be determined using the indicated preambleTransMax parameter, and a parameter can be defined that only defines the maximum number of retransmissions of the PRACH operating in SBFD (so that the remaining number of transmissions can be deducted from the total number of retransmissions as the PRACH operating in SBFD) to adjust the number of transmissions of the PRACH operating in SBFD.

[0687] In this case, the terminal adds one PREAMBLE_TRANSMISSION_COUNTER variable for each retransmission, and switches from SBFD operation to non-SBFD operation when the PREAMBLE_TRANSMISSION_COUNTER variable becomes equal to the SBFD-specific maximum number of retransmissions.

[0688] The PREAMBLE_TRANSMISSION_COUNTER variable of the terminal is not initialized upon switching, and is added by one for each retransmission even in non-SBFD operation, and the retransmission is terminated when the value of the finally indicated preambleTransMax parameter is reached.

[0689] As another example, a parameter maxtrans_SBFD indicating the maximum number of retransmissions of a PRACH operating as SBFD can be defined, and this can operate together with a parameter preambleTransMax indicating the number of retransmissions of the entire PRACH so that the terminal can determine the maximum number of retransmissions of a PRACH operating as non-SBFD as preambleTransMax - maxtrans_SBFD.

[0690] Additionally, if a constant for controlling the PREAMBLE_TRANSMISSION_COUNTER variable of the terminal is called maxtrans_SBFD in SBFD symbols and maxtras_non-SBFD in non-SBFD symbols, then max(maxtrans_SBFD, maxtras_non-SBFD) can be set to be less than or equal to the maximum number of retransmissions of an SBFD non-aware UE, or min(maxtrans_SBFD, maxtras_non-SBFD) can be set to be greater than or equal to the maximum number of retransmissions of an SBFD non-aware UE.

[0691] Alternatively, the PREAMBLE_POWER_RAMPING_COUNTER can be considered instead of the PREAMBLE_TRANSMISSION_COUNTER in SBFD symbols. In this case, if power ramping is not performed during PRACH retransmission, the PREAMBLE_TRANSMISSION_COUNTER and the PRACH power do not increase proportionally. In contrast, the PREAMBLE_POWER_RAMPING_COUNTER can be more directly related to the PRACH power because the counter does not increase when power ramping is not performed, which allows for more accurate determination of symbol type usage according to the PRACH power level.

[0692] Alternatively, the abort trigger for SBFD symbol transmission can be transmitted through the expected link quality of the SBFD symbol, rather than through a retransmission counter. In this case, the terminal can check the reference transmitted by the base station and determine the RSRP based on the downlink path loss, and compare this value with the threshold set by the base station. If the RSRP is greater, the terminal can perform a PRACH transmission on the SBFD symbol.

[0693] As an example of thresholds set by the base station, thresholds for SBFD can be added in RACH-ConfigCommon IE (Table 21) or RACH-ConfigCommonTwoStepRA (Table 22) such as rsrp-Threshold_SBFD or msgA-RSRP-Threshold-SBFD, or existing thresholds can be reused such as rsrp-Threshold, rsrp-Threshold_SSB, msgA-RSRP-Threshold, msgA-RSRP-Threshold_SSB. RACH-ConfigCommon IE is an information element used to specify cell-specific random access parameters.

[0694] [Table 21]

[0695]

[0696]

[0697] [Table 22]

[0698]

[0699]

[0700] <SBFD 혹은 non-SBFD 시스템에 PRACH 전송의 우선권을 부여하는 방법>

[0701] There are several methods for prioritizing PRACH transmission in SBFD or non-SBFD systems. These methods relate to PRACH transmission methods in SBFD-specific additional ROs (hereinafter referred to as “Additional ROs”) or non-SBFD-specific legacy ROs (hereinafter referred to as “Legacy ROs”) during initial transmission / retransmission.

[0702] The priority mentioned in the scenarios below refers to granting priority to a specific RO type based on a given situation, allowing PRACH transmission. The UE can preferentially select an RO of the given RO type and transmit the preamble belonging to that RO.

[0703] For example, if an additional RO is given priority, the additional RO may be selected and transmitted with priority over the legacy RO. Conversely, if a legacy RO is given priority, the legacy RO may be selected and transmitted with priority over the additional RO.

[0704] The above-mentioned situation may mean that the selection of the RO type is required during the initial transmission, the retransmission period, or when starting a new transmission after all retransmissions have failed. The priority may be applied to at least one type of RO that constitutes an RO set, and if there are multiple RO sets, the priority may be applied to the RO set that is composed of at least one RO type.

[0705] For example, in case of RACH configuration option 1, one RO set can be configured with legacy ROs and additional ROs (ROs in DL SBFD symbols) through legacy RACH configuration, and priority can be given to the additional RO. For example, in case of RACH configuration option 2, when two RO sets exist based on legacy RACH configuration and additional RACH configuration, priority can be given to the RO set configured by the additional RACH configuration.

[0706] Meanwhile, when selecting an RO based on a specific criterion (e.g., RSRP), if the SSB satisfying the criteria includes all types of ROs, a specific RO (e.g., an additional RO) can be given priority. Alternatively, a specific RO (e.g., an additional RO) can be given priority, and only the first-selected RO type can be selected based on a specific criterion (e.g., RSRP).

[0707] <Scenario 1. How to apply the same priority for PRACH transmission to additional ROs and legacy ROs during the first transmission>

[0708] This scenario applies to cases where there is no priority between the additional RO and the legacy RO, when the UE is in the initial transmission and retransmission operation, and when the retransmission fails and the PRACH is transmitted again. If the RO is selected based on a specific criterion (e.g., RSRP), measurements (e.g., RSRP) are required to determine whether the specific criterion is satisfied depending on the selected RO type. Each type can have its own SSB, and it is unclear whether an SSB using the same TCI state will be transmitted in both types. Therefore, rsrp-ThresholdSSB can use different values ​​for each type. For example, rsrp-Threshold-SBFD or msgA-rsrp-Threshold-SBFD can be used.

[0709] <Scenario 1-1. Terminal Retransmission Behavior>

[0710] Alt 1-1. A method of retransmitting by selecting the RO type that satisfies the given conditions without priority after a previous transmission failure.

[0711] Although this method is described for retransmissions, it can also be applied to initial transmissions. Regardless of whether the initial transmission used a legacy RO or an additional RO, the terminal can find an SSB that satisfies its conditions and transmit the PRACH on the RO mapped to that SSB.

[0712] This means that ROs of the same SSB have no priority, and if an RO is selected based on certain criteria (such as RSRP), all types of RO combinations are possible for retransmission. This method has the advantage of being simple for the terminal to perform, as it does not require any specific actions from the terminal, and can quickly find an SSB that satisfies the terminal's conditions. When falling back to a legacy RO, which is a different RO type, this method can introduce a power offset value, such as POWER_OFFSET_LegacyRO.

[0713] Alt 1-2: How to keep the same RO type during retransmission.

[0714] This method determines whether to use additional RO or legacy RO at the time of retransmission based on whether the terminal used additional RO or legacy RO in the previous transmission. If the terminal performed the previous PRACH transmission using additional RO, the additional RO is also used in the next retransmission, and if the terminal transmitted the previous PRACH transmission using legacy RO, the legacy RO is also used in the next retransmission.

[0715] Since this method allows the terminal to use only one type of RO, the terminal can expect to receive only one RO configuration, and this configuration will remain unchanged. Furthermore, it has the advantage of not requiring changes to the components of the terminal's PRACH configuration when transmitting across different types. For example, in the case of RACH configuration option 2, once a single RO set is determined, PRACH retransmissions can be transmitted via the determined single RO type.

[0716] Alt 1-3: If the previous transmission was a legacy RO transmission and failed, the retransmission is limited to a legacy RO retransmission.

[0717] This method determines whether to use an additional RO or a legacy RO at the time of retransmission based on whether the terminal used an additional RO or a legacy RO in the previous transmission. This method assumes that the terminal transmitted via the legacy RO at the time of the previous PRACH transmission. At this time, it can be assumed that the environment of the terminal may not allow the base station to smoothly receive the PRACH even in a non-SBFD system. Therefore, since the reception environment of the base station may be more severe due to interference such as CLI, if the previous PRACH transmission was performed via a legacy RO, the PRACH can be transmitted via the legacy RO even in the next retransmission. However, if the additional RO is performed in a non-SBFD symbol, the terminal may also use the additional RO in the next retransmission to be consistent with the intention of the method.

[0718] Alt 1-4: How retransmissions are limited to legacy RO retransmissions if the previous transmission fails after an additional RO transmission.

[0719] This method determines whether to use an additional RO or a legacy RO at the time of retransmission based on whether the terminal used an additional RO or a legacy RO in the previous transmission. This method assumes that the terminal transmitted via an additional RO at the time of the previous PRACH transmission. At this time, it can be assumed that the environment of the terminal may not allow the base station to receive the PRACH smoothly in the SBFD system. Therefore, since the reception environment of the base station may be more severe in the SBFD symbol due to interference such as CLI, if the previous PRACH transmission was performed via an additional RO, the PRACH can be transmitted via the legacy RO in the case of the next retransmission. However, this method may install a counter that switches from an additional RO to a legacy RO. For example, as mentioned above, a trigger such as a specific number of retransmissions (PREAMBLE_TRANSMISSION_COUNTER, PREAMBLE_POWER_RAMPING_COUNTER, etc.) can be installed to enable transmission to a legacy RO when a certain condition is met. Alternatively, a single additional RO can cause the next retransmission to be switched to a legacy RO. This method implies a fallback to another RO type, the legacy RO, and a power offset value such as POWER_OFFSET_LegacyRO can be introduced in relation to this.

[0720] Alt 1-5: How to limit retransmission to legacy RO retransmission if previous transmission fails.

[0721] This method determines whether to use an additional RO or a legacy RO at the time of retransmission, regardless of whether the UE used an additional RO or a legacy RO in the previous transmission. This method assumes that the UE's environment may not allow smooth PRACH reception by the base station in either an SBFD or non-SBFD system, regardless of the RO type transmitted by the UE at the time of the previous PRACH transmission. Therefore, since the base station's reception environment may be considered to be more severe due to interference such as CLI, the PRACH can be transmitted through the legacy RO for the next retransmission regardless of the type of the previous PRACH transmission. However, if the additional RO is performed in a non-SBFD symbol, the UE may also use the additional RO for the next retransmission to be consistent with the intention of the method. This method implies a fallback to a different RO type, the legacy RO, and in this regard, a power offset value such as POWER_OFFSET_LegacyRO may be introduced.

[0722] Alt 1-6: Limiting legacy RO retransmissions after a certain number of failed transmissions.

[0723] This method determines whether to use an additional RO or a legacy RO at the time of retransmission, regardless of whether the terminal used an additional RO or a legacy RO in the previous transmission. This method assumes that the base station's PRACH reception may not be smooth even in an SBFD or non-SBFD system, regardless of the RO type transmitted by the terminal at the time of the previous PRACH transmission. Therefore, since the base station's reception environment is considered to be more severe due to interference such as CLI, the PRACH can be transmitted through the legacy RO for the next retransmission, regardless of the type of the previous PRACH transmission. However, this method may install a counter that switches from an additional RO to a legacy RO. For example, as mentioned above, a trigger such as a specific number of retransmissions (PREAMBLE_TRANSMISSION_COUNTER, PREAMBLE_POWER_RAMPING_COUNTER, etc.) can be installed to enable transmission to a legacy RO when a certain condition is met. Alternatively, a single additional RO can cause the next retransmission to be switched to a legacy RO. If this method falls back to a different RO type, such as a legacy RO, a power offset value such as POWER_OFFSET_LegacyRO can be introduced.

[0724] <Scenario 1-2. Next PRACH transmission behavior when all retransmissions fail>

[0725] This scenario describes the following PRACH transmission behavior when the UE has completed retransmission but the initial operation has not yet been completed. If an RO is selected based on a specific criterion (e.g., RSRP), measurements (e.g., RSRP) are required to determine whether the specific criterion is satisfied depending on the RO type selected. Each type can have its own SSB, and it is unclear whether an SSB using the same TCI state will be transmitted to both types. Therefore, rsrp-ThresholdSSB can use different values ​​depending on the type, and for example, rsrp-Threshold-SBFD or msgA-rsrp-Threshold-SBFD can be used.

[0726] Alt 1-1: A method of selecting and transmitting the RO type that satisfies the given conditions without priority after the previous transmission failure.

[0727] Although this method describes the case of retransmission, it can also be applied to initial transmission. The UE can find an SSB that satisfies the UE's conditions and transmit the PRACH on the RO mapped to that SSB, regardless of whether the initial transmission used a legacy RO or an additional RO. This means that ROs of the same SSB have no priority, and if an RO is selected based on certain criteria (such as RSRP), all types of RO combinations are possible for retransmission. This method has the advantage of being simple for the UE because it does not require specific UE behavior, and can quickly find an SSB that satisfies the UE's conditions. When falling back to a different RO type, such as a legacy RO, this method can introduce a power offset value, such as POWER_OFFSET_LegacyRO.

[0728] Alt 1-2: A method to limit the next first transfer to a legacy RO transfer if the previous transfer fails.

[0729] This method determines whether to use the additional RO or the legacy RO at the time of retransmission based on whether the terminal used the additional RO or the legacy RO in the previous transmission. If the terminal transmitted via the additional RO in the previous PRACH transmission, the additional RO is also used in the next retransmission, and if the terminal transmitted via the legacy RO in the previous PRACH transmission, the legacy RO is also used in the next retransmission. Since this method uses only one type of RO in the terminal, the terminal only needs to receive one RO configuration and can expect that the configuration will not change. In addition, there is an advantage in that components that need to be changed when transmitting in different types do not need to be changed in terms of the terminal's PRACH configuration.

[0730] Alt 1-3: If the previous transmission fails after SBFD RO transmission, the next first transmission is limited to a legacy RO transmission.

[0731] This method determines whether to use an additional RO or a legacy RO at the time of retransmission based on whether the terminal used an additional RO or a legacy RO in the previous transmission. This method assumes that the terminal transmitted via a legacy RO during the previous PRACH transmission. At this time, it can be assumed that the environment of the terminal may not allow smooth PRACH reception by the base station even in a non-SBFD system. Therefore, since the reception environment of the base station may be more severe due to interference such as CLI, if the previous PRACH transmission was performed via a legacy RO, the PRACH can be transmitted via the legacy RO even for the next retransmission. However, if the additional RO is performed in a non-SBFD symbol, the additional RO may also be used for the next retransmission to be consistent with the intention of the method. When this method falls back to a different RO type, such as a legacy RO, a power offset value such as POWER_OFFSET_LegacyRO may be introduced.

[0732] Alt 1-4: How to limit the next first transfer to a legacy RO transfer if the previous transfer fails.

[0733] This method determines whether to use an additional RO or a legacy RO at the time of retransmission based on whether the terminal used an additional RO or a legacy RO in the previous transmission. This method assumes that the terminal transmitted via an additional RO at the time of the previous PRACH transmission. At this time, it can be assumed that the environment of the terminal may not allow the base station to smoothly receive the PRACH in the SBFD system. Therefore, since the reception environment of the base station in the SBFD symbol may be more severe due to interference such as CLI, if the previous PRACH transmission was performed via an additional RO, the PRACH can be transmitted via the legacy RO in the case of the next retransmission. However, this method may install a counter that switches from an additional RO to a legacy RO. For example, as mentioned above, a trigger such as a specific number of retransmissions (PREAMBLE_TRANSMISSION_COUNTER, PREAMBLE_POWER_RAMPING_COUNTER, etc.) can be installed to enable transmission to a legacy RO when a certain condition is met. Alternatively, a single additional RO can cause the next retransmission to be switched to a legacy RO. When this method falls back to a legacy RO, which is another RO type, a power offset value such as POWER_OFFSET_LegacyRO can be introduced.

[0734] <Scenario 2. How to apply priority for PRACH transmission to the additional RO among the additional RO and legacy RO during the first transmission>

[0735] This scenario may be relevant when the UE is performing initial transmission, retransmission, or retransmission and PRACH transmission again when the priority lies with the additional RO among the legacy ROs. If the RO is selected based on certain criteria (e.g., RSRP), measurements (e.g., RSRP) may be required to determine whether the specific criteria are met depending on the RO type selected. Each type may have its own SSB, and it is unclear whether an SSB using the same TCI state will be transmitted to both types. Therefore, rsrp-ThresholdSSB may use different values ​​depending on the type, for example, rsrp-Threshold-SBFD or msgA-rsrp-Threshold-SBFD may be used. In this case, certain criteria may be applied to the additional RO that has been given priority.

[0736] <Scenario 2-1. Terminal Retransmission Behavior>

[0737] Alt 2-1. A method of retransmitting by selecting an RO type that satisfies the given conditions without priority after a previous transmission failure.

[0738] Although this method describes the case of retransmission, it can also be applied to initial transmission. The terminal can find an SSB that satisfies the terminal's conditions and transmit the PRACH in the RO mapped to the SSB, regardless of whether the initial transmission used a legacy RO or an additional RO. This means that ROs of the same SSB have no priority, and if an RO is selected based on certain criteria (such as RSRP), all types of RO combinations are possible for retransmission. This method has the advantage of being simple for the terminal because it does not generate conditions based on specific actions of the terminal and can quickly find an SSB that satisfies the terminal's conditions. When falling back to a different RO type, such as a legacy RO, this method can introduce a power offset value, such as POWER_OFFSET_LegacyRO.

[0739] Alt 2-2: How to keep the same additional RO type during retransmission.

[0740] This method determines whether to use an additional RO or a legacy RO at the time of retransmission based on whether the terminal used an additional RO or a legacy RO in the previous transmission. If the terminal transmitted via an additional RO in the previous PRACH transmission, the additional RO is also used in the next retransmission, and if the terminal transmitted via a legacy RO in the previous PRACH transmission, the legacy RO is also used in the next retransmission. Since this method allows the terminal to use only one type of RO, the terminal only needs to receive one RO configuration and can expect that the configuration will not change. In addition, in terms of the terminal's PRACH configuration, there is an advantage in that components that need to be changed when transmitting on different types of ROs do not need to be changed.

[0741] Alt 2-3: A method to limit retransmissions to legacy ROs if a previous transmission fails after being transmitted from an additional RO.

[0742] This method determines whether to use an additional RO or a legacy RO at the time of retransmission based on whether the terminal used an additional RO or a legacy RO in the previous transmission. This method assumes that the terminal transmitted via an additional RO at the time of the previous PRACH transmission. At this time, it can be assumed that the environment of the terminal may not allow the base station to smoothly receive the PRACH in the SBFD system. Therefore, since the reception environment of the base station in the SBFD symbol may be more severe due to interference such as CLI, if the previous PRACH transmission was performed via an additional RO, the PRACH can be transmitted via the legacy RO in the case of the next retransmission. However, this method may install a counter that switches from an additional RO to a legacy RO. For example, as mentioned above, a trigger such as a specific number of retransmissions (PREAMBLE_TRANSMISSION_COUNTER, PREAMBLE_POWER_RAMPING_COUNTER, etc.) can be installed to enable transmission to a legacy RO when a certain condition is met. Alternatively, a single additional RO can cause the next retransmission to be switched to a legacy RO. When this method falls back to a legacy RO, which is another RO type, a power offset value such as POWER_OFFSET_LegacyRO can be introduced.

[0743] <Scenario 2-2. Next PRACH transmission behavior when all retransmissions fail>

[0744] Alt 2-1. A method of retransmitting by selecting an RO type that satisfies the given conditions without priority after a previous transmission failure.

[0745] Although this method primarily describes retransmission cases, it can also be applied to initial transmissions. Regardless of whether the initial transmission used a legacy RO or an additional RO, the UE can find an SSB that satisfies its conditions and transmit a PRACH on the RO mapped to that SSB. This means that ROs of the same SSB have no priority, and if an RO is selected based on a specific criterion (such as RSRP), all types of RO combinations are possible for retransmission. This method has the advantage of being simple for the UE because it does not generate conditions based on specific UE behavior, and can quickly find an SSB that satisfies the UE's conditions. When this method falls back to a different RO type, such as a legacy RO, a power offset value such as POWER_OFFSET_LegacyRO can be introduced.

[0746] Alt 2-2: If a previous transmission fails in an additional RO, retransmission is limited to being performed in a legacy RO.

[0747] This method determines whether to use the additional RO or the legacy RO at the time of retransmission based on whether the terminal used the additional RO or the legacy RO in the previous transmission. This method assumes that the terminal transmitted through the additional RO at the time of the previous PRACH transmission. At this time, it can be assumed that the environment of the terminal may not allow the base station to receive the PRACH smoothly in the SBFD system. Therefore, since the reception environment of the base station in the SBFD symbol may be more severe due to interference such as CLI, if the previous PRACH transmission was performed through the additional RO, the PRACH can be transmitted through the legacy RO at the time of the next retransmission. However, this method may install a counter that switches from the additional RO to the legacy RO. For example, as mentioned above, a trigger such as a specific number of retransmissions (PREAMBLE_TRANSMISSION_COUNTER, PREAMBLE_POWER_RAMPING_COUNTER, etc.) can be installed to enable transmission to a legacy RO when a certain condition is met. Alternatively, a single additional RO can cause the next retransmission to be switched to a legacy RO. When this method falls back to a legacy RO, which is another RO type, a power offset value such as POWER_OFFSET_LegacyRO can be introduced.

[0748] <Scenario 3. How to apply priority for PRACH transmission to the legacy RO among additional ROs and legacy ROs during the first transmission>

[0749] This scenario may be relevant when the UE is in the initial transmission, retransmission operation, or when the retransmission fails and PRACH is transmitted again when the priority exists in the legacy RO among the additional RO and the legacy RO. If the RO is selected based on a specific criterion (e.g., RSRP), a measurement (e.g., RSRP) needs to be performed to determine whether the specific criterion is satisfied depending on the RO type selected. Each type can have its own SSB, and it is unclear whether an SSB using the same TCI state will be transmitted in both types. Therefore, rsrp-ThresholdSSB can use different values ​​depending on the type, and for example, rsrp-Threshold-SBFD or msgA-rsrp-Threshold-SBFD can be used. In this case, a specific criterion can be applied to the legacy RO that has been given priority.

[0750] <Scenario 3-1. Terminal behavior during retransmission>

[0751] Alt 3-1. A method of retransmitting by selecting an RO type that satisfies the given conditions without priority after a previous transmission failure.

[0752] Although this method is described for retransmission, it can also be applied to initial transmission. Regardless of whether the UE used a legacy RO or an additional RO for the initial transmission, it can find an SSB that satisfies its conditions and transmit a PRACH on the RO mapped to that SSB. This means that ROs of the same SSB have no priority, and if an RO is selected based on a specific criterion (such as RSRP), all types of RO combinations are possible for retransmission. This method has the advantage of being simple for the UE because it does not generate conditions based on specific UE behavior, and can quickly find an SSB that satisfies the UE's conditions. When this method falls back to a different RO type, such as a legacy RO, a power offset value such as POWER_OFFSET_LegacyRO can be introduced.

[0753] Alt 3-2: How to keep the same RO type during retransmission.

[0754] This method determines whether to use an additional RO or a legacy RO at the time of retransmission based on whether the terminal used an additional RO or a legacy RO in the previous transmission. If the terminal transmitted via an additional RO in the previous PRACH transmission, the additional RO is also used in the next retransmission, and if the terminal transmitted via a legacy RO in the previous PRACH transmission, the legacy RO is also used in the next retransmission. Since this method allows the terminal to use only one type of RO, the terminal only needs to receive one RO configuration and can expect that the configuration will not change. In addition, in terms of the terminal's PRACH configuration, there is an advantage in that there is no need to change any components that need to be changed when transmitting on different types of ROs.

[0755] <Scenario 3-2. Next PRACH transmission behavior when all retransmissions fail>

[0756] Alt 3-1. A method of retransmitting by selecting an RO type that satisfies the given conditions without priority after a previous transmission failure.

[0757] Although this method is described for retransmission, it can also be applied to initial transmission. Regardless of whether the initial transmission used a legacy RO or an additional RO, the UE can find an SSB that satisfies its conditions and transmit a PRACH on the RO mapped to that SSB. This means that ROs of the same SSB have no priority, and if an RO is selected based on a specific criterion (such as RSRP), all types of RO combinations are possible for retransmission. This method has the advantage of being simple for the UE because it does not generate conditions based on specific UE behavior, and can quickly find an SSB that satisfies the UE's conditions. When this method falls back to a different RO type, such as a legacy RO, a power offset value such as POWER_OFFSET_LegacyRO can be introduced.

[0758] Alt 3-2: How to limit retransmissions to be performed from the legacy RO if the previous transmission failed in the legacy RO.

[0759] This method determines whether to use an additional RO or a legacy RO at the time of retransmission based on whether the terminal used an additional RO or a legacy RO in the previous transmission. This method assumes that the terminal transmitted via the legacy RO at the time of the previous PRACH transmission. At this time, it can be assumed that the environment of the terminal may not allow the base station to smoothly receive the PRACH even in a non-SBFD system. Therefore, since the reception environment of the base station may be more severe due to interference such as CLI, if the previous PRACH transmission was performed via a legacy RO, the PRACH can be transmitted via the legacy RO even in the next retransmission. However, if the additional RO is performed in a non-SBFD symbol, the terminal may be able to perform the next retransmission even in the additional RO, consistent with the intention of the method.

[0760] <Scenario 4. Applying priority for PRACH transmission between additional RO and legacy RO through upper layer signaling>

[0761] This scenario may be relevant when the UE is in the middle of initial transmission, retransmission, or retransmission and retransmission of a PRACH when the priority is set by higher-layer signaling between additional ROs and legacy ROs. Since the type of RO on which the PRACH will be transmitted is determined by higher-layer signaling in this method, no prior action by the UE is required. However, the base station must indicate to the UE which type of RO will be used for PRACH transmission with priority. For example, this information can be included in the RACH-ConfigCommon IE (Table 23) or the RACH-ConfigDedicated IE (Table 24). RACH-ConfigDedicated is an information element used to specify dedicated random access parameters.

[0762] [Table 23]

[0763]

[0764] [Table 24]

[0765]

[0766] When using PRACH iteration, conditions can be differentiated based on whether this threshold is applied. The details are as follows.

[0767] Method 1. When applying PRACH repetition, the path loss threshold for determining whether to use SBFD RACH can be set differently depending on the number of repetition transmissions / method to be applied.

[0768] When using PRACH repetition, the minimum threshold required for reception may vary because combining can be performed upon reception of PRACHs transmitted from ROs set as an RO group.

[0769] Considering this, the base station may consider transmitting PRACH via SBFD symbols by setting a different threshold for the threshold indicated during PRACH transmission than for single transmission. For example, rsrp-Threshold_SBFD_repetition may be used instead of the aforementioned rsrp-Threshold_SBFD.

[0770] Alternatively, the terminal can vary the threshold value indicated during PRACH transmission by a value corresponding to the number of repetitions. For example, if the number of repetitions is 8, the number of repetitions can be set as an offset, and PRACH transmission via SBFD symbols can be considered based on the value obtained by dividing the threshold by 8 (the offset) or subtracting the value after considering a log scale.

[0771] The advantage of this method is that PRACH transmission via SBFD symbols can be performed in more environments because the threshold changes through repetition.

[0772] Method 2. A method of using the measured path loss value adjusted according to repetition for judgment through the path loss threshold.

[0773] When using PRACH repetition, the RSRP based on downlink path loss for comparison with the threshold may vary because the PRACHs transmitted from ROs configured as an RO group can be combined upon reception by the base station. For example, if the repetition count is 8, the RSRP based on downlink path loss can be considered for PRACH transmission in the SBFD symbol by comparing it with the threshold based on a value obtained by multiplying the RSRP based on downlink path loss by 8 or adding it while considering the log scale.

[0774] The advantage of this method is that no additional instructions are required because the RSRP is adjusted based on the downlink path loss measured and determined within the terminal.

[0775] Figure 20 illustrates an operation method of a terminal according to one embodiment of the present disclosure.

[0776] Referring to FIG. 20, the terminal receives separate power control parameters for transmission of PRACH in legacy ROs (random access channel occasions) and additional ROs from a network (e.g., a base station) (S201).

[0777] For example, the individual power control parameters may include a parameter preambleReceivedTargetPower indicating a target power level at the receiver side of the network. The individual power control parameters may include a parameter powerRampingStep indicating power ramping steps for the PRACH. The individual power control parameters may include a parameter preambleTransMax related to a maximum number of random access preamble transmissions. The individual power control parameters may be provided by a single RACH configuration. That is, the individual power control parameters described above may be provided for RACH configuration option 1.

[0778] The network can provide terminals with power control parameters for these PRACH transmissions individually for legacy ROs and additional ROs. This is described, for example, in "I. Separated PRACH Power Control" and "III. General Procedure."

[0779] The terminal determines whether it has received information related to the RO type (legacy RO or additional RO) from the network (S202), and if the terminal has received information related to the RO type from the network, the terminal determines the PRACH transmission power using the power control parameters for the RO of the RO type indicated by the information, and transmits the PRACH in the RO of the corresponding type (S203).

[0780] If the terminal does not receive the above information from the network, the terminal selects a specific RO type based on the SSB (Synchronization Signal / PBCH block) RSRP (Reference Signal Received Power) threshold, determines the PRACH transmission power using the power control parameters for the RO of that type, and transmits the PRACH in the RO of the corresponding RO type (S204).

[0781] For example, when determining power for PRACH transmission, the terminal may use power control parameters for the legacy RO for the legacy RO and use power control parameters for the additional RO for the additional RO to determine power for PRACH transmission. The PRACH transmission may be an initial transmission among initial transmission and retransmission.

[0782] In other words, the terminal determines power for transmission of a PRACH, and transmits the PRACH at the power in ROs of one type among legacy ROs and additional ROs, wherein the terminal receives individual power control parameters for transmission of the PRACH in the legacy ROs and the additional ROs from the network, and transmits the PRACH through an RO of the RO type based on the fact that the terminal has been provided with information related to the RO type from the network, and transmits the PRACH based on the fact that the terminal has not been provided with the information from the network, and selects a specific RO type based on an SSB RSRP threshold to transmit the PRACH.

[0783] For example, when a RACH procedure is initiated for an SBFD-aware UE, the network may indicate or inform the UE, through information related to the aforementioned RO type, that the additional RO has priority over the legacy RO. In the absence of such an indication from the network, the SBFD-aware UE selects the legacy RO or the SBFD RO based on SSB RSRP.

[0784] The above RO type can be a legacy RO or an additional RO.

[0785] The above terminal may be a subband full duplex-aware UE.

[0786] In some embodiments, the UE may be allowed to attempt PRACH transmission in legacy ROs (i.e., the UE switches to legacy ROs) after attempting PRACH transmission a certain number of times in subband full duplex (SBFD) ROs located in SBFD symbols. For example, in a RACH procedure, this operation (i.e., the UE switches from SBFD ROs to legacy ROs to attempt PRACH retransmission after attempting PRACH transmission a certain number of times in SBFD ROs but (if unsuccessful) fails) may be applied.

[0787] For example, in the case of PRACH transmission retries in a single RACH procedure, after a certain (configured) number of RACH attempts have been made in SBFD ROs, the UE may be allowed to switch to a legacy RO. This has been described in detail, for example, in 'I. Separated PRACH Power Control', 'III. General Procedure', etc.

[0788] According to the method according to the present disclosure, PRACH transmission purposes can be set differently according to different RO types, and a terminal can effectively transmit PRACH by selecting an RO type that matches the settings. In addition, separate power control parameters are provided for different RO types, so that appropriate power control can be performed for ROs of different RO types that are likely to have different channel characteristics or interference amounts, thereby enabling efficient PRACH transmission. In addition, the conditions for performing PRACH transmission by switching RO types in a situation where different RO types are mixed are made clear, so that ambiguity does not arise between the network and the terminal.

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

[0790] Referring to FIG. 21, the base station provides individual power control parameters for PRACH transmission in legacy ROs and additional ROs to the terminal (S211). For example, the base station may provide individual power control parameters for PRACH transmission to the terminal through at least one RACH configuration (e.g., RACH configuration option 1).

[0791] The base station provides the terminal with information related to the RO type (legacy RO or additional RO) (indicating the RO type) (S212).

[0792] The base station receives a PRACH having a specific power from the terminal in the ROs of the RO type indicated by the above information among the legacy ROs and additional ROs (S213).

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

[0794] Referring to FIG. 22, the base station provides individual power control parameters for transmission of PRACH in legacy ROs and additional ROs to the terminal (SBFD-aware terminal) (S221).

[0795] The base station provides RO type information to the terminal (S222).

[0796] The terminal determines the PRACH transmission power using the corresponding power control parameters in the ROs of the type based on the RO type information (S223), and transmits the PRACH in the corresponding RO with the determined transmission power (S224).

[0797] In FIGS. 21 and 22, an example is described in which, when the terminal receives information related to the RO type from the network, the terminal determines the PRACH transmission power using the power control parameters for the RO of the RO type indicated by the information, and transmits the PRACH in the RO of the corresponding type.

[0798] If the terminal does not receive the information (information on the RO type) from the network, the terminal selects a specific RO type based on the SSB RSRP threshold, determines the PRACH transmission power using the power control parameters for the RO of that type, and transmits the PRACH in the RO of the corresponding RO type.

[0799] IV. Power Control for PRACH Transmission Across SBFD and Non-SBFD Symbols

[0800] Hereinafter, a method for determining the transmission power of a PRACH transmitted in an RO, when multiple or one RO is configured to span SBFD symbols and non-SBFD symbols, is described. The necessity of distinguishing the transmission power between SBFD symbols and non-SBFD symbols has been previously described. Which of the methods below to use, or the maximum / minimum in Method 3 or the symbol reference in Method 4, can be set by the base station.

[0801] There are two main situations that can cause problems: when different types of symbols (SBFD symbols and non-SBFD symbols) exist within a single RACH slot, and when different types of symbols (SBFD symbols and non-SBFD symbols) are located across multiple RACH slots. Each case can be summarized as follows.

[0802] 1. When different types of symbols (SBFD symbols, non-SBFD symbols) exist in one RACH slot.

[0803] In cases where a long preamble is transmitted across different types of symbols, the long preamble may span different types of symbols because one RACH slot is transmitted across multiple slots.

[0804] When a short preamble is transmitted across different types of symbols, the short preamble ends up transmitting PRACH within a slot or subframe in the current standard, as shown in the PRACH configuration index table. Therefore, unless there is a separate modification to the table above, multiple symbol types can exist in a single PRACH format if both SBFD and non-SBFD symbol types are configured within a slot or subframe.

[0805] 2. When multiple RACH slots are located on different types of symbols (SBFD symbols, non-SBFD symbols).

[0806] When a RO group is transmitted across different types of symbols due to PRACH repetition, multiple ROs can be configured as a single RO group, and in this case, ROs configured for different symbol types can be configured as a single RO group.

[0807] When a retransmission following a PRACH transmission failure occurs on different symbol types, this is the case when multiple RACH transmissions are performed using ROs in different RACH slots. While a single transmission may be assigned to an SBFD or non-SBFD symbol, a retransmission may be assigned to a different symbol type. Since the power of the initial and retransmission transmissions may ramp in the case of retransmissions, using the same or different power for these methods means excluding the ramping factor.

[0808] When ROs operating in different systems (SBFD / non-SBFD) are defined on symbols different from those in the system due to different system operations. For example, this may be the case when an RO additionally set for an SBFD system is valid not only on SBFD symbols but also on non-SBFD symbols.

[0809] Method 1. A method of transmitting PRACH on SBFD symbols with power A, and PRACH on non-SBFD symbols with power B.

[0810] The transmission power applied in this method can be applied when multiple ROs are set for SBFD symbols and non-SBFD symbols, respectively.

[0811] Option 1. If the terminal receives one setting for SBFD symbols and non-SBFD symbols.

[0812] Transmission power is set differently for SBFD and non-SBFD symbols through reinterpretation within the terminal. In the RO set for each symbol type, the PRACH transmission power is determined through the received parameters and a preset calculation formula for each symbol type in the terminal, and transmission is performed independently according to the symbol type.

[0813] Option 2. If the terminal has received separate settings for SBFD and non-SBFD symbols.

[0814] Since the base station independently indicates the corresponding parameters for each symbol type, the terminal may need to be able to receive both parameters. For the terminal receiving the instructions, the RO configured for each symbol type determines the PRACH transmission power based on the configured parameters and the terminal's calculations, and transmits independently according to the symbol type.

[0815] Additionally, for retransmission, the following methods can be considered:

[0816] When applying different power controls to each RO included in multiple RACH retransmissions (both Option 1 and Option 2), maintenance / restoration of power ramping counters may be considered for each type of RO included in multiple RACH retransmissions.

[0817] When there are ROs belonging to two different types of symbols, if RACH transmission is not performed in ROs belonging to one type of symbol (i.e., when ROs are transmitted in multiple types of symbols), the power ramping counter is maintained. That is, power ramping by retransmission is performed. If RACH transmission is not performed in all ROs belonging to different types of symbols (i.e., when ROs are transmitted in one type of symbol), the power ramping counter is restored (-1). That is, if the power ramping counter due to retransmission is the same as before and the symbol type changes, no additional power ramping is performed. However, power control according to the type of symbol, excluding ramping by retransmission, is considered independently.

[0818] The advantage of this method is that since it follows the transmission power set for each symbol type, if the base station has instructed the transmission power to be optimized for the situation by considering various factors, the instruction can be followed well and transmission optimized for the situation can be performed.

[0819] Method 2. A method of continuing to apply the power applied to transmission in the symbol type of the first symbol of PRACH transmission.

[0820] The transmission power applied in this method can be applied when multiple ROs are set to SBFD symbols and non-SBFD symbols respectively, and when one RO is set across SBFD symbols and non-SBFD symbols.

[0821] Option 1. If the terminal receives a single configuration for SBFD and non-SBFD symbols, the transmission power can be set differently for SBFD and non-SBFD symbols through reinterpretation within the terminal. The terminal can know the symbol type of the first symbol, and accordingly, rather than using the configured parameters and the preset calculation formula for each symbol type in the terminal, the terminal can use the preset calculation formula for the symbol type of the first symbol to determine the PRACH transmission power for other symbol types. The terminal applies the determined transmission power to both single and multiple PRACH transmissions.

[0822] Option 2. When the terminal receives separate configurations for SBFD and non-SBFD symbols. Since the base station independently indicates the corresponding parameters for each symbol type, the terminal may need to be able to receive both parameters. For the terminal that has received the configuration, the PRACH transmission power can be determined based on the parameters set in the RO configured for the symbol type of the first symbol and calculations made by the terminal. The terminal applies the determined transmission power to both single and multiple PRACH transmissions.

[0823] The advantage of this method is that the transmission power is unified according to the symbol type of the first symbol, and there is no power switching according to the symbol type, so the instruction complexity and implementation complexity of the terminal and base station are low.

[0824] Additionally, for retransmission, the following methods can be considered:

[0825] When applying different power controls to each RO included in multiple RACH retransmissions (both Option 1 and Option 2), maintenance / restoration of power ramping counters may be considered for each type of RO included in multiple RACH retransmissions.

[0826] When there are ROs belonging to two different types of symbols, if RACH transmission is not performed in ROs belonging to one type of symbol (i.e., when ROs are transmitted in multiple types of symbols), the power ramping counter is maintained. That is, power ramping by retransmission is performed. If RACH transmission is not performed in all ROs belonging to different types of symbols (i.e., when ROs are transmitted in one type of symbol), the power ramping counter is restored (-1). That is, if the power ramping counter due to retransmission is the same as before and the symbol type changes, no additional power ramping is performed. However, power control according to the type of symbol, excluding ramping due to retransmission, considers maintaining the power control parameters applied to the first RO.

[0827] Method 3. A method of continuously applying one value based on the minimum or maximum value of power A and power B.

[0828] The transmission power applied in this method can be applied when multiple ROs are set to SBFD symbols and non-SBFD symbols respectively, and when one RO is set across SBFD symbols and non-SBFD symbols.

[0829] Option 1. If the terminal receives a single configuration for SBFD and non-SBFD symbols, the transmission power can be set differently for SBFD and non-SBFD symbols through reinterpretation within the terminal. The terminal can determine the symbol type that uses higher / lower transmission power through the configured value and reinterpretation, and accordingly, the terminal can determine the PRACH transmission power by using the preset calculation formula for the symbol type that calculates the value based on the minimum or maximum value, rather than using the configured parameter and the preset calculation formula for each symbol type in the terminal. The terminal applies the determined transmission power to both single and multiple PRACH transmissions.

[0830] Option 2. When the terminal receives separate configurations for SBFD and non-SBFD symbols. Since the base station independently indicates the corresponding parameters for each symbol type, the terminal must be able to receive both parameters. For a terminal that has received the configuration, the terminal can interpret each parameter to determine the symbol type that uses higher / lower transmission power, and can then determine the PRACH transmission power based on the configured parameters and terminal calculations. The terminal applies the determined transmission power to both single and multiple PRACH transmissions.

[0831] The advantage of this method is that it unifies the transmission power according to the type of symbol that uses higher / lower power, and since there is no power switching according to the symbol type, the instruction complexity and implementation complexity of the terminal and base station are low, and it can be set for the minimum transmission requirement considering the surrounding environment of PRACH transmission or for high power for the link quality of the terminal.

[0832] Method 4. A method of continuously applying the PRACH power on the SBFD symbol (or the PRACH power on the non-SBFD symbol) as is.

[0833] The transmission power applied in this method can be applied when multiple ROs are set to SBFD symbols and non-SBFD symbols respectively, and when one RO is set across SBFD symbols and non-SBFD symbols.

[0834] Option 1. When a terminal receives a single configuration for an SBFD symbol and a non-SBFD symbol, the terminal can set the transmission power for the SBFD symbol and the non-SBFD symbol differently through reinterpretation within the terminal. The terminal can know the transmission power of each symbol type through the configured value and reinterpretation, and accordingly, without using the configured parameters and the preset calculation formula for each symbol type in the terminal, the terminal can determine the PRACH transmission power by using the preset calculation formula for the SBFD (or non-SBFD) symbol type, which is a pre-arranged symbol type, in other symbol types. The terminal applies the determined transmission power to both single and multiple PRACH transmissions.

[0835] Option 2. When the terminal receives separate configurations for SBFD and non-SBFD symbols, the base station independently indicates the corresponding parameters for each symbol type. The terminal requires the ability to interpret at least one parameter of each symbol type. For the terminal that has received the instruction, the terminal can determine the transmission power through parameter calculation for each symbol type, and accordingly, the terminal can determine the PRACH transmission power through the parameters of the SBFD (or non-SBFD) symbol type, which is a pre-arranged symbol type, and the calculation at the terminal. The terminal applies the determined transmission power to both single and multiple PRACH transmissions.

[0836] The advantage of this method is that since power is uniformly used in a preset symbol type without comparison between symbol types, the instruction complexity and implementation complexity of the terminal and base station are low, and the minimum transmission requirements considering the surrounding environment of PRACH transmission or high power for the link quality of the terminal can be set respectively.

[0837] Method 5. Using new power control parameters when RO spans different types of symbols.

[0838] The transmission power applied in this method can be applied when multiple ROs are set for SBFD symbols and non-SBFD symbols, respectively.

[0839] Option 1. When the terminal receives a configuration for both SBFD and non-SBFD symbols, the base station can specify whether or not to perform a new reinterpretation through a new RRC parameter. When reinterpretation is indicated by the base station, the terminal sets the transmission power differently for SBFD and non-SBFD symbols through reinterpretation. In the RO set for each symbol type, the PRACH transmission power is determined through the configured parameters and a preset calculation formula for each symbol type in the terminal, and transmission is performed independently according to the symbol type. In this case, the result of reinterpretation may differ from the result of power control reinterpretation of non-SBFD symbols in a non-SBFD system.

[0840] Option 2. When the terminal receives separate configurations for SBFD and non-SBFD symbols. Since the base station independently indicates the corresponding parameters for each symbol type through new RRC parameters, the terminal may need to be able to receive both parameters. In the case of the terminal that has received the configuration, the RO configured for each symbol type determines the PRACH transmission power through the configured parameters and calculations by the terminal, and transmits independently according to the symbol type. In this case, the power control for the instructed non-SBFD symbol may differ from the power control result for the non-SBFD symbol of the non-SBFD system.

[0841] Figure 23 illustrates a wireless device applicable to the present specification.

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

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

[0844] The processor (102) is characterized in that it determines power for transmission of a PRACH, transmits the PRACH at the power in ROs of one type among legacy ROs and additional ROs, receives individual power control parameters for transmission of the PRACH in the legacy ROs and the additional ROs from the network, and transmits the PRACH through an RO of the RO type based on information related to the RO type provided from the network, and selects a specific RO type based on an SSB RSRP threshold based on information not provided from the network and transmits the PRACH. The specific operation has been described above with reference to FIGS. 20 to 22.

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

[0846] The processor (202) is characterized in that it provides individual power control parameters for transmission of PRACH in legacy ROs and additional ROs to the terminal, and receives PRACH having specific power from the terminal in one type of RO among the legacy ROs and the additional ROs, and provides information indicating one type to the terminal. The specific operation thereof has been described above with reference to FIGS. 20 to 22.

[0847] Figure 24 illustrates another example of a wireless device.

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

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

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

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

[0852] For example, at least one computer readable medium (CRM) including instructions based on being executed by at least one processor may be characterized by performing the operations of determining power for transmission of a PRACH, transmitting the PRACH at the power in ROs of any one type among legacy ROs and additional ROs, wherein individual power control parameters for transmission of the PRACH in the legacy ROs and the additional ROs are received from a network, and, based on information related to the RO type being provided from the network, transmitting the PRACH through an RO of the RO type, and, based on not receiving the information from the network, selecting a specific RO type based on an SSB RSRP threshold and transmitting the PRACH. The specific operations have been described with reference to FIGS. 20 to 22.

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

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

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

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

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

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

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

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

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

[0862] 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 has been 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.

[0863] Fig. 26 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. 23.

[0864] Referring to FIG. 26, a transmission device (e.g., a processor, a processor and a memory, or a processor and a transceiver) within a terminal or base station may include a scrambler (401), a modulator (402), a layer mapper (403), a precoder (404), a resource block mapper (405), and a signal generator (406).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0878] 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. 27 may be the transceiver (106, 206) of FIG. 26.

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

[0880] Fig. 27 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. 27. 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.

[0881] Fig. 28 illustrates a communication system (1) applicable to this specification.

[0882] Referring to FIG. 28, 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.

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

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

[0885] 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, The terminal (user equipment: UE) determines the power for transmission of the physical random access channel (PRACH), and The terminal transmits the PRACH with the power in one type of ROs among legacy ROs (random access channel occasions) and additional ROs, The terminal receives individual power control parameters for transmission of the PRACH in the legacy ROs and the additional ROs from the network, The terminal transmits the PRACH through the RO of the RO type based on the information provided by the network regarding the RO type, and A method characterized in that the terminal selects a specific RO type based on an SSB (Synchronization Signal / PBCH block) RSRP (Reference Signal Received Power) threshold and transmits the PRACH based on the fact that the terminal has not received the information from the network.

2. In paragraph 1, A method characterized in that the above RO type is a legacy RO or an additional RO.

3. A method according to claim 1, wherein the terminal is a subband full duplex-aware UE.

4. A method according to claim 1, wherein the individual power control parameters include a parameter indicating a target power level on the receiver side of the network.

5. A method according to claim 1, wherein the individual power control parameters include parameters indicating power ramping steps for the PRACH.

6. A method according to claim 1, wherein the individual power control parameters include a parameter related to the maximum number of random access preamble transmissions.

7. A method according to claim 1, wherein the individual power control parameters are provided by a single RACH configuration.

8. In paragraph 1, A method characterized in that the terminal allows PRACH transmission attempts in legacy ROs after a specific number of PRACH transmission attempts in SBFD ROs located in subband full duplex (SBFD) symbols.

9. In paragraph 1, A method characterized in that the transmission of the above PRACH is the initial transmission among the initial transmission and the retransmission.

10. 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, Determine the power for transmission of PRACH (physical random access channel), and Including transmitting the PRACH with the power in one type of ROs among legacy ROs (random access channel occasions) and additional ROs, The terminal receives individual power control parameters for transmission of the PRACH in the legacy ROs and the additional ROs from the network, The terminal transmits the PRACH through the RO of the RO type based on the information provided by the network regarding the RO type, and A terminal characterized in that, based on the fact that the terminal has not received the information from the network, the terminal selects a specific RO type based on an SSB (Synchronization Signal / PBCH block) RSRP (Reference Signal Received Power) threshold and transmits the PRACH.

11. In paragraph 10, A terminal characterized in that the above RO type is a legacy RO or an additional RO.

12. A terminal according to claim 10, characterized in that the terminal is a subband full duplex-aware UE.

13. A terminal according to claim 10, wherein the individual power control parameters include a parameter indicating a target power level on the receiver side of the network.

14. A terminal according to claim 10, wherein the individual power control parameters include parameters indicating power ramping steps for the PRACH.

15. A terminal according to claim 10, wherein the individual power control parameters include a parameter related to the maximum number of random access preamble transmissions.

16. A terminal according to claim 10, wherein the individual power control parameters are provided by a single RACH configuration.

17. In paragraph 10, The terminal is characterized in that a PRACH transmission attempt in legacy ROs is allowed after a specific number of PRACH transmission attempts in SBFD ROs located in subband full duplex (SBFD) symbols.

18. In paragraph 10, A terminal characterized in that the transmission of the above PRACH is the initial transmission among the initial transmission and the retransmission.

19. 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, Determine the power for transmission of PRACH (physical random access channel), and Including transmitting the PRACH with the power in one type of ROs among legacy ROs (random access channel occasions) and additional ROs, The device receives individual power control parameters for transmission of the PRACH in the legacy ROs and the additional ROs from the network, The device transmits the PRACH through the RO of the RO type based on the information provided from the network regarding the RO type, and A device characterized in that the device selects a specific RO type based on an SSB (Synchronization Signal / PBCH block) RSRP (Reference Signal Received Power) threshold and transmits the PRACH based on the fact that the device has not received the information from the network.

20. At least one computer readable medium (CRM) containing instructions based on being executed by at least one processor, An operation for determining power for transmission of a PRACH (physical random access channel), and An operation of transmitting the PRACH with the power is performed in one type of ROs among legacy ROs (random access channel occasions) and additional ROs, wherein said at least one processor receives individual power control parameters for transmission of said PRACH in said legacy ROs and said additional ROs from the network, wherein said at least one processor transmits said PRACH through an RO of said RO type based on information related to the RO type provided from said network, and A CRM characterized in that, based on the at least one processor not receiving the information from the network, the at least one processor selects a specific RO type based on a SSB (Synchronization Signal / PBCH block) RSRP (Reference Signal Received Power) threshold and transmits the PRACH.

21. In the method, The base station provides individual power control parameters to the terminal for transmission of the physical random access channel (PRACH) in legacy ROs (random access channel occasions) and additional ROs, and The base station receives a PRACH having a specific power from the terminal in any one type of ROs among the legacy ROs and the additional ROs, A method characterized in that the base station provides information indicating one of the above types to the terminal.

22. 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, Provides individual power control parameters to the terminal for transmission of physical random access channel (PRACH) in legacy ROs (random access channel occasions) and additional ROs, and Receiving a PRACH having a specific power from the terminal in one type of ROs among the legacy ROs and the additional ROs, A base station characterized in that the base station provides information indicating one of the above types to the terminal.

Images