Random access verification across multiple symbol types

Abstract

Methods, systems, and apparatus for random access authentication across multiple symbol types are described. In some examples, the User Equipment (UE) may receive a configuration message indicating to the UE a set of Random Access Channel (RACH) times for performing the random access procedure. In some examples, the UE may select a valid RACH time from the set of RACH times based on a first validity rule, where the first validity rule defines the validity of the RACH time when it is associated with a first time slot spanning one or more sub-band full-duplex (SBFD) resources and one or more non-SBFD resources. In some examples, the UE may transmit a Physical RACH (PRACH) preamble during a valid RACH time selected according to the first validity rule.

Description

[0001] Cross-references

[0002] This patent application claims the benefits of U.S. Provisional Patent Application No. 63 / 572,711, filed April 1, 2024, entitled “RANDOM ACCESS VALIDATION ACROSS MULTIPLE SYMBOL TYPES,” and U.S. Patent Application No. 19 / 042,330, filed January 31, 2025, entitled “RANDOM ACCESS VALIDATION ACROSS MULTIPLE SYMBOL TYPES,” each of which is assigned to the assignee of this application. Technical Field

[0003] The following section deals with random access authentication across multiple symbol types, including random access authentication across multiple symbol types. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting random access authentication across multiple symbol types. For example, the described techniques provide network entities and user equipment (UEs) with improved efficiency in preamble transmission. For instance, the UE and network entities can use validity rules to analyze whether a given random access channel (RACH) timing (RO) is a valid RO for the transmission of a random access preamble.

[0006] In some examples, RO is valid based on sub-band full-duplex (SBFD) resources that exclusively span the physical RACH (PRACH) time slot or non-SBFD resources that exclusively span the PRACH time slot. In some cases, similar rules can be used to verify the physical uplink shared channel (PUSCH) timing (PO) for two-step RO.

[0007] In some examples, a RO can be valid across both SBFD and non-SBFD resources if one or more conditions are met. Conditions may include that the SBFD and non-SBFD resources are directly adjacent in time (e.g., without time gaps), and that the RO across both SBFD and non-SBFD resources is associated with the same set of frequency resources, the same spatial configuration, and the same power control parameters. Similar rules can be used in some cases to verify the PO of a two-step RO.

[0008] In some examples, when a guard period (e.g., a time gap) exists between SBFD and non-SBFD resources, the RO can be valid across both SBFD and non-SBFD resources. In a first example, the UE can ignore the guard period and transmit the RACH preamble throughout the entire RO. In a second example, the UE can discard the portion of the RACH preamble during the guard period, but transmit the portion of the RACH preamble during both SBFD and non-SBFD resource periods. In a third example, the UE can discard the portion of the RACH preamble during the non-SBFD resource period and transmit it exclusively during the SBFD resource period. In a fourth example, the UE can discard the portion of the RACH preamble during the SBFD resource period and transmit it exclusively during the non-SBFD resource period. In some cases, one or more similar rules can be used to verify the PO of a two-step RO.

[0009] In some examples, the RO may include a set of sequence repetitions of the PRACH preamble, where the UE may transmit the PRACH preamble during each sequence repetition. Therefore, if one of the sequence repetitions of the RO aligns with the boundary between SBFD and non-SBFD resources, the RO can be valid across both SBFD and non-SBFD resources.

[0010] Additionally or alternatively, the UE may be configured with a second RO, which is a time-division duplex (TDD) RO exclusively scheduled for non-SBFD resources. Therefore, the RO can be valid based on how it overlaps with the second RO across time and frequency.

[0011] A method for wireless communication by a UE is described. The method may include: receiving a configuration message indicating to the UE a set of multiple Remote Access Registries (ROs) for performing a random access procedure; selecting a valid RO from the set of ROs based on a first validity rule, wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources; and transmitting a PRACH preamble during the selection of the valid RO according to the first validity rule.

[0012] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code so that the UE: receives a configuration message indicating to the UE a set of multiple Remote Access Registries (ROs) for performing a random access procedure; selects a valid RO from the set of multiple ROs based on a first validity rule, wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources; and transmits a PRACH preamble during the selection of the valid RO according to the first validity rule.

[0013] Another UE for wireless communication is described. The UE may include: components for receiving a configuration message indicating to the UE a set of multiple Remote Access Registries (ROs) for performing a random access procedure; components for selecting a valid RO from the set of ROs based on a first validity rule, wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources; and components for transmitting a PRACH preamble during the selection of the valid RO according to the first validity rule.

[0014] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive a configuration message indicating to the UE a set of multiple Remote Access Registries (ROs) for performing a random access procedure; select a valid RO from the set of ROs based on a first validity rule, wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources; and transmit a PRACH preamble during the selection of the valid RO according to the first validity rule.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, a valid RO may be valid based on the first validity rule, either exclusively spanning the one or more SBFD resources of the first time slot or exclusively spanning the one or more non-SBFD resources of the first time slot.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, according to the first validity rule, a valid RO can be valid across one or more SBFD resources and one or more non-SBFD resources that are directly adjacent in time, and the valid RO can be associated with the same set of multiple frequency resources, the same spatial configuration, and the same power control parameters across one or more SBFD resources and one or more non-SBFD resources.

[0017] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first time slot includes a protection period between the one or more SBFD resources and the one or more non-SBFD resources, and the effective RO spans the protection period, the one or more SBFD resources, and the one or more non-SBFD resources.

[0018] The methods described herein, UEs, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for transmitting the PRACH preamble across the protection period, the one or more SBFD resources, and each of the one or more non-SBFD resources during the effective RO, wherein the PRACH preamble may be associated with the same set of transmission parameters across the one or more SBFD resources and the one or more non-SBFD resources.

[0019] The methods described herein, examples of UEs and nontransitory computer-readable media may also include operations, features, components or instructions for discarding a portion of the PRACH preamble across the protection period during the effective RO, wherein the PRACH preamble may be associated with a first set of transmission parameters across the one or more SBFD resources and with a second set of transmission parameters across the one or more non-SBFD resources.

[0020] Some examples of the methods, UEs, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: transmitting a first portion of the PRACH preamble associated with one or more SBFD resources in the first time slot prior to the protection period; and discarding a second portion of the PRACH preamble associated with one or more non-SBFD resources in the first time slot after the protection period.

[0021] The methods described herein, some examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for transmitting a third part of the PRACH preamble associated with resources during the protection period.

[0022] Some examples of the methods, UEs, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: discarding the PRACH preamble, a first portion of which is associated with the one or more SBFD resources of the first time slot, spanning from the beginning of the first time slot to the end of the protection period; and transmitting the PRACH preamble, a second portion of which is associated with the one or more non-SBFD resources of the first time slot after the protection period.

[0023] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, according to the first validity rule, the valid RO comprises a set of multiple sequence repeats, and the valid RO may be valid based on the sequence repeats in the set of multiple sequence repeats that can be aligned with the boundary between the one or more SBFD resources and the one or more non-SBFD resources.

[0024] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the effective RO spans the one or more SBFD resources and the one or more non-SBFD resources, and the UE may be configured with a second RO that exclusively spans the one or more non-SBFD resources, the second RO including a time-division duplex RO.

[0025] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the effective RO timing may be valid based on the effective RO crossing one or more non-SBFD resources across one or more first symbols, provided that the one or more first symbols do not overlap with one or more second symbols associated with the second RO, according to the first validity rule.

[0026] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the valid RO can be valid based on the first validity rule, whereby the valid RO and the second RO are each mapped to the same synchronization signal block index.

[0027] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, a valid RO can be valid based on the first validity rule, whereby the valid RO is associated with a first frequency span and the second RO is associated with a second frequency span, and the frequency interval between the first and second frequency spans satisfies a threshold.

[0028] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the random access procedure may be a two-step random access procedure, and the methods, apparatus, and nontransitory computer-readable media may also include operations, features, components, or instructions for: selecting a valid PUSCH timing from a set of multiple Physical Uplink Shared Channel (PUSCH) timings based on a second validity rule, wherein the second validity rule defines the validity of the PUSCH timing when it can be associated with a second time slot spanning one or more second SBFD resources and one or more second non-SBFD resources; and transmitting data messages during the valid PUSCH timing selected according to the second validity rule.

[0029] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the second validity rule defines the validity of the valid PUSCH timing based on whether the valid PUSCH timing exclusively spans the one or more second SBFD resources of the second time slot or exclusively spans the one or more second non-SBFD resources of the second time slot.

[0030] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the second validity rule defines the validity of the valid PUSCH timing based on the valid PUSCH timing spanning the one or more second SBFD resources and the one or more second non-SBFD resources of the second time slot; the one or more second SBFD resources and the one or more second non-SBFD resources may be directly adjacent in time; and the PUSCH timing may be associated with the same set of multiple frequency resources, the same spatial configuration, and the same power control parameters across the one or more second SBFD resources and the one or more second non-SBFD resources of the second time slot.

[0031] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the second time slot includes a second protection period between the one or more second SBFD resources and the one or more second non-SBFD resources, and the effective PUSCH timing spans the second protection period, the one or more second SBFD resources, and the one or more second non-SBFD resources.

[0032] The methods described herein, UEs, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for transmitting the data message across each of the second protection period, the one or more second SBFD resources, and the one or more second non-SBFD resources during the effective PUSCH timing, wherein the data message may be associated with the same set of transmission parameters across the one or more second SBFD resources and the one or more second non-SBFD resources.

[0033] The methods described herein, some examples of UEs and nontransitory computer-readable media may also include operations, features, components or instructions for discarding a portion of the data message spanning the second protection period during the effective PUSCH timing, wherein the data message may be associated with a first set of transmission parameters across the one or more second SBFD resources and with a second set of transmission parameters across the one or more second non-SBFD resources.

[0034] Some examples of the methods, UEs, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: transmitting a first portion of the data message associated with the one or more second SBFD resources in the second time slot prior to the second protection period; and discarding a second portion of the data message associated with the one or more second non-SBFD resources in the second time slot after the second protection period.

[0035] The methods described herein, some examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for transmitting a third part of the data message associated with resources during the second protection period.

[0036] Some examples of the methods, UEs, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: discarding a first portion of the data message associated with the one or more second SBFD resources of the second time slot, spanning from the beginning of the second time slot to the end of the second protection period; and transmitting a second portion of the data message associated with the one or more second non-SBFD resources of the second time slot after the second protection period.

[0037] A method for wireless communication by a network entity is described. The method may include: sending a configuration message indicating to a UE a set of multiple Remote Routers (ROs) for performing a random access procedure; and receiving a PRACH preamble during a valid RO in the set of ROs, wherein the valid RO is based on a first validity rule, and wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources.

[0038] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to cause the network entity to: send a configuration message indicating to the UE a set of multiple Remote Routers (ROs) for performing a random access procedure; and receive a PRACH preamble during a valid RO in the set of multiple ROs, wherein the valid RO is based on a first validity rule, and wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources.

[0039] Another network entity for wireless communication is described. This network entity may include: components for sending a configuration message indicating to the UE a set of multiple Remote Routers (ROs) for performing a random access procedure; and components for receiving a PRACH preamble during a valid RO in the set of multiple ROs, wherein the valid RO is based on a first validity rule, and wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources.

[0040] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: transmit a configuration message indicating to the UE a set of multiple Remote Routers (ROs) for performing a random access procedure; and receive a PRACH preamble during a valid RO in the set of ROs, wherein the valid RO is based on a first validity rule, and wherein the first validity rule defines the validity of an RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources.

[0041] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a valid RO may be valid based on the first validity rule, either exclusively spanning the one or more SBFD resources of the first time slot or exclusively spanning the one or more non-SBFD resources of the first time slot.

[0042] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, according to the first validity rule, a valid RO can be valid across one or more SBFD resources and one or more non-SBFD resources that are directly adjacent in time, and the valid RO can be associated with the same set of multiple frequency resources, the same spatial configuration, and the same power control parameters across one or more SBFD resources and one or more non-SBFD resources.

[0043] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first time slot includes a protection period between the one or more SBFD resources and the one or more non-SBFD resources, and the effective RO spans the protection period, the one or more SBFD resources, and the one or more non-SBFD resources.

[0044] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving, during the effective RO, a portion of the PRACH preamble across the protection period, the one or more SBFD resources, and the one or more non-SBFD resources, wherein the PRACH preamble may be associated with the same set of transmission parameters across the one or more SBFD resources and the one or more non-SBFD resources.

[0045] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving the PRACH preamble and associated with one or more SBFD resources in the first time slot prior to the protection period.

[0046] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second portion of the PRACH preamble associated with resources during the protection period.

[0047] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving the PRACH preamble and associated with the first portion of the first time slot after the protection period, which is one or more non-SBFD resources.

[0048] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, according to the first validity rule, the valid RO comprises a set of multiple sequence repeats, and the valid RO may be valid based on the sequence repeats in the set of multiple sequence repeats that can be aligned with the boundary between the one or more SBFD resources and the one or more non-SBFD resources.

[0049] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the effective RO spans the one or more SBFD resources and the one or more non-SBFD resources, and the UE may be scheduled to have a second RO that exclusively spans the one or more non-SBFD resources, the second RO including a time-division duplex RO.

[0050] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the effective RO timing may be valid based on the first validity rule, whereby the effective RO across one or more non-SBFD resources and across one or more first symbols, which do not overlap with one or more second symbols associated with the second RO.

[0051] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, a valid RO may be valid based on the first validity rule, whereby the valid RO and the second RO are each mapped to the same synchronization signal block index.

[0052] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a valid RO can be valid based on the first validity rule, whereby the valid RO is associated with a first frequency span and the second RO is associated with a second frequency span, and the frequency interval between the first and second frequency spans satisfies a threshold.

[0053] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the random access procedure may be a two-step random access procedure, and the method, apparatus, and nontransitory computer-readable media may also include operations, features, components, or instructions for receiving data messages during a valid PUSCH time slot in a set of multiple PUSCH time slots, wherein the valid PUSCH time slot may be based on a second validity rule, wherein the second validity rule defines the validity of the PUSCH time slot when it can be associated with a second time slot spanning one or more second SBFD resources and one or more second non-SBFD resources.

[0054] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the second validity rule defines the validity of the valid PUSCH timing based on whether the valid PUSCH timing exclusively spans the one or more second SBFD resources of the second time slot or exclusively spans the one or more second non-SBFD resources of the second time slot.

[0055] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the second validity rule defines the validity of the valid PUSCH timing based on the valid PUSCH timing spanning the one or more second SBFD resources and the one or more second non-SBFD resources of the second time slot; the one or more second SBFD resources and the one or more second non-SBFD resources may be directly adjacent in time; and the PUSCH timing may be associated with the same set of multiple frequency resources, the same spatial configuration, and the same power control parameters across the one or more second SBFD resources and the one or more second non-SBFD resources of the second time slot.

