Method for determining validity of random access occasion in SBFD system, and device using same

Abstract

The present disclosure relates to a random access process, wherein a user equipment (UE): receives, from a base station, semi-static configuration information for a first SBFD section and dynamic configuration information for a second SBFD section; determines a valid RO on the basis of at least one among the semi-static configuration information and the dynamic configuration information; and transmits a preamble to the base station in the valid RO, wherein whether an RO located within the second SBFD section is valid is determined on the basis of whether the RO is included in an uplink subband or a UL usable PRB region configured for the second SBFD section.

Description

Method for determining the validity of random access opportunities in an SBFD system and device using the same

[0001] The present disclosure relates to a wireless communication system, and provides a method and apparatus for determining the validity of a Random Access Occasion (RO) in relation to a Random Access (RA) process in a wireless communication system in which Subband Full Duplex (SBFD) is operated.

[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 (DL) reception and uplink (UL) 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; this 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] Meanwhile, in SBFD operation, since UL and DL are placed in different subbands for specific symbols, slots, or periods, alignment of RO placement with the UL subband or the UL usable Physical Resource Block (PRB) area becomes important. For example, since the PRACH (Physical Random Access Channel) preamble is a UL transmission, random access can be performed normally only if the RO exists within the frequency range where UL transmission is possible.

[0007] In particular, in SBFD operation, it is possible to consider operating sections that are configured semi-statically and sections that change SBFD resource allocation dynamically together. In this case, the terminal must determine whether the RO is valid by considering both the semi-static configuration information and the dynamic configuration information.

[0008] Conventional standard specifications assume that the RO is set only on non-SBFD resources in relation to the random access process. On the other hand, in future wireless communication systems, the RO may be set on SBFD resources as well. In this case, using the existing random access process as is in future wireless communication systems where SBFD resources are introduced is inefficient and may lead to ambiguity.

[0009] In particular, when the UL subband or DL ​​subband changes or the link direction of the SBFD symbol is switched during a dynamic SBFD interval, it may be difficult to consistently determine whether the terminal is an RO capable of transmitting a PRACH preamble under the current conditions.

[0010] If conventional RO validation methods are used in such an environment, problems such as unnecessary preamble transmission attempts in ROs located in frequency ranges where PRACH preamble transmission is impossible, increased resource conflicts, connection delays, and increased failure rates may occur.

[0011] Therefore, in wireless communication systems where dynamic SBFD can be operated, there is an increasing need for a method to determine a valid RO and transmit a preamble only to a valid RO.

[0012] The technical problem that the present disclosure aims to solve is related to a wireless communication system, and to provide a method and apparatus for determining the validity of a Random Access Occasion (RO) in relation to a random access process in a wireless communication system in which different types of Subband Full Duplex (SBFD) are operated.

[0013] In a wireless communication system, the method is characterized in that a terminal (user equipment: UE) receives semi-static configuration information for a first SBFD (Subband Full Duplex) section and dynamic configuration information for a second SBFD section from a base station, determines a valid Random Access Occasion (RO) based on at least one of the semi-static configuration information or the dynamic configuration information, and transmits a preamble from the valid RO to the base station, wherein the validity of the RO located within the second SBFD section is determined based on whether it is included in an uplink (UL) subband or a UL usable Physical Resource Block (PRB) area configured for the second SBFD section.

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

[0015] In another aspect, a method of operation of a base station and a base station device are provided. In the above method, the base station transmits semi-static configuration information for a first SBFD (Subband Full Duplex) section and dynamic configuration information for a second SBFD section to a terminal (user equipment: UE), and receives a preamble from the terminal at an effective RO, wherein the RO located within the second SBFD section among the effective ROs is included in an uplink (UL) subband or UL usable Physical Resource Block (PRB) area configured for the second SBFD section.

[0016] According to the method proposed in the present disclosure, a terminal can consistently determine the validity of a Random Access Occasion (RO) based on whether the RO within a dynamic subband full duplex (SBFD) interval is included in an uplink (UL) subband or a UL usable Physical Resource Block (PRB) area, and transmit a preamble only to a valid RO, thereby eliminating ambiguity in RO selection and preamble transmission during dynamic SBFD operation, thereby suppressing unnecessary PRACH transmission, resource collisions, etc., and simultaneously improving the random access success rate and resource efficiency.

[0017] According to the present disclosure, when an SBFD symbol is changed to a UL symbol, an RO set within a UL subband or a UL available PRB area may cause UL resource fragmentation in the UL symbol, so UL resource fragmentation can be prevented by introducing a new parameter related to frequency offset or reinterpreting an existing parameter.

[0018] According to the present disclosure, even when there are multiple dynamic SBFD segments, different RACH settings can be applied to each segment, thereby ensuring scalability and operational flexibility even when configuring multiple dynamic SBFD segments. In addition, communication overhead can be reduced by configuring the RACH (Random Access Channel) setting information related to one of the multiple dynamic SBFD segments to include all parameters regarding the RACH setting, and configuring the RACH setting information related to the remaining dynamic SBFD segments to include only parameters having values ​​that are not identical to this.

[0019] According to the present disclosure, when a dynamic SBFD section is set or directed in overlap after a semi-static SBFD section is set, rules such as invalidating existing ROs or selectively validating only ROs within UL resources are proposed, and even when a semi-static SBFD section and a dynamic SBFD section are set simultaneously, rules such as maintaining only ROs within the semi-static SBFD section are proposed, thereby enabling systematic prevention of RO conflicts in various situations, such as the overlap of semi-static SBFD sections and dynamic SBFD sections.

[0020] According to the present disclosure, by applying masking or muting to ROs within a dynamic SBFD interval based on masking or muting information and additionally selecting allowed ROs for which preamble transmission is permitted, unnecessary PRACH (Physical Random Access Channel) resource transmission and collisions between resources can be prevented in accordance with the dynamic SBFD resource usage policy of the network.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0035] FIG. 13 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.

[0036] FIG. 14 illustrates the operation method of a terminal.

[0037] FIG. 15 illustrates a process for determining the validity of an RO located within the second SBFD interval (dynamic SBFD interval).

[0038] Figure 16 illustrates the signaling process between a base station and a terminal related to a random access process.

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

[0040] Figure 18 illustrates another example of a wireless device.

[0041] Figure 19 illustrates an example of a signal processing module structure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0067] The following drawings are prepared 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.

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

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

[0070] 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 stage, the terminal can check the downlink channel status by receiving a Downlink Reference Signal (DL RS).

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

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

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

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

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

[0076] Wireless resource structure

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

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

[0079] When a normal CP is used, each slot may contain 14 symbols. When an 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).

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

[0081] Table 1 shows an example of SCS setting μ.

[0082] μΔf=2 μ ·15[kHz]CP(Cyclic prefix)015Normal 130Normal 260Normal,Extended 3120Normal 4240Normal 5480Normal 6960Normal

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

[0084] μN slot symb N frame,μ slot N subframe,μ slot 014101114202214404314808414160165143203261464064

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

[0086] μN slot symb N frame,μ slot N subframe,μ slot 212404

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

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

[0089] 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 two types of frequency ranges (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 the “sub 6GHz range” and FR2 may mean the “above 6GHz range” and may be referred to as millimeter wave (mmW).

[0090] Frequency Range Designation Corresponding Frequency Range Subcarrier Spacing FR1 450MHz - 6000MHz 15, 30, 60kHz FR2 24 250MHz - 52600MHz 60, 120, 240kHz

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

[0092] Frequency Range Designation Corresponding Frequency Range Subcarrier Spacing FR1 4 10 MHz - 7 125 MHz 15, 30, 60 kHz FR2 25 250 MHz - 5 2600 MHz 60, 120, 240 kHz

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

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

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

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

[0097] 1. DL only setting

[0098] 2. UL only setting

[0099] 3. Mixed UL-DL Settings

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

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

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

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

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

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

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

[0107] Transmission operation:

[0108] Common SN;

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

[0110] Individual encryption for source and target cells.

[0111] Receiving operation:

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

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

[0114] Common PDCP reordering;

[0115] Sequential delivery and duplicate detection;

[0116] Common buffer management.

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

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

[0119] UE RF / Baseband Requirements

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0136] The UE is N for the target MCG cells target pdcch-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.

[0137] Full duplex operation for NR

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

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

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

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

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

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

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

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

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

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

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

[0149] For the sake of convenience of explanation, it is assumed below that the base station performs full-duplex communication and the terminal performs half-duplex communication, but this 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.

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

[0151] RACH (random access channel) procedure

[0152] The physical random access procedure can be triggered by a PRACH transmission request or PDCCH command (order) from the upper layer.

