Method and device for performing random access process in wireless communication system having different types of random access occasions

Abstract

The present disclosure relates to a random access process in which a terminal: receives i) a random access channel (RACH) occasion (RO) type RSRP threshold and ii) message 1 (Msg1) repetition number RSRP thresholds; chooses a specific RO type on the basis of the RO type RSRP threshold; and determines the number of Msg1 repetitions on the basis of an Msg1 repetition number RSRP threshold related to the specific RO type.

Description

Method and apparatus for performing a random access process in a wireless communication system where different types of random access opportunities exist

[0001] The present disclosure relates to a wireless communication system and to a method and apparatus in which a terminal performs a random access process in a situation where different types of random access opportunities exist.

[0002] Wireless access systems are being widely deployed to provide various types of communication services, such as voice and data. Generally, a wireless access system is a multiple access system capable of supporting communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.). Examples of multiple access systems include 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) systems.

[0003] As more communication devices require larger communication capacities, the need for enhanced mobile broadband communication compared to existing radio access technology (RAT) is emerging. Furthermore, Massive Machine Type Communications (MTC), which connects multiple devices and objects to provide various services anytime and anywhere, is also one of the major issues to be considered in next-generation communication. In addition, communication system designs that take into account services and terminals sensitive to reliability and latency are being discussed. Thus, the introduction of next-generation radio access technologies that consider enhanced mobile broadband communication, massive MTC, and Ultra-Reliable and Low Latency Communication (URLC) is being discussed, and for convenience, this technology is referred to as new RAT or NR in this disclosure.

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

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

[0006] Conventional standard specifications assume that, in relation to the random access process, the RO is configured only on non-SBFD resources. On the other hand, in future wireless communication systems, the RO may be configured on SBFD resources as well. In other words, in future wireless communication systems, different types of ROs may exist.

[0007] Using the conventional random access process as is in future wireless communication systems where SBFD resources are introduced is inefficient and may lead to ambiguity. For example, in the prior art, the RACH opportunity for transmitting Message 1 (random access channel occasion: which may also be referred to as physical random access channel occasion, random access occasion, etc., and which may be abbreviated as RO) was set only in HD resources, but in NR or subsequent wireless communication systems, RO may be set not only in HD resources but also in SBFD resources.

[0008] In this case, it is necessary to define how the SBFD-aware UE performs the random access process, more specifically, how to determine the repetition number of the transmission of the PRACH (physical random access channel) preamble (which may also be referred to as message 1).

[0009] The technical problem that the present disclosure aims to solve relates to a wireless communication system, and provides a method and apparatus for determining the number of repetitions of a PRACH preamble transmission in relation to a random access process by a terminal in a wireless communication system in which different types of random access opportunities exist.

[0010] In a wireless communication system, a terminal receives i) a RACH opportunity (random access channel occasion: RO) type RSRP (Reference Signal Received Power) threshold and ii) a message 1 (Msg1) repetition count RSRP threshold, selects a specific RO type based on the RO type RSRP threshold, and determines the Msg1 repetition count based on the Msg1 repetition count RSRP threshold associated with the specific RO type.

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

[0012] According to the present disclosure, a random access process can be efficiently performed even in a wireless communication system in which SBFD resources and non-SBFD resources (e.g., resources of the existing HD method) are mixed.

[0013] According to the present disclosure, a method for determining the number of message 1 repetitions that can be applied to a current random access procedure in a wireless communication system where SBFD resources can be used is clarified so that no ambiguity occurs between the network and the terminal.

[0014] In addition, according to the present disclosure, the terminal first selects an RO type, and once the RO type is determined, determines the number of repetitions of Message 1 by applying a threshold value set or indicated for the RO type. When a new RO type is introduced to an existing wireless communication system, system flexibility is increased because an optimized threshold value for determining the number of repetitions of Message 1 for the new RO type can be applied while maintaining legacy settings.

[0015] The effects obtainable from the embodiments of the present disclosure are not limited to those mentioned above, and other unmentioned effects can be clearly derived and understood by a person skilled in the art to which the technical configuration of the present disclosure applies from the description of the embodiments of the present disclosure below. That is, unintended effects resulting from implementing the configuration described in the present disclosure can also be derived by a person skilled in the art from the embodiments of the present disclosure.

[0016] The drawings attached below are intended to aid in understanding the present disclosure and may provide embodiments of the present disclosure together with the detailed description. However, the technical features of the present disclosure are not limited to specific drawings, and features disclosed in each drawing may be combined with one another to form new embodiments. Reference numerals in each drawing may denote 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 wireless 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 in an intra-carrier according to an embodiment of the present disclosure.

[0022] FIG. 6 illustrates examples of resource structures in which a time resource operating in HD (half duplex) and a time resource operating in FD (full duplex) coexist according to one embodiment of the present disclosure.

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

[0024] Figure 8 illustrates RO groups in the case where the number of repetitions is 4, the number of SSBs (synchronization signal blocks) is 2, the FDMed (frequency domain multiplexed) RO is 2, and the number of SSBs per RO is 1 / 2.

[0025] Figure 9 illustrates RO groups in the case where the number of repetitions is 4, the number of SSBs is 3, the FDMed RO 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 according to one embodiment of the present disclosure is applied.

[0028] FIG. 12 illustrates an example of a flexible slot when the RO is set by the legacy RO setting.

[0029] FIG. 13 illustrates an example of a flexible slot when the RO is set with a separated RO setting.

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

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

[0032] FIG. 16 illustrates an example in which an 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.

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

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

[0035] FIG. 19 illustrates RRC information elements for RACH operation.

[0036] Figure 20 shows a specific example of applying Case 1-1.

[0037] FIG. 21 illustrates the signaling process and operation method between a base station and a terminal.

[0038] Figure 22 is an example of a method for selecting a random access (RA) type.

[0039] FIG. 23 illustrates a terminal operation that performs RA type selection.

[0040] FIG. 24 illustrates a wireless device that can be applied to the present specification.

[0041] Figure 25 illustrates another example of a wireless device.

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

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

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

[0045] FIG. 29 illustrates a communication system (1) applicable to the present specification.

[0046] The attached drawings are intended to aid in understanding the present disclosure and may provide embodiments of the present disclosure together with the detailed description. However, the technical features of the present disclosure are not limited to specific drawings, and features disclosed in each drawing may be combined with one another to form new embodiments. Reference numerals in each drawing may denote structural elements.

[0047] The following embodiments are combinations of the components and features of the present disclosure in a predetermined form. Each component or feature may be considered optional unless otherwise explicitly stated. Each component or feature may be implemented in a form not combined with other components or features. Additionally, 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 any embodiment may be included in other embodiments, or may be replaced with corresponding components or features of other embodiments.

[0048] In the description of the drawings, procedures or steps that could obscure the gist of the present disclosure have not been described, nor have procedures or steps that are understandable to those skilled in the art been described.

[0049] Throughout the specification, when a part is described as "comprising" or "including" a component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components. Furthermore, terms such as "...part," "...unit," and "module" as used in the specification refer to a unit that performs at least one function or operation, and this may be implemented in hardware, software, or a combination of hardware and software. Additionally, "one (a or an)," "one," "the," and similar related terms may be used in the context describing the present disclosure (particularly in the context of the following claims) in both singular and plural forms, unless otherwise indicated in the specification or clearly contradicted by the context.

[0050] In this specification, the embodiments of the present disclosure are described with a focus on the data transmission and reception relationship between a base station and a mobile station. Here, the base station refers to a terminal node of a network that communicates directly with a mobile station. Specific operations described in this document as being performed by a base station may, in some cases, be performed by an upper node of the base station.

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

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

[0053] Furthermore, the transmitting end refers to a fixed and / or mobile node that provides data or voice services, and the receiving end refers to a fixed and / or mobile node that receives data or voice services. Therefore, in the case of the uplink, a mobile station can be the transmitting end and a base station can be the receiving end. Similarly, in the case of the downlink, a mobile station can be the receiving end and a base station can be the transmitting end.

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

[0055] In addition, the embodiments of the present disclosure may be applied to other wireless access systems and are not limited to the systems described above. For example, they may be applicable to systems applied after the 3GPP 5G NR system and are not limited to specific systems.

[0056] That is, obvious steps or parts not described in the embodiments of the present disclosure may be described by referring to the aforementioned documents. Additionally, all terms disclosed in this document may be explained by the aforementioned standard documents.

[0057] Hereinafter, preferred embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to describe exemplary embodiments of the present disclosure and is not intended to represent the only embodiment in which the technical configuration of the present disclosure can be implemented.

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

[0059] The following technology can be applied to various wireless access systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access).

[0060] For the sake of clarity, the following description is based on 3GPP communication systems (e.g., LTE, NR, etc.), but the technical scope of this disclosure is not limited thereto. LTE may refer to technology from 3GPP TS 36.xxx Release 8 onwards. Specifically, LTE technology from 3GPP TS 36.xxx Release 10 onwards is referred to as LTE-A, and LTE technology from 3GPP TS 36.xxx Release 13 onwards may be referred to as LTE-A pro. 3GPP NR may refer to technology from TS 38.xxx Release 15 onwards. 3GPP 6G may be an example of a next-generation wireless communication system. "xxx" indicates a specific standard document number. LTE / NR / 6G may be collectively referred to as 3GPP systems.

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

[0062] In this disclosure, “A or B” may mean “only A,” “only B,” or “both A and B.” Alternatively, “A or B” may be interpreted as “A and / or B.” For example, “A, B or C” may mean “only A,” “only B,” “only C,” or “any combination of A, B and C.”

[0063] As used herein, a slash ( / ) or a comma may mean “and / or.” For example, “A / B” may mean “A and / or B.” Accordingly, “A / B” may mean “only A,” “only B,” or “both A and B.” For example, “A, B, C” may mean “A, B or C.”

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

[0065] Additionally, in this specification, “at least one of A, B and C” may 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” may mean “at least one of A, B and C.”

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

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

[0068] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

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

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

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

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

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

[0074] Meanwhile, when the random access process is performed in two stages, the preamble transmission and PUSCH transmission of the terminal can be performed as a single operation, and the RAR transmission and PDSCH transmission of the base station can be performed as a single operation.

[0075] Afterwards, the terminal may receive PDCCH signals and / or PDSCH signals as a general uplink / downlink signal transmission procedure (S17), or transmit PUSCH signals and / or PUCCH signals (S18).

[0076] The control information transmitted by 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 via PUCCH, but it may be transmitted via PUSCH if control information and data need to be transmitted simultaneously. Additionally, the terminal may transmit UCI aperiodically via PUSCH in response to network requests or instructions.

[0077] Wireless resource structure

[0078] FIG. 2 illustrates the structure of a wireless frame of NR according to one embodiment of the present disclosure. The embodiment of FIG. 2 may be combined with various embodiments of the present disclosure.

[0079] Referring to FIG. 2, radio frames can be used for uplink and downlink transmission in NR. The radio frame has a length of 10 ms and can be defined as two 5 ms half-frames (HF). A half-frame may contain five 1 ms subframes (SF). A subframe may be divided into one or more slots, and the number of slots within a subframe may be determined by the subcarrier spacing (SCS). Each slot may contain 12 or 14 OFDM(A) symbols according to the cyclic prefix (CP).

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

[0081] When normal CP is used, the number of symbols per slot (N) according to the SCS setting (μ) slot symb ), number of slots per frame (N frame,μ slot ) and the number of slots per subframe (N subframe,μ slot ) can change.

[0082] The following Table 1 shows an example of SCS setting μ.

[0083] [Table 1]

[0084]

[0085] The following Table 2 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 the subframe (N subframe,μ slot ) exemplifies.

[0086] [Table 2]

[0087]

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

[0089] [Table 3]

[0090]

[0091] In an NR system, the OFDM(A) numerology (e.g., SCS, CP length, etc.) can be configured differently among multiple cells that are merged into a single terminal. Accordingly, the (absolute time) intervals of time resources (e.g., subframe, slot, or TTI) (collectively referred to as TU (Time Unit) for convenience) configured with the same number of symbols can be configured differently among the merged cells.

[0092] In NR, multiple numerologies or SCSs may be supported to support various 5G services. For example, if the SCS is 15 kHz, a wide area in traditional cellular bands may be supported, and if the SCS is 30 kHz / 60 kHz, dense-urban, lower latency, and wider carrier bandwidth may be supported. If the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz may be supported to overcome phase noise.

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

[0094] [Table 4]

[0095]

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

[0097] [Table 5]

[0098]

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

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

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

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

[0103] 1. DL only setting

[0104] 2. UL only setting

[0105] 3. Mixed UL-DL Settings

[0106] - DL Area + GP (Guard Period) + UL Control Area

[0107] - DL Control Area + GP + UL Area

[0108] DL Area: (i) DL Data Area, (ii) DL Control Area + DL Data Area

[0109] UL Area: (i) UL Data Area, (ii) UL Data Area + UL Control Area

[0110] PDCCH can be transmitted in the DL control area, and PDSCH can be transmitted in the DL data area. PUCCH can be transmitted in the UL control area, and PUSCH can be transmitted in the UL data area. Downlink Control Information (DCI), such as DL data scheduling information and UL data scheduling information, can be transmitted in PDCCH. UCI, such as ACK / NACK (Positive Acknowledgement / Negative Acknowledgement) information for DL ​​data, Channel State Information (CSI) information, and Scheduling Request (SR), can be transmitted in PUCCH. The Guard Period (GP) provides a time gap during the process in which a Base Station (BS) and a terminal switch from transmit mode to receive mode or from receive mode to transmit mode. Within a subframe, some symbols at the point of transition from DL to UL can be set as GP.

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

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

[0113] Transmission operation:

[0114] Common SN;

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

[0116] Individual encryption for source and target cells.

[0117] Receiving operation:

[0118] Individual decoding for source cells and target cells;

[0119] Restoration of individual headers for source and target cells;

[0120] Common PDCP reordering;

[0121] Sequential delivery and duplicate detection;

[0122] Common buffer management.

[0123] Generally, the network side and the UE have the same processes and functions for transmission and reception operations. The only difference is whether these functions exist in the same location. On the network side, since all functions except for DL ​​PDCP SN allocation and UL PDCP reordering are performed separately at the source eNB and target eNB, two PDCP entities located at the source eNB and target eNB are assumed.

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

[0125] UE RF / Baseband Requirements

[0126] To minimize interruptions, the UE must continue data transmission and reception with the source cell when performing random access procedures to the target cell, regardless of whether it is SAPS or DAPS. This is possible only when the UE supports simultaneous transmission and reception with two cells. This works in most cases for UEs with Dual Rx / Dual Tx chains, and more restrictions may be required for UEs with Dual Rx / Single Tx RF chains or Single Rx / Single Tx RF chains.

[0127] Additionally, functional partitioning of the UE is necessary for the effective use of baseband and RF resources. In the case of SAPS, coordinating UE baseband and RF resources is not simple, leading to additional interruptions and UE complexity.

[0128] For UEs with a Dual Rx / Single Tx RF chain, simultaneous UL data transmission to two cells can be supported if certain requirements are met, such as when the bandwidth of the source cell is greater than that of the target cell. Otherwise, a UL TDM (time division multiplexing) pattern is required, which increases additional interrupt time and UL switching complexity. However, this UE option provides various UE implementation methods in terms of hardware and power efficiency for low-cost devices (including UEs that do not support UL CA and / or UL MIMO).

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

[0130] In general, solutions should be designed for all types of UE functions rather than being limited to specific ones. Therefore, solutions should be considered that support Dual Rx / Dual Tx as the standard, and Dual Rx / Single Tx and Single Rx / Single Tx as alternatives.

[0131] Explain DAPS-HO in the standard specification (e.g., TS 38.213).

[0132] If the UE represents the function for DAPS HO, the UE can be provided with a source MCG (Master Cell Group) and a target MCG.

[0133] If the UE is configured as an MCG and SCG (Secondary Cell Group) using NR radio access in FR1 and / or FR2, the maximum power P for transmission in the MCG by p-DAPS-FR1 and / or p-DAPS-FR2 MCG Maximum power P for transmission in and SCG SCG It is configured, and an inter-CG power sharing mode by UplinkPowerSharingDAPS-HO-mode for FR1 and / or FR2 is configured. The UE determines the transmission power of the MCG and SCG for each frequency band.

[0134] If the UE indicates UplinkPowerSharingDAPS-HO = Semi-static-mode1 and is provided with UplinkPowerSharingDAPS-HO-mode = Semi-static-mode1, the UE considers the target MCG as the MCG and the source MCG as the SCG to determine the transmission power for the target MCG or the source MCG.

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

[0136] If the UE indicates UplinkPowerSharingDAPS-HO = Dynamic and is provided with UplinkPowerSharingDAPS-HO-mode = Dynamic, the UE considers the target MCG as the MCG and the source MCG as the SCG to determine the transmission power for the target MCG or the source MCG.

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

[0138] The cases in which the transmission of the target cell and the source cell is considered to overlap are as follows:

[0139] When the carrier frequencies of the target MCG and source MCG are in the same frequency (intra-frequency) and same band (intra-band) and are within an overlapping time resource.

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

[0141] In the case of same-frequency DAPS HO operation, the UE expects that the active DL BWP and active UL BWP of the target cell are contained within the active DL BWP and active UL BWP of the source cell, respectively.

[0142] The UE is N for the target MCG cells targetpdcch-BlindDetectionMCG1-UE can be provided to indicate the ability to monitor the maximum number of PDCCH candidates per slot corresponding to downlink cells, and for the source MCG N cells source 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. If the UE is provided with a search space set for both the target MCG and the source MCG, the UE expects that no USS set in any slot will have any assigned PDCCH candidates for both the target MCG and the source MCG.

[0143] Full duplex operation for NR

[0144] In 5G, new service types such as XR (Extended Reality), AI-based services, and self-driving cars are emerging. In these services, traffic fluctuates dynamically in both the DL and UL directions, and low latency may be required for transmitted packets. In 5G services, traffic load can increase explosively to support various new use cases.

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

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

[0147] Referring to Fig. 5, the structure in which DL and UL are allocated on the frequency axis of SBFD (subband-wise full duplex, which can simply be called sub-band full duplex) and SSFD (spectrum-sharing full duplex) can be identified. In the case of SBFD, transmission and reception of DL and UL are performed through different frequency resources within a single carrier. That is, DL and UL have different frequency resources for the same time resource. In the case of SSFD, transmission and reception of DL and UL are performed through the same frequency resource or overlapping frequency resources within a single carrier. That is, DL and UL can have the same or overlapping frequency resources for the same time resource.

[0148] This full-duplex (FD) communication can be used in combination with existing half-duplex (HD) communication. In an existing half-duplex-based TDD communication environment, some time resources may be used for full-duplex communication. In some time resources where full-duplex communication is performed, SBFD or SSFD operations may be performed.

[0149] FIG. 6 illustrates examples of resource structures in which a time resource operating in HD (half duplex) and a time resource operating in FD (full duplex) coexist according to one embodiment of the present disclosure.

[0150] Referring to FIG. 6(a), some time resources are used for SBFD-based communication, and the remaining time resources are used for HD-based communication. Referring to FIG. 6(b), some time resources are used for SSFD-based communication, and the remaining time resources are used for HD-based communication. Here, time resources can be set to slots, symbols, subframes, or other similar time units.

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

[0152] The above total frequency resources may refer to the system band, but may also refer to the DL BWP in the downlink and the UL BWP in the uplink. Additionally, frequency resources operating as UL may be referred to as 'UL usable PRBs'. UL usable PRBs may also be referred to as RBs (PRBs) included in both the active UL BWP and the UL subband (or UL subband frequency resources within the active UL BWP).

[0153] DL available PRBs may be referred to as DL subband frequency resources within an active DL BWP (or RBs (PRBs) included in both the active DL BWP and the DL subband).

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

[0155] Hereinafter, for the sake of convenience of explanation, it is assumed that the base station performs full-duplex communication and the terminal performs half-duplex communication, but is not limited thereto. For example, the methods described in this disclosure may be applied even when both the base station and the terminal perform full-duplex communication.

[0156] The following describes a random access procedure / process. The present disclosure proposes a method for setting up a bandwidth part (BWP) resource for intra-carrier full-duplex communication based on the random access procedure described below.

[0157] RACH (random access channel) procedure

[0158] The physical random access procedure can be triggered by a PRACH transmission request or PDCCH command (order) from the upper layer. The upper layer settings for the PRACH transmission may include the following:

[0159] Settings for PRACH transmission.

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

[0161] PRACH consists of the PRACH format selected from the specified PRACH resource and the transmission power P PRACH,b,f,c It is transmitted using (i).

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