[0056] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the second time slot includes a second protection period between the one or more second SBFD resources and the one or more second non-SBFD resources, and the effective PUSCH timing spans the second protection period, the one or more second SBFD resources, and the one or more second non-SBFD resources.

[0057] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving, during the effective PUSCH timing, a portion of the data message spanning the second protection period, the one or more second SBFD resources, and the one or more second non-SBFD resources, wherein the data message may be associated with the same set of transmission parameters across the one or more second SBFD resources and the one or more second non-SBFD resources.

[0058] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving the data message in connection with one or more second SBFD resources in the second time slot prior to the second protection period.

[0059] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second portion of the data message associated with the resources during the second protection period.

[0060] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving the data message in connection with one or more second non-SBFD resources in the second time slot following the second protection period. Attached Figure Description

[0061] Figure 1 An example of a wireless communication system supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown.

[0062] Figure 2 An example of a wireless communication system supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown.

[0063] Figure 3A and Figure 3B Examples of transmission timing verification processes supporting random access verification across multiple symbol types are shown, each according to one or more aspects of this disclosure.

[0064] Figure 4A and Figure 4B Examples of transmission timing verification processes supporting random access verification across multiple symbol types are shown, each according to one or more aspects of this disclosure.

[0065] Figures 5A to 5D Examples of transmission timing verification processes supporting random access verification across multiple symbol types are shown, each according to one or more aspects of this disclosure.

[0066] Figure 6 An example of a random access channel (RACH) timing verification process supporting random access verification across multiple symbol types, according to one or more aspects of this disclosure, is shown.

[0067] Figure 7 An example of a RACH timing verification process supporting random access verification across multiple symbol types, according to one or more aspects of this disclosure, is shown.

[0068] Figure 8 An example of a process flow supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown.

[0069] Figure 9 and Figure 10 A block diagram of an apparatus supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown.

[0070] Figure 11 A block diagram of a communication manager supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown.

[0071] Figure 12 A diagram is shown of a system including a device that supports random access authentication across multiple symbol types, according to one or more aspects of this disclosure.

[0072] Figure 13 and Figure 14 A block diagram of an apparatus supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown.

[0073] Figure 15 A block diagram of a communication manager supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown.

[0074] Figure 16 A diagram is shown of a system including a device that supports random access authentication across multiple symbol types, according to one or more aspects of this disclosure.

[0075] Figures 17 to 20 A flowchart illustrating a method for supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0076] In some examples of wireless communication, user equipment (UE) can perform random access procedures with a network entity. For example, a network entity can configure the UE with one or more Random Access Channel (RACH) times (ROs), on which the UE can send a random access preamble to request the establishment of a radio connection with the network entity. In some examples, the network entity can schedule a set of ROs across one or more physical RACH (PRACH) time slots. Additionally or alternatively, PRACH time slots can span a set of subband full-duplex (SBFD) resources that allow concurrent transmission and reception of data at the UE, and can also span a set of non-SBFD resources (e.g., uplink resources or flexible resources). However, in some cases, if a given RO spans both SBFD and non-SBFD resources, the effectiveness of preamble transmission during a given RO may be reduced. For example, SBFD and non-SBFD resources may be associated with different timing advances, different frequency allocations, different spatial beamforming allocations, and different power control parameters, which may reduce the reliability of preamble transmission.

[0077] Network entities and UEs can improve the efficiency of preamble transmission by operating according to the techniques described herein. For example, UEs and network entities can use validity rules to analyze whether a given RO is a valid RO for the transmission of a random access preamble.

[0078] In some examples, the RO is valid based on either SBFD resources that exclusively span the PRACH slot or non-SBFD resources that exclusively span the PRACH slot. In some cases, similar rules can be used to verify the Physical Uplink Shared Channel (PUSCH) Timing (PO) for a two-step RO.

[0079] In some examples, a RO can be valid across both SBFD and non-SBFD resources if one or more conditions are met. Conditions may include that the SBFD and non-SBFD resources are directly adjacent in time (e.g., without time gaps), and that the RO across both SBFD and non-SBFD resources is associated with the same set of frequency resources, the same spatial configuration, and the same power control parameters. Similar rules can be used in some cases to verify the PO of a two-step RO.

[0080] In some examples, when a guard period (e.g., a time gap) exists between SBFD and non-SBFD resources, the RO can be valid across both SBFD and non-SBFD resources. In some cases, the guard period may be referred to as a transient period. In the first example, the UE may ignore the guard period and transmit the RACH preamble throughout the entire RO. In the second example, the UE may discard the portion of the RACH preamble during the guard period, but transmit the portion of the RACH preamble during both SBFD and non-SBFD resource periods. In the third example, the UE may discard the portion of the RACH preamble during the non-SBFD resource period and transmit exclusively during the SBFD resource period. In the fourth example, the UE may discard the portion of the RACH preamble during the SBFD resource period and transmit exclusively during the non-SBFD resource period. In some cases, one or more similar rules may be used to verify the PO of a two-step RO.

[0081] In some examples, the RO may include a set of sequence repetitions, where the UE may send a RACH preamble during each sequence repetition. Therefore, if one of the sequence repetitions of the RO aligns with the boundary between SBFD and non-SBFD resources, the RO can be valid across both SBFD and non-SBFD resources.

[0082] Additionally or alternatively, the UE may be configured with a second RO, which is a time-division duplex (TDD) RO exclusively scheduled for non-SBFD resources. Therefore, the RO can be valid based on how it overlaps with the second RO across time and frequency.

[0083] Various aspects of this disclosure are first described in the context of wireless communication systems, transmission timing verification processes, RO verification processes, and process flows. These aspects are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to random access verification across multiple symbol types, and are further described with reference to these diagrams.

[0084] Figure 1 An example of a wireless communication system 100 supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown. The wireless communication system 100 may include one or more devices, such as one or more network devices (e.g., network entity 105), one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0085] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via communication link 125 (e.g., a radio frequency (RF) access link). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish communication link 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0086] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are shown below. Figure 1 As shown, the UE 115 described herein may be able to support communication with various types of devices in the wireless communication system 100 (e.g., other wireless communication devices, including the UE 115 or network entity 105).

[0087] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0088] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via backhaul communication link 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof, or may include one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with the core network 130 via communication link 155.

[0089] One or more of the network entities 105 or network equipment described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, Node B, evolved Node B (eNB), next-generation Node B or gigabit Node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home Node B, home evolved Node B or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).

[0090] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across multiple network entities (e.g., network entity 105) such as an Integrated Access and Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) (such as CU 160), a Distributed Unit (DU) (such as DU 165), a Radio Unit (RU) (such as RU 170), a RAN Intelligent Controller (RIC) (such as RIC 175) (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a Service Management and Orchestration (SMO) system (such as SMO system 180), or any combination thereof. RU 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0091] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 (e.g., one or more CUs) can connect to DU 165 (e.g., one or more DUs) or RU 170 (e.g., one or more RUs) or some combination thereof, and DU 165, RU 170, or both can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and can each be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split may be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can (e.g., via one or more different RUs, such as RU 170) support one or more different cells. In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by a different one of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by corresponding network entities (e.g., one or more network entities in network entity 105) that communicate via such communication links.

[0092] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities in network entity 105 (e.g., network entity 105 or IAB node 104) may be partially controlled by each other. IAB node 104 may be referred to as a donor entity or IAB donor. DU 165 or RU 170 may be partially controlled by CU 160 associated with network entity 105 or base station 140 (such as a donor network entity or donor base station). One or more donor entities (e.g., IAB donors) may communicate with one or more additional devices (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DU 165) of a coupled IAB donor. The IAB-MT may be equipped with a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include one or more DUs (e.g., DU 165) that support communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., IAB node 104, or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0093] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the tests described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., components such as IAB node, DU 165, CU 160, RU 170, RIC 175, SMO system 180).

[0094] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in a variety of objects such as appliances, vehicles, or meters.

[0095] The UE 115 described herein can communicate with various types of devices, such as the UE 115 which sometimes operates as a relay, as well as network entity 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0096] UE 115 and network entity 105 can wirelessly communicate with each other via communication link 125 (e.g., one or more access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined PHY layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured to utilize multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities, such as one or more network entities in network entity 105).

[0097] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0098] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response This can represent the supported subcarrier spacing, and The supported Discrete Fourier Transform (DFT) size can be represented. Time intervals for communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0099] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may also be divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems, such as wireless communication system 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0100] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0101] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a public search space set configured to transmit control information to UE115 (e.g., one or more UEs), or it may include a UE-specific search space set configured to transmit control information to UE115 (e.g., a particular UE).

[0102] In some examples, network entity 105 (e.g., base station 140, RU 170) can be mobile, and thus provide communication coverage to mobile coverage areas (such as coverage area 110). In some examples, coverage areas 110 associated with different technologies (e.g., different coverage areas) can overlap, but coverage areas 110 (e.g., different coverage areas) can be supported by the same network entity (e.g., network entity 105). In some other examples, overlapping coverage areas (such as coverage area 110) associated with different technologies can be supported by different network entities (e.g., network entity 105). The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 support communication in coverage areas 110 (e.g., different coverage areas) using the same or different RATs.

[0103] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0104] In some examples, UE 115 may be configured to support direct communication with other UEs (e.g., one or more UEs in UE 115) via a device-to-device (D2D) communication link (such as D2D communication link 135) (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group performing D2D communication may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, where each UE 115 sends to one or more UEs within the group. In some examples, network entity 105 can facilitate the scheduling of resources used for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving network entity 105.

[0105] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0106] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers).

[0107] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0108] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0109] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a particular orientation of the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., for the antenna array of the transmitting or receiving device or for some other orientation).

[0110] In some examples of the wireless communication system 100, UE 115 may perform a random access procedure with network entity 105. For example, network entity 105 may configure UE 115 with one or more ROs, on which UE 115 may send a random access preamble to request the establishment of a wireless connection with network entity 105. In some examples, network entity 105 may schedule a set of ROs across one or more PRACH slots. Additionally or alternatively, PRACH slots may span a set of SBFD resources that allow concurrent transmission and reception of data at UE 115, and may also span a set of non-SBFD resources (e.g., uplink resources or flexible resources). However, in some cases, if a given RO spans both SBFD and non-SBFD resources, the effectiveness of preamble transmission during a given RO may be reduced. For example, SBFD and non-SBFD resources may be associated with different timing advances, different frequency allocations, different spatial beamforming allocations, and different power control parameters, which may reduce the reliability of preamble transmission.

[0111] Network entity 105 and UE 115 can improve the efficiency of preamble transmission by operating according to the techniques described herein. For example, UE 115 and network entity 105 can use validity rules to analyze whether a given RO is a valid RO for the transmission of a random access preamble.

[0112] In some examples, an RO is valid based on either an SBFD resource that exclusively spans the PRACH time slot or a non-SBFD resource that exclusively spans the PRACH time slot. In some cases, similar rules can be used to verify the PO for a two-step RO.

[0113] In some examples, a RO can be valid across both SBFD and non-SBFD resources if one or more conditions are met. Conditions may include that the SBFD and non-SBFD resources are directly adjacent in time (e.g., without time gaps), and that the RO across both SBFD and non-SBFD resources is associated with the same set of frequency resources, the same spatial configuration, and the same power control parameters. Similar rules can be used in some cases to verify the PO of a two-step RO.

[0114] In some examples, when a guard period (e.g., a time gap) exists between SBFD and non-SBFD resources, the RO can be valid across both SBFD and non-SBFD resources. In a first example, UE 115 may ignore the guard period and transmit the RACH preamble throughout the entire RO. In a second example, UE 115 may discard the portion of the RACH preamble during the guard period, but transmit the portion of the RACH preamble during both SBFD and non-SBFD resource periods. In a third example, UE 115 may discard the portion of the RACH preamble during the non-SBFD resource period and transmit exclusively during the SBFD resource period. In a fourth example, UE 115 may discard the portion of the RACH preamble during the SBFD resource period and transmit exclusively during the non-SBFD resource period. In some cases, one or more similar rules may be used to verify the PO of a two-step RO.

[0115] In some examples, the RO may include a set of sequence repetitions, where the UE 115 may send a RACH preamble during each sequence repetition. Therefore, if one of the sequence repetitions of the RO aligns with the boundary between SBFD and non-SBFD resources, the RO can be valid across both SBFD and non-SBFD resources.

[0116] Additionally or alternatively, UE 115 may be configured with a second RO, which is a TDD-RO exclusively scheduled for non-SBFD resources. Therefore, the RO can be valid based on how it overlaps with the second RO across time and frequency.

[0117] Figure 2 An example of a wireless communication system 200 supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown. The wireless communication system 200 may implement, or be implemented by, aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a UE 115-a, which may be an example of UE 115 as described herein. The wireless communication system 200 may include a network entity 105-a, which may be an example of network entity 105 as described herein.

[0118] In some examples of the wireless communication system 200, UE 115-a and network entity 105-a may operate according to one or more random access procedures. For example, when UE 115-a may have data to transmit, when UE 115-a wishes to establish a connection with network entity 105-a, or both, UE 115-a may use a random access procedure to initiate communication with network entity 105-a. As part of the random access procedure, UE 115-a may send a PRACH preamble 220 to network entity 105-a via the uplink, where the PRACH preamble 220 serves as a request for access to network entity 105-a.

[0119] In some cases, UE 115-a may use a contention-based random access (CBRA) procedure. For example, according to the CBRA procedure, UE 115-a may select a PRACH preamble 220 from one or more preamble pools shared by UE 115-a and other UE 115s associated with network entity 105-a. Therefore, network entity 105-a monitors preambles from these pools and may allocate uplink resources to one or more UE 115s that successfully send the corresponding preamble without conflict. In the event of a conflict, a given UE 115-a may retry the CBRA procedure using a different preamble (e.g., after a configured random access backoff period). In some examples, CBRA may be suitable for scenarios with a large number of UE 115s and varying traffic loads because CBRA allows for flexible and dynamic access to network entity 105-a. Additionally or alternatively, the CBRA procedure may be referred to as a four-step RACH procedure.

[0120] In some cases, UE 115-a may use a contention-free random access (CFRA) procedure. According to the CFRA procedure, conflict-free access to network resources can be ensured through scheduled access. For example, network entity 105-a may allocate appropriate time slots or resources to one or more UEs 115, which can reduce contention and PRACH preamble 220 collisions for UE 115-a. In some examples, CFRA-scheduled access may be based on various factors, such as quality of service parameters, service priority ordering, or pre-negotiated access protocols. Therefore, CFRA may be advantageous in scenarios where improved quality of service is beneficial or where contention-based access may lead to excessive collisions and latency. Additionally or alternatively, the CFRA procedure may be referred to as a two-step RACH procedure.

[0121] In some cases, UE 115-a may perform a given RACH procedure (e.g., CBRA or CFRA) based on one or more ROs. For example, the set of ROs may refer to a corresponding time interval within a communication protocol, where UE 115-a may initiate a RACH procedure to access network entity 105-a. In some examples, UE 115-a may determine the set of ROs based on receiving RACH configuration message 205. For example, RACH configuration message 205 may be an example of a PRACH configuration (e.g., as part of an RRC configuration), which may be configured to include one or more tables of the corresponding PRACH configuration. Therefore, RACH configuration message 205 or a second control message may indicate an index associated with one or more tables of the PRACH configuration. For example, the index may indicate the preamble format, PRACH period, PRACH slot, and the number of ROs per PRACH slot.

[0122] In some examples, UE 115-a and network entity 105-a may determine to operate according to a two-step RACH (e.g., instead of a four-step RACH) based on one or more advantages. For example, a two-step RACH procedure may be associated with reduced latency and signaling overhead compared to a four-step RACH procedure. Additionally or alternatively, a two-step RACH procedure may support the use of different transport block sizes (TBS), different modulation and decoding schemes (MCS), or both, with no timing advance (TA) and no permission for small uplink packet transmission. Additionally or alternatively, a two-step RACH procedure may be associated with increased message payload capacity and power efficiency compared to a four-step RACH procedure.

[0123] In the case of two-step RACH, UE 115-a can also be configured with a set of POs that can be associated with a set of configured ROs. For example, similar to ROs that may include time and frequency resources allocated for the transmission of msgA PRACH preamble 220, POs may include time and frequency resources allocated for the transmission of msgA PUSCH (e.g., data transmission). To support asynchronous uplink transmission in two-step RACH, a guard time (GT) and guard band (GB) can be configured for each PO to mitigate inter-carrier interference (ICI) and inter-symbol interference (ICI).

[0124] Additionally or alternatively, a given RO may be associated with a corresponding PO set. For example, if UE 115-a selects a first RO from a configured set of ROs for transmission of PRACH preamble 220, the first RO may be associated with a set of POs from which UE 115-a may select a first PO for transmission of PUSCH. Additionally or alternatively, the msgA transmission of the two-step RACH procedure may be associated with a PUSCH resource unit (PRU), which may indicate the PO and demodulation reference signal (DMRS) port or sequence used for msgA payload transmission.

[0125] In both four-step RACH (e.g., Type 1 RACH) and two-step RACH (e.g., Type 2 RACH) scenarios, the configured PRACH slots can span different types of symbols. For example, a PRACH slot can span both SBFD symbols and non-SBFD symbols. As described herein, an SBFD symbol may include both uplink and downlink resources that allow concurrent transmission and reception of data at UE 115-a. Additionally or alternatively, a non-SBFD symbol may include uplink resources or flexible resources that allow UE 115-a to transmit data. In a first example, a PRACH slot (e.g., which includes one or more ROs) can span a single slot (e.g., a mixed slot) that includes both SBFD and non-SBFD resources. In a second example, a PRACH slot (e.g., which includes one or more ROs) can span multiple SBFD and non-SBFD slots (e.g., for a long PRACH preamble 220 sequence type). Additionally or alternatively, a Type 2 RACH may include a PUSCH slot (e.g., which includes one or more POs) that spans both SBFD and non-SBFD symbols.

[0126] However, in some cases, if a given RO spans both SBFD and non-SBFD resources, the effectiveness of preamble transmission during that given RO may be reduced. For example, SBFD and non-SBFD resources can be associated with different timing advances, different frequency allocations, different spatial beamforming allocations, and different power control parameters, which may decrease the reliability of preamble transmission. Similarly, a given PO spanning both SBFD and non-SBFD resources can reduce the effectiveness of PUSCH transmission during that given PO.

[0127] Network entity 105-a and UE 115-a can improve the efficiency of preamble and PUSCH transmission by operating according to the techniques described herein. For example, UE 115-a and network entity 105-a can use one or more validity rules to analyze whether a given RO is a valid RO for the transmission of PRACH preamble 220. For example, as Figure 2 As shown, UE 115-a may operate according to a first validity rule to perform a RACH timing verification procedure 210 to determine whether a given RO is valid. Therefore, UE 115-a may select a valid RO (e.g., according to the RACH timing verification procedure 210), during which UE 115-a may send a PRACH preamble 220. Additionally or alternatively, for a two-step RACH procedure, UE 115-a may operate according to a second validity rule to perform a PUSCH timing verification procedure 215 to determine whether a given PO is valid. Therefore, UE 115-a may select a valid PO (e.g., according to the PUSCH timing verification procedure 215), during which UE 115-a may send a data message 225 (e.g., PUSCH transmission).

[0128] In some examples, the RO is valid based on either an SBFD resource that exclusively spans the PRACH slot or a non-SBFD resource that exclusively spans the PRACH slot. Similar rules can be used to verify the PO for two-step RACH in some cases. (Reference) Figure 3A and Figure 3B Further discussion of this validity rule is described.

[0129] In some examples, a RO can be valid across both SBFD and non-SBFD resources if one or more conditions are met. Conditions may include that the SBFD and non-SBFD resources are directly adjacent in time (e.g., without time gaps), and that the RO across both SBFD and non-SBFD resources is associated with the same set of frequency resources, the same spatial configuration, and the same power control parameters. Similar rules can be used to verify the PO for a two-step RACH in some cases. (Reference) Figure 4A and Figure 4B Further discussion of this validity rule is described.

[0130] In some examples, when a guard period (e.g., a time gap) exists between SBFD and non-SBFD resources, the RO can be valid across both SBFD and non-SBFD resources. In the first example, UE 115-a can ignore the guard period and transmit the RACH preamble throughout the entire RO. In the second example, UE 115-a can discard the portion of the RACH preamble during the guard period, but transmit the portion of the RACH preamble during both SBFD and non-SBFD resource periods. In the third example, UE 115-a can discard the portion of the RACH preamble during the non-SBFD resource period and transmit exclusively during the SBFD resource period. In the fourth example, UE 115-a can discard the portion of the RACH preamble during the SBFD resource period and transmit exclusively during the non-SBFD resource period. In some cases, one or more similar rules can be used to verify the PO of a two-step RACH. Reference Figures 5A to 5D A discussion of such validity rules is described.

[0131] In some examples, the RO may include a set of sequence repetitions, where UE 115-a may transmit a RACH preamble during each sequence repetition. Therefore, if one of the sequence repetitions of the RO aligns with the boundary between SBFD and non-SBFD resources, the RO can be valid across both SBFD and non-SBFD resources. (Reference) Figure 6 The discussion of this validity rule is described.

[0132] Additionally or alternatively, UE 115-a may be configured with a second RO, which is a TDD-RO exclusively scheduled for non-SBFD resources. Therefore, an RO spanning both SBFD and non-SBFD resources can be effective based on how the RO overlaps with the second RO across time and frequency. (Reference) Figure 7 The discussion of this validity rule is described.

[0133] Figure 3A and Figure 3B Examples of transmission timing verification procedures 300-a and 300-b, respectively supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, are shown. Transmission timing verification procedures 300-a and 300-b may be implemented by or by aspects of wireless communication systems 100 and 200. For example, transmission timing verification procedures 300-a and 300-b may use techniques from RACH timing verification procedure 210, PUSCH timing verification procedure 215, or both. Additionally, the techniques described with reference to transmission timing verification procedures 300-a and 300-b may be performed by network entity 105, UE 115, or both.

[0134] For reference Figure 3A As illustrated, UE 115 may be configured with a transmission slot 305-a spanning a single slot including both SBFD portion 310 and non-SBFD portion 315. Therefore, SBFD portion 310 may include both uplink resource 320 and downlink resource 325, and the non-SBFD portion may include uplink resource 320 (e.g., or flexible resources configured for uplink use in other examples). Additionally, transmission slot 305-a may include multiple transmission times 330 (e.g., transmission times 330-a, 330-b, and 330-c).

[0135] In some cases, transmission slot 305-a can be a PRACH slot, where each of transmission opportunities 330-a, 330-b, and 330-c is a corresponding RO. When UE 115 is configured with an RO of type 1 RACH or type 2 RACH in a PRACH slot that spans both SBFD and non-SBFD resources, UE 115 can operate according to a first validity rule used to perform the RACH opportunity verification procedure 210. For example, the first validity rule can determine that a valid RO can exclusively span the same symbol type within a PRACH slot (e.g., a valid RO can exclusively span SBFD symbols or exclusively span non-SBFD symbols). That is, referencing Figure 3A Furthermore, according to the first validity rule, UE 115 and network entity 105 can determine that transmission timing 330-a is a valid RO based on SBFD symbols that exclusively span SBFD portion 310, determine that transmission timing 330-c is a valid RO based on non-SBFD symbols that exclusively span non-SBFD portion 315, and determine that transmission timing 330-b is not a valid RO based on symbols that span both SBFD portion 310 and non-SBFD portion 315. Therefore, UE 115 can choose to transmit the PRACH preamble during transmission timing 310-a or 310-c based on the validity of transmission timing 310-a or 310-c determined according to the first validity rule.

[0136] In some cases, transmission slot 305-a can be a PUSCH slot, where each of transmission opportunities 330-a, 330-b, and 330-c is a corresponding PO. When UE 115 is configured with a Type 2 RACH PO spanning both SBFD and non-SBFD resources in a PUSCH slot, UE 115 can operate according to a second validity rule used to perform the PUSCH opportunity verification procedure 215. For example, the second validity rule can determine that a valid PO can exclusively span the same symbol type within a PUSCH slot (e.g., a valid PO can exclusively span SBFD symbols or exclusively span non-SBFD symbols). That is, refer to Figure 3AFurthermore, according to the second validity rule, UE 115 and network entity 105 can determine that transmission timing 330-a is a valid PO based on SBFD symbols that exclusively span SBFD portion 310, determine that transmission timing 330-c is a valid PO based on non-SBFD symbols that exclusively span non-SBFD portion 315, and determine that transmission timing 330-b is not a valid PO based on symbols that span both SBFD portion 310 and non-SBFD portion 315. Therefore, UE 115 can select to transmit a data message during transmission timing 310-a or 310-c based on the validity of transmission timing 310-a or 310-c determined according to the second validity rule.

[0137] For reference Figure 3B As illustrated, UE 115 may be configured with a transmission slot 305-b spanning an SBFD slot 335 including SBFD symbols and a non-SBFD slot 340 spanning non-SBFD symbols. Therefore, SBFD slot 335 may include both uplink resource 320 and downlink resource 325, and non-SBFD slot 340 may include uplink resource 320 (e.g., or flexible resources configured for uplink in other examples). Additionally, transmission slot 305-b may include multiple transmission times 330 (e.g., transmission times 330-d, 330-f, and 330-e).

[0138] In some cases, transmission slot 305-b can be a PRACH slot, where each of transmission opportunities 330-d, 330-e, and 330-f is a corresponding RO. In such cases, UE 115 and network entity 105 can, according to reference... Figure 3A The first validity rule is described. That is, UE 115 and network entity 105 can determine that transmission timing 330-d is a valid RO based on SBFD symbols that exclusively span SBFD slot 335, determine that transmission timing 330-f is a valid RO based on non-SBFD symbols that exclusively span non-SBFD slot 340, and determine that transmission timing 330-e is not a valid RO based on symbols spanning both SBFD slot 335 and non-SBFD slot 340. Therefore, UE 115 can select to transmit the PRACH preamble during transmission timing 310-d or 310-f based on the validity of transmission timing 310-d or 310-f determined according to the first validity rule.

[0139] In some cases, transmission slot 305-b can be a PUSCH slot, where each of transmission opportunities 330-d, 330-e, and 330-f is a corresponding PO. In this case, UE 115 and network entity 105 can, according to reference... Figure 3BThe second validity rule described herein applies. That is, UE 115 and network entity 105 can determine that transmission timing 330-d is a valid PO based on SBFD symbols that exclusively span SBFD slot 335, determine that transmission timing 330-f is a valid PO based on non-SBFD symbols that exclusively span non-SBFD slot 340, and determine that transmission timing 330-e is not a valid PO based on symbols spanning both SBFD slot 335 and non-SBFD slot 340. Therefore, UE 115 can select to transmit a data message during transmission timing 310-d or 310-f based on the validity of transmission timing 310-d or 310-f determined according to the second validity rule.

[0140] Figure 4A and Figure 4B Examples of transmission timing verification procedures 400-a and 400-b, respectively supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, are shown. Transmission timing verification procedures 400-a and 400-b may be implemented by or by aspects of wireless communication systems 100 and 200. For example, transmission timing verification procedures 400-a and 400-b may use techniques from RACH timing verification procedure 210, PUSCH timing verification procedure 215, or both. Additionally, the techniques described with reference to transmission timing verification procedures 400-a and 400-b may be performed by network entity 105, UE 115, or both.

[0141] For reference Figure 4A As illustrated, UE 115 may be configured with a transmission time slot 405-a spanning a single time slot including both SBFD portion 410 and non-SBFD portion 415. Therefore, SBFD portion 410 may include both uplink resource 420 and downlink resource 425, and the non-SBFD portion may include uplink resource 420 (e.g., or a flexible resource configured for uplink in other examples). Additionally, transmission time slot 405-a may include transmission timing 430-a. Additionally or alternatively, the transmission time slot may include a time slot 445-a between SBFD portion 410 and non-SBFD portion 415.

[0142] In some cases, transmission slot 405-a may be a PRACH slot, where transmission timing 430-a is a RO. When UE 115 is configured with a Type 1 RACH or Type 2 RACH spanning both SBFD and non-SBFD resources, UE 115 may operate according to a first validity rule used to perform RACH timing verification procedure 210. For example, the first validity rule may determine a valid RO if one or more conditions are met. For example, one or more conditions may include time slot 445-a being equal to zero (e.g., no time slot between SBFD and non-SBFD symbols, including no change in TA), identical resource allocation for RO between SBFD portion 410 and non-SBFD portion 415 (e.g., identical narrow uplink resource allocation), identical spatial relationships between SBFD portion 410 and non-SBFD portion 415 (e.g., identical uplink beam or identical spatial relationship information configuration), identical power control parameters between SBFD portion 410 and non-SBFD portion 415 (e.g., identical uplink transmission parameters), or combinations thereof.

[0143] In some cases, transmission slot 405-a can be a PUSCH slot, where transmission timing 430-a is a PO. When UE 115 is configured with a PO for Type 2 RACH spanning both SBFD and non-SBFD resources, UE 115 can operate according to a second validity rule used to perform the PUSCH timing verification procedure 215. For example, the second validity rule can determine a valid PO if one or more conditions are met. For example, one or more conditions may include time slot 445-a being equal to zero (e.g., no time slot between SBFD and non-SBFD symbols, including no change in TA), identical resource allocation for RO between SBFD portion 410 and non-SBFD portion 415 (e.g., identical narrow uplink resource allocation), identical spatial relationships between SBFD portion 410 and non-SBFD portion 415 (e.g., identical uplink beam or identical spatial relationship information configuration), identical power control parameters between SBFD portion 410 and non-SBFD portion 415 (e.g., identical uplink transmission parameters), or combinations thereof.

[0144] For reference Figure 4BAs illustrated, UE 115 may be configured with a transmission slot 405-b spanning an SBFD slot 435 including SBFD symbols and a non-SBFD slot 440 spanning non-SBFD symbols. Therefore, SBFD slot 435 may include both uplink resource 420 and downlink resource 425, and non-SBFD slot 440 may include uplink resource 420 (e.g., or a flexible resource configured for uplink in other examples). Additionally, transmission slot 405-b may include transmission timing 430-b. Additionally or alternatively, the transmission slot may include a time gap 445-b between SBFD slot 435 and non-SBFD slot 440.

[0145] In some cases, transmission slot 405-b can be a PRACH slot, where transmission slot 430-b is RO. In such cases, UE 115 and network entity 105 can, according to reference... Figure 4A The first validity rule described is used for operation. That is, UE 115 and network entity 105 can operate based on whether RO meets the reference Figure 4A One or more conditions described determine when 430-b is a valid RO.

[0146] In some cases, transmission slot 405-b can be a PUSCH slot, where transmission slot 430-b is PO. In such cases, UE 115 and network entity 105 can, according to reference... Figure 4A The second validity rule described herein shall be used for operation. That is, UE 115 and network entity 105 may operate based on whether PO satisfies the reference... Figure 4A One or more conditions described determine the timing of transmission. 430-b is a valid PO.

[0147] Figures 5A to 5D Examples of transmission timing verification procedures 500-a, 500-b, 500-c, and 500-d, each supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, are shown respectively. Transmission timing verification procedures 500-a, 500-b, 500-c, and 500-d may be implemented by or be implemented by aspects of wireless communication systems 100 and 200. For example, transmission timing verification procedures 500-a, 500-b, 500-c, and 500-d may use techniques from RACH timing verification procedure 210, PUSCH timing verification procedure 215, or both. Additionally, the techniques described with reference to transmission timing verification procedures 500-a, 500-b, 500-c, and 500-d may be performed by network entity 105, UE 115, or both.

[0148] For reference Figures 5A to 5DAs illustrated, UE 115 can be configured with transmission slots 505 (e.g., transmission slots 505-a, 505-b, 505-c, and 505-d) spanning SBFD slots 510 (e.g., SBFD slots 510-a, 510-b, 510-c, and 510-d respectively) and non-SBFD slots 515 (e.g., non-SBFD slots 515-a, 515-b, 515-c, and 515-d respectively). As described herein, SBFD slot 510 may include both uplink resource 525 and downlink resource 530, and non-SBFD slot 515 may include uplink resource 525. Additionally, Figures 5A to 5D Each of these may include a protection period 520 between SBFD time slot 510 and non-SBFD time slot 515 (e.g., protection periods 520-a, 520-b, 520-c, and 520-d, respectively). Additionally, although Figures 5A to 5D Each is illustrated with its corresponding transmission slot 505 spanning SBFD slot 510 and non-SBFD slot 515; however, it should be understood that each transmission slot 505 may correspond to a single hybrid slot including both SBFD and non-SBFD portions (e.g., similar to reference). Figure 3A and Figure 4A (Example provided). Additionally, although... Figures 5A to 5D Examples are given of the SBFD portion that occurs before the interval 520 and the non-SBFD portion that occurs after the interval 520. However, it should be understood that the non-SBFD portion may occur before the interval 520 and the SBFD portion may occur after the interval 520.

[0149] Additionally, Figures 5A to 5D Each of these may include a transmission timing 535 spanning each of SBFD slot 510, guard period 520, and non-SBFD slot 515 (e.g., transmission timings 535-a, 535-b, 535-c, and 535-d, respectively). Additionally or alternatively, each transmission timing in transmission timing 535 may be an example of a valid RO (e.g., where transmission slot 505 is a PRACH slot) or a valid PO (e.g., where transmission slot 505 is a PUSCH slot). Therefore, Figures 5A to 5D Each illustrates a corresponding technique used by UE 115 to transmit during a valid transmission opportunity 535.

[0150] like Figure 5AAs shown, UE 115 can determine to ignore the guard period 520-a and transmit information during the span of transmission timing 535-a. For example, if transmission timing 535-a is a valid RO, UE 115 can transmit the PRACH preamble during SBFD slot 510-a, during the guard period 520-a, and during the non-SBFD slot 515-a. If transmission timing 535-a is a valid PO, UE 115 can transmit data messages during SBFD slot 510-a, during the guard period 520-a, and during the non-SBFD slot 515-a. In some examples, UE 115 can use the same set of transmission parameters (e.g., the same beam, the same transmit power, and the same frequency) across both SBFD and non-SBFD symbols of transmission timing 535-a.

[0151] like Figure 5B As illustrated, UE 115 can determine to discard a portion of the transmission at transmission timing 535-b. For example, if transmission timing 535-b is a valid RO, UE 115 can discard a portion of the PRACH preamble spanning the protection period (e.g., discarding portion 540-a). If transmission timing 535-b is a valid PO, UE 115 can discard a portion of the data message spanning the protection period (e.g., discarding portion 540-a). Therefore, UE 115 can resume transmission (e.g., the PRACH preamble or the data message) after the protection period. Figure 5B As illustrated, UE 115 may additionally change one or more transmission parameters associated with transmission timing 535-b before and after the protection period 520-b. For example, transmission timing 535-b may be associated with a first beam 545-a during SBFD time slot 510-b and with a second beam 545-b during non-SBFD time slot 515-b. Additionally or alternatively, transmission timing 535-b may be associated with a frequency span during SBFD time slot 510-b and with a second different frequency span during non-SBFD time slot 515-b. Additionally or alternatively, transmission timing 535-b may be associated with a first transmission power during SBFD time slot 510-b and with a second different transmission power during non-SBFD time slot 515-b.

[0152] like Figure 5CAs illustrated, UE 115 can determine to discard a portion of a transmission occurring after the protection period 520-c at transmission timing 535-c. For example, if transmission timing 535-c is a valid RO, UE 115 can discard a portion of the PRACH preamble occurring after the protection period 520-c (e.g., discarding portion 540-b). If transmission timing 535-c is a valid PO, UE 115 can discard a portion of the data message occurring after the protection period 520-c (e.g., discarding portion 540-b). In some cases, discarding portion 540-b may include the protection period 520-c (e.g., as...). Figure 5C (as shown), or alternatively, UE 115 may determine to transmit during the protection period 520-c.

[0153] like Figure 5D As illustrated, UE 115 can determine to discard a portion of the transmission occurring before the end of the protection period 520-d at transmission timing 535-d. For example, if transmission timing 535-c is a valid RO, UE 115 can discard a portion of the PRACH preamble occurring before the end of the protection period 520-c (e.g., discarding portion 540-c). If transmission timing 535-c is a valid PO, UE 115 can discard a portion of the data message occurring before the end of the protection period 520-c (e.g., discarding portion 540-c).

[0154] Figure 6 An example of a RACH timing verification process 600 supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown. The RACH timing verification process 600 may be implemented by or by aspects of wireless communication systems 100 and 200. For example, the RACH timing verification process 600 may use the techniques of RACH timing verification process 210. Additionally, the techniques described with reference to the RACH timing verification process 600 may be performed by network entity 105, UE 115, or both.

[0155] For reference Figure 6 As illustrated, UE 115 may be configured with an SBFD slot 610 spanning an SBFD symbol and a PRACH slot 605 spanning a non-SBFD slot 615 spanning a non-SBFD symbol. Therefore, SBFD slot 635 may include both uplink resource 620 and downlink resource 625, and non-SBFD slot 615 may include uplink resource 620 (e.g., or a flexible resource configured for uplink in other examples). Additionally, PRACH slot 605 may include RO 630. Additionally, although... Figure 6An example of a PRACH slot 605 spanning SBFD slot 610 and non-SBFD slot 615 is illustrated; however, it should be understood that PRACH slot 605 may correspond to a single hybrid slot including both SBFD and non-SBFD portions (e.g., similar to reference 1). Figure 3A and Figure 4A (Example provided). Additionally, although... Figure 6 The example illustrates that the SBFD portion occurs before the non-SBFD portion, but it should be understood that the non-SBFD portion may occur before the SBFD portion.

[0156] like Figure 6 As illustrated, the PRACH preamble associated with RO 630 can be configured with a set of sequence repetitions of 635. For example, Figure 6 Examples of PRACH preambles are shown, including sequence repetitions 635-a, 635-b, and 635-c spanning symbols in SBFD slot 610 and sequence repetitions 635-d, 635-e, and 635-f spanning symbols in non-SBFD slot 615. In some examples, a given sequence repetition 635 may include a set of information associated with the transmission of the PRACH preamble, wherein each sequence repetition 635 includes the same set of information. Including multiple sequence repetitions 635 in the RO timing increases the likelihood of successful PRACH preamble transmission from UE 115 to network entity 105.

[0157] When UE 115 is configured with an RO 630 comprising multiple sequence repeats 635 and spanning both SBFD and non-SBFD resources in a Type 1 or Type 2 RACH, UE 115 may operate according to a first validity rule used to perform the RACH timing verification procedure 600. For example, the first validity rule may determine that RO 630 is valid if the boundary between SBFD and non-SBFD symbols aligns with the start of a given sequence repeat. For example, resource type boundary 640 may be the boundary between the end of the SBFD resource establishing SBFD slot 610 and the start of the non-SBFD resource in non-SBFD slot 615 (e.g., and vice versa). Based on the alignment of the start of sequence repeat 635-d with resource type boundary 640, UE 115 and network entity 105 may determine that RO 630 is valid. Therefore, UE 115 may select to transmit a PRACH preamble during RO 630 based on the determination that RO 630 is valid according to the first validity rule.

[0158] Figure 7An example of a RACH timing verification process 700 supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown. The RACH timing verification process 700 may be implemented by or by aspects of wireless communication systems 100 and 200. For example, the RACH timing verification process 700 may use the techniques of RACH timing verification process 210. Additionally, the techniques described with reference to the RACH timing verification process 700 may be performed by network entity 105, UE 115, or both.

[0159] For reference Figure 7 As illustrated, UE 115 may be configured with an SBFD slot 710 spanning an SBFD symbol and a PRACH slot 705 spanning a non-SBFD slot 715 spanning a non-SBFD symbol. Therefore, the SBFD slot 710 may include both uplink resource 720 and downlink resource 725, and the non-SBFD slot 715 may include uplink resource 720 (e.g., or a flexible resource configured for uplink in other examples). Additionally, the PRACH slot 705 may include RO 730. Additionally, although... Figure 7 An example of a PRACH slot 705 spanning SBFD slot 710 and non-SBFD slot 715 is illustrated; however, it should be understood that PRACH slot 705 may correspond to a single hybrid slot including both SBFD and non-SBFD portions (e.g., similar to reference ). Figure 3A and Figure 4A (Example provided). Additionally, although... Figure 7 The example illustrates that the SBFD portion occurs before the non-SBFD portion, but it should be understood that the non-SBFD portion may occur before the SBFD portion.

[0160] like Figure 7 As illustrated, PRACH slot 705 may also include a TDD-RO 735 that exclusively spans a non-SBFD slot 715 across PRACH slot 705. Therefore, RO 730 and TDD-RO 735 may partially overlap in frequency, partially overlap in time, or both. When UE 115 is configured with RO 730 spanning both SBFD and non-SBFD resources for a Type 1 RACH or Type 2 RACH and is configured with TDD-RO 735, UE 115 may operate according to a first validity rule used to perform the RACH timing verification procedure 700.

[0161] In the first example, UE 115 determines that RO 730 is valid if it does not overlap with one or more OFDM symbols of TDD-RO 735 in non-SBFD slot 715. In the second example, UE 115 determines that RO 730 is valid if RO 730 and TDD-RO 735 overlap with one or more OFDM symbols and are mapped to the same SSB index (e.g., associated with the same SSB). In the third example, UE 115 determines that RO 730 is valid if a minimum frequency interval exists between RO 730 and TDD-RO 735. For example, RO 730 may be valid if RO 730 spans a first frequency bandwidth and TDD-RO 735 spans a second frequency bandwidth, where the frequency interval between the first and second frequency bandwidths is greater than a configured threshold (e.g., the configured threshold is met).

[0162] In some cases, UE 115 may use one of the techniques described with reference to the first, second, and third examples to determine the validity of RO 730. In some cases, UE 115 may use a combination of the techniques described with reference to the first, second, and third examples to determine the validity of RO 730. Additionally or alternatively, RO 730 may be part of a legacy PRACH configuration for verification at UE 115 or a dedicated SBFD PRACH at UE 115.

[0163] Figure 8 An example of a process flow 800 supporting random access authentication across multiple symbol types according to one or more aspects of this disclosure is shown. In some examples, process flow 800 may implement aspects of wireless communication system 100, wireless communication system 200, transmission timing verification processes 300-a to 500-d, and RACH timing verification processes 600 and 700. Process flow 800 may include UE 115-b and network entity 105-b, as referenced Figures 1 to 7 The following alternative examples can be implemented, some of which may be performed in a different order than described, or not at all. In some cases, steps may include additional features not mentioned below, or additional steps may be added. Furthermore, it should be understood that these processes can occur between any number of network devices and network device types.

[0164] At 805, UE 115-b can receive a configuration message that indicates to UE 115-b the set of ROs for performing the random access procedure.

[0165] At 810, UE 115-b can perform the RACH timing verification procedure (e.g., refer to...). Figure 2The RACH timing verification process 210). For example, UE 115-b may use a first validity rule that defines the validity of an RO when it is associated with a first slot (e.g., a PRACH slot) that spans one or more SBFD resources and one or more non-SBFD resources.

[0166] In some examples, according to the first validity rule, a valid RO is valid based on a valid RO exclusively spanning one or more SBFD resources in the first time slot or exclusively spanning one or more non-SBFD resources in the first time slot.

[0167] In some examples, a valid RO is valid if it spans one or more SBFD resources and one or more non-SBFD resources and satisfies one or more conditions. For example, according to the first validity rule, one or more conditions may include one or more SBFD resources and one or more non-SBFD resources being directly adjacent in time, and a valid RO spanning one or more SBFD resources and one or more non-SBFD resources being associated with the same set of frequency resources, the same spatial configuration, and the same power control parameters.

[0168] In some examples, a valid Return of Registry (RO) may include a set of sequence repeats. In such examples, a valid RO is based on the first validity rule, where a valid RO is a set of sequence repeats that are aligned with the boundary between one or more SBFD resources and one or more non-SBFD resources.

[0169] In some examples, the valid RO spans one or more SBFD resources and one or more non-SBFD resources, and UE 115-b is scheduled with a second RACH timing that exclusively spans one or more non-SBFD resources, wherein the second RACH timing may include a TDD-RO. In the first example, according to the first validity rule, the valid RO timing is valid based on the valid RO spanning one or more first symbols across the one or more non-SBFD resources, and the one or more first symbols do not overlap with one or more second symbols associated with the second RO. In the second example, according to the first validity rule, the valid RO is valid based on the valid RO and the second RO each mapping to the same SSB index. In the third example, according to the first validity rule, the valid RO is valid based on the valid RO being associated with a first frequency span and the second RO being associated with a second frequency span, wherein the frequency interval between the first frequency span and the second frequency span satisfies a threshold.

[0170] At 815, UE 115-b can perform a valid RO selection procedure. For example, UE 115-b can determine that multiple ROs in a PRACH slot are valid by performing a RACH timing verification procedure. Therefore, UE 115-b can select a valid RO from the set of RACH timings based on a first validity rule.

[0171] In some examples, the random access procedure can be a type 2 RACH, where the RACH configuration also configures UE 115-b with a set of POs. In such examples, UE 115-b can optionally perform aspects of 820 and 825.

[0172] At 820, UE 115-b can perform a PUSCH timing verification procedure, where a second validity rule defines the validity of a PO when it is associated with a second time slot (e.g., a PUSCH time slot) that spans one or more second SBFD resources and one or more second non-SBFD resources.

[0173] In some examples, the second validity rule defines the validity of a valid PO based on whether the valid PO exclusively spans one or more second SBFD resources in the second time slot or one or more second non-SBFD resources in the second time slot.

[0174] In some examples, the second validity rule defines the validity of a valid PO based on the fact that a valid PO spans one or more second SBFD resources and one or more second non-SBFD resources in a second time slot and meets one or more conditions. For example, one or more conditions may include that one or more second SBFD resources and one or more second non-SBFD resources are directly adjacent in time, and that the PUSCH timing spanning one or more second SBFD resources and one or more second non-SBFD resources in a second time slot is associated with the same set of frequency resources, the same spatial configuration, and the same power control parameters.

[0175] At 825, UE 115-b can perform a valid PO selection procedure. For example, UE 115-b can determine that multiple POs for a PUSCH slot are valid by performing a PUSCH timing verification procedure. Therefore, UE 115-b can select a valid PO from the set of PUSCH timings based on a second validity rule.

[0176] At 830, UE 115-b may send a PRACH preamble during a valid RO selected according to the first validity rule.

[0177] In some cases, the first time slot may include a protection period between one or more SBFD resources and one or more non-SBFD resources, wherein the effective RO spans the protection period, one or more SBFD resources, and one or more non-SBFD resources. In a first example, UE 115-b may transmit each portion of the PRACH preamble across the protection period, the one or more SBFD resources, and the one or more non-SBFD resources during the effective RO, wherein the PRACH preamble is associated with the same set of transmission parameters across the one or more SBFD resources and the one or more non-SBFD resources. In a second example, UE 115-b may discard a portion of the PRACH preamble across the protection period during the effective RO, wherein the PRACH preamble is associated with a first set of transmission parameters across the one or more SBFD resources and with a second set of transmission parameters across the one or more non-SBFD resources. In a third example, UE 115-b may transmit a first portion of the PRACH preamble associated with resources in the first time slot before the protection period and discard a second portion of the PRACH preamble associated with resources in the first time slot after the protection period. In this third example, UE 115-b can determine whether to send the third portion of the PRACH preamble associated with resources during the protection period or discard the third portion of the PRACH preamble. In the fourth example, UE 115-b can discard the first portion of the PRACH preamble associated with resources in the first time slot, spanning from the beginning of the first time slot to the end of the protection period, and send the second portion of the PRACH preamble associated with resources in the first time slot after the protection period.

[0178] At 835, UE 115-b may send data messages during a valid PO selected according to the second validity rule.

[0179] In some cases, the second time slot may include a second protection period between one or more second SBFD resources and one or more second non-SBFD resources, wherein the valid PO spans the second protection period, one or more second SBFD resources, and one or more second non-SBFD resources. In a first example, UE 115-b may transmit each portion of a data message spanning the second protection period, one or more second SBFD resources, and one or more second non-SBFD resources during the valid PO, wherein the data message is associated with the same set of transmission parameters across one or more second SBFD resources and one or more second non-SBFD resources. In a second example, UE 115-b may discard a portion of a data message spanning the second protection period during the valid PO, wherein the data message is associated with a first set of transmission parameters across one or more second SBFD resources and with a second set of transmission parameters across one or more second non-SBFD resources. In a third example, UE 115-b may transmit a first portion of a data message associated with resources in the second time slot prior to the second protection period and discard a second portion of the data message associated with resources in the second time slot after the second protection period. In this third example, UE 115-b can determine whether to send the third portion of the data message associated with resources during the second protection period or to discard the third portion of the data message. In the fourth example, UE 115-b can discard the first portion of the data message associated with resources in the second time slot, spanning from the beginning of the second time slot to the end of the second protection period, and send the second portion of the data message associated with resources in the second time slot after the second protection period.

[0180] Figure 9 A block diagram 900 of a device 905 supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown. Device 905 may be an example of various aspects of UE 115 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, communication manager 920), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0181] Receiver 910 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with random access authentication across multiple symbol types). The information may be delivered to other components of device 905. Receiver 910 may utilize a single antenna or a collection of antennas.

[0182] Transmitter 915 may provide components for transmitting signals generated by other components of device 905. For example, transmitter 915 may transmit information associated with various information channels, such as control channels, data channels, and information channels related to random access authentication across multiple symbol types, including packets, user data, control information, or any combination thereof. In some examples, transmitter 915 may be co-located with receiver 910 in a transceiver module. Transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0183] The communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be examples of components used to perform various aspects of random access authentication across multiple symbol types as described herein. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0184] In some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0185] Additionally or alternatively, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., referred to as processor executable code) (e.g., implemented as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0186] In some examples, the communication manager 920 may be configured to use a receiver 910, a transmitter 915, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0187] The communication manager 920 may support wireless communication according to examples disclosed herein. For example, the communication manager 920 may be able to, be configured to, or be operable to support components for: receiving a configuration message that indicates to the UE a set of multiple ROs for performing a random access procedure; the communication manager 920 may be able to, be configured to, or be operable to support components for: selecting a valid RO from the set of multiple ROs based on a first validity rule, wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources; and the communication manager 920 may be able to, be configured to, or be operable to support components for: transmitting a PRACH preamble during the valid RO selected according to the first validity rule.

[0188] By including or configuring a communication manager 920 according to an example as described herein, device 905 (e.g., controlling receiver 910, transmitter 915, communication manager 920 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reduced processing, reduced power consumption, and more efficient utilization of communication resources.

[0189] Figure 10 A block diagram 1000 of a device 1005 supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown. Device 1005 may be an example of aspects of device 905 or UE 115 as described herein. Device 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Device 1005, or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, communication manager 1020), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0190] Receiver 1010 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with random access authentication across multiple symbol types). The information may be delivered to other components of device 1005. Receiver 1010 may utilize a single antenna or a collection of antennas.

[0191] Transmitter 1015 may provide components for transmitting signals generated by other components of device 1005. For example, transmitter 1015 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with random access authentication across multiple symbol types), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 1015 may be co-located with receiver 1010 in a transceiver module. Transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0192] Device 1005 or its various components may be examples of parts for performing various aspects of random access authentication across multiple symbol types as described herein. For example, communication manager 1020 may include message monitoring component 1025, RO selection component 1030, preamble transmission component 1035, or any combination thereof. Communication manager 1020 may be examples of aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use receiver 1010, transmitter 1015, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or integrate in combination with receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0193] Communication manager 1020 may support wireless communication according to examples disclosed herein. Message monitoring component 1025 is capable of, configured to, or operable to support components for receiving configuration messages that indicate to the UE a set of multiple ROs for performing a random access procedure. RO selection component 1030 is capable of, configured to, or operable to support components for selecting a valid RO from the set of multiple ROs based on a first validity rule, wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources. Preamble transmission component 1035 is capable of, configured to, or operable to support components for transmitting a PRACH preamble during the valid RO selected according to the first validity rule.

[0194] Figure 11 A block diagram 1100 of a communication manager 1120 supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown. The communication manager 1120 may be an example of a communication manager 920, a communication manager 1020, or aspects thereof as described herein. The communication manager 1120 or its various components may be examples of parts for performing various aspects of random access authentication across multiple symbol types as described herein. For example, the communication manager 1120 may include a message monitoring component 1125, an RO selection component 1130, a preamble transmission component 1135, a PUSCH timing selection component 1140, a data transmission component 1145, a preamble transmission component 1150, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0195] Communication manager 1120 may support wireless communication according to examples disclosed herein. Message monitoring component 1125 is capable of, configured to, or operable to support components for receiving configuration messages that indicate to the UE a set of multiple ROs for performing a random access procedure. RO selection component 1130 is capable of, configured to, or operable to support components for selecting a valid RO from the set of multiple ROs based on a first validity rule, wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources. Preamble transmission component 1135 is capable of, configured to, or operable to support components for transmitting a PRACH preamble during the selection of the valid RO according to the first validity rule.

[0196] In some examples, according to the first validity rule, a valid RO is valid based on a valid RO exclusively spanning one or more SBFD resources in the first time slot or exclusively spanning one or more non-SBFD resources in the first time slot.

[0197] In some examples, a valid RO is defined as a valid RO spanning one or more SBFD resources and one or more non-SBFD resources. In some examples, one or more SBFD resources and one or more non-SBFD resources are directly adjacent in time. In some examples, according to the first validity rule, a valid RO spanning one or more SBFD resources and one or more non-SBFD resources is associated with the same set of multiple frequency resources, the same spatial configuration, and the same power control parameters.

[0198] In some examples, the first time slot includes a protection period between one or more SBFD resources and one or more non-SBFD resources, and the effective RO spans the protection period, one or more SBFD resources, and one or more non-SBFD resources.

[0199] In some examples, the preamble transmission component 1150 is capable of, configured to, or able to operate to support components for transmitting each portion of the PRACH preamble across the protection period, the one or more SBFD resources, and the one or more non-SBFD resources during the active RO, wherein the PRACH preamble across the one or more SBFD resources and the one or more non-SBFD resources is associated with the same set of transmission parameters.

[0200] In some examples, the preamble transmission component 1150 is capable of, configured to, or able to operate to support components for: discarding a portion of the PRACH preamble across the protection period during the valid RO, wherein the PRACH preamble is associated with a first set of transmission parameters across the one or more SBFD resources and with a second set of transmission parameters across the one or more non-SBFD resources.

[0201] In some examples, the preamble transmission component 1150 is capable of, configured to, or operable to support components for transmitting a first portion of the PRACH preamble associated with one or more SBFD resources in the first time slot prior to the protection period. In some examples, the preamble transmission component 1150 is capable of, configured to, or operable to support components for discarding a second portion of the PRACH preamble associated with one or more non-SBFD resources in the first time slot after the protection period.

[0202] In some examples, the preamble sending component 1150 is capable of, configured to, or able to operate to support components for sending a third portion of the PRACH preamble associated with resources during the protection period.

[0203] In some examples, the preamble transmission component 1150 is capable of, configured to, or operable to support components for: discarding a first portion of the PRACH preamble associated with the one or more SBFD resources of the first time slot, spanning from the beginning of the first time slot to the end of the protection period. In some examples, the preamble transmission component 1150 is capable of, configured to, or operable to support components for: transmitting a second portion of the PRACH preamble associated with the one or more non-SBFD resources of the first time slot after the protection period.

[0204] In some examples, a valid Return of Principle (RO) comprises a set of multiple sequence repeats. In some examples, according to the first validity rule, a valid RO is based on the validity of sequence repeats within the set of multiple sequence repeats that are aligned to the boundary between one or more SBFD resources and one or more non-SBFD resources.

[0205] In some examples, the effective RO spans one or more SBFD resources and one or more non-SBFD resources. In some examples, the UE is configured with a second RO that exclusively spans one or more non-SBFD resources, which includes a time-division duplex RO.

[0206] In some examples, according to the first validity rule, the validity RO timing is based on the fact that the validity RO is valid across one or more non-SBFD resources across one or more first symbols, and that one or more first symbols do not overlap with one or more second symbols associated with the second RO.

[0207] In some examples, according to the first validity rule, the valid RO is valid based on the fact that the valid RO and the second RO are each mapped to the same synchronization signal block index.

[0208] In some examples, the valid RO is valid based on the fact that the valid RO is associated with a first frequency span and the second RO is associated with a second frequency span. In some examples, the frequency interval between the first frequency span and the second frequency span meets a threshold according to the first validity rule.

[0209] In some examples, the random access procedure is a two-step random access procedure, and the PUSCH timing selection component 1140 is capable of, configured to, or operable to support components for selecting a valid PUSCH timing from a set of multiple PUSCH timings based on a second validity rule, wherein the second validity rule defines the validity of a PUSCH timing when it is associated with a second time slot spanning one or more second SBFD resources and one or more second non-SBFD resources. In some examples, the random access procedure is a two-step random access procedure, and the data transmission component 1145 is capable of, configured to, or operable to support components for transmitting data messages during a valid PUSCH timing selected according to the second validity rule.

[0210] In some examples, the second validity rule defines the validity of a valid PUSCH timing based on whether the valid PUSCH timing exclusively spans one or more second SBFD resources in the second time slot or exclusively spans one or more second non-SBFD resources in the second time slot.

[0211] In some examples, the second validity rule defines the validity of the valid PUSCH timing based on the one or more second SBFD resources and the one or more second non-SBFD resources spanning the second time slot. In some examples, the one or more second SBFD resources and the one or more second non-SBFD resources are directly adjacent in time. In some examples, the one or more second SBFD resources and the one or more second non-SBFD resources spanning the second time slot are associated with the same set of multiple frequency resources, the same spatial configuration, and the same power control parameters.

[0212] In some examples, the second time slot includes a second protection period between the one or more second SBFD resources and the one or more second non-SBFD resources, and the effective PUSCH timing spans the second protection period, the one or more second SBFD resources, and the one or more second non-SBFD resources.

[0213] In some examples, the data transmission component 1145 is capable of, configured to, or able to operate to support components for transmitting data messages across each of a second protection period, one or more second SBFD resources, and one or more second non-SBFD resources during a valid PUSCH timing, wherein the data messages are associated with the same set of transmission parameters across one or more second SBFD resources and one or more second non-SBFD resources.

[0214] In some examples, the data transmission component 1145 is capable of, configured to, or able to operate to support components for: discarding a portion of a data message spanning a second protection period during a valid PUSCH timing, wherein the data message is associated with a first transmission parameter set across one or more second SBFD resources and with a second transmission parameter set across one or more second non-SBFD resources.

[0215] In some examples, the data transmission component 1145 is capable of, configured to, or able to operate to support components for: transmitting a first portion of the data message associated with the one or more second SBFD resources in the second time slot prior to the second protection period. In some examples, the data transmission component 1145 is capable of, configured to, or able to operate to support components for: discarding a second portion of the data message associated with the one or more second non-SBFD resources in the second time slot after the second protection period.

[0216] In some examples, the data transmission component 1145 is capable of, configured to, or able to operate to support components for transmitting a third portion of the data message associated with the resources during the second protection period.

[0217] In some examples, the data transmission component 1145 is capable of, configured to, or able to operate to support components for: discarding a first portion of the data message associated with the one or more second SBFD resources of the second time slot, spanning from the beginning of the second time slot to the end of the second protection period. In some examples, the data transmission component 1145 is capable of, configured to, or able to operate to support components for: transmitting a second portion of the data message associated with the one or more second non-SBFD resources of the second time slot after the second protection period.

[0218] Figure 12 A diagram of a system 1200 including device 1205 supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of device 905, device 1005, or UE 115 as described herein, or may include components thereof. Device 1205 may communicate with one or more other devices (e.g., network entity 105, UE 115, or a combination thereof) (e.g., wirelessly). Device 1205 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1220, an input / output (I / O) controller (e.g., I / O controller 1210), a transceiver 1215, one or more antennas 1225, at least one memory 1230, code 1235, and at least one processor 1240. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1245).

[0219] I / O controller 1210 manages the input and output signals of device 1205. I / O controller 1210 can also manage peripheral devices not integrated into device 1205. In some cases, I / O controller 1210 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1210 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ®Alternatively, the I / O controller 1210 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1210 may be implemented as part of one or more processors, such as at least one processor 1240. In some cases, a user may interact with the device 1205 via the I / O controller 1210 or via hardware components controlled by the I / O controller 1210.

[0220] In some cases, device 1205 may include a single antenna. However, in other cases, device 1205 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1215 may communicate bidirectionally via one or more antennas 1225 as described herein using a wired or wireless link. For example, transceiver 1215 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1215 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1225 for transmission; and demodulating packets received from one or more antennas 1225. Transceiver 1215, or transceiver 1215 and one or more antennas 1225, may be an example of transmitter 915, transmitter 1015, receiver 910, receiver 1010, or any combination thereof or components thereof as described herein.

[0221] At least one memory 1230 may include random access memory (RAM) and read-only memory (ROM). At least one memory 1230 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1235. Code 1235 may include instructions that, when executed by at least one processor 1240, cause device 1205 to perform the various functions described herein. Code 1235 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1235 may not be directly executable by at least one processor 1240, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1230 may include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0222] At least one processor 1240 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 1240 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 1240. At least one processor 1240 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1230) to cause device 1205 to perform various functions (e.g., various functions or tasks supporting random access authentication across multiple symbol types). For example, device 1205 or components thereof may include at least one processor 1240 and at least one memory 1230 coupled to or coupled to the at least one processor 1240, the at least one processor 1240 and the at least one memory 1230 being configured to perform the various functions described herein.

[0223] In some examples, at least one processor 1240 may include multiple processors, and at least one memory 1230 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1240 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1240) and memory circuitry (which may include at least one memory 1230)) or components that receive or obtain input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1240 or a processing system including at least one processor 1240 may be configured, capable of being configured, or operable to cause device 1205 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code 1235 (e.g., processor-executable code) stored in at least one memory 1230 or otherwise.

[0224] The communication manager 1220 may support wireless communication according to examples disclosed herein. For example, the communication manager 1220 may be able to support components for: receiving a configuration message that indicates to the UE a set of multiple ROs for performing a random access procedure; the communication manager 1220 may be able to support components for: selecting a valid RO from the set of multiple ROs based on a first validity rule, wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources; and the communication manager 1220 may be able to support components for: transmitting a PRACH preamble during the valid RO selected according to the first validity rule.

[0225] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 can support techniques for improving communication reliability, reducing latency, improving and reducing user experience related to processing, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, and improving the utilization of processing power.

[0226] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using transceiver 1215, one or more antennas 1225, or any combination thereof, or otherwise cooperating with them. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or executed by at least one processor 1240, at least one memory 1230, code 1235, or any combination thereof. For example, code 1235 may include instructions that can be executed by at least one processor 1240 to cause device 1205 to perform various aspects of random access authentication across multiple symbol types as described herein, or at least one processor 1240 and at least one memory 1230 may be otherwise configured to perform or support such operations individually or jointly.

[0227] Figure 13A block diagram 1300 of a device 1305 supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown. Device 1305 may be an example of aspects of network entity 105 as described herein. Device 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. Device 1305, or one or more components of device 1305 (e.g., receiver 1310, transmitter 1315, communication manager 1320), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0228] Receiver 1310 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be delivered to other components of device 1305. In some examples, receiver 1310 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1310 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0229] Transmitter 1315 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1305. For example, transmitter 1315 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1315 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1315 and receiver 1310 may be co-located in a transceiver, which may include or be coupled to a modem.

[0230] The communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be examples of components used to perform various aspects of random access authentication across multiple symbol types as described herein. For example, the communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0231] In some examples, the communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0232] Additionally or alternatively, the communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., referred to as processor executable code) (e.g., implemented as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 1320, receiver 1310, transmitter 1315, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0233] In some examples, the communication manager 1320 may be configured to use a receiver 1310, a transmitter 1315, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1320 may receive information from the receiver 1310, transmit information to the transmitter 1315, or be integrated in combination with the receiver 1310, the transmitter 1315, or both to acquire information, output information, or perform various other operations as described herein.

[0234] The communication manager 1320 may support wireless communication according to examples disclosed herein. For example, the communication manager 1320 may be, configured to, or operable to support components for: sending a configuration message indicating to the UE a set of multiple ROs for performing a random access procedure. The communication manager 1320 may be, configured to, or operable to support components for: receiving a PRACH preamble during a valid RO in the set of multiple ROs, wherein the valid RO is based on a first validity rule, and wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources.

[0235] By including or configuring a communication manager 1320 according to an example as described herein, device 1305 (e.g., controlling receiver 1310, transmitter 1315, communication manager 1320, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for reduced processing, reduced power consumption, and more efficient utilization of communication resources.

[0236] Figure 14 A block diagram 1400 of a device 1405 supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown. Device 1405 may be an example of aspects of device 1305 or network entity 105 as described herein. Device 1405 may include a receiver 1410, a transmitter 1415, and a communication manager 1420. Device 1405, or one or more components of device 1405 (e.g., receiver 1410, transmitter 1415, communication manager 1420), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0237] Receiver 1410 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be delivered to other components of device 1405. In some examples, receiver 1410 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1410 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0238] Transmitter 1415 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1405. For example, transmitter 1415 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1415 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1415 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1415 and receiver 1410 may be co-located in a transceiver, which may include or be coupled to a modem.

[0239] Device 1405 or its various components may be examples of parts for performing various aspects of random access authentication across multiple symbol types as described herein. For example, communication manager 1420 may include message sending component 1425, preamble monitoring component 1430, or any combination thereof. Communication manager 1420 may be examples of aspects of communication manager 1320 as described herein. In some examples, communication manager 1420 or its various components may be configured to use receiver 1410, transmitter 1415, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1420 may receive information from receiver 1410, transmit information to transmitter 1415, or be integrated in combination with receiver 1410, transmitter 1415, or both to acquire information, output information, or perform various other operations as described herein.

[0240] Communication manager 1420 may support wireless communication according to examples disclosed herein. Message transmission component 1425 is capable of, configured to, or able to operate to support components for: transmitting a configuration message that indicates to the UE a set of multiple ROs for performing a random access procedure. Preamble monitoring component 1430 is capable of, configured to, or able to operate to support components for: receiving a PRACH preamble during a valid RO in the set of multiple ROs, wherein the valid RO is based on a first validity rule, and wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources.

[0241] Figure 15A block diagram 1500 is shown of a communication manager 1520 supporting random access authentication across multiple symbol types according to one or more aspects of this disclosure. The communication manager 1520 may be an example of aspects of the communication manager 1320, communication manager 1420, or both as described herein. The communication manager 1520 or its various components may be examples of components for performing various aspects of random access authentication across multiple symbol types as described herein. For example, the communication manager 1520 may include a message sending component 1525, a preamble detection component 1530, a data detection component 1535, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses). Communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0242] Communication manager 1520 may support wireless communication according to examples disclosed herein. Message transmission component 1525 is capable of, configured to, or able to operate to support components for transmitting a configuration message that indicates to the UE a set of multiple ROs for performing a random access procedure. Preamble monitoring component 1530 is capable of, configured to, or able to operate to support components for receiving a PRACH preamble during a valid RO in the set of multiple ROs, wherein the valid RO is based on a first validity rule, and wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources.

[0243] In some examples, according to the first validity rule, a valid RO is valid based on a valid RO exclusively spanning one or more SBFD resources in the first time slot or exclusively spanning one or more non-SBFD resources in the first time slot.

[0244] In some examples, a valid RO is defined as a valid RO spanning one or more SBFD resources and one or more non-SBFD resources. In some examples, one or more SBFD resources and one or more non-SBFD resources are directly adjacent in time. In some examples, according to the first validity rule, a valid RO spanning one or more SBFD resources and one or more non-SBFD resources is associated with the same set of multiple frequency resources, the same spatial configuration, and the same power control parameters.

[0245] In some examples, the first time slot includes a protection period between one or more SBFD resources and one or more non-SBFD resources, and the effective RO spans the protection period, one or more SBFD resources, and one or more non-SBFD resources.

[0246] In some examples, the preamble monitoring component 1530 is capable of, configured to, or able to operate to support components for receiving, during the effective RO, each portion of the PRACH preamble across the protection period, the one or more SBFD resources, and the one or more non-SBFD resources, wherein the PRACH preamble across the one or more SBFD resources and the one or more non-SBFD resources is associated with the same set of transmission parameters.

[0247] In some examples, the preamble monitoring component 1530 is capable of, configured to, or able to operate to support components for receiving the first portion of the PRACH preamble associated with one or more SBFD resources in the first time slot prior to the protection period.

[0248] In some examples, the preamble monitoring component 1530 is capable of, configured to, or able to operate to support components for receiving the second portion of the PRACH preamble associated with resources during the protection period.

[0249] In some examples, the preamble monitoring component 1530 is capable of, configured to, or able to operate to support components for receiving the PRACH preamble and associated with one or more non-SBFD resources in the first time slot after the protection period.

[0250] In some examples, a valid Return of Principle (RO) comprises a set of multiple sequence repeats. In some examples, according to the first validity rule, a valid RO is based on the validity of sequence repeats within the set of multiple sequence repeats that are aligned to the boundary between one or more SBFD resources and one or more non-SBFD resources.

[0251] In some examples, the effective RO spans one or more SBFD resources and one or more non-SBFD resources. In some examples, the UE is scheduled with a second RO that exclusively spans one or more non-SBFD resources, which includes a time-division duplex RO.

[0252] In some examples, according to the first validity rule, the validity RO timing is based on the fact that the validity RO is valid across one or more non-SBFD resources across one or more first symbols, and that one or more first symbols do not overlap with one or more second symbols associated with the second RO.

[0253] In some examples, according to the first validity rule, the valid RO is valid based on the fact that the valid RO and the second RO are each mapped to the same synchronization signal block index.

[0254] In some examples, the valid RO is valid based on the fact that the valid RO is associated with a first frequency span and the second RO is associated with a second frequency span. In some examples, the frequency interval between the first frequency span and the second frequency span meets a threshold according to the first validity rule.

[0255] In some examples, the random access procedure is a two-step random access procedure, and the data monitoring component 1535 is capable of, configured to, or able to operate to support components for receiving data messages during valid PUSCH times in a set of multiple PUSCH times, wherein the valid PUSCH times are based on a second validity rule, wherein the second validity rule defines the validity of a PUSCH time when it is associated with a second time slot spanning one or more second SBFD resources and one or more second non-SBFD resources.

[0256] In some examples, the second validity rule defines the validity of a valid PUSCH timing based on whether the valid PUSCH timing exclusively spans one or more second SBFD resources in the second time slot or exclusively spans one or more second non-SBFD resources in the second time slot.

[0257] In some examples, the second validity rule defines the validity of the valid PUSCH timing based on the one or more second SBFD resources and the one or more second non-SBFD resources spanning the second time slot. In some examples, the one or more second SBFD resources and the one or more second non-SBFD resources are directly adjacent in time. In some examples, the one or more second SBFD resources and the one or more second non-SBFD resources spanning the second time slot are associated with the same set of multiple frequency resources, the same spatial configuration, and the same power control parameters.

[0258] In some examples, the second time slot includes a second protection period between the one or more second SBFD resources and the one or more second non-SBFD resources, and the effective PUSCH timing spans the second protection period, the one or more second SBFD resources, and the one or more second non-SBFD resources.

[0259] In some examples, the data monitoring component 1535 is capable of, configured to, or able to operate to support components for receiving data messages across each of a second protection period, one or more second SBFD resources, and one or more second non-SBFD resources during a valid PUSCH timing, wherein the data messages are associated with the same set of transmission parameters across one or more second SBFD resources and one or more second non-SBFD resources.

[0260] In some examples, the data monitoring component 1535 is capable of, configured to, or able to operate to support components for receiving the data message in connection with one or more second SBFD resources in the second time slot prior to the second protection period.

[0261] In some examples, the data monitoring component 1535 is capable of, configured to, or able to operate to support components for receiving the data message in connection with a second portion of the resource during the second protection period.

[0262] In some examples, the data monitoring component 1535 is capable of, configured to, or able to operate to support components for receiving the data message associated with one or more second non-SBFD resources in the second time slot after the second protection period.

[0263] Figure 16 A diagram of a system 1600 including device 1605 supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown. Device 1605 may be an example of device 1305, device 1405, or network entity 105 as described herein, or may include components thereof. Device 1605 may communicate with other network devices or network equipment, such as network entity 105, UE 115, or any combination thereof. Communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1605 may include components supporting output and acquisition of communication, such as a communication manager 1620, a transceiver 1610, one or more antennas 1615, at least one memory 1625, code 1630, and at least one processor 1635. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1640).

[0264] Transceiver 1610 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1610 may include a wired transceiver and be able to communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1610 may include a wireless transceiver and be able to communicate bidirectionally with another wireless transceiver. In some examples, device 1605 may include one or more antennas 1615 that may be able to transmit or receive wireless transmissions (e.g., concurrently). Transceiver 1610 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1615, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1615, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1610 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1615 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1615 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1610 may include one or more processors or one or more memory components, or be configured to couple to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1610, or transceiver 1610 and one or more antennas 1615, or transceiver 1610 and one or more antennas 1615 and one or more processors or one or more memory components (e.g., at least one processor 1635, at least one memory 1625, or both), may be included in a chip or chip assembly mounted in device 1605. In some examples, transceiver 1610 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0265] At least one memory 1625 may include RAM, ROM, or any combination thereof. At least one memory 1625 may store computer-readable code, computer-executable code, or processor-executable code, such as code 1630. Code 1630 may include instructions that, when executed by one or more of the at least one processor 1635, cause the device 1605 to perform the various functions described herein. Code 1630 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1630 may not be directly executable by one of the at least one processor 1635, but may enable the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1625 may include a BIOS, etc., which controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1635 may include multiple processors, and at least one memory 1625 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0266] At least one processor 1635 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 1635 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1635. At least one processor 1635 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1625) to cause device 1605 to perform various functions (e.g., various functions or tasks supporting random access authentication across multiple symbol types). For example, device 1605 or components thereof may include at least one processor 1635 and at least one memory 1625 coupled to one or more processors in the at least one processor 1635, the at least one processor 1635 and the at least one memory 1625 being configured to perform the various functions described herein. The at least one processor 1635 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functions (e.g., by executing code 1630) to perform the functions of device 1605. The at least one processor 1635 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1605 (such as within one or more memories of the at least one memory 1625).

[0267] In some examples, at least one processor 1635 may include multiple processors, and at least one memory 1625 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1635 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1635) and memory circuitry (which may include at least one memory 1625)) or components that receive or obtain input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1635 or a processing system including at least one processor 1635 may be configured, capable of being configured, or operable to cause device 1605 to perform one or more of the functions described herein. Furthermore, as described herein, “configurable to,” “configurable to,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1625 or otherwise.

[0268] In some examples, bus 1640 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1640 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1605, or communication performed between different components of device 1605 that are co-addressable or may be located in different locations (e.g., where device 1605 may refer to a system in which one or more of communication manager 1620, transceiver 1610, at least one memory 1625, code 1630 and at least one processor 1635 may be located in one component of different components or partitioned between different components).

[0269] In some examples, the communication manager 1620 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1620 can manage the delivery of data communications by client devices such as one or more UEs 115. In some examples, the communication manager 1620 can manage communication with one or more other network entities 105 and may include a controller or scheduler for (e.g., cooperating with one or more other network devices) controlling communication with UE 115. In some examples, the communication manager 1620 may support the X2 interface in LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0270] The communication manager 1620 may support wireless communication according to examples disclosed herein. For example, the communication manager 1620 is capable of, configured to, or able to operate to support components for: sending a configuration message that indicates to the UE a set of multiple ROs for performing a random access procedure. The communication manager 1620 is capable of, configured to, or able to operate to support components for: receiving a PRACH preamble during a valid RO in the set of multiple ROs, wherein the valid RO is based on a first validity rule, and wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources.

[0271] By including or configuring a communication manager 1620 according to an example as described herein, device 1605 can support techniques for improving communication reliability, reducing latency, improving and reducing user experience related to processing, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, and improving the utilization of processing power.

[0272] In some examples, the communication manager 1620 may be configured to use or otherwise cooperate with transceiver 1610, one or more antennas 1615 (e.g., where applicable) or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1620 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1620 may be supported or performed by transceiver 1610, one or more processors in at least one processor 1635, one or more memories in at least one memory 1625, code 1630, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1635, at least one memory 1625, code 1630, or any combination thereof). For example, code 1630 may include instructions that can be executed by one or more processors of at least one processor 1635 to cause device 1605 to perform various aspects of random access authentication across multiple symbol types as described herein, or at least one processor 1635 and at least one memory 1625 may be otherwise configured to perform or support such operations individually or jointly.

[0273] Figure 17 A flowchart illustrating a method 1700 for supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown. Operation of method 1700 can be implemented by a UE or its components as described herein. For example, operation of method 1700 can be performed by, as referenced... Figures 1 to 12The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0274] At 1705, the method may include receiving a configuration message that indicates to the UE a set of multiple Remote Routers (ROs) for performing the random access procedure. The operation of 1705 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1705 may be provided by reference to [reference needed]. Figure 11 The described message monitoring component 1125 is executed.

[0275] At 1710, the method may include selecting a valid RO from a set of multiple ROs based on a first validity rule, wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources. The operation of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1710 may be derived from references... Figure 11 The RO selection component 1130 is described to perform this action.

[0276] At 1715, the method may include sending a PRACH preamble during a valid RO selected according to a first validity rule. The operation at 1715 may be performed according to examples disclosed herein. In some examples, aspects of the operation at 1715 may be derived from references... Figure 11 The preamble sending component 1135 described herein performs this action.

[0277] Figure 18 A flowchart illustrating a method 1800 for supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown. Operation of method 1800 can be implemented by a UE or its components as described herein. For example, operation of method 1800 can be performed by, as referenced... Figures 1 to 12 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0278] At 1805, the method may include receiving a configuration message that indicates to the UE a set of multiple Remote Routers (ROs) for performing the random access procedure. The operation of 1805 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1805 may be provided by reference to [reference needed]. Figure 11 The described message monitoring component 1125 is executed.

[0279] At 1810, the method may include selecting a valid RO from a set of multiple ROs based on a first validity rule, wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources. The operation of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1810 may be derived from references... Figure 11 The RO selection component 1130 is described to perform this action.

[0280] At 1815, the method may include sending a PRACH preamble during a valid RO selected according to a first validity rule. The operation at 1815 may be performed according to examples disclosed herein. In some examples, aspects of the operation at 1815 may be derived from references... Figure 11 The preamble sending component 1135 described herein performs this action.

[0281] At 1820, the method may include selecting a valid PUSCH timing from a set of multiple PUSCH timings based on a second validity rule, wherein the second validity rule defines the validity of a PUSCH timing when it is associated with a second time slot spanning one or more second SBFD resources and one or more second non-SBFD resources. The operation of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1820 may be derived from references... Figure 11 The described PUSCH timing selection component 1140 is used to perform this.

[0282] In 1825, the method may include sending a data message during a valid PUSCH timing selected according to a second validity rule. The operation of 1825 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1825 may be derived from references... Figure 11 The data sending component 1145 described herein shall perform this action.

[0283] Figure 19 A flowchart illustrating a method 1900 for supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown. Operation of method 1900 may be implemented by a network entity or its components as described herein. For example, operation of method 1900 may be implemented by, as referenced... Figures 1 to 8 as well as Figures 13 to 16 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0284] At 1905, the method may include sending a configuration message indicating to the UE a set of multiple Remote Routers (ROs) for performing the random access procedure. The operation at 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1905 may be provided by reference to [reference needed]. Figure 15 The message sending component 1525 described herein shall be used to perform this action.

[0285] At 1910, the method may include receiving a PRACH preamble during a valid RO in the set of plurality of ROs, wherein the valid RO is based on a first validity rule, and wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources. The operation of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1910 may be derived from references... Figure 15 The preamble monitoring component 1530 described herein is used to perform this.

[0286] Figure 20 A flowchart illustrating a method 2000 for supporting random access authentication across multiple symbol types, according to one or more aspects of this disclosure, is shown. The operation of method 2000 may be implemented by a network entity or its components as described herein. For example, the operation of method 2000 may be implemented by, as referenced... Figures 1 to 8 as well as Figures 13 to 16 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0287] At 2005, the method may include sending a configuration message that indicates to the UE a set of multiple ROs for performing the random access procedure. Operation of 2005 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2005 may be provided by reference to [reference needed]. Figure 15 The message sending component 1525 described herein shall be used to perform this action.

[0288] At 2010, the method may include receiving a PRACH preamble during a valid RO in a set of plurality of ROs, wherein the valid RO is based on a first validity rule, and wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources. Operation of 2010 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2010 may be derived from references... Figure 15 The preamble monitoring component 1530 described herein is used to perform this.

[0289] At 2015, the method may include receiving a data message during a valid PUSCH timeout from a set of multiple PUSCH timeouts, wherein the valid PUSCH timeout is based on a second validity rule, wherein the second validity rule defines the validity of the PUSCH timeout when it is associated with a second time slot spanning one or more second SBFD resources and one or more second non-SBFD resources. The operation of 2015 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2015 may be derived from references... Figure 15 The data monitoring component 1535 described is used to perform this.

[0290] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a configuration message indicating to the UE a plurality of Remote Routers (ROs) for performing a random access procedure; selecting a valid RO from the plurality of ROs based at least in part on a first validity rule, wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources; and transmitting a PRACH preamble during the period of the valid RO selected according to the first validity rule.

[0291] Aspect 2: According to the method of aspect 1, wherein, according to the first validity rule, the valid RO is valid at least in part based on the valid RO exclusively spanning the one or more SBFD resources of the first time slot or exclusively spanning the one or more non-SBFD resources of the first time slot.

[0292] Aspect 3: The method according to any one of Aspects 1 to 2, wherein, according to the first validity rule, the valid RO is at least partially based on the fact that the valid RO is valid across the one or more SBFD resources and the one or more non-SBFD resources, the one or more SBFD resources and the one or more non-SBFD resources are directly adjacent in time, and the valid RO across the one or more SBFD resources and the one or more non-SBFD resources is associated with the same plurality of frequency resources, the same spatial configuration and the same power control parameters.

[0293] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the first time slot includes a protection period between the one or more SBFD resources and the one or more non-SBFD resources, and the effective RO spans the protection period, the one or more SBFD resources and the one or more non-SBFD resources.

[0294] Aspect 5: According to the method of aspect 4, the method further includes: transmitting a portion of the PRACH preamble across the guard period, the one or more SBFD resources and the one or more non-SBFD resources during the effective RO, wherein the PRACH preamble is associated with the same set of transmission parameters across the one or more SBFD resources and the one or more non-SBFD resources.

[0295] Aspect 6: The method according to any one of Aspects 4 to 5, the method further comprising: discarding a portion of the PRACH preamble across the guard period during the effective RO, wherein the PRACH preamble is associated with a first set of transmission parameters across the one or more SBFD resources and with a second set of transmission parameters across the one or more non-SBFD resources.

[0296] Aspect 7: The method according to any one of Aspects 4 to 6, the method further comprising: transmitting a first portion of the PRACH preamble associated with the one or more SBFD resources in the first time slot before the protection period; and discarding a second portion of the PRACH preamble associated with the one or more non-SBFD resources in the first time slot after the protection period.

[0297] Aspect 8: According to the method of aspect 7, the method further includes: sending a third portion of the PRACH preamble associated with resources during the protection period.

[0298] Aspect 9: The method according to any one of Aspects 4 to 8, the method further comprising: discarding a first portion of the PRACH preamble associated with the one or more SBFD resources of the first time slot spanning from the beginning of the first time slot to the end of the protection period; and transmitting a second portion of the PRACH preamble associated with the one or more non-SBFD resources of the first time slot after the protection period.

[0299] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the effective RO comprises a plurality of sequence repeats, and according to the first validity rule, the effective RO is at least in part based on the fact that the effective RO comprises a sequence repeat among the plurality of sequence repeats that is aligned with the boundary between the one or more SBFD resources and the one or more non-SBFD resources.

[0300] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the effective RO spans the one or more SBFD resources and the one or more non-SBFD resources, and the UE is configured with a second RO that exclusively spans the one or more non-SBFD resources, the second RO including a time-division duplex RO.

[0301] Aspect 12: According to the method of aspect 11, wherein the effective RO timing is based at least in part on the effective RO being valid across one or more first symbols across the one or more non-SBFD resources, and the one or more first symbols not overlapping with one or more second symbols associated with the second RO, in accordance with the first validity rule.

[0302] Aspect 13: The method according to any one of Aspects 11 to 12, wherein the valid RO is valid at least in part based on the first validity rule, which states that the valid RO and the second RO are each mapped to the same synchronization signal block index.

[0303] Aspect 14: The method according to any one of Aspects 11 to 13, wherein the effective RO is valid at least in part based on the first validity rule being associated with a first frequency span and the second RO being associated with a second frequency span and the frequency interval between the first frequency span and the second frequency span satisfying a threshold.

[0304] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the random access procedure is a two-step random access procedure, the method further comprising: selecting a valid PUSCH timing from a plurality of PUSCH timings at least in part based on a second validity rule, wherein the second validity rule defines the validity of the PUSCH timing when it is associated with a second time slot spanning one or more second SBFD resources and one or more second non-SBFD resources; and transmitting a data message during the valid PUSCH timing selected according to the second validity rule.

[0305] Aspect 16: According to the method of aspect 15, wherein the second validity rule defines the validity of the valid PUSCH timing at least in part based on the valid PUSCH timing exclusively spanning the one or more second SBFD resources of the second time slot or exclusively spanning the one or more second non-SBFD resources of the second time slot.

[0306] Aspect 17: The method according to any one of Aspects 15 to 16, wherein the second validity rule defines the validity of the valid PUSCH timing at least in part based on the valid PUSCH timing spanning the one or more second SBFD resources and the one or more second non-SBFD resources of the second time slot, the one or more second SBFD resources and the one or more second non-SBFD resources being directly adjacent in time, and the PUSCH timing spanning the one or more second SBFD resources and the one or more second non-SBFD resources of the second time slot being associated with the same plurality of frequency resources, the same spatial configuration and the same power control parameters.

[0307] Aspect 18: The method according to any one of Aspects 15 to 17, wherein the second time slot includes a second protection period between the one or more second SBFD resources and the one or more second non-SBFD resources, and the effective PUSCH timing spans the second protection period, the one or more second SBFD resources and the one or more second non-SBFD resources.

[0308] Aspect 19: The method according to aspect 18, the method further comprising: during the effective PUSCH timing, transmitting a portion of the data message spanning the second protection period, the one or more second SBFD resources and the one or more second non-SBFD resources, wherein the data message is associated with the same set of transmission parameters across the one or more second SBFD resources and the one or more second non-SBFD resources.

[0309] Aspect 20: The method according to any one of Aspects 18 to 19, the method further comprising: discarding a portion of the data message spanning the second protection period during the effective PUSCH timing, wherein the data message is associated with a first transmission parameter set across the one or more second SBFD resources and with a second transmission parameter set across the one or more second non-SBFD resources.

[0310] Aspect 21: The method according to any one of aspects 18 to 20, the method further comprising: sending a first portion of the data message associated with the one or more second SBFD resources in the second time slot prior to the second protection period; and discarding a second portion of the data message associated with the one or more second non-SBFD resources in the second time slot after the second protection period.

[0311] Aspect 22: According to the method of aspect 21, the method further includes: sending a third portion of the data message associated with the resources during the second protection period.

[0312] Aspect 23: The method according to any one of aspects 18 to 22, the method further comprising: discarding a first portion of the data message associated with the one or more second SBFD resources of the second time slot spanning from the beginning of the second time slot to the end of the second protection period; and sending a second portion of the data message associated with the one or more second non-SBFD resources of the second time slot after the second protection period.

[0313] Aspect 24: A method for wireless communication at a network entity, the method comprising: sending a configuration message indicating to a UE a plurality of ROs for performing a random access procedure; and receiving a PRACH preamble during a valid RO among the plurality of ROs, wherein the valid RO is based at least in part on a first validity rule, and wherein the first validity rule defines the validity of the RO when it is associated with a first time slot spanning one or more SBFD resources and one or more non-SBFD resources.

[0314] Aspect 25: The method according to aspect 24, wherein, according to the first validity rule, the valid RO is valid at least in part based on the valid RO exclusively spanning the one or more SBFD resources of the first time slot or exclusively spanning the one or more non-SBFD resources of the first time slot.

[0315] Aspect 26: The method according to any one of Aspects 24 to 25, wherein, according to the first validity rule, the valid RO is at least in part based on the fact that the valid RO is valid across the one or more SBFD resources and the one or more non-SBFD resources, the one or more SBFD resources and the one or more non-SBFD resources are directly adjacent in time, and the valid RO across the one or more SBFD resources and the one or more non-SBFD resources is associated with the same plurality of frequency resources, the same spatial configuration and the same power control parameters.

[0316] Aspect 27: The method according to any one of Aspects 24 to 26, wherein the first time slot includes a protection period between the one or more SBFD resources and the one or more non-SBFD resources, and the effective RO spans the protection period, the one or more SBFD resources and the one or more non-SBFD resources.

[0317] Aspect 28: The method according to aspect 27, the method further comprising: receiving, during the effective RO, a portion of the PRACH preamble spanning each of the guard period, the one or more SBFD resources, and the one or more non-SBFD resources, wherein the PRACH preamble is associated with the same set of transmission parameters across the one or more SBFD resources and the one or more non-SBFD resources.

[0318] Aspect 29: The method according to any one of Aspects 27 to 28, the method further comprising: receiving a first portion of the PRACH preamble associated with the one or more SBFD resources of the first time slot prior to the protection period.

[0319] Aspect 30: The method according to aspect 29, the method further comprising: receiving a second portion of the PRACH preamble associated with resources during the protection period.

[0320] Aspect 31: The method according to any one of Aspects 27 to 30, the method further comprising: receiving a first portion of the PRACH preamble associated with the one or more non-SBFD resources in the first time slot after the protection period.

[0321] Aspect 32: The method according to any one of Aspects 24 to 31, wherein the effective RO comprises a plurality of sequence repeats, and according to the first validity rule, the effective RO is at least partially based on the fact that the effective RO comprises a sequence repeat among the plurality of sequence repeats that is aligned with the boundary between the one or more SBFD resources and the one or more non-SBFD resources.

[0322] Aspect 33: The method according to any one of Aspects 24 to 32, wherein the effective RO spans the one or more SBFD resources and the one or more non-SBFD resources, and the UE is scheduled with a second RO that exclusively spans the one or more non-SBFD resources, the second RO including a time-division duplex RO.

[0323] Aspect 34: According to the method of aspect 33, wherein the effective RO timing is based at least in part on the effective RO being effective across one or more first symbols across one or more non-SBFD resources, and the one or more first symbols not overlapping with one or more second symbols associated with the second RO, in accordance with the first validity rule.

[0324] Aspect 35: The method according to any one of Aspects 33 to 34, wherein the valid RO is valid at least in part based on the first validity rule, which states that the valid RO and the second RO are each mapped to the same synchronization signal block index.

[0325] Aspect 36: The method according to any one of Aspects 33 to 35, wherein the effective RO is valid at least in part based on the first validity rule being associated with a first frequency span and the second RO being associated with a second frequency span, and the frequency interval between the first frequency span and the second frequency span satisfying a threshold.

[0326] Aspect 37: The method according to any one of Aspects 24 to 36, wherein the random access procedure is a two-step random access procedure, the method further comprising: receiving a data message during a valid PUSCH timing among a plurality of PUSCH timings, wherein the valid PUSCH timing is based at least in part on a second validity rule, wherein the second validity rule defines the validity of the PUSCH timing when it is associated with a second time slot spanning one or more second SBFD resources and one or more second non-SBFD resources.

[0327] Aspect 38: According to the method of aspect 37, wherein the second validity rule defines the validity of the valid PUSCH timing at least in part based on the valid PUSCH timing exclusively spanning the one or more second SBFD resources of the second time slot or exclusively spanning the one or more second non-SBFD resources of the second time slot.

[0328] Aspect 39: The method according to any one of Aspects 37 to 38, wherein the second validity rule defines the validity of the valid PUSCH timing at least in part based on the one or more second SBFD resources and the one or more second non-SBFD resources spanning the second time slot, the one or more second SBFD resources and the one or more second non-SBFD resources being directly adjacent in time, and the one or more second SBFD resources and the one or more second non-SBFD resources spanning the second time slot being associated with the same plurality of frequency resources, the same spatial configuration and the same power control parameters.

[0329] Aspect 40: The method according to any one of Aspects 37 to 39, wherein the second time slot includes a second protection period between the one or more second SBFD resources and the one or more second non-SBFD resources, and the effective PUSCH timing spans the second protection period, the one or more second SBFD resources and the one or more second non-SBFD resources.

[0330] Aspect 41: The method according to aspect 40, the method further comprising: receiving, during the effective PUSCH timing, a portion of the data message spanning the second protection period, the one or more second SBFD resources and the one or more second non-SBFD resources, wherein the data message is associated with the same set of transmission parameters across the one or more second SBFD resources and the one or more second non-SBFD resources.

[0331] Aspect 42: The method according to any one of aspects 40 to 41, the method further comprising: receiving a first portion of the data message associated with the one or more second SBFD resources in the second time slot prior to the second protection period.

[0332] Aspect 43: The method according to aspect 42, the method further comprising: receiving a second portion of the data message associated with resources during the second protection period.

[0333] Aspect 44: The method according to any one of aspects 40 to 43, the method further comprising: receiving a first portion of the data message associated with the one or more second non-SBFD resources in the second time slot after the second protection period.

[0334] Aspect 45: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of aspects 1 to 23.

[0335] Aspect 46: A UE for wireless communication, the UE comprising at least one component for performing the method according to any one of aspects 1 to 23.

[0336] Aspect 47: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 23.

[0337] Aspect 48: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of Aspects 24 to 44.

[0338] Aspect 49: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 24 to 44.

[0339] Aspect 50: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform a method according to any one of aspects 24 to 44.

[0340] It should be noted that the methods described herein describe possible specific implementations. Operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0341] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0342] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0343] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, graphics processing unit (GPU), neural processing unit (NPU), FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.

[0344] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

[0345] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0346] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0347] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components,” and subsequent reference to “the component” in a claim may be understood to be equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” may refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0348] The term "determine" encompasses a wide range of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

[0349] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0350] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," and not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some figures, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0351] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: The system receives configuration information that indicates to the UE the timing of multiple random access channels (RACH) for performing a random access procedure; The selection of a valid RACH timing from the plurality of RACH timings is based at least in part on a first validity rule, wherein the first validity rule defines the validity of the RACH timing when it is associated with a first time slot that spans one or more sub-band full-duplex (SBFD) resources and one or more non-SBFD resources; as well as The physical RACH (PRACH) preamble is sent during the valid RACH timing selected according to the first validity rule.

2. The UE of claim 1, wherein, according to the first validity rule, the valid RACH timing is valid at least in part based on the valid RACH timing exclusively spanning the one or more SBFD resources of the first time slot or exclusively spanning the one or more non-SBFD resources of the first time slot.

3. The UE of claim 1, wherein, according to the first validity rule, the RACH timing is invalid at least in part based on the RACH timing spanning the one or more SBFD resources and the one or more non-SBFD resources.

4. The UE according to claim 1, wherein: According to the first validity rule: the valid RACH timing is at least partially based on the fact that the valid RACH timing is valid across the one or more SBFD resources and the one or more non-SBFD resources; The one or more SBFD resources and the one or more non-SBFD resources are directly adjacent in time; and The effective RACH timing is associated with the one or more SBFD resources and the one or more non-SBFD resources, along with the same multiple frequency resources, the same spatial configuration, and the same power control parameters.

5. The UE of claim 1, wherein the first time slot includes a protection period between the one or more SBFD resources and the one or more non-SBFD resources, and the effective RACH timing spans the protection period, the one or more SBFD resources, and the one or more non-SBFD resources.

6. The UE of claim 5, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: During the effective RACH timing, a portion of the PRACH preamble is transmitted across the guard period, the one or more SBFD resources, and the one or more non-SBFD resources, wherein the PRACH preamble across the one or more SBFD resources and the one or more non-SBFD resources is associated with the same set of transmission parameters.

7. The UE according to claim 1, wherein: The effective RACH timing spans across the one or more SBFD resources and the one or more non-SBFD resources; and The UE is configured with a second RACH timing that exclusively spans the one or more non-SBFD resources, the second RACH timing including a time-division duplex RACH timing.

8. The UE of claim 7, wherein, according to the first validity rule, the valid RACH timing is at least in part based on the fact that the valid RACH timing is valid across one or more first symbols across the one or more non-SBFD resources, and the one or more first symbols do not overlap with one or more second symbols associated with the second RACH timing.

9. The UE of claim 7, wherein the valid RACH timing is valid at least in part based on the first validity rule, whereby the valid RACH timing and the second RACH timing are each mapped to the same synchronization signal block index.

10. The UE according to claim 7, wherein: According to the first validity rule: the valid RACH timing is at least partially based on the fact that the valid RACH timing is associated with the first frequency span and the second RACH timing is associated with the second frequency span; and The frequency interval between the first frequency span and the second frequency span satisfies a threshold.

11. The UE of claim 1, wherein the random access procedure is a two-step random access procedure, and the one or more processors are also capable of operating individually or jointly to execute the code to cause the UE to: The selection of a valid PUSCH timing from multiple Physical Uplink Shared Channel (PUSCH) timings is based at least in part on a second validity rule, wherein the second validity rule defines the validity of the PUSCH timing when it is associated with a second time slot spanning one or more second SBFD resources and one or more second non-SBFD resources; and Data messages are sent during the valid PUSCH timing selected according to the second validity rule.

12. The UE of claim 1, wherein, according to the first validity rule, the PRACH timing is invalid at least in part based on the PRACH timing spanning the one or more SBFD resources and the one or more non-SBFD resources.

13. The UE of claim 11, wherein the second validity rule defines the validity of the valid PUSCH timing at least in part based on the valid PUSCH timing exclusively spanning the one or more second SBFD resources of the second time slot or exclusively spanning the one or more second non-SBFD resources of the second time slot.

14. The UE according to claim 11, wherein: The second validity rule defines the validity of the valid PUSCH timing at least in part based on the one or more second SBFD resources and the one or more second non-SBFD resources that the valid PUSCH timing spans the second time slot; The one or more second SBFD resources and the one or more second non-SBFD resources are directly adjacent in time; and The PUSCH timing of the one or more second SBFD resources and the one or more second non-SBFD resources spanning the second time slot is associated with the same multiple frequency resources, the same spatial configuration, and the same power control parameters.

15. The UE of claim 11, wherein the second time slot includes a second protection period between the one or more second SBFD resources and the one or more second non-SBFD resources, and the effective PUSCH timing spans the second protection period, the one or more second SBFD resources, and the one or more second non-SBFD resources.

16. The UE of claim 15, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: During the effective PUSCH period, the data message is transmitted across each portion of the second protection period, the one or more second SBFD resources, and the one or more second non-SBFD resources, wherein the data message across the one or more second SBFD resources and the one or more second non-SBFD resources is associated with the same set of transmission parameters.

17. A method for conducting wireless communication at a user equipment (UE), the method comprising: The system receives configuration information that indicates to the UE the timing of multiple random access channels (RACH) for performing a random access procedure; The selection of a valid RACH timing from the plurality of RACH timings is based at least in part on a first validity rule, wherein the first validity rule defines the validity of the RACH timing when it is associated with a first time slot that spans one or more sub-band full-duplex (SBFD) resources and one or more non-SBFD resources; as well as The physical RACH (PRACH) preamble is sent during the valid RACH timing selected according to the first validity rule.

18. The UE of claim 17, wherein, according to the first validity rule, the valid RACH timing is valid at least in part based on the valid RACH timing exclusively spanning the one or more SBFD resources of the first time slot or exclusively spanning the one or more non-SBFD resources of the first time slot.

19. The UE according to claim 17, wherein: According to the first validity rule: the valid RACH timing is at least partially based on the fact that the valid RACH timing is valid across the one or more SBFD resources and the one or more non-SBFD resources; The one or more SBFD resources and the one or more non-SBFD resources are directly adjacent in time; and The effective RACH timing is associated with the one or more SBFD resources and the one or more non-SBFD resources, along with the same multiple frequency resources, the same spatial configuration, and the same power control parameters.

20. A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to: Receive configuration information, which indicates the timing of multiple random access channels (RACH) for performing a random access procedure; The selection of a valid RACH timing from the plurality of RACH timings is based at least in part on a first validity rule, wherein the first validity rule defines the validity of the RACH timing when it is associated with a first time slot that spans one or more sub-band full-duplex (SBFD) resources and one or more non-SBFD resources; as well as The physical RACH (PRACH) preamble is sent during the valid RACH timing selected according to the first validity rule.

Images