Multiple physical random access channel transmissions in sub-band full duplex operation

Abstract

To provide a method, UE, and a system for enhancing Physical Random Access Channel (PRACH) transmission in sub-band full duplex operation (SBFD).SOLUTION: A method includes, by user equipment (UE), receiving a configuration for SBFD operation and PRACH repetition, constructing a RACH occasion (RO) group on the basis of the configuration, and communicating with a base station using at least one RO from the RO group. The RO group includes one or more ROs from a set of SBFD symbols and a set of non-SBFD symbols.SELECTED DRAWING: Figure 19

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority and benefit under 35 U.S.C. § 119(e) to U.S. Provisional Application No. 63 / 574,767, filed April 4, 2024, entitled "Multiple PRACH Transmissions in SBFD Operation," U.S. Provisional Application No. 63 / 644,414, filed May 8, 2024, entitled "Multiple PRACH Transmissions in SBFD Operation," and U.S. Provisional Application No. 19 / 093,038, filed March 27, 2025, entitled "Multiple Physical Random Access Channel Transmissions in Sub-Band Full Duplex Operation," the disclosures of which are incorporated herein by reference in their entireties.

[0002]

[0002] 1. Technical field Aspects of some embodiments relate to wireless communications, for example, to improving physical random access channel (PRACH) transmissions in subband full duplex (SBFD) operation. [Background technology]

[0003] 2. Description of Related Art In subband full-duplex (SBFD) operation, some network nodes (e.g., base stations such as gNBs) may change their antenna configurations between SBFD symbols and non-SBFD symbols to address self-interference caused by simultaneous transmission and reception in full-duplex operation. Therefore, legacy PRACH repetition schemes may need to be adjusted or improved to accommodate the fact that some RACH occasions (ROs) in an RO group associated with a certain repetition number may correspond to SBFD symbols and other ROs may correspond to non-SBFD symbols. Terms such as an RO group associated with a particular repetition number and a set of the same number of valid PRACH occasions may be used interchangeably throughout this disclosure. For example, if a UE transmits multiple PRACH transmissions on ROs in the same RO group across SBFD and non-SBFD symbols, some of those transmissions may not be received by a gNB using the same receive (Rx) beam. Because the UE does not know whether the gNB changed its antenna configuration between SBFD and non-SBFD symbols, some of its transmissions may not be properly received by the gNB.

[0004]

[0004] Furthermore, in legacy New Radio (NR), if (e.g., if) the UE requests Msg3 repetition, the UE can select one of the RACH resources (e.g., RO and / or preamble) for requesting Msg3 repetition. For example, if (e.g., if) the UE determines the need for Msg3 repetition based on Msg3 transmitted in SBFD symbols, but (e.g., if) the UE transmits Msg3 on non-SBFD symbols, the UE's initial assessment may not be valid. Therefore, there is a need to improve PRACH transmission in SBFD operation.

[0005]

[0005] The above information disclosed in this Background Art section is intended merely to enhance understanding of the background art, and therefore, the information discussed in this Background Art section does not necessarily constitute prior art. Summary of the Invention

[0006]

[0006] Modern communication devices, also known as UEs (e.g., mobile phones, vehicles, laptops, satellites, and the like), can communicate with network nodes (e.g., gNBs) to receive data from and transmit data to networks associated with the network nodes. When there are multiple PRACH transmissions, applying legacy methods to construct RO groups can be problematic. For example, if an RO group includes an RO in an SBFD symbol and an RO in a non-SBFD symbol, the gNB may use different antenna configurations, resulting in inefficient reception of the PRACH transmissions. Furthermore, because the starting points for forming an RO group are different, the start of the RO group may not be aligned between legacy UEs and SBFD-aware UEs. This increases the complexity of blind detection at the gNB. Therefore, a method for constructing RO groups to enhance SBFD operation is desirable.

[0007]

[0007] A method according to one or more embodiments of the present disclosure includes: receiving, by a user equipment (UE), a configuration for subband full duplex (SBFD) operation and physical random access channel (PRACH) repetition; and The method may include the UE constructing a RACH Occasion (RO) group based on the configuration, where the RO group includes one or more ROs from a set of SBFD symbols and a set of non-SBFD symbols.

[0008] In one or more embodiments, one or more ROs in the group of ROs: At least one RO from the set of SBFD symbols; at least one RO from the set of non-SBFD symbols; and / or at least one RO from among the set of SBFD symbols and the set of non-SBFD symbols; Contains one or more of the following:

[0009] In one or more embodiments, an RO group includes multiple ROs and may include at least one RO from a set of SBFD symbols and at least one RO from a set of non-SBFD symbols.

[0010]

[0010] In one or more embodiments, the method may further include a step in which the UE transmits a communication signal to the base station, the communication signal being configured to establish communication between the UE and the base station based on the RO group.

[0011] In one or more embodiments, the step of establishing the RO group further includes: The method includes: a UE establishing a first set of RO groups and a second set of RO groups; each of the RO groups in the first set includes one or more ROs from the set of SBFD symbols; each of the RO groups in the second set includes one or more ROs from the set of non-SBFD symbols; The constructed RO group is included in a first set of RO groups and a second set of RO groups.

[0012] In one or more embodiments, each of the RO groups in the first set may include only one or more ROs in SBFD symbols, and each of the RO groups in the second set may include only one or more ROs in non-SBFD symbols.

[0013]

[0013] In one or more embodiments, the method further comprises the steps of: the UE receiving threshold data for determining the number of PRACH repetitions, the threshold data may be based on a Reference Signal Received Power (RSRP) level; The UE determines the number of PRACH repetitions by comparing the RSRP of the downlink path loss reference signal with threshold data; The constructed RO group may be based on the determined number of PRACH repetitions.

[0014]

[0014] In one or more embodiments, the threshold data may indicate a first threshold value provided by a first upper layer signaling for a first set of RO groups; The threshold data may indicate second thresholds provided by second upper layer signaling for a second set of RO groups; and The first threshold may be different from the second threshold.

[0015]

[0015] In one or more embodiments, the method may further include applying a legacy procedure to the first set of RO groups in response to a determination that the number of ROs in the SBFD symbol is different from the number of ROs in the non-SBFD symbol.

[0016]

[0016] In one or more embodiments, the method may further include a step of disabling an RO group including at least one RO from the set of SBFD symbols and at least one RO from the set of non-SBFD symbols.

[0017]

[0017] In one or more embodiments, the method may include a step of dropping at least one RO from an RO group including at least one RO from a set of SBFD symbols and at least one RO from a set of non-SBFD symbols, wherein the number of the dropped at least one RO is less than the number of remaining ROs.

[0018]

[0018] In one or more embodiments, at least one RO in an SBFD symbol and at least one RO in a non-SBFD symbol occupy different physical resource blocks (PRBs) and have the same frequency resource index.

[0019] In one or more embodiments, the method further comprises: receiving, by the UE, an indication through higher layer signaling; and the indication indicates whether the RO group includes at least one RO in an SBFD symbol and at least one RO in a non-SBFD symbol.

[0020] A UE according to some embodiments of the present disclosure may include a processing circuit, which: receiving a configuration regarding SBFD operation and PRACH repetitions; and The method is configured to perform the step of constructing an RO group based on the configuration, the RO group possibly including multiple ROs, the multiple ROs: RO in SBFD symbols; RO on non-SBFD symbols; at least one RO in an SBFD symbol and at least one RO in a non-SBFD symbol; and / or At least one RO across SBFD symbols and non-SBFD symbols; may contain.

[0021] A system according to some embodiments of the present disclosure may include a UE, wherein the UE: receiving a configuration regarding SBFD operation and PRACH repetitions; and The method is configured to perform the step of constructing an RO group based on the configuration, the RO group possibly including multiple ROs, the multiple ROs: RO in SBFD symbols; RO on non-SBFD symbols; at least one RO in an SBFD symbol and at least one RO in a non-SBFD symbol; and / or At least one RO across SBFD symbols and non-SBFD symbols; may contain. [Brief explanation of the drawings]

[0022]

[0022] These and other aspects of the present disclosure will be more clearly understood from the following detailed description of illustrative, non-limiting embodiments, taken in conjunction with the accompanying drawings. [Figure 1]

[0023] FIG. 1 illustrates an example four-step RACH procedure in Release 16 (Rel-16) in accordance with some embodiments of the present disclosure. [Figure 2]

[0024] FIG. 2 illustrates an example method for constructing an RO group according to some embodiments of the present disclosure. [Figure 3]

[0025] FIG. 3 illustrates an example RACH configuration shared between a legacy UE and an SBFD-enabled UE, in accordance with some embodiments of the present disclosure. [Figure 4]

[0026] FIG. 4 illustrates an example method for constructing two sets of RO groups according to some embodiments of the present disclosure. [Figure 5]

[0027] FIG. 5 illustrates an example UL-DL slot configuration with RO in SBFD symbols configured as flexible, in accordance with some embodiments of the present disclosure. [Figure 6A]

[0028] FIG. 6A illustrates an example method for handling RO replicas in SBFD symbols configured as flexible, according to some embodiments of the present disclosure. [Figure 6B]

[0029] FIG. 6B illustrates an example method for using RO outside of the UL sub-band, in accordance with some embodiments of the present disclosure. [Figure 7]

[0030] FIG. 7 illustrates an example method for disabling an RO group that includes ROs in both SBFD and non-SBFD symbols, according to some embodiments of the present disclosure. [Figure 8]

[0031] FIG. 8 illustrates an example method for disabling an RO group that includes an RO in an SBFD symbol configured as downlink and an SBFD symbol configured as flexible, according to some embodiments of the present disclosure. [Figure 9]

[0032] FIG. 9 illustrates an example method for excluding an RO with a symbol type different from the symbol type of the first RO in an RO group, according to some embodiments of the present disclosure. [Figure 10]

[0033] FIG. 10 illustrates an example method for excluding ROs in a first type symbol that have a smaller number than ROs in a second type symbol, according to some embodiments of the present disclosure. [Figure 11]

[0034] FIG. 11 illustrates an example method for excluding an RO in an SBFD symbol configured as flexible within an RO group that includes an RO in a downlink and an SBFD symbol configured as flexible, in accordance with some implementations of the present disclosure. [Figure 12A]

[0035] FIG. 12A illustrates an example shared RO configuration for legacy UEs, in accordance with some embodiments of the present disclosure. [Figure 12B]

[0036] FIG. 12B illustrates an example shared RO configuration for SBFD-enabled UEs, in accordance with some embodiments of the present disclosure. [Figure 13]

[0037] FIG. 13 is a diagram illustrating example preamble splitting between SBFD-enabled UEs and legacy UEs, in accordance with some embodiments of the present disclosure. [Figure 14]

[0038] FIG. 14 illustrates an example method for constructing RO groups with frequency offsets between ROs in SBFD symbols and ROs in non-SBFD symbols in accordance with some embodiments of the present disclosure. [Figure 15]

[0039] FIG. 15 illustrates an example method for constructing two sets of RO groups in response to frequency division multiplexed (FDMed) ROs, according to some embodiments of the present disclosure. [Figure 16]

[0040] FIG. 16 is a diagram illustrating an example RO group having a suitable number of ROs, according to some embodiments of the present disclosure. [Figure 17]

[0041] FIG. 17 is a diagram illustrating an example RO group including valid ROs in different RBs, according to some embodiments of the present disclosure. [Figure 18]

[0042] FIG. 18 is a diagram illustrating an example RO group in set 1 with SBFD symbols configured as flexible, according to some embodiments of the present disclosure. [Figure 19]

[0043] FIG. 19 is a flowchart illustrating an example method for constructing an RO group, according to some embodiments of the present disclosure. [Figure 20]

[0044] FIG. 20 is a block diagram of an electronic device in a network environment according to some embodiments of the present disclosure. [Figure 21]

[0045] FIG. 21 illustrates a system including a UE and a gNB communicating with each other in accordance with some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0023]

[0046] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the present disclosure. However, it will be understood by those skilled in the art that the disclosed aspects may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to obscure the subject matter disclosed herein.

[0024]

[0047] Throughout this specification, a reference to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with that embodiment may be included in at least one embodiment disclosed herein. Thus, the appearances of the phrases "in one embodiment," "in an embodiment," or "according to one embodiment" (or other phrases of similar import) in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In this regard, the word "exemplary" as used herein means "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" should not necessarily be construed as preferred or advantageous over other embodiments. Furthermore, particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. Furthermore, singular terms may include their corresponding plural forms, and plural terms may include their corresponding singular forms, depending on the context of the description herein. Similarly, hyphenated terms (e.g., "two-dimensional," "pre-determined," "pixel-specific," etc.) may sometimes be used interchangeably with their corresponding unhyphenated versions (e.g., "two-dimensional," "predetermined," "pixel-specific," etc.), and capitalized entries (e.g., "Counter Clock," "Row Select," "PIXOUT," etc.) may sometimes be used interchangeably with their corresponding uncapitalized versions (e.g., "Counter Clock," "Row Select," "Pixout," etc.). Such occasional interchangeable usages shall not be considered to be mutually inconsistent.

[0025]

[0048] Also, singular terms may include the corresponding plural, and plural terms may include the corresponding singular, depending on the context of the description herein. It should be further noted that the various figures (including component figures) shown and described herein are for illustrative purposes only and are not drawn to scale. For example, the dimensions of some elements may be exaggerated relative to other elements for clarity. Furthermore, where considered appropriate, reference numerals have been repeated among the figures to indicate corresponding and / or similar elements.

[0026]

[0049] The terminology used herein is for the purpose of describing some example embodiments only and is not intended to limit the claimed subject matter. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that, as used herein, the terms "comprises" and / or "comprising" specify the presence of stated features, elements, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, steps, operations, elements, components, and / or groups thereof.

[0027]

[0050] When an element or layer is referred to as being on, "connected to," or "coupled to" another element or layer, it will be understood that it can be directly on, connected to, or coupled to the other element or layer, or that there may be intervening elements or layers. In contrast, when an element is referred to as being "directly on," "directly connected to," or "directly coupled to" another element or layer, there are no intervening elements or layers. Like numbers refer to like elements throughout. As used herein, the terms "or" and "and / or" include any and all combinations of one or more of the associated listed items.