[0153] In the present disclosure, the term PDCCH order may be a control signal in which a base station instructs a terminal to start a random access procedure. The PDCCH order may be used, for example, when the uplink synchronization of the terminal is not correct, when uplink signal transmission is required for location measurement, or when synchronization is required when adding a secondary cell.

[0154] In the case of a PDCCH command, the base station may use DCI format 1_0, which is a DCI format for downlink (PDSCH) scheduling. In this case, to distinguish it from general data scheduling, specific field values ​​of DCI format 1_0 may be manipulated and transmitted.

[0155] When the PDCCH command is triggered, the fields related to / included in DCI format 1_0 may be indicated, for example, as follows.

[0156] 1) Frequency domain resource assignment (FDRA): All ones. When all bits of the FDRA field are set to 1, the terminal interprets DCI format 1_0 as a PDCCH command and the remaining fields as information related to random access rather than PDSCH scheduling information.

[0157] 2) RO Type Index: An RO type may be provided (e.g., legacy RO or additional RO). The RO Type Index field may be referred to by other names, such as the RACH occasion indicator or the RO Type indicator. In other words, in this specification, the RO Type Index field may mean the RACH occasion indicator field or the RO Type indicator field. If the value of the RO Type Index field is 0, it indicates first PRACH occasions (RO), and if it is 1, it indicates second PRACH occasions (RO). The first PRACH occasion may be associated with the RO (and / or legacy RO) within the non-SBFD symbol, and the second PRACH occasion may be associated with the RO (and / or additional RO) within the SBFD symbol.

[0158] 3) Random access preamble index: Related preamble information (e.g., ra-PreambleIndex) may be provided in advance. In this case, if no preamble partitioning is provided for a specific type of RO, the RO type may not be distinguishable based on the given preamble value alone.

[0159] 4) SS / PBCH Index.

[0160] i) An SSB value (SSB index) may be given.

[0161] ii) If a separate set of SSBs is configured for RO configuration related to SBFD, the base station can configure / instruct the relevant SSB index according to each RO type.

[0162] iii) An SSB index can be set in the SSB set based on the RO set type.

[0163] 5) PRACH mask index. This field indicates at least one RACH opportunity (RO) associated with the SS / PBCH indicated by the 'SS / PBCH index' for the PRACH transfer of contention-free random access (CFRA) resources.

[0164] Next, the upper-layer configuration for PRACH transmission may include the following:

[0165] Settings for PRACH transmission.

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

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

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

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

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

[0171] 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 contention-based preamble associated with the SS / PBCH block index per valid PRACH opportunity starts at preamble index 0. If N ≥ 1, n·N is associated with the SS / PBCH block index n (0 ≤ n ≤ N-1) per valid PRACH opportunity. preamble total Starting from / N, where N preamble totalis 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.

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

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

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

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

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

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

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

[0179] 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 SSB Obtain 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 SSBIf 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.

[0180] 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 TA Assume =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.

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

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

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

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

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

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

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

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

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

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

[0191] For unpaired spectra:

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

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

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

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

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

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

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

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

[0200] Preamble SCS gap 1.25 kHz or 5 kHz 015 kHz or 30 kHz or 60 kHz or 120 kHz 2480 kHz 8960 kHz 16

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

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

[0203] If the active UL BWP does not change, Δ BWPSwitching =0, and if not, Δ BWPSwitching silver It can be defined in standard specifications.

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

[0205] T switch is the switching gap duration.

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

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

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

[0209] Table 8 shows examples of random access settings for FR1 and unpaired spectrum. PRACH setting indices can range from 0 to 262, and Table 8 provides examples of only some of these. For Table 8, refer to the full Table 6.3.3.2-3 of 3GPP TS 38.211 V19.

[0210] PRACH Settings Index Preamble Format f mod x = y, starting subframe number, symbol, number of PRACH slots within the subframe N RA,slot t ,N number of time domain PRACH opportunities within the PRACH slot RA dur , PRACH 구간xy0016190--0108190--0204190--0302090--0402190--0502040--0602140--0701090--0801080--0901070--01001060--01101050--01201040--01301030--01401020--0150101,600160101,67--0170104,90- -0180103,80--0190102,70--0200108,90--0210104,8,90--0220103,4,90--0230107,8,90--0240103,4,8,90--0250106,7,8,90--0260101,4,6,90--0...........................26102020--026202120--0

[0211] Table 9 shows examples of random access settings for FR2 and unpaired spectrum. PRACH setting indices can range from 0 to 255, and Table 9 provides examples of only some of these. For Table 9, refer to the full Table 6.3.3.2-4 of 3GPP TS 38.211 V19.

[0212] PRACH Settings Index Preamble Format fmod x = y slot number starting symbol 60kHz number of PRACH slots within the slot N RA,slot t ,N number of time domain PRACH opportunities within the PRACH slot RA dur ,PRACH interval xy0A11614,9,14,19,24,29,34,3902621A11613,7,11,15,19,23,27,31,35,3901622A181,29,19,29,3902623A1814,9,14,19,24,29,34,3902624A1813,7,11,15,19,23,27,31,35,3901625A141 4,9,14,19,24,29,34,3901626A1414,9,14,19,24,29,34,3902627A1413,7,11,15,19,23,27,31, 35,3901628A1217,15,23,31,3902629A1214,9,14,19,24,29,34,39016210A1214,9,14,19,24,29, 34,39026211A1213,7,11,15,19,23,27,31,35,39016212A11019,39713213A1103,5,7016214A110 24,29,34,39713215A1109,19,29,39723216A11017,19,37,39016217A1109,19,29,39026218A110 4,9,14,19,24,29,34,39016219A1104,9,14,19,24,29,34,39713220A1103,5,7,9,11,13713221A 11023,27,31,35,39713222A1107,15,23,31,39016223A11023,27,31,35,39016224A11013,14,15, 29,30,31,37,38,39723225A1103,7,11,15,19,23,27,31,35,39713226A1103,7,11,15,19,23,27,31,35,39 0162................................254A3 / B3103,7,11,15,19,23,27,31,35,392126255A3 / B3101,3,5,7,… ,37,392126

[0213] Table 10 shows examples of random access settings for FR1 and paired spectrum / supplementary uplink. PRACH setting indices can range from 0 to 255, and Table 10 shows only some of these. For Table 10, refer to the full Table 6.3.3.2-2 of 3GPP TS 38.211 V19.

[0214] PRACH Settings Index Preamble Format f mod x = y, starting subframe number, symbol, number of PRACH slots within the subframe N RA,slot t ,N number of time domain PRACH opportunities within the PRACH slot RA dur ,PRACH interval xy0016110--01016140--02016170--03016190--0408110--0508140--0608170--0708190--0804110--0904140--01004170--01104190--01202110--01 302140--01402170--01502190--01601010--01701040--01801070--0190101,60--0200102,70--0210103,80--0220101,4,70--0230102,5,80--0240103, 6, 90--0250100,2,4,6,80--0260101,3,5,7,90--0270100,1,2,3,4,5,6,7,8,90--028116110--029116140--0............. ................252C2101,4,70226253C2100,2,4,6,80226254C2100,1,2,3,4,5,6,7,8,90226255C2101,3,5,7,90226

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

[0216] L RA ΔfRA for PRACHΔf for PUSCHN RA RB allocation expressed in number of RBs for PUSCH 8391.2515678391.2530318391.2560213383951524128395301210839560671391515122139153062139156032139301524213930301221393060621396060122139601206213912060242139120120122139120480311391209602231394801204821394804801221394809 6062139960120962139960480242139960960122571301596257130304825713060242571120120482571120480121571120960747571480120192257148048048257148096024211511515961115115304811151156024111511201209761151120480252311511209601345

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

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

[0219] OFDM baseband signal generation for PRACH

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

[0221]

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

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

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

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

[0226] n RA start is the frequency offset of the lowest PRACH transmission opportunity in the frequency domain for physical resource block 0 of the active uplink bandwidth portion. n RA star tis 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.

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

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

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

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

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

[0232] 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 startRA , 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.

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

[0234]

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

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

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

[0238] Δ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, and symbol position l is l=l0+n t RA N dur RA +14n slot RA It is given as follows:

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

[0240] 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 ∈{139,571,1151}, it can be provided by a predetermined table, and L RA It is fixed at 1 when =839.

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

[0242] n slot RA is given as follows:

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

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

[0245] If Δf RA ∈{480,960} and:

[0246] When the "number of PRACH slots within the 60 kHz slot" in the predetermined table is 1, Δf RA n at 480kHz slot RA =7, Δf RA n at =960kHz slot RA =15.

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

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

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

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

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

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

[0253] PRACH repetition

[0254] 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 said 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.

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

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

[0257] 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 SSB For 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.

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

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

[0260] <Slot Settings>

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

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

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

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

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

[0266] ii) pattern1.

