Method and device for carrying out random access procedure in communication system

Abstract

The present disclosure relates to application of mapping between an SSB and an RO in a communication system having different types of ROs, wherein a terminal receives information defining PRACH occasions (ROs) related to the SSB, and transmits a random access preamble in at least one RO among the ROs, wherein the ROs include first type ROs and second type ROs, and SSB start indices of the second type ROs within a specific mapping cycle of the SSB and the RO are determined on the basis of SSB start indices of the second type ROs within a mapping cycle immediately before the specific mapping cycle and the number of SSBs related to the first type ROs.

Description

Method and device for performing a random access process in a communication system

[0001] The present disclosure relates to a wireless communication system, and to a method and apparatus in which a terminal performs a random access process when different types of random access opportunities are defined.

[0002] Wireless access systems are being widely deployed to provide various types of communication services, such as voice and data. Generally, a wireless access system is a multiple access system capable of supporting communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.). Examples of multiple access systems include CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access) systems.

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

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

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

[0006] Meanwhile, in the prior art, a RACH opportunity (random access channel occasion; this may also be expressed by other terms such as physical random access channel (PRACH) occasion, random access occasion, etc., and these terms may be abbreviated as RO) for transmitting a preamble for random access was set only in HD resources (non-SBFD resources), but in wireless communication systems after NR, RO can be set not only in HD resources but also in SBFD resources. In this case, different types of ROs can coexist, such as ROs set in non-SBFD resources like HD resources and ROs set in SBFD resources.

[0007] An RO can be associated with / related to an SSB (Synchronization Signal Block, which may also be referred to as an SS / PBCH block). For example, an SSB can be mapped to one or more ROs. The terminal can select the SSB of the highest quality among several SSBs and transmit a preamble for random access from the RO mapped to the selected SSB.

[0008] This SSB-RO mapping was conventionally defined only for the RO of HD resources, but as mentioned above, since RO of FD resources will also be introduced in future communication systems, it is difficult to use the conventional technology as is. In particular, if the number of ROs for HD resources and ROs for FD resources is set differently, it may be a problem how to determine the SSB-RO mapping rule.

[0009] In addition, if the number of ROs for HD resources and ROs for FD resources are different, it may be a problem how to ensure diversity of SSBs mapped to each RO.

[0010] The technical problem that the present disclosure aims to solve relates to a wireless communication system and provides a method and apparatus in which a terminal performs a random access process in different types of random access opportunities (ROs).

[0011] In one aspect, a method of operation of a terminal is provided. According to the method, the terminal receives information defining physical random access channel occasions (ROs) related to an SSB, and transmits a random access preamble from at least one of the ROs, wherein the ROs include first type ROs and second type ROs, and the SSB start index of the second type ROs within a specific mapping cycle of the SSB and RO is determined based on the SSB start index of the second type ROs within the mapping cycle immediately preceding the specific mapping cycle and the number of SSBs related to the first type ROs.

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

[0013] In another aspect, a method of operation of a base station is provided. According to the method, the base station transmits information defining physical random access channel occasions (ROs) related to an SSB to a terminal, and receives a random access preamble from at least one of the ROs from the terminal, wherein the ROs include first type ROs and second type ROs, and the SSB start index of the second type ROs within a specific mapping cycle of an SSB and an RO is determined based on the SSB start index of the second type ROs within the mapping cycle immediately preceding the specific mapping cycle and the number of SSBs related to the first type ROs.

[0014] In another aspect, a base station that executes the above method is provided.

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

[0016] According to the present disclosure, an SSB index associated with a second type of RO (e.g., SBFD RO) can be mapped by taking into account the number of first type of RO (e.g., non-SBFD RO). As a result, even if the number of second type ROs is less or more than the number of first type ROs, diversity of SSB indices mapped to second type ROs within each mapping cycle can be ensured.

[0017] Through this, when various SSB indexes are sequentially mapped to various ROs, RACH resources can be provided more fairly distributed across a wider variety of beams (SSB indexes). This can prevent the load from being concentrated on specific ROs and contribute to increasing the overall RACH success rate.

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

[0019] The accompanying 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0035] FIG. 16 illustrates an example in which an SBFD according to one embodiment of the present disclosure is applied to a DL slot among resources consisting of a DL slot and a UL slot.

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

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

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

[0039] Figure 20 illustrates the mapping between ROs of two RO types and SSBs.

[0040] Figure 21 illustrates a problem that can occur when using a single SSB-RO mapping for different types of ROs.

[0041] Figure 22 illustrates SSB-RO mapping by Method 1.

[0042] Figure 23 illustrates an SSB-RO mapping that uses separate sets of SSBs for each RO type.

[0043] Figure 24 shows an example where the SSB index associated with each RO type is different for each mapping cycle.

[0044] Figure 25 shows an example of sequentially mapping SSB indexes to non-SFBD ROs, and then sequentially mapping SSB indexes to SFBD ROs.

[0045] Figure 26 illustrates a case where the associated SSB indices in SBFD ROs are not consecutive.

[0046] Figure 27 illustrates another case where the associated SSB indices in SBFD ROs are not consecutive.

[0047] FIG. 28 illustrates a method of operation of a terminal according to the present disclosure.

[0048] FIG. 29 illustrates a signaling and operation method between a base station and a terminal.

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

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

[0051] Figure 32 illustrates an example of a signal processing module structure.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0080] Referring to FIG. 1, when a terminal is turned on again after being turned off or newly enters a cell, it performs an initial cell search operation, such as synchronizing with a base station (S11). Specifically, the terminal receives a Primary Synchronization Channel (P-SCH) and a Secondary Synchronization Channel (S-SCH) from the base station, synchronizes with the base station, and obtains information such as a cell ID. Afterward, the terminal can obtain cell broadcast information by receiving a Physical Broadcast Channel (PBCH) signal from the base station. Meanwhile, during the initial cell search phase, the terminal can check the downlink channel status by receiving a Downlink Reference Signal (DL RS).

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

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

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

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

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

[0086] Wireless resource structure

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

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

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

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

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

[0092] [Table 1]

[0093]

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

[0095] [Table 2]

[0096]

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

[0098] [Table 3]

[0099]

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

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

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

[0103] [Table 4]

[0104]

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

[0106] [Table 5]

[0107]

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

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

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

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

[0112] 1. DL only setting

[0113] 2. UL only setting

[0114] 3. Mixed UL-DL Settings

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

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

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

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

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

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

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

[0122] Transmission operation:

[0123] Common SN;

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

[0125] Individual encryption for source and target cells.

[0126] Receiving operation:

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

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

[0129] Common PDCP reordering;

[0130] Sequential delivery and duplicate detection;

[0131] Common buffer management.

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

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

[0134] UE RF / Baseband Requirements

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0151] The UE is N for the target MCG cells targetpdcch-BlindDetectionMCG1-UE can be provided to indicate the ability to monitor the maximum number of PDCCH candidates per slot corresponding to downlink cells, and for the source MCG N cells source pdcch-BlindDetectionMCG2-UE may be provided to indicate the ability to monitor the maximum number of PDCCH candidates per slot corresponding to a downlink cell. If the UE is provided with a search space set for both the target MCG and the source MCG, the UE expects that no USS set in any slot will have any assigned PDCCH candidates for both the target MCG and the source MCG.

[0152] Full duplex operation for NR

[0153] In 5G, new service types such as XR (Extended Reality), AI-based services, and self-driving cars are emerging. In these services, traffic becomes flexible in both 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.

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

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

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

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

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

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

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

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

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

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

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

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

[0166] RACH (random access channel) procedure

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

[0168] Settings for PRACH transmission.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0192] [Table 6]

[0193]

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

[0195] For unpaired spectra:

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

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

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

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

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

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

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

[0204] [Table 7]

[0205]

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

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

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

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

[0210] T switch is the switching gap duration.

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

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

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

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

[0215] [Table 8]

[0216]

[0217]

[0218]

[0219]

[0220]

[0221]

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

[0223] [Table 9]

[0224]

[0225]

[0226]

[0227]

[0228]

[0229]

[0230]

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

[0232] [Table 10]

[0233]

[0234]

[0235]

[0236]

[0237]

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

[0239] [Table 11]

[0240]

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

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

[0243] OFDM baseband signal generation for PRACH

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

[0245] [Equation 1]

[0246]

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

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

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

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

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

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

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

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

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

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

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

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

[0259] [Equation 2]

[0260]

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

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

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

[0264] Δ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 tRA N dur RA +14n slot RA It is given as follows:

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

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

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

[0268] n slot RA is given as follows:

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

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

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

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

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

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

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

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

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

[0278] [Table 12]

[0279]

[0280] PRACH repetition

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

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

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

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

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

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

[0287] <Slot Settings>

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

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

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

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

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

[0293] ii) pattern1.

[0294] pattern1 can provide the following:

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

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

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

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

[0299] Uplink symbols u by nrofUplinkSymbols sym .

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

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

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

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

[0304] Pattern 2 can provide the following.

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

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

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

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

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

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

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

[0312] Among the S2 slots, the first d slots,2 The slot contains only downlink symbols, and the last u slots,2 The slot contains only uplink symbols. The first d slots,2 d after the slot sym,2 The symbol is a downlink symbol. The last u slots,2 u prior to the slot sym,2 The symbol is an uplink symbol. The remainder (S2-d slots,2 -u slots,2 )-N symb slot - d sym,2 -u sym,2 is a flexible symbol.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0346] If UE

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0373] UE Procedure for Determining Slot Format

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0393] [Table 13]