[0028]

[0051] As used herein, terms such as "first," "second," etc. are used as labels for the nouns they precede and do not imply any type of ordering (e.g., spatial, temporal, or logical) unless explicitly defined accordingly. Furthermore, the same reference numerals may be used across two or more figures to refer to parts, components, blocks, circuits, units, or modules having the same or similar functions. However, such usage is for ease of illustration and discussion only; it does not imply that the construction or architectural details of such components or units are the same across all embodiments or that such commonly-referenced parts / modules are the only way to implement some of the exemplary embodiments disclosed herein.

[0029]

[0052] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the subject matter of this application pertains. It will be further understood that terms as defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art, and not in an idealized or overly formal sense unless expressly defined herein accordingly.

[0030]

[0053] As used herein, the term "module" refers to any combination of software, firmware, and / or hardware configured to provide the functionality described herein with respect to the module. For example, software may be embodied as a software package, code, and / or an instruction set or instructions, and the term "hardware" as used in any implementation described herein may include, for example, an assembly, hardwired circuitry, a programmable circuit, a state machine circuit, and / or firmware that stores instructions executed by a programmable circuit, alone or in any combination. Modules may collectively or individually be embodied as circuits that form part of a larger system, such as, but not limited to, an integrated circuit (IC), a system-on-chip (SoC), an assembly, etc.

[0031]

[0054] The electronic or electrical devices and / or any other related devices or components according to the embodiments of the present disclosure described herein may be implemented using any suitable hardware, firmware (e.g., application-specific integrated circuits (ASICs)), software, or a combination of software, firmware, and hardware. For example, the various components of these devices may be formed on a single integrated circuit (IC) chip or on separate IC chips. Furthermore, the various components of these devices may be implemented on a flexible printed circuit film, a tape carrier package (TCP), a printed circuit board (PCB), or may be formed on a single substrate. Furthermore, the various components of these devices may be processes or threads running on one or more processors in one or more computing devices, executing computer program instructions and interacting with other system components to perform the various functions described herein. The computer program instructions are stored in memory, which may be implemented in the computing devices using standard memory devices such as random access memory (RAM). The computer program instructions may also be stored on other non-transitory computer-readable media, such as, for example, a CD-ROM, a flash drive, etc. Those skilled in the art will also recognize that the functionality of various computing devices may be combined or integrated within a single computing device, or that the functionality of a particular computing device may be distributed across one or more other computing devices, without departing from the spirit and scope of the exemplary embodiments of the present disclosure.

[0032]

[0055] In the 3GPP New Radio (NR) standard, a UE is designed to transmit various uplink (UL) signals to a base station (e.g., a gNB). In NR, the UE uses UL transmissions to convey various information to the gNB. In particular, the UE transmits user data to the gNB over a specific configuration of time and frequency resources, such as a Physical Uplink Shared Channel (PUSCH). Specifically, the Multiple Access (MAC) layer provides the user data intended for delivery to the corresponding layer at the gNB. The UE's Physical (PHY) layer receives MAC layer data as input and outputs a corresponding PUSCH signal via a PUSCH processing chain. Similarly, the UE transmits control data to the gNB over a Physical Uplink Control Channel (PUCCH). The control data may be Uplink Control Information (UCI) and may be considered as the payload for the PUCCH signal.

[0033]

[0056] Conversely, the UE is designed to receive various downlink (DL) signals from the gNB. Similar to UL transmissions, the UE receives DL transmissions and extracts various information from the gNB. The UE receives user data from the gNB on a specific configuration of time and frequency resources, such as a Physical Downlink Shared Channel (PDSCH). The UE's PHY layer extracts data from the physical signals received on the PDSCH and provides the data to the MAC layer. Similarly, the UE receives control data from the gNB on a Physical Downlink Control Channel (PDCCH). The control data is Downlink Control Information (DCI) and may be considered as the payload for the PDCCH.

[0034]

[0057] Furthermore, the UE is provided with a search space (SS) set configuration and a control resource set (CORESET) configuration for monitoring DCI in the PDCCH in the serving cell. In particular, the SS set configuration provides PDCCH monitoring occasion information in the time domain, and each monitoring occasion is associated with a CORESET configuration linked to the SS set configuration. The CORESET configuration provides a symbol duration and a set of resource blocks (RBs) for monitoring PDCCH candidates, where the PDCCH candidates include a set of control channel elements (CCEs) according to the aggregation level. A CCE may include six resource element groups (REGs), and each REG may be a group of 12 consecutive resource elements (REs). For example, the UE monitors a set of REs for PDCCH candidates located in a specified time and frequency domain based on the CORESET and SS set configurations.

[0035]

[0058] Another physical signal transmitted by the UE may be a Physical Random Access Channel (PRACH) signal. Similar to Long Term Evolution (LTE) cellular systems, communication between the UE and the gNB is frame-based. During the initial access procedure, the UE UL transmission is not time-aligned with the gNB frame timing due to the lack of consideration of round-trip delay. To synchronize the frame timing for both the UE and the gNB, e.g., UL and DL transmissions, the UE transmits a PRACH signal, which is used by the gNB to estimate the round-trip delay. The UE is informed of the Timing Adjustment (TA) value required to apply to its UL transmission for appropriate adjustment of the frame timing. Therefore, during the initial access procedure, the UE transmits a PRACH signal in addition to acquiring system information from the gNB.

[0036]

[0059] 1 illustrates an example four-step RACH procedure in Release 16 (Rel-16), in accordance with some embodiments of the present disclosure. Similar to LTE, a UE performs an initial access procedure through a random access (RA) process.

[0037]

[0060] Before initiating the random access procedure, the UE receives system information (e.g., Master Information Block (MIB) / System Information Block (SIB)) broadcast from the gNB using Synchronization Signal Block (SSB) transmissions. For example, the UE attempts to receive the broadcast information, which provides the UE with the necessary information for retrieving the MIB and SIB. The system information may provide the UE with information regarding the configuration of the random access procedure. Multiple SSBs are typically broadcast in a periodic manner, where each SSB is transmitted by the gNB using a different broad transmission beam. The UE then attempts to decode the various SSBs and selects an appropriate SSB (e.g., the best SSB or the SSB with the highest Reference Signal Received Power (RSRP)). Such an SSB may indicate an appropriate beam (e.g., the best broad beam) to be used by the gNB for communication with the UE.

[0038]

[0061] The four-step RACH procedure can be described as follows:

[0039]

[0062] (1) The UE starts by transmitting a preamble to the gNB, for example, by transmitting Msg1 to the gNB. The UE selects one preamble from a pool of suitable / possible preambles. The identifier (ID) of the preamble selected by the UE may be a Random Access Preamble Identifier (RAPID). At this point, multiple UEs may be simultaneously starting the four-step RA process, and each UE may use a preamble with a different RAPID.

[0040]

[0063] (2) In response to successful reception of the preamble by the gNB, the gNB transmits Msg2 to the UE (downlink transmission (DL Transmission)). Msg2 includes the RAPID of the preamble selected by one UE (or multiple UEs in case of contention), a Timing Advance (TA) value for the UE with the corresponding RAPID, and an UL grant (including, for example, PUSCH frequency resource, PUSCH time resource, MCS, TPC, etc.) for the transmission of Msg3.

[0041]

[0064] (3) The UE proceeds by transmitting Msg3 using the resources indicated in the UL grant. Msg3 contains the Contention Resolution ID (CRID) provided to the UE's physical layer by higher layers. The UE applies the TA value indicated in Msg2 to the transmission of Msg3 (TA applied). Note that no TA was applied for Msg1. If (for example) multiple UEs have the same RAPID, all UEs will transmit Msg3 containing different CRIDs.

[0042]

[0065] (4) The gNB sends Msg4 containing the CRID of one UE. The UE with the corresponding CRID proceeds by sending an acknowledgement (ACK) message confirming successful reception of Msg4 and the initial access procedure.

[0043]

[0066] When selecting a preamble for Msg1 transmission (e.g., in this case), the UE first determines a group from a collection of preamble groups from which the UE selects a particular preamble. The collection of groups is non-intersecting pools (e.g., non-overlapping pools) of preambles configured by the gNB in ​​the cell. In response to the UE selecting a preamble from a particular group, the gNB determines which group was selected by the UE upon receiving the preamble. A designation method may be used in a four-step RACH process to indicate information about the pathloss level between the UE and the gNB and the potential payload size of Msg3. For example, in a four-step RACH process, the gNB configures two groups of preambles, e.g., Group A and Group B. In response to the pathloss between the UE and the gNB exceeding a configured threshold and / or the expected payload size of Msg3 exceeding a certain threshold, the UE selects Group B. On the other hand, in response to the path loss between the UE and the gNB being below a configured threshold and / or in response to the expected payload size of Msg3 being below a certain threshold, the UE selects Group A.

[0044]

[0067] After the UE transmits Msg1 and Msg3, the UE begins monitoring for an expected reply from the gNB. When the last symbol of Msg1 (or Msg3) is transmitted, the UE starts a monitoring timer (e.g., a monitoring window) at the beginning of the following symbol of CORESET, where the Msg3 (or Msg4) scheduling DCI is expected to be received. The monitoring window duration is configured by RRC in the UE. If a retransmission is required, the UE receives DCI 0_0 within the window that schedules the retransmission of Msg3. The monitoring window restarts after each retransmission.

[0045]

[0068] Multiple PRACH transmissions may be used to extend the PRACH coverage. For multiple PRACH transmissions, the UE constructs multiple groups of valid ROs. The definition of a valid RO is based on existing specifications. For example, an RO is considered invalid if it partially or completely overlaps with a symbol configured as "D" (downlink) by tdd-UL-DL-ConfigurationCommon. Configuring multiple PRACH transmissions is based on the same framework of feature combinations introduced for multiple features, such as Msg 3 repetition. For example, the multiple PRACH transmission procedure may be considered as a new preamble feature, and each Msg 1 repetition value (e.g., 2, 4, and / or 8) is treated as a separate preamble feature. The gist is as follows:

[0046]

[0069] (1) In BWP-UplinkCommon, a list of rach-ConfigCommon-r17 is configured in addition to the legacy rach-ConfigCommon. For this purpose, a new RRC parameter Additional-RACH-ConfigList-r17 is used.

[0047]

[0070] (2) rach-ConfigCommon-r17 is exactly the same as rach-ConfigCommon, but additionally contains a featureCominationPreamblesList-r17 associated with this RACH configuration. This means that the gNB can configure a separate RO for the same RO or feature combinations as used for legacy rach-ConfigCommon.

[0048]

[0071] (3) The gNB can use featureCominationPreambles to determine the RACH resources to be used for this feature combination from those configured by rach-ConfigCommon-r17, in particular to indicate which RO (via ssb-SharedRO-MaskIndex) and which preamble (via startPreambleForThisPartition and numberOfPreamblesPerSSB-ForThisPartition).

[0049]

[0072] The number of valid ROs constituting an RO group is determined by the number of Msg1 repetitions provided via Msg1-RepetitionNum-r18 in featureCominationPreambles. Since multiple Msg1 repetition values, e.g., 2, 4, or 8, can be configured, the gNB may determine the RSRP level to select the Msg1 repetition value. For example, three RRC parameters, e.g., rsrp-ThresholdMsg1-RepetitionNum2-r18, rsrp-ThresholdMsg1-RepetitionNum4-r18, and rsrp-ThresholdMsg1-RepetitionNum8-r18 in BWP-UplinkCommon, may be configured. The UE compares the RSRP of the downlink path loss criterion with the configured threshold for 2, 4, and 8 repetitions. For 8 repetitions, if the measured RSRP is less than the threshold, the 8-repetition Msg1 is applicable, and so on.

[0050]

[0073] Based on the configured number of Msg1 repetitions, the UE configures multiple RO groups, where each RO group consists of {2, 4, 8} valid ROs, and transmits the same selected preamble in the first RO in the RO group. The ROs included in an RO group are contiguous in time, use the same frequency resources (occupying the same RBs), and are associated with the same one or more SS / PBCH block indices, where each SS / PBCH block index is associated with the same preamble index in all valid PRACH occasions in the RO group.

[0051]

[0074] An RO group is determined based on its first valid RO within a group. The first RO in the first RO group is the first valid RO in frame 0. The first RO in subsequent RO groups is determined in ascending order, first in the frequency domain and then in the time domain. Successive RO groups are either back-to-back or separated by TimeOffsetBetweenStartingRO consecutive valid ROs.

[0052]

[0075] FIG. 2 illustrates an example RO group configuration for SSB#0 for two Msg1 repetitions. The first RO (e.g., the first initiating RO (1)) in the first RO group 210 is st The first RO (e.g., second starting RO (205)) of a subsequent RO group (e.g., second RO group 220) is determined in the frequency domain and the time domain. nd The first RO (e.g., the third starting RO (215)) of a subsequent RO group (e.g., the third RO group 230 and the fourth RO group 240) is ordered in increasing order in the frequency domain and then in the time domain. rd starting RO) 225 and the fourth starting RO (4 th The starting RO) 235) is determined in the time domain next.

[0053]

[0076] In legacy single PRACH transmission, an association pattern period is used to simplify implementation for the UE and gNB. For example, an association pattern period includes one or more association periods, and is determined such that the association pattern between PRACH occasions (ROs) and SS / PBCH block indices is repeated at most every 160 msec. In other words, the UE does not need to know the association between ROs and SSBs starting from frame 0 to be able to determine the association between SSBs and ROs in later frames. The UE can determine the association pattern period, and the association pattern between SSBs and ROs is repeated in each association pattern period.

[0054]

[0077] The concept of association pattern period may also be applied to the repetition of Msg1, where the pattern of RO groups is repeated in each time period. For example, a set of RO groups for a set number of PRACH transmissions is determined in time period X, starting from frame 0. The determined set of RO groups is repeated every time period X. The value of X is the smallest integer number of association pattern periods, so that N Tx SSB At least one set of valid PRACH occasions for each SS / PBCH block index can be determined within a time period for all configured numbers of preamble repetitions. In other words, if (e.g., if) a UE is configured with multiple repetition values, only a single value (e.g., the value of X) applies to all configured values.