[0267] pattern1 can provide the following:

[0268] Slot setting period in units of P msec by dl-UL-TransmissionPeriodicity,

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

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

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

[0272] Uplink symbols u by nrofUplinkSymbols sym .

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

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

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

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

[0277] Pattern 2 can provide the following.

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

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

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

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

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

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

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

[0285] 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 symbslot - d sym,2 -u sym,2 is a flexible symbol.

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

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

[0288] UE references SCS setting μ ref For 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0319] If UE,

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

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

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

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

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

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

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

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

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

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

[0330] i) A symbol that is 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,

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0346] UE Procedure for Determining Slot Format

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0366] Page 254 까지Reserved255UE는 tdd-UL-DL-ConfigurationCommon 또는UE determines the slot format for the slot based on tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated and, if any, on detected DCI formats

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

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

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

[0370] 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 the slotFormats values, 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.

[0371] The UE sets the SCS μ for the active UL BWP of the second UL carrier. SUL This μ SUL ≥μ SFI,SULReference 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.

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

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

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

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

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

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

[0378] 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 a PDCCH or PDSCH via ssb-PositionsInBurst of SIB1, ssb-PositionsInBurst of ServingCellConfigCommon, NonCellDefiningSSB, or dl-OrJointTCI-StateList 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0397] 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 iteration of PUSCH or the PRACH transmission in the symbol set.

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

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

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

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

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

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

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

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

[0406] 3) The UE receives the PDCCH.

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

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

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

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

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

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

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

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

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

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

[0417] The CFRA (Contention-Free Random Access) operation is described below.

[0418] Unlike CBRA (Contention-Based Random Access), CFRA can be provided by a random access preamble and SSB (except for beam failure recovery) by the network.

[0419] Table 14 illustrates which events trigger CFRA in RRC_CONNECTED mode, compared with CBRA-related events. If CFRA fails, it can fall back to CBRA.

[0420] RA Trigger Events Initial access in RRC_IDLE state - RRC Re-establishment procedure - Handover - Beam Failure recovery - RRC Connection Resume procedure from RRC_INACTIVE state - Downlink out of sync - Uplink out of sync - Explicit request by RRC during synchronous reconfiguration - Time alignment setting for secondary TAG - SR failure - Request for Other SI

[0421] The following describes the process of selecting a set of random access resources by considering CFRA to perform a random access procedure.

[0422] If, in the LTM Cell Switch Command MAC CE, a CFRA resource for a random access procedure is provided, and a non-zero Msg1 repetition number is indicated in the LTM Cell Switch Command MAC CE:

[0423] Assuming that Msg1 repetition is applicable, the number of Msg1 repetitions applied to the current random access procedure can be assumed to be the number of Msg1 repetitions specified in the LTM cell switch command MAC CE.

[0424] Otherwise, if a CFRA resource for a random access procedure is provided and the number of Msg1 iterations is specified in rach-ConfigDedicated:

[0425] Assuming that Msg1 iterations are applicable, the number of Msg1 iterations applied to the current random access procedure can be assumed to be the number of Msg1 iterations specified in rach-ConfigDedicated.

[0426] Otherwise, in the LTM cell switch command MAC CE, a CFRA resource for a random access procedure is provided, a non-zero number of Msg1 iterations is indicated in the said LTM cell switch command MAC CE, and RedCap (Reduced Capability) is applicable to the current random access procedure:

[0427] You can select a random access resource set associated with the indicated number of Msg1 iterations for this random access procedure and configured only with RedCap indication and Msg1 iteration indication.

[0428] Otherwise, if a CFRA resource containing Msg1 iterations is provided to the random access procedure, and the number of Msg1 iterations is also specified in rach-ConfigDedicated, and RedCap is applicable to the current random access procedure:

[0429] You can select a random access resource set that is associated with the number of Msg1 iterations for this random access procedure and consists only of RedCap instructions and Msg1 iteration instructions.

[0430] Otherwise, in the LTM cell switch command MAC CE, a CFRA resource for a random access procedure is provided, a non-zero number of Msg1 iterations is indicated in the said LTM cell switch command MAC CE, and eRedCap(enhanced Reduced Capability) is applicable to the current random access procedure:

[0431] You can select a random access resource set that is associated with the number of Msg1 iterations for this random access procedure and consists only of eRedCap instructions and Msg1 iteration instructions.

[0432] Otherwise, if a CFRA resource containing Msg1 iterations is provided to the random access procedure, the number of Msg1 iterations is specified in rach-ConfigDedicated, and eRedCap is applicable to the current random access procedure:

[0433] You can select a random access resource set that is associated with the number of Msg1 iterations for this random access procedure and consists only of eRedCap instructions and Msg1 iteration instructions.

[0434] Otherwise, if a CFRA resource for a random access procedure is provided, RedCap is applicable to the current random access procedure, and there exists a set of random access resources consisting solely of RedCap instructions; or

[0435] Where a CFRA resource for a random access procedure is provided, eRedCap is applicable to the current random access procedure, and there exists a set of random access resources consisting solely of eRedCap instructions; or

[0436] If CFRA resources are provided for a random access procedure, eRedCap is applicable to the current random access procedure, and there is no random access resource set consisting solely of eRedCap instructions but there is one random access resource set consisting solely of RedCap instructions:

[0437] For this random access procedure, a set of random access resources can be selected.

[0438] else:

[0439] If a random access procedure is initiated by a PDCCH order, the PRACH association indicator field of the DCI is set to 1, and the SSB-MTC-AdditionalPCI is configured by the upper layers, a random access resource set corresponding to the additionalPCI associated with the active TCI states can be selected.

[0440] Otherwise, if the random access procedure is initiated by a PDCCH order for an LTM candidate cell, a random access resource set corresponding to the Cell indicator field in the PDCCH order can be selected.

[0441] Otherwise, if a CFRA resource for a random access procedure is provided in the LTM cell switch command MAC CE and a non-zero number of Msg1 repetitions is indicated in the LTM cell switch command MAC CE, a set of random access resources consisting only of Msg1 repetition instructions can be selected that is associated with the indicated number of Msg1 repetitions for this random access procedure.

[0442] Otherwise, if a CFRA resource containing Msg1 iterations is provided for this random access procedure and the number of Msg1 iterations is specified in rach-ConfigDedicated, a set of random access resources can be selected that is associated with the specified number of Msg1 iterations for this random access procedure and also consists only of Msg1 iteration instructions.

[0443] The following explains that when selecting an RO, the relevant preamble and SSB values ​​can be provided via RRC / MAC CE signaling or PDCCH order.

[0444] If a CFRA resource for a beam failure recovery request associated with at least one of the SSBs or CSI-RSs is explicitly provided by the RRC; and

[0445] If at least one of the SSBs in candidateBeamRSList has an SS-RSRP exceeding rsrp-ThresholdSSB, or at least one of the CSI-RSs in candidateBeamRSList has a CSI-RSRP exceeding rsrp-ThresholdCSI-RS, then:

[0446] You can select an SSB among the SSBs in candidateBeamRSList that has an SS-RSRP exceeding rsrp-ThresholdSSB, or a CSI-RS among the CSI-RSs in candidateBeamRSList that has a CSI-RSRP exceeding rsrp-ThresholdCSI-RS.

[0447] If CSI-RS is selected, and there is no ra-PreambleIndex associated with the selected CSI-RS:

[0448] You can set the PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected CSI-RS and the quasi-colocated SSB in candidateBeamRSList.

[0449] else:

[0450] From the random access preamble set for beam failure recovery requests, PREAMBLE_INDEX can be set to the ra-PreambleIndex corresponding to the selected SSB or CSI-RS.

[0451] Otherwise, if ra-PreambleIndex is explicitly provided by PDCCH and ra-PreambleIndex is not 0b000000, PREAMBLE_INDEX can be set to the ra-PreambleIndex provided as a signal and the SSB indicated by the signal by PDCCH can be selected.

[0452] Otherwise, if the CFRA resource is explicitly provided by the LTM cell switch command MAC CE and the SS-RSRP of the SSB indicated by the LTM cell switch command MAC CE exceeds rsrp-ThresholdSSB, the random access preamble index indicated by the signal of the LTM cell switch command MAC CE can be set to PREAMBLE_INDEX and the SSB indicated by the LTM cell switch command MAC CE can be selected.

[0453] Otherwise, if CFRA resources are not explicitly provided by the LTM cell switch command MAC CE, and random access procedures are not initiated for recovery using the LTM candidate configuration, and CFRA resources associated with the SSBs are explicitly provided in rach-ConfigDedicated, and at least one of the associated SSBs is available that has an SS-RSRP exceeding rsrp-ThresholdSSB, then the SSB among the associated SSBs that has an SS-RSRP exceeding rsrp-ThresholdSSB can be selected, and PREAMBLE_INDEX can be set to the ra-PreambleIndex corresponding to the selected SSB.