[0394]

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

[0396] For paired spectral operation for the UE of the serving cell, the SFI index field of DCI format 2_0 indicates a combination of slot formats including the slot format combination for the reference DL BWP and the slot format combination for the reference UL BWP of the serving cell. The UE uses the reference SCS setting μ for the slot format combination indicated by the SFI index field value of DCI format 2_0 for the reference DL BWP of the serving cell, determined by the subcarrier spacing. SFI,DL It is provided. subcarrierSpacing2 is the reference SCS setting μ for the slot format combination indicated by the SFI index field value of DCI format 2_0 for the serving cell's reference UL BWP. SFI,UL Provides to the UE. μ SFI,DL ≥μ SFI,UL and each The value of the slot format provided by the value, where the value of the slot format is determined by the value of the slot format combination ID of the slot format combination, and the value of the slot format combination ID is set to the value of the SFI index field value of DCI format 2_0, and the first The value for the slot format combination applies to the reference DL BWP, and the following value applies to the reference UL BWP. μ SFI,DL <μ SFI,UL and each For the value, the first value of the slot format combination is applied to the reference DL BWP, and the next The value is applied to the reference UL BWP.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0434] 3) The UE receives the PDCCH.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0475] FIG. 16 illustrates an example in which an SBFD according to one embodiment of the present disclosure is applied to a DL slot among resources consisting of a DL slot and a UL slot. In FIG. 16, a slot treated as an SBFD slot by an SBFD-aware UE is treated as a DL slot by a legacy UE.

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

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

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

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

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

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

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

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

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

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

[0486] Case 3: When SBFD is applied to some DL slots or flexible slots

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

[0488] Specific embodiments of the present disclosure

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

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

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

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

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

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

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

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

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

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

[0499] The relevant RRC parameters are as follows.

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

[0501] [Table 14]

[0502]

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

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

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

[0506] [Table 15]

[0507]

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

[0509] [Table 16]

[0510]

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

[0512] [Table 17]

[0513]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0541] 2> Increase PREAMBLE_TRANSMISSION_COUNTER by 1.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0556] Now, we will explain the mapping between SSB and RO.

[0557] A UE may be provided with N SS / PBCH block (SSB) indices associated with one PRACH opportunity (RO) by upper-tier parameters (e.g., ssb-perRACH-OccasionAndCB-PreamblesPerSSB) and Q contention-based preambles per SSB index per valid RO by upper-tier parameters (e.g., msgA-CB-PreamblesPerSSB-PerSharedRO). For a UE provided with a PRACH mask index, PRACH transfers may be performed on a subset of ROs associated with the same SSB index within an SSB-RO mapping cycle.

[0558] The SSB (SS / PBCH block) index provided by ssb-PositionsInBurst of SIB1 or ServingCellConfigCommon can be mapped to valid ROs in the following order.

[0559] First, ascending order of preamble indices within a single RO(PRACH Occasion).

[0560] Second, ascending order of frequency resource indices for frequency-multiplexed ROs.

[0561] Third, ascending order of time resource indices for time-multiplexed ROs within the PRACH slot.

[0562] Fourth, ascending order of the indices of the PRACH slots.

[0563] The association period for mapping SSB indexes to ROs (PRACH opportunities) is the smallest integer in the set determined by the PRACH configuration period according to Table 6, starting from Frame 0, and N Tx SSB SSB indexes are mapped to ROs at least once within the association cycle.

[0564] The UE is N in the ssb-PositionsInBurst value of SIB1 or ServingCellConfigCommon Tx SSB It can be obtained. The association pattern period includes one or more association periods, and the pattern between ROs and SSB indices is determined to repeat every 160 milliseconds (msec) at most. After an integer number of association periods have passed, ROs not associated with an SSB index are not used for PRACH transmission.

[0565] In the case of a UE PRACH transmission triggered by a PDCCH order, if the value of the Random Access Preamble Index field is not zero, the PRACH Mask Index field indicates the RO for the PRACH transmission. Here, the ROs are associated with the SS / PBCH block index indicated by the SS / PBCH Block Index field of the PDCCH order, and if a Cell Indicator field is present, indicate the cell for the PRACH transmission. K to the UE by cellSpecificKoffset cell,offset If this is provided, RO is slot n+2 μ ·K cell,offset It is after. Here, n is T TAAssuming =0, it is a slot of UL BWP for PRACH transmission that overlaps with the end of PDCCH command reception, and μ is an SCS setting for PRACH transmission.

[0566] For a PRACH transmission triggered by an upper layer, if ssb-ResourceList is provided, the PRACH mask index is indicated by ra-ssb-OccasionMaskIndex and represents the ROs for the PRACH transmission. The ROs are associated with the selected SSB index.

[0567] ROs are mapped consecutively for each corresponding SSB index. The indexing of ROs indicated by the mask index value is reset for every mapping cycle of consecutive ROs per SSB index. In the first available mapping cycle, the UE selects the RO indicated by the PRACH mask index value for the indicated SSB index for PRACH transmission.

[0568] Meanwhile, in a wireless communication system where SBFD is applied, the random accesss operation may provide two types of RO. For example, in the case of RACH configuration Option 1, the RO is configured by a single legacy RACH configuration, consisting of i) an additional RO in an SBFD symbol and ii) a legacy RO in a non-SBFD symbol / Flexible SBFD symbol. In the case of RACH configuration Option 2, the RO is configured by a legacy RACH configuration and an additional RACH configuration, i) the legacy RO in a non-SBFD symbol is configured by the legacy RACH configuration, and ii) the additional RO in an SBFD symbol (and / or non-SBFD symbol) is configured by the additional RACH configuration.

[0569] Legacy RO refers to the RO prior to the introduction of SBFD, and additional ROs can be defined as follows depending on the RACH configuration options.

[0570] 1) Shared RO configuration: For RACH configuration option 1 (which may be referred to as a single RACH configuration or RACH configuration option 1) having a legacy RACH configuration, an additional RO may be defined that includes at least one SBFD symbol configured as DL by tdd-UL-DL-ConfigurationCommon.

[0571] 2) Separate RACH configuration (Searate RO configuration): In the case of RACH configuration option 2, which has legacy RACH configuration and additional RACH configuration, the RO configured by the additional RACH configuration can be defined as additional RO.

[0572] Meanwhile, the current standard specification specifies that both PRACH setting option 1 (a setting option that uses a single PRACH setting parameter for both SBFD terminals and legacy terminals, corresponding to the aforementioned RACH setting option 1) and PRACH setting option 2 (a setting option that uses individual PRACH settings for each SBFD terminal and legacy terminal, corresponding to the aforementioned RACH setting option 2) use SSB-RO mapping for non-SBFD specific RO and SBFD specific RO, respectively.

[0573] However, it was agreed not to use different SSB-RO mapping rules for SBFD / non-SBFD specific ROs, but to map each type of RO using the same rules.

[0574] For example, a first SSB-RO mapping is applied to non-SBFD specific ROs, and a second SSB-RO mapping is applied to SBFD specific ROs. In this way, each SSB-RO mapping is applied to non-SBFD specific ROs and SBFD specific ROs, but the first SSB-RO mapping and the second SSB-RO mapping are performed using the same rule.

[0575] For example, in the case of a UE aware of the SBFD in the RRC connected state and RACH configuration option 1 (i.e., a configuration option that uses a single RACH configuration and is based only on the existing parameters of the single RACH configuration),