[0055]

[0078] The number of Msg1s actually transmitted may be less than the configured number of repetitions. For example, legacy PRACH exclusion rules may apply, e.g., when the PRACH and other UL channels (e.g., PUSCH, PUCCH, and / or SRS) are in the same slot and / or there is no sufficient gap in the time domain. To handle the transmission of two PRACHs when there is no sufficient gap in the time domain, Rel-18 introduces additional exclusion rules. The UE will not transmit the first and second PRACH repetitions when there is no sufficient time gap, unless the UE indicates that it may support such functionality through capability signaling.

[0056]

[0079] Therefore, a method may be needed to construct the set of RO groups and apply additional exclusion rules in response to the determined set of RO groups being associated with particular numbers of repetitions in SBFD symbols and other numbers of repetitions in non-SBFD symbols. Additionally, there is a need for an improved PRACH transmission in SBFD operation in response to evaluation of Msg3 repetitions.

[0057]

[0080] One or more aspects of the present disclosure provide configured / predefined behavior for treating an RO that spans both SBFD and non-SBFD symbols as if it were an RO that fits entirely within one particular symbol type, e.g., an RO that fits entirely within an SBFD symbol or entirely within a non-SBFD symbol.

[0058]

[0081] Furthermore, one or more aspects of the present disclosure provide set / predefined rules to be applied to an RO that falls entirely within an SBFD symbol to determine whether such an RO should be treated as an RO that falls entirely within an SBFD symbol or a non-SBFD symbol. For example, in response to the first or last instance of such an RO being within an SBFD symbol, an RO that spans both an SBFD symbol and a non-SBFD symbol is treated as if the RO were entirely within the SBFD symbol rather than within a non-SBFD symbol.

[0059]

[0082] Based on the configuration, the gNB can instruct the UE how to handle an RO that spans both SBFD and non-SBFD symbols. This instruction can be conveyed via higher layer signaling, e.g., an RRC parameter, in the remaining minimum System Information (RMSI), Other System Information (OSI), and / or UE-specific signaling. For example, in response to the RRC parameter being set to "SBFD," the UE can treat an RO that spans both SBFD and non-SBFD symbols as if it were an RO that falls entirely within an SBFD symbol.

[0060]

[0083] In some embodiments, an SBFD symbol may be defined as a symbol using subbands that a gNB uses for SBFD operations, e.g., DL subband(s) and / or UL subband(s).

[0061]

[0084] Throughout this disclosure, legacy UEs may refer to UEs that support earlier releases of NR, or even Rel-19 or later, but do not recognize SBFD configurations.

[0062]

[0085] Regarding the RACH configuration for legacy UEs and SBFD-enabled UEs (SBFD-aware UEs), a shared RACH configuration, RO, and preamble between legacy UEs and SBFD-enabled UEs may be used. For example, legacy UEs are not affected by the presence of SBFD-enabled UEs because the RACH resources are not partitioned. SBFD-enabled UEs may use SBFD symbols and non-SBFD symbols. For example, SBFD-enabled UEs may use RACH resources in both SBFD and non-SBFD symbols, or alternatively, SBFD-enabled UEs may use RACH resources only in SBFD symbols.

[0063]

[0086] In this scenario, the gNB may provide the same RACH configuration to the SBFD-enabled UE as it provides to the legacy UE. An additional offset in the frequency or time domain or a different interpretation of the legacy RACH configuration parameters, such as Msg1-FrequencyStart, may be applied to the ROs in the SBFD symbols to ensure that most of them are within the UL subband.

[0064]

[0087] An SBFD-enabled UE may apply different validation rules to ROs in SBFD symbols in addition to the legacy validation rules, e.g., an RO that falls entirely within the UL subband is a valid RO.

[0065]

[0088] 3 illustrates an example RACH configuration shared between a legacy UE and an SBFD-enabled UE, according to some embodiments of the present disclosure. The top diagram shows a DL-UL-TDD slot configuration period from the perspective of a legacy UE, and the bottom diagram shows a DL-UL-TDD slot configuration period from the perspective of an SBFD-aware UE. In the diagram, "v" is a valid RO and "x" is an invalid RO.

[0066]

[0089] Allowing SBFD-capable UEs to use RACH resources in both SBFD and non-SBFD symbols may reduce the latency experienced by SBFD-capable UEs and provide more RACH resources for SBFD-capable UEs, potentially enhancing coverage.

[0067]

[0090] In the case of multiple PRACH transmissions, applying legacy methods to construct RO groups can be problematic. Depending on whether the RO group spans both SBFD and non-SBFD symbols, the gNB may use different antenna configurations, resulting in inefficient reception of the PRACH transmissions. Furthermore, the start of the RO group may not be aligned between legacy and SBFD-capable UEs, e.g., the starting point for forming the RO group may differ. This increases the complexity of blind detection at the gNB.

[0068]

[0091] Referring to Figure 3, the number of PRACH transmissions can be set to 4. A legacy UE identifies a different set of valid ROs than the set identified by an SBFD-enabled UE. Therefore, the RO groups established by the legacy UE and the RO groups established by the SBFD-enabled UE are not aligned, e.g., group #x for the legacy UE and group #y+2 for the SBFD-enabled UE are not aligned. Furthermore, some RO groups identified by the SBFD-enabled UE span both SBFD and non-SBFD symbols, e.g., group #y+2 and group #y+5.

[0069]

[0092] FIG. 4 illustrates an example method for constructing two sets of RO groups according to some embodiments of the present disclosure.

[0070]

[0093] To address the issue of RACH configurations shared between legacy and SBFD-enabled UEs, an SBFD-enabled UE may construct two sets of RO groups, where each set of RO groups may contain only ROs in the same type of symbol, e.g., only ROs in SBFD symbols or only ROs in non-SBFD symbols. For example, one set of RO groups may contain ROs that fall entirely in SBFD symbols (i.e., only ROs that fall exclusively in SBFD symbols), and another set of RO groups may contain ROs that fall entirely in non-SBFD symbols (i.e., only ROs that fall exclusively in non-SBFD symbols).

[0071]

[0094] Referring to FIG. 4, Set 0 (e.g., the first set of RO groups) may include RO groups constructed by ROs in SBFD symbols. For example, RO group #y+2 in Set 0 includes ROs in SBFD symbols, excluding ROs in non-SBFD symbols. Similarly, Set 1 (e.g., the second set of RO groups) may include RO groups constructed by ROs in non-SBFD symbols. For example, RO group #y+3 in Set 1 includes ROs in non-SBFD symbols, excluding ROs in SBFD symbols.

[0072]

[0095] In one or more embodiments, an SBFD symbol is configured in a symbol configured as downlink by tdd-UL-DL-ConfigurationCommon. Therefore, an RO corresponding to this SBFD symbol is considered invalid for legacy UEs. On the other hand, an RO in an SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon may be valid for legacy UEs.

[0073]

[0096] In one or more embodiments, an SBFD-capable UE may include ROs in SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon in a set of ROs in non-SBFD symbols (e.g., set 1), which is beneficial for aligning RO group boundaries between legacy UEs and SBFD-capable UEs.

[0074]

[0097] FIG. 5 illustrates an example UL-DL slot configuration with RO in SBFD symbols configured as flexible, in accordance with some embodiments of the present disclosure.

[0075]

[0098] The SBFD symbol shown in Figure 4 may be configured in a symbol configured as downlink by tdd-UL-DL-ConfigurationCommon. Therefore, the RO corresponding to this SBFD symbol is considered invalid for legacy UEs. On the other hand, the RO in an SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon may be valid for legacy UEs.

[0076]

[0099] In one or more embodiments, an SBFD-capable UE may include ROs in SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon in a set of ROs in non-SBFD symbols (e.g., Set 1 shown in FIG. 5), which is beneficial for aligning RO group boundaries between legacy UEs and SBFD-capable UEs.

[0077]

[0100] Referring to Figure 5, the UL-DL slot configuration may be provided as DDDFU (e.g., DL, DL, DL, Flexible, and UL) by the tdd-UL-DL-ConfigurationCommon using several ROs corresponding to the flexible symbols. An SBFD-capable UE uses ROs in SBFD symbols configured as flexible for RO groups configured in Set 1 (e.g., RO groups using ROs in non-SBFD symbols). In this case, the SBFD-capable UE configures RO groups in Set 0 (e.g., RO groups using ROs in SBFD symbols) using ROs in SBFD symbols configured as downlink by the tdd-UL-DL-ConfigurationCommon. For example, RO groups #y, #y+1, #y+4, #y+6, #y+7, etc. in Set 0 are configured from valid ROs in SBFD symbols configured as downlink by the tdd-UL-DL-ConfigurationCommon. On the other hand, RO groups #y+2, #y+3, #y+5, #y+8, #y+9, etc. in set 1 consist of valid ROs in SBFD symbols and non-SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon.

[0078]

[0101] Alternatively, an SBFD-capable UE may consider ROs in SBFD symbols configured as flexible by the tdd-UL-DL-ConfigurationCommon, even if they are ROs in SBFD symbols configured as downlink by the tdd-UL-DL-ConfigurationCommon. For example, an SBFD-capable UE does not distinguish between ROs in SBFD symbols configured as downlink or flexible by the tdd-UL-DL-ConfigurationCommon. In this case, two sets of RO groups may be configured as shown in FIG. 4. This may be beneficial if (e.g., if) power control parameters separate from legacy power control parameters are likely to be used to transmit the PRACH in SBFD symbols configured in either downlink or flexible symbols by the tdd-UL-DL-ConfigurationCommon.

[0079]

[0102] In some embodiments, if (e.g., if) the RO is in an SBFD symbol configured as "F" by tdd-UL-DL-ConfigurationCommon, two sets of RO groups may be constructed.

[0080]

[0103] FIG. 6A illustrates an example method for handling RO replicas in SBFD symbols configured as flexible, according to some embodiments of the present disclosure.

[0081]

[0104] If (for example) an SBFD-capable UE applies an additional offset in the frequency domain or a different interpretation of legacy RACH configuration parameters such as Msg1-FrequencyStart, this could create two effective replicas of an RO in an SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon. Therefore, it is beneficial to determine how RO groups are constructed. An SBFD-capable UE can include an RO in an SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon in the set of ROs in non-SBFD symbols, such as Set 1 shown in FIG. 5.

[0082]

[0105] In one or more embodiments, for RO replicas in SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon, an SBFD-capable UE may use only ROs that fall within the UL subband. This configuration aligns with the SBFD symbol definition, which states that UL transmissions are not allowed outside the UL subband. As a result, RO groups may contain ROs that do not occupy the same resource block (RB), as shown in Figure 6A. For example, RO group #y+2 in Figure 6A contains three ROs in the UL subband and one RO in the non-SBFD UL symbol. RO group #y+3 in Figure 6A contains two ROs in the non-SBFD UL symbol and two ROs in the UL subband.

[0083]

[0106] In some embodiments, an SBFD-capable UE may operate as a legacy UE to handle RO replicas in an SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon, i.e., this SBFD symbol may be considered a non-SBFD symbol and legacy UE behavior may apply.

[0084]

[0107] 6B illustrates an example method for using ROs outside the UL subband, according to some embodiments of the present disclosure. For example, RO group #y+2 includes ROs that occupy the same physical resource blocks (PRBs) as legacy UEs.

[0085]

[0108] For an SBFD capable UE operating as a legacy UE, one or more methods may be provided as follows:

[0086]

[0109] (1) An additional offset to the location of the RO in the frequency domain or a different interpretation of a legacy RACH configuration parameter, such as Msg1-FrequencyStart, may only be applied in SBFD symbols configured as downlink by tdd-UL-DL-ConfigurationCommon. In other words, the RO offset and different interpretation may not be applied to ROs in SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon. In practice, an SBFD-capable UE may operate as a legacy UE to use ROs in SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon. For example, an RO in an SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon falls in the downlink subband and may be considered invalid and not used by the SBFD-capable UE if (e.g., if) the SBFD-capable UE operates as an SBFD-capable UE. On the other hand, in response to the RO falling in the UL subband, the RO is valid and may be used by the SBFD-capable UE.

[0087]

[0110] (2) The validation rules for SBFD-capable UEs may consider an RO in an SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon as invalid, regardless of whether the RO falls within a UL subband. For example, an RO in an SBFD symbol configured as "F (Flexible)" is considered invalid regardless of whether it falls within a UL subband.

[0088]

[0111] Therefore, an SBFD-enabled UE may apply one or more of the above methods and / or any combination of one or more methods to determine valid ROs and / or any other procedures (e.g., exclusion rules), and then construct an RO group based on the valid ROs.

[0089]

[0112] Alternatively, an SBFD-capable UE may consider ROs in SBFD symbols configured as flexible by the tdd-UL-DL-ConfigurationCommon as if they were ROs in SBFD symbols configured as downlink by the tdd-UL-DL-ConfigurationCommon. In other words, an SBFD-capable UE does not distinguish between ROs in SBFD symbols configured as downlink or flexible by the tdd-UL-DL-ConfigurationCommon. An SBFD-capable UE may consider RO replicas outside the UL subband as invalid. In this case, the two sets of RO groups may be configured as shown in FIG. 4. This may be beneficial if (e.g., if) power control parameters separate from legacy power control parameters are used to transmit PRACH in SBFD symbols configured as either downlink or flexible by the tdd-UL-DL-ConfigurationCommon.

[0090]

[0113] FIG. 7 illustrates an example method for disabling an RO group that includes ROs in both SBFD and non-SBFD symbols, according to some embodiments of the present disclosure.

[0091]

[0114] It may be beneficial for the gNB to specify whether the UE establishes two sets of RO groups. Furthermore, the gNB may indicate to the UE which set of RO groups should be used. One set of RO groups may include RO groups for valid ROs in SBFD symbols, and another set may include RO groups for valid ROs in non-SBFD symbols. For example, some gNBs may use the same antenna configuration for both SBFD and non-SBFD symbols, and they (e.g., RO transmissions in SBFD and non-SBFD symbols) do not expect reception degradation. Furthermore, such gNBs may address the additional complexity of handling inconsistent RO groups between legacy and SBFD-capable UEs. To this end, the gNB may provide an indication to the UE (e.g., legacy UE and / or SBFD-capable UE) via higher layer signaling, such as the RRC parameter RO_group_twoSets. Such an RRC parameter may be provided via RMSI, OSI, and / or dedicated higher layer signaling. In the absence of such an indication, a default behavior may be defined such that two sets of RO groups are constructed. Furthermore, the decision of whether to construct two sets of RO groups (e.g., Set 0 and Set 1) or which set of them to use may be determined based on a threshold. In some embodiments, the threshold may be predefined / configured, e.g., defined in a specification and / or provided via higher layer signaling, e.g., RMSI, OSI, and / or UE-dedicated RRC signaling. The threshold may be determined / configured based on the L1-RSRP of the selected Synchronization Signal Block (SSB) / Channel State Information Reference Signal (CSI-RS) for PRACH transmission.For example, if (e.g., if) an SBFD-enabled UE is in poor coverage and the measured L1-RSRP is below a provided / determined threshold, the SBFD-enabled UE may select an RO group in Set 0 or an RO group in Set 1.

[0092]

[0115] In one or more embodiments, RO groups may be constructed as in legacy (e.g., according to legacy procedures). For example, RO groups may be constructed without distinguishing ROs between SBFD and non-SBFD symbols. In some embodiments, RO groups that include ROs for both SBFD and non-SBFD symbols may not be used for transmitting PRACH repetitions.

[0093]

[0116] 7, each RO group may include four valid ROs for multiple PRACH transmissions. For example, some RO groups that span both SBFD and non-SBFD symbols, RO groups #y+2 and #y+5, may not be used in multiple PRACH transmissions. In some embodiments, in response to the UE determining to use an RO for a single PRACH transmission, any of the ROs may be used; for example, RO groups #y+2 and #y+5 may be valid for a single PRACH transmission.

[0094]

[0117] A new validation rule at the RO group level may be applied to exclude RO groups that contain at least one RO in an SBFD symbol and at least one RO in a non-SBFD symbol. For example, an RO group may be considered invalid in response to ROs within the RO group spanning both SBFD and non-SBFD symbols, even though each RO may be valid individually.

[0095]

[0118] FIG. 8 illustrates an example method for disabling an RO group that includes an RO in an SBFD symbol configured as downlink and an SBFD symbol configured as flexible, according to some embodiments of the present disclosure.

[0096]

[0119] An example of four PRACH repetitions with some ROs falling on SBFD symbols configured as flexible is shown in Figure 8. For example, RO group #y+1 is considered invalid because it contains ROs in downlink and SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon.

[0097]

[0120] In one or more embodiments, if an RO is configured based on an SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon and an RO group includes an RO in both the downlink and SBFD symbols configured as flexible (e.g., if so), the entire RO group may be considered invalid. Because an RO in an SBFD symbol configured as flexible may be visible to legacy UEs, an RO group including an RO in an SBFD symbol configured as flexible may be excluded. Furthermore, if an SBFD-capable UE applies an additional offset to the position of the RO in the frequency domain or applies a different interpretation of legacy RACH configuration parameters (e.g., if so), the RO may be moved to be in the UL subband. In this case, legacy UEs may use an RO that is in the DL subband, while SBFD-capable UEs may use a replica RO that is in the UL subband. Therefore, if (e.g., if) switching from an SBFD symbol configured as downlink by tdd-UL-DL-ConfigurationCommon to an SBFD symbol configured as flexible ensures that the performance of legacy UEs is not adversely affected, the gNB may need to change its antenna configuration.

[0098]

[0121] It is beneficial to avoid using RO groups that include ROs in the downlink and SBFD symbols configured as flexible. In response to the use of such RO groups, the antenna configuration of the gNB may need to be adjusted across different PRACH repetitions within the RO group. Furthermore, RO groups established by legacy UEs and SBFD-enabled UEs may not be aligned.

[0099]

[0122] Alternatively, an SBFD-capable UE may consider ROs in SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon as if they were ROs in SBFD symbols configured as downlink by tdd-UL-DL-ConfigurationCommon. In other words, an SBFD-capable UE does not distinguish between ROs in SBFD symbols configured as downlink or flexible by tdd-UL-DL-ConfigurationCommon. In this case, an RO group containing at least one RO in a non-SBFD symbol and at least one RO in an SBFD symbol is considered invalid, regardless of whether the ROs are configured as downlink or flexible, which is similar to the exclusion rule described in Figure 7.

[0100]

[0123] In one or more embodiments, the RO group verification level may be applied when part of the RO configured for a legacy UE is outside the UL subband. For example, an SBFD-enabled UE may apply an additional offset to the position of the RO in the frequency domain or apply a different interpretation of the legacy RACH configuration parameters to move the RO in the UL subband. Therefore, a method for handling RO replicas in SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon to configure the RO group may be applied. For example, one or more methods may be provided as follows:

[0101]

[0124] (1) An additional offset to the location of the RO in the frequency domain or a different interpretation of the legacy RACH configuration parameters may apply. For example, Msg1-FrequencyStart may apply in an SBFD symbol configured as downlink by tdd-UL-DL-ConfigurationCommon. In other words, the RO offset and different interpretation may not apply to an RO in an SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon. In effect, an SBFD-capable UE may operate as a legacy UE to use an RO in an SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon. For example, an RO in an SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon falls in the downlink subband and may be considered invalid and may not be used by the SBFD-capable UE if (e.g., if) the SBFD-capable UE operates as an SBFD-capable UE. In some embodiments, if (e.g., if) the RO falls in the UL subband, the RO may be valid and may be used by the SBFD-capable UE.

[0102]

[0125] (2) The validation rule for SBFD-capable UEs can disable ROs in SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon, regardless of whether they fall within the UL subband. For example, ROs in SBFD symbols configured as "F (Flexible)" are considered invalid regardless of whether they fall within the UL subband.

[0103]

[0126] Therefore, an SBFD-enabled UE may apply one or more methods and / or any combination of one or more methods described above to determine valid ROs and / or any other procedures, and then construct an RO group based on the valid ROs.

[0104]

[0127] 9 illustrates an example method for excluding ROs in a symbol type different from the symbol type of a first RO in an RO group, according to some embodiments of the present disclosure. FIG. 10 illustrates an example method for excluding ROs in a first type of symbol that has a smaller number than ROs in a second type of symbol, according to some embodiments of the present disclosure.

[0105]

[0128] In one or more embodiments, RO groups may be constructed in the same way as in legacy (e.g., according to legacy procedures). For example, RO groups may be constructed without distinguishing between ROs in SBFD symbols and non-SBFD symbols. In some embodiments, only RO groups including ROs in the same symbol (e.g., in either SBFD or non-SBFD symbols) may be used for multiple PRACH transmissions. In this case, some ROs in the RO group are excluded even if they are valid for a single PRACH transmission. In some embodiments, a predefined / configured rule (e.g., excluding some ROs in an RO group including at least one RO in an SBFD symbol and at least one RO in a non-SBFD symbol) may be used to determine which parts of the RO group are used and which parts of the RO group are excluded (e.g., excluding ROs in SBFD symbols or excluding ROs in non-SBFD symbols). For example, some ROs in an RO group including the first RO in the RO group (e.g., some ROs in the same type of symbol) are used, and the remaining ROs in the RO group are excluded. That is, if (e.g., if) an RO in a non-SBFD symbol in an RO group is used, then an RO in an SBFD symbol in the RO group is excluded. Similarly, if (e.g., if) an RO in an SBFD symbol in an RO group is used, then an RO in a non-SBFD symbol in the RO group will be excluded.

[0106]

[0129] An additional exclusion rule to the above predefined / configured rules is to utilize a portion of an RO group that has more ROs in the same symbol type, e.g., SBFD symbols or non-SBFD symbols. For example, if there are three ROs in SBFD symbols and one RO in a non-SBFD symbol in an RO group, the ROs in the non-SBFD symbols in the RO group will be excluded. Alternatively, which ROs in an RO group should be excluded may depend on the symbol type, e.g., if an RO group includes ROs in SBFD symbols and non-SBFD symbols, the ROs in the non-SBFD symbols will be excluded. In some embodiments, the gNB may configure which portion of ROs should be excluded via higher layer signaling.

[0107]

[0130] It would be beneficial for a gNB to be able to indicate to a UE whether to consider as valid (e.g., utilize) an RO group containing at least one RO in an SBFD symbol and at least one non-SBFD symbol, or an RO group containing at least one RO in an SBFD symbol configured as downlink and / or flexible by the tdd-UL-DL-ConfigurationCommon. For example, some gNBs may use the same antenna configuration in SBFD symbols and non-SBFD symbols and do not anticipate reception degradation. Furthermore, such a gNB may be able to address the additional complexity of handling inconsistent RO groups between legacy and SBFD-capable UEs. To this end, the gNB may provide an indication to the UE (e.g., legacy UE and / or SBFD-capable UE) via higher layer signaling, such as the RRC parameter RO_group_valid_SBFD_nonSBFD. Such an RRC parameter may be provided via RMSI, OSI, and / or dedicated higher layer signaling. In the absence of such an indication, a default behavior may be defined, such that an RO group is considered disabled if (or if) it contains at least one RO in an SBFD symbol and at least one RO in a non-SBFD symbol. Furthermore, the decision may be based on a threshold that may be predefined / configured, e.g., defined in a specification, and / or provided via higher layer signaling, e.g., RMSI, OSI, and / or UE-specific RRC signaling. The threshold may be based on the L1-RSRP of the selected SSB / CSI-RS for PRACH transmission. For example, if (e.g., if) an SBFD-capable UE is in poor coverage and the measured L1-RSRP is below the provided / determined threshold, the SBFD-capable UE may enable / disable an RO group spanning SBFD and non-SBFD symbols.

[0108]

[0131] Referring to Figure 9, an example of an RO group including four valid ROs for multiple PRACH transmissions is shown. In Figure 9, the RO group including valid ROs in SBFD symbols and non-SBFD symbols is modified by excluding ROs in symbol types different from the symbol type of the first RO in the RO group. For example, if (e.g., if) the first RO in the RO group is in an SBFD symbol, ROs in non-SBFD symbols are excluded. Thus, for RO groups #y+2 and #y+5, only the first RO is used.

[0109] 10, the usable portion of an RO group spanning SBFD symbols and non-SBFD symbols is determined based on which portion has more ROs. For example, the first RO in RO groups #y+2 and #y+5 is in the SBFD symbol, but the number of ROs in the SBFD symbol is less than the number of ROs in the non-SBFD symbol. Therefore, the RO in the SBFD symbol (e.g., the first RO) is excluded, and the RO in the non-SBFD symbol is used.

[0110]

[0132] FIG. 11 illustrates an example method for excluding an RO in an SBFD symbol configured as flexible within an RO group that includes an RO in a downlink and an SBFD symbol configured as flexible, in accordance with some embodiments of the present disclosure.

[0111]

[0133] If (for example, if) an RO is in an SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon, the RO group including the RO in the downlink and SBFD symbols configured as flexible may also be divided into portions. For example, one portion of the RO in the SBFD symbol is configured as downlink by tdd-UL-DL-ConfigurationCommon, and the other portion of the RO in the SBFD symbol is configured as flexible by tdd-UL-DL-ConfigurationCommon. The RO in the SBFD symbol configured as flexible is visible to legacy UEs. Therefore, a gNB may need to change its antenna configuration to ensure that the performance of legacy UEs is not adversely affected when switching from an RO in an SBFD symbol configured as downlink by tdd-UL-DL-ConfigurationCommon to an RO in an SBFD symbol configured as flexible. In this case, an SBFD-capable UE may exclude one of the portions using any of the exclusion rules described above.

[0112]

[0134] 11, an example of four PRACH repetitions with some ROs falling on SBFD symbols configured as flexible is shown. In this case, RO groups #y+1 and #y+4 include ROs in the downlink and SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon. In this case, an SBFD-capable UE may exclude ROs in SBFD symbols configured as flexible within these RO groups.

[0113]

[0135] It is beneficial to avoid utilizing an RO group that includes at least one RO in an SBFD symbol configured as downlink and at least one RO in an SBFD symbol configured as flexible. In response to such an RO group, the antenna configuration of the gNB may need to be adjusted across different PRACH repetitions within the RO group. Moreover, RO groups established by legacy UEs and SBFD-capable UEs may not be aligned.

[0114]

[0136] Alternatively, an SBFD-capable UE may consider an RO in an SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon as if it were an RO in an SBFD symbol configured as downlink by tdd-UL-DL-ConfigurationCommon. In other words, an SBFD-capable UE does not distinguish between ROs in SBFD symbols configured as downlink or flexible by tdd-UL-DL-ConfigurationCommon. In this case, the exclusion rules may be applied to an RO group that includes ROs in non-SBFD symbols and SBFD symbols (regardless of whether they are configured as downlink or flexible), similar to the exclusion rules described in Figures 9 and 10.

[0115]

[0137] In one or more embodiments, the above exclusion rules for ROs in an RO group apply if (e.g., when) ROs configured for legacy UEs are restricted within the UL subband of the SBFD-enabled UE, and may be extended when the RO is outside the UL subband. For example, the SBFD-enabled UE may apply an additional offset to the position of the RO in the frequency domain to move the RO in the UL subband, or may apply a different interpretation of the legacy RACH configuration parameters. Thus, one or more methods for handling RO replicas in SBFD symbols configured as flexible by the tdd-UL-DL-ConfigurationCommon may be provided, as follows:

[0116]

[0138] (1) An additional offset to the location of the RO in the frequency domain or a different interpretation of the legacy RACH configuration parameters may apply. For example, Msg1-FrequencyStart may only apply in SBFD symbols configured as downlink by tdd-UL-DL-ConfigurationCommon. In other words, the RO offset and different interpretation may not apply to ROs in SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon. In effect, an SBFD-capable UE can operate as a legacy UE and use an RO in an SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon. For example, an RO in an SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon corresponds to the downlink subband and may be considered invalid and may not be used by the SBFD-capable UE if (e.g., if) the SBFD-capable UE operates as an SBFD-capable UE. On the other hand, if (e.g., if) the RO corresponds to the UL subband, the RO is valid and may be used by the SBFD-capable UE.

[0117]

[0139] (2) The validation rules for SBFD-capable UEs may consider ROs in SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon, regardless of whether they fall within the UL subband. For example, ROs in SBFD symbols configured as "F (Flexible)" are considered invalid, regardless of whether they fall within the UL subband.

[0118]

[0140] Therefore, an SBFD-enabled UE may apply one or more methods and / or any combination of one or more methods described above to determine valid ROs and / or any other procedures, and then construct an RO group based on the valid ROs.

[0119]

[0141] It would be beneficial for a gNB to be able to instruct a UE whether to apply the partial exclusion rule to an RO group that includes ROs in SBFD and non-SBFD symbols, or that includes ROs in SBFD symbols configured as downlink and flexible by the tdd-UL-DL-ConfigurationCommon. For example, some gNBs may use the same antenna configuration for SBFD and non-SBFD symbols and do not anticipate reception degradation. Furthermore, such a gNB may be able to address the additional complexity of handling inconsistent RO groups between legacy and SBFD-capable UEs. To this end, the gNB may provide an indication to the UE (e.g., legacy UE and / or SBFD-capable UE) via higher layer signaling (e.g., instructing the UE whether to apply the partial exclusion rule), such as the RRC parameter RO_group_partialdropping_SBFD_nonSBFD. Such an RRC parameter may be provided via RMSI, OSI, and / or dedicated higher layer signaling. In the absence of such an indication, a default behavior may be defined, such as partial RO group exclusion being applied if (e.g., if) an RO group includes ROs in SBFD and non-SBFD symbols. Furthermore, the decision may be based on a threshold that may be predefined / configured, e.g., defined in a specification, and / or provided via higher layer signaling, e.g., RMSI, OSI, and / or UE-specific RRC signaling. The threshold may be based on the L1-RSRP of the selected SSB / CSI-RS for PRACH transmission. For example, if (e.g., if) an SBFD-capable UE is in poor coverage and the measured L1-RSRP is below a predefined / configured threshold, the SBFD-capable UE may or may not perform partial exclusion of some ROs in the RO group.

[0120]

[0142] To provide the gNB with more flexibility, the gNB may instruct the UE which portions of an RO group are to be excluded. In some embodiments, the gNB may instruct the UE via higher layer signaling that a portion of ROs having the same type as the first RO in the RO group should be excluded, or that other portions should be excluded. For example, if (e.g., the first RO in the RO group is an RO in an SBFD symbol), the gNB may instruct the UE to exclude a portion of the ROs in the SBFD symbols in the RO group, or to exclude a portion of the ROs in non-SBFD symbols. In some embodiments, the gNB may instruct the UE via higher layer signaling that a portion of an RO group containing more ROs having the same type should be excluded, or that other portions should be excluded. For example, if (e.g., if) there are three ROs in the SBFD symbols and one RO in the non-SBFD symbols in an RO group, the gNB may instruct the UE to exclude the ROs in the SBFD symbols (e.g., the part of the RO group that contains more ROs with the same type) or to exclude the ROs in the non-SBFD symbols (e.g., the other part of the RO group).

[0121]

[0143] Additional exclusion rules may be applied to utilize portions of the RO corresponding to either SBFD symbols or non-SBFD symbols, and which portion to utilize may be an indication from the gNB or may be included in the gNB indication via higher layer signaling provided in RMSI, OSI, and / or UE-dedicated signaling. Because the RO in non-SBFD symbols may be shared with legacy UEs, utilizing only the RO in SBFD symbols may make blind detection easier for the gNB compared to utilizing the RO in non-SBFD symbols.

[0122]

[0144] In one or more embodiments, disabling an RO group that spans SBFD and non-SBFD symbols and / or excluding some ROs in an RO group may be applied if (e.g., when) Frequency Division Multiplexed (FDMed) ROs are not formed. Alternatively, an RO group may be formed if (e.g., when) valid ROs in SBFD symbols and valid ROs in non-SBFD symbols with the same frequency resource index occupy different RBs, and the above-described embodiments for disabling an RO group or partially excluding some ROs in an RO group may be applied if (e.g., when) an RO group includes ROs that span both SBFD and non-SBFD symbols.

[0123]

[0145] If (e.g., if) an RO is configured in an SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon, the SBFD-capable UE may apply an additional offset to the position of the RO in the frequency domain or apply a different interpretation of the legacy RACH configuration parameters to move the RO in the UL subband. In this case, the legacy RO may fall in the DL subband. To avoid any adverse effects on legacy UEs, the gNB may receive PRACH transmissions, e.g., via an RO in the DL subband and in the SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon. In other words, the gNB may switch from SBFD operation to legacy TDD operation and perform only UL reception in this symbol (e.g., an RO in the DL subband and in the SBFD symbol configured as flexible). In this case, one or more methods may be provided for the SBFD-capable UE, as follows:

[0124]

[0146] (1) An SBFD-capable UE only needs to transmit UL transmissions in the UL subband, regardless of the collision handling rules that apply to ROs in other SBFD symbols but not in DL subbands. An SBFD-capable UE can operate as if UL transmissions were restricted only within the UL subband. For example, the UL resource block group (RBG) that intersects the UL subband may be a fractional RBG, with fewer RBs than the remaining RBs in the UL RBG.

[0125]

[0147] (2) An SBFD-capable UE may transmit UL transmissions over the entire UL Bandwidth Part (BWP), including BWPs outside the UL subband. In other words, an SBFD-capable UE may switch to legacy TDD operation.

[0126]

[0148] In response to a gNB switching from SBFD operation to legacy TDD operation, one or more of the methods and / or any combination of one or more of the methods described above may be applied.

[0127]

[0149] Under a shared configuration between legacy UEs and SBFD-enabled UEs, additional restrictions may be applied to SBFD-enabled UEs to avoid any impact on legacy UEs. For example, an SBFD-enabled UE may not be allowed to use ROs in non-SBFD symbols, for example, by regarding ROs in non-SBFD symbols as invalid ROs. In this case, an RO group consists only of valid ROs in SBFD symbols.

[0128]

[0150] 12A and 12B illustrate example shared RO configurations for legacy and SBFD-enabled UEs, respectively, in accordance with some embodiments of the present disclosure.

[0129]

[0151] 12A and 12B show an exemplary RO configuration shared between a legacy UE and an SBFD-capable UE. In the exemplary RO configuration, RO groups are constructed based on valid ROs from their own perspectives (e.g., SBFD-capable UEs and legacy UEs each construct their own RO groups). The number of RACH transmissions is set to 4. If (e.g., if) SBFD-capable UEs are not permitted to use ROs in non-SBFD symbols, those ROs (e.g., ROs in non-SBFD symbols) are considered invalid for either a single PRACH transmission or multiple PRACH transmissions. The SBFD-capable UEs then construct RO groups according to legacy rules based on valid ROs (e.g., ROs in SBFD symbols).

[0130]

[0152] In one or more embodiments, an SBFD-capable UE can choose whether to be treated as a legacy UE or as an SBFD-capable UE, regardless of whether the SBFD-capable UE is permitted to utilize RO in non-SBFD symbols. With reference to FIG. 3 , an SBFD-capable UE may choose to establish an RO group in the same way as a legacy UE, or an SBFD-capable UE may establish an RO group in the same way as other SBFD-capable UEs. Similarly, to establish an RO group, an SBFD-capable UE may choose to apply the improvements disclosed in FIG. 3 or to apply the same procedure as a legacy UE. In this case, one or more methods and a combination of one or more methods may be applied to an SBFD-capable UE as follows:

[0131]

[0153] (1) An SBFD-capable UE may always operate as an SBFD-capable UE and may not operate as a legacy UE. For example, an SBFD-capable UE may apply all restrictions imposed on SBFD-capable UEs. For example, if an SBFD-capable UE constructs two sets of RO groups (e.g., a set of RO groups including only ROs in SBFD symbols and another set of RO groups including only ROs in non-SBFD symbols) as in the rule disclosed in FIG. 4, the SBFD-capable UE must apply it (e.g., operate as an SBFD-capable UE) and cannot construct RO groups similar to a legacy UE.

[0132]

[0154] (2) An SBFD-capable UE can choose whether it operates as another SBFD-capable UE or as a legacy UE. If (e.g., if) a validation rule at the RO group level, such as that disclosed in FIG. 7, applies, an SBFD-capable UE can choose whether to apply this rule as an SBFD-capable UE or to build an RO group in the same way as a legacy UE. Such a decision (e.g., to operate as an SBFD-capable UE or a legacy UE) may be determined based on one or a combination of the following conditions:

[0133]

[0155] 1. The decision may be based on internal criteria of the UE implementation, such as which behavior results in faster completion of multiple PRACH transmissions. In some embodiments, the gNB may enable or disable the decision via higher layer signaling, e.g., RMSI, OSI, and / or UE-specific RRC signaling. A default behavior may be defined for the lack of a corresponding configuration, such as operating as an SBFD-capable UE.

[0134]

[0156] 2. The threshold may be based on a predefined / configured threshold, e.g., a threshold defined in a specification and / or a threshold provided via higher layer signaling, e.g., RMSI, OSI, and / or UE-specific RRC signaling. The threshold may be set based on the L1-RSRP of the selected SSB and / or CSI-RS for PRACH transmission. For example, if (e.g., if) an SBFD-capable UE is in poor coverage and the measured L1-RSRP is below a predefined / configured threshold, the SBFD-capable UE may operate as an SBFD-capable UE and apply the corresponding restrictions and behaviors as disclosed herein.

[0135]

[0157] In one or more embodiments, if (e.g., if) an SBFD-capable UE constructs two sets of RO groups, e.g., a set of RO groups containing valid ROs in SBFD symbols (denoted as set 0) and another set of RO groups containing valid ROs in non-SBFD symbols (denoted as set 1), it may be beneficial for the gNB to indicate which set of RO groups should be used. To this end, one or more methods or a combination of one or more methods may be applied to determine how an SBFD-capable UE, e.g., a legacy UE or an SBFD-capable UE, behaves. The one or more methods may be provided as follows:

[0136]

[0158] (1) An SBFD-capable UE can always use an RO group in set 0, e.g., an RO group including an RO in an SBFD symbol, and cannot use an RO group in set 1, e.g., an RO group including an RO in a non-SBFD symbol.

[0137]

[0159] (2) An SBFD-capable UE can select whether to use an RO group in Set 0 or an RO group in Set 1. Such a decision may be determined based on one or a combination of the following conditions:

[0138]

[0160] 1. The decision may be based on internal criteria of the UE implementation, such as which behavior results in faster completion of multiple PRACH transmissions. In some embodiments, the gNB may enable / disable the decision via higher layer signaling, e.g., RMSI, OSI, and / or UE-dedicated RRC signaling. In the absence of a corresponding configuration, a default behavior may be defined, such as using the RO group in set 0.

[0139]

[0161] 2. It may be based on a predefined / configured threshold, e.g., a threshold defined in the specification and / or a threshold provided via higher layer signaling, e.g., RMSI, OSI, and / or UE-dedicated RRC signaling. The threshold may be set based on the L1-RSRP of the selected SSB and / or CSI-RS for PRACH transmission. For example, if (e.g., if) an SBFD-capable UE is in poor coverage and the measured L1-RSRP is below a predefined / configured threshold, the SBFD-capable UE may use an RO group in Set 0.

[0140]

[0162] For PRACH retransmissions, it may be beneficial to have consistency between the initial PRACH transmission and subsequent retransmissions. For example, if an SBFD-capable UE chooses to operate as a legacy UE for the initial PRACH transmission, the SBFD-capable UE is expected to operate as a legacy UE for subsequent retransmissions. Similarly, if multiple sets of RO groups are implemented (e.g., if implemented), an SBFD-capable UE is expected to select the same set of RO groups for both the initial transmission and subsequent retransmissions. Using the same set of RO groups and / or operating in the same manner for both the initial transmission and subsequent retransmissions avoids applying different power control parameters, e.g., different target power and / or power ramping steps, for PRACH transmissions in SBFD and non-SBFD symbols, and thus may simplify the power control procedure.

[0141]

[0163] In some embodiments, providing flexibility between the initial PRACH transmission and subsequent retransmissions may also be beneficial to reduce latency. For example, if an SBFD-capable UE chooses to operate as a legacy UE for the initial PRACH transmission, the SBFD-capable UE may choose to operate as an SBFD-capable UE for subsequent retransmissions. Similarly, if (e.g., if) multiple sets of RO groups are introduced, the SBFD-capable UE may choose a particular set of RO groups for the initial PRACH transmission and a different set of RO groups for subsequent retransmissions. In this case, the same power control parameters may be applied to PRACH transmissions in both SBFD and non-SBFD symbols. Thus, if (e.g., if) a single set of power control parameters is provided for PRACH transmissions in SBFD and non-SBFD symbols, the UE does not need to ensure consistency between the initial PRACH transmission and subsequent retransmissions. In some embodiments, the gNB may indicate to the UE whether consistency should be ensured between the initial PRACH transmission and subsequent retransmissions via higher layer signaling, e.g., via new RRC parameters that may be carried in RSMI, OSI, and / or UE-specific RRC configurations.

[0142]

[0164] In one or more embodiments, the RACH configuration, e.g., even the configuration of the RO and preamble, may be shared between legacy and SBFD-enabled UEs, and some of the shared RACH parameters may be modified.

[0143]

[0165] The number of multiple PRACH transmissions for an SBFD-capable UE may differ from the corresponding number for a legacy UE, msg1-RepetitionNum-r18. To extend coverage, an SBFD-capable UE may require more repetitions compared to a legacy UE. The gNB may provide an SBFD-capable UE with an additional value, e.g., msg1-RepetitionNum-SBFD, to be applied if (e.g., when) the SBFD-capable UE operates as an SBFD-capable UE rather than as a legacy UE.

[0144]

[0166] An SBFD-capable UE may apply different thresholds for determining the number of repetitions compared to a legacy UE that applies rsrp-ThresholdMsg1-RepetitionNum2, rsrp-ThresholdMsg1-RepetitionNum4, and / or rsrp-ThresholdMsg1-RepetitionNum8. The gNB may provide the SBFD-capable UE with additional values, e.g., rsrp-ThresholdMsg1-RepetitionNum2-SBFD, rsrp-ThresholdMsg1-RepetitionNum4-SBFD, and / or rsrp-ThresholdMsg1-RepetitionNum8-SBFD, to be applied if (e.g., when) the SBFD-capable UE operates as an SBFD-capable UE rather than as a legacy UE.

[0145]

[0167] FIG. 13 is a diagram illustrating an example preamble partitioning between SBFD-enabled UEs and legacy UEs, in accordance with some embodiments of the present disclosure.

[0146]

[0168] 13 shows an example in which separate preambles are configured for SBFD-capable UEs and legacy UEs, while only sharing the RO configuration between the SBFD-capable UEs and legacy UEs. This can be beneficial in SBFD operation, as the gNB can distinguish between SBFD-capable UEs and legacy UEs.

[0147]

[0169] Therefore, dedicating some preambles for SBFD-capable UEs in ROs shared between legacy and SBFD-capable UEs may be applicable to a single PRACH transmission. For example, ROs in non-SBFD symbols may be used by both SBFD-capable UEs and legacy UEs, and therefore allocating some preambles for SBFD-capable UEs may be beneficial in these occasions (e.g., a single PRACH transmission). In some embodiments, dedicating preambles for ROs in SBFD symbols may not be required for ROs in SBFD symbols. Therefore, SBFD-capable UEs may apply preamble partitioning only to ROs shared with legacy UEs, e.g., ROs in non-SBFD symbols and / or ROs in SBFD symbols configured in flexible symbols based on tdd-UL-DL-ConfigurationCommon. On the other hand, preamble partitioning is not applied to ROs not shared with legacy UEs, e.g., ROs in SBFD symbols configured in downlink symbols based on tdd-UL-DL-ConfigurationCommon.

[0148]

[0170] Assuming that SBFD-capable UEs may use ROs in non-SBFD symbols to construct RO groups, applying the legacy rules may result in excluding ROs in non-SBFD symbols, because for legacy UEs, during multiple PRACH transmissions, an RO group containing valid ROs associated with the same SSB index and each SSB index associated with the same preamble is present in all valid PRACH occasions within the RO group.

[0149]

[0171] To construct an RO group, which may include ROs in SBFD symbols and ROs in non-SBFD symbols, an SBFD-capable UE may assume that the same preamble partitioning applies to ROs in SBFD symbols as to ROs in non-SBFD symbols, whereas in the case of a single PRACH transmission, preamble partitioning does not apply to ROs in SBFD symbols.

[0150]

[0172] FIG. 13 shows an example of PRACH preamble partitioning based on PRACH repetition, RO groups containing only ROs in SBFD or non-SBFD symbols, and / or single PRACH transmission with ROs in SBFD or non-SBFD symbols.

[0151] In a first scenario 701, if (eg, if) an SBFD-capable UE transmits a single PRACH with RO in an SBFD symbol, the preamble is chosen from among any preambles arranged for the selected SSB.

[0152] In a second scenario 702, if (e.g., if) an SBFD-capable UE transmits a single PRACH with RO in a non-SBFD symbol, preamble partitioning is applied between the legacy UE and the SBFD-capable UE, and a preamble is selected from the portion for the SBFD-capable UE.

[0153] In a third scenario 703, if (e.g., if) an SBFD-capable UE transmits multiple PRACH transmissions within an RO group that falls entirely within an SBFD symbol (e.g., an RO group that includes an RO in an SBFD symbol), a preamble is selected from among those preambles allocated for the four PRACH repetitions without making any additional distinction between SBFD-capable UEs and legacy UEs.

[0154] In a fourth scenario 704, if (e.g., if) an SBFD-capable UE transmits multiple PRACH transmissions within an RO group that falls entirely within a non-SBFD symbol or spans both SBFD and non-SBFD symbols, a preamble is selected from among the preambles allocated for the four PRACH repetitions for the SBFD-capable UE.

[0155]

[0173] Therefore, the legacy rules for RO groups can be modified to reflect the above procedure, e.g., an RO group including each SSB index associated with the same preamble index in all valid PRACH occasions within the RO group and valid ROs associated with the same SSB index. For example, the first RO in RO group #y+2 in Figure 13 can be considered to have all preambles for the 4-step RACH, as in the first scenario 701. However, preamble partitioning may be applied to the remaining ROs in RO group #y+2 to form the RO group.

[0156]

[0174] Similar to the case where the RO and preamble are shared, an SBFD-capable UE may choose to operate as a legacy UE or an SBFD-capable UE. The above-described methods for determining whether an SBFD-capable UE operates as a legacy UE may apply.

[0157]

[0175] Furthermore, similar to the case where ROs and preambles are shared, some of the shared parameters, such as the RSRP threshold for determining the number of repetitions, may be modified, or SBFD-capable UEs may be given a different number of repetitions than the number configured for legacy UEs.

[0158]

[0176] It may be beneficial for a gNB to be able to indicate to a UE whether preamble partitioning applies to an RO group containing ROs in SBFD and non-SBFD symbols. For example, some gNBs may use the same antenna configuration for SBFD and non-SBFD symbols, and such gNBs do not expect reception degradation. Furthermore, such gNBs may be configured to handle the additional complexity of handling inconsistent RO groups between legacy and SBFD-capable UEs. To this end, the gNB may specify how preambles should be partitioned, e.g., the absence of a start preamble and preamble number may indicate that preamble partitioning does not apply. Alternatively, partitioning information may be provided, but the decision to apply the partitioning information may be based on predefined / configured thresholds, e.g., thresholds defined in the specification and / or thresholds provided via higher layer signaling, e.g., RMSI, OSI, and / or UE-specific RRC signaling. The threshold may be based on the L1-RSRP of the selected SSB / CSI-RS for PRACH transmission. For example, if (e.g., if) an SBFD-enabled UE is in poor coverage and the measured L1-RSRP is below a predefined / configured threshold, the SBFD-enabled UE may or may not apply the preamble partitioning configuration.

[0159]

[0177] In one or more embodiments, the above method for applying preamble partitioning between SBFD-capable UEs and legacy UEs in a shared RO in a non-SBFD symbol may also be applied to a scenario in which an RO is shared between a legacy UE and an SBFD-capable UE in an SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon.

[0160]

[0178] FIG. 14 illustrates an example method for constructing RO groups with frequency offsets between ROs in SBFD symbols and ROs in non-SBFD symbols in accordance with some embodiments of the present disclosure.

[0161]

[0179] Providing ROs for SBFD-capable UEs that are separate from ROs for legacy UEs may mitigate problems caused by misaligned boundaries of RO groups between legacy and SBFD-capable UEs, in which case an RO group for an SBFD-capable UE may span both SBFD and non-SBFD symbols. However, providing separate ROs for SBFD-capable UEs and legacy UEs may create problems if (e.g., if) a gNB changes its antenna configuration between SBFD and non-SBFD symbols. Therefore, the aforementioned method (e.g., constructing two sets of RO groups) can be applied to ensure that all available ROs in an RO group fall entirely within an SBFD symbol or a non-SBFD symbol.

[0162]

[0180] In legacy procedures / approaches, an RO group may include valid ROs that utilize the same frequency resources. In response to scenarios where an RO configuration is shared between SBFD-capable UEs and legacy UEs, it may be desirable to have a frequency offset between ROs located in SBFD and non-SBFD symbols. It may be beneficial to ensure that some ROs fall within the UL subband and are at the edges of the UL BWP and UL subband in non-SBFD and SBFD symbols.

[0163]

[0181] In one or more embodiments, the method of constructing two sets of RO groups (e.g., a set of RO groups containing ROs in SBFD symbols and another set of RO groups containing ROs in non-SBFD symbols) may be applied to address scenarios where RO configurations are shared between SBFD-capable UEs and legacy UEs.

[0164]

[0182] Figure 14 shows an example of an RO configuration shared between a legacy UE and an SBFD-capable UE, in which a frequency offset is applied between ROs in SBFD symbols and ROs in non-SBFD symbols. The frequency offset value may be provided by higher layer signaling. In this case, an SBFD-capable UE may construct two sets of RO groups. For example, RO group set 0 may include RO groups constructed by ROs in SBFD symbols, and RO group set 1 may include RO groups constructed by ROs in non-SBFD symbols. For example, RO group #y+2 in set 0 includes ROs in SBFD symbols but not in non-SBFD symbols. Similarly, RO group #y+3 in set 1 includes ROs in non-SBFD symbols but not in SBFD symbols.

[0165]

[0183] FIG. 15 illustrates an example method for constructing two sets of RO groups in response to an FDMed RO, according to some embodiments of the present disclosure.

[0166]

[0184] If (e.g., if) there is an RO in the SBFD symbol configured as flexible by tdd-UL-DL-ConfigurationCommon, a replica of the RO in the SBFD symbol is created by applying a shift and / or a different interpretation. Thus, the method disclosed in Figure 6 may be applied to determine how the RO group is configured and its corresponding set (e.g., Set 0 or Set 1).

[0167]

[0185] If (e.g., if) multiple FDMed ROs exist, RO groups may be constructed utilizing legacy rules that apply correspondingly to Set 0 and Set 1. For example, the first RO in the first RO group in Set 0 is determined as the first valid RO in Set 0 of a symbol, e.g., an SBFD symbol. Further, the first RO in subsequent RO groups in Set 0 is determined in ascending order across symbols, e.g., Set 0 of an SBFD symbol, first in the frequency domain and then in the time domain. The same method (e.g., determining RO groups first in the frequency domain and then in the time domain) applies to Set 1 of RO groups in non-SBFD symbols.

[0168]

[0186] Therefore, combining the methods disclosed in FIG. 4 and FIG. 15, the RO groups in each set may be determined as follows:

[0169]

[0187] (1) The first valid RO in the first RO group of Set 0 may be the first valid PRACH occasion that corresponds to the SBFD symbol.

[0170]

[0188] (2) The first valid RO in the first RO group of Set 1 may be the first valid PRACH occasion that falls on a non-SBFD symbol.

[0171]

[0189] (3) The first valid PRACH occasion of a subsequent RO group in Set 0 may be determined based on the order of valid PRACH occasions in the SBFD symbol. The order may be in ascending order of frequency resource index for PRACH occasions frequency multiplexed in the SBFD symbol, and then the order may be in ascending order of time resource index for PRACH occasions time multiplexed in the SBFD symbol.

[0172]

[0190] (4) The first valid PRACH occasion of a subsequent RO group in Set 1 may be determined according to the order of valid PRACH occasions in non-SBFD symbols. The order may be in ascending order of frequency resource index for PRACH occasions frequency multiplexed in non-SBFD symbols, and then the order may be in ascending order of time resource index for PRACH occasions time multiplexed in non-SBFD symbols.

[0173]

[0191] (5) For each frequency resource index for FDMed ROs, the first valid PRACH occasion of the first RO group in set 0 may be the first valid PRACH occasion in the SBFD symbol.

[0174]

[0192] (6) The first valid PRACH occasion of a subsequent RO group in Set 0 may be the consecutive valid PRACH occasion in SBFD symbols that is TimeOffsetBetweenStartingRO after the first valid PRACH occasion of the preceding set in the time domain, where each PRACH occasion is associated with the same SS / PBCH block index and each SS / PBCH block index is associated with the same preamble. Alternatively, if (e.g., if) TimeOffsetBetweenStartingRO is not provided, the first valid PRACH occasion of a subsequent RO group in Set 0 may be after the PRACH occasion of the preceding RO group.

[0175]

[0193] (7) For each frequency resource index for FDMed RO, the first valid PRACH occasion of the first RO group in Set 1 may be the first valid PRACH occasion in a non-SBFD symbol.

[0176]

[0194] (8) The first valid PRACH occasion of a subsequent RO group in Set 1 may be a consecutive valid PRACH occasion in non-SBFD symbols that is TimeOffsetBetweenStartingRO after the first valid PRACH occasion of the preceding set in the time domain, where each PRACH occasion is associated with the same SSB index and each SSB index is associated with the same preamble. Alternatively, if (e.g., if) TimeOffsetBetweenStartingRO is not provided, the first valid PRACH occasion of a subsequent RO group in Set 1 may be after the PRACH occasion of the preceding RO group.

[0177]

[0195] In one or more embodiments, an SBFD-capable UE may use legacy procedures to construct RO groups per symbol type (e.g., SBFD symbol or non-SBFD symbol). For example, legacy procedures may be applied to construct / determine RO groups based on valid ROs in SBFD symbols, and then the same procedures may be applied to determine RO groups based on valid ROs in non-SBFD symbols.

[0178]

[0196] FIG. 16 is a diagram illustrating an example RO group having a suitable number of ROs, according to some embodiments of the present disclosure.

[0179]

[0197] The set of RO groups may be determined to include an appropriate number of ROs in each RO group of the determined RO group set. For example, in general, an RO group may have four ROs, and an RO group in the determined RO group set may have only two ROs. Such a determination may be beneficial if (e.g., if) the number of valid FDMed ROs in an SBFD symbol is different from the number of valid FDMed ROs in a non-SBFD symbol and / or if (e.g., if) the FDMed ROs in an SBFD symbol and the FDMed ROs in a non-SBFD symbol occupy different RBs.

[0180]

[0198] The RO space in the time domain may be divided into "portions" based on the nominal configured number of repetitions and whether TimeOffsetBetweenStartingRO is provided / configured. If a portion contains both SBFD and non-SBFD symbols (e.g., an RO group containing an RO in an SBFD symbol and an RO in a non-SBFD symbol), the portion is divided in response to a transition from an SBFD symbol to a non-SBFD symbol, or vice versa. In some embodiments, the legacy approach for constructing RO groups may be applied to each portion in the RO space.

[0181]

[0199] FIG. 16 shows an example of four Msg1 iterations. Portions are determined for each of four valid ROs in the time domain (e.g., by dividing the portion by each of the four valid ROs). All portions contain either SBFD symbols or non-SBFD symbols, except that the first portion 1201 and the second portion 1202 each contain both types of symbols (e.g., the first portion 1201 and the second portion 1202 contain ROs in SBFD symbols and ROs in non-SBFD symbols). In this case, the first portion 1201 and the second portion 1202 are further divided into sub-portions in response to transitions from SBFD symbols to non-SBFD symbols, or vice versa. For example, each sub-portion may contain only ROs in the same type of symbol (e.g., SBFD symbols or non-SBFD symbols). In some embodiments, legacy procedures / techniques for constructing RO groups may be applied to each portion. As a result, all RO groups have four valid ROs, except for the RO groups in the first portion 1201 and the second portion 1202, which have two valid ROs. It may be beneficial to divide the portions until each portion with ROs in the same type of symbol can guarantee that all ROs in the RO group occupy the same RB. Therefore, RO groups in the first portion 1201 and the second portion 1202 with only two Msg1 repetitions are allowed.

[0182]

[0200] To construct RO groups in a portion that includes both SBFD and non-SBFD symbols, the legacy rule that all ROs in an RO group occupy the same RB may be relaxed (e.g., repealed). Because the number of FDMed ROs in an SBFD symbol is expected to be fewer than the number of FDMed ROs in a non-SBFD symbol, it may be beneficial to determine how the ROs are grouped. For example, ROs may be numbered in ascending order in the frequency domain and specified, for example, by the frequency resource index of the frequency-multiplexed PRACH. Thus, in a portion that includes both SBFD and non-SBFD symbols, ROs with the same frequency resource index are grouped together even if they occupy different RBs. In some embodiments, other rules may be applied to determine which ROs are grouped together, for example, an RO in an SBFD symbol with the lowest frequency resource index is grouped with an RO in a non-SBFD symbol with a higher frequency resource index.

[0183]

[0201] FIG. 17 is a diagram illustrating an example RO group including valid ROs in different RBs, according to some embodiments of the present disclosure.

[0184]

[0202] Referring to FIG. 17, an example of four Msg1 repetitions may be applied. The RO space may be divided into portions, each with four valid ROs, in the time domain. For example, RO groups / portions may be determined / constructed using the four valid ROs. All portions contain either SBFD symbols or non-SBFD symbols, except for first portion 1301 and second portion 1302, which contain both types of symbols (e.g., SBFD symbols and non-SBFD symbols). In this case, first portion 1301 and second portion 1302 are further divided into sub-portions in response to transitions from SBFD symbols to non-SBFD symbols, or vice versa.

[0185]

[0203] In the first portion 1301 and the second portion 1302, the RO in the SBFD symbol with the lowest frequency resource index is grouped with the RO in the non-SBFD symbol with the lowest frequency resource index, and the RO in the SBFD symbol with the second lowest frequency resource index is grouped with the RO in the non-SBFD symbol with the second lowest frequency resource index. The RO in the non-SBFD symbol with the highest frequency resource index is not grouped with any RO in the SBFD symbol. Therefore, the constructed RO group may include two ROs instead of four ROs.

[0186]

[0204] FIG. 18 is a diagram illustrating an example RO group in set 1 with SBFD symbols configured as flexible, according to some embodiments of the present disclosure.

[0187]

[0205] In response to the presence of RO in SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon, a combination of the methods disclosed above may be applied as follows: Since RO in SBFD symbols configured as flexible symbols is visible to legacy UEs, the main objective of the following solution is to maintain similarity between both legacy and SBFD-capable UEs.

[0188]

[0206] The approach disclosed in Figure 18 may be to apply the frameworks disclosed in Figures 16 and 17 when constructing an RO group in Set 1. An RO group in Set 1 may be an RO group including ROs in non-SBFD symbols, but it may also include an RO group constructed by ROs in SBFD symbols configured as flexible by tdd-UL-DL-ConfigurationCommon. Also, constructing an RO group in Set 0, for example, an RO group including ROs in SBFD symbols configured as downlink by tdd-UL-DL-ConfigurationCommon, may be constructed based on the above approach since the number of FDMed ROs is the same.

[0189]

[0207] For example, the RO space in the time domain is divided into portions based on the nominal number of repetitions (e.g., minimum number of repetitions) and whether TimeOffsetBetweenStartingRO is set. If any portion contains both SBFD and non-SBFD symbols, an RO group may be constructed based on the frequency resource index in the portion that includes an RO in an SBFD symbol configured as flexible and an RO in a non-SBFD symbol. In response to the absence of an RO associated with the same frequency resource index in an SBFD symbol and the presence of an RO in a non-SBFD symbol in that portion, a smaller RO group, e.g., an RO group including two ROs, may be constructed.

[0190]

[0208] In one or more embodiments, the divided portions may be contiguous in the time domain, as shown in FIG. 18. The divided portions may not be contiguous in the time domain. For example, an RO group in set 0 may exist among RO groups in set 1. The UE may first determine ROs in SBFD symbols configured as flexible and ROs in non-SBFD symbols, excluding ROs in SBFD symbols configured as downlink. The UE may then construct RO groups based on the determined ROs, as shown in FIG. 18, where the determined ROs are not necessarily contiguous and / or in the same time domain. The UE may then construct RO groups for set 1 based on the above-described scheme. In some embodiments, the UE may apply the constructed RO groups based on the original position of each RO.

[0191]

[0209] In some embodiments, the approach for constructing an RO group in response to an FDMed RO being configured may also be applied to the case where an FDMed RO is not configured, in which case the ROs in SBFD symbols and the ROs in non-SBFD symbols occupy different RBs.

[0192]

[0210] According to the present disclosure, to enhance SBFD processing, one or more methods may include determining the RO by the following steps:

[0193]

[0211] (1) Constructing two sets for RO groups, where the first set includes RO groups including ROs in SBFD symbols and the second set includes RO groups including ROs in non-SBFD symbols.

[0194]

[0212] (2) Steps to exclude new validation rules at the RO group level.

[0195]

[0213] (3) In response to an RO group spanning an RO in an SBFD symbol and an RO in a non-SBFD symbol, introducing a new exclusion rule, for example, based on the position of the first RO in the RO group and / or based on the portion of the RO group that has more ROs.

[0196]

[0214] (4) Receiving an indication from the gNB via higher layer signaling indicating whether the RO group may span ROs in SBFD symbols and ROs in non-SBFD symbols.

[0197]

[0215] Furthermore, to determine how an SBFD-capable UE should behave, e.g., as an SBFD-capable UE or a legacy UE, one or more rules may be applied as follows:

[0198]

[0216] (1) An SBFD-capable UE may always operate as an SBFD-capable UE, which means that an SBFD-capable UE does not have to operate as a legacy UE.

[0199]

[0217] (2) An SBFD-capable UE may choose to operate as a legacy UE based on the UE implementation or based on a threshold predefined or configured by the gNB.

[0200]

[0218] To address the scenario of sharing RACH configuration between SBFD capable UE and legacy UE, the following parameters may be modified:

[0201]

[0219] (1) The number of repetitions may differ between legacy UEs and SBFD-enabled UEs.

[0202]

[0220] (2) Different thresholds may be applied to determine the number of iterations that are applicable.

[0203]

[0221] For ROs that are shared but have separate preambles between legacy UEs and SBFD-capable UEs, one or more of the following approaches may be applied:

[0204]

[0222] (1) A method of applying preamble partitioning only to ROs in non-SBFD symbols.

[0205]

[0223] A method for an SBFD-capable UE to apply preamble partitioning in response to transmitting multiple PRACHs in an RO group across SBFD and non-SBFD symbols.

[0206]

[0224] Furthermore, the legacy constraint / restriction that each SSB index is associated with the same preamble index in all valid PRACH occasions within an RO group may be removed, e.g., legacy RO groups containing valid ROs associated with the same SSB index, and each SSB index associated with the same preamble index in valid PRACH occasions within an RO group.

[0207]

[0225] Furthermore, the constraint / restriction that all ROs in an RO group occupy the same frequency resources is modified to apply to a set of RO groups, where each RO group is in the same symbol type, e.g., SBFD symbols or non-SBFD symbols.

[0208]

[0226] Furthermore, if (eg, if) the ROs in SBFD symbols and the ROs in non-SBFD symbols occupy different RBs, new rules / procedures for constructing RO groups apply.

[0209]

[0227] 19 is a flowchart illustrating a method for constructing an RO group according to some embodiments of the present disclosure. Although FIG. 19 illustrates various operations in a method for constructing an RO group, one or more embodiments according to the present disclosure are not limited thereto, and according to one or more embodiments, the method may include additional or fewer operations, and the order of operations may be varied, without departing from the spirit and scope of embodiments according to the present disclosure, unless otherwise stated or implied.

[0210]

[0228] Referring to FIG. 19, in operation 1905, the UE receives a configuration for SBFD operation and PRACH repetition.

[0211]

[0229] In operation 1910, the UE constructs an RO group based on the configuration. The RO group may include one or more ROs from the set of SBFD symbols and the set of non-SBFD symbols. In some embodiments, one or more ROs in the RO group: At least one RO from the set of SBFD symbols; at least one RO from the set of non-SBFD symbols; and / or at least one RO from among the set of SBFD symbols and the set of non-SBFD symbols; It may contain one or more of the following:

[0212] In some embodiments, an RO group includes multiple ROs and may include at least one RO from the set of SBFD symbols and at least one RO from the set of non-SBFD symbols.

[0213]

[0230] In some embodiments, the UE may further transmit a communication to the base station, which may be configured to establish communication between the UE and the base station based on the RO group.

[0214]

[0231] In some embodiments, constructing the RO groups includes constructing a first set of RO groups and a second set of RO groups, where each of the RO groups in the first set includes one or more ROs from a set of SBFD symbols and each of the RO groups in the second set includes one or more ROs from a set of non-SBFD symbols, and the constructed RO groups are included in the first set of RO groups and the second set of RO groups.

[0215]

[0232] In some embodiments, each of the RO groups in the first set may exclude ROs in non-SBFD symbols (e.g., include only ROs in SBFD symbols), and each of the RO groups in the second set may exclude ROs in SBFD symbols (e.g., include only ROs in non-SBFD symbols).

[0216]

[0233] In some embodiments, the UE may further receive threshold data for determining the number of PRACH repetitions, the threshold data may be based on a Reference Signal Received Power (RSRP) level, and the UE may determine the number of PRACH repetitions by comparing the RSRP of a downlink path loss reference signal with the threshold data. The constructed RO group may be based on the determined number of PRACH repetitions.

[0217]

[0234] In some embodiments, the threshold data may indicate a first threshold value provided by a first upper layer signaling for a first set of RO groups; the threshold data may indicate a second threshold value provided by a second upper layer signaling for a second set of RO groups; and the first threshold value is different from the second threshold value.

[0218]

[0235] In some embodiments, the UE may further apply legacy procedures to the first set of RO groups in response to determining that the number of ROs in the SBFD symbols differs from the number of ROs in the non-SBFD symbols.

[0219]

[0236] In some embodiments, the UE may further disable an RO group that includes at least one RO from the set of SBFD symbols and at least one RO from the set of non-SBFD symbols.

[0220]

[0237] In some embodiments, the UE may further exclude at least one RO from an RO group including at least one RO from the set of SBFD symbols and at least one RO from the set of non-SBFD symbols, where the number of the excluded at least one RO is less than the number of remaining ROs.

[0221]

[0238] In some embodiments, at least one RO in an SBFD symbol and at least one RO in a non-SBFD symbol may occupy different PRBs and may have the same frequency resource index.

[0222]

[0239] In some embodiments, the UE may further receive an indication via higher layer signaling, which may indicate whether the RO group includes at least one RO in an SBFD symbol and at least one RO in a non-SBFD symbol.

[0223]

[0240] In operation 1915, the UE communicates with a base station (e.g., a gNB) using at least one RO from the RO group. For example, the UE may modify the manner in which the UE transmits in its communication with the gNB in ​​step 1915 based on the RO group determined in step 1910 so that the gNB's current antenna configuration efficiently receives and interprets the communication.

[0224]

[0241] FIG. 20 is a block diagram of an electronic device in a network environment according to some embodiments of the present disclosure.

[0225]

[0242] 20 , an electronic device 2001 in a network environment 2000 may communicate with an electronic device 2002 via a first network 2098 (e.g., a short-range wireless communication network) or may communicate with an electronic device 2004 or a server 2008 via a second network 2099 (e.g., a long-range wireless communication network). The electronic device 2001 may communicate with the electronic device 2004 via the server 2008. The electronic device 2001 may include a processor 2020, a memory 2030, an input device 2050, a sound output device 2055, a display device 2060, an audio module 2070, a sensor module 2076, an interface 2077, a haptic module 2079, a camera module 2080, a power management module 2088, a battery 2089, a communication module 2090, a subscriber identification module (SIM) card 2096, and / or an antenna module 2097. In one embodiment, at least one of the components (e.g., the display device 2060 or the camera module 2080) may be omitted from the electronic device 2001, or one or more other components may be added to the electronic device 2001. Some components may be implemented as an integrated circuit (IC). For example, the sensor module 2076 (e.g., a fingerprint sensor, an iris sensor, or an illuminance sensor) may be integrated into the display device 2060 (e.g., a display).

[0226]

[0243] The processor 2020 may execute software (e.g., program 2040) to control at least one other component (e.g., hardware or software component) of the electronic device 2001 coupled to the processor 2020 and perform various data processing or calculations.

[0227]

[0244] As at least a part of its data processing or computation, the processor 2020 may load commands or data received from another component (e.g., the sensor module 2076 or the communication module 2090) into the volatile memory 2032, process the commands or data stored in the volatile memory 2032, and store the resulting data in the non-volatile memory 2034. The processor 2020 includes a main processor 2021 (e.g., a central processing unit or application processor (AP)) and an auxiliary processor 2023 (e.g., a graphics processing unit (GPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that operates independently or in conjunction with the main processor 2021. Additionally or alternatively, the auxiliary processor 2023 may be adapted to consume less power or to perform specific functions than the main processor 2021. The auxiliary processor 2023 may be implemented separately from the main processor 2021 or as part of it.

[0228]

[0245] The auxiliary processor 2023 may control at least a portion of the functionality or state associated with at least one component (e.g., the display device 2060, the sensor module 2076, or the communication module 2090) either opposite to the main processor 2021 while the main processor 2021 is in an inactive (e.g., sleep) state or together with the main processor 2021 while the main processor 2021 is in an active state (e.g., executing an application). The auxiliary processor 2023 (e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., the camera module 2080 or the communication module 2090) that is functionally associated with the auxiliary processor 2023.

[0229]

[0246] The memory 2030 may store various data used by at least one component (e.g., the processor 2020 or the sensor module 2076) of the electronic device 2001. The various data may include, for example, input data or output data for software (e.g., the program 2040) and their associated instructions. The memory 2030 may include volatile memory 2032 or non-volatile memory 2034.

[0230]

[0247] The programs 2040 may be stored in the memory 2030 as software, and may include, for example, an operating system (OS) 2042 , middleware 2044 , or applications 2046 .

[0231]

[0248] The input device 2050 may receive instructions or data from outside the electronic device 2001 (e.g., from a user) for use by other components of the electronic device 2001 (e.g., the processor 2020). The input device 2050 may include, for example, a microphone, a mouse, and a keyboard.

[0232]

[0249] The sound output device 2055 may output sound signals external to the electronic device 2001. The sound output device 2055 may include, for example, a speaker or a receiver. The speaker may be used for general purposes such as playing or recording multimedia, or the receiver may be used to receive incoming calls. The receiver may be implemented separately from the speaker or as part of the speaker.

[0233]

[0250] The display device 2060 can visually present information to an external (e.g., user) of the electronic device 2001. The display device 2060 can include, for example, a display, a holographic device, or a projector, and can include control circuitry for controlling the corresponding display, holographic device, or projector. The display device 2060 can include touch circuitry configured to detect a touch or can include sensor circuitry (e.g., a pressure sensor) configured to measure the strength of a force caused by a touch.

[0234]

[0251] The audio module 2070 can convert sound into electrical signals and vice versa. The audio module 2070 may acquire sound via the input device 2050 or output sound via headphones or sound output device 2055 of an external electronic device 2002 that is directly (e.g., wired) or wirelessly coupled to the electronic device 2001.

[0235]

[0252] The sensor module 2076 may detect an operating state (e.g., power or temperature) of the electronic device 2001 or an environmental state (e.g., a user state) external to the electronic device 2001. The sensor module 2076 may then generate an electrical signal or data value corresponding to the detected state. The sensor module 2076 may include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, and / or an illuminance sensor.

[0236]

[0253] The interface 2077 may support one or more specific protocols used when the electronic device 2001 is coupled directly (e.g., wired) or wirelessly to the external electronic device 2002. The interface 2077 may include, for example, a high-definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.

[0237]

[0254] The connection terminal 2078 may include a connector that allows the electronic device 2001 to be physically connected to the external electronic device 2002. The connection terminal 2078 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0238]

[0255] The haptic module 2079 can convert the electrical signals into mechanical stimuli (e.g., vibration or movement) or electrical stimuli that can be perceived by the user through a tactile or kinesthetic sense. The haptic module 2079 can include, for example, a motor, a piezoelectric element, or an electrical stimulator.

[0239]

[0256] The camera module 2080 can capture still or video images. The camera module 2080 can include one or more lenses, an image sensor, an image signal processor, or a flash. The power management module 2088 can manage the power provided to the electronic device 2001. The power management module 2088 can be implemented, for example, as at least part of a power management integrated circuit (PMIC).

[0240]

[0257] The battery 2089 may be capable of providing power to at least one component of the electronic device 2001. The battery 2089 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0241]

[0258] The communication module 2090 may support establishing a direct (e.g., wired) or wireless communication channel between the electronic device 2001 and an external electronic device (e.g., the electronic device 2002, the electronic device 2004, or the server 2008) and performing communication over the established communication channel. The communication module 2090 may include one or more communication processors capable of operating independently of the processor 2020 (e.g., an AP) and may support direct (e.g., wired) or wireless communication. The communication module 2090 includes a wireless communication module 2092 (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 2094 (e.g., a local area network (LAN) communication module or a power line communication (PLC) module). Corresponding ones of these communication modules may communicate with external electronic devices over a first network 2098 (e.g., a short-range communication network such as Bluetooth, Wi-Fi (wireless-fidelity) Direct, or the Infrared Data Association (IrDA) standard) or over a second network 2099 (e.g., a long-range communication network such as a cellular network, the Internet, or a computer network (e.g., a LAN or wide area network (WAN))). These various types of communication modules may be implemented as a single component (e.g., a single IC) or as multiple components (e.g., multiple ICs) separate from one another.The wireless communication module 2092 can use subscriber information (e.g., International Mobile Subscriber Identity (IMSI)) stored in the subscriber identification module 2096 to identify and authenticate the electronic device 2001 within a communication network, such as the first network 2098 or the second network 2099.

[0242]

[0259] The antenna module 2097 may transmit / receive signals or power to / from outside the electronic device 2001 (e.g., an external electronic device). The antenna module 2097 may include one or more antennas. The communication module 2090 (e.g., wireless communication module 2092) may select at least one of the one or more antennas suitable for a communication method used in a communication network, such as a first network 2098 or a second network 2099. Then, signals or power may be transmitted or received between the communication module 2090 and the external electronic device via the selected at least one antenna.

[0243]

[0260] Instructions or data may be transmitted or received between the electronic device 2001 and the external electronic device 2004 via a server 2008 connected to a second network 2099. Each of the electronic devices 2002 and 2004 may be the same type of device as the electronic device 2001 or a different type of device from the electronic device 210. All or part of the operations performed by the electronic device 2001 may be performed by one or more of the external electronic devices 2002, 2004, or the server 2008. For example, if the electronic device 2001 is to perform a function or service automatically or in response to a request from a user or other device, the electronic device 2001 may request one or more external electronic devices to perform at least a portion of the function or service instead of or in addition to performing the function or service. The one or more external electronic devices that receive the request may perform at least a portion of the requested function or service, or an additional function or service related to the request, and transmit the results of the execution to the electronic device 2001. The electronic device 2001 may provide the result as at least part of a response to the request, with or without further processing of the result, and for that purpose, for example, cloud computing, distributed computing, or client-server computing techniques may be used.

[0244]

[0261] Figure 21 illustrates a system including a UE 2105 and a gNB 2110 communicating with each other. The UE may include a radio 2115 and a processing circuit (or means for processing) 2120 that may perform various methods disclosed herein, such as the method described in Figure 19. For example, the processing circuit 2120 may receive transmissions from a network node (gNB) 2110 via the radio 2115, and the processing circuit 2120 may transmit signals to the gNB 2110 via the radio 2115.

[0245]

[0262] Embodiments of the subject matter and operations described herein may be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed herein and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described herein may be implemented as one or more computer programs, i.e., as one or more modules of computer program instructions encoded on a computer storage medium for execution by or to control the operation of a data processing apparatus. Alternatively, or additionally, the program instructions may be encoded in an artificially generated propagated signal, such as a machine-generated electrical, optical, or electromagnetic signal generated to encode information for transmission to a suitable receiving device for execution by a data processing apparatus. The computer storage medium may be, or be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination thereof. Furthermore, while a computer storage medium is not a propagating signal, a computer storage medium may be a source or destination of computer program instructions encoded in an artificially generated propagating signal. Also, a computer storage medium may be or be contained in one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices). Furthermore, the operations described herein may be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or data received from other sources.

[0246]

[0263] While the specification may include many specific implementation details, these implementation details should not be construed as limitations on the scope of any claimed subject matter, but rather as descriptions of features specific to particular embodiments. Certain features described herein in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination. Furthermore, while features may be described above as functioning in a particular combination, and even as such in the initial claims, one or more features of a claimed combination may, in some cases, be carved out of that combination, and the claimed combination may relate to subcombinations or variations of the subcombination.

[0247]

[0264] Similarly, while operations may be depicted in the figures in a particular order, this should not be understood as requiring such operations to be performed in the particular order or sequential order depicted, or that all of the operations depicted be performed, to achieve desired results. In some situations, multitasking and parallel processing may be advantageous. Furthermore, it should be understood that the division of various system components in the above-described embodiments does not require such division in all embodiments, and that the described program components and systems may generally be integrated together in a single software product or packaged in multiple software products.

[0248]

[0265] Certain embodiments of the subject matter have been described herein. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. Furthermore, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous.

[0249]

[0266] As will be recognized by those skilled in the art, the innovative concepts described herein are susceptible to modification and variation over a wide range of applications. Accordingly, the scope of the claims should not be limited to any of the specific exemplary teachings described above, but rather is defined by the following claims, including functional equivalents thereof.

Claims

1. A user equipment (UE) receives a configuration for subband full duplex (SBFD) operation and physical random access channel (PRACH) repetition; and the UE constructing a RACH occasion (RO) group based on the configuration, the RO group including one or more ROs from a set of SBFD symbols and a set of non-SBFD symbols; A method comprising:

2. 10. The method of claim 1, wherein one or more ROs in the group of ROs: at least one RO from said set of SBFD symbols; at least one RO from the set of non-SBFD symbols; or at least one RO from among the set of SBFD symbols and the set of non-SBFD symbols; The method includes one or more of the following:

3. 2. The method of claim 1, wherein the RO group includes a plurality of ROs, and includes at least one RO from the set of SBFD symbols and at least one RO from the set of non-SBFD symbols.

4. 10. The method of claim 1, further comprising the step of the UE transmitting a communication signal to a base station, the communication signal configured to establish communication between the UE and the base station based on the RO group.

5. 2. The method of claim 1, wherein the step of constructing an RO group further comprises: The UE establishing a first set of RO groups and a second set of RO groups; each RO group in the first set includes one or more ROs from the set of SBFD symbols; each RO group in the second set includes one or more ROs from the set of non-SBFD symbols; The method, wherein the constructed RO group is included in the first set of RO groups and the second set of RO groups.

6. 6. The method of claim 5, wherein: each RO group in the first set includes only one or more ROs from the set of SBFD symbols; Each of the RO groups in the second set includes only one or more ROs from the set of non-SBFD symbols.

7. 6. The method of claim 5, further comprising: receiving, by the UE, threshold data for determining a number of PRACH repetitions, the threshold data being based on a reference signal received power (RSRP) level; the UE determining the number of PRACH repetitions by comparing an RSRP of a downlink path loss reference signal with the threshold data; wherein the constructed RO group is based on a determined number of PRACH repetitions.

8. 8. The method of claim 7, wherein: The threshold data indicates a first threshold value provided by first upper layer signaling for a first set of RO groups; The threshold data indicates a second threshold value provided by second upper layer signaling for a second set of RO groups; and The method, wherein the first threshold is different from the second threshold.

9. 6. The method of claim 5, further comprising, in response to determining that a number of ROs in an SBFD symbol differs from a number of ROs in a non-SBFD symbol, applying a legacy procedure to the first set of RO groups.

10. 4. The method of claim 3, further comprising: Disabling an RO group including at least one RO from the set of SBFD symbols and at least one RO from the set of non-SBFD symbols; A method comprising:

11. 4. The method of claim 3, further comprising: removing at least one RO from an RO group including at least one RO from the set of SBFD symbols and at least one RO from the set of non-SBFD symbols, wherein the number of the removed at least one RO is less than the number of remaining ROs; A method comprising:

12. 4. The method of claim 3, wherein at least one RO in the SBFD symbol and at least one RO in the non-SBFD symbol occupy different physical resource blocks (PRBs) and have the same frequency resource index.

13. 4. The method of claim 3, further comprising: receiving, by the UE, an indication through higher layer signaling; wherein the indication indicates whether an RO group includes at least one RO in the SBFD symbol and at least one RO in the non-SBFD symbol.

14. 1. A user equipment (UE) comprising a processing circuit, the processing circuit comprising: receiving a configuration for subband full duplex (SBFD) operation and physical random access channel (PRACH) repetition; and constructing a RACH occasion (RO) group based on the configuration, the RO group including one or more ROs from a set of SBFD symbols and a set of non-SBFD symbols; The UE is configured to:

15. 15. The UE of claim 14, wherein one or more ROs in the RO group: at least one RO from said set of SBFD symbols; at least one RO from the set of non-SBFD symbols; or at least one RO from among the set of SBFD symbols and the set of non-SBFD symbols; UE, including one or more of:

16. 15. The UE of claim 14, wherein the RO group includes a plurality of ROs, and includes at least one RO from the set of SBFD symbols and at least one RO from the set of non-SBFD symbols.

17. 15. The UE of claim 14, wherein the processing circuitry further comprises: a UE configured to perform the step of transmitting a communication signal to a base station, the communication signal configured to establish communication between the UE and the base station based on the RO group.

18. 15. In the UE of claim 14, the step of establishing an RO group further comprises: constructing a first set of RO groups and a second set of RO groups; each RO group in the first set includes one or more ROs from the set of SBFD symbols; each RO group in the second set includes one or more ROs from the set of non-SBFD symbols; The constructed RO group is included in the first set of RO groups and the second set of RO groups.

19. 20. The UE of claim 18, wherein the processing circuitry further comprises: Disabling an RO group including at least one RO from the set of SBFD symbols and at least one RO from the set of non-SBFD symbols; The UE is configured to:

20. 1. A system including a user equipment (UE), the UE comprising: receiving a configuration for subband full duplex (SBFD) operation and physical random access channel (PRACH) repetition; and constructing a RACH occasion (RO) group based on the configuration, the RO group including one or more ROs from a set of SBFD symbols and a set of non-SBFD symbols; A system that is configured to:

Images