[0454] Otherwise, if CFRA resources are not explicitly provided by the LTM cell switch command MAC CE, and random access procedures are not initiated for recovery using LTM candidate configurations, and CFRA resources associated with CSI-RSs are explicitly provided in rach-ConfigDedicated, and at least one CSI-RS among the associated CSI-RSs has a CSI-RSRP exceeding rsrp-ThresholdCSI-RS is available, then the CSI-RS among the associated CSI-RSs that has a CSI-RSRP exceeding rsrp-ThresholdCSI-RS can be selected, and PREAMBLE_INDEX can be set to the ra-PreambleIndex corresponding to the selected CSI-RS.

[0455] The following describes the random access operation in semi-static SBFDs.

[0456] In SBFD random access operations, two RO types can be provided. For RACH configuration Option 1, RO is configured with a single legacy RACH configuration, which can consist of an additional RO within SBFD symbols and a legacy RO within non-SBFD symbols / flexible SBFD symbols. For RACH configuration Option 2, RO can be configured with a legacy RACH configuration and an additional RACH configuration. In this case, the legacy RO within non-SBFD symbols can be configured with the legacy RACH configuration, and the additional RO within SBFD symbols (and / or non-SBFD symbols) can be configured with the additional RACH configuration.

[0457] For a UE aware of an SBFD in the RRC CONNECTED state (SBFD-aware UE), both Option 1 and Option 2 may be supported, but a configuration enabling both options simultaneously for a single UE may not be supported. Additionally, the UE may not be required to support both options.

[0458] Alt 1-1 in Option 1 is a method of operating RO based only on the existing parameters of a single configuration while using a single RACH configuration, for example, at least one of whether or how the msg1-FrequencyStart parameter in rach-ConfigCommon is reinterpreted, RO validation rules, SSB-RO mapping rules, etc. may be additionally considered. Option 2 is a method of using legacy RACH configuration and additional RACH configuration separately, for example, RO validation rules for additional RO, SSB-RO mapping rules, and / or whether all current parameters included in rach-ConfigCommon must be included in the additional RACH configuration, etc.

[0459] When applying Alt 1-1 of Option 1, legacy ROs, including ROs located in non-SBFD symbols and ROs located in SBFD symbols that are flexibly configured by tdd-UL-DL-ConfigurationCommon, may follow the legacy SSB-RO mapping rules. Meanwhile, for ROs located in SBFD symbols that are downlinked by tdd-UL-DL-ConfigurationCommon, a separate SSB-RO mapping distinct from the legacy ROs may be applied.

[0460] Additionally, Alt 2-1 may be supported in determining the lowest RO in the frequency domain of additional ROs within SBFD symbols in Alt 1-1 of Option 1. For example, according to Alt 2-1, the msg1-FrequencyStart parameter in rach-ConfigCommon can be reinterpreted as the frequency offset of the lowest RO in the frequency domain based on the lowest PRB of the UL usable PRBs, and an RO located outside the UL usable PRB area can be determined as an invalid RO.

[0461] When applying Option 2, legacy SSB-RO mapping rules are applied to additional ROs configured by additional RACH settings, but they can be operated separately from the SSB-RO mapping for legacy ROs configured by legacy RACH settings. In this case, the method of handling cases where legacy ROs and additional ROs overlap in the time or frequency domain may be additionally considered, for example, priority, selection rules, or exclusive application rules in the overlap situation may be defined separately.

[0462] Additionally, N within the additional ROs preamble rep When a PRACH transmission containing preamble repetitions is performed, the decision rules used in the current standard are reused, N preamble rep A set of valid additional ROs can be determined, and a time period to which the set applies can be determined. In this case, the time period for the set of valid additional ROs can be determined separately from the time period for legacy ROs.

[0463] In the present disclosure, additional ROs may be defined as follows. For Option 1, they may include ROs within SBFD symbols configured as downlinks by tdd-UL-DL-ConfigurationCommon, and ROs existing across SBFD symbols configured as downlinks and SBFD symbols configured as flexible. For Option 2, they may mean ROs configured by additional RACH configurations.

[0464] In terms of supporting random access operations for UEs aware of SBFDs in the RRC CONNECTED state (SBFD-aware UEs) through Option 2, according to Alt 2-3, additional ROs set on non-SBFD symbols by additional RACH settings may be considered invalid for SBFD-aware UEs, and specific processing rules for cases where additional ROs partially overlap with non-SBFD symbols may be additionally considered. On the other hand, according to Alt 2-4, additional ROs set on non-SBFD symbols by additional RACH settings may be configured to be valid for SBFD-aware UEs as well. Meanwhile, for legacy ROs set by legacy RACH settings, legacy RO validity rules and legacy SSB-RO mapping rules may be applied as they are for SBFD-aware UEs. In addition, for example, Option 2 supports Alt 2-3, so that additional ROs set on non-SBFD symbols by additional RACH settings can be treated as invalid for UEs that recognize SBFD.

[0465] With respect to Alt 1-1 of Option 1, as described above, legacy SSB-RO mapping may be applied to legacy ROs (e.g., ROs within non-SBFD symbols and ROs within SBFD symbols configured as flexible), and separate SSB-RO mapping may be applied to ROs within SBFD symbols configured as downlinks. Additionally, in Alt 1-1 of Option 1, a method of reusing legacy SSB-RO mapping rules for additional ROs may be considered, in which matters regarding the association period and association pattern period may be additionally considered.

[0466] In Option 2, legacy SSB-RO mapping rules are applied to additional ROs configured by additional RACH settings, but can be operated separately from the SSB-RO mapping for legacy ROs configured by legacy RACH settings, and the method of handling the overlap between legacy ROs and additional ROs can be additionally considered.

[0467] With respect to RO validation, for ROs within SBFD symbols set as downlinks by tdd-UL-DL-ConfigurationCommon in Alt 1-1 of Option 1, the following additional conditions may apply: (i) a valid RO may start after at least an Ngap symbol following the last downlink non-SBFD symbol, and (ii) a valid RO may start after at least an Ngap symbol following the SSB. Here, Ngap may be set to the same value as Ngap defined in the current specification.

[0468] An additional RO in Option 2 may be deemed valid if, for example, the following conditions are satisfied. The additional RO may satisfy the conditions that (i) it is located within an SBFD symbol, or that it may be configured to be valid even if it starts at an SBFD symbol and ends at a non-SBFD symbol within or across the same slot by network configuration, (ii) it starts at least after an Ngap symbol following the last downlink non-SBFD symbol, (iii) it starts at least after an Ngap symbol following the latest SSB, and (iv) it does not overlap with the SSB in the time domain. In this case, the Ngap may be the same value as the Ngap defined in the current specification. Additionally, it may be the responsibility of the network to ensure that the additional RO is configured within the bandwidth of UL available PRBs.

[0469] FIG. 10 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 (1010, which may be referred to as an “SBFD-aware terminal” or an “SBFD-aware UE”) refers to a terminal capable of performing SBFD operations, and a legacy UE (1120) may be understood as a terminal performing HD communication.

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

[0471] However, since the SBFD-aware UE (1010) 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 (1010), and can be set as an additional RO setting, that is, as a separate RO setting.

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

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

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

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

[0476] FIG. 11 illustrates an example of a flexible slot when the RO is configured by a legacy RO configuration, and FIG. 12 illustrates an example of a flexible slot when the RO is configured by a separate RO configuration. Since the legacy UE (1120) 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 (1110) 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 (1120) and SBFD-aware UEs (1110), 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.

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

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

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

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

[0481] FIG. 13 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.

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

[0483] In the following, a random access operation method suitable for cases where dynamic SBFD operation is supported is described. In this disclosure, it is assumed that dynamic SBFD intervals can be set or indicated in units of symbols, slots, and / or specific predefined patterns.

[0484] For example, in the present disclosure, a semi-static configuration is assumed as the default operation, and it may be assumed that the entire section can support a semi-static SBFD operation. In this case, the UE may dynamically receive information regarding the location of SBFD symbol resources through additional configuration and / or instructions from the base station, and the UE may define the dynamically configured and / or indicated resource section as a dynamic SBFD section. In the resource referred to as the dynamic SBFD section, dynamic SBFD operations in units of symbols, slots, and periods may be performed.

[0485] For example, semi-static SBFD intervals and dynamic SBFD intervals may be set and / or indicated simultaneously. In this case, semi-static SBFD intervals and dynamic SBFD intervals do not overlap. Dynamic SBFD intervals can be understood (recognized as to the existence and location of the resource) even by UEs in an inactive or standby state, but it can be assumed that which SBFD random access operation can actually be performed (which RO is valid) is determined or applied only when the RRC connected state is established.