[0576] For legacy ROs (including ROs for non-SBFD symbols and ROs for SBFD symbols flexibly configured by tdd-UL-DL-ConfigurationCommon (if present), legacy SSB-RO mapping is applied. For ROs for SBFD symbols configured as downlinks by tdd-UL-DL-ConfigurationCommon, a separate SSB-RO mapping is used.

[0577] For RACH configuration option 1, existing SSB-RO mapping rules are reused for additional ROs. For RACH configuration option 2, legacy SSB-RO mapping rules are used for additional ROs configured by the additional RACH configuration, and SSB-RO mapping is used separately from the SSB-RO mapping for legacy ROs configured by the legacy RACH configuration.

[0578] Meanwhile, for RACH setting option 2, the PRACH setting index is different, so the UE cannot freely use RO between SBFD and non-SBFD, and for RACH setting option 1, separate mapping is used for each symbol type, so there may be restrictions on the use of SBFD / non-SBFD specific RO.

[0579] Figure 20 illustrates the mapping between ROs of two RO types and SSBs.

[0580] Referring to FIG. 20, two RO types, for example, RO of RO type 1 (non-SBFD RO) and RO of RO type 2 (SBFD RO), can be mapped to each mapping cycle.

[0581] Figure 20 (a) shows an example in which, in each mapping cycle, ROs of type 2 are first mapped to SSBs, and if there are ROs of type 1, ROs of type 1 are mapped to SSBs.

[0582] Figure 20(b) shows an example in which, in each mapping cycle, ROs of type 1 are first mapped to SSBs, and if there are ROs of type 2, ROs of type 2 are mapped to SSBs.

[0583] For example, 2 nd Mapping cycle and 4 th In the mapping cycle, an example is shown in which ROs of type 2 are first mapped to SSBs and then ROs of type 1 are mapped to SSBs (see Fig. 20 (a)), and an example is shown in which ROs of type 1 are first mapped to SSBs and then ROs of type 2 are mapped to SSBs (see Fig. 20 (b)).

[0584] Here, non-SBFD RO refers to an RO configured in a non-SBFD symbol / slot (hereinafter referred to as a non-SBFD symbol for convenience), and SBFD RO may refer to an RO configured in an SBFD symbol / slot (hereinafter referred to as an SBFD symbol for convenience). SBFD can be extended and interpreted as SSFD. A UE can perform PRACH transmission using two types of RO (RO type 1, RO type 2, or more).

[0585] In this disclosure, for convenience, SBFD RO and non-SBFD RO have been described as examples, but the methods presented in this disclosure can be applied to other examples where the time resource is generalized to a second time resource and a first time resource.

[0586] In these examples, different types of ROs can be distinguished as ROs in the first time resource and ROs in the second time resource.

[0587] The RO in the first time resource may be a non-SBFD RO, and the RO in the second time resource may be an SBFD RO.

[0588] Alternatively, the RO in the first time resource may be a non-SBFD RO, and the RO in the second time resource may be an SSFD RO.

[0589] As another example, the RO in the first time resource may be the RO that is basically directed, and the RO in the second time resource may be the RO that is additionally directed.

[0590] As explained above, if there is a basically indicated RO, the RO of the first time resource can be distinguished as the legacy RO, and the RO of the second time resource can be distinguished as the additional RO.

[0591] According to the embodiment, the RO in the non-SBFD symbol may be called the legacy RO, and the RO in the SBFD symbol may be called the additional RO. In other words, the legacy RO may be the non-SBFD RO, and the additional RO may be the SBFD RO.

[0592] If the number of SBFD ROs is less than the number of non-SBFD ROs, legacy ROs may be considered as SBFD ROs and additional ROs as non-SBFD ROs.

[0593] In the following, terms such as RO Type 1 instead of Legacy RO and RO Type 2 instead of Additional RO may be used.

[0594] In SSB-RO (=SSB-to-RO) mapping, SSB-RO mapping can be performed on legacy ROs first, and then SSB-to-RO mapping can be performed on additional ROs.

[0595] For example, the mapping cycle / mapping pattern cycle applied in legacy ROs can be commonly applied to additional ROs as well.

[0596] This explains the method for determining the valid ROs used for the SSB-RO mapping among the valid ROs of additional ROs within the range of the mapping period / mapping pattern period when applying a single SSB-RO mapping for legacy ROs.

[0597] Because different types of ROs may have different interference based on different environments in different symbol types (or may be designed for different purposes), each RO type allows transmission through an RO with different characteristics when configured. For example, if two different types are an SBFD RO and a non-SBFD RO, the pRACH detection performance of the gNB may differ. Depending on the purpose of pRACH usage, a specific type of RO can be selected based on the needs of the UE or gNB.

[0598] Other types of RO can be configured with a single RACH configuration or one or more RACH configurations. However, even if configured by one or more RACH configurations, it is assumed that a specific UE can view all types of ROs and select a specific RO. In this case, the selection of a specific RO may be based on gNB configurations / instructions based on environment / conditions / priorities or by the UE's selection.

[0599] If there is a UE that can freely use SBFD RO and non-SBFD RO among the two different types of RO, SSB-RO mapping can be done in two ways.

[0600] The first is a separated SSB-RO mapping that applies a separate SSB-RO mapping to each SBFD RO and non-SBFD RO, respectively. This method can introduce unnecessary complexity in that a single UE must compute both types of SSB-RO mappings. For example, since separate SSB-RO mappings exist, when a specific association (pattern) period is defined for each RO type, the UE must compute an SSB-RO mapping based on that specific association (pattern) period.

[0601] If, despite having separate SSB-RO mapping rules, there is a single association (pattern) cycle, there is an RO type among SBFD / non-SBFD ROs that serves as the basis for the cycle of the association pattern cycle. In this case, assuming that all configured SSB indexes are mapped to SSB-RO at least once, if the number of required ROs corresponding to the RO type differs, the association (pattern) cycle can be set to a single value based on the RO type configured with the smaller number of ROs.

[0602] If one of the RO types is a specific legacy RO type, the association (pattern) period can be set to a single value to match that specific legacy RO.

[0603] Furthermore, when the UE executes the PRACH preamble iteration, if the SSB-RO mapping differs for each RO type, a delay may occur during the execution of the PRACH preamble iteration because the frequencies of ROs mapped to the same SSB differ, making it practically difficult to apply the PRACH preamble iteration to different RO types.

[0604] To solve the above problem, a single SSB-RO mapping can be introduced even in the case of an RO configuration consisting of different RO types.

[0605] However, when a single SSB-RO mapping is applied to ROs composed of different RO types, a problem like that shown in Fig. 20 may occur.

[0606] For example, as can be seen in Figure 20 (a), all SSB indices (SSB#1, SSB#2, SSB#3, SSB#4) are mapped to SBFD ROs, but in the case of non-SBFD ROs, there may be cases where only some SSB indices, such as SSB#2 and SSB#3, are repeatedly mapped.

[0607] Likewise, as can be seen in Figure 20 (b), all SSB indices (SSB#1, SSB#2, SSB#3, SSB#4) are mapped to non-SBFD ROs, but in the case of SBFD ROs, there may be cases where only some SSB indices, such as SSB#2 and SSB#3, are repeatedly mapped.

[0608] In addition, if CFRA is introduced and the PRACH index and SSB index are applied to RRC, MAC-CE, and PDCCH instructions, there may be limitations on the variety of ROs that a gNB or UE can select.

[0609] This document proposes methods to avoid problems that occur when using a single SSB-RO mapping in an environment where different types of ROs are configured.

[0610] In addition to a configuration using a small number of ROs (e.g., temporally intermittent time intervals) for Network Energy Saving (NES), additional ROs may be indicated along the time and / or frequency axes. These can be distinguished as legacy ROs and additional ROs, respectively; SSB-RO mapping cycles / pattern cycles can be performed first on the legacy ROs, followed by SSB-RO mapping on the additional ROs. In this case, the proposed method can be applied.

[0611] In the following, a new mapping rule is proposed to avoid problems that arise when a single SSB-RO mapping rule is used for various types of ROs. Problems that may occur when a single SSB-RO mapping rule is not used have been previously described (for example, when a UE executes a PRACH preamble iteration, if the SSB-RO mapping differs for each RO type, the frequencies of ROs mapped to the same SSB may differ, causing delays when executing the PRACH preamble iteration, and it may be practically difficult to apply the PRACH preamble iteration to different RO types). Problems that may occur when using a single SSB-RO mapping rule are explained below. Hereinafter, the SSB-RO mapping rule may be simply referred to as the mapping rule.

[0612] In 6G or later communication systems, i) a UE that does not recognize SBFD RO and recognizes only Non-SBFD RO, and ii) a UE that recognizes both SBFD RO and non-SBFD RO may be allowed.

[0613] In the case where a UE that recognizes only Non-SBFD RO and a UE that recognizes both SBFD RO and non-SBFD RO commonly use non-SBFD RO, to ensure that the mapping of the SSB index to non-SBFD RO operates without ambiguity, SSB-RO mapping is performed only on non-SBFD RO. For SBFD RO, SSB-RO mapping is performed only on SBFD RO.

[0614] At this time, making the SSB-RO index mapping period (hereinafter abbreviated as mapping period) of the SBFD RO and non-SBFD RO the same has the advantage that for a UE using both types of ROs, SSB RO mapping can be performed by calculating only one period.

[0615] However, within the mapping period, the number of valid ROs of SBFD ROs may be equal to or different from the number of ROs mapped to valid ROs of non-SBFD ROs, and if the numbers are different, only specific SSB indices may be mapped to SBFD ROs, and SSB indices mapped to non-SBFD ROs may be mapped identically to adjacent SBFD ROs.

[0616] For a UE that can recognize and use both SBFD RO and non-SBFD RO, an SSB-RO mapping is required that can produce the same effect as SSB-RO mapping without distinguishing between SBFD RO and non-SBFD RO.

[0617] The terminal performing SSB-RO mapping can be one of the following two terminals.

[0618] 1) A UE that cannot recognize SBFD RO and can only recognize non-SBFD RO. (Hereinafter referred to as a non-SBFD recognizing UE)

[0619] 2) A UE capable of recognizing both SBFD RO and non-SBFD RO. (Hereinafter referred to as an SBFD-aware UE)

[0620] First, we will explain the UE that cannot recognize SBFD RO and can only recognize non-SBFD RO.

[0621] In performing SSB-RO mapping, the terminal receives instructions from the base station regarding the number of available valid ROs and the SSBs mapped to each RO. Alternatively, the terminal determines the valid ROs based on information transmitted by the base station.

[0622] When performing SSB-RO mapping based solely on instructions, it can be assumed that the SBFD-aware UE can recognize both SBFD ROs and non-SBFD ROs, and can sequentially map SSBs to ROs without distinguishing between SBFD / non-SBFD ROs for all ROs.