[0163] In a Type-2 random access procedure (for a common set of PRACH opportunities), the UE is provided with N, the number of SS / PBCH block indices associated with one PRACH opportunity, by ssb-perRACH-OccasionAndCB-PreamblesPerSSB, and Q, the number of contention-based preambles per SS / PBCH block index per valid PRACH opportunity, by msgA-CB-PreamblesPerSSB-PerSharedRO. PRACH transfers may be performed within an SSB-RO mapping cycle on a subset of PRACH opportunities associated with the same SS / PBCH block index according to the PRACH mask index provided by msgA-SSB-SharedRO-MaskIndex.

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

[0165] For a Type-1 random access procedure or a Type-2 random access procedure using PRACH opportunities set separately from the Type-1 random access procedure, if N < 1, a single SS / PBCH block index is mapped to 1 / N consecutive valid PRACH opportunities, and the R-competition-based preamble associated with the SS / PBCH block index per valid PRACH opportunity starts at preamble index 0. If N ≥ 1, the R-competition-based preamble associated with the SS / PBCH block index n (0 ≤ n ≤ N-1) per valid PRACH opportunity is preamble index n·N preamble total Starting from / N, where N preamble total is provided by totalNumberOfRA-Preambles for a type-1 random access procedure, or by msgA-TotalNumberOfRA-Preambles for a type-2 random access procedure, and is an integer multiple of N.

[0166] For a Type-2 random access procedure using commonally configured PRACH opportunities, if N < 1, a single SS / PBCH block index is mapped to 1 / N consecutive valid PRACH opportunities, and the Q-competition-based preamble associated with the SS / PBCH block index per valid PRACH opportunity starts at preamble index R. If N ≥ 1, the Q-competition-based preamble associated with the SS / PBCH block index n (0 ≤ n ≤ N-1) per valid PRACH opportunity is preamble index n·N preamble total Starting from / N+R, where N preamble total is provided by totalNumberOfRA-Preambles.

[0167] For link recovery, the UE is provided with N SS / PBCH block indices associated with one PRACH opportunity by the 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 the 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 N consecutive SS / PBCH block indices are associated with one PRACH opportunity.

[0168] SS / PBCH block indexes are provided by ssb-PositionsInBurst of SIB1 or ServingCellConfigCommon and can be mapped to valid PRACH opportunities in the following order depending on specific parameters:

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

[0170] Second, in ascending order of the frequency resource index of frequency multiplexing PRACH opportunities.

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

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

[0173] The association period for mapping SS / PBCH block indexes to PRACH opportunities starts from frame 0, and at least once N within the association period Tx SSB It is the smallest value in the set determined from the PRACH setup cycle so that SS / PBCH block indexes are mapped to PRACH opportunities. Here, UE is N Tx SSBObtain from the ssb-PositionsInBurst value of SIB1 or ServingCellConfigCommon. N even after an integer cycle mapping SS / PBCH block indexes to PRACH opportunities within the association cycle. Tx SSB If there are sets of PRACH opportunities or PRACH preambles that are not mapped to SS / PBCH block indices, the SS / PBCH block index is not mapped to those sets of PRACH opportunities or PRACH preambles. The association pattern period includes one or more association periods, and the pattern between a PRACH opportunity and an SS / PBCH block index is determined to repeat at a maximum of 160ms. PRACH opportunities that are not associated with an SS / PBCH block index after an integer number of association periods are not used for PRACH transmission.

[0174] In the case of a PRACH transfer triggered by a PDCCH command, the PRACH mask index field indicates the PRACH opportunity of the PRACH transfer 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 zero. The UE is K by CellSpecific_Koffset cell,offset If provided, the PRACH opportunity is UL BWP slot n+2 μ ·K cell,offset It is set thereafter. Here, n is the slot of the UL BWP for PRACH transmission that overlaps with the end of the PDCCH command reception, μ is the SCS setting for PRACH transmission, and T TAAssume =0. If the PDCCH reception for a PDCCH command contains two PDCCH candidates from two associated sets of search spaces based on searchSpaceLinking, the last symbol of the PDCCH reception is the last symbol of the PDCCH candidate that ends later. The PDCCH reception contains two PDCCH candidates even if the UE does not need to monitor either of the two PDCCH candidates.

[0175] For a PRACH transfer triggered by a request from an upper layer, if ssb-ResourceList is provided, the PRACH mask index is represented by ra-ssb-OccasionMaskIndex, which indicates the PRACH opportunity of the PRACH transfer in the PRACH opportunity associated with the selected SS / PBCH block index.

[0176] PRACH opportunities are mapped consecutively for each corresponding SS / PBCH block index. The indexing of PRACH opportunities represented by the mask index value is initialized for each mapping cycle of consecutive PRACH opportunities per SS / PBCH block index. The UE selects a PRACH opportunity represented by the PRACH mask index value for the SS / PBCH block index designated for PRACH transmission in the first available mapping cycle.

[0177] For the specified preamble index, the order of PRACH opportunities is as follows:

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

[0179] Second, within the PRACH slot, in ascending order of the time resource index of the time multiplexing PRACH opportunity.

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

[0181] For a PRACH transfer triggered by a request from an upper layer, if csirs-ResourceList is provided, the value of ra-OccasionList represents a list of PRACH opportunities for the PRACH transfer represented by the selected CSI-RS index (csi-RS). The indexing of PRACH opportunities represented by ra-OccasionList is initialized for each association pattern cycle.

[0182] Table 6 shows the mapping between the PRACH setup cycle and the PRACH opportunity association cycle in the SS / PBCH block.

[0183] [Table 6]

[0184]

[0185] For the paired spectrum or supplementary uplink band, all PRACH opportunities are valid.

[0186] For unpaired spectra:

[0187] If the UE is not provided with tdd-UL-DL-ConfigurationCommon, it does not precede the SS / PBCH block in the PRACH slot, and at least N after the last SS / PBCH block received symbol. gap If it starts after the symbol, the PRACH opportunity within the PRACH slot is valid. The above N gap It is provided in Table 7 below. Additionally, if channelAccessMode = "semiStatic" is provided, it must not overlap with the consecutive symbol set prior to the start of the next channel occupancy time, in which case the UE does not perform transmission.

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

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

[0190] If it is within the UL symbol, or

[0191] Not preceding the SS / PBCH block within the PRACH slot, and at least N after the last downlink symbol gap It starts after the symbol, and at least N after the last SS / PBCH block symbol. gap In the case where it starts after the symbol. The above N gap This is provided in Table 7 below. Additionally, if channelAccessMode = "semiStatic" is provided, it must not overlap with the consecutive symbol set prior to the start of the next channel occupancy time, in which case transmission must not be performed.

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

[0193] For a specific preamble format (e.g., preamble format B4), N gap It can be 0.

[0194] Table 7 shows N for preamble SCS(μ). gap Represents the value.

[0195] [Table 7]

[0196]

[0197] If a random access procedure is initiated by a PDCCH command, and if requested by an upper layer, the UE transmits a PRACH at a 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 at least msec.

[0198] 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 of the SCS setting of the PDCCH command and the SCS setting of the corresponding PRACH transmission.

[0199] If the active UL BWP is not changed, △BWPSwitching=0, otherwise △BWPSwitching may be defined in the standard specification.

[0200] In the case of FR1, △ Delay =0.5 msec, and in the case of FR2, △ Delay =0.25 msec.

[0201] T switch is the switching gap duration.

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

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

[0204] Hereinafter, examples of PRACH setting tables used in the methods proposed through the present disclosure are described.

[0205] Table 8 shows examples of random access settings for FR1 and unpaired spectra.

[0206] [Table 8]

[0207]

[0208]

[0209]

[0210]

[0211]

[0212]

[0213] Table 9 shows examples of random access settings for FR2 and unpaired spectra.

[0214] [Table 9]

[0215]

[0216]

[0217]

[0218]

[0219]

[0220]

[0221]

[0222] Table 10 shows examples of random access settings for FR1 and paired spectrum / supplementary uplink.

[0223] [Table 10]

[0224]

[0225]

[0226]

[0227]

[0228]

[0229] Table 11 shows the supported △f RA and corresponding combinations of △f It represents.

[0230] [Table 11]

[0231]

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

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

[0234] OFDM baseband signal generation for PRACH

[0235] Time continuous signal s of antenna port p for PRACH l (p,u) (t) can be defined as in Equation 1.

[0236] [Equation 1]

[0237]

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

[0239] △f RA is the subcarrier spacing of the initial uplink bandwidth portion during initial connection. In the case of non-initial connection, △f RA is the subcarrier spacing of the active uplink bandwidth portion.

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

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

[0242] 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-level parameter msgA-RO-FrequencyStart and applies if a Type-2 random access procedure is started. Otherwise, it is provided by msg1-FrequencyStart.

[0243] n RA is a frequency domain PRACH transmission opportunity index for a specific PRACH transmission opportunity at a given time instance.

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

[0245] N RB,UL,n start,μ is RB n,UL start,μ This is the starting CRB index of the uplink RB set n corresponding to the amount. The UE assumes that the RB set is defined when IntraCellGuardBandsPerSCS is not provided for the UL carrier.

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

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

[0248] N CP,l RA = N CP RA+ n·16k, and △f RA When ∈{1.25, 5}kHz, n=0 and △f RA For ∈{15, 30, 60, 120, 480, 960}kHz, 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 = This is the number of times it overlaps with 0.5ms.

[0249] PRACH preamble starting position 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), provided by [Equation 2].

[0250] [Equation 2]

[0251]

[0252] Here, it is assumed that the subframe or 60 kHz slot starts at t=0.

[0253] Timing advance value N TA We must assume =0.

[0254] N u μ and N CP,l-1 μ It can be provided according to standard specifications.

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

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

[0257] N t RA is a PRACH transmission opportunity within the PRACH slot, ranging from 0 to N within the PRACH slot. t RA,slot Numbers are assigned in ascending order up to -1. Here, N t RA,slot is L RA ∈ When it is {139, 571, 1151}, it can be provided by a predetermined table, and L RA It is fixed at 1 when =839.

[0258] N dur RA is provided by a predetermined table.

[0259] n slot RA is given as follows:

[0260] △f RA For the case where ∈{1.25,5,15,60}kHz, n slot RA .

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

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

[0263] If the "number of PRACH slots within the 60 kHz slot" of the predetermined table is 1, △f RA n at 480kHz slot RA =7, △f RA n at =960kHz slot RA =15.

[0264] If the "number of PRACH slots within the 60 kHz slot" of the predetermined table is 2, △f RA n at =480kHz slot RA ∈{3,7}, △f RA n at =960kHz slot RA ∈{7,15}.

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

[0266] n t RA =N t RA,slot In the case of -1, the PRACH preamble is transmitted in the corresponding PRACH preamble format among B1, B2, and B3 during the PRACH transmission opportunity.

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

[0268] Supported N RB RA , △f RA , parameter combinations of △f and The values ​​corresponding to can be represented as shown in Table 12 below.

[0269] [Table 12]

[0270]

[0271] PRACH repetition

[0272] RO groups for PRACH repetition can be introduced to improve coverage. For example, if a base station sets and / or directs N (e.g., 2, 4, 8) repetition numbers, N ROs among the valid ROs existing at the same frequency can be grouped into an RO group in ascending order of time domain index. In the RO group, N-1 ROs may be located at the same frequency as the first RO, as shown in FIGS. 8 and 9. That is, N ROs existing at the same frequency among the valid ROs associated with the same beam can be grouped into a single RO group.

[0273] Figure 8 illustrates RO groups in the case where the number of repetitions is 4, the number of SSBs (synchronization signal blocks) is 2, the FDMed (frequency domain multiplexed) RO is 2, and the number of SSBs per RO is 1 / 2.

[0274] Figure 9 illustrates RO groups in the case where the number of repetitions is 4, the number of SSBs is 3, the FDMed RO is 4, and the number of SSBs per RO is 1.

[0275] When PRACH transmission is performed with preamble repetitions, the time period starting from frame 0 is defined as an associative pattern period of at least an integer number, and N for all configured preamble repetition counts within that time period. Tx SSBFor each SS / PBCH block index, at least one set of valid PRACH opportunities must be determined. For each set number of preamble iterations, the set of valid PRACH opportunities is repeated at the corresponding time period, and the time period is defined as the minimum integer number of associated pattern periods. Here, the associated pattern period can be set to one or more associated periods, and for each SSB index, an associated pattern having at least one set of valid PRACH opportunities is repeated at a maximum of 160ms.

[0276] The association cycle for mapping SS / PBCH block indexes to PRACH opportunities starts from frame 0, and N Tx SSB It is the minimum integer value in the set determined by the PRACH setup cycle so that the SS / PBCH block index is mapped to a PRACH opportunity at least once within the corresponding association cycle. Here, UE is N Tx SSB Obtain from the ssb-PositionsInBurstssb-PositionsInBurstssb-PositionsInBurst value of SIB1 or ServingCellConfigCommon. The associative pattern cycle includes one or more associative cycles, and is determined so that the pattern between the PRACH opportunity and the SS / PBCH block index repeats at most every 160ms.

[0277] Below, the HD operations supported by NR are described.

[0278] <Slot Settings>

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

[0280] The following items are applicable to each serving cell.

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

[0282] tdd-UL-DL-ConfigurationCommon provides the following:

[0283] i) Reference SCS setting μ by referenceSubcarrierSpacing ref .

[0284] ii) pattern1.

[0285] pattern1 can provide the following:

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

[0287] The number of slots containing only downlink symbols, d, determined by nrofDownlinkSlots. slots ,

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

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

[0290] Uplink symbols u by nrofUplinkSymbols sym .

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

[0292] SCS setting μ for slot setting period P msec ref The slot containing is included. The first d in the S slot slots The slot contains only downlink symbols, and the last slot u slots ...includes only uplink symbols. The first d slots Slot D sym The subsequent symbol is a downlink symbol. The last u slots u in front of the slot sym The symbol is an uplink symbol. The rest (Sd slots -u slots )-N symb slot -d sym -u sym is a flexible symbol.

[0293] In every 20 / P cycle, the first symbol is the first symbol of the even frame.

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

[0295] Pattern 2 can provide the following.

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

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

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

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

[0300] Uplink symbols u by nrofUplinkSymbols sym,2 .

[0301] The applicable value of P2 is the same as the applicable value of P.

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

[0303] 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 the slot sym,2 The symbol is a downlink symbol. The last u slots,2 u prior to the slot sym,2 The symbol is an uplink symbol. The remainder (S2-d slots,2 -u slots,2 )-N symb slot - d sym,2 -u sym,2 is a flexible symbol.

[0304] UE expects P+P2 to be able to divide 20 ms.

[0305] For every 20 / (P+P2) period, the first symbol is the first symbol of the even frame.

[0306] UE references SCS setting μ refFor this configured DL BWP or UL BWP, it is expected to be less than or equal to the SCS setting μ. Each slot provided by pattern1 or pattern2 is a consecutive 2 of an active DL BWP or active UL BWP. (μ-μref) It can be applied to the slot. The reference SCS setting μ is for the slot. ref Starts at the same time as the first slot of, and reference SCS setting μ ref Each downlink, flexible, or uplink symbol for is 2 for SCS setting μ (μ-μref) It corresponds to a continuous downlink, flexible, or uplink symbol.

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

[0308] tdd-UL-DL-ConfigurationDedicated can provide the following.

[0309] The set of slot settings provided by slotSpecificConfigurationsToAddModList,

[0310] For each slot configuration in the slot configuration set, the slot index of the slot provided by slotIndex, and the set of symbols of the slot provided by symbols: if symbols = allDownlink, all symbols of the slot are downlinks; if symbols = allUplink, all symbols of the slot are uplinks; if symbols = explicit, nrofDownlinkSymbols provides the number of the first downlink symbols of the slot, and nrofUplinkSymbols provides the number of the last uplink symbols of the slot. If nrofDownlinkSymbols is not provided, the slot has no first downlink symbol, and if nrofUplinkSymbols is not provided, the slot has no last uplink symbol. The remaining symbols of the slot are flexible symbols.

[0311] For each slot having 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 mark a symbol designated as a downlink by tdd-UL-DL-ConfigurationCommon as an uplink, or a symbol designated as an uplink as a downlink.

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

[0313] The number of downlink symbols, uplink symbols, and flexible symbols in each slot of the slot configuration cycle and tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are determined from each configured BWP.

[0314] The UE considers the symbols in the slots marked as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as receiving, and the symbols in the slots marked as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated as transmitting.

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

[0316] If the UE receives the corresponding instruction in DCI format, it receives PDSCH or CSI-RS from the symbol set of the slot.

[0317] If the UE receives the corresponding instruction from DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR, it transmits PUSCH, PUCCH, PRACH, or SRS in the symbol set of the slot.

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

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

[0320] If the UE is provided 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.

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

[0322] If the UE does not indicate the [partialCancellation] function, the UE receives T from the last symbol of the PDCCH reception. proc,2 It is expected that the transmission of PUCCH, PUSCH, or PRACH will not be cancelled in the symbols occurring within. Otherwise, the UE cancelled the transmission of PUCCH, PUSCH, the actual repetition of PUSCH, or PRACH.

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

[0324] The UE receives T from the last symbol of the PDCCH reception proc,2 It is expected that SRS transmission will not be canceled on symbols occurring within this period. The UE cancels SRS transmission on a subset of the remaining symbols.

[0325] T proc,2 is d 2,1It can be assumed to be =1, and it is the PUSCH preparation time for UE processing capability that matches μ, which corresponds to the smallest SCS setting between the SCS setting of PDCCH containing the DCI format and the SCS settings of SRS, PUCCH, and PUSCH. If the SCS setting of PRACH is 15kHz or higher, μ corresponds to the SCS setting of PRACH; otherwise, μ r =0.

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

[0327] If the symbol set of a slot is indicated as an uplink to the UE 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 from the symbol set of that slot.

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

[0329] If the symbol set of a slot is marked as flexible to the UE by tdd-UL-DL-ConfigurationCommon and, if provided, tdd-UL-DL-ConfigurationDedicated, the UE does not expect to receive both upper-layer-only parameters that set the UE's transmit and upper-layer-only parameters that set the UE's receive from the symbol set of that slot.

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

[0331] If the 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 half-DuplexTDD-CA-SameSCS-r16 feature support; and if none of the multiple serving cells are 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 receiving SS / PBCH blocks, or the symbols of the slots corresponding to the SS / PBCH blocks configured for L1 beam measurement / reporting, by ssb-PositionsInBurst of SSB-MTCAdditionalPCI associated with the active TCI status of PDCCH or PDSCH, provided that the UE is not provided with dl-OrJointTCI-StateList. For a set, if a transmission overlaps with a symbol of that symbol set, the UE does not transmit PUSCH, PUCCH, or PRACH in the slot, and does not transmit SRS within the symbol set of the following slots.

[0332] i) where the UE is not capable of simultaneous transmission and reception via simultaneousRxTxInterBandCA between multiple serving cells, ii) one of the cells corresponding to the same band as the first cell, regardless of whether any of the multiple serving cells are capable of simultaneous transmission and reception via simultaneousRxTxInterBandCA.

[0333] The symbol set of the slot corresponding to the valid PRACH event and N prior to the valid PRACH event gapIn the case of a symbol, if the reception overlaps with a symbol of the symbol set, the UE does not receive PDCCH, PDSCH, or CSI-RS in the slot. The UE does not expect the symbol set of the slot to be indicated as a downlink by tdd-UL-DL-Configuration Common or tdd-UL-DL-ConfigurationDedicated.

[0334] For the symbol set of slots indicated to the UE by pdcch-ConfigSIB1 in the MIB for the CORESET for the Type0-PDCCH CSS set, the UE does not expect that symbol set to be indicated uplinked by tdd-UL-DL-Configuration Common or tdd-UL-DL-ConfigurationDedicated.

[0335] 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 is scheduled to receive PDSCH in one of the multiple slots is an uplink symbol, the UE does not receive PDSCH in the slot.

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

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

[0338] Indicates that it supports half-duplex TDD-CA-SameSCS-r16 features, and

[0339] If PDCCH is not configured to monitor to detect DCI format 2_0 in multiple service cells,

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

[0341] i) Multiple serving cells configured where the UE cannot transmit and receive simultaneously as indicated by simultaneous RxTxInterBandCA among the multiple serving cells, ii) Multiple serving cells configured such that the UE can transmit and receive simultaneously via RxTxInterBandCA, with each band cell configured accordingly.

[0342] Here, the symbol is set as follows.

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

[0344] If the symbol is flexible and the UE is configured to transmit SRS, PUCCH, PUSCH, or PRACH from the symbol, it can be configured as an uplink.

[0345] If the symbol is flexible and the UE is configured to receive PDCCH, PDSCH, or CSI-RS from the symbol, it can be configured as a downlink.

[0346] If another cell among the cells configured as directionalCollisionHandling-r16 operates in the same frequency band as the reference cell, the UE does not expect the following.

[0347] i) Symbols that are displayed as a downlink or uplink in the reference cell and as an uplink or downlink in other cells, respectively, by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated,

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