[0486] In a situation where the SBFD segment is divided into a semi-static SBFD segment and a dynamic SBFD segment, the method of providing RACH settings for RO configuration may include multiple options. For example, the UE may be configured to share a single RACH setting across the semi-static SBFD segment and the dynamic SBFD segment, or it may be configured to provide different RACH settings for each of the semi-static SBFD segment and the dynamic SBFD segment. Additionally, if SBFD is not mandatory, RACH settings that allow setting non-SBFD segments may be included in the configuration options.

[0487] In addition, multiple operational rules may be defined regarding the setting and / or instruction relationship between semi-static SBFD sections and dynamic SBFD sections. For example, (i) it may be defined so that dynamic SBFD settings are not set and / or instruction when semi-static SBFD sections are set and / or instruction, or (ii) it may be defined so that dynamic SBFD operations are set and / or instruction only in sections where semi-static SBFD sections are not set. Furthermore, it may be defined so that after each section is assigned, the sections remain as semi-static SBFD sections and dynamic SBFD sections for at least a predetermined period. Alternatively, even if the sections are distinguished and indicated in this manner, switching between semi-static SBFD sections and dynamic SBFD sections may be applied according to subsequent settings and / or instructions.

[0488] At this time, the meaning of performing dynamic random access operations in the dynamic SBFD interval may include, for example, at least one of the following: First, the dynamic SBFD interval may support an SBFD symbol or slot in which at least one of a DL and / or UL subband or a UL and / or DL ​​available PRB of a frequency range different from that set in the semi-static SBFD interval is set or indicated. Second, in the dynamic SBFD interval, switching may be performed from an SBFD slot and / or symbol to a non-SBFD slot and / or symbol (DL-only or UL-only).

[0489] Accordingly, in a wireless communication system where semi-static SBFD periods and dynamic SBFD periods can be operated together, the UL subband or UL available PRB range may differ from the semi-static period during the dynamic SBFD period, or SBFD symbols or slots may be switched to non-SBFD symbols or slots that are DL-only or UL-only, so the identified RO may not always be located in a UL resource where PRACH preamble transmission is possible. For example, an RO calculated based on the semi-static SBFD period may be placed in a UL transmission-unavailable area of ​​the dynamic SBFD period, and if SBFD slots and / or symbols are switched to non-SBFD slots and / or symbols (DL-only or UL-only) during the dynamic SBFD period, the RO may be located in a frequency domain or time resource where UL transmission is unavailable depending on the switching result.

[0490] In such cases, unnecessary preamble transmission, random access failure, and connection delays may occur, and the possibility of resource conflicts may increase. Therefore, a technology is required in which a terminal determines the validity of an RO during a dynamic SBFD interval and transmits a preamble only to a valid RO. Accordingly, the method for determining the validity of an RO of a terminal proposed in this disclosure is described below.

[0491] First, if RACH configuration information for a dynamic SBFD section is separately specified, the UE can set the RO according to the parameters of said RACH configuration information. On the other hand, if separate RACH configuration information is not specified, a method of reusing RACH configuration information for a semi-static SBFD section may also be considered. In this case, if necessary, one or more parameters may be reinterpreted.

[0492] In the present disclosure, an RO configured through RACH configuration information related to a semi-static SBFD section may be referred to as a semi-static SBFD RO. Depending on the situation, a dynamic SBFD section may include a portion of the semi-static SBFD RO. Additionally, an RO configured through RACH configuration information related to a dynamic SBFD section may be referred to as a dynamic SBFD RO. If RACH configuration information separate from the SBFD exists, the RO configured in this case may be referred to as a non-SBFD RO.

[0493] CASE 1: When a separate RO is not set in the dynamic SBFD section

[0494] Option 1: Use the same RACH configuration information for the semi-static SBFD section and the dynamic SBFD section. In this case, the dynamic SBFD section may be configured or specified later within the semi-static SBFD section. Alternatively, the semi-static SBFD section and the dynamic SBFD section may be configured simultaneously but without overlapping. The commonly used RACH configuration information may be configured based on the semi-static SBFD section. In this case, the validation rule applied to the dynamic SBFD section may be as follows.

[0495] If set to only downlink (Only DL), it can be determined as an invalid RO.

[0496] If set to Uplink Only (Only UL), it can be determined as a Valid RO.

[0497] At this time, when an SBFD symbol changes to a UL symbol, an RO configured within a UL subband or UL available PRB may cause uplink resource fragmentation in the UL symbol.

[0498] To prevent this, new parameters related to the frequency offset may be introduced, or existing parameters such as msg1-FrequencyStart may be reinterpreted. For example, if the reference of the existing frequency offset is set to the lowest frequency PRB of the UL subband or UL available PRB, when switching to the UL symbol, the reference may be interpreted as the lowest frequency PRB (PRB0) of the uplink bandwidth portion (UL BWP) or the wideband, which is the entire bandwidth of the UL BWP.

[0499] When a downlink and / or uplink subband or a downlink and / or uplink available PRB of a different frequency is set with respect to the SBFD symbol of the semi-static SBFD section, only the RO included in the newly set UL subband can be determined as valid.

[0500] To increase RO configuration flexibility, new parameters related to frequency offset can be introduced or existing parameters can be reinterpreted.

[0501] In addition, the reference of the above frequency offset may be defined or interpreted, for example, as at least one of the following.

[0502] i) The reference can be the UL available PRB based on the semi-static SBFD interval or the lowest frequency PRB of the UL subband.

[0503] ii) The reference may be the lowest frequency PRB of the UL available PRB, UL subband, UL full bandwidth part, or UL full bandwidth based on the dynamic SBFD section.

[0504] iii) The reference can be interpreted as the lowest frequency PRB (PRB0) of the entire bandwidth of the UL BWP or UL BWP.

[0505] Option 2: If a dynamic SBFD section is subsequently configured or indicated within a semi-static SBFD section, all ROs in the section switched to the dynamic SBFD section may be invalidated. Additionally, if a semi-static SBFD section and a dynamic SBFD section are configured simultaneously but do not overlap, an RO can be configured only within the semi-static SBFD section using RACH configuration information. In this case, PRACH can be transmitted only within the semi-static SBFD section.

[0506] If the dynamic SBFD interval becomes long, there is a possibility that the random access capacity will decrease.

[0507] Option 3: The RO is configured considering a semi-static SBFD interval, and the UE can assume that the RO interval is always valid even if dynamic SBFD operation is supported in the area where the RO is configured in this way. That is, the base station can consider this assumption when configuring the dynamic SBFD interval. In this case, the RACH configuration information for the semi-static SBFD interval can be assumed to be legacy.

[0508] Additionally, when using some ROs among the semi-static SBFD ROs in a dynamic SBFD interval, dynamic masking may be considered for the semi-static SBFD ROs within the dynamic SBFD interval. Dynamic masking can be used to indicate dynamically allowed ROs. The masking and / or muting pattern may be predefined or set, or one of a plurality of predefined patterns may be dynamically indicated.

[0509] When RACH configuration information is applied to set semi-static SBFD ROs within a dynamic SBFD interval, dynamic masking may be considered for the semi-static SBFD ROs within the dynamic SBFD interval. Dynamic masking can be used to indicate dynamically allowed ROs. The masking / muting pattern may be predefined or configured, or one of multiple predefined patterns may be dynamically indicated. The masking and / or muting pattern may be defined based on dynamic SBFD symbols, slots, and / or periods. For example, the start of the pattern may be defined to coincide with the start of the dynamic SBFD interval. Also, for example, the start of the pattern may be defined to coincide with the start of the semi-static SBFD interval.

[0510] Meanwhile, the above methods may have relatively low RO configuration flexibility. To compensate for this, separate RACH configuration information can be introduced in the dynamic SBFD section.

[0511] CASE 2: When supporting separate RO configuration when setting or instructing dynamic SBFD intervals

[0512] If there are two or more dynamic SBFD segments, different RACH configuration information may be provided. For example, if there are three dynamic SBFD segments, the three RACH configuration information may each have related RO configuration parameters, such as a PRACH configuration index. To reduce overhead, based on the PRACH configuration information associated with the first dynamic SBFD segment that includes all identical parameters, RACH configuration information for the remaining dynamic SBFD segments may be set to include only parameters that do not have identical values. In this case, the dynamic SBFD RO may be set to be included in the UL available PRB or UL subband of the dynamic SBFD segment, and such an RO may be determined to be a valid RO. Conversely, if it falls outside the above segment, it may be determined to be invalid.

[0513] In addition, cases may be considered where a dynamic SBFD section is subsequently set or directed within a semi-static SBFD section. ROs set in the semi-static SBFD section and ROs set in the dynamic SBFD section may coexist. In this case, the following validation rules may be applied.

[0514] For example, all semi-static SBFD ROs can be deemed invalid. This prevents unnecessary nesting and can be advantageous for each SSB-RO mapping.

[0515] According to an embodiment, only ROs included in the UL subband, UL wideband, or UL available PRB among the semi-static SBFD ROs are classified as valid and can coexist with dynamic SBFD ROs. In this case, new parameters may be introduced or existing parameters may be reinterpreted so that the semi-static SBFD ROs satisfy the validity judgment rules of the dynamic SBFD section. The reference of the frequency offset may be set or interpreted as, for example, at least one of the following.

[0516] i) The reference can be the UL available PRB based on the semi-static SBFD interval or the lowest frequency PRB of the UL subband.

[0517] ii) The reference may be the UL available PRB based on the dynamic SBFD interval, or the UL subband, or the UL full bandwidth portion, or the lowest frequency PRB of the UL full bandwidth.

[0518] iii) The reference can be interpreted as the lowest frequency PRB (PRB0) of the entire bandwidth of the UL BWP or UL BWP.

[0519] Additionally, one may consider masking or muting only some of the ROs among the ROs set as dynamic SBFD ROs or the semi-static ROs included in the dynamic SBFD interval. Dynamic masking can be used to indicate dynamically allowed ROs. The masking and / or muting patterns may be predefined or configured, or one of multiple predefined patterns may be dynamically indicated. The masking and / or muting patterns may be defined based on dynamic SBFD symbols, slots, and / or periods. For example, the start of the pattern may be defined to coincide with the start of the dynamic SBFD interval. Also, for example, the start of the pattern may be defined to coincide with the start of the semi-static SBFD interval.

[0520] FIG. 14 illustrates a method of operation of a terminal. An embodiment of FIG. 14 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.

[0521] Referring to FIG. 14, the terminal (user equipment: UE) can receive semi-static configuration information for the first SBFD (Subband Full Duplex) section and dynamic configuration information for the second SBFD section from the base station (S141).

[0522] The above terminal may be, for example, a terminal that is aware of SBFD (subband full duplex).

[0523] For example, an SBFD section configured by the above semi-static configuration information can be called a semi-static SBFD section.

[0524] For example, the SBFD section configured by the above dynamic setting information can be called a dynamic SBFD section.

[0525] In the present disclosure, semi-static configuration information for the first SBFD interval may mean, for example, a set of parameters related to an SBFD time resource that a base station configures to a terminal via a higher layer (e.g., RRC layer) message.

[0526] For example, the above SBFD time resource (e.g., SBFD symbol) is not limited to being additionally set on a DL time resource, UL time resource, or flexible time resource, and may be set independently as a separate SBFD operation target time resource.

[0527] For example, a base station may provide tdd-UL-DL-ConfigurationCommon (TDD-UL-DL-ConfigCommon) through the ServingCellConfigCommonSIB information element (IE) included in SIB1, which is configuration information for providing common settings regarding a serving cell to a terminal, and through this, the terminal can obtain a basic TDD-UL-DL pattern at the cell level.

[0528] In addition, the above TDD-UL-DL-ConfigCommon may additionally include indices for specifying time intervals in which SBFD subbands are applied within the same TDD-UL-DL period. Specifically, the above TDD-UL-DL-ConfigCommon may include at least one of i) sbfd-StartingSlotIndex-r19 for setting the starting slot index of SBFD subbands within the TDD-UL-DL period, ii) sbfd-EndingSlotIndex-r19 for setting the ending slot index of SBFD subbands within the TDD-UL-DL period, iii) sbfd-StartingSymbolIndex-r19 for setting the starting symbol index within the starting slot of SBFD subbands within the TDD-UL-DL period, or iv) sbfd-EndingSymbolIndex-r19 for setting the ending symbol index within the ending slot of SBFD subbands within the TDD-UL-DL period. And, through this, the start slot or start symbol and the end slot or end symbol of the SBFD subband can be semi-statically set.

[0529] According to an embodiment, a base station may provide semi-static configuration information for defining an SBFD interval for a terminal through an RRCReconfiguration message. RRCReconfiguration is defined as a message capable of transmitting wireless resource configuration information and may transmit configurations including physical channel configuration for the terminal. The RRCReconfiguration may include a field for transmitting SIB1 exclusively. Specifically, dedicatedSIB1-Delivery OCTET STRING (CONTAINING SIB1) may be defined within RRCReconfiguration-IEs, thereby allowing the base station to exclusively transmit common configuration information included in SIB1 to a specific terminal.

[0530] In addition, frequency-related configuration information including SBFD-Subband-Allocation related parameters for dividing the first SBFD section into subbands from the perspective of frequency resources may be further provided to the terminal. For example, an SCS-SpecificCarrier may be provided through an RRC IE, and the SCS-SpecificCarrier may include an index for specifying the location and bandwidth of the frequency domains of the UL subband and the DL subband. The above SCS-SpecificCarrier may include sbfd-Subband-Allocation-r19, and the sbfd-Subband-Allocation-r19 may include at least one of i) ul-subbandlocationAndBandwidth-r19, which sets the location and bandwidth of the frequency domain of the UL subband; ii) firstDL-subbandlocationAndBandwidth-r19, which sets the location and bandwidth of the frequency domain of the first DL subband; or iii) secondDL-subbandlocationAndBandwidth-r19, which sets the location and bandwidth of the frequency domain of the second DL subband. And, through this, the location and bandwidth of the frequency domains of the DL subband and the UL subband can be semi-statically set.

[0531] Furthermore, the term "semi-static" as used in this disclosure may be based on the premise that the SBFD is a setting configured in advance for the terminal. Accordingly, semi-static setting information for the first SBFD section may include setting information for the SBFD section that is maintained valid for a certain period of time by the base station providing it to the terminal in the form of RRC IE and the terminal acquiring and applying it.

[0532] In comparison, in the present disclosure, dynamic configuration information for a second SBFD interval may mean a set of parameters related to an SBFD time resource that is dynamically indicated or activated by the base station to be updated in relatively short time intervals according to wireless channel conditions, traffic load, interference conditions, or network operation policies, separately from the SBFD interval pre-configured by the semi-static configuration information for the terminal.

[0533] For example, the dynamic setting information may include a location and range on the time resource of the second SBFD interval or SBFD resource usage rules applied in the second SBFD interval.

[0534] Additionally, the dynamic configuration information may be provided through a DCI-based instruction, which is a lower-layer (e.g., PHY layer) control signal transmitted from a base station to a terminal. Alternatively, depending on the embodiment, it may be provided through a MAC CE-based instruction.

[0535] Accordingly, in the present disclosure, semi-static configuration information for the first SBFD section provides an SBFD section and resource frame that are maintained for a relatively long period for the terminal, whereas dynamic configuration information for the second SBFD section makes it possible to additionally configure the second SBFD section or temporarily change the configuration as needed, thereby increasing the flexibility of SBFD operation.

[0536] The terminal can determine a valid Random Access Occasion (RO) based on at least one of the semi-static setting information or the dynamic setting information (S142). At this time, the validity of an RO located within the second SBFD section (dynamic SBFD section) can be determined based on whether it is included in an uplink (UL) subband or UL usable Physical Resource Block (PRB) area set for the second SBFD section (dynamic SBFD section).

[0537] For example, ROs may be set / instructed based on RACH setting information. The RACH setting information may include, for example, information about an SSB, information about ROs related to the SSB, or at least one of mask information indicating or informing a specific RO among the ROs. These ROs may be located in a first SBFD section (semi-static SBFD section) or a second SBFD section (dynamic SBFD section). For an RO located within an SBFD section among the ROs, it may be determined to be a valid RO only if it is included in the uplink subband or UL available PRB area set for the second SBFD section (dynamic SBFD section), and otherwise determined to be an invalid RO.

[0538] FIG. 15 illustrates a process for determining the validity of an RO located within the second SBFD interval (dynamic SBFD interval). Some descriptions, functions, procedures, suggestions, methods, and / or operations of the above embodiments may be omitted.

[0539] FIG. 15 assumes a case where the first SBFD section (semi-static SBFD section) and the second SBFD section (dynamic SBFD section) do not overlap, FIG. 15 (a) is a case where the RO is located outside the UL subband or UL available PRB area set for the second SBFD section, and FIG. 15 (b) is a case where the RO is located within the UL subband or UL available PRB area set for the second SBFD section. The area excluding the UL subband and UL available PRB area is assumed to be the DL subband or DL ​​available PRB area.

[0540] In this case, in the case of FIG. 15 (a), when determining the validity of ROs located within the second SBFD section, since the ROs located within the second SBFD section are located outside the UL subband or UL available PRB area set for the second SBFD section, according to the method proposed in this disclosure, the ROs can be determined to be invalid.

[0541] On the other hand, in the case of FIG. 15(b), when determining the validity of ROs located within the second SBFD interval, since the ROs located within the second SBFD interval are located within the UL subband or UL available PRB area set for the second SBFD interval, according to the method proposed in the present disclosure, the ROs can be determined to be valid.

[0542] Referring again to FIG. 14, the random access opportunity may be referred to by other terms, such as PRACH opportunity, RO, etc.

[0543] According to an embodiment, if the second SBFD section is set as a downlink (DL) exclusive section, the RO located within the second SBFD section may be determined to be invalid. Since the section set as a downlink exclusive section cannot be considered to be included in the uplink (UL) subband or the UL usable PRB (Physical Resource Block) area, the RO in that section may be excluded from the preamble transmission target.

[0544] According to an embodiment, if the second SBFD section is set as an uplink-only section, the RO located within the second SBFD section can be determined to be valid. Since the section set as an uplink-only section can be considered to be included in the uplink (UL) subband or UL usable PRB (Physical Resource Block) area, the RO in the section can be included in the preamble transmission target.

[0545] According to an embodiment, if the RO located within the second SBFD section is included within the uplink subband or the UL available PRB area, the RO located within the second SBFD section can be determined to be valid.

[0546] According to an embodiment, if the RO located within the second SBFD section is located outside the uplink subband or the UL available PRB area, the RO located within the second SBFD section may be determined to be invalid.

[0547] An RO determined to be invalid in this manner may be treated as not allowing preamble transmission.

[0548] For example, the terminal can perform a preamble transmission from a resource set excluding the RO determined to be invalid.

[0549] According to an embodiment, the RO can be identified based on a parameter related to a frequency offset.

[0550] According to an embodiment, when identifying an RO located within the second SBFD section, the reference of the frequency offset may be the lowest frequency PRB of the uplink subband or the lowest frequency PRB of the UL available PRB area.

[0551] According to an embodiment, when the second SBFD section is set as an uplink-only section, in identifying an RO located within the second SBFD section, the reference of the frequency offset may be the lowest frequency PRB of the UL Bandwidth Part (BWP) or the lowest frequency PRB of the UL wideband.

[0552] Here, identifying the RO may include an action of specifying the location or range of the RO.

[0553] At this time, the terminal can determine the validity of the RO by aligning the frequency position of the RO according to the interpretation of the reference of the frequency offset.

[0554] According to an embodiment, if the second SBFD section is set or indicated within the first SBFD section after the first SBFD section is set, the RO located within the second SBFD section may be determined to be invalid.

[0555] According to an embodiment, if the first SBFD section and the second SBFD section are simultaneously set or indicated and the second SBFD section is set or indicated outside the first SBFD section, RO may be set only within the first SBFD section.

[0556] The above terminal can transmit a preamble from the valid RO to the base station (S143).

[0557] For example, the above preamble may also be called message 1 (message 1; Msg1).

[0558] Here, based on transmitting the above preamble to the base station, a Random Access (RA) process can be performed.

[0559] According to an embodiment, the terminal determining the valid random access opportunity (RO) (in other words, determining the validity of the random access opportunity (RO)) may include the terminal receiving Random Access Channel (RACH) setting information that is commonly applied to the first SBFD section and the second SBFD section from the base station, and identifying the RO based on the RACH setting information.

[0560] According to an embodiment, the RACH configuration information may include a set of parameters provided by a base station to a terminal to determine the RO to transmit a preamble and to perform a preamble transmission operation when the terminal performs a random access procedure. According to an embodiment, the RACH configuration information may include parameters provided by the configuration of the RRC layer, and may also be implemented in a form that further includes parameters dynamically indicated or activated by MAC layer or physical layer control.

[0561] According to an embodiment, the RACH setting information may include parameters related to the preamble transmission operation of the terminal. For example, preambleReceivedTargetPower, which sets the preamble target reception power, and preambleTransMax, which sets the maximum number of preamble transmissions.

[0562] Alternatively, it may include powerRampingStep, etc., for setting power ramping steps.

[0563] According to an embodiment, the terminal determining the valid random access opportunity (RO) may include the terminal receiving from the base station first RACH setting information applied to the first SBFD section and second RACH setting information applied to the second SBFD section, and i) identifying an RO located within the first SBFD section based on the first RACH setting information and ii) identifying an RO located within the second SBFD section based on the second RACH setting information.

[0564] According to an embodiment, if there are multiple second SBFD segments, the terminal may use different RACH setting information for each of the multiple second SBFD segments. In this case, the RACH setting information applied to one of the multiple second SBFD segments includes all parameters regarding RACH setting, and the RACH setting information applied to each of the remaining second SBFD segments may include only parameters having values ​​different from the all parameters. This allows for a reduction in communication overhead.

[0565] According to an embodiment, in transmitting a preamble to a base station, the terminal may include an operation of receiving information regarding masking or muting, applying masking or muting to an RO located within the second SBFD interval based on the information regarding masking or muting, and determining an allowed RO based on the result of applying the masking or muting.

[0566] For example, in addition to determining the validity of the RO in step S142 of FIG. 14, an additional operation to select an RO for preamble transmission may be performed. For example, when the masking or muting is applied, among the ROs that the terminal has determined to be valid, an RO that is allowed to transmit the preamble (allowed RO) may be additionally selected based on the result of applying the masking or muting.

[0567] Here, the masking or muting may be applied to the RO(s) located within the second SBFD section among the ROs derived by the RACH setting information applied to the first SBFD section.

[0568] The information regarding the masking or muting above is information indicating one of the predetermined masking or muting patterns, and said patterns may be defined based on the symbol, slot, or period of the second SBFD interval.

[0569] For example, the starting point of the above patterns may be defined to coincide with the starting point of the second SBFD interval or the first SBFD interval.

[0570] According to an embodiment, the random access process for the terminal may be triggered by a media access control control element (MAC CE).

[0571] Alternatively, according to an embodiment, the random access process for the terminal may be triggered by a physical downlink control channel (PDCCH) order.

[0572] The PDCCH command can be instructed to the terminal, for example, through DCI format 1_0.

[0573] The method of FIG. 14 is related to a random access process, and the random access process may be a contention-free random access (CFRA) process.

[0574] For example, in a situation where random access is triggered by a MAC CE or PDCCH command, the terminal can determine the validity of the RO according to the SBFD interval according to the method of FIG. 14.

[0575] FIG. 16 illustrates a signaling process between a base station and a terminal related to a random access process. An embodiment of FIG. 16 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiments may be omitted.

[0576] Referring to FIG. 16, the base station can transmit semi-static configuration information for the first SBFD section and dynamic configuration information for the second SBFD section to the terminal (S161).

[0577] As described above, the SBFD section configured by the semi-static configuration information can be referred to as a semi-static SBFD section, and the SBFD section configured by the dynamic configuration information can be referred to as a dynamic SBFD section.

[0578] The terminal determines a valid RO based on at least one of the semi-static setting information or the dynamic setting information, wherein the validity of an RO located within the second SBFD section is determined based on whether it is included in an uplink (UL) subband or a UL usable PRB (Physical Resource Block) area set for the second SBFD section (S162).

[0579] ROs determined to be invalid may be treated as not allowing preamble transmission. Therefore, preamble transmission may be possible only in subsequent steps with valid ROs.

[0580] The base station can receive a preamble from the terminal in an effective RO (S163).

[0581] The specific signaling process between the base station and the terminal can be performed by referring to the method described above in FIG. 14.

[0582] The method disclosed in FIGS. 14 to 16 can be operated as follows when viewed from the perspective of a base station.

[0583] The base station can transmit semi-static configuration information for the first SBFD (Subband Full Duplex) section and dynamic configuration information for the second SBFD section to the terminal.

[0584] Subsequently, the base station may receive a preamble from the terminal at the valid RO. Among the valid ROs, the RO located within the second SBFD section may be an RO whose validity is determined based on whether it is included in the uplink (UL) subband or UL usable Physical Resource Block (PRB) area set for the second SBFD section.

[0585] According to the method of the present disclosure, a random access process can be efficiently performed even in a wireless communication system where resources of the SBFD method and existing HD method are mixed. In particular, by eliminating ambiguity in determining the validity of RO and transmitting preambles during dynamic SBFD operation, unnecessary PRACH transmissions or resource collisions can be suppressed, thereby simultaneously improving the success rate of random access and resource efficiency.

[0586] According to the present disclosure, increased ROs can be effectively utilized in a wireless communication system where SBFD resources can be used, thereby improving the performance of the random access process.

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

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

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

[0590] At least one processor (102) receives semi-static configuration information for a first SBFD (Subband Full Duplex) section and dynamic configuration information for a second SBFD section from a second wireless device (200), determines a valid Random Access Occasion (RO) based on at least one of the semi-static configuration information or the dynamic configuration information, and transmits a preamble from the valid RO to the second wireless device (200), wherein the validity of an RO located within the second SBFD section is determined based on whether it is included in an uplink (UL) subband or UL usable Physical Resource Block (PRB) area configured for the second SBFD section. The specific operation has been described above with reference to FIGS. 14 and 15.

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

[0592] The processor (202) transmits semi-static configuration information for a first SBFD (Subband Full Duplex) section and dynamic configuration information for a second SBFD section to a first wireless device (100), and the second wireless device (200) receives a preamble from the first wireless device (100) at a valid random access occasion (RO), wherein the validity of an RO located within the second SBFD section among the valid ROs is determined based on whether it is included in an uplink (UL) subband or UL usable physical resource block (PRB) area configured for the second SBFD section. The specific operation has been described above with reference to FIGS. 14 to 16.

[0593] Figure 18 illustrates another example of a wireless device.

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

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

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

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

[0598] For example, in at least one computer-readable storage medium (CRM) comprising instructions that are executed by at least one processor to perform operations,

[0599] The above operations include receiving semi-static configuration information for a first SBFD (Subband Full Duplex) section and dynamic configuration information for a second SBFD section from a base station, determining a valid Random Access Occasion (RO) based on at least one of the semi-static configuration information or the dynamic configuration information, and transmitting a preamble from the valid RO to the base station, wherein the RO located within the second SBFD section is determined to be valid based on whether it is included in an uplink (UL) subband or UL usable Physical Resource Block (PRB) area configured for the second SBFD section. The specific operations have been described above with reference to FIGS. 14 to 16.

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

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

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

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

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

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

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

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

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

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

[0610] FIG. 20 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. 17.

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

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

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

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

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

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

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

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

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

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

[0621] Referring to FIG. 21, 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 in the number of multiple units.

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

[0623] 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. 21 may be the memory (104, 204) of FIG. 17.

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

[0625] 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. 21 may be the transceiver (106, 206) of FIG. 17.

[0626] Although not illustrated in FIG. 21, 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).

[0627] FIG. 21 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. 21. 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.

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

[0629] Referring to FIG. 22, 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.

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

[0631] 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 uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and inter-base station communication (150c) (e.g., relay, IAB (Integrated Access Backhaul) and various wireless access technologies (e.g., 5G NR). 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.

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

[0633] In this specification, formulas and mathematical expressions may be used interchangeably.

Claims

In terms of method, The terminal (user equipment: UE) receives semi-static configuration information for a first SBFD (Subband Full Duplex) section and dynamic configuration information for a second SBFD section from a base station; The terminal determines a valid random access occasion (Random access Occasion; RO) based on at least one of the semi-static setting information or the dynamic setting information; and The above terminal transmits a preamble from the above effective RO to the above base station, A method characterized by determining the validity of an RO located within the second SBFD section based on whether it is included in an uplink (UL) subband or a UL usable Physical Resource Block (PRB) area set for the second SBFD section. A method according to claim 1, characterized in that when the second SBFD section is set as a downlink (DL) exclusive section, the RO located within the second SBFD section is determined to be invalid. A method according to claim 1, characterized in that when the second SBFD section is set as an uplink-only section, the RO located within the second SBFD section is determined to be valid. A method according to claim 1, characterized in that if the RO located within the second SBFD section is included within the uplink subband or the UL available physical resource block area, the RO located within the second SBFD section is determined to be valid. A method according to claim 1, characterized in that if the RO located within the second SBFD section is located outside the uplink subband or the UL available physical resource block area, the RO located within the second SBFD section is determined to be invalid. A method according to claim 1, wherein the random access opportunity is identified based on a parameter related to a frequency offset. A method according to claim 6, wherein when identifying the RO located within the second SBFD section, the reference of the frequency offset is the lowest frequency PRB of the uplink subband or the lowest frequency PRB of the UL available physical resource block area. A method according to claim 6, wherein when the second SBFD section is set as an uplink-only section, in identifying the RO located within the second SBFD section, the reference of the frequency offset is the lowest frequency PRB of the UL Bandwidth Part (BWP) or the lowest frequency PRB of the UL wideband. A method according to claim 1, wherein the terminal determining the validity of the random access opportunity includes the terminal receiving Random Access Channel (RACH) setting information that is commonly applied to the first SBFD section and the second SBFD section from the base station, and identifying the RO based on the RACH setting information. A method according to claim 1, wherein the terminal determining the validity of the random access opportunity comprises receiving from the base station first Random Access Channel (RACH) setting information applied to the first SBFD section and second RACH setting information applied to the second SBFD section, and i) identifying an RO located within the first SBFD section based on the first RACH setting information and ii) identifying an RO located within the second SBFD section based on the second RACH setting information. A method according to claim 10, wherein, when the second SBFD segments are multiple, the terminal applies different second RACH setting information to each of the multiple second SBFD segments. A method according to claim 11, wherein RACH setting information applied to one of the plurality of second SBFD segments includes all parameters regarding RACH setting, and RACH setting information applied to each of the remaining second SBFD segments among the plurality of second SBFD segments includes only parameters having values ​​different from the all parameters. A method according to claim 10, characterized in that if the second SBFD section is set or indicated within the first SBFD section after the first SBFD section is set, the RO identified by the first RACH setting information is determined to be invalid. A method according to claim 10, characterized in that, when the second SBFD section is set or indicated within the first SBFD section after the first SBFD section is set, the RO included in the uplink subband, UL available physical resource block area, or UL wideband among the ROs identified by the first RACH setting information is determined to be valid. A method according to claim 1, wherein transmitting the preamble to the base station comprises the terminal receiving information regarding masking or muting, applying masking or muting to the RO located within the second SBFD interval based on the information regarding masking or muting, and determining an allowed RO where transmission of the preamble is permitted based on the result of applying the masking or muting. A method according to claim 15, wherein the masking or muting is applied to the RO located within the second SBFD section among the ROs identified by the RACH (Random Access Channel) setting information applied to the first SBFD section. A method according to claim 15, wherein the information regarding the masking or muting is information indicating one of the predetermined masking or muting patterns, wherein the patterns are defined based on the symbol, slot, or period of the second SBFD interval. A method according to claim 17, characterized in that the starting point of the patterns is defined to coincide with the starting point of the second SBFD interval or the first SBFD interval. 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, Receiving semi-static configuration information for the first SBFD (Subband Full Duplex) section and dynamic configuration information for the second SBFD section from a base station; Determining a valid random access occasion (Random access Occasion; RO) based on at least one of the above semi-static setting information or the above dynamic setting information; and Transmit the preamble from the above effective RO to the above base station, A terminal characterized by determining the validity of an RO located within the second SBFD section based on whether it is included in an uplink (UL) subband or a UL usable Physical Resource Block (PRB) area set for the second SBFD section. The device, 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, Receiving semi-static configuration information for the first SBFD (Subband Full Duplex) section and dynamic configuration information for the second SBFD section from a base station; Determining a valid random access occasion based on at least one of the above semi-static setting information or the above dynamic setting information; and Transmit the preamble from the above effective RO to the above base station, A device characterized by determining the validity of an RO located within the second SBFD section based on whether it is included in an uplink (UL) subband or a UL usable Physical Resource Block (PRB) area set for the second SBFD section. In 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, Receiving semi-static configuration information for the first SBFD (Subband Full Duplex) section and dynamic configuration information for the second SBFD section from a base station; Determining a valid random access occasion (Random access Occasion; RO) based on at least one of the above semi-static setting information or the above dynamic setting information; and Transmit the preamble from the above effective RO to the above base station, A CRM comprising an operation to determine validity based on whether an RO located within the second SBFD section is included in an uplink (UL) subband or UL usable Physical Resource Block (PRB) area set for the second SBFD section. In terms of method, The base station transmits semi-static configuration information for a first SBFD (Subband Full Duplex) section and dynamic configuration information for a second SBFD section to a terminal (user equipment: UE); and The above base station receives a preamble from the terminal in the valid RO, A method characterized in that the RO located within the second SBFD section among the above effective ROs is an RO included in the uplink (UL) subband or UL usable Physical Resource Block (PRB) area set for the second SBFD section. The base station 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, Transmitting semi-static configuration information for the first SBFD (Subband Full Duplex) section and dynamic configuration information for the second SBFD section to a terminal (user equipment: UE); and A preamble is received from the terminal in the valid RO, A method characterized in that the RO located within the second SBFD section among the valid ROs is an RO included in the uplink (UL) subband or UL usable Physical Resource Block (PRB) area set for the second SBFD section.

Images