[0623] Since non-SBFD aware UEs cannot recognize SBFD ROs, they can only map SSBs to ROs for non-SBFD ROs. In this case, the index of the SSB sequentially mapped by the SBFD aware UE and the non-SBFD aware UE to the first RO in terms of time and frequency of the non-SBFD RO may differ. Consequently, a problem may arise where the mapping result targeting only the non-SBFD RO differs from the mapping result targeting both SBFD and non-SBFD ROs from the perspective of the SBFD aware UE. Therefore, when a base station receives a PRACH from the corresponding RO, additional information may be required to distinguish which SSB the PRACH was generated based on. To avoid generating such additional information, it is necessary for both SBFD and non-SBFD aware UEs to perform SSB-RO mapping in common on the non-SBFD RO.

[0624] Secondly, we describe a UE capable of recognizing both SBFD RO and non-SBFD RO.

[0625] When performing SSB-RO mapping, the terminal receives instructions from the base station regarding the number of available valid ROs and the SSB mapped to each RO. Assuming that all terminals can see both SBFD / non-SBFD ROs, a common SSB-RO mapping is used for both SBFD / non-SBFD ROs; however, if a terminal performs RACH targeting only a specific type of RO, a problem may arise where only specific SSB indices are concentrated in that specific type of RO.

[0626] Alternatively, a problem may arise where a terminal can only transmit via a specific type in order to use a specific SSB. When using only a specific RO type, unnecessary restrictions may be imposed on the UE because the channel environment, interference, coverage, and beam may be limited due to the characteristics of the RO type. Therefore, it may be necessary for SBFD / non-SBFD ROs to map all SSBs.

[0627] Figure 21 illustrates a problem that can occur when using a single SSB-RO mapping for different types of ROs.

[0628] Referring to Fig. 21, in each mapping cycle, the number of SBFD ROs and the number of non-SBFD ROs may be the same (e.g., 3). In this case, in each mapping cycle, 3 SBFD ROs may be mapped to SSB#0, 1, 2 and 3 non-SBFD ROs may be mapped to SSB#3, 4, 5, and this process may be repeated.

[0629] In the case of a non-SBFD recognized UE, since only non-SBFD RO can be recognized, if SSB-RO mapping is performed as shown in Fig. 21, a problem arises in that only the channel environments / interference / coverage / beams of SSB#3, 4, and 5 can be used for PRACH.

[0630] Even in the case of an SBFD-aware UE, if it is only available for SBFD RO, there may be cases where only the channel environments / interference / coverage / beams of SSB#0, 1, and 2 are available for PRACH, just like with a non-SBFD UE.

[0631] Therefore, even if the UE can recognize both SBFD ROs and non-SBFD ROs and transmit over them, mapping some SSB indices to only a specific type of RO may lead to environmental, interference, coverage, or beaming issues. Therefore, it is desirable to map all SSB indices to a specific type as well.

[0632] Generally, non-SBFD ROs can be used for SBFD-aware UEs, and mapping rules can be established so that all SSBs are mapped to non-SBFD ROs. These rules may be known in advance by mutual agreement between the base station and the UE, and the base station may inform the terminal of the mapping parameters via RRC / MAC CE / DCI / SIB, etc.

[0633] Regarding the methods proposed below, the base station may explicitly set one of the following: whether the terminal uses each of the methods proposed in the present disclosure, whether all ROs are simply mapped to SSB-RO without distinguishing types, or whether SBFD ROs and non-SBFD ROs are mapped to SSB-RO individually / independently.

[0634] 5.1 Mapping Cycle-Based Method

[0635] If CFRA is supported, relevant parameters may be introduced to allow the gNB to select an RO type and to set / indicate the RO type via the RRC, MAC CE, or PDCCH commands. Additionally, the RRC, MAC CE, or PDCCH commands may include a random access preamble index. This field may indicate the random access preamble index of CFRA resources.

[0636] For example, the RRC, MAC CE, or PDCCH command may include an SS / PBCH index. This field may indicate an SS / PBCH (SSB) to be used to determine / resolve a RACH opportunity (RO) for the PRACH transfer of CFRA resources.

[0637] For example, the RRC, MAC CE, or PDCCH command may include a PRACH mask index. This field indicates the RACH opportunity (RO) associated with the SS / PBCH indicated by the 'SS / PBCH index' for the PRACH transfer of the CFRA resource.

[0638] Method 1) Based on these parameters, the RO of the first available mapping cycle can be selected. The first available mapping cycle may refer to the first mapping cycle where all given parameters are applicable. This can be the best method to reduce latency.

[0639] Figure 22 illustrates SSB-RO mapping by Method 1.

[0640] Referring to Fig. 22, for example, if SSB#0, SBFD RO, and PRACH mask index 1 (e.g., meaning PRACH chance index 1) are given as CFRA operations, the first (1 st The mapping cycle can be the first available mapping cycle.

[0641] As another example, given SSB#2, non-SBFD RO, and PRACH mask index 1, the second (2 nd The mapping cycle can be the first available mapping cycle.

[0642] Method 2) Parameters related to the mapping cycle may also be included. When RO is configured as shown in Fig. 22, the mapping cycle satisfying SSB#0, SBFD RO, and PRACH mask index 1 is the first (1st ) mapping cycle and the third(3 rd A mapping cycle exists. Mapping cycle parameters may be introduced to additionally set / instruct specific mapping cycles. For example, given SSB#0, SBFD RO, PRACH mask index 1, and mapping cycle 1, the third (3 rd PRACH transmission can occur during the mapping cycle.

[0643] Method 3) When using the methods of Method 1 and / or Method 2 described above, the UE may not expect a specific combination of parameters. For example, if SSB#1, non-SBFD RO is set / instructed, the UE may not expect such a combination of parameters because there is no corresponding RO in any mapping cycle.

[0644] Method 4) When using the method of Method 1 and / or Method 2, the gNB is configured to set / instruct specific combinations of parameters. For example, if SSB#1, non-SBFD RO is configured / instructed, the gNB may configure / instruct other combinations of parameters excluding this combination, because there is no corresponding RO in any mapping cycle.

[0645] To resolve the issue where a specific SSB index is not mapped to ROs of a specific RO type, the SSB-RO mapping rule can be modified as follows. The SSB-RO mapping rule is applicable to CBFA as well as CFRA.

[0646] 5.2 Mapping rule-based method

[0647] In the following, we propose a new SSB-RO mapping rule to avoid problems that arise when using a single SSB-RO mapping for various types of ROs. As examples of various types of ROs, two different types (SBFD RO and non-SBFD RO) are described.

[0648] Method 1) A method using separate SSB sets for each RO type.

[0649] Even if a single SSB-RO mapping is applied to an RO configuration composed of different types of ROs, the SSB index mapped to the different types of ROs can be composed of a new set of SSBs or a set of SSBs from one type.

[0650] In Method 1, SSB-RO mapping is not simply performed in the existing given mapping order. For example, if there are only two non-SBFD ROs in the mapping cycle as shown in FIG. 22, a set of SSBs suitable for the non-SBFD ROs can be provided. In other words, separate sets of SSBs suitable for different RO types can be constructed. If a new set of SSBs is needed, relevant parameters can be set / instructed to construct a set of SSBs corresponding to each of the different RO types.

[0651] Figure 23 illustrates an SSB-RO mapping that uses separate sets of SSBs for each RO type.

[0652] Referring to Fig. 23, SSB#0-SSB#3 may be given to SBFD ROs and SSB#4 and SSB#5 may be given to non-SBFD ROs. In other words, distinct sets of SSBs may be given for different RO types.

[0653] According to an embodiment, a part (subset) of the set of SSBs of the first type RO can be configured into the set of SSBs of the second type RO based on a specific rule. The rule can be set / directed at an upper layer.

[0654] Method 2) When there are mapping cycles composed of the same or different RO types, a method of setting an independent mapping cycle type for each RO type and applying an offset only to that type.

[0655] A mapping cycle containing a mixture of different types of ROs can be defined as mapping cycle type #1, and a mapping cycle consisting only of ROs of the same type can be defined as mapping cycle type #2. In this case, different mapping cycle rules may be applied to the two mapping cycle types. For example, for a mapping cycle of mapping cycle type #2, first, the preamble indices within a single PRACH opportunity are mapped in ascending order, and next, the frequency resource indices within frequency-multiplexed PRACH opportunities are mapped in ascending order. Next, the time resource indices within time-multiplexed PRACH opportunities within a PRACH slot are mapped in ascending order, and next, the indices of the PRACH slots of the SSB-RO mapping rule are mapped in ascending order.

[0656] The mapping cycle of mapping cycle type #1 follows the default mapping rules for the mapping cycle of mapping cycle type #2, but the order of the SSB indices of the starting RO type within mapping cycle type #1 can be changed / diversified by adding an offset value to the index of the starting RO type.

[0657] Figure 24 shows an example where the SSB index associated with each RO type is different for each mapping cycle.

[0658] Referring to Fig. 24, in the existing mapping rule, if the SSB start index of a type RO (e.g., SBFD RO) starting in the first mapping cycle is k (e.g., k=0), the SSB start index of a type RO (e.g., SBFD RO) starting in the second mapping cycle may also be k (e.g., k=0). Likewise, for a Non-SBFD RO, the SSB start index is the same at 2 in the second mapping cycle and the fourth mapping cycle.

[0659] On the other hand, according to the new mapping rule, the SSB starting index can be set differently in each mapping cycle. For example, in the case of an SBFD RO, the SSB starting index may be k (e.g., k=0) in the second mapping cycle, whereas in the fourth mapping cycle, the SSB starting index may be k+m (e.g., 0+2). Here, m may be the number of RO types other than the starting RO type (e.g., SBFD RO) constituting the mapping cycle (e.g., SBFD RO) (e.g., non-SBFD RO). This method prevents situations where a specific SSB index is not mapped to a specific RO type in the corresponding mapping cycle.

[0660] The initialization of the SSB index is as follows.

[0661] When the SSB start index reaches the maximum SSB index, the SSB start index can be initialized to 0.

[0662] SSBStartingIndex = LastmappedSSBindex non-SBFD - TotalnumberofusedSSB+TotalnumberofusedSSB non-SBFD It can be represented as +1.

[0663] SSBStartingIndex=LastmappedSSBindex-TotalnumberofusedSSB SBFD It can be represented as +1.

[0664] Considering the possibility that the number of valid ROs of different types and the number of ROs used for SSB-RO mapping may not be integer multiples due to RO settings, SSB-RO mapping ratios, and RO validation, it must be considered how many ROs from the valid ROs of different types will be used for SSB-RO mapping.

[0665] At this time, the following rules may be applied, and the examples of the rules below are based on SBFD RO and non-SBFD RO.

[0666] Let N be the number of ROs mapped to SSB within the SSB-RO mapping period of non-SBFD ROs, and let M be the number of valid ROs among the additional ROs within the SSB-RO mapping period,

[0667] (1) In the case of M > N,

[0668] Find the largest natural number a satisfying N*a (a is a natural number) < M, and

[0669] Among the M - N*a remaining additional ROs, valid ROs are not used for SSB-RO mapping.

[0670] (2) If M < N, M valid ROs are not used for SSB-RO mapping.

[0671] SSB-RO mapping starts from the RO included in the earliest RACH slot among the additional ROs within the frame containing the earliest RACH slot in the SSB-RO mapping cycle of the non-SBFD RO.

[0672] At this time, the method of using the new mapping cycle mentioned in Section 5.1 above can be applied to the new SSB-RO mapping rule of Method 1) above.

[0673] Method 1-1) The RO of the first available mapping cycle can be selected. The first available mapping cycle may refer to the first mapping cycle where all given parameters are applicable. This can be the best method to reduce latency.

[0674] For example, if SSB#0, non-SBFD RO, and PRACH mask index 1 (e.g., meaning PRACH chance index 1) are given as CFRA operations in Fig. 24, the fourth mapping cycle according to the new mapping rule can be the first available mapping cycle. If the new mapping rule is not applied, it is a combination that cannot be indicated.

[0675] Method 1-2) At this time, parameters related to the mapping cycle may also be included. When RO is configured as shown in FIG. 23, there exists a 1st mapping cycle and a 3rd mapping cycle for the mapping cycle satisfying SSB#0, SBFD RO, and PRACH mask index 1. Mapping cycle parameters may be introduced to additionally configure / instruct specific mapping cycles. For example, given SSB#0, SBFD RO, PRACH mask index 1, and mapping cycle #1, PRACH transmission may occur in the 3rd mapping cycle.

[0676] Method 1-3) When using the methods of Method 1 and / or Method 2, the UE may not expect a specific combination of parameters. For example, if SSB#1, non-SBFD RO, and 2nd mapping cycle are set / instructed, there is no corresponding RO.

[0677] Method 1-4) When using the method of Method 1 and / or Method 2, gNB is configured / instructed to set / instruct specific combinations of parameters. For example, if SSB#1, non-SBFD RO, and 2nd mapping cycle are configured / instructed, this is because there is no corresponding RO.

[0678] Method 3) A method for calculating implicitly associated SSB indexes without distinguishing by RO type.

[0679] A. The terminal can agree with the base station in advance as follows to calculate the starting (initial) SSB index of the next mapping cycle.

[0680] i. Terminals need a reference point for implicit calculation. For example, a terminal may use a mapping cycle / association (pattern) period starting from SFN (System Frame Number) 0 as a reference point (reference mapping cycle / association (pattern) period), calculate how many mapping cycles / association (pattern) periods away from the reference mapping cycle, and reflect this in the rule.

[0681] ii. Since the terminal is configured with two RO types, SBFD / non-SBFD RO, the mapping cycle may not end exactly at a specific RO. Therefore, a new mapping cycle, for example, a virtual mapping cycle, can be arbitrarily configured. Here, a virtual mapping cycle means that even if the SSB-RO mapping has not ended exactly, the time (time axis) at which a non-SBFD RO containing (associated with) the last index of the SSB exists can be set as the end point of the previous mapping cycle / the start point of the new mapping cycle.

[0682] B. The terminal can first determine the SSB-RO mapping in non-SBFD ROs and then derive the SSB-RO mapping index in SBFD ROs as follows to find the index.

[0683] i. The range of the associated pattern period or mapping cycle is determined first by the legacy RO.

[0684] In this case, the legacy RO may be pre-assigned as a non-SBFD RO. Alternatively, the legacy RO may be set as the type of RO with fewer ROs between the non-SBFD RO and the SBFD RO. Alternatively, the legacy RO may be designated by the base station as an RRC / MAC CE / DCI / SIB.

[0685] ii. Regardless of the position on the time axis of the SBFD RO and the non-SBFD RO, the terminal can determine the start (initial) SSB index of the SBFD RO by finding the SSB index of the RO to which the last SSB among the non-SBFD ROs is mapped in the association pattern period in which the non-SBFD RO and the SBFD RO are set.

[0686] In the process of ii) above, 1. the terminal can determine the SSB index mapped to the SBFD RO by referring only to the associated pattern period without needing to consider the previous associated pattern period.

[0687] 2. In order to calculate the SSB-RO mapping quickly for the terminal, the mapping cycle / virtual mapping cycle may be taken as the minimum unit in addition to the associated pattern period to calculate the SSB mapping location of the SBFD RO.

[0688] 3. After sequentially mapping SSBs to non-SFBD ROs, SSBs can be sequentially mapped to SFBD ROs.

[0689] For example, it can be considered in a way that sequentially maps SSB 0~5, 0~5, and 0~2 to 15 non-SFBD ROs, and then sequentially maps SSB 3~5, 0~5, and 0~5 to 15 SFBD ROs.

[0690] The SSB start index of an SBFD RO can use the SSB end (ending) index of a non-SBFD RO + 1.

[0691] For example, SSB-RO mapping can be performed first on non-SFBD ROs, and after defining the association (pattern) cycle, the SSB index (e.g., A) mapped to the non-SBFD RO can be followed by mapping the next SSB index (e.g., A+1) to the first SBFD RO.

[0692] Figure 25 shows an example of sequentially mapping SSB indexes to non-SFBD ROs, and then sequentially mapping SSB indexes to SFBD ROs.

[0693] Referring to Fig. 25, for example, for each RO type, a total of 5 mapping cycles may be included in the association (pattern) cycle. That is, let us assume that there are a total of 5 mapping cycles for SBFD ROs and a total of 5 mapping cycles for non-SBFD ROs.

[0694] In this case, the process of sequentially mapping SSB indices 0 to 4 to 15 non-SFBD ROs is repeated.

[0695] If the last SSB index (251) mapped to non-SBFD ROs is 4, the first SBFD RO (252) can be mapped starting from the next SSB index (e.g., 0).

[0696] iii. After the Non-SBFD RO, the SSB index is mapped in a non-contiguous manner from the SBFD RO.

[0697] The terminal can know the total number of SSBs mapped to ROs within the previous mapping cycle. Additionally, assuming the terminal knows the index of the last mapped SSB of the non-SBFD ROs and the total number of SSB indices mapped to the non-SBFD ROs, the terminal can derive the starting index of the next mapping cycle as follows.

[0698] As the mapping cycle changes, the next mapping cycle can start by adding the SSB-RO mapping start index by the number of non-SBFD ROs. In other words, an offset value can be applied.

[0699] For example, in the Nth mapping cycle, the SSB starting index of the additional ROs is 0 and 2 SSBs are mapped to the non-SBFD ROs, then in the next (N+1)th mapping cycle, the SSB starting index of the additional ROs becomes 2 (=0+2), and in the N+2th mapping cycle, the SSB starting index of the additional ROs becomes 4 (=2+2).

[0700] For example, if the starting index of the SSB mapped to the additional RO in the Nth mapping cycle is k (e.g., k=0) and m (e.g., m=2) SSBs are mapped to non-SBFD ROs, then the starting index of the SSB mapped to the additional RO in the next (N+1)th mapping cycle can be k+m (e.g., 0+2 = 2). In this case, if p (e.g., p=2) non-SBFD ROs are mapped in the (N+1)th mapping cycle, then the starting index of the SSB of the additional RO in the next (N+2)th mapping cycle can be k+m+p (e.g., 0+2+2 = 4). If there are no non-SBFD ROs in the (N+1)th mapping cycle (i.e., p=0), it can be defined that the starting index of the SSB mapped to the additional RO in that mapping cycle is reused in the next (N+2)th mapping cycle.

[0701] When the SSB start index reaches the maximum SSB index (or exceeds the maximum SSB index), the SSB start index can be initialized to 0.

[0702] Expressed as a formula, SSBStartingIndex = LastmappedSSBindex non-SBFD - TotalnumberofusedSSB+TotalnumberofusedSSB non-SBFDIt can be represented as +1.