[0349] iii) Established by the upper layer to receive PDCCH, PDSCH, or CSI-RS on a flexible symbol in a reference cell and to detect a DCI format that schedules transmission in that symbol in another cell.

[0350] If the reference cell and another cell among the cells configured with directionalCollisionHandling-r16 operate in different frequency bands, the UE

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

[0352] ii) If the corresponding symbol in the reference cell is marked as a downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, a signal / channel scheduled by DCI format is transmitted from the symbol in another cell.

[0353] 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 set in the upper layer from the flexible symbols of the reference cell in that symbol set.

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

[0355] 1) It is not expected that the tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated symbol for the reference cell will be identified as an uplink and that the DCI format will be detected to schedule reception at the corresponding symbol of another cell.

[0356] 2) It is not expected that the upper layer will detect a DCI format that is configured to transmit SRS, PUCCH, PUSCH, or PRACH on a flexible symbol in a reference cell and schedule reception on the corresponding symbol in another cell.

[0357] 3) If at least one symbol in the corresponding symbol set is indicated as a downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the reference cell, or corresponds to PDCCH, PDSCH, or CSI-RS reception, PUCCH, PUSCH, or PRACH set by the upper layer for the symbol set of another cell is not transmitted.

[0358] 4) If the corresponding symbol set is indicated as a 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.

[0359] 5) If at least one symbol in the corresponding symbol set is indicated as an uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the reference cell, or corresponds to an SRS, PUCCH, PUSCH, or PRACH transmission, it does not receive a PDCCH, PDSCH, or CSI-RS set by the upper layer for the symbol set of another cell.

[0360] 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 designated as downlink or uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated in the other cell is considered a flexible symbol.

[0361] 7) It is not expected to detect a first DCI format that schedules transmission or reception for a specific symbol in the first cell, and a second DCI format that schedules reception or transmission for that symbol in the second cell, respectively.

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

[0363] UE Procedure for Determining Slot Format

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

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

[0366] In addition, the UE L for DCI format 2_0 in one or more serving cells SFI having a CCE aggregation level Receives a search space set for monitoring PDCCH candidates and settings for the corresponding CORESET p. PDCCH candidates are CCE aggregation levels L for the search space set s in CORESET p. SFI The first about PDCCH is a candidate.

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

[0368] 1) ID of the serving cell by servingCellId

[0369] 2) SFI index field location of DCI format 2_0 by positionInDCI

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

[0371] 4) For unpaired spectral operation, the reference SCS setting μ based on the subcarrier spacing SFI , if an auxiliary UL carrier is set in the serving cell, the reference SCS setting μ by subcarrierSpacing2 for the auxiliary UL carrier SFI,SUL

[0372] 5) For paired spectral operation, the reference SCS setting μ for DL ​​BWP by subcarrier spacing SFI,DL and reference SCS setting μ for UL BWP by subcarrierSpacing2 SFI,UL

[0373] 6) The locations of the available RB set indicator fields in DCI format 2_0 and the fields by available RB-SetsPerCell are as follows.

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

[0375] A bitmap mapped to the RB set of the serving cell, and the intraCellGuardBandsDL-List for the serving cell, where intraCellGuardBandsDL-List for the serving cell is set or if no intraCellGuardBandsDL-List for the serving cell is 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 if the value is '1', it indicates that the RB set is available for reception, and if the value is '0', it indicates that the RB set is not available for reception, and the RB set remains available or unavailable for reception until the end of the remaining channel occupancy period.

[0376] The location of the Channel Occupancy Period field, indicated by CO-DurationsPerCell in DCI format 2_0; this field represents the remaining channel occupancy period of the serving cell, starting from the first symbol of the slot where the UE detects DCI format 2_0 by providing a value from co-DurationList. In the Channel Occupancy Period field Bits are included, where COdurationListSize is the number of values ​​provided by co-DurationList. If CO-DurationsPerCell is not provided, the remaining channel occupancy period of the serving cell is the number of slots where the SFI-index field value provides the corresponding slot format, starting from the slot where the UE detects DCI format 2_0.

[0377] Reference SCS settings for co-DurationList by subcarrierSpacing.

[0378] Location of the search space set group switching flag field, DCI format 2_0 by SearchSpaceSwitchTrigger, where the field indicates a group of two search space set groups for PDCCH monitoring for scheduling for a serving cell or a serving cell set, and is provided by CellGroupsForSwitching.

[0379] The SFI index field value of DCI Format 2_0 indicates to the UE the slot format for each slot corresponding to the number of slots in each DL BWP or each UL BWP, starting from the slot where the UE detected DCI Format 2_0. The number of slots must 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. Slot formats are identified by their corresponding format indices as provided in Table 7, where 'D' represents downlink symbols, 'U' represents uplink symbols, and 'F' represents flexible symbols.

[0380] 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 obtained by the UE during PDCCH monitoring for DCI format 2_0 by the corresponding SFI index field value, and the UE detects one or more DCI format 2_0s representing a slot format for one slot, the UE expects that each of the one or more DCI format 2_0s represents the same slot format.

[0381] The UE is not expected to be configured to monitor PDCCH for DCI format 2_0 in a second serving cell using an SCS larger than the serving cell.

[0382] Table 13 shows examples of slot formats for normal cyclic prefixes.

[0383] [Table 13]

[0384]

[0385]

[0386] For non-paired spectral operation for the UE in the serving cell, the reference SCS setting μ for each slot format is determined by the subcarrier spacing (SCS).SFI It is provided as a combination of slot formats indicated by the SFI index field value of DCI format 2_0. The UE references the SCS setting μ SFI and for active DL BWP or active UL BWP with SCS setting μ, μ≥μ SFI It 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 active UL BWP. (μ-μ_SFI) It is applied to consecutive slots, and the first slot is the reference SCS setting μ SFI Starts simultaneously with the first slot of and references SCS setting μ SFI Each downlink, flexible, or uplink symbol corresponds to a succession of downlink, flexible, or uplink symbols in the SCS setting μ.

[0387] For paired spectral operation for the UE of the serving cell, the SFI index field of DCI format 2_0 indicates a combination of slot formats including the slot format combination for the reference DL BWP and the slot format combination for the reference UL BWP of the serving cell. The UE uses the reference SCS setting μ for the slot format combination indicated by the SFI index field value of DCI format 2_0 for the reference DL BWP of the serving cell, determined by the subcarrier spacing. SFI,DL It 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 serving cell's reference UL BWP. 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 the first The value for the slot format combination applies to the reference DL BWP, and the following value applies to the reference UL BWP. μ SFI,DL <μ SFI,UL and each For the value, the first value of the slot format combination is applied to the reference DL BWP, and the next The value is applied to the reference UL BWP.

[0388] UE references SCS setting μ SFI,DL Provided with, the SCS setting μ of the active DL BWP DL μ for DL ≥μ SFI,DL satisfies. The UE references the SCS setting μ SFI,UL Provided with, the SCS setting μ of the active UL BWP UL μ for UL ≥μ SFI,UL It satisfies. For the reference DL BWP, each slot format of the slot format combination indicated by the SFI-index field value of DCI format 2_0 is indicated by the slotFormatCombinationId value mapped to the slotFormats value in slotFormatCombination, starting from the first slot that starts at the same time as the first slot of the reference DL BWP for the active DL BWP. It is applied to consecutive slots. Also, refer to the SCS setting μ SFI,DL Each downlink or flexible symbol is SCS setting μ DL About It corresponds to a number of consecutive downlinks or flexible symbols. For each slot format combination of the reference UL BWP, for the active UL BWP, starting from the first slot that begins at the same time as the first slot of the reference UL BWP. It is applied to consecutive slots. Also, refer to the SCS setting μ SFI,UL Each uplink or flexible symbol is SCS setting μ UL About It corresponds to a number of consecutive uplinks or flexible symbols.

[0389] In the case of an unpaired spectrum operation where the UE uses a second UL carrier in a serving cell, the SFI-index field value of DCI Format 2_0 indicates a slot format combination including a slot format combination for the serving cell's reference first UL carrier and a slot format combination for the serving cell's reference second UL carrier. For the serving cell's reference first UL carrier, the UE sets the reference SCS setting μ by subcarrierSpacing for the slot format combination indicated by the SFI-index field value of DCI Format 2_0. SFI The UE is provided with the reference SCS setting μ 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 Receives. Each For +1 slotFormats value, the first slot format combination The value is applied to the reference 1 UL carrier, and the next value is applied to the reference 2 UL carrier.

[0390] The UE sets the SCS μ for the active UL BWP of the second UL carrier. SUL This μ SUL ≥μ SFI,SUL Reference SCS setting μ to satisfy SFI,SUL It is expected that this will be provided. For the reference first UL carrier, each slot format of the slot format combination indicated by the SFI-index field of DCI format 2_0 is for the active DL BWP and the active UL BWP of the first UL carrier, starting from the first slot that begins at the same time as the first slot of the reference first UL carrier. It applies to consecutive slots. Each slot format for the slot format combination of the reference 2nd UL carrier is for the active UL BWP of the 2nd UL carrier, starting from the first slot that begins at the same time as the first slot of the reference 2nd UL carrier. It applies to consecutive slots.

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

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

[0393] For a symbol set of a slot, the UE detects DCI format 2_0 containing an SFI-index field value directing the symbol set of the slot to an uplink, and does not simultaneously detect a DCI format directing to receive PDSCH or CSI-RS in the symbol set of the same slot.

[0394] For a symbol set of a slot, the UE detects DCI format 2_0 containing an SFI-index field value directing the symbol set of the slot to a downlink, and does not simultaneously detect DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR directing to transmit PUSCH, PUCCH, PRACH, or SRS in the same symbol set of the slot.

[0395] For a set of symbols in a slot indicated by DCI format 2_0 as being within the remaining channel occupancy period through the channel occupancy period field or the SFI-index field, the UE does not detect DCI format 2_0 indicating that at a later point in time, no symbols in that set of symbols are within the remaining channel occupancy period through the channel occupancy period field or the SFI-index field.

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

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

[0398] The symbol set of the slot corresponding to the valid PRACH opportunity and N prior to the valid PRACH opportunity gap For a symbol, the UE does not detect DCI format 2_0 containing an SFI-index field value that indicates the symbol set of the corresponding slot as a downlink.

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

[0400] This applies to the symbol set of slots flexibly directed to the UE by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated (if provided), or when tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the UE, and the UE detects DCI format 2_0 which provides a format for the slot using a slot format value other than 255.

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

[0402] If the SFI-index field value of DCI format 2_0 indicates that the symbol set of the slot is flexible and the UE detects a DCI format that instructs the UE to receive PDSCH or CSI-RS from the symbol set of the slot, the UE receives PDSCH or CSI-RS from the symbol set of the slot.

[0403] If the SFI-index field value of DCI format 2_0 indicates that the symbol set of the slot is flexible, 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 from the symbol set of the slot, the UE transmits PUSCH, PUCCH, PRACH, or SRS from the symbol set of the slot.

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

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

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

[0407] If the UE is configured by the upper layer to transmit PUCCH, PUSCH, or PRACH from the symbol set of a slot, the UE transmits PUCCH, PUSCH, or PRACH from the symbol set of a slot only when the SFI-index field value of DCI format 2_0 indicates the symbol set of that slot as an uplink.

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

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

[0410] The UE does not detect cases where the SFI-index field value of DCI format 2_0 indicates the symbol set of a slot as downlink or flexible for a symbol set of a slot containing symbols corresponding to a repetition of a PUSCH transmission enabled by UL Type 2 grant PDCCH.

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

[0412] If the UE is configured by the upper layer to receive CSI-RS or PDSCH from the symbol set of a slot, the UE detects DCI format 2_0 which indicates a slot format where the slot format value is not 255, and the slot format indicates a subset of the symbol set to uplink or flexible, or the UE detects a DCI format that indicates the UE to transmit PUSCH, PUCCH, SRS, or PRACH from at least one symbol in the symbol set, the UE cancels receiving CSI-RS from the symbol set of the slot or cancels receiving PDSCH from the slot.

[0413] In the case of UE operation using shared spectrum channel access in FR1 or in FR2-2 where the UE is set ChannelAccessMode2 = 'enabled', the UE is configured by the upper layer to receive CSI-RS, and if CO-DurationsPerCell is provided, for the symbol set of a slot designated as downlink or flexible 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 symbol set of the corresponding slot that is not included within the remaining channel occupancy period.

[0414] If the UE is configured by the upper layer to receive DL PRS from a slot's symbol set, the UE detects DCI format 2_0 which indicates a slot format where the slot format value is not 255, and the slot format indicates a subset of the symbol set to the uplink, or the UE detects a DCI format that indicates the UE to transmit PUSCH, PUCCH, SRS, or PRACH in at least one symbol of the symbol set, the UE cancels receiving DL PRS from the slot's symbol set.

[0415] If the UE is configured by the upper layer to transmit SRS, PUCCH, PUSCH, or PRACH in the symbol set of a slot, and the UE detects DCI format 2_0 indicating a slot format where the slot format value is not 255, and that slot format indicates a subset of the symbol set to downlink or flexible, or detects a DCI format that instructs the UE to receive CSI-RS or PDSCH in a subset of the symbol set, then

[0416] If the UE does not indicate the [partialCancellation] function, the UE transmits PUCCH, PUSCH, or PRACH from the last symbol of the PDCCH reception where the first symbol of the symbol set detected the DCI format to T proc,2 If it occurs within [time], the transmission is not canceled. Otherwise, the UE cancels the PUCCH, PUSCH, or the actual repetition of PUSCH or the PRACH transmission in the symbol set.

[0417] If the UE indicates the [partialCancellation] function, the UE detects the DCI format from the last symbol of the received PDCCH T proc,2 PUCCH, PUSCH, or PRACH transmissions are not cancelled in symbols of the symbol set occurring within the following period. The UE cancelled the PRACH transmission in the actual repetition of PUCCH, PUSCH, or PUSCH, or in symbols of the remaining symbol set.

[0418] The UE detects the DCI format from the last symbol of the received PDCCH, T proc,2 The UE does not cancel SRS transmissions on symbols in the symbol subset occurring within [time]. The UE cancels SRS transmissions on symbols in the remaining symbol subset.

[0419] T proc,2 is the PUSCH preparation time for the corresponding UE processing capability, and d 2,1Assuming =1, μ is the SCS setting of PDCCH including the DCI format and the SCS setting of SRS, PUCCH, PUSCH or μ r It corresponds to the smallest SCS setting among them. Here, μ r corresponds to the PRACH SCS setting if the PRACH SCS setting is 15kHz or higher, and otherwise μ r =0.

[0420] If the UE is configured by the upper layer to receive CSI-RS, or detects DCI format 0_1 ​​and is instructed to receive CSI-RS from one or more sets of RBs and the symbol set of the slot, or if the UE detects DCI format 2_0 and indicates that the bitmap is not receivable from any of the one or more sets of RBs, the UE cancels receiving CSI-RS from the symbol set of the slot.

[0421] For PDCCH monitoring, the UE considers the flexible symbols of the CORESET set in the UE as downlink symbols if the UE does not detect the SFI-index field value of DCI format 2_0 which directs the symbol set of the slot to flexible or uplink, and also does not detect the DCI format which directs to transmit SRS, PUSCH, PUCCH, or PRACH in that symbol set.

[0422] For a symbol set of slots designated as flexible (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 fails to detect DCI format 2_0 providing a slot format for the slot,

[0423] 1) The UE receives PDSCH or CSI-RS from the symbol set of the corresponding slot, only when the UE receives a DCI format containing instructions for it.

[0424] 2) The UE transmits PUSCH, PUCCH, PRACH, or SRS in the symbol set of the corresponding slot, only when the UE receives a DCI format containing instructions for the corresponding RAR UL grant, fallbackRAR UL grant, or successRAR.

[0425] 3) The UE receives the PDCCH.

[0426] 4) If the UE is configured by the upper layer to receive PDSCH from the symbol set of a slot, the UE does not receive PDSCH from the symbol set of that slot.

[0427] 5) If the UE is configured by the upper layer to receive CSI-RS from the symbol set of a slot, the UE does not receive CSI-RS from the symbol set of that slot unless CO-DurationsPerCell is provided and the symbol set of the slot falls within the remaining channel occupancy period.

[0428] 6) If the UE is configured by the upper layer to receive DL PRS from the symbol set of a slot, the UE receives DL PRS from the symbol set of that slot.

[0429] 7) If the UE is configured by the upper layer to transmit SRS, PUCCH, PUSCH, or PRACH in the slot's symbol set, but enableConfiguredUL is not provided,

[0430] a) If the UE does not instruct the [partialCancellation] function, the first symbol of PUCCH, PUSCH, the actual repetition of PUSCH, or PRACH is T from the last symbol of the PDCCH reception configured to monitor DCI format 2_0. proc,2 If it occurs within the slot, the UE does not cancel the transmission. Otherwise, the UE cancels the transmission of PUCCH, PUSCH, the actual repetition of PUSCH, or PRACH from the slot.

[0431] b) If the UE indicates the [partialCancellation] function, the UE monitors T from the last symbol of the PDCCH reception configured to monitor DCI format 2_0. proc,2 PUCCH, PUSCH, actual repetition of PUSCH, or PRACH transmission in the symbols of the symbol set occurring within [time] is not cancelled. The UE cancelled PUCCH, PUSCH, actual repetition of PUSCH, or PRACH transmission in the symbols of the remaining symbol set.

[0432] The UE is configured to monitor DCI format 2_0 from the last symbol of the received PDCCH T proc,2 The UE does not cancel SRS transmissions on symbols of the symbol set occurring within [timeframe]. The UE cancels SRS transmissions on symbols of the remaining symbol set.

[0433] T proc,2 is the PUSCH preparation time for the corresponding UE processing capability, and d 2,1 It can be assumed that =1. μ is the SCS setting of PDCCH containing DCI format 2_0 and the SCS setting of SRS, PUCCH, PUSCH or μ r It corresponds to the smallest SCS setting among them. Here, μ r corresponds to the PRACH SCS setting if the PRACH SCS setting is 15kHz or higher, and otherwise μ r =0.

[0434] If the UE is configured by the upper layer to transmit SRS, PUCCH, PUSCH, or PRACH from the slot's symbol set and enableConfiguredUL is provided, the UE can transmit SRS, PUCCH, PUSCH, or PRACH, respectively.

[0435] In a cell in the FR1 frequency band, if a UE is performing unpaired spectrum operation and scheduling restrictions based on RRM measurement are not applied, and the UE detects a DCI format that instructs it to transmit in a symbol set, there is no need to perform RRM measurement in another cell based on receiving an SS / PBCH block or CSI-RS containing at least one symbol from the symbol set.

[0436] TDD slot and / or symbol configurations can be determined through multiple operations. For example, all UEs in a cell can be assigned a cell-specific DL / UL pattern via tdd-UL-DL-ConfigurationCommon. Additionally, a UE can receive resources that were previously held as flexible slots and / or symbols as UE-specific allocations via the dedicated RRC signal tdd-UL-DL-ConfigurationDedicated. tdd-UL-DL-ConfigurationCommon can be transmitted via SIB1 or dedicated RRC signaling. For a specific slot and / or symbol to be configured as a flexible slot and / or symbol, both must be configured as flexible through 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, a DL / UL pattern configured based on tdd-UL-DL-ConfigurationCommon is used. If the UE does not receive the SlotFormatIndicator setting, it may receive PDSCH or CSI-RS in some or all symbols of the slot according to the instructions of DCI format 1_0, DCI format 1_1, or DCI format 0_1. Additionally, if the UE does not receive the SlotFormatIndicator setting, the UE may transmit PUSCH, PUCCH, PRACH, or SRS in some or all symbols of the slot according to the instructions of DCI format 0_0, DCI format 0_1, DCI format 1_0, DCI format 1_1, or DCI format 2_3.

[0437] Additionally, the base station does not set RO on resources allocated in slot and / or symbol units for HD DL transmission, and the UE may not expect RO setting. For resources allocated as HD flexible, RO setting may be performed based on several constraints. For example, if RO is not set via tdd-UL-DL-ConfigurationCommon, the PRACH occasion for a resource set as a PRACH slot does not lie before the SS / PBCH block resource, or is at least N with the last SS / PBCH block reception symbol. gap If it is located after the number of symbols, the corresponding PRACH opportunity can be treated as a valid RO.

[0438] On the other hand, if RO is configured via tdd-UL-DL-ConfigurationCommon, the PRACH opportunity of the resource configured as a UL symbol or PRACH slot is not located before the SS / PBCH block resource, or at least N with the last SS / PBCH block repeat symbol. gap If it is located after the number of symbols, the corresponding PRACH opportunity can be treated as a valid RO.

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

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

[0441] Referring to FIG. 10, when an SBFD setting / feature is applied to a resource in which a DL slot or a flexible (F) slot is set by an upper layer, some frequency resources of the SBFD slot may be set to DL, i.e., the SBFD DL subband, and some frequency resources may be set to UL, i.e., the SBFD UL subband. Here, a frequency gap may be set between the frequency resources of the SBFD DL subband and the frequency resources of the SBFD UL subband. Meanwhile, the direction of each SBFD subband may be indicated through a dynamic indication (e.g., DCI format 2_0 or SFI (slot format indicator)).

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

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

[0444] However, since the SBFD-aware UE (1110) recognizes the downlink slot resource to which the SBFD setting is applied as an SBFD resource (e.g., an SBFD symbol), it can expect an RO setting in the SBFD UL subband according to the new rule. The new rule is to view the SBFD symbol as a flexible symbol, which specifically means a condition in which a setting can be made in both the UL direction and the DL direction from a single symbol. At this time, the set RO or RO group can only be used by the SBFD-aware UE (1110) and can be set as an additional RO setting, that is, as a separate RO setting.

[0445] When determining the RO setting index, the base station may allow RO to be set for SBFD symbols configured as downlink by TDD settings. For example, the base station may inform the terminal of SBFD symbols through information included in the system information block (SIB). Additionally, it may indicate whether the symbols within the slot are downlink symbols, uplink symbols, or flexible symbols by TDD settings. In this case, a symbol designated as a downlink symbol by TDD settings may be a symbol designated as an SBFD symbol by the SIB. In such a case, the said SBFD symbol may be referred to as an SBFD symbol configured as downlink by TDD settings.

[0446] Likewise, a symbol designated as a flexible symbol by the TDD setting may be a symbol designated as an SBFD symbol by the SIB. In this case, the SBFD symbol may be referred to as an SBFD symbol set as flexible (flexible, F) by the TDD setting.

[0447] Based on parameters related to the signaled RO configuration index, ROs may be located in SBFD symbols and non-SBFD symbols. In this case, ROs that can be PRACH transmitted by legacy UEs and SBFD-aware UEs may be referred to as legacy ROs below, and ROs that can be PRACH transmitted only by SBFD-aware UEs may be referred to as SBFD ROs. Legacy UEs may determine that legacy ROs located in non-SBFD symbols and flexible symbols (e.g., SBFD symbols configured as flexible (F) by TDD configuration) are valid ROs, and SBFD-aware UEs may determine that legacy ROs and SBFD ROs located in non-SBFD symbols and SBFD symbols are valid ROs.

[0448] FIGS. 12 and FIGS. 13 illustrate examples of flexible slots to which an SBFD setting according to one embodiment of the present disclosure is applied.

[0449] FIG. 12 illustrates an example of a flexible slot when the RO is configured by a legacy RO configuration, and FIG. 13 illustrates an example of a flexible slot when the RO is configured by a separate RO configuration. Since the legacy UE (1220) treats the allocated resources as flexible slots, it determines the RO configuration based on existing rules and determines whether the RO is valid or invalid. On the other hand, since the SBFD-aware UE (1210) recognizes the resource as an SBFD resource, it can expect RO settings in the SBFD UL subband according to the new rule (SBFD UL subband may also be expressed as 'UL usable PRBs'. UL usable PRBs may refer to UL subband frequency resources within an active UL BWP. DL usable PRBs may refer to DL subband frequency resources within an active DL BWP. UL usable PRBs may refer to UL subband frequency resources within an initial UL BWP. DL usable PRBs may refer to DL subband frequency resources within an initial DL BWP. Hereinafter, SBFD UL subband may be replaced with UL usable PRBs). When there are both legacy UEs (1220) and SBFD-aware UEs (1210), when setting up an RO or RO group, the location of the time and frequency resources of the RO can be determined by considering SBFD and non-SBFD. The settings and methods applied to the RO below can be applied in the same way to the RO group.

[0450] A. RO Configuration and Conflicts in SBFD DL Subbands

[0451] Legacy RO can be understood as a resource that legacy UEs and SBFD-aware UEs can use for PRACH transmissions, and SBFD dedicated RO can be understood as a resource that only SBFD-aware UEs can use for PRACH transmissions. SBFD dedicated RO may also be simply referred to as SBFD RO below.

[0452] The following two methods can be proposed as ways to configure legacy RO and SBFD-dedicated RO.

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

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

[0455] Referring to FIG. 14, it can be seen that RO1 and RO2 can be set at different frequencies by separate RO settings. For example, the ROs can be set by two separate RACH settings. For convenience, let's assume that the two separate RACH settings are the legacy RACH setting and the additional RACH setting. The legacy RACH setting can be described as a RACH setting that can be interpreted by both the legacy UE and the SBFD-cognitive UE, and the additional RACH setting can be a RACH setting that can be interpreted only by the SBFD-cognitive UE. In this case, RO1 can be set by the additional RACH setting, and RO2 can be set by the legacy RACH setting. An SBFD-only RO set on a non-SBFD symbol can be invalidated.

[0456] Secondly, a method can be used in which legacy ROs and SBFD-only ROs are supported through a single RO configuration. A configuration in which legacy ROs and SBFD-only ROs are configured simultaneously can be referred to as a shared RO configuration or a single RACH configuration. Through the single RACH configuration, legacy UEs and SBFD-aware UEs can receive the location of the RO together.

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

[0458] Referring to Fig. 15, the RO of the non-SBFD slot and the RO of the SBFD slot can be set to the same frequency resource. When a shared RO setting is used, the SBFD-aware UE can receive the location of the RO together with the legacy UE.

[0459] For convenience of explanation, using a single RACH setting is referred to as RACH setting option 1, and using two separate RACH settings is referred to as RACH setting option 2.

[0460] In RACH setting option 1, a RACH setting (e.g., RO setting) is performed based on the existing parameters of a single RACH setting, and the existing parameters can be extended / added / changed for an SBFD-cognitive terminal.

[0461] In RACH configuration option 2, a 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 can be described as a RACH configuration that can be interpreted by both legacy UEs and SBFD-aware UEs, and the additional RACH configuration can be described as a RACH configuration that can be interpreted only by SBFD-aware UEs.

[0462] An SBFD-aware UE can support both RACH configuration option 1 and RACH configuration option 2. Enabling both options simultaneously for a single UE may not be supported.

[0463] An SBFD-aware UE can perform PRACH transfers through the ROs of the SBFD slot and UL slot. A legacy UE can perform PRACH transfers through the ROs of the flexible slot (which can be used as an SBFD slot or a non-SBFD slot) and UL slot.

[0464] If both RACH configuration options 1 and 2 are supported by the UE, signaling from a higher layer (e.g., RRC) may be performed to inform the UE which RACH configuration option is being used.

[0465] Case 1: When SBFD is applied to the DL slot

[0466] FIG. 16 illustrates an example in which an 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. 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.

[0467] Referring to Fig. 16, the following four methods can be applied.

[0468] 1) When shared RO settings are applied: From the perspective of the legacy UE, since the SBFD slot is a DL slot, only the ROs in the non-SBFD symbol are valid. From the perspective of the SBFD-aware terminal, all ROs set in the SBFD / non-SBFD slots can be valid if they satisfy the RO validity rules.

[0469] 2) When separate RO settings are applied: gNB sets the RO for the SBFD-aware UE in the SBFD slot / UL slot as RO setting 1 (e.g., additional RACH setting) and sets the RO for the SBFD-aware terminal and legacy UE in the UL slot as RO setting 2 (e.g., legacy RACH setting).

[0470] 3) If SBFD does not require an RO for SBFD-aware UEs, legacy RACH settings alone may be sufficient.

[0471] 4) If the SBFD-aware UE has UL latency or UL coverage issues: An SBFD-only RO may be assigned to the SBFD slot and / or UL slot with a separate RO configuration.

[0472] Case 2: When SBFD is applied to a flexible slot

[0473] FIG. 17 illustrates an example in which an SBFD is applied to all flexible slots in a resource including flexible slots according to one embodiment of the present disclosure. A slot treated as an SBFD slot by an SBFD-aware UE is a case where it is treated as a flexible (F) slot by a legacy UE.

[0474] When a shared RO configuration is applied: Following the existing RO configuration, the base station (e.g., gNB) configures ROs in the flexible slot and UL slot. Since the SBFD slot is treated as a flexible slot from the perspective of the legacy UE, ROs can be configured in both the SBFD slot and the non-SBFD slot by the shared RO configuration. In the case of a shared RO configuration, it should be considered that an SBFD-aware UE can perform a PRACH transmission to the RO of the SBFD UL subband.

[0475] Where separate RO settings are applied: The base station may set an RO for SBFD-aware UEs in the SBFD slot and / or UL slot by RO setting 2 (e.g., additional RACH setting) and set an RO for legacy UEs in the flexible slot (SBFD slot) and / or UL slot by RO setting 1 (e.g., legacy RACH setting). In this case, for RO setting 1 and RO setting 2, the base station may set the RO only in the SBFD UL subband of the flexible slot to account for SBFD-aware UEs. However, if the RO is set to overlap with resources outside the SBFD UL subband according to RO setting 1, the SBFD-aware UE may follow the RO setting of RO setting 2.

[0476] When supported by a base station to allow legacy UEs to perform PRACH transmissions using only the ROs assigned to non-SBFD slots: The base station sets all flexible slots to DL before SBFD is applied. Subsequently, ROs can be set in the same way as in Case 1, where there are no flexible slots. That is, through separated ROs, SBFD-aware UEs can use all ROs assigned to SBFD slots and UL slots, while legacy UEs can use only the ROs assigned to UL slots.

[0477] Case 3: When part of the SBFD is applied to a DL slot or a flexible slot

[0478] FIG. 18 illustrates an example in which an 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 an SBFD-aware UE are treated as DL slots or flexible slots by a legacy UE. An RO configuration can be set by combining Case 1 and Case 2.

[0479] Now, a method and apparatus for determining the number of repetitions of a PRACH preamble transmission in relation to a random access process by a terminal in a wireless communication system having different types of random access opportunities according to the present disclosure will be described.

[0480] In the following, legacy RO refers to the RO prior to the introduction of SBFD.

[0481] An additional RO may be defined as follows according to the RACH configuration options. The aforementioned shared RO configuration may be referred to as RACH configuration option 1 and uses a legacy RO configuration. When RACH configuration option 1 is applied or configured, the additional RO may mean an configured RO that includes at least one SBFD symbol configured as a downlink by tdd-UL-DL-ConfigurationCommon.

[0482] The aforementioned searate RO configuration may be referred to as RACH configuration option 2 and uses legacy RACH configuration and additional RACH configuration. When RACH configuration option 2 is applied or configured, additional RO may refer to the RO configured by the additional RACH configuration.

[0483] The RO group to support PRACH iteration can be provided with only legacy ROs or only additional ROs. In this case, for RACH setting option 1, a legacy RO group (an RO group consisting only of legacy ROs) and an additional RO group (an RO group consisting only of additional ROs) can be configured. For RACH setting option 2, if ROs are configured by the legacy RACH setting, only the legacy RO group is configured, and if ROs are configured by the additional RACH setting, only the additional RO group is configured.

[0484] If other RO group types are selectable, it is necessary to determine which RO group type to select, whether to perform multiple PRACH transmissions or single PRACH transmissions, and what conditions or settings / instruction methods should be introduced for such operations. For example, in a wireless communication system where different types of ROs may coexist, it is necessary to define a method for determining the number of Message 1 repetitions that can be applied to the current random access procedure.

[0485] In the following, SBFD is described as an example of an additional RO, but is not limited thereto. For example, an additional RO is defined for RACH adaptation in network energy saving (NES), and an RO type selection process may be included. In this case, if the NES RO is activated by signaling such as DCI, either the NES RO or the legacy RO may be selected.

[0486] Specific embodiments of the present disclosure

[0487] As described above, when an RO group to support PRACH repetition is given as either legacy ROs only or additional ROs only, in the case of RACH setting option 1, a legacy RO group (in other words, an RO group consisting only of legacy ROs) and an additional RO group (in other words, an RO group consisting only of additional ROs) can be configured. In the case of RACH setting option 2, if the RO is configured with a legacy RACH setting, only a legacy RO group is configured, and if the RO is configured with an additional RACH setting, only an additional RO group is configured.

[0488] Conventional standard specifications do not specify how to perform random access processes during RO-type switching, such as PRACH repetition or how to control PRACH transmission power.

[0489] Considering these points, a method must be determined regarding which RO group type to select when different RO group types are given, whether the RO group type should be switched if necessary, and when the switching should occur if RO group type switching is introduced. To support this, the related operations and parameters are described below.

[0490] In the following, the term RO group type may be replaced with the term RO type. When PRACH repeated transmission is configured, PRACH is transmitted in units of RO groups, which are groups of ROs, and all ROs included in such RO groups may have the same RO type. Therefore, in this specification, RO group type and RO type may be used or interpreted as having the same meaning.

[0491] N preamble rep For a PRACH transmission with preamble repetitions, the set consists of N that are temporally consecutive, use the same frequency resource, and are associated with one or more identical SS / PBCH block indices. preamble rep It consists of valid PRACH opportunities, and each SS / PBCH block index is associated with the same preamble indices in all valid PRACH opportunities within the set.

[0492] Within a time period, N preamble rep N for PRACH transmissions with n preamble repetitions preamble repFor a set(s) of valid PRACH opportunities, the first valid PRACH opportunity of the first set is the first valid PRACH opportunity. The first valid PRACH opportunity of subsequent sets is determined according to the ordering of the valid PRACH opportunities. For example, first, for frequency multiplexing PRACH opportunities, in ascending order of frequency resource indices, and next, for time multiplexing PRACH opportunities, in ascending order of time resource indices.

[0493] A base station may set specific PRACH resources (e.g., specifying a preamble start index and a total number) to inform a terminal that a specific single feature or a combination of specific features is supported, and the terminal intending to use or request a specific feature and / or a combination of specific features may be configured to select one of the preamble indices in the area allocated for the desired specific feature and / or combination of specific features during the RACH process and transmit a PRACH preamble. RRC parameters for this operation may be defined, for example, in the standard specifications “FeatureCombinationPreambles” and “FeatureCombination”.

[0494] FIG. 19 illustrates RRC information elements for RACH operation.

[0495] Referring to Fig. 19, the base station can additionally assign a RACH configuration through AdditionalRACH-Config-r17 in addition to the RACH-ConfigCommon assigned to the existing BWP-UplinkCommon. Consequently, terminals up to Rel-16 that cannot read AdditionalRACH-Config-r17 perform the RACH process by looking at the RACH-ConfigCommon assigned to the existing BWP-UplinkCommon, but terminals from Rel-17 onwards that can read AdditionalRACH-Config-r17 perform the RACH process by checking the RACH-ConfigCommon assigned to AdditionalRACH-Config-r17 in addition to the RACH-ConfigCommon assigned to the existing BWP-UplinkCommon.

[0496] In addition, one or more of the FeatureCombinationPreambles described above may be configured in the RACH-ConfigCommon assigned to the existing BWP-UplinkCommon, and one or more of the FeatureCombinationPreambles described above may also be configured in the RACH-ConfigCommon assigned to AdditionalRACH-Config-r17.

[0497] The relevant RRC parameters are as follows.

[0498] Table 14 illustrates the information element (IE) BWP-UplinkCommon, which is used to set the common parameters of the uplink BWP. These parameters are "cell specific," and the network ensures the necessary alignment with the corresponding parameters of other UEs. The common parameters of the initial BWP of the primary cell (PCell), excluding additionalRACH-perPCI-ToAddModList and additionalRACH-perPCI-ToReleaseList, are provided via system information. For all other serving cells, the network provides the common parameters via dedicated signaling.

[0499] [Table 14]

[0500]

[0501]

[0502] In Table 14, rsrp-ThresholdMsg1-RepetitionNum2, rsrp-ThresholdMsg1-RepetitionNum4, and rsrp-ThresholdMsg1-RepetitionNum8 are thresholds used by the UE to determine whether to select resources representing Msg1 iteration counts of 2, 4, or 8 in this BWP. These values ​​apply to all BWPs and all RACH configurations. For a given MSG1 iteration count, this field is mandatory if both a set of random access resources with an MSG1 iteration instruction associated with this MSG1 iteration count and a set of random access resources without an MSG1 iteration instruction are configured in the BWP, or if both a set of random access resources with an MSG1 iteration instruction associated with this MSG1 iteration count and a set of random access resources with an MSG1 iteration instruction associated with a lower iteration count are configured in the BWP; otherwise, this field is absent.

[0503] In Table 14, preambleTransMax-Msg1-Repetition is the maximum number of MSG1 iterations (2, 4, and 8) performed before switching to a higher number of iterations. This field applies only when two or more iterations are set in the shared RO. Without this field, it is not possible to switch from a lower number of iterations to a higher number of iterations.

[0504] Table 15 illustrates the information element RACH-ConfigCommon, which is used to define cell-specific random access parameters.

[0505] [Table 15]

[0506]

[0507]

[0508] The information element FeatureCombinationPreambles in Table 16 associates a set of preambles with feature combinations. For parameters that may be provided in this information element, the UE applies this field value when performing random access using the preambles of this featureCombinationPreambles, and otherwise applies the corresponding value determined by the applicable Need Code (e.g., Need S). In a specific BWP, there may be at most one set of preambles associated with a given feature combination per MSG1 iteration per RA type (e.g., 4-step RACH or 2-step RACH).

[0509] [Table 16]

[0510]

[0511] Table 17 shows an example of the information element RACH-ConfigDedicated.

[0512] [Table 17]

[0513]

[0514] The PRACH repetition operation can be performed as follows.

[0515] 1> If no contention-free random access resources are provided for this random access procedure, and the BWP selected for the random access procedure consists of a set of random access resources with msg1-Repetitions set to true and a set of random access resources with msg1-Repetitions not set to true:

[0516] 2> If the random access resource set associated with the selected BWP for the random access procedure is set to Msg1 iteration count 8, and the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum8:

[0517] 3> Assume that Msg1 iterations are applicable and that the number of Msg1 iterations applicable to the current random access procedure includes 8.

[0518] 2> If the random access resource set associated with the selected BWP for the random access procedure is set to Msg1 iteration count 4, and the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum4:

[0519] 3> Assume that Msg1 iterations are applicable and that the number of Msg1 iterations applicable to the current random access procedure includes 4.

[0520] 2> If the random access resource set associated with Msg1 iteration count 2 is set for the selected BWP for the random access procedure, and the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum2:

[0521] 3> Assume that Msg1 iterations are applicable and that the number of Msg1 iterations applicable to the current random access procedure includes 2.

[0522] 2> Otherwise, if the RSRP based on downlink path loss is not less than the set rsrp-ThresholdMsg1-RepetitionNumX:

[0523] 3> Assume that the Msg1 iteration cannot be applied to the current random access procedure.

[0524] 1> Otherwise, if the BWP selected for the random access procedure is configured only with random access resources where msg1-Repetitions is set to true:

[0525] 2> Assume that the Msg1 iteration is applicable to the current random access procedure.

[0526] 2> If one or more of rsrp-ThresholdMsg1-RepetitionNumX are set:

[0527] 3> If rsrp-ThresholdMsg1-RepetitionNum8 is set and the RSRP based on downlink path loss is less than rsrp-ThresholdMsg1-RepetitionNum8;

[0528] 4> The number of Msg1 iterations applicable to the current random access procedure is set to 8.

[0529] 3> If rsrp-ThresholdMsg1-RepetitionNum4 is set and the RSRP based on downlink path loss is less than rsrp-ThresholdMsg1-RepetitionNum4:

[0530] 4> Assume that the number of Msg1 iterations applicable to the current random access procedure is 4.

[0531] 3> If rsrp-ThresholdMsg1-RepetitionNum2 is set and the RSRP based on downlink path loss is less than rsrp-ThresholdMsg1-RepetitionNum2:

[0532] 4> Assume that the number of Msg1 iterations applicable to the current random access procedure includes 2.

[0533] 3> Otherwise, if the RSRP based on downlink path loss is not less than the set rsrp-ThresholdMsg1-RepetitionNumX:

[0534] 4> Assume that the number of Msg1 iterations applicable to the current random access procedure is the lowest number of Msg1 iterations set for this BWP.

[0535] 2> Otherwise (rsrp-ThresholdMsg1-RepetitionNumX is not set):

[0536] 3> Assume that the number of Msg1 iterations applicable to the current random access procedure is the number of Msg1 iterations set for this BWP.

[0537] The process of performing a PRACH iteration to the next largest number of iterations when the transmission of the PRACH iteration to the previously selected number of iterations fails is as follows.

[0538] In the following, preambleTransMax-Msg1-Repetition refers to the maximum number of random access preamble transmissions, given as the number of Msg1 iterations before switching to the next available Msg1 iteration with a higher number of iterations.

[0539] 1> If the ra-ResponseWindow configured in RACH-ConfigCommon expires and a random access response containing a random access preamble identifier matching the transmitted PREAMBLE_INDEX is not received:

[0540] 2> Received random access response is considered unsuccessful.

[0541] 2> Increase PREAMBLE_TRANSMISSION_COUNTER by 1.

[0542] 2> If PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax + 1:

[0543] 3> When a random access preamble is transmitted from SpCell:

[0544] 4> Instruct the upper layer to solve the random access problem;

[0545] 4> If this random access procedure is triggered for an SI request:

[0546] 5> The random access procedure is considered not to have been successfully completed.

[0547] 3> Otherwise, if the random access preamble is transmitted from the secondary cell (SCell):

[0548] 4> The random access procedure is considered not to have been successfully completed.

[0549] 2> If the random access procedure is not completed:

[0550] 3> If a random access preamble is transmitted through iterations and no contention-free random access resource is provided for this random access procedure or for the random access resource for the SI request:

[0551] 4> PREAMBLE_TRANSMISSION_COUNTER = [preambleTransMax-Msg1-Repetition] + 1 if; or

[0552] 4> If PREAMBLE_TRANSMISSION_COUNTER = 2 × [preambleTransMax-Msg1-Repetition] + 1:

[0553] 5> If a random access resource set is available that is set to the same prach-ConfigurationIndex and associated with a higher Msg1 iteration count, having the same feature or combination of features as the current random access resource set:

[0554] 6> For this random access procedure, select the set of random access resources associated with the next highest Msg1 iteration count that has the same feature or combination of features;

[0555] 6> Initialize the startPreambleForThisPartition, numberOfPreamblesPerSSB-ForThisPartition, ssb-SharedRO-MaskIndex, and numberOfRA-PreamblesGroupA parameters for the random access procedure according to the values ​​set by RRC for the selected set of random access resources.

[0556] <RO 그룹 선택 방법>

[0557] 1. Method for the network to determine / configure the RO group type.

[0558] In relation to this method, parameters that the gNB sets or directs to determine the RO group type may be introduced. For example, the above parameters may be included in the BWP-UplinkCommon information element. Regarding the parameters for setting or directing the RO type and RO group type in RO selection and RO group type selection, a single parameter may be used commonly, or they may be given as separate parameters to be set differently.

[0559] Depending on the RO group type specified by the value set / instructed by the above parameter, the value of the parameter related to PRACH repetition, such as msg1-RepetitionNum, msg1-RepetitionTimeOffsetROGroup, rsrp-ThresholdMsg1-RepetitionNum2, rsrp-ThresholdMsg1-RepetitionNum4, rsrp-ThresholdMsg1-RepetitionNum8, preambleTransMax-Msg1-Repetition, etc., may be set / instructed.

[0560] For example, in RACH configuration Option 1, it is assumed that one parameter can be commonly used to set / indicate the RO type in RO selection and to set / indicate the RO group type in RO group type selection.

[0561] If the above parameter value is provided along with values ​​such as rsrp-ThresholdMsg1-RepetitionNum2, rsrp-ThresholdMsg1-RepetitionNum4, rsrp-ThresholdMsg1-RepetitionNum8, it can be used to select an RO group type. If an additional RO group is set / instructed, PRACH repeated transmissions are possible through the additional RO group, and the number of PRACH repetitions can be determined based on the RSRP of the downlink pathloss reference measurement value. If parameters such as ThresholdMsg1-RepetitionNum2, rsrp-ThresholdMsg1-RepetitionNum4, rsrp-ThresholdMsg1-RepetitionNum8 are not provided, the above parameter value can be set / instructed for the selection of an RO for a single transmission.

[0562] For example, in RACH setting option 2, if the above parameter is applied, it can be said that gNB sets / instructs RO resources configured with legacy RACH settings or additional RACH settings.

[0563] In this case, the above parameter value can set / indicate the RO type or RO group type of the first transmission. If PRACH repetition is supported, parameters such as msg1-RepetitionNum, msg1-RepetitionTimeOffsetROGroup, rsrp-ThresholdMsg1-RepetitionNum2, rsrp-ThresholdMsg1-RepetitionNum4, rsrp-ThresholdMsg1-RepetitionNum8, and preambleTransMax-Msg1-Repetition can be set in the legacy RACH settings and additional RACH settings, respectively.

[0564] 2. Method by which the UE determines the RO group type.

[0565] Regarding RACH resource selection, when initiating the CBRA RACH procedure for a UE that recognizes SBFD, the UE may select one type of RO, either a legacy RO or an additional RO, based on specific specified / configured conditions / priorities, unless there are additional instructions from the network.

[0566] In the case of a PRACH transfer retry in a single RACH procedure, after attempting RACH a specific (configured) number of times in SBFD RACH opportunities, the UE can switch to legacy RACH opportunities.

[0567] In this method, the UE can directly perform the selection of the RO group type. When the UE selects the RO type, the UE can make the selection independently of the gNB. Alternatively, specific priorities and / or specific conditions are provided by the gNB, and the terminal can select an RO group type that satisfies these conditions.

[0568] Regarding priority, parameters that can be set / directed by network configuration may be introduced, and specific conditions may be given for rsrp-ThresholdSSB (e.g., rsrp-ThresholdSSB-ROtype) related to RO group type selection. rsrp-ThresholdSSB-ROtype can be used for RO selection during a single transfer operation and / or for RO group selection during a PRACH iteration operation. Parameters related to the respective rsrp-ThresholdSSB may be introduced for a single transfer and a PRACH iteration. For example, they may be included in the BWP-UplinkCommon information element, FeatureCombinationPreambles information element, etc.

[0569] For example, the UE can execute a single PRACH transfer and a PRACH iteration within a single RO type. For instance, after an RO is selected via a single PRACH transfer, the UE can determine whether to apply a PRACH iteration and the number of iterations within the same RO.

[0570] [Table 18]

[0571]

[0572]

[0573] In Table 18, rsrp-ThresholdSSB-ROtype-r19 is an example of an RO type RSRP (Reference Signal Received Power) threshold, which is a threshold used to select a RACH opportunity (random access channel occasion: RO) type.

[0574] [Table 19]

[0575]

[0576] In Table 19, rsrp-ThresholdSSB-ROtype-r19 is an example of an RO type RSRP (Reference Signal Received Power) threshold, which is a threshold used to select a RACH opportunity (random access channel occasion: RO) type.

[0577] Assuming the UE selects an RO group type, the number of PRACH iterations may vary depending on each RO group type. For example, the maximum number of PRACH iterations configurable for additional ROs may differ from the maximum number of PRACH iterations configurable for legacy ROs. This takes into account that if gNB-gNB CLI (cross-link interference) significantly affects SBFD symbols / slots, even a large number of PRACH iterations may not significantly affect the PRACH detection performance of the gNB.

[0578] Depending on the RO group type (RO type), the values ​​of the SSB-RSRP threshold, which serve as the criteria for selecting the number of PRACH iterations, may also vary.

[0579] Alt 1: Regardless of the RO group type, the parameter values ​​msg1-RepetitionNum, rsrp-ThresholdMsg1-RepetitionNum2, rsrp-ThresholdMsg1-RepetitionNum4, and rsrp-ThresholdMsg1-RepetitionNum8 are used together. In other words, the same value is given by gNB.

[0580] Alt 2: Depending on the RO group type, the parameters msg1-RepetitionNum, rsrp-ThresholdMsg1-RepetitionNum2, rsrp-ThresholdMsg1-RepetitionNum4, and rsrp-ThresholdMsg1-RepetitionNum8 are introduced as respective parameters to set / instruct whether the same or different values ​​can be used.

[0581] For example, in future wireless communication systems, msg1-RepetitionNum-r19, rsrp-ThresholdMsg1-RepetitionNum2-r19, rsrp-ThresholdMsg1-RepetitionNum4-r19, rsrp-ThresholdMsg1-RepetitionNum8-r19, etc. may be introduced.

[0582] Depending on the RO group type (RO type), the number of candidate values ​​for the number of PRACH iterations may also differ. For example, if msg1-RepetitionNum-r18 supports 2, 4, and 8, msg1-RepetitionNum-r19 may only support 2 and 4.

[0583] Let preambleTransMax-Msg1-Repetition be the maximum number of PRACH repetitions that can be transmitted before RO group switching; this parameter may be given the same or different values ​​for different types of RO groups.

[0584] Table 20 shows an example where RSRP thresholds related to the number of PRACH iterations (message 1 iterations) are provided according to the RO group type (RO type).

[0585] [Table 20]

[0586]

[0587]

[0588] Table 21 shows an example where the number of PRACH repetitions (number of message 1 repetitions) and time offset are provided according to the RO group type (RO type).

[0589] [Table 21]

[0590]

[0591] 3. How the RO group type is determined as an additional RO group or a legacy RO group.

[0592] gNB and UE can decide to select additional RO groups (or legacy RO groups) when selecting an RO group type. For example, they can prioritize specific RO group types and define details related to standard specifications.

[0593] Depending on the specified RO group type, the values ​​of parameters related to PRACH repetition, such as msg1-RepetitionNum, msg1-RepetitionTimeOffsetROGroup, rsrp-ThresholdMsg1-RepetitionNum2, rsrp-ThresholdMsg1-RepetitionNum4, rsrp-ThresholdMsg1-RepetitionNum8, etc., may be set / instructed.

[0594] The aforementioned methods can be applied to the selection of the initial RO group type. Newly introduced parameters related to other RO group types can also be applied when performing RO group switching.

[0595] 4. A method for determining the number of PRACH iterations, including a single PRACH transmission, when different types of RO types are given.

[0596] PRACH transmission can be performed through a single PRACH transmission or multiple PRACH transmissions having a specific number of repetitions.

[0597] If other types of ROs exist, one type of RO can be selected when performing a single PRACH transmission. The other types of ROs may be legacy ROs or additional ROs for SBFD operations. The conditions applied when selecting the RO type may be RSRP threshold parameters related to RSRP or SSB (e.g., rsrp-Threshold_ROtype, rsrp-Threshold_SSB_ROtype) and may be provided by the gNB.

[0598] If other types of ROs exist, PRACH iterative transmission can be performed. The other types may be legacy ROs and additional ROs for SBFD operations. In this case, the group of other types of ROs configured for PRACH iterative transmission may be a legacy RO group (an RO group consisting only of legacy ROs) or an additional RO group (an RO group consisting only of additional ROs).

[0599] For example, in the case of the conventional technology (NR's Rel 18 standard specification), the msg1-RepetitionNum of the legacy RO is 3, and N can be N1, N2, N3 (e.g., 2, 4, 8), and the rsrp-ThresholdMsg1-RepetitionNumberN, which determines a single PRACH or PRACH to be repeated N times, can be given as rsrp-ThresholdMsg1-RepetitionNumber2, rsrp-ThresholdMsg1-RepetitionNumber4, rsrp-ThresholdMsg1-RepetitionNumber8.

[0600] For example, the additional RO's msg1-RepetitionNum_rel19 can be set to 3, and N can be N11, N12, N13 (e.g., 2, 4, 8), and the rsrp-ThresholdMsg1-RepetitionNumberN_rel19, which determines a single PRACH or PRACH repeated N times, can be given as rsrp-ThresholdMsg1-RepetitionNumber2_rel19, rsrp-ThresholdMsg1-RepetitionNumber4_rel19, rsrp-ThresholdMsg1-RepetitionNumber8_rel19.

[0601] In future standard specifications, threshold values ​​related to the number of iterations may differ from the above. For example, the number of iterations may not be the same for the additional RO and the legacy RO, and some or all values ​​may differ. For example, the number of iterations applied to the additional RO may be 16, 32, etc. For example, the number of iterations applied to the additional RO may be one or more, and three or more may be possible.

[0602] In the following process, depending on the RO type to which PRACH is transmitted, a UL BWP corresponding to the RO setting (e.g., when a legacy RO is selected) or a UL usable PRB (e.g., when an additional RO is selected) may be selected.

[0603] If a random access resource set associated with Msg1 iteration count 8 is set for the selected BWP (or UL available PRB) in the random access procedure, and the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum8 (or rsrp-ThresholdMsg1-RepetitionNum8_rel19): assume that Msg1 iteration is applicable and that 8 is included in the number of Msg1 iterations applicable to the current random access procedure.

[0604] If a random access resource set associated with Msg1 iteration count 4 is set for the BWP (or UL available PRB) selected for the random access procedure, and the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum4 (or rsrp-ThresholdMsg1-RepetitionNum4_rel19): assume that Msg1 iteration is applicable and that 4 is included in the number of Msg1 iterations applicable to the current random access procedure.

[0605] For a random access procedure, a set of random access resources associated with Msg1 iteration count 2 is set for the selected BWP (or UL available PRB), and the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum2 (or rsrp-ThresholdMsg1-RepetitionNum2_rel19): assume that Msg1 iteration is applicable and that 2 is included in the number of Msg1 iterations applicable to the current random access procedure.

[0606] If the RSRP of the downlink path loss criterion is not less than the set rsrp-ThresholdMsg1-RepetitionNumX (or rsrp-ThresholdMsg1-RepetitionNumX_rel19): assume that Msg1 iterations are not applied to the current random access procedure.

[0607] When parameters related to the legacy RO group and the additional RO group are set as described above, single / multiple PRACH transmissions can be determined by the following method or procedure.

[0608] Case 1) The relevant rsrp-threshold value for RO type selection is set / instructed by the gNB. The relevant rsrp-threshold may reuse the threshold for RO type selection when there is no iteration, or may be newly set for iteration. Once RO selection is complete, it is decided whether to perform a single PRACH transfer or multiple PRACH transfers with N iterations based on the selected / selected RO type.

[0609] In this case, the following procedure may be applied. For RACH configuration option 1, the same msg1-RepetitionNum may be given to the additional RO group and the legacy RO group. For RACH configuration option 2, separate parameters (e.g., msg1-RepetitionN_rel19, msg1-RepetitionNumN) may be applied to the additional RO group and the legacy RO group.

[0610] Case 1-1)

[0611] Step 1) Set / instruct the relevant rsrp-Threshold from the gNB for RO type selection. For example, rsrp-Threshold_ROtype (or it may be denoted as sbfd-RSRP-ThresholdRO-Type) can be set / instructed from the gNB.

[0612] Step 2) Once the RO type is determined, apply the rsrp-ThresholdMsg1-RepetitionNumberN set / instructed for each RO type to determine whether to perform a single PRACH transmission, or if to perform RPACH repetition, how many times to repeat the transmission. For example, if the RO type is determined to be a legacy RO (e.g., an RO type associated with the RO of a non-subband full-duplex (non-SBFD) time resource), apply rsrp-ThresholdMsg1-RepetitionNumberN (e.g., rsrp-ThresholdMsg1-RepetitionNum2, rsrp-ThresholdMsg1-RepetitionNum4, rsrp-ThresholdMsg1-RepetitionNum8), and if the RO type is determined to be an additional RO (e.g., an RO type associated with the RO of an SBFD time resource), apply rsrp-ThresholdMsg1-RepetitionNumberN_rel19 (e.g., sbfd-RSRP-ThresholdMsg1-RepetitionNum2, sbfd-RSRP-ThresholdMsg1-RepetitionNum4, Apply sbfd-RSRP-ThresholdMsg1-RepetitionNum8).

[0613] Figure 20 shows a specific example of applying Case 1-1.

[0614] Referring to FIG. 20, the terminal receives i) a 'RO type RSRP threshold' which is a threshold used by the (SBFD aware) UE for choosing a RACH occasion type, and ii) 'Msg1 repetition number RSRP thresholds' which are a threshold used by the UE for determining whether to select resources indicating Msg1 repetition number 2, 4, or 8, which is a threshold used by the terminal for determining whether to select resources indicating Msg1 repetition number 2, 4, or 8 (S201).

[0615] The RO type RSRP threshold (which can be provided, for example, through a parameter such as sbfd-RSRP-ThresholdRO-Type) can be used, for example, for the initial PRACH preamble transmissions.

[0616] The Msg1 repetition count RSRP threshold may be provided by at least one of parameters such as rsrp-ThresholdMsg1-RepetitionNum2, rsrp-ThresholdMsg1-RepetitionNum4, and rsrp-ThresholdMsg1-RepetitionNum8 for the first RO type, and by at least one of parameters such as sbfd-RSRP-ThresholdMsg1-RepetitionNum2, sbfd-RSRP-ThresholdMsg1-RepetitionNum4, and sbfd-RSRP-ThresholdMsg1-RepetitionNum8 for the second RO type.

[0617] Here, the first RO type is an RO type associated with the RO of a non-subband full duplex (non-SBFD) time resource, and the second RO type may be an RO type associated with the RO of an SBFD time resource.

[0618] For example, the first RO type may be an RO type associated with PRACH opportunities that are considered uplink in a random access process and contain only symbols designated as uplink or flexible by tdd-UL-DL-ConfigurationCommon, and the second RO type may be an RO type associated with PRACH opportunities that start at an SBFD symbol and end at a non-SBFD symbol, or contain at least one SBFD symbol designated as downlink by tdd-UL-DL-ConfigurationCommon while being in RBs (resource blocks) in both active UL BWP and UL subband.

[0619] According to the embodiment, it may be expressed that the first RO type is related to the legacy RO and the second RO type is related to the SBFD RO.

[0620] The terminal selects a specific RO type based on the above RO type RSRP threshold (S202). For example, the specific RO type may be the second RO type.

[0621] For example, the terminal can select the specific RO type based on the comparison result of the RSRP of the RO type RSRP threshold and the downlink pathloss reference RSRP.

[0622] According to an embodiment, the RO type RSRP threshold is set, and if the RSRP based on downlink path loss is greater than the RO type RSRP threshold (above), a second RO type can be selected / set. Alternatively, according to an embodiment, if the RO type RSRP threshold is set and the RSRP based on downlink path loss is less than the RO type RSRP threshold (below), a second RO type can be selected / set. Which of these two embodiments is used can be determined by the base station. In other words, the base station can provide the terminal with information indicating how the SBFD-UE selects the RACH opportunity (RO) type using sbfd-RSRP-ThresholdRO-Type, along with the RO type RSRP threshold.

[0623] The above downlink path loss criteria can be, for example, the SSB (Synchronization Signal Block) or CSI-RS (Channel State Information-Reference Signal).

[0624] After that, the terminal determines the number of Msg1 iterations applicable to the current random access procedure based on the Msg1 iteration count RSRP threshold associated with the specific RO type (S203).

[0625] In other words, the terminal first determines / judges / sets a specific RO type among the first RO type and the second RO type based on the RO type RSRP threshold, and determines / assumes the number of Msg1 iterations that can / are applied to the current random access procedure based on the Msg1 iteration count RSRP threshold(s) associated with the specific RO type.

[0626] For example, based on the comparison result between the RSRP of the downlink path loss criterion and the Msg1 iteration count RSRP threshold related to the specific RO type, it is assumed that the Msg1 iteration count applicable to the current random access process includes a specific value (e.g., 2, 4 and / or 8).

[0627] For example, if the RSRP threshold for the number of Msg1 repetitions, sbfd-RSRP-ThresholdMsg1-RepetitionNum8, is set and the RSRP of the downlink path loss criterion is less than sbfd-RSRP-ThresholdMsg1-RepetitionNum8, the terminal determines / assumes that 8 is included in the number of Msg1 repetitions that can be applied to the current random access procedure. This involves determining / assuming the number of Msg1 repetitions that can be applied / applied to the current random access procedure by comparing the RSRP of the downlink path loss criterion (e.g., SSB), which indicates the downlink channel state, with a threshold related to a specific number of Msg1 repetitions.

[0628] When the RSRP threshold for the number of repetitions of Msg1, sbfd-RSRP-ThresholdMsg1-RepetitionNum4, is set and the RSRP of the downlink path loss criterion is less than sbfd-RSRP-ThresholdMsg1-RepetitionNum4, the terminal determines / assumes that 4 is included in the number of repetitions of Msg1 that can be applied to the current random access procedure.

[0629] When the RSRP threshold for the number of repetitions of Msg1, sbfd-RSRP-ThresholdMsg1-RepetitionNum2, is set and the RSRP of the downlink path loss criterion is less than sbfd-RSRP-ThresholdMsg1-RepetitionNum2, the terminal determines / assumes that 2 is included in the number of repetitions of Msg1 that can be applied to the current random access procedure.

[0630] The number of repetitions of the above Msg1 may be related to the number of repetitions of the preamble transmission of the random access procedure.

[0631] The aforementioned RO type RSRP threshold and Msg1 repetition count RSRP threshold can be received through an RRC (radio resource control) information element (IE). For example, the base station (network) can provide the RO type RSRP threshold and Msg1 repetition count RSRP threshold to the terminal through a BWP-UplinkCommon IE used to set common parameters of the uplink BWP (bandwidth part).

[0632] In the method of Fig. 20, 'RO type RSRP threshold' may mean 'information related to / telling / providing about RO type RSRP threshold', and 'Msg1 iteration count RSRP threshold' may mean 'information related to / telling / providing about Msg1 iteration count RSRP threshold'.

[0633] For example, in the aforementioned step S201, receiving the 'RO type RSRP threshold' and the 'Msg1 repetition count RSRP threshold' may mean receiving 'information related to / notifying / providing the RO type RSRP threshold' and 'information related to / notifying / providing the Msg1 repetition count RSRP threshold'. The 'information related to the RO type RSRP threshold' and the 'information related to the Msg1 repetition count RSRP threshold' may be notified or provided to the terminal by the base station (network) through the aforementioned BWP-UplinkCommon IE, for example.

[0634] The present disclosure relates to a terminal that performs a random access process in a situation where ROs configured on SBFD resources and ROs configured on non-SBFD resources are mixed, and the terminal may be an SBFD (subband full duplex) aware terminal.

[0635] According to an embodiment, when a first RO type is selected based on the RO type RSRP threshold, the terminal can determine the number of Msg1 repetitions applicable to a current random access procedure based on the Msg1 repetition count RSRP threshold associated with the first RO type.

[0636] According to an embodiment, when a first RO type is selected based on the RO type RSRP threshold, the terminal may perform a single PRACH (physical random access channel) transmission without repetition.

[0637] In the example of Fig. 20, the case where sbfd-RSRP-ThresholdMsg1-RepetitionNumX and rsrp-ThresholdMsg1-RepetitionNumX (where X is 2, 4, 8) are set was described. If neither sbfd-RSRP-ThresholdMsg1-RepetitionNumX nor rsrp-ThresholdMsg1-RepetitionNumX are set, the terminal can determine / assume that the number of Msg1 repetitions set for the corresponding BWP is the number of Msg1 repetitions applicable to the current random access procedure.

[0638] To briefly summarize the method of FIG. 20, the terminal receives i) an RO type RSRP threshold and ii) Msg1 repetition count RSRP thresholds (S201), selects a specific RO type based on the RO type RSRP threshold (S202), and determines the number of Msg1 repetitions based on the Msg1 repetition count RSRP threshold associated with the specific RO type (S203). In other words, the terminal first selects a specific RO type and then determines the number of Msg1 repetitions associated with that RO type.

[0639] According to the present disclosure, a random access process can be efficiently performed even in a wireless communication system in which SBFD resources and non-SBFD resources (e.g., resources of the existing HD method) are mixed.

[0640] According to the present disclosure, a method for determining the number of message 1 repetitions that can be applied to a current random access procedure in a wireless communication system where SBFD resources can be used is clarified so that no ambiguity occurs between the network and the terminal.

[0641] In addition, according to the present disclosure, the terminal first selects an RO type, and once the RO type is determined, determines the number of repetitions of Message 1 by applying a threshold value set or indicated for the RO type. When a new RO type is introduced to an existing wireless communication system, system flexibility is increased because an optimized threshold value for determining the number of repetitions of Message 1 for the new RO type can be applied while maintaining legacy settings.

[0642] FIG. 21 illustrates the signaling process and operation method between a base station and a terminal.

[0643] Referring to FIG. 21, the base station provides the terminal with RO type RSRP thresholds and Msg1 repetition count RSRP thresholds (S211).

[0644] The terminal first selects an RO type based on the RO type RSRP threshold (S212), and determines / assumes the number of Msg1 iterations that can be applied to the current random access procedure based on the Msg1 iteration count RSRP threshold associated with the RO type (S213).

[0645] The terminal performs repeated transmission of Msg1 (S214). For example, the terminal can repeatedly transmit the PRACH preamble with the number of Msg1 repetitions that can be applied to the current random access procedure.

[0646] Case 2) Select the RO type using the smallest PRACH iteration count from rsrp-ThresholdMsg1-RepetitionNumberN and / or rsrp-ThresholdMsg1-RepetitionNumberN_rel19. Note that in future standard specifications, the threshold values ​​related to the iteration count may differ from the above. For example, the iteration counts for the Additional RO and the Legacy RO may not be the same, and some or all values ​​may differ. For example, the iteration count applied to the Additional RO could be 16, 32, etc. For RACH configuration option 1, the same msg1-RepetitionNum may be given to the Additional RO group and the Legacy RO group. For RACH configuration option 2, separate parameters (e.g., msg1-RepetitionN_rel19, msg1-RepetitionNumN) may be applied to the Additional RO group and the Legacy RO group.

[0647] Case 2-1)

[0648] Step 1) The smallest number of iterations in rsrp-ThresholdMsg1-RepetitionNumberN can be used without receiving separate settings / instructions from gNB for rsrp-Threshold for RO type selection (e.g., rsrp-Threshold_SSB for RO type selection). The smallest number of iterations in rsrp-ThresholdMsg1-RepetitionNumberN and the smallest number of iterations in rsrp-ThresholdMsg1-RepetitionNumberN_rel19 may be the same.

[0649] Step 2) Once the RO type is determined, determine whether to perform a single PRACH transmission or, if RPACH iteration, how many times to repeat transmission based on the parameters set / instructed for each type. If determined to be a legacy RO, apply rsrp-ThresholdMsg1-RepetitionNumberN, and if determined to be an additional RO, apply rsrp-ThresholdMsg1-RepetitionNumberN_rel19.

[0650] Case 2-2)

[0651] Step 1) The smallest number of iterations in rsrp-ThresholdMsg1-RepetitionNumberN_rel19 can be used without receiving separate settings / instructions from gNB for rsrp-Threshold for RO type selection (e.g., rsrp-Threshold_SSB for RO type selection). The smallest number of iterations in rsrp-ThresholdMsg1-RepetitionNumberN and the smallest number of iterations in rsrp-ThresholdMsg1-RepetitionNumberN_rel19 may be the same.

[0652] Step 2) Once the RO type is determined, determine whether to perform a single PRACH transmission or, if RPACH iteration, how many times to repeat transmission based on the parameters set / instructed for each type. If determined to be a legacy RO, apply rsrp-ThresholdMsg1-RepetitionNumberN, and if determined to be an additional RO, apply rsrp-ThresholdMsg1-RepetitionNumberN_rel19.

[0653] Case 2-3)

[0654] Step 1) The smallest value of the number of PRACH repetitions of rsrp-ThresholdMsg1-RepetitionNumberN and the smallest number of the number of PRACH repetitions of rsrp-ThresholdMsg1-RepetitionNumberN_rel19 are given.

[0655] If the measured RSRP value satisfies a single threshold value, the associated RO type is determined.

[0656] If the measured RSRP value satisfies all of the rsrp-ThresholdMsg1-RepetitionNumbers, the RO type is determined by the set / defined conditions or priority.

[0657] The smallest number of repetitions in rsrp-ThresholdMsg1-RepetitionNumberN and the smallest number of repetitions in rsrp-ThresholdMsg1-RepetitionNumberN_rel19 can be the same.

[0658] Step 2) Once the RO type is determined, determine whether to perform a single PRACH transmission or, if RPACH iteration, how many times to repeat transmission based on the parameters set / instructed for each type. If determined to be a legacy RO, apply rsrp-ThresholdMsg1-RepetitionNumberN, and if determined to be an additional RO, apply rsrp-ThresholdMsg1-RepetitionNumberN_rel19.

[0659] For example, if the same PRACH iteration counts of 2, 4, and 8 are assigned to the legacy RO group and the additional RO group during Step 1, rsrp-ThresholdMsg1-RepetitionNumber2 or rsrp-ThresholdMsg1-RepetitionNumber2_rel19 may be used. The two values ​​can be identical. If the two values ​​are different, the RO type is determined by a specific rule. The specific rule may be a set / defined condition or priority.

[0660] For example, during Step 1, the number of PRACH iterations may vary depending on the RO type. For instance, 2, 4, and 8 may be assigned to legacy RO groups, while 4 and 6 may be set / instructed to additional RO groups. In this case, rsrp-ThresholdMsg1-RepetitionNumber2 or rsrp-ThresholdMsg1-RepetitionNumber4_rel19 may be used. The two values ​​may be identical. If the two values ​​are different, the RO type is determined by a specific rule. This specific rule may be a set / defined condition or priority.

[0661] If one or more related rsrp-Thresholds are satisfied in this way, the RO type / RO group type can be set by the following settings / directives / priorities.

[0662] The UE can select the configured RO / RO group type associated with the rsrp-Threshold that has been set to a high value.

[0663] The UE can select the RO / RO group type based on the implementation.

[0664] The UE can select an RO type with a small association period or association pattern period. This can provide an advantage in terms of PRACH latency.

[0665] The UE can select additional RO / RO groups. This can help with early detection, allowing subsequent msg2 / 3 / 4 related transmissions to be performed at SBFD symbols, and can also help with load balancing.

[0666] Case 3) The RO type can be determined by comparing the measured RSRP with all given rsrp-ThresholdMsg1-RepetitionNumberN and rsrp-ThresholdMsg1-RepetitionNumberN_rel19 without limiting it to a specific rsrp-Threshold value. In this case, one or more values ​​may be satisfied for each RO type. For RACH setting option 1, the same msg1-RepetitionNum may be given to the additional RO group and the legacy RO group. For RACH setting option 2, separate parameters (e.g., msg1-RepetitionN_rel19, msg1-RepetitionNumN) may be applied to the additional RO group and the legacy RO group.

[0667] For example, there may be cases such as the following.

[0668] If the measured RSRP is less than rsrp-ThresholdMsg1-RepetitionNumber4 and less than rsrp-ThresholdMsg1-RepetitionNumber2_rel19.

[0669] If the measured RSRP is less than rsrp-ThresholdMsg1-RepetitionNumber2 and less than rsrp-ThresholdMsg1-RepetitionNumber2_rel19.

[0670] If the measured RSRP is less than rsrp-ThresholdMsg1-RepetitionNumber2 and less than rsrp-ThresholdMsg1-RepetitionNumber4_rel19.

[0671] In such cases, the RO type can be selected based on the following criteria, and the number of PRACH iterations can be determined.

[0672] Alt 1) Select according to the UE implementation.

[0673] Alt 2) Select a large value for N. This can help expand coverage.

[0674] Alt 3) Select a small value for N. This can help reduce latency.

[0675] Alt 4) Select Legacy RO: Detection performance can be good because there is no CLI / SI interference.

[0676] Alt 5) Select additional RO: Priorities can be assigned, and additional ROs can be selected for load balancing.

[0677] Alt 6) Select the parameter with the largest threshold value among the specified threshold values ​​that the measured RSRP satisfies. If multiple parameters have the same threshold value, Alt 1-5 may be applied.

[0678] Alt 7) You can use one or more of the Alts mentioned above in combination.

[0679] Alt 8) In the range where additional RO thresholds exist, legacy RO thresholds can be ignored.

[0680] Alt 9) When the range created by the thresholds for each iteration of the legacy RO and the range created by the thresholds for each iteration of the additional RO overlap, the iteration can be performed on the additional RO by prioritizing the thresholds for the additional RO. When the ranges do not overlap, that is, when there are no thresholds satisfied by the UE for the additional RO, the iteration can be performed on the legacy RO.

[0681] As mentioned above, random access operations in communication systems applying / supporting SBFD can provide two types of RO.

[0682] For RACH setting option 1, RO is set with a single legacy RACH setting, which may include additional RO for SBFD symbols and legacy RO for non-SBFD symbols / flexible SBFD symbols.

[0683] For RACH setting option 2, RO is set with legacy RACH settings and additional RACH settings, legacy RO of non-SBFD symbols is set with legacy RACH settings, and additional RO within SBFD symbols (and / or non-SBFD symbols) is set with additional RACH settings.

[0684] For SBFD-aware UEs with RRC connection status, RACH configuration option 1 (hereinafter referred to as Option 1), which uses a single RACH configuration and is based only on the existing parameters of the single RACH configuration, and RACH configuration option 2 (hereinafter referred to as Option 2), which uses two separate RACH configurations including one existing RACH configuration and one additional RACH configuration, are both supported. It is not supported to enable both options simultaneously for a UE.

[0685] The UE does not need to support both of the above two options.

[0686] For a UE that recognizes SBFD in the RRC CONNECTED state, for RACH configuration option 1, legacy SSB-RO mapping is applied to legacy ROs including ROs of non-SBFD symbols and ROs of SBFD symbols flexibly configured by tdd-UL-DL-ConfigurationCommon.

[0687] For ROs of SBFD symbols configured as downlinks by tdd-UL-DL-ConfigurationCommon, a separate SSB-RO mapping is used.

[0688] For RACH configuration option 1, the following method is supported to determine the lowest RO of additional ROs for SBFD symbols. The msg1-FrequencyStart parameter of rach-ConfigCommon is reinterpreted as the frequency offset of the lowest RO in the frequency domain relative to the lowest PRB among the UL usable PRBs. ROs outside the UL usable PRBs are invalid.

[0689] For RACH setting option 2, for additional ROs configured by additional RACH settings, legacy SSB-RO mapping rules are used, but an SSB-RO mapping separate from the SSB-RO mapping for legacy ROs configured by legacy RACH settings is used.

[0690] N within additional ROs preamble rep For PRACH transmissions with preamble repetitions, N preamble rep The set of valid additional ROs and N preamble rep The current standard specification for determining the time period of the set of valid additional ROs can be reused.

[0691] N preamble repThe time period of the set of valid additional ROs is determined separately from the time period of legacy ROs.

[0692] For RACH configuration option 1, additional ROs may include ROs of SBFD symbols configured as downlinks by tdd-UL-DL-ConfigurationCommon, ROs of SBFD symbols configured as downlinks by tdd-UL-DL-ConfigurationCommon, and ROs of SBFD symbols configured as flexible. For RACH configuration option 2, additional ROs are ROs configured by additional RACH configurations.

[0693] To support random access operations for SBFD-aware UEs in an RRC connection state, for RACH setting option 2, the following alternatives may be selected.

[0694] 1) Additional ROs for non-SBFD symbols configured by additional RACH settings are not valid for SBFD-identified UEs. 2) Additional ROs for non-SBFD symbols configured by additional RACH settings may be valid for SBFD-identified UEs.

[0695] For example, in the case of RACH setting option 2, additional ROs of non-SBFD symbols set by additional RACH settings are not valid for SBFD-identified UEs.

[0696] For legacy ROs configured by legacy RACH settings, SBFD-aware UEs follow legacy RO validity rules and legacy SSB-RO mapping rules.

[0697] When RACH configuration option 1 is applied to a UE that recognizes SBFD in an RRC connection state, legacy SSB-RO mapping is applied to legacy ROs, including ROs of non-SBFD symbols and ROs of SBFD symbols flexibly configured by tdd-UL-DL-ConfigurationCommon.

[0698] For ROs of SBFD symbols configured as downlinks by tdd-UL-DL-ConfigurationCommon, a separate SSB-RO mapping is used.

[0699] For RACH setting option 1, existing SSB-RO mapping rules are reused for additional ROs. For RACH setting option 2, legacy SSB-RO mapping rules are used for additional ROs configured by the additional RACH setting, but an SSB-RO mapping separate from the SSB-RO mapping for legacy ROs configured by the legacy RACH setting is used.

[0700] For RACH configuration option 1, for ROs of SBFD symbols configured as downlinks by tdd-UL-DL-ConfigurationCommon, the following conditions may be additionally supported to determine RO validity.

[0701] Condition #1: Valid ROs are at least N from the last downlink non-SBFD symbol. gap It starts after the symbols.

[0702] Condition #2: Valid ROs are at least N from the SSB gap It starts after the symbol.

[0703] For RACH setting option 2, additional RO is valid in the following cases.

[0704] 1) It may be valid if it is within SBFD symbols, or starts at an SBFD symbol and ends at a non-SBFD symbol in the same slot or another slot (if the network sets this case as valid).

[0705] 2) Minimum N from the last downlink SBFD symbol gap If it started after the symbol.

[0706] 3) Minimum N from the most recent SSB gap If it started after the symbol.

[0707] 4) Cases where it does not overlap with the SSB in the time domain.

[0708] Meanwhile, if different types of ROs exist and support a single PRACH transmission, a single PRACH transmission can be performed by selecting one type of RO. The different types of ROs may include legacy ROs or additional ROs for SBFD operations. In this case, the conditions applied to select one RO type may be related to RSRP threshold parameters (e.g., rsrp-Threshold_ROtype, rsrp-Threshold_SSB_ROtype) related to RSRP or SSB, and these parameters may be provided by gNB.

[0709] If there are other types of ROs (legacy ROs and additional ROs for SBFD operations), multiple PRACH transfers can be supported. In this case, multiple PRACH transfers can be performed by selecting an RO group composed of ROs of the same type.

[0710] At this time, other types of RO groups configured for the PRACH iteration may include legacy RO groups (RO groups consisting only of legacy ROs) or additional RO groups (RO groups consisting only of additional ROs).

[0711] In conventional standard specifications, the msg1-RepetitionNum of the legacy RO can be set to 3, and N can be N1, N2, N3 (e.g., 2, 4, 8).

[0712] Regarding the criteria for determining whether to perform a single PRACH transmission or to repeat the PRACH transmission N times, rsrp-ThresholdMsg1-RepetitionNumberN can be given as rsrp-ThresholdMsg1-RepetitionNumber2, rsrp-ThresholdMsg1-RepetitionNumber4, and rsrp-ThresholdMsg1-RepetitionNumber8.

[0713] For example, the additional RO's msg1-RepetitionNum_rel19 can be set to 3, and N can be N11, N12, N13 (e.g., 2, 4, 8), and the rsrp-ThresholdMsg1-RepetitionNumberN_rel19, which determines a single PRACH or PRACH repeated N times, can be given as rsrp-ThresholdMsg1-RepetitionNumber2_rel19, rsrp-ThresholdMsg1-RepetitionNumber4_rel19, rsrp-ThresholdMsg1-RepetitionNumber8_rel19.

[0714] In this case, in future standard specifications, the threshold values ​​related to the number of iterations of Msg1 may differ from the above. For example, the number of iterations of Msg1 may not be the same for the additional RO and the legacy RO, and some or all values ​​may differ. For example, the number of iterations applied (or applicable) to the additional RO may be 16, 32, etc. For example, the number of iterations applied to the additional RO may be one or more, and three or more may be possible.

[0715] When parameters related to legacy RO and additional RO are set as such, single / multiple PRACH transmissions can be determined by the following method or procedure.

[0716] <RO 타입을 먼저 선택한 후, 단일 PRACH 전송 혹은 다중 PRACH 전송을 선택하는 방법>

[0717] Figure 22 is an example of a method for selecting a random access (RA) type.

[0718] Referring to FIG. 22, the terminal can select an RA type by going through the settings of, for example, BWP selection, RO type selection, functional applicability determination, availability determination of the RA resource set, and RA resource selection. In other words, as shown in FIG. 22, RO type selection can be performed before determining single / multiple PRACH transmission (RA type selection).

[0719] Case 1-1)

[0720] To select the RO type, the relevant RSRP threshold value is set / instructed by the gNB. The relevant RSRP threshold may be reused from those defined for RO type selection when PRACH iteration is not supported, or newly set for PRACH iteration. Once RO selection is complete, it is determined whether to perform a single PRACH transfer or multiple PRACH transfers with N iterations based on the selected / selected RO type. At this time, the following procedure may be applied.

[0721] Step 1) Set / instruct the relevant RSRP-threshold (e.g., ROtype_rsrp-Threshold) for RO type selection from gNB.

[0722] Step 2) Once the RO type is determined, apply the rsrp-ThresholdMsg1-RepetitionNumberN set / instructed for each type to determine whether to perform a single PRACH transfer, or if RPACH repetition, how many times to repeat the transfer. If the RO type is determined to be Legacy RO, apply rsrp-ThresholdMsg1-RepetitionNumberN, and if it is determined to be Additional RO, apply rsrp-ThresholdMsg1-RepetitionNumberN_additionalRO.

[0723] In this case, for RACH configuration option 1, the same msg1-RepetitionNum can be given to the additional RO group and the legacy RO group. For RACH configuration option 2, separate parameters (e.g., msg1-RepetitionN_additionalRO, msg1-RepetitionNumN) can be applied to the additional RO group and the legacy RO group.

[0724] In other words, in Step 1), the UE can determine the RO type after measuring the terminal RSRP. For example, if the measured terminal RSRP value is greater than the ROtype_rsrp-Threshold, an additional RO can be selected. However, depending on the motivation / purpose / reason for applying SBFD, it may be defined so that an additional RO can be selected if the measured terminal RSRP value is less than the ROtype_rsrp-Threshold. For example, assume that the value of N is given as 2, 4, or 8.

[0725] If additional ROs are selected in Step 2), the legacy iteration count selection procedure can be applied based on rsrp-ThresholdMsg1-RepetitionNum2_additionalRO, rsrp-ThresholdMsg1-RepetitionNum4_additionalRO, and rsrp-ThresholdMsg1-RepetitionNum8_additionalRO (if configured).

[0726] For a BWP (or UL available PRB) selected for a random access procedure, a random access resource set associated with Msg1 iteration count 8 is set, and if the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum8_additionalRO: it can be assumed that Msg1 iteration is applicable and that 8 is included in the number of Msg1 iterations applicable to the current random access procedure.

[0727] Option 1-1) Before performing the RO group type (RO type, hereinafter the same) switching procedure, the number of repetitions can be increased while maintaining the selected RO group type. A maximum number of repetitions may be defined as a condition for the switching to be performed, and after multiple PRACH transmissions are performed for the maximum number of repetitions, if the PRACH transmission is not successful, the switching to a different type of RO group type is performed.

[0728] Option 1-2) After selecting PRACH repetition, the selected RO group type is maintained. In other words, RO type switching can be introduced for a single PRACH transmission.

[0729] For a BWP (or UL available PRB) selected for a random access procedure, a random access resource set associated with Msg1 iteration count 4 is set, and if the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum4_additionalRO: it can be assumed that Msg1 iteration is applicable and that 4 is included in the number of Msg1 iterations applicable to the current random access procedure.

[0730] Option 1-1) Before performing the RO group type switching procedure, the number of repetitions can be increased while maintaining the selected RO group type. A maximum number of repetitions may be defined as a condition for the switching to be performed, and after multiple PRACH transmissions are performed for the maximum number of repetitions, if the PRACH transmission is unsuccessful, the switching to a different type of RO group type is performed.

[0731] Option 1-2) After selecting PRACH repetition, the selected RO group type is maintained. In other words, RO type switching can be introduced for a single PRACH transmission.

[0732] For a BWP (or UL available PRB) selected for a random access procedure, a random access resource set associated with Msg1 iteration count 2 is set, and if the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum2_additionalRO: it can be assumed that Msg1 iteration is applicable and that 2 is included in the number of Msg1 iterations applicable to the current random access procedure.

[0733] Option 1-1) Before performing the RO group type switching procedure, the number of repetitions can be increased while maintaining the selected RO group type. A maximum number of repetitions may be defined as a condition for the switching to be performed, and after multiple PRACH transmissions are performed for the maximum number of repetitions, if the PRACH transmission is unsuccessful, the switching to a different type of RO group type is performed.

[0734] Option 1-2) After selecting PRACH repetition, the selected RO group type is maintained. In other words, RO type switching can be introduced for a single PRACH transmission.

[0735] If the RSRP of the downlink path loss threshold is not less than the set rsrp-ThresholdMsg1-RepetitionNumX_additionalRO: it can be assumed that the Msg1 repetition is not applied to the current random access procedure. That is, a single PRACH transmission is performed.

[0736] Meanwhile, the maximum number of iterations given as a condition for RO type switching to be performed may be a function related to the selected number of iterations. For example, it must be a number equal to or greater than the selected number of iterations. For example, if the set number of iterations is 2, 4, or 8, the maximum number of iterations can be selected from 2, 4, or 8. For example, if the set number of iterations is 2 or 4, the maximum number of iterations cannot be 8.

[0737] If the maximum number of repetitions is set / instructed by gNB to a value (e.g., 2) smaller than the selected number of repetitions (e.g., 4), the terminal may operate as follows.

[0738] Option 1) If PRACH transmission fails after performing PRACH iterations for the selected number of iterations, switch to a different type of RO group type.

[0739] Option 2) If transmission fails after performing PRACH iterations for the selected number of iterations, determine / consider it as a PRACH transmission failure.

[0740] Option 3) After switching to a different type of RO group type, perform an RPACH iteration.

[0741] Meanwhile, if a legacy RO is selected in step 2) described above, the legacy repetition count selection procedure is applied based on rsrp-ThresholdMsg1-RepetitionNum2, rsrp-ThresholdMsg1-RepetitionNum4, and rsrp-ThresholdMsg1-RepetitionNum8 (if configured).

[0742] For a BWP (or UL available PRB) selected for a random access procedure, a random access resource set associated with Msg1 iteration count 8 is set, and if the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum8: it can be assumed that Msg1 iteration is applicable and that 8 is included in the number of Msg1 iterations applicable to the current random access procedure.

[0743] Option 1-1) Before performing the RO group type (RO type) switching procedure, the number of iterations may be increased while maintaining the selected RO group type. A maximum number of iterations may be defined as a condition for the switching to be performed, and after multiple PRACH transmissions are performed up to the maximum number of iterations, if the PRACH transmission fails, the RO group type is switched to a different type. Depending on the embodiment, RO group type switching may not be supported when selecting a legacy RO. In this case, it may operate in the same manner as Option 1-2 below.

[0744] Option 1-2) After selecting PRACH repetition, the selected RO group type is maintained. In other words, RO type switching can be introduced for a single PRACH transmission.

[0745] For a BWP (or UL available PRB) selected for a random access procedure, a random access resource set associated with Msg1 iteration count 4 is established, and if the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum4: it can be assumed that Msg1 iteration is applicable and that 4 is included in the number of Msg1 iterations applicable to the current random access procedure.

[0746] Option 1-1) Before performing the RO group type switching procedure, the number of iterations may be increased while maintaining the selected RO group type. A maximum number of iterations may be defined as a condition for the switching to be performed, and after multiple PRACH transmissions are performed up to the maximum number of iterations, if the PRACH transmission fails, the RO group type is switched to a different type. Depending on the embodiment, RO group type switching may not be supported when selecting a legacy RO. In this case, it may operate in the same manner as Option 1-2 below.

[0747] Option 1-2) After selecting PRACH repetition, the selected RO group type is maintained. In other words, RO type switching can be introduced for a single PRACH transmission.

[0748] For a BWP (or UL available PRB) selected for a random access procedure, a random access resource set associated with Msg1 iteration count 2 is set, and if the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum2: it can be assumed that Msg1 iteration is applicable and that 2 is included in the number of Msg1 iterations applicable to the current random access procedure.

[0749] Option 1-1) Before performing the RO group type switching procedure, the number of iterations may be increased while maintaining the selected RO group type. A maximum number of iterations may be defined as a condition for the switching to be performed, and after multiple PRACH transmissions are performed up to the maximum number of iterations, if the PRACH transmission fails, the RO group type is switched to a different type. Depending on the embodiment, RO group type switching may not be supported when selecting a legacy RO. In this case, it may operate in the same manner as Option 1-2 below.

[0750] Option 1-2) After selecting PRACH repetition, the selected RO group type is maintained. In other words, RO type switching can be introduced for a single PRACH transmission.

[0751] If the RSRP of the downlink path loss criterion is not less than the set rsrp-ThresholdMsg1-RepetitionNumX (where X in rsrp-ThresholdMsg1-RepetitionNumX is 2, 4, or 8): it can be assumed that Msg1 iterations are not applied to the current random access procedure. That is, if a legacy RO type is selected, RO type switching (RO group type switching) may not be supported.

[0752] At this time, the maximum number of iterations of Msg1 given as a condition for switching to be performed may be a function related to the set / selected number of iterations. For example, the maximum number of iterations must be a number equal to or greater than the set / selected number of iterations. For example, if the set number of iterations is 2, 4, or 8, the maximum number of iterations can be selected from 2, 4, or 8. For example, if the set number of iterations is 2 or 4, the maximum number of iterations cannot be 8.

[0753] If such a function is not introduced and the maximum number of iterations is set / instructed by gNB to a value (e.g., 2) smaller than the selected number of iterations (e.g., 4), it may operate as follows.

[0754] Option 1) After performing PRACH iterations for the selected number of iterations, if PRACH transmission fails, switch to a different type of RO group type.

[0755] Option 2) After performing PRACH iterations for the selected number of iterations, if transmission fails, determine / consider it as a PRACH transmission failure.

[0756] Option 3) After switching to a different type of RO group type, perform an RPACH iteration.

[0757] At this time, the ROtype_rsrp-Threshold value may be set to be greater than the rsrp-ThresholdMsg1-RepetitionNumX and rsrp-ThresholdMsg1-RepetitionNumX_additional RO values ​​that are set / instructed according to the RO type. gNB ensures that the ROtype_rsrp-Threshold value is set to be greater than the rsrp-ThresholdMsg1-RepetitionNumX and rsrp-ThresholdMsg1-RepetitionNumX_additional RO values ​​that are set / instructed according to the RO type. The UE can expect that the ROtype_rsrp-Threshold value is greater than the rsrp-ThresholdMsg1-RepetitionNumX and rsrp-ThresholdMsg1-RepetitionNumX_additional RO values ​​that are set / instructed according to the RO type.

[0758] As another selection criterion applicable to RO type selection, if a UE with capability according to future standard specifications is allocated an additional RO from the base station, it may always be allowed to select the additional RO. Subsequently, the UE may follow the legacy method to determine the number of PRACH iterations.

[0759] As other selection criteria applicable to RO type selection, the gNB can directly determine the priority and configure / instruct the related signaling. Subsequently, the UE can follow the legacy method to determine the number of PRACH iterations based on the specified RO type.

[0760] Case 1-2)

[0761] In selecting the RO type, rsrp-ThresholdMsg1-RepetitionNumberN and / or rsrp-ThresholdMsg1-RepetitionNumberN_additionalRO may be used. A threshold parameter associated with the smallest number of PRACH iterations (e.g., 2) among the given N values ​​(e.g., 2, 4, 8) may be used. In this case, in future standard specifications, the threshold parameter associated with the number of iterations may be given differently from the above.

[0762] For example, the number of iterations is not the same for the additional ROs and legacy ROs, and some or all values ​​may differ. For instance, the number of iterations applied to the additional ROs could be 16, 32, etc. For RACH configuration option 1, the same msg1-RepetitionNum can be assigned to both the additional RO group and the legacy RO group. For RACH configuration option 2, separate parameters can be applied to the additional RO group and the legacy RO group. The following procedure may be applied.

[0763] Step 1) The smallest number of repetitions in rsrp-ThresholdMsg1-RepetitionNumberN can be used without receiving separate settings / instructions from gNB for rsrp-Threshold for RO type selection (e.g., rsrp-Threshold_SSB for RO type selection).

[0764] According to the embodiment, the smallest number of repetitions in rsrp-ThresholdMsg1-RepetitionNumberN and the smallest number of repetitions in rsrp-ThresholdMsg1-RepetitionNumberN_additionalRO may be the same.

[0765] According to an embodiment, if the measured RSRP value of the terminal satisfies a threshold value, it can be determined as the associated RO type. For example, if the measured RSRP value of the terminal is greater than rsrp-ThresholdMsg1-RepetitionNumber2, the RO type can be determined as legacy RO.

[0766] If the measured RSRP value of the terminal satisfies all of rsrp-ThresholdMsg1-RepetitionNumberN, the RO type may be determined by the set / defined conditions or priority. In this case, the smallest number of repetitions in rsrp-ThresholdMsg1-RepetitionNumberN and the smallest number of repetitions in rsrp-ThresholdMsg1-RepetitionNumberN_additionalRO may be the same.

[0767] Step 2) Once the RO type is determined, determine whether to perform a single PRACH transmission or, if RPACH iteration, how many times to repeat transmission based on the parameters set / instructed for each type. For example, if legacy RO is determined as the RO type, apply rsrp-ThresholdMsg1-RepetitionNumberN, and if additional RO is determined as the RO type, apply rsrp-ThresholdMsg1-RepetitionNumberN_additionalRO.

[0768] In the process of step 1) described above, if the same number of PRACH iterations (2, 4, 8) is given to the legacy RO group and the additional RO group, rsrp-ThresholdMsg1-RepetitionNumber2 and / or rsrp-ThresholdMsg1-RepetitionNumber2_additionalRO may be used. In this case, the two values ​​may be identical. If the two values ​​are different, the RO type is determined by a specific rule. Conditions or priorities set / defined in relation to the said specific rule may be set.

[0769] For example, in the above Step 1 process, the number of PRACH iterations may be given differently depending on the RO type. For example, 2, 4, and 8 may be set / instructed for the legacy RO group, and 4 and 6 may be set / instructed for the additional RO group. In this case, rsrp-ThresholdMsg1-RepetitionNumber2 or rsrp-ThresholdMsg1-RepetitionNumber4_additionalRO may be used. Here, the two values ​​may be the same. If the two values ​​are different, the RO type is determined by a specific rule. Conditions or priorities set / defined in relation to the above specific rule may be established.

[0770] For example, if one or more relevant rsrp-Thresholds are satisfied in Step 1, the RO type / RO group type may be set by the following settings / directives / priorities.

[0771] i) The UE can select the configured RO / RO group type associated with the rsrp-Threshold that has been set to a high value.

[0772] ii) UE can select an RO / RO group type based on the implementation.

[0773] iii) The UE can select an RO type with a small association period or association pattern period. In this case, it can benefit in terms of PRACH delay.

[0774] iv) The UE can select additional RO / RO groups. This can help with early detection, allowing subsequent msg2 / 3 / 4 related transmissions to be performed at SBFD symbols, and can also help with load balancing.

[0775] If an additional RO is selected in step 2) above, the legacy repetition count selection procedure can be applied based on rsrp-ThresholdMsg1-RepetitionNum2_additionalRO, rsrp-ThresholdMsg1-RepetitionNum4_additionalRO, and rsrp-ThresholdMsg1-RepetitionNum8_additionalRO (if configured).

[0776] For a BWP (or UL available PRB) selected for a random access procedure, a random access resource set associated with Msg1 iteration count 8 is set, and if the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum8_additionalRO: it can be assumed that Msg1 iteration is applicable and that 8 is included in the number of Msg1 iterations applicable to the current random access procedure.

[0777] Option 1-1) Before performing the RO group type switching procedure, the number of repetitions can be increased while maintaining the selected RO group type. A maximum number of repetitions may be defined as a condition for the switching to be performed, and after multiple PRACH transmissions are performed for the maximum number of repetitions, if the PRACH transmission is unsuccessful, the switching to a different type of RO group type is performed.

[0778] Option 1-2) After selecting PRACH repetition, the selected RO group type is maintained. In other words, RO type switching can be introduced for a single PRACH transmission.

[0779] For a BWP (or UL available PRB) selected for a random access procedure, a random access resource set associated with Msg1 iteration count 4 is set, and if the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum4_additionalRO: it can be assumed that Msg1 iteration is applicable and that 4 is included in the number of Msg1 iterations applicable to the current random access procedure.

[0780] Option 1-1) Before performing the RO group type switching procedure, the number of repetitions can be increased while maintaining the selected RO group type. A maximum number of repetitions may be defined as a condition for the switching to be performed, and after multiple PRACH transmissions are performed for the maximum number of repetitions, if the PRACH transmission is unsuccessful, the switching to a different type of RO group type is performed.

[0781] Option 1-2) After selecting PRACH repetition, the selected RO group type is maintained. In other words, RO type switching can be introduced for a single PRACH transmission.

[0782] For a BWP (or UL available PRB) selected for a random access procedure, a random access resource set associated with Msg1 iteration count 2 is set, and if the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum2_additionalRO: it can be assumed that Msg1 iteration is applicable and that 2 is included in the number of Msg1 iterations applicable to the current random access procedure.

[0783] Option 1-1) Before performing the RO group type switching procedure, the number of repetitions can be increased while maintaining the selected RO group type. A maximum number of repetitions may be defined as a condition for the switching to be performed, and after multiple PRACH transmissions are performed for the maximum number of repetitions, if the PRACH transmission is unsuccessful, the switching to a different type of RO group type is performed.

[0784] Option 1-2) After selecting PRACH repetition, the selected RO group type is maintained. In other words, RO type switching can be introduced for a single PRACH transmission.

[0785] If the RSRP of the downlink path loss threshold is not less than the set rsrp-ThresholdMsg1-RepetitionNumX_additionalRO: it can be assumed that the Msg1 repetition is not applied to the current random access procedure. That is, a single PRACH transmission is performed.

[0786] In this case, the maximum number of iterations given as a condition for switching to be performed may be a function related to the set / selected number of iterations. For example, it must be a number equal to or greater than the set / selected number of iterations. For example, if the set number of iterations is 2, 4, or 8, the maximum number of iterations can be selected from 2, 4, or 8. For example, if the set number of iterations is 2 or 4, the maximum number of iterations cannot be 8. If such a function is not introduced and the maximum number of iterations is set / instructed by gNB to a value (e.g., 2) smaller than the selected number of iterations (e.g., 4), it may operate as follows.

[0787] Option 1) If PRACH transmission fails after performing PRACH iterations for the selected number of iterations, switch to a different type of RO group type.

[0788] Option 2) If transmission fails after performing PRACH iterations for the selected number of iterations, determine / consider it as a PRACH transmission failure.

[0789] Option 3) Switch to a different type of RO group type and then perform an RPACH iteration.

[0790] Meanwhile, if a legacy RO is selected in step 2), the legacy repetition count selection procedure is applied based on rsrp-ThresholdMsg1-RepetitionNum2, rsrp-ThresholdMsg1-RepetitionNum4, and rsrp-ThresholdMsg1-RepetitionNum8 (if configured).

[0791] For a BWP (or UL available PRB) selected for a random access procedure, a random access resource set associated with Msg1 iteration count 8 is set, and if the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum8: it can be assumed that Msg1 iteration is applicable and that 8 is included in the number of Msg1 iterations applicable to the current random access procedure.

[0792] Option 1-1) Before performing the RO group type (RO type) switching procedure, the number of iterations may be increased while maintaining the selected RO group type. A maximum number of iterations may be defined as a condition for the switching to be performed, and after multiple PRACH transmissions are performed up to the maximum number of iterations, if the PRACH transmission fails, the RO group type is switched to a different type. Depending on the embodiment, RO group type switching may not be supported when selecting a legacy RO. In this case, it may operate in the same manner as Option 1-2 below.

[0793] Option 1-2) After selecting PRACH repetition, the selected RO group type is maintained. In other words, RO type switching can be introduced for a single PRACH transmission.

[0794] For a BWP (or UL available PRB) selected for a random access procedure, a random access resource set associated with Msg1 iteration count 4 is established, and if the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum4: it can be assumed that Msg1 iteration is applicable and that 4 is included in the number of Msg1 iterations applicable to the current random access procedure.

[0795] Option 1-1) Before performing the RO group type switching procedure, the number of iterations may be increased while maintaining the selected RO group type. A maximum number of iterations may be defined as a condition for the switching to be performed, and after multiple PRACH transmissions are performed up to the maximum number of iterations, if the PRACH transmission fails, the RO group type is switched to a different type. Depending on the embodiment, RO group type switching may not be supported when selecting a legacy RO. In this case, it may operate in the same manner as Option 1-2 below.

[0796] Option 1-2) After selecting PRACH repetition, the selected RO group type is maintained. In other words, RO type switching can be introduced for a single PRACH transmission.

[0797] For a BWP (or UL available PRB) selected for a random access procedure, a random access resource set associated with Msg1 iteration count 2 is set, and if the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum2: it can be assumed that Msg1 iteration is applicable and that 2 is included in the number of Msg1 iterations applicable to the current random access procedure.

[0798] Option 1-1) Before performing the RO group type switching procedure, the number of iterations may be increased while maintaining the selected RO group type. A maximum number of iterations may be defined as a condition for the switching to be performed, and after multiple PRACH transmissions are performed up to the maximum number of iterations, if the PRACH transmission fails, the RO group type is switched to a different type. Depending on the embodiment, RO group type switching may not be supported when selecting a legacy RO. In this case, it may operate in the same manner as Option 1-2 below.

[0799] Option 1-2) After selecting PRACH repetition, the selected RO group type is maintained. In other words, RO type switching can be introduced for a single PRACH transmission.

[0800] If the RSRP of the downlink path loss criterion is not less than the set rsrp-ThresholdMsg1-RepetitionNumX (where X in rsrp-ThresholdMsg1-RepetitionNumX is 2, 4, or 8): it can be assumed that Msg1 iterations are not applied to the current random access procedure. That is, if a legacy RO type is selected, RO type switching (RO group type switching) may not be supported.

[0801] At this time, the maximum number of iterations of Msg1 given as a condition for switching to be performed may be a function related to the set / selected number of iterations. For example, the maximum number of iterations must be a number equal to or greater than the set / selected number of iterations. For example, if the set number of iterations is 2, 4, or 8, the maximum number of iterations can be selected from 2, 4, or 8. For example, if the set number of iterations is 2 or 4, the maximum number of iterations cannot be 8.

[0802] If such a function is not introduced and the maximum number of iterations is set / instructed by gNB to a value (e.g., 2) smaller than the selected number of iterations (e.g., 4), it may operate as follows.

[0803] Option 1) After performing PRACH iterations for the selected number of iterations, if PRACH transmission fails, switch to a different type of RO group type.

[0804] Option 2) After performing PRACH iterations for the selected number of iterations, if transmission fails, determine / consider it as a PRACH transmission failure.

[0805] Option 3) After switching to a different type of RO group type, perform an RPACH iteration.

[0806] <RO 타입 각각에 주어진 문턱치 값을 기준으로 RO 타입과 단일 PRACH 전송을 포함한 반복 횟수를 동시에 결정하는 방법>

[0807] FIG. 23 illustrates a terminal operation that performs RA type selection.

[0808] Referring to FIG. 23, the terminal can select an RA type through the settings of BWP selection, functional applicability determination, availability determination of the RA resource set, and RA resource selection.

[0809] RO type selection can be included in the configuration process of RA resource selection.

[0810] To select the RO type, rsrp-ThresholdMsg1-RepetitionNumberN and / or rsrp-ThresholdMsg1-RepetitionNumberN_additionalRO may be used. N values ​​of 2, 4, and 8 may be given for legacy ROs and additional ROs. In future standard specifications, threshold values ​​related to the number of repetitions may be given differently from the above. For example, the number of repetitions may not be the same for additional ROs and legacy ROs, and some or all values ​​may differ. For example, the number of repetitions applied to additional ROs may be 16, 32, etc. For RACH configuration option 1, the same msg1-RepetitionNum may be given to the additional RO group and the legacy RO group. For RACH configuration option 2, separate parameters (e.g., msg1-RepetitionN_rel19, msg1-RepetitionNumN) may be applied to the additional RO group and the legacy RO group.

[0811] According to an embodiment, the RO type may be determined by comparing the measured RSRP with all given rsrp-ThresholdMsg1-RepetitionNumberN and rsrp-ThresholdMsg1-RepetitionNumberN_additionalRO without limiting it to a specific rsrp-threshold value. In this case, one or more values ​​may be satisfied in each RO type.

[0812] In other words, the measured rsrp of the terminal may satisfy one or more threshold parameters. In this case, the RO type can be selected based on the following criteria, and the number of PRACH iterations including a single transmission can be determined.

[0813] Alt 1) Select according to the UE implementation.

[0814] Alt 2) Select a large value for N. This can help expand coverage.

[0815] Alt 3) Select a small value for N. This can help reduce latency.

[0816] Alt 4) Legacy RO selection: Detection performance can be good because there is no CLI (cross link interference) / SI (self interference).

[0817] Alt 5) Select additional RO: Additional ROs may be given priority, which may be for load balancing.

[0818] Alt 6) Select the parameter with the largest threshold among the specified thresholds that satisfies the RSRP. If multiple parameters have the same threshold, Alt 1-Alt 5 may be applied.

[0819] Alt 7) You can use one or more of the Alts mentioned above in combination.

[0820] Alt 8) Legacy RO-related thresholds can be ignored in the range where additional RO-related thresholds exist.

[0821] Alt 9) When the range created by the thresholds for each iteration of the legacy RO overlaps with the range created by the thresholds for each iteration of the additional RO, the PRACH iteration may be performed on the additional RO by prioritizing the threshold of the additional RO. If the ranges do not overlap, that is, if there is no threshold satisfied by the UE for the additional RO, the PRACH iteration may be performed on the legacy RO.

[0822] Alt 10) gNB can set / instruct each threshold value with the following restrictions. UE can expect threshold values ​​to be set / instructed with the following restrictions.

[0823] rsrp-ThresholdMsg1-RepetitionNumber2 for SBFD RO > rsrp-ThresholdMsg1-RepetitionNumber2 for Legacy RO > rsrp-ThresholdMsg1-RepetitionNumber4 for SBFD RO > rsrp-ThresholdMsg1-RepetitionNumber4 for Legacy RO > rsrp-ThresholdMsg1-RepetitionNumber8 for SBFD RO > rsrp-ThresholdMsg1-RepetitionNumber8 for Legacy RO.

[0824] At this time, in the case of rsrp-ThresholdMsg1-RepetitionNumber2 for SBFD RO > RSRP of the terminal > rsrp-ThresholdMsg1-RepetitionNumber2 for legacy RO, if a single transmission in legacy RO is satisfied and two PRACH repetitions in SBFD RO are satisfied, RO type selection can be made based on the RO type selection conditions mentioned above.

[0825] Once the RO type and the number of PRACH transmissions are determined, the following operations can be performed.

[0826] If multiple PRACH iterations are selected:

[0827] Option 1-1) Before performing the RO group type (RO type, hereinafter the same) switching procedure, the number of repetitions can be increased while maintaining the selected RO group type. A maximum number of repetitions may be defined as a condition for the switching to be performed, and after multiple PRACH transmissions are performed for the maximum number of repetitions, if the PRACH transmission is not successful, the switching to a different type of RO group type is performed.

[0828] Option 1-2) After selecting PRACH repetition, the selected RO group type is maintained. In other words, RO type switching can be introduced for a single PRACH transmission.

[0829] If a single PRACH transfer is selected:

[0830] Performs a single PRACH transmission with the selected RO type.

[0831] In this case, the maximum number of iterations given as a condition for switching to be performed may be a function related to the set / selected number of iterations. For example, it must be a number equal to or greater than the selected number of iterations. For example, if the set number of iterations is 2, 4, or 8, the maximum number of iterations can be selected from 2, 4, or 8. For example, if the set number of iterations is 2 or 4, the maximum number of iterations cannot be 8. If such a function is not introduced and the maximum number of iterations is set / instructed by gNB to a value (e.g., 2) smaller than the selected number of iterations (e.g., 4), it may operate as follows.

[0832] Option 1) If PRACH transmission fails after performing PRACH iterations for the selected number of iterations, switch to a different type of RO group type.

[0833] Option 2) If transmission fails after performing PRACH iterations for the selected number of iterations, determine / consider it as a PRACH transmission failure.

[0834] Option 3) Switch to a different type of RO group type and then perform an RPACH iteration.

[0835] FIG. 24 illustrates a wireless device that can be applied to the present specification.

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

[0837] The first wireless device (100) includes at least one processor (102) and at least one memory (104), and may additionally include at least one transceiver (106) and / or at least one antenna (108). The at least one processor (102, hereinafter simply referred to as processor) controls at least one memory (104, hereinafter simply referred to as memory) and / or at least one transceiver (106, hereinafter simply referred to as transceiver or transceiver), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document. For example, the processor (102) may process information within the memory (104) to generate a first information / signal, and then transmit a wireless signal containing the first information / signal through the transceiver (106). Additionally, the processor (102) may receive a wireless signal containing a second information / signal through a transceiver (106) and then store information obtained from signal processing of the second information / signal in a 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 store software code containing instructions for performing some or all of the processes controlled by the processor (102) or for performing the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive 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 in combination with an RF (Radio Frequency) unit.In this specification, a wireless device may refer to a communication modem / circuit / chip.

[0838] At least one processor (102) receives i) a RACH opportunity (random access channel occasion: RO) type RSRP (Reference Signal Received Power) threshold and ii) a message 1 (message 1: Msg1) repetition count RSRP threshold, selects a specific RO type based on the RO type RSRP threshold, and determines the Msg1 repetition count based on the Msg1 repetition count RSRP threshold associated with the specific RO type. The specific operation has been described above with reference to FIGS. 20 and 21.

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

[0840] The processor (202) provides the terminal with i) a RO type RSRP (Reference Signal Received Power) threshold, which is a threshold used to select a RACH opportunity (random access channel occasion: RO) type, and ii) a Msg1 repetition count RSRP threshold, which is a threshold used to determine whether to select resources indicating the repetition count of message 1 (Msg1), and receives a message 1 repetition transmission from the terminal. The specific operation has been described above with reference to FIGS. 20 and 21.

[0841] Figure 25 illustrates another example of a wireless device.

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

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

[0844] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation 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 flowcharts of operation disclosed in this document. One or more processors (102, 202) may generate a signal (e.g., baseband signal) containing a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document.

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

[0846] For example, in at least one computer-readable medium (CRM) comprising instructions that are executed by at least one processor to perform operations, the operations include: receiving an RO type RSRP threshold and ii) Msg1 iteration count RSRP thresholds; selecting a specific RO type based on the RO type RSRP threshold; and determining the number of Msg1 iterations based on the Msg1 iteration count RSRP threshold associated with the specific RO type. The specific operations have been described above with reference to FIGS. 20 and 21.

[0847] The descriptions, functions, procedures, proposals, methods, and / or operation sequences 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. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be included in one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

[0848] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0849] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc., of this document to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc., disclosed in this document from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may 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 connected 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, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document through 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 the received wireless signal / channel, etc. from an RF band signal to a baseband signal in order to process the received user data, control information, wireless signal / channel, etc. using one or more processors (102, 202).One or more transceivers (106, 206) can convert user data, control information, wireless signals / channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters.

[0850] FIG. 26 illustrates an example of a signal processing module structure. Here, signal processing may be performed in the processor (102, 202) of FIG. 24.

[0851] Referring to FIG. 26, a transmission device (e.g., a processor, a processor and memory, or a processor and a transceiver) within a terminal or base station may include a scrambler (301), a modulator (302), a layer mapper (303), an antenna port mapper (304), a resource block mapper (305), and a signal generator (306).

[0852] The transmission device can transmit one or more codewords. Each coded bit within a codeword is scrambled by a scrambler (301) and transmitted over a physical channel. A codeword may be referred to as a data sequence and may be equivalent to a transmission block, which is a data block provided by the MAC layer.

[0853] 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 to arrange them into complex-valued modulation symbols representing positions on a signal constellation. There are no restrictions on the modulation scheme, and m-PSK (m-Phase Shift Keying) or m-QAM (m-Quadrature Amplitude Modulation), etc., may be used for modulating the encoded data. The modulator may be referred to as a modulation mapper.

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

[0855] The resource block mapper (305) can map complex modulation symbols for each antenna port to appropriate resource elements within a virtual resource block allocated for transmission. The resource block mapper can map the virtual resource block to a physical resource block according to an appropriate mapping scheme. The resource block mapper (305) can assign complex modulation symbols for each antenna port to appropriate subcarriers and multiplex them according to the user.

[0856] The signal generator (306) can generate a complex-valued time domain OFDM symbol signal by modulating a complex modulation symbol for each antenna port, for example, an antenna-specific symbol, using a specific modulation method, for example, OFDM (Orthogonal Frequency Division Multiplexing). 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 after the IFFT is performed. The OFDM symbol is transmitted to a receiving device through each transmitting antenna after undergoing digital-to-analog conversion, frequency uplink conversion, etc. The signal generator may include an IFFT module, a CP inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc.

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

[0858] Referring to FIG. 27, a transmission device (e.g., a processor, a processor and 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).

[0859] For one codeword, the transmission device can scramble the coded bits within the codeword by the scrambler (401) and then transmit them through the physical channel.

[0860] The scrambled bits are modulated into complex modulation symbols by a modulator (402). The modulator may modulate the scrambled bits according to a predetermined modulation scheme to arrange them into complex modulation symbols representing positions on a signal constellation. There are no restrictions 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), etc., may be used for modulating the encoded data.

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

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

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

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

[0865] The signal generator (406) can generate a complex-valued time domain Orthogonal Frequency Division Multiplexing (OFDM) symbol signal by modulating a complex modulated symbol using a specific modulation method, such as 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 after the IFFT is performed. The OFDM symbol is transmitted to a receiving device through each transmitting antenna after undergoing digital-to-analog conversion, frequency uplink conversion, etc. The signal generator (406) may include an IFFT module, a CP inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc.

[0866] The signal processing process of the receiving device may be configured as the inverse of the signal processing process of the transmitter. Specifically, the processor of the receiving device performs decoding and demodulation for a wireless signal received from the outside through the antenna port(s) of the transmitter and receiver. The receiving device may include multiple receiving antennas, and each signal received through the receiving antennas is restored to a baseband signal, then undergoes multiplexing and MIMO demodulation to be restored to the data sequence that the transmitting device originally intended to transmit. 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 processed signals, and a channel demodulator for demodulating the multiplexed signal sequence into the corresponding codeword. The signal restorer, multiplexer, and channel demodulator may be configured as a single integrated module or as separate independent modules that perform their functions. 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 CP from the digital signal, an FFT module that applies a fast Fourier transform (FFT) to the signal from which 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 transport layer by a multiplexer, and the transport layer is restored to a codeword that the transmitting device intended to transmit by a channel demodulator.

[0867] FIG. 28 illustrates an example of a wireless communication device according to an embodiment of the present disclosure.

[0868] Referring to FIG. 28, 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). The antenna and the processor may be multiple.

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

[0870] The memory (2330) is connected to the processor (2310) and stores information related to the operation of the processor. The memory may be located inside or outside the processor and may be connected to the processor through various technologies such as wired or wireless connections. The memory (2330) of FIG. 28 may be the memory (104, 204) of FIG. 24.

[0871] The user can input various types of information, such as phone numbers, using various techniques, such as pressing a button on the keypad (2320) or using a microphone (2350) to activate sound. The processor (2310) receives and processes the user's information and can perform appropriate functions, such as making a call to the input phone number. In some scenarios, data may be retrieved from a SIM card (2325) or memory (2330) to perform appropriate functions. In some scenarios, the processor (2310) can display various types of information and data on a display (2315) for the user's convenience.

[0872] A transceiver (2335) is connected to a processor (2310) to transmit and / or receive a wireless signal, such as a Radio Frequency (RF) signal. The processor may control the transceiver to initiate communication or to transmit a wireless signal 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 embodiments, when the transceiver receives a wireless signal, it 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 to be output through a speaker (2345). The transceiver of FIG. 28 may be the transceiver (106, 206) of FIG. 27.

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

[0874] FIG. 28 is merely one example of an implementation of a terminal, and is not limited thereto. The terminal is not required to include all the elements of FIG. 28. 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 and, in this case, may not be included in the terminal.

[0875] FIG. 29 illustrates a communication system (1) applicable to the present specification.

[0876] Referring to FIG. 29, the communication system (1) to which the present specification applies includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using 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 Thing) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with wireless communication capabilities, an autonomous vehicle, a vehicle capable of performing inter-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 HMDs (Head-Mounted Devices), HUDs (Head-Up Displays) equipped in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Portable devices may include smartphones, smartpads, wearable devices (e.g., smartwatches, smart glasses), computers (e.g., laptops, etc.). Home appliances may include TVs, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, base stations and networks may be implemented as wireless devices, and a specific wireless device (200a) may operate as a base station / network node to other wireless devices.

[0877] Wireless devices (100a to 100f) can be connected to a network (300) through a base station (200). Artificial Intelligence (AI) technology may be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) through the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices (100a to 100f) may communicate with each other through the base station (200) / network (300), but they may 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). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0878] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base station (200) and base station (200) / base station (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 inter-base station communication (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 / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on various proposals of this specification, at least some of the following may be performed: 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.), resource allocation processes, etc.

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

Claims

1. Regarding the method, The terminal (user equipment: UE) receives i) a RACH opportunity (random access channel occasion: RO) type RSRP (Reference Signal Received Power) threshold and ii) message 1 (message 1: Msg1) repetition count RSRP thresholds, and The above terminal selects a specific RO type based on the RO type RSRP threshold, and A method characterized by the above terminal determining the number of Msg1 repetitions based on the Msg1 repetition count RSRP threshold related to the specific RO type.

2. A method according to claim 1, characterized in that the RO type RSRP threshold is a threshold used by the UE for choosing RO type.

3. A method according to claim 1, wherein each of the Msg1 repetition number RSRP thresholds is a threshold used by the UE for determining whether to select resources indicating a Msg1 repetition number.

4. A method according to claim 1, wherein the terminal determines the number of Msg1 iterations applicable to a current random access procedure based on the Msg1 iteration count RSRP threshold associated with the specific RO type.

5. In Paragraph 1, A method characterized in that the above RO type includes a first RO type related to the RO of a non-subband full duplex (non-SBFD) time resource and a second RO type related to the RO of an SBFD time resource.

6. In Paragraph 5, A method characterized in that the above specific RO type is the above second RO type.

7. A method according to claim 1, characterized by selecting the specific RO type based on the comparison result of the RSRP of the RO type RSRP threshold and the RSRP of the downlink pathloss reference.

8. A method according to claim 7, characterized in that the downlink path loss criterion is related to the SSB (Synchronization Signal Block) or CSI-RS (Channel State Information-Reference Signal).

9. A method according to claim 1, characterized in that the number of repetitions of Msg1 is related to the number of repetitions of the preamble transmission of the random access procedure.

10. A method according to claim 1, characterized by assuming that the number of Msg1 iterations applicable to the current random access process includes a specific value based on the result of comparing the RSRP of the downlink pathloss reference with the Msg1 iteration count RSRP threshold related to the specific RO type.

11. A method according to claim 10, characterized in that the specific value is 2, 4, or 8.

12. A method according to claim 1, characterized in that the RO type RSRP threshold and the Msg1 repetition count RSRP threshold are received through an RRC (radio resource control) information element.

13. A method according to claim 1, characterized in that the terminal is an SBFD (subband full duplex) aware terminal.

14. A method according to claim 1, wherein when a first RO type is selected based on the RO type RSRP threshold, the terminal performs a single PRACH (physical random access channel) transmission without repetition.

15. The terminal (user equipment: UE) is, At least one transmitter / receiver; At least one memory; and The above includes at least one transceiver and at least one processor connected to the above at least one memory, The above at least one memory includes instructions that are executed by the above at least one processor to perform operations, wherein The above operations are, Receive i) the RACH opportunity (random access channel occasion: RO) type RSRP (Reference Signal Received Power) threshold and ii) the message 1 (Msg1) repetition count RSRP thresholds, and Select a specific RO type based on the above RO type RSRP threshold, and A terminal characterized by including an operation to determine the number of Msg1 repetitions based on the RSRP threshold of the number of Msg1 repetitions associated with the specific RO type mentioned above.

16. A terminal according to claim 15, characterized in that the RO type RSRP threshold is a threshold used by the UE for choosing an RO type.

17. A terminal according to claim 15, wherein each of the Msg1 repetition number RSRP thresholds is a threshold used by the UE for determining whether to select resources indicating a Msg1 repetition number.

18. In claim 15, the terminal is characterized by determining the number of Msg1 iterations applicable to a current random access procedure based on the Msg1 iteration count RSRP threshold associated with the specific RO type.

19. In Paragraph 15, A terminal characterized in that the above RO type includes a first RO type related to the RO of a non-subband full duplex (non-SBFD) time resource and a second RO type related to the RO of an SBFD time resource.

20. In Paragraph 19, A terminal characterized in that the above specific RO type is the above second RO type.

21. A terminal characterized by selecting the specific RO type based on the comparison result of the RSRP of the RO type RSRP threshold and the RSRP of the downlink pathloss reference in claim 15.

22. A terminal according to claim 21, characterized in that the downlink path loss criterion is related to an SSB (Synchronization Signal Block) or a CSI-RS (Channel State Information-Reference Signal).

23. A terminal according to claim 15, characterized in that the number of repetitions of Msg1 is related to the number of repetitions of the preamble transmission of the random access procedure.

24. A terminal according to claim 15, characterized in that, based on the comparison result between the RSRP of the downlink pathloss reference and the RSRP threshold of the Msg1 iteration count related to the specific RO type, the Msg1 iteration count applicable to the current random access process includes a specific value.

25. A terminal according to claim 24, characterized in that the specific value is 2, 4, or 8.

26. A terminal according to claim 15, characterized in that the RO type RSRP threshold and the Msg1 repetition count RSRP threshold are received through an RRC (radio resource control) information element.

27. A terminal according to claim 15, characterized in that the terminal is an SBFD (subband full duplex) aware terminal.

28. A terminal according to claim 15, wherein when a first RO type is selected based on the RO type RSRP threshold, the terminal performs a single PRACH (physical random access channel) transmission without repetition.

29. The device is, At least one memory; and The above includes at least one processor operably coupled with at least one memory, The above at least one memory includes instructions that are executed by the above at least one processor to perform operations, wherein The above operations are, Receive i) the RACH opportunity (random access channel occasion: RO) type RSRP (Reference Signal Received Power) threshold and ii) the message 1 (Msg1) repetition count RSRP thresholds, and Select a specific RO type based on the above RO type RSRP threshold, and A device characterized by including an operation to determine the number of Msg1 repetitions based on the Msg1 repetition count RSRP threshold related to the specific RO type above.

30. At least one computer-readable storage medium (CRM) comprising instructions that are executed by at least one processor to perform operations, The above operations are, Receive i) the RACH opportunity (random access channel occasion: RO) type RSRP (Reference Signal Received Power) threshold and ii) the message 1 (Msg1) repetition count RSRP thresholds, and Select a specific RO type based on the above RO type RSRP threshold, and A CRM characterized by including an operation to determine the number of Msg1 repetitions based on the Msg1 repetition count RSRP threshold related to the specific RO type mentioned above.

Images