[0703] Alternatively, it can be calculated as follows.

[0704] SSBStartingIndex=LastmappedSSBindex-TotalnumberofusedSSB SBFD +1.

[0705] Considering the possibility that the number of valid ROs among additional ROs and the number of ROs used for SSB-RO mapping of non-SBFD ROs may not be an integer multiple due to RO settings, SSB-RO mapping ratios, and RO validation, it is necessary to specify how many ROs among the valid ROs of additional ROs will be used for SSB-RO mapping.

[0706] For example, the following rules may apply.

[0707] Let N be the number of ROs mapped to SSB within the SSB-RO mapping period of non-SBFD ROs, and let M be the number of effective ROs among the additional ROs within the SSB-RO mapping period,

[0708] (1) In the case of M > N,

[0709] Find the largest natural number a satisfying N*a (a is a natural number) < M, and

[0710] Among the M - N*a remaining additional ROs, valid ROs are not used for SSB-RO mapping.

[0711] (2) If M < N, M valid ROs are not used for SSB-RO mapping.

[0712] SSB-RO mapping starts from the RO included in the earliest RACH slot among the additional ROs within the frame containing the earliest RACH slot in the SSB-RO mapping cycle of the non-SBFD RO.

[0713] At this time, the method of using the new mapping cycle mentioned in Section 5.1 above can be applied to the RO configuration set based on Section 5.3.

[0714] Figure 26 illustrates a case where the associated SSB indices in SBFD ROs are not consecutive.

[0715] Referring to Fig. 26, let us assume that the ROs labeled SBFD&legacy RO are ROs of the first RO type (hereinafter simply referred to as the first type), and the ROs labeled SBFD RO are ROs of the second RO type (hereinafter simply referred to as the second type).

[0716] In this case, SSB-RO mapping is first performed on the ROs of the first RO type. Then, SSB indices 0 to 3 are mapped repeatedly to a total of 9 ROs of the first RO type, and the SSB index mapped to the last RO of the first RO type (261) becomes 0.

[0717] Then, an SSB index 1 is mapped to the first RO (262) of the first mapping cycle among the ROs of the second RO type. In this case, an SSB index 0 is mapped to the first RO (263) of the second RO type in the second mapping cycle. The SSB index mapped to the first RO (263) of the second RO type in the second mapping cycle is determined based on the SSB index (e.g., 1) mapped to the first RO (262) of the second RO type in the first mapping cycle and the number of ROs of the first RO type in the first mapping cycle (or the number of SSBs associated with the ROs of the first RO type, e.g., 3). For example, the SSB index mapped to the first RO (263) of the second mapping cycle can be determined by the sum of the SSB index (e.g., 1) mapped to the first RO (262) of the second RO type of the first mapping cycle and the number of ROs of the first RO type of the first mapping cycle (or, in an equivalent sense, the number of SSBs related to the ROs of the first RO type of the first mapping cycle, e.g., 3). At this time, the sum becomes 4, which exceeds the maximum SSB index of 3, so it is mapped to SSB index 0.

[0718] The SSB index mapped to the first RO (264) of the second RO type of the third mapping cycle is determined by the sum of the SSB index (e.g., 0) mapped to the first RO (263) of the second RO type of the second mapping cycle and the number of ROs of the first RO type of the second mapping cycle (or, in an equivalent sense, the number of SSBs related to the ROs of the first RO type of the second mapping cycle, e.g., 3).

[0719] By this method, the SSB indices mapped to the first ROs (262, 263, 264) of the second RO type in each mapping cycle become 0, 3, and 2, ensuring diversity of the mapped SSB indices.

[0720] Figure 27 illustrates another case where the associated SSB indices in SBFD ROs are not consecutive.

[0721] Referring to Fig. 27, let us assume that the ROs labeled as non-SBFD are ROs of the first RO type, and the ROs labeled as SBFD RO are ROs of the second RO type.

[0722] In this case, SSB-RO mapping is first performed on the ROs of the first RO type. Then, SSB indices 0 to 4 are sequentially repeated and mapped to a total of 12 ROs of the first RO type, and the SSB index mapped to the last RO of the first RO type (271) becomes 1.

[0723] Then, the first RO (272) of the first mapping cycle among the ROs of the second RO type is mapped to SSB index 2. In this case, the first RO (273) of the second mapping cycle is mapped to SSB index 0.

[0724] The SSB index mapped to the first RO (273) of the second mapping cycle is determined based on the SSB index mapped to the first RO (272) of the first mapping cycle (e.g., 2) and the number of ROs of the first RO type of the first mapping cycle (or the number of SSBs related to the ROs of the first RO type of the first mapping cycle, e.g., 3). For example, the SSB index mapped to the first RO (273) of the second RO type of the second mapping cycle can be determined by the sum of the SSB index mapped to the first RO (272) of the second RO type of the first mapping cycle (e.g., 2) and the number of ROs of the first RO type of the first mapping cycle (the number of SSBs related to the ROs of the first RO type of the first mapping cycle, e.g., 3). In this case, the sum becomes 5, which exceeds the maximum SSB index of 4, so it is mapped to SSB index 0.

[0725] The SSB index mapped to the first RO (274) of the second RO type of the third mapping cycle is determined based on the SSB index mapped to the first RO (273) of the second mapping cycle (e.g., 0) and the number of ROs of the first RO type of the second mapping cycle (or the number of SSBs related to the ROs of the first RO type of the second mapping cycle, e.g., 3). For example, the SSB index mapped to the first RO (274) of the second RO type of the third mapping cycle can be determined as 3 by the sum of the SSB index mapped to the first RO (273) of the second RO type of the second mapping cycle (e.g., 0) and the number of ROs of the first RO type of the second mapping cycle (or the number of SSBs related to the ROs of the first RO type of the second mapping cycle, e.g., 3).

[0726] In the same way, the SSB index mapped to the first RO (275) of the second RO type of the fourth mapping cycle becomes 1.

[0727] By this method, the SSB indices mapped to the first ROs (272, 273, 274, 275) of the second RO type in each mapping cycle become 2, 0, 3, and 1, thereby ensuring diversity of the SSB indices mapped to the ROs.

[0728] 5.3 CFRA Operation Based on SSB-RO Mapping Rules and SSB-RO Mapping Methods

[0729] The behavior of MAC CE and PDCCH commands can be described as follows.

[0730] 5.3.1 MAC CE Settings

[0731] In CFRA, information about the RO to be selected can be provided to the SBFD-aware UE through MAC CE settings. A configured preamble (e.g., a random access preamble index) can be specified through the associated MAC CE. A configured SSB can be specified through the associated MAC CE. To support this, the MAC CE associated with the SBFD CFRA may include one or more of the following fields.

[0732] 1) C: This field indicates the presence of CFRA (Contentless Random Access) resource fields. If the value of this field is set to 1, the following fields exist: Random Access Preamble Index Field, S / U Field, SS / PBCH Index Field, PRACH Mask Index Field, Iteration Count Field, and Reservation Bit within the same octet. If the value of this field is set to 0, these fields do not exist.

[0733] 2) S / U: This field indicates the uplink carrier to transmit the PRACH of the CFRA resources. If the value of this field is set to 1, SUL (Supplemental Uplink) is used; otherwise, NUL (Normal Uplink) is used.

[0734] 3) Random Access Preamble Index: This field indicates the random access preamble index of the CFRA resources. This field must not be set to 0b000000, and the field length is 6 bits.

[0735] 4) SS / PBCH Index: This field indicates the SS / PBCH to be used to determine / assess the RACH occasion for PRACH transfer of CFRA resources (contention-free Random Access Resources). The length of this field is 6 bits.

[0736] 5) PRACH Mask Index: This field indicates the RACH opportunity associated with the SS / PBCH indicated by the 'SS / PBCH Index' for the PRACH transfer of CFRA resources.

[0737] 6) Repetition Count: This field indicates the number of Msg1 repetitions to be applied to CFRA. If this field is set to 0, no Msg1 repetitions are applied. If this field is set to 1, the number of Msg1 repetitions is 2. If this field is set to 2, the number of Msg1 repetitions is 4. If this field is set to 3, the number of Msg1 repetitions is 8. The length of this field is 2 bits.

[0738] 7) RO Type: Indicates the type of RO indicated by the PRACH mask index.

[0739] In relation to the above 7), at least one of the following methods 1, 2, and 3 may be applied.

[0740] Method 1)

[0741] The PRACH mask index can indicate one of the following states.

[0742] One state: RO type 1 (RO of SBFD symbols)

[0743] One state: RO Type 2 (RO of non-SBFD symbols (and / or RO of flexible SBFD symbols)

[0744] One state: RO Type 3 (all ROs)

[0745] It may be reserved if there is no need to specify the RO set type. For example, this may be the case where the RO type is fixed to a single type by the network configuration.

[0746] Method 2)

[0747] The PRACH mask index can indicate one of the following states.

[0748] One state: Use only the RO of SBFD symbols

[0749] One state: Use all ROs currently set in the cell (e.g., ROs for SBFD symbols and ROs for non-SBFD symbols).

[0750] When the corresponding field is not provided, use only the RO of non-SBFD symbols.

[0751] Method 3)

[0752] The PRACH mask index can indicate one of the following states.

[0753] One state: Use only the RO of SBFD symbols

[0754] One state: Use only RO of non-SBFD symbols

[0755] If the corresponding field is not sent, all ROs currently set in the cell (e.g., ROs for SBFD symbols and ROs for Non-SBFD symbols) are used.

[0756] 8) Mapping Cycle Index: Can set / indicate which available mapping cycle among a number of mapping cycles containing the RO pointed to by the set / indicated RO type and RO mask index. For example, the mapping cycle index may include at least one of the following states.

[0757] One state: First available mapping cycle

[0758] One state: Second available mapping cycle.

[0759] One state: Last available mapping cycle.

[0760] If the corresponding mapping cycle does not exist, the state is reserved. Reserved values ​​are ignored by the UE.

[0761] 5.3.1.2 PDCCH command alt 1

[0762] When the PDCCH command is triggered, the fields associated with DCI format 1_0 may be specified as follows. The PDCCH command may include one or more of the following fields.

[0763] 1) Frequency domain resource assignment: All 1

[0764] 2) Random Access Preamble Index

[0765] A related preamble (e.g., ra-PreambleIndex) is given in advance. In this case, if no preamble is given for a specific type of RO, the RO type may not be distinguishable based on the given preamble value alone.

[0766] If a preamble setting associated with SBFD is supported, a random access preamble index associated with SBFD can be specified.

[0767] 3) SS / PBCH Index

[0768] The SSB value is given.

[0769] If a separate set of SSBs is configured for RO settings related to SBFD, gNB can allocate the relevant SSB index.

[0770] An SSB index can be set in an SSB set based on the RO type.

[0771] 4) PRACH Mask Index

[0772] This field indicates the RACH opportunity associated with the SS / PBCH indicated by the 'SS / PBCH index' for the PRACH transfer of CFRA resources.

[0773] 5) RO Type: Indicates the type of RO indicated by the PRACH mask index.

[0774] In relation to the above 5), at least one of the following methods 1 to 3 may be applied.

[0775] Method 1.

[0776] The PRACH mask index can indicate one of the following states.

[0777] One state: RO type 1 (RO of SBFD symbols)

[0778] One state: RO Type 2 (RO of non-SBFD symbols (and / or RO of flexible SBFD symbols)

[0779] One state: RO Type 3 (all ROs)

[0780] Cases where it is not necessary to specify the RO set type may be reserved. For example, this may be the case where the RO type is fixed to a single type by the network configuration.

[0781] Method 2.

[0782] The PRACH mask index can indicate one of the following states.

[0783] One state: Use only the RO of SBFD symbols

[0784] One state: Use all ROs currently set in the cell (e.g., ROs for SBFD symbols and ROs for non-SBFD symbols).

[0785] When the corresponding field is not provided, use only the RO of Non-SBFD symbols.

[0786] Method 3.

[0787] The PRACH mask index can indicate one of the following states.

[0788] One state: Use only the RO of SBFD symbols

[0789] One state: Use only RO of non-SBFD symbols

[0790] If the corresponding field is not sent, all ROs currently set in the cell (e.g., ROs for SBFD symbols and ROs for Non-SBFD symbols) are used.

[0791] 6) Mapping Cycle Index: Sets / indicates which available mapping cycle among a number of mapping cycles containing the RO pointed to by the set / indicated RO type and RO mask index. For example, the mapping cycle index may include at least one of the following states.

[0792] One state: First available mapping cycle

[0793] One state: Second available mapping cycle.

[0794] One state: Last available mapping cycle

[0795] If the corresponding mapping cycle does not exist, the state is reserved. The reserved value is ignored by the UE.

[0796] 7) Reserved bits

[0797] 5.3.1.2 PDCCH command alt 2

[0798] CFRA can be performed based on the nearest RO following the PDCCH command. In this case, specific RO types are not distinguished. The PDCCH command does not need to include an RO type field, but may include a mapping cycle index field. For example, if the PDCCH command is triggered, the fields related to DCI format 1_0 may be specified as follows. The PDCCH command may include one or more of the following fields.

[0799] 1) Frequency Domain Resource Allocation: All 1

[0800] 2) Random Access Preamble Index

[0801] The related preamble (e.g., ra-Preamble index) is given in advance.

[0802] In this case, if a preamble is not provided for a specific type of RO, the RO type may not be distinguishable based solely on the given preamble value.

[0803] If a preamble setting associated with SBFD is supported, a random access preamble index associated with SBFD can be specified.

[0804] 3) SS / PBCH Index

[0805] An SSB value can be given.

[0806] If a separate set of SSBs is configured for RO settings related to SBFD, gNB can allocate the relevant SSB index.

[0807] An SSB index can be set in an SSB set based on the RO type.

[0808] 4) PRACH Mask Index

[0809] This field indicates the RACH opportunity associated with the SS / PBCH indicated by 'SS / PBCH' for the PRACH transfer of CFRA resources.

[0810] 5) Mapping Cycle Index: Indicates which mapping cycle's PRACH mask index indicates the RO among multiple mapping cycles of the configured / instructed RO type. For example, it may include one or more of the following states.

[0811] One state: First available mapping cycle

[0812] One state: Second available mapping cycle.

[0813] One state: Last available mapping cycle

[0814] If the corresponding mapping cycle does not exist, the state is reserved. The reserved value is ignored by the UE.

[0815] 6) Reserved bits

[0816] FIG. 28 illustrates a method of operation of a terminal according to the present disclosure.

[0817] Referring to FIG. 28, the terminal receives information defining PRACH opportunities (physical random access channel occasion: RO) related to the SSB (Synchronization Signal Block) (S281).

[0818] The terminal transmits a random access preamble from at least one of the ROs, wherein the ROs include first type ROs and second type ROs, and the SSB start index of the second type ROs within a specific mapping cycle of SSB and RO is determined based on the SSB start index of the second type ROs within the mapping cycle immediately preceding the specific mapping cycle and the number of SSBs associated with the first type ROs (S282).

[0819] The above first type ROs are ROs associated with non-SBFD (subband full duplex) time resources, and the second type RO may be an RO associated with SBFD time resources.

[0820] For example, the first type ROs may be ROs that include only symbols designated as uplink or flexible by the TDD (time division duplex) setting, and the second type RO may be an RO associated with at least one SBFD symbol (e.g., an RO associated only with SBFD symbols that include at least one SBFD symbol designated as downlink by the TDD setting, or an RO that starts at an SBFD symbol and ends at non-SBFD symbols).

[0821] According to an embodiment, when the number of first type ROs related to SSB within the mapping cycle of the first type ROs is denoted as N (where N is a natural number) and the number of effective ROs among the second type ROs within the mapping cycle is denoted as M (where M is a natural number), if M is greater than N (M>N), the effective ROs among the MN*a (where a is a natural number) second type ROs may not be used for mapping between SSB and RO.

[0822] According to an embodiment, information indicating whether the ROs are a first type RO or a second type RO can be further received.

[0823] After determining the mapping between the SSB and RO for the first type ROs, an SSB index for the mapping between the SSB and RO for the second type ROs can be determined.

[0824] The SSB start indices within each mapping cycle of the above-mentioned second-type ROs may differ from each other. For example, as illustrated in FIG. 26, the SSB start indices associated with the second-type ROs within each mapping cycle may differ from each other, such as #1, #0, and #3.

[0825] The terminal can transmit the random access preamble during the CFRA (contention-free random access) process.

[0826] According to an embodiment, the at least one RO may be directed by a PDCCH (physical downlink control channel) order.

[0827] For example, the above PDCCH command may include an RO type field indicating either a first type RO or a second type RO. The RO type field may have a different name. For example, the RO type field may be called the 'RACH occasion indicator' field. The RO type field may consist of 1 bit.

[0828] According to an embodiment, the PDCCH command may include a mapping cycle index field indicating which mapping cycle among a plurality of mapping cycles the at least one RO is included in.

[0829] According to the embodiment, the CFRA process can be performed based on the nearest RO after receiving the PDCCH command.

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

[0831] According to the method of the present disclosure, an SSB index associated with a second type of RO (e.g., SBFD RO) can be mapped by taking into account the number of first type of RO (e.g., non-SBFD RO). As a result, even if the number of second type ROs is less or more than the number of first type ROs, diversity of SSB indices mapped to second type ROs within each mapping cycle can be ensured.

[0832] Through this, when various SSB indexes are sequentially mapped to various ROs, RACH resources can be provided more fairly distributed across a wider variety of beams (SSB indexes). This can prevent the load from being concentrated on specific ROs and contribute to increasing the overall RACH success rate.

[0833] FIG. 29 illustrates a signaling and operation method between a base station and a terminal.

[0834] Referring to FIG. 29, the base station provides the terminal with information defining ROs related to the SSB (S291). The terminal may be an SBFD-aware terminal.

[0835] The terminal determines at least one of the ROs including first type ROs and second type ROs, wherein the SSB start index of the second type ROs within a specific mapping cycle of SSB and RO is determined based on the SSB start index of the second type ROs within the mapping cycle immediately preceding the specific mapping cycle and the number of SSBs related to the first type ROs (S292).

[0836] The terminal transmits a random access preamble from at least one RO (S293).

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

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

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

[0840] The processor (102) receives information defining physical random access channel occasions (ROs) associated with a Synchronization Signal Block (SSB) and transmits a random access preamble from at least one of the ROs. The ROs include first type ROs and second type ROs, and the SSB start index of the second type ROs within a specific mapping cycle of the SSB and RO is determined based on the SSB start index of the second type ROs within the mapping cycle immediately preceding the specific mapping cycle and the number of SSBs associated with the first type ROs. The specific operation has been described above with reference to FIGS. 26 to 29.

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

[0842] The processor (202) transmits information defining physical random access channel occasions (ROs) related to a Synchronization Signal Block (SSB) to the terminal, and receives a random access preamble from at least one of the ROs from the terminal. The ROs include first type ROs and second type ROs, and the SSB start index of the second type ROs within a specific mapping cycle of SSB and RO is determined based on the SSB start index of the second type ROs within the mapping cycle immediately preceding the specific mapping cycle and the number of SSBs related to the first type ROs. The specific operation has been described above with reference to FIGS. 26 to 29.

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

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

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

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

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

[0848] For example, at least one computer-readable medium (CRM) containing an instruction based on execution by at least one processor performs the operation of receiving information defining physical random access channel occasions (ROs) related to a Synchronization Signal Block (SSB) and the operation of transmitting a random access preamble in at least one of the ROs, wherein the ROs include first type ROs and second type ROs, and the SSB start index of the second type ROs within a specific mapping cycle of the SSB and RO is determined based on the SSB start index of the second type ROs within the mapping cycle immediately preceding the specific mapping cycle and the number of SSBs related to the first type ROs. The specific operation has been described with reference to FIGS. 26 to 29.

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

[0850] 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, codes, 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0870] Referring to FIG. 34, a wireless communication device, for example, a terminal, may include at least one of a processor (2310), such as a digital signal processor (DSP) or a microprocessor, a transceiver (2335), a power management module (2305), an antenna (2340), a battery (2355), a display (2315), a keypad (2320), a Global Positioning System (GPS) chip (2360), a sensor (2365), a memory (2330), a Subscriber Identification Module (SIM) card (2325), a speaker (2345), and a microphone (2350). The antenna and the processor may be multiple.

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

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

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

[0874] 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. 34 may be the transceiver (106, 206) of FIG. 33.

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

[0876] FIG. 34 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. 34. For example, some components, such as a keypad (2320), a Global Positioning System (GPS) chip (2360), a sensor (2365), a SIM card (2325), etc., may not be essential and, in this case, may not be included in the terminal.

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

[0878] Referring to FIG. 35, 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.

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

[0880] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base station (200) and base station (200) / base station (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR), such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and inter-base station communication (150c) (e.g., relay, IAB (Integrated Access Backhaul)). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on various proposals of this specification, at least some of the following may be performed: various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc.

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

Claims

1. Regarding the method, The terminal receives information defining PRACH opportunities (physical random access channel occasions: RO) related to the SSB (Synchronization Signal Block), and The above terminal transmits a random access preamble in at least one of the above ROs, The above ROs include first type ROs and second type ROs, and A method characterized in that the SSB start index of the second type ROs within a specific mapping cycle of SSB and RO is determined based on the SSB start index of the second type ROs within the mapping cycle immediately preceding the specific mapping cycle and the number of SSBs related to the first type ROs.

2. In Paragraph 1, A method characterized in that the first type ROs are ROs associated with non-SBFD (subband full duplex) time resources, and the second type RO is an RO associated with SBFD time resources.

3. In Paragraph 1, A method characterized in that, when the number of first-type ROs related to SSB within the mapping cycle of the first-type ROs is N (where N is a natural number) and the number of effective ROs among the second-type ROs within the mapping cycle is M (where M is a natural number), if M is greater than N, the effective ROs among the MN*a (where a is a natural number) second-type ROs are not used for mapping between SSB and RO.

4. A method according to claim 1, characterized by further receiving information indicating whether the ROs are a first type RO or a second type RO.

5. A method according to claim 1, characterized by determining an SSB index for mapping between an SSB and an RO for the first type ROs, and then determining an SSB index for mapping between an SSB and an RO for the second type ROs.

6. A method according to claim 1, characterized in that the SSB start index within each mapping cycle of the second type ROs is different from one another.

7. A method according to claim 1, wherein the terminal transmits the random access preamble during the CFRA (contention-free random access) process.

8. A method according to claim 1, characterized in that at least one RO is directed by a PDCCH (physical downlink control channel) order.

9. A method according to claim 8, wherein the PDCCH command includes an RO type field indicating either a first type RO or a second type RO.

10. A method according to claim 8, wherein the PDCCH command comprises a mapping cycle index field indicating which mapping cycle among a plurality of mapping cycles the at least one RO is included in.

11. A method according to claim 8, characterized by performing a CFRA process based on the nearest RO after receiving the PDCCH command.

12. The terminal (user equipment: UE) is, At least one transmitter / receiver; At least one memory; and The above includes at least one transceiver and at least one processor connected to the above at least one memory, The above at least one memory includes instructions that are executed by the above at least one processor to perform operations, wherein The above operations are, Receive information defining PRACH opportunities (physical random access channel occasions: ROs) related to the SSB (Synchronization Signal Block), and The method includes transmitting a random access preamble in at least one of the above ROs, wherein The above ROs include first type ROs and second type ROs, and A terminal characterized in that the SSB start index of the second type ROs within a specific mapping cycle of SSB and RO is determined based on the SSB start index of the second type ROs within the mapping cycle immediately preceding the specific mapping cycle and the number of SSBs related to the first type ROs.

13. In Paragraph 12, A terminal characterized in that the first type ROs are ROs associated with non-SBFD (subband full duplex) time resources, and the second type RO is an RO associated with SBFD time resources.

14. In Paragraph 12, A terminal characterized in that, when the number of first type ROs related to the SSB within the mapping cycle of the first type ROs is N (where N is a natural number) and the number of effective ROs among the second type ROs within the mapping cycle is M (where M is a natural number), if M is greater than N, the effective ROs among the MN*a (where a is a natural number) second type ROs are not used for mapping between the SSB and the RO.

15. A terminal according to claim 12, characterized by further receiving information indicating whether the ROs are a first type RO or a second type RO.

16. A terminal according to claim 12, characterized by determining an SSB index for mapping between an SSB and an RO for the first type ROs, and then determining an SSB index for mapping between an SSB and an RO for the second type ROs.

17. A terminal according to claim 12, characterized in that the SSB start index within each mapping cycle of the second type ROs is different from one another.

18. In claim 12, the terminal is characterized by transmitting the random access preamble during the CFRA (contention-free random access) process.

19. A terminal according to claim 12, wherein at least one RO is directed by a PDCCH (physical downlink control channel) order.

20. A terminal according to claim 19, wherein the PDCCH command includes an RO type field indicating either a first type RO or a second type RO.

21. A terminal according to claim 19, wherein the PDCCH command comprises a mapping cycle index field indicating which mapping cycle among a plurality of mapping cycles the at least one RO is included in.

22. A terminal according to claim 19, characterized by performing a CFRA process based on the nearest RO after receiving the PDCCH command.

23. The device is, At least one memory; and The above includes at least one processor operably coupled with at least one memory, The above at least one memory includes instructions that are executed by the above at least one processor to perform operations, wherein The above operations are, Receive information defining PRACH opportunities (physical random access channel occasions: ROs) related to the SSB (Synchronization Signal Block), and The method includes transmitting a random access preamble in at least one of the above ROs, wherein The above ROs include first type ROs and second type ROs, and An apparatus characterized in that the SSB start index of second type ROs within a specific mapping cycle of SSB and RO is determined based on the SSB start index of second type ROs within the mapping cycle immediately preceding the specific mapping cycle and the number of SSBs related to first type ROs.

24. At least one computer-readable storage medium comprising instructions that are executed by at least one processor to perform operations, The above operations are, Receive information defining PRACH opportunities (physical random access channel occasions: ROs) related to the SSB (Synchronization Signal Block), and The method includes transmitting a random access preamble in at least one of the above ROs, wherein The above ROs include first type ROs and second type ROs, and At least one computer-readable storage medium characterized in that the SSB start index of the second type ROs within a specific mapping cycle of SSB and RO is determined based on the SSB start index of the second type ROs within the mapping cycle immediately preceding the specific mapping cycle and the number of SSBs related to the first type ROs.

25. Regarding the method, The base station transmits information to the terminal defining PRACH opportunities (physical random access channel occasions: RO) related to the SSB (Synchronization Signal Block), and The base station receives a random access preamble from at least one of the ROs from the terminal, The above ROs include first type ROs and second type ROs, and A method characterized in that the SSB start index of the second type ROs within a specific mapping cycle of SSB and RO is determined based on the SSB start index of the second type ROs within the mapping cycle immediately preceding the specific mapping cycle and the number of SSBs related to the first type ROs.

26. A 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, Transmit information defining PRACH opportunities (physical random access channel occasions: RO) related to the SSB (Synchronization Signal Block) to the terminal, and The method includes receiving a random access preamble from at least one of the ROs from the terminal, wherein The above ROs include first type ROs and second type ROs, and A base station characterized in that the SSB start index of the second type ROs within a specific mapping cycle of SSB and RO is determined based on the SSB start index of the second type ROs within the mapping cycle immediately preceding the specific mapping cycle and the number of SSBs related to the first type ROs.

Images