Random access channel (RACH) preamble repetition for sub-band non-overlapping full duplex (SBFD) operation

Abstract

Methods, systems, and devices for wireless communication are described. In some systems, a network entity can receive configuration information for a physical random access channel (PRACH) transmission. The configuration information can indicate a random access channel (RACH) occasion (RO) group and a number of preamble repetitions, where the RO group includes a set of valid PRACH occasions. In some aspects, the network entity can support sub-band non-overlapping full duplex (SBFD) operation, and the set of valid PRACH occasions can include at least one SBFD RO that is valid for the PRACH transmission. The RO group can support a single duplex symbol type (e.g., SBFD symbols) or can support different duplex symbol types (e.g., a combination of SBFD symbols and non-SBFD symbols). The network entity can transmit multiple instances of a PRACH message via the RO group, where the number of PRACH message instances is equal to the number of preamble repetitions.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. Patent Application No. 19 / 072,739, filed March 6, 2025, entitled "RANDOM ACCESS CHANNEL (RACH) PREAMBLE REPETITION FOR SUBBAND ​​NON-OVERLAPPING FULL DUPLEX (SBFD) OPERATION," which claims priority to U.S. Patent Application No. 19 / 072,739, filed April 5, 2024, entitled "RANDOM ACCESS CHANNEL (RACH) PREAMBLE REPETITION FOR SUBBAND ​​NON-OVERLAPPING FULL DUPLEX (SBFD)." The benefit of U.S. Provisional Patent Application No. 63 / 575,088, entitled “OPERATION (Random Access Channel (RACH) Preamble Repetition for Subband Non-overlapping Full-Duplex (SBFD) Operation),” is assigned to the assignee of this application, and the entire contents of each of these applications are expressly incorporated herein by reference. Background Technology

[0003] The following pertains to wireless communications related to the Random Access Channel (RACH) procedure.

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. 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 for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0005] The described techniques relate to methods, systems, apparatuses, and devices that support improved preamble repetition for random access channel (RACH) operations for subband non-overlapping full-duplex (SBFD) operation. For example, the described techniques provide improved reliability and resource utilization associated with random access procedures. In some wireless communication systems, network entities such as user equipment (UEs) may receive configuration information for physical random access channel (PRACH) transmission. The configuration information may indicate RACH timing (RO) groups and the number of preamble repetitions for PRACH transmission, wherein the RO group comprises a set of valid PRACH timings. In some aspects, the network entity may support SBFD operation, and the set of valid PRACH timings may include at least one SBFD RO valid for PRACH transmission. An SBFD RO may be an example of an RO within an uplink subband of an SBFD symbol. In some aspects, the RO group may support a single duplex symbol type (e.g., ROs with SBFD symbols). In some other aspects, the RO group may support different duplex symbol types (e.g., ROs with a combination of SBFD symbols and non-SBFD symbols). Additionally or alternatively, the configuration information may include a single RACH configuration or multiple RACH configurations. A network entity may receive the configuration information and may send multiple instances of PRACH messages based on the configuration information. For example, a network entity may send multiple instances of PRACH messages via a group of ROs including at least one SBFD RO, wherein the number of PRACH message instances sent may be equal to the number of configurations for preamble repetition.

[0006] A method for wireless communication performed by a network entity is described. The method may include: receiving configuration information for PRACH transmission, wherein the configuration information indicates RO groups and the number of preamble repetitions, wherein the RO groups comprise a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for PRACH transmission. The method may further include: a set of multiple instances of transmitting PRACH messages via the RO groups based on the number of preamble repetitions.

[0007] A network entity for wireless communication is described. The network entity may include a processing system configured to receive configuration information for PRACH transmission, wherein the configuration information indicates RO groups and the number of preamble repetitions, wherein the RO groups comprise a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for PRACH transmission. The processing system may be configured to transmit a set of multiple instances of PRACH messages via RO groups based on the number of preamble repetitions.

[0008] Another network entity for wireless communication is described. This network entity may include: a component for receiving configuration information for PRACH transmission, wherein the configuration information indicates RO groups and the number of preamble repetitions, wherein the RO groups comprise a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for PRACH transmission. The network entity may also include: a component for transmitting a set of multiple instances of PRACH messages via the RO groups based on the number of preamble repetitions.

[0009] A non-transitory computer-readable medium having code for wireless communication stored thereon is described. When executed by a network entity, the code enables the network entity to: receive configuration information for PRACH transmission, wherein the configuration information indicates RO groups and the number of preamble repetitions, wherein the RO groups comprise a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for PRACH transmission. When executed by the network entity, the code further enables the network entity to: transmit a set of multiple instances of PRACH messages via the RO groups based on the number of preamble repetitions.

[0010] In some aspects of the methods, network entities, and non-transitory computer-readable media described herein, the RO group may be a first RO group, wherein the first RO group includes SBFD ROs, and the configuration information further indicates a second RO group, wherein the second RO group includes Time Division Duplex (TDD) ROs. In some aspects of the methods, network entities, and non-transitory computer-readable media described herein, the configuration information may individually indicate: a first PRACH sequence format, a first transmit beam, a first set of frequency resources, a first RACH preamble, or any combination thereof, corresponding to the first RO group; and a second PRACH sequence format different from the first PRACH sequence format, a second transmit beam different from the first transmit beam, a second set of frequency resources different from the first set of frequency resources, a second RACH preamble different from the first RACH preamble, or any combination thereof, corresponding to the second RO group. In some aspects of the methods, network entities, and non-transitory computer-readable media described herein, the number of preamble repetitions may be a first number of preamble repetitions for SBFD ROs, and the configuration information individually indicates a second number of preamble repetitions for TDD ROs.

[0011] In some aspects of the methods, network entities, and non-transitory computer-readable media described herein, configuration information indicates, for the first RO group and the second RO group, the same PRACH sequence format, the same transmit beam, the same set of frequency resources, the same RACH preamble, or any combination thereof. In some aspects of the methods, network entities, and non-transitory computer-readable media described herein, the number of preamble repetitions corresponds to both the first RO group and the second RO group.

[0012] In some aspects of the methods, network entities, and nontransitory computer-readable media described herein, the RO group includes at least one SBFD RO and at least one TDD RO.

[0013] Some aspects of the methods, network entities, and nontransitory computer-readable media described herein may include operations, features, components, or codes for receiving information indicating that RO groups support the same duplex symbol type. Some examples of the methods, network entities, and nontransitory computer-readable media described herein may include operations, features, components, or codes for receiving information indicating that RO groups support different duplex symbol types.

[0014] The methods, network entities, and nontransitory computer-readable media described herein may include operations, features, components, or code for determining whether RO groups support the same or different duplex symbol types based on a comparison of PRACH parameters configured for SBFD symbols and non-SBFD symbols. In some aspects of the methods, network entities, and nontransitory computer-readable media described herein, PRACH parameters include PRACH sequence format, transmit beam, set of frequency resources, RACH preamble, or any combination thereof.

[0015] In some aspects of the methods, network entities, and nontransitory computer-readable media described herein, the number of preamble repetitions may be a first number of preamble repetitions for a network entity that supports at least one SBFD RO valid for PRACH transmission, and the configuration information further indicates a second number of preamble repetitions for a second network entity that fails to identify a SBFD RO valid for PRACH transmission.

[0016] In some aspects of the methods, network entities, and nontransitory computer-readable media described herein, a group of ROs for a network entity shares one or more ROs with a second group of ROs for a second network entity, and the RO group and the second group of ROs correspond to different RACH preambles for the one or more shared ROs. In some other aspects of the methods, network entities, and nontransitory computer-readable media described herein, a first corresponding RO in the group of ROs for a network entity may be different from a second corresponding RO in the second group of ROs for a second network entity.

[0017] Some aspects of the methods, network entities, and nontransitory computer-readable media described herein may include operations, features, components, or code for receiving a Random Access Response (RAR) message based on at least one instance of a set of multiple instances of a PRACH message. In some aspects of the methods, network entities, and nontransitory computer-readable media described herein, the set of multiple instances of a PRACH message corresponds to a single RAR, and the methods, apparatus, and nontransitory computer-readable media may include operations, features, components, or code for monitoring RAR messages via monitoring timing associated with the single RAR.

[0018] In some aspects of the methods, network entities, and nontransitory computer-readable media described herein, at least one SBFD RO may be located within a subband configured for uplink transmission within an SBFD symbol.

[0019] In some aspects of the methods, network entities, and nontransitory computer-readable media described herein, the set of valid PRACH timings includes a set of multiple PRACH timings that span the same set of frequency resources, correspond to the same transmit beam, correspond to the same transmit power, correspond to the same RACH preamble, or correspond to the same duplex symbol type.

[0020] In some aspects of the methods, network entities, and non-transitory computer-readable media described herein, configuration information includes Radio Resource Control (RRC) signals or System Information Blocks (SIBs).

[0021] In some aspects of the methods, network entities, and non-transitory computer-readable media described herein, the number of sets of multiple instances of a PRACH message may be equal to the number of preamble repetitions. In some aspects of the methods, network entities, and non-transitory computer-readable media described herein, the number of preamble repetitions may be greater than one. In some aspects of the methods, network entities, and non-transitory computer-readable media described herein, the number of opportunities in the set of valid PRACH opportunities may be equal to the number of preamble repetitions.

[0022] A method for wireless communication performed by a network entity is described. The method may include: transmitting configuration information for PRACH transmission, wherein the configuration information indicates RO groups and the number of preamble repetitions, wherein the RO groups comprise a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for PRACH transmission. The method may further include: receiving at least one instance from a set of multiple instances of receiving PRACH messages via the RO groups based on the number of preamble repetitions.

[0023] A network entity for wireless communication is described. The network entity may include a processing system configured to transmit configuration information for PRACH transmission, wherein the configuration information indicates RO groups and the number of preamble repetitions, wherein the RO groups comprise a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for PRACH transmission. The processing system may be configured to receive at least one instance from a set of multiple instances of receiving PRACH messages via the RO groups based on the number of preamble repetitions.

[0024] Another network entity for wireless communication is described. This network entity may include: components for causing the transmission of configuration information for PRACH transmission, wherein the configuration information indicates RO groups and the number of preamble repetitions, wherein the RO groups comprise a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for PRACH transmission. The network entity may further include: components for receiving at least one instance from a set of multiple instances of PRACH messages via the RO groups based on the number of preamble repetitions.

[0025] A non-transitory computer-readable medium having code for wireless communication stored thereon is described. When executed by a network entity, the code enables the network entity to: send configuration information for PRACH transmission, wherein the configuration information indicates RO groups and the number of preamble repetitions, wherein the RO groups comprise a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for PRACH transmission. When executed by the network entity, the code further enables the network entity to: receive at least one instance from a set of multiple instances of receiving PRACH messages via the RO groups based on the number of preamble repetitions.

[0026] In some aspects of the methods, network entities, and nontransitory computer-readable media described herein, the RO group may be a first RO group, wherein the first RO group includes SBFD ROs, and the configuration information further indicates a second RO group, wherein the second RO group includes TDD ROs.

[0027] In some aspects of the methods, network entities, and nontransitory computer-readable media described herein, configuration information individually indicates: a first PRACH sequence format, a first transmit beam, a first set of frequency resources, a first RACH preamble, or any combination thereof, corresponding to a first RO group; and a second PRACH sequence format different from the first PRACH sequence format, a second transmit beam different from the first transmit beam, a second set of frequency resources different from the first set of frequency resources, a second RACH preamble different from the first RACH preamble, or any combination thereof, corresponding to a second RO group.

[0028] In some aspects of the methods, network entities, and non-transitory computer-readable media described herein, the number of preamble repetitions is a first number for SBFD RO, and the configuration information separately indicates a second number for TDD RO. In some aspects of the methods, network entities, and non-transitory computer-readable media described herein, the configuration information indicates the same PRACH sequence format, the same transmit beam, the same set of frequency resources, the same RACH preamble, or any combination thereof for the first RO group and the second RO group. In some aspects of the methods, network entities, and non-transitory computer-readable media described herein, the number of preamble repetitions corresponds to both the first RO group and the second RO group.

[0029] In some aspects of the methods, network entities, and non-transitory computer-readable media described herein, configuration information includes RRC signals or SIBs. Attached Figure Description

[0030] Figure 1 and Figure 2 An example of a wireless communication system supporting random access channel (RACH) preamble repetition for subband non-overlapping full-duplex (SBFD) operation is shown, according to one or more aspects of this disclosure.

[0031] Figures 3 to 5 An example of a RACH configuration supporting RACH preamble repetition for SBFD operation is shown, according to one or more aspects of this disclosure.

[0032] Figure 6 An example of a process flow supporting RACH preamble repetition for SBFD operation is shown, according to one or more aspects of this disclosure.

[0033] Figure 7 and Figure 8 A block diagram of a device supporting RACH preamble repetition for SBFD operation is shown, according to one or more aspects of this disclosure.

[0034] Figure 9A block diagram of a communication manager supporting RACH preamble repetition for SBFD operation, according to one or more aspects of this disclosure, is shown.

[0035] Figure 10 A diagram of a system including a device supporting RACH preamble repetition for SBFD operation is shown, according to one or more aspects of this disclosure.

[0036] Figures 11 to 14 A flowchart illustrating a method for supporting RACH preamble repetition for SBFD operation according to one or more aspects of this disclosure is shown. Detailed Implementation

[0037] In some wireless communication systems, network entities such as user equipment (UEs) may support Subband Non-overlapping Full-Duplex (SBFD) operation. In SBFD operation, a network entity may determine symbols configured for SBFD communication (e.g., SBFD symbols) and may transmit uplink signaling via the subband of the SBFD symbol configured for uplink communication. Other frequency resources of the SBFD symbol may support downlink communication such that the frequency resources of the SBFD symbol configured for uplink and the frequency resources of the SBFD symbol configured for downlink are “non-overlapping” in the frequency domain. In some aspects, a wireless communication system may include a first subset of network entities supporting SBFD operation (e.g., “SBFD-aware” UEs) and a second subset of network entities operating under Time Division Duplex (TDD) operation (e.g., “non-SBFD-aware” or “legacy” UEs). For example, in TDD operation, a network entity may transmit uplink signaling via symbols configured for uplink operation and receive downlink signaling via symbols configured for downlink operation, but the network entity may not recognize the SBFD symbol. Wireless communication systems can use SBFD symbols to improve the random access process of network entities that support SBFD operations.

[0038] For example, a network entity supporting SBFD operation may receive configuration information for Physical Random Access Channel (PRACH) transmission. In some aspects, a network entity (e.g., a UE) may receive the configuration information from another network entity (e.g., a base station or other network entity) via Radio Resource Control (RRC) messages or broadcast signals. The configuration information may indicate the RACH timing (RO) group and the number of preamble repetitions for PRACH transmission, wherein the RO group comprises a set of valid PRACH timings. In some aspects, this set of valid PRACH timings may include at least one SBFD RO valid for PRACH transmission. An SBFD RO may be an example of an RO within an uplink subband of an SBFD symbol. In some aspects, the RO group may support a single duplex symbol type (e.g., an RO in an SBFD symbol or an RO in a non-SBFD symbol such as a TDD symbol). In some other aspects, the RO group may support different duplex symbol types (e.g., an RO in a combination of SBFD symbols and non-SBFD symbols). Additionally or alternatively, the configuration information may include a single RACH configuration or multiple RACH configurations. For example, a single RACH configuration can indicate different information to an SBFD-aware UE compared to a non-SBFD-aware UE (e.g., different ROs, different numbers of preamble repetitions). Alternatively, multiple RACH configurations may include a first RACH configuration indicating information to an SBFD-aware UE and a second RACH configuration indicating different information to a non-SBFD-aware UE.

[0039] Network entities can receive configuration information and can send multiple instances of PRACH messages based on the configuration information. For example, a network entity can send multiple instances of PRACH messages via a group of ROs. An RO group can include a certain number of valid ROs equal to the configured number of preamble repetitions, and the network entity can send a corresponding instance of the PRACH message in each valid RO in the RO group. Therefore, the network entity can send a certain number of PRACH message instances equal to the number of preamble repetitions indicated by the configuration information. Based on an RO group including at least one SBFD RO, the network entity can perform RACH preamble repetition via one or more SBFD symbols, thereby improving the reliability, latency, and resource utilization associated with random access procedures.

[0040] The various aspects of this disclosure are first described in the context of a wireless communication system. Additional aspects of this disclosure are described with reference to RACH configuration and process flow. The various aspects of this disclosure are further illustrated and described by means of and reference to apparatus diagrams, system diagrams, and flowcharts relating to RACH preamble repetition for SBFD operation.

[0041] Figure 1An example of a wireless communication system 100 supporting RACH preamble repetition for SBFD operation is shown according to one or more aspects of this disclosure. The wireless communication system 100 may include one or more devices, such as one or more network entities. Network entities may be examples of network devices (e.g., network entity 105), UE 115, or core network 130. In some aspects, 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 according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0042] Network entity 105 may be distributed across a geographical area to form wireless communication system 100 and may include devices in different forms or with 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 aspects, 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 a coverage area 110 (e.g., a geographical coverage area) over which UE 115 and network entity 105 may establish communication link 125. Coverage area 110 may be an example of a geographical area in which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0043] As described herein, a network entity (which may alternatively be referred to as an entity, node, network node, or wireless entity) may be, resemble, include, or be included in (e.g., may be a component of): a base station (e.g., any base station described herein, including a decomposed base station), a UE (e.g., any UE described herein), a RedCap device, an enhanced RedCap device, an ambient Internet of Things (IoT) device, a device with energy harvesting (EH) capability, a network controller, apparatus, device, computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, a network entity may be a UE. As another example, a network entity may be a base station. As used herein, “network entity” may refer to an entity configured to operate in a network, such as network entity 105. For example, “network entity” is not limited to an entity currently located in and / or currently operating in a network. Rather, a network entity can be any entity capable of communicating and / or operating within a network.

[0044] The adjectives "first," "second," "third," etc., are used to distinguish between two or more modified nouns in a contextual discussion and do not imply absolute modifiers applicable only to a specific corresponding entity throughout the document. For example, a network entity may be referred to as "first network entity" in one discussion and as "second network entity" in another, and vice versa. As an example, the first network entity may be configured to communicate with a second network entity or a third network entity. In one aspect of this example, the first network entity may be a UE, the second network entity may be a base station, and the third network entity may be a UE. In another aspect of this example, the first network entity may be a UE, the second network entity may be a base station, and the third network entity may be a base station. In yet other aspects of this example, the first, second, and third network entities may be different from these examples.

[0045] Similarly, references to UE, base station, device, equipment, computing system, etc., may include disclosures of UE, base station, device, equipment, computing system, etc., as network entities. For example, a disclosure of a UE being configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity. Consistent with this disclosure, once a particular example is extended according to this disclosure (e.g., a disclosure of a UE being configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station and a first network entity is configured to receive information from a second network entity, the first network entity may refer to a first UE, a first base station, a first device, a first equipment, a first computing system, a first set of one or more components, a first processing entity, etc., configured to receive information; and the second network entity may refer to a second UE, a second base station, a second device, a second equipment, a second computing system, a second set of one or more components, a second processing entity, etc.

[0046] As described herein, different terms may be used in various contexts to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network entity may be described as being configured to send information to a second network entity. In this example and consistent with this disclosure, disclosure that a first network entity is configured to send information to a second network entity includes disclosure that the first network entity is configured to provide, transmit, output, communicate, or send information to the second network entity. Similarly, in this example and consistent with this disclosure, disclosure that a first network entity is configured to send information to a second network entity includes disclosure that the second network entity is configured to receive, obtain, or decode information provided, transmitted, output, communicate, or sent by the first network entity.

[0047] As shown in the figure, a network entity (e.g., network entity 105) may include processing system 106. Similarly, a network entity (e.g., UE 115) may include processing system 112. A processing system may include one or more components (or sub-components), such as those described herein. For example, a corresponding component of such one or more components may be, resemble, include, or be included in at least one memory, at least one communication interface, or at least one processor. For example, a processing system may include one or more components. In such an example, the one or more components may include a first component, a second component, and a third component. In this example, the first component may be coupled to the second and third components. In this example, the first component may be at least one processor, the second component may be a communication interface, and the third component may be at least one memory. A processing system may generally be one or more components of a system capable of performing one or more functions (such as any function or combination of functions described herein). For example, one or more components may receive input information (e.g., any information as input, such as a signal, any digital information, or any other information), one or more components may process the input information to generate output information (e.g., any information as output, such as a signal or any other information), and one or more components may perform any function as described herein or any combination thereof. As described herein, “input” and “input information” may be used interchangeably. Similarly, as described herein, “output” and “output information” may be used interchangeably. Any information generated by any component may be provided to components of one or more other systems or network entities, such as those described herein. For example, a processing system may include a first component configured to receive or obtain information, a second component configured to process the information to generate output information, and / or a third component configured to provide the output information to other systems or components. In this example, the first component may be a communication interface (e.g., a first communication interface), the second component may be at least one processor (e.g., coupled to the communication interface and / or at least one memory), and the third component may be a communication interface (e.g., the first communication interface or the second communication interface). For example, the processing system may include at least one memory, at least one communication interface and / or at least one processor, wherein the at least one processor may be coupled to, for example, the at least one memory and the at least one communication interface.

[0048] The processing system of the network entity described herein can interface with one or more other components of the network entity, process information received from one or more other components (such as input information), or output such information to one or more other components. For example, the processing system may include a first component configured to interface with one or more other components of the network entity to receive or obtain information, a second component configured to process the information to generate one or more outputs, and / or a third component configured to output the one or more outputs to one or more other components. In this example, the first component may be a communication interface (e.g., a first communication interface), the second component may be at least one processor (e.g., coupled to the communication interface and / or at least one memory), and the third component may be a communication interface (e.g., the first communication interface or the second communication interface). For example, a chip or modem of the network entity may include the processing system. The processing system may include a first communication interface for receiving or obtaining information, and a second communication interface for outputting, transmitting, or providing information. In some aspects, the first communication interface may be an interface configured to receive input information, and such information may be provided to the processing system. In some aspects, the second system interface may be configured to transmit information output from the chip or modem. The second communication interface can also obtain or receive input information, and the first communication interface can also output, send, or provide information.

[0049] UE 115 may be distributed throughout the entire coverage area 110 of wireless communication system 100, and each UE 115 may be stationary, mobile, or both at different times. UE 115 may be devices of different forms or with different capabilities. Figure 1 Examples of UE 115 are illustrated herein. 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 UE 115 or network entity 105), such as... Figure 1 As shown.

[0050] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or a 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. Alternatively, a node may be network entity 105. Alternatively, a first node may be configured to communicate with a second or 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.

[0051] In some aspects, 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 aspects, 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 aspects, 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. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or 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 can communicate with core network 130 via communication link 155.

[0052] One or more network entities or network equipment described herein as network entity 105 or network equipment 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, eNodeB (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 evolution node B, or other suitable terms). In some aspects, 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 that is physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).

[0053] In some aspects, 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 IAB networks, Open RAN (O-RAN) (e.g., network configurations sponsored by the O-RAN Alliance), or Virtualized RAN (vRAN) (e.g., Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: CU such as CU 160, DU such as DU 165, RU such as RU 170, RAN Intelligent Controller (RIC) such as RIC 175 (e.g., near real-time RIC (near RT RIC), non-real-time RIC (non-RT RIC)), 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 aspects, 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)).

[0054] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities based 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 respects, CU 160 can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 (e.g., one or more CUs) may 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 may 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 may each be at least partially controlled by CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between DU 165 and RU 170, such that DU 165 may support one or more layers of the protocol stack, and RU 170 may support one or more different layers of the protocol stack. DU 165 may (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 respects, 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, each layer of which is supported by a corresponding network entity (e.g., one or more network entities in network entity 105) communicating via such a communication link.

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

[0056] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture can 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, etc.).

[0057] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any 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 aspects, UE 115 may include or be referred to as a wireless local loop (WLL) station, IoT device, Internet of Things (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in a variety of objects such as appliances, vehicles, or instruments.

[0058] The UE 115 described herein may be able to communicate with various types of devices, such as the UE 115 which may sometimes operate 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.

[0059] 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 collection 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 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may 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 mean that any part of network entity 105 of the RAN (e.g., base station 140, CU 160, DU 165, RU 170) communicates 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).

[0060] In some aspects, such as in carrier aggregation configurations, a carrier may have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., of the same or different RATs) are used to anchor the connection.

[0061] The communication link 125 of the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. The carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0062] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some aspects, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a specific RAT (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have a hardware configuration that supports communication using a specific carrier bandwidth, or may be configured to support communication using one of the carrier bandwidths in the set of carrier bandwidths. In some aspects, the wireless communication system 100 may include a network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some aspects, each served UE 115 may be configured to operate using a portion (e.g., a sub-band, BWP) or all of the carrier bandwidth.

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

[0064] 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, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval for organizing communication resources can be based on 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).

[0065] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some aspects, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a 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 number of symbol periods (e.g., based 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.

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

[0067] 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 common search space set configured to transmit control information to UE 115 (e.g., one or more UEs), or it may include a UE-specific search space set configured to transmit control information to UE 115 (e.g., a particular UE).

[0068] In some aspects, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas such as coverage area 110. In some aspects, coverage areas 110 associated with different technologies (e.g., different coverage areas) may overlap, but coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., network entity 105). In some other aspects, overlapping coverage areas (such as coverage area 110) associated with different technologies may 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 use the same or different RATs to support communication for coverage area 110 (e.g., different coverage areas).

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

[0070] In some aspects, UE 115 may be configured to support direct communication with other UEs (e.g., one or more UEs in UE 115) via device-to-device (D2D) communication links (such as D2D communication link 135) (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some aspects, 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 aspects, 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 aspects, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, in which each UE 115 transmits to one or more UEs in the group. In some aspects, network entity 105 can facilitate the scheduling of resources for D2D communication. In some other aspects, D2D communication can be performed between UEs 115 without involving network entity 105.

[0071] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may 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 transferred through user plane entities, which provide IP address allocation and other functions. User plane entities 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.

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

[0073] 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 using unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some aspects, operation using unlicensed frequency bands may be combined with component carriers operating using licensed frequency bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0074] 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 aspects, the antennas or antenna arrays associated with network entity 105 may be located in 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.

[0075] 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 specific orientation relative to 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 specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0076] The wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly for transmission via logical channels. The MAC layer may perform priority processing and multiplexing of logical channels to transport channels. The MAC layer may also implement error detection, error correction, or both to support retransmission and improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer may map transport channels to physical channels.

[0077] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under relatively poor radio conditions (e.g., low signal-to-noise ratio conditions). In some aspects, the device can support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other aspects, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0078] In some wireless communication systems, UE 115 (e.g., an example of a first network entity) may perform a random access procedure to establish a connection with a wireless network, for example, via network entity 105 (e.g., an example of a second network entity). UE 115 may trigger the random access procedure with network entity 105 based on a request transmitted in PRACH (e.g., via higher-layer signaling) or based on a physical downlink control channel (PDCCH) command for the cell.

[0079] The random access procedure may involve the exchange of RACH messages between UE 115 (e.g., a first network entity) and network entity 105 (e.g., a second network entity). During the four-step random access procedure, UE 115 may send RACH message 1 (Msg1) including a RACH preamble to network entity 105, and network entity 105 may respond with a Random Access Response (RAR) message, which may be referred to as RACH message 2 (Msg2). The RAR message may include a RACH preamble identifier (RAPID) corresponding to the RACH preamble and uplink permission. UE 115 may send RACH message 3 (Msg3) including Physical Uplink Shared Channel (PUSCH) data via the resources granted by the uplink permission. Network entity 105 may respond to a contention-resolved RACH message 4 (Msg4) to complete the random access procedure and establish a connection between UE 115 and network entity 105. Alternatively, during the two-step random access process, UE 115 may send a RACH message A (MsgA) including a RACH preamble and PUSCH data, and network entity 105 may respond with a RACH message B (MsgB) including a RAR message and contention resolution information.

[0080] Network entity 105 may configure RACH parameters to UE 115 to perform a random access procedure. For example, network entity 105 may send configuration information to UE 115 for PRACH transmission for a cell (e.g., a cell served by network entity 105). Network entity 105 may send the configuration information via higher-layer signaling (such as via RRC messages or broadcast signals (e.g., System Information Block (SIB) 1)). In some aspects, the configuration information may include indications of the following: preamble index, preamble subcarrier spacing (SCS), target transmit power for PRACH transmission (e.g., ...). The configuration information includes: the value of the random access radio network temporary identifier (RA-RNTI) (if applicable), the PRACH resource for the cell, or a set of PRACH resources, or any combination thereof. Additionally or alternatively, the configuration information may indicate the number of preamble repetitions used for PRACH transmission. If UE 115 supports the transmission of PRACH messages with repetitions, the number of preamble repetitions can be greater than one (e.g., ).

[0081] UE 115 (e.g., the first network entity) can be based on the indicated number of preamble repetitions. One or more instances of a PRACH message are sent. Instances of a PRACH message can be RACH Msg1, RACH MsgA, a RACH preamble, or an instance of some other portion of RACH Msg1 or RACH MsgA sent via a valid PRACH timing (e.g., RO). For example, UE 115 may send a certain number of instances of a PRACH message equal to the indicated number of preamble repetitions. If the configuration information indicates... (For example, if the number of preamble repetitions is set to one), then UE 115 can send a single instance of the PRACH message via a single valid PRACH timing (e.g., a single RO). Alternatively, if the configuration information indicates... (For example, if the number of preamble repetitions is greater than one), then UE 115 can send a set of multiple instances of PRACH messages via a set of valid PRACH opportunities (e.g., a set of ROs corresponding to RO groups), where the number of instances of PRACH messages sent and the number of valid PRACH opportunities in the set are both equal to the number of preamble repetitions. .

[0082] UE 115 can transmit one or more PRACH message instances based on configuration information. For example, UE 115 can use a selected PRACH format, a transmission power based on a configured target transmission power for PRACH transmission, and a configured PRACH resource using the same spatial filter (e.g., corresponding to the same transmission beam) based on the configuration information. )or A collection of PRACH resources (e.g., if) (or any combination thereof) to send PRACH message instances for the cell. A set of PRACH resources can correspond to a single RO group. RO groups can be time-continuous, use the same frequency resources, and are associated with the same one or more Synchronization Signal (SS) / Physical Broadcast Channel (PBCH) Block (SSB) indices. A set of valid PRACH opportunities, wherein each SSB index can be associated with the same RACH preamble index used for a valid PRACH opportunity within that set. Configuration information can configure one or more RO groups for UE 115, and UE 115 can select or otherwise determine the RO groups used for PRACH transmission. For PRACH transmissions with RACH preamble repetition, UE 115 can determine the time period associated with the preamble repetition. The time period starting from frame 0 can be the smallest integer of the associated pattern time period, such that the RO group used for all configured numbers of preamble repetitions (e.g., one, two, four, or eight preamble repetitions) can be determined within that time period. At least one set of valid PRACH opportunities for each SSB index in the SSB indexes. The set of valid PRACH opportunities for each configured number of preamble repetitions can be repeated by time period.

[0083] In some aspects, network entity 105 (e.g., a second network entity) may configure UE 115 (e.g., a first network entity) to include a group of ROs comprising at least one SBFD RO. An SBFD RO may be an example of a valid resource within a subband configured for uplink transmission within an SBFD symbol for PRACH transmission. Additionally, network entity 105 may configure UE 115 to have a greater than one number of preamble repetitions, such that UE 115 can transmit multiple instances of PRACH messages via one or more SBFD ROs, one or more TDD ROs (e.g., ROs within an uplink symbol), or a combination thereof. UE 115 may perform RACH preamble repetition for SBFD operations based on this configuration (e.g., via one or more SBFD ROs).

[0084] Figure 2An example of a wireless communication system 200 supporting RACH preamble repetition for SBFD operation, according to one or more aspects of this disclosure, is shown. The wireless communication system 200 may be as referenced herein. Figure 1 An example of a described wireless communication system 100. The wireless communication system 200 may include a first network entity 205, a second network entity 210, and a third network entity 215. The first network entity 205 may be an SBFD-aware UE (such as those referenced herein). Figure 1 The example described is UE 115. The SBFD-aware UE can perform uplink transmissions via the uplink subband of the SBFD symbol. The second network entity 210 may be as referenced herein. Figure 1 The example described is of network entity 105 providing network coverage for coverage area 110-a. Third network entity 215 may be a non-SBFD-aware UE (e.g., a "legacy" UE) (such as those referenced herein). Figure 1 An example of the described UE 115. In some respects, a non-SBFD-aware UE can process SBFD symbols in the same way as downlink symbols. The first network entity 205 can support random access operations via SBFD symbols.

[0085] In some aspects, the first network entity 205 may support random access procedures when operating in RRC connected mode. Additionally or alternatively, the first network entity 205 may support random access procedures when operating in RRC idle mode or RRC inactive mode. The first network entity 205 may perform PRACH transmission via SBFD symbols, TDD symbols (e.g., uplink symbols), or combinations thereof. In some aspects, the first network entity 205 may support RACH preamble repetition for PRACH transmission via SBFD symbols or across SBFD and non-SBFD (e.g., TDD) symbols based on RACH configuration.

[0086] The second network entity 210 may send configuration information to the first network entity 205 via downlink channel 220, the configuration information indicating one or more RACH configurations for the first network entity 205. In some aspects, the second network entity 210 may send a single RACH configuration 230-a applicable to both SBFD symbol types and non-SBFD (e.g., TDD) symbol types. The second network entity 210 may use the single RACH configuration 230-a to improve the signaling overhead associated with the RACH configuration based on both SBFD-aware UEs (e.g., the first network entity 205) and non-SBFD-aware UEs (e.g., the third network entity 215). The single RACH configuration 230-a may configure one or more valid ROs within an uplink subband of an SBFD symbol, one or more valid ROs within a non-SBFD uplink or flexible symbol, or a combination thereof. SBFD-aware UEs (e.g., the first network entity 205) and non-SBFD-aware UEs (e.g., the third network entity 215) receiving the single RACH configuration 230-a may determine different valid ROs based on the same RACH configuration 230-a. For example, a first network entity 205 may determine the valid RO within an SBFD symbol, an uplink symbol, or both, based on a single RACH configuration 230-a. A third network entity 215 may determine the valid RO within uplink and flexible symbols (but not SBFD symbols) based on a single RACH configuration 230-a. In some aspects, if an SBFD RO is configured in an SBFD flexible (FL) symbol, a non-SBFD-aware UE may utilize the random access procedure via the SBFD symbol. To support the single RACH configuration 230-a, the RACH configuration may be enhanced to support indicating SBFD ROs, and SBFD-aware UEs may follow RO validity rules and SSB-to-RO mappings for SBFD symbols.

[0087] In some other aspects, the second network entity 210 may transmit separate RACH configurations for SBFD-aware UEs and for non-SBFD-aware UEs. For example, the second network entity 210 may transmit a first RACH configuration 230-a corresponding to a first duplex symbol type (e.g., SBFD) and a second RACH configuration 230-b corresponding to a different second duplex symbol type (e.g., TDD). In some cases, the second RACH configuration 230-b for the TDD symbol type may be referred to as a "legacy" RACH configuration. Separate RACH configurations may configure different PRACH parameters. For example, the first RACH configuration 230-a and the second RACH configuration 230-b may indicate different RO time resources, different RO frequency resources, different preambles, different transmit power configurations, or any combination thereof. Additionally or alternatively, the first RACH configuration 230-a and the second RACH configuration 230-b may support independent SSB-to-RO mapping. An SBFD-aware UE (e.g., first network entity 205) may receive a first RACH configuration 230-a and determine valid ROs within the uplink subband of an SBFD symbol. A non-SBFD-aware UE (e.g., third network entity 215) or an SBFD-aware UE may receive a second RACH configuration 230-b and determine valid ROs within the uplink symbol. Therefore, the second RACH configuration 230-b may be an example of “RO-Config1” for TDD, and the first RACH configuration 230-a may be an example of “RO-Config2” for SBFD. The SBFD-aware UE may follow RO validity rules for SBFD symbols and may select an RO configuration from the first RACH configuration 230-a and the second RACH configuration 230-b for PRACH transmission. In some aspects, the SBFD-aware UE may switch between different RACH configurations.

[0088] RACH configuration 230-a can indicate the number of preamble repetitions used for SBFD-aware UEs. In some aspects, the second network entity 210 may send a single RACH configuration 230-a indicating a single number of preamble repetitions for SBFD-aware UEs and non-SBFD-aware UEs. In some other aspects, the second network entity 210 may send a first number of preamble repetitions indicating a first number of preamble repetitions for SBFD-aware UEs (e.g., ) and a second number of preamble repetitions for non-SBFD-aware UEs (e.g., A single RACH configuration 230-a, wherein the first number may be the same as or different from the second number. In some other aspects, the second network entity 210 may send an indication of the first number of repetitions of the preamble for the SBFD symbol (e.g., The first RACH configuration 230-a can transmit a second number of preamble repetitions (e.g., for uplink and / or flexible (TDD) symbols) indicating the number of repetitions. The second RACH configuration 230-b, wherein the first quantity may be the same as or different from the second quantity. Therefore, the first network entity 205 may receive RACH configuration 230-a and may determine the number of PRACH message instances to be sent based on the number of preamble repetitions indicated by RACH configuration 230-a. For example, the first network entity 205 may send an amount equal to the indicated number of preamble repetitions (e.g., ...). or The number of instances of PRACH messages.

[0089] The first network entity 205 can be configured to be two based on the number of preamble repetitions (e.g., The first network entity 205 can transmit a first PRACH message instance 235-a and a second PRACH message instance 235-b via PRACH (e.g., uplink channel 225). Alternatively, other numbers of preamble repetitions may be supported, such as one (e.g., corresponding to a single PRACH message instance), four, eight, or any other value. The first network entity 205 may, based on a specific RACH configuration 230-a, transmit a set of multiple instances of PRACH messages via one or more SBFD symbols, one or more uplink (e.g., TDD) symbols, or combinations thereof. (See reference...) Figures 3 to 5 A more detailed description of the example RACH configuration is provided.

[0090] Supporting RACH preamble repetition via SBFD symbols can improve the reliability and latency of random access procedures for SBFD-aware UEs. For example, a first network entity 205 may transmit one or more instances of a PRACH message via one or more SBFD symbols preceding one or more TDD symbols. By transmitting PRACH message instances via SBFD symbols instead of waiting for TDD symbols, the first network entity 205 can reduce the latency involved in transmitting PRACH message instances. Additionally or alternatively, by transmitting multiple PRACH message instances instead of a single PRACH message, the first network entity 205 can increase the likelihood that a second network entity 210 will successfully receive at least one PRACH message instance and respond with a RAR message, thereby improving the reliability of the random access procedure.

[0091] Figure 3 An example of a RACH configuration 300 supporting RACH preamble repetition for SBFD operation is shown, according to one or more aspects of this disclosure. RACH configuration 300 may be as referenced herein. Figure 2Examples of RACH configuration 230-a or RACH configuration 230-b are described. RACH configuration 300 can support the same duplex symbol type (e.g., SBFD or TDD symbols) within the corresponding RO group. Therefore, multiple instances of network entities sending PRACH messages (such as those referenced in this document) Figure 1 and Figure 2 The described UE 115 or network entity 205 may send the multiple instances within SBFD RO or TDD RO, but not both.

[0092] RACH configuration 300 (e.g., a single RACH configuration or multiple RACH configurations) can configure one or more RO groups for RACH preamble repetition. The corresponding RO group may correspond to SBFD symbols or non-SBFD symbols, but not both. For example, RACH configuration 300 may correspond to uplink symbol 305 (e.g., a TDD symbol), a first SBFD symbol 310-a, and a second SBFD symbol 310-b. These SBFD symbols can support both uplink and downlink communication. For example, an SBFD symbol can support uplink communication via subband 315 and downlink communication via other frequency resources. The uplink signal-to-interference-plus-noise ratio (SINR) can be different for SBFD symbols compared to TDD symbols. Therefore, having different RO groups for SBFD symbols and TDD symbols reduces complexity by avoiding managing different SINR values ​​for different ROs within the same group.

[0093] RACH configuration 300 may include two distinct SSB indices, SSB index number 0 and SSB index number 1 (or any other number of SSB indices or any other SSB index value). In some aspects, uplink symbol 305 may include four frequency division multiplexing (FDM) ROs, while SBFD symbols may include two FDM ROs within subband 315. RO groups may include RO 320-a with a first SSB index, RO 320-b with a second SSB index, or both. RO groups may include ROs with SSB indices corresponding to the same RACH preamble. For example, if the first SSB index corresponds to a different RACH preamble than the second SSB index, then the RO group may include RO 320-a with the first SSB index or RO 320-b with the second SSB index, but not both. Alternatively, if the first SSB index corresponds to the same RACH preamble as the second SSB index, the RO group may include RO 320-a with the first SSB index, RO 320-b with the second SSB index, or a combination thereof.

[0094] RACH Configuration 300 supports different PRACH sequence formats for TDD RO and SBFD RO. In some respects, RACH Configuration 300 supports different transmit beams for TDD RO and SBFD RO. Additionally or alternatively, RACH Configuration 300 supports different sets of RACH preambles for TDD RO and SBFD RO of the same PRACH format.

[0095] In some aspects, such as Figure 3 As illustrated, RO groups used for PRACH repetition can include the same duplex symbol type. For example, the first and second RO groups can be examples of TDD RO groups (e.g., first TDD RO group 325-a and second TDD RO group 325-b), and can include TDD ROs (but not SBFD ROs). The third and fourth RO groups can be examples of SBFD RO groups (e.g., SBFD RO group 330-a and SBFD RO group 330-b), and can include SBFD ROs (but not TDD ROs). In some such respects, no RO group can span a combination of TDD ROs and SBFD ROs. That is, an RO group can be time-continuous in non-SBFD symbols or SBFD symbols (but not both), using the same frequency resources, and associated with the same one or more SSB indices. A set of valid PRACH opportunities, wherein each SSB index can be associated with the same RACH preamble index used for valid PRACH opportunities within that set.

[0096] In some respects, the number of preamble repetitions can be the same for both TDD RO and SBFD RO. For example, RACH configuration 300 can indicate that the number is two for both TDD and SBFD RO (e.g., The preamble is repeated. The network entity can identify a first TDD RO group 325-a with two TDD ROs, a second TDD RO group 325-b with two TDD ROs, and an SBFD RO group 330-a with two SBFD ROs.

[0097] In some cases, a larger number of consecutive SBFD symbols or slots can be achieved compared to the relatively sparse ROs in uplink (e.g., TDD) symbols or slots. In some aspects, the configuration number of preamble repetitions can be different for TDD ROs and SBFD ROs to efficiently utilize consecutive SBFD symbols. For example, RACH configuration 300 can indicate a number of two ROs for TDD (e.g., ...). The preamble is repeated and the number of ROs for SBFD is four (e.g., Preamble repetition. Network entities can determine a first TDD RO group 325-a with two TDD ROs, a second TDD RO group 325-b with two TDD ROs, and an SBFD RO group 330-b with four SBFD ROs based on different numbers of preamble repetitions. In some aspects, RACH configuration information (e.g., configured by RRC configuration messages or broadcast messages such as SIB1) may include a first field indicating the number of preamble repetitions for TDD ROs and a second field indicating the number of preamble repetitions for SBFD ROs. If the second field is not configured (e.g., the second field is blank, not included, or set to a null value), the network entity can determine to use the number of preamble repetitions for SBFD ROs indicated by the first field (e.g., to use the same number of preamble repetitions in addition to TDD ROs).

[0098] In some respects, RACH configuration 300 can utilize relatively long PRACH sequences to configure SBFD ROs. For example, PRACH sequence formats 0 to 3 can span one or more milliseconds and can include repeating RACH preambles within a single PRACH sequence. Such PRACH sequence formats can provide relatively large cell coverage based on inherent repetition within the format, which may result in further preamble redundancy or inefficiency. In some of these respects, SBFD ROs may not support PRACH repetition. Therefore, groups of ROs used for PRACH repetition may occur in non-SBFD symbols (e.g., uplink symbol 305) instead of in SBFD symbols. Instead, network entities (e.g., SBFD-aware UE 115) can send PRACH messages via SBFD symbols, and a single instance of a PRACH message (e.g., with a relatively long PRACH sequence) can be sent via a single SBFD RO. In some respects, a second network entity (e.g., network entity 105) may send a separate RACH configuration for that network entity (e.g., SBFD-aware UE 115), which indicates a relatively long PRACH sequence and has no preamble repetition for SBFD RO (e.g., ).

[0099] Figure 4 An example of a RACH configuration 400 supporting RACH preamble repetition for SBFD operation is shown, according to one or more aspects of this disclosure. RACH configuration 400 may be as referenced herein. Figure 2 Examples of RACH configuration 230-a or RACH configuration 230-b are described. RACH configuration 400 can support different duplex symbol types (e.g., combinations of SBFD and TDD symbols) within the corresponding RO group. Therefore, multiple instances of network entities sending PRACH messages (such as those referenced herein) Figure 1 and Figure 2 The UE 115 or network entity 205 described may transmit the multiple instances within one or more SBFD ROs, one or more TDD ROs, or a combination thereof.

[0100] RACH configuration 400 (e.g., a single RACH configuration or multiple RACH configurations) can be configured with one or more RO groups for RACH preamble repetition. A corresponding RO group can correspond to any combination of SBFD symbols and non-SBFD symbols. For example, RACH configuration 400 can correspond to a first uplink symbol 405-a (e.g., a TDD symbol), a first SBFD symbol 410-a, a second SBFD symbol 410-b, and a second uplink symbol 405-b. SBFD symbols can support uplink communication via subband 415 and can support downlink communication via other frequency resources. RACH configuration 400 can include two distinct SSB indices, SSB index number 0 and SSB index number 1 (or any other number of SSB indices or any other SSB index value). In some aspects, uplink symbols can include four FDM ROs, while SBFD symbols can include two FDM ROs within subband 415. RO groups can include RO 420-a with a first SSB index, RO 420-b with a second SSB index, or both.

[0101] RACH configuration 400 can support reduced latency for PRACH repetition by utilizing SBFD resources for PRACH repetition. Additionally or alternatively, RACH configuration 400 with PRACH repetition across different duplex symbol types can achieve a relatively larger number of repetitions within the same time period compared to PRACH repetition across the same duplex symbol type. For example, for... A group of valid ROs repeating a RACH preamble can span SBFD symbols, non-SBFD symbols, or both. For example, RACH configuration 400 may include RO group 430, which includes two TDD ROs in the first uplink symbol 405-a and two SBFD ROs in the first SBFD symbol 410-a. These TDD ROs and SBFD ROs may correspond to the same set of frequency resources and SSB indices corresponding to the same RACH preamble. RO groups can be time-contiguous across non-SBFD symbols and / or SBFD symbols, using the same frequency resources, and associated with the same one or more SSB indices. A set of valid PRACH opportunities, wherein each SSB index can be associated with the same RACH preamble index used for valid PRACH opportunities within that set.

[0102] A network entity (e.g., an SBFD-aware UE) can determine whether to support or restrict repetition across different duplex symbol types. In some aspects, a second network entity (e.g., network entity 105) can configure the network entity to support RO groups of different or the same duplex symbol types via higher-layer parameters (e.g., RRC signaling, SIB1). In other aspects, a network entity (e.g., an SBFD-aware UE) can implicitly determine whether an RO group supports different or the same duplex symbol types based on a comparison of PRACH parameters for SBFD RO and TDD RO. For example, if the network entity is configured with different preambles, different transmit beams, different PRACH configurations, different start resource blocks for RO, or any combination thereof, for SBFD and TDD symbols, the RO group may support a single duplex symbol type (e.g., SBFD RO or TDD RO, but not both).

[0103] In some respects, different network entities can determine different RO groups based on RACH configuration 400. For example, RACH configuration 400 can indicate a preamble repetition of four times (e.g., SBFD-aware UEs can receive configuration information for RACH configuration 400 and can determine RO group 430, which includes both TDD RO and SBFD RO. Conversely, non-SBFD-aware UEs (e.g., legacy UEs) can receive the same configuration information for RACH configuration 400 and can determine RO group 425, which includes TDD RO (but not SBFD RO). Because SBFD RO is not a valid PRACH opportunity for non-SBFD-aware UEs, four consecutive valid PRACH opportunities for non-SBFD-aware UEs may include TDD RO in the first uplink symbol 405-a and the second uplink symbol 405-b, while four consecutive valid PRACH opportunities for SBFD-aware UEs may include TDD RO in the first uplink symbol 405-a and SBFD RO in the first SBFD symbol 410-a.

[0104] Figure 5 An example of a RACH configuration 500 supporting RACH preamble repetition for SBFD operation is shown, according to one or more aspects of this disclosure. RACH configuration 500 may be as referenced herein. Figure 2 Examples of RACH configuration 230-a or RACH configuration 230-b are described. RACH configuration 500 can support different duplex symbol types (e.g., combinations of SBFD and TDD symbols) within the corresponding RO group. Therefore, multiple instances of network entities sending PRACH messages (such as those referenced in this document) Figure 1 and Figure 2The UE 115 or network entity 205 described may transmit the multiple instances within one or more SBFD ROs, one or more TDD ROs, or a combination thereof.

[0105] RACH configuration 500 (e.g., a single RACH configuration or multiple RACH configurations) can be configured with one or more RO groups for RACH preamble repetition. A corresponding RO group can correspond to any combination of SBFD symbols and non-SBFD symbols. For example, RACH configuration 500 can correspond to a first uplink symbol 505-a (e.g., a TDD symbol), a first SBFD symbol 510-a, a second SBFD symbol 510-b, and a second uplink symbol 505-b. SBFD symbols can support uplink communication via subband 515 and can support downlink communication via other frequency resources. RACH configuration 500 can include two distinct SSB indices, SSB index number 0 and SSB index number 1 (or any other number of SSB indices or any other SSB index value). In some aspects, uplink symbols can include four FDM ROs, while SBFD symbols can include two FDM ROs within subband 515. RO groups can include RO 520-a with a first SSB index, RO 520-b with a second SSB index, or both.

[0106] In some respects, the configuration information instructing RACH configuration 500 can indicate different numbers of preamble repetitions for SBFD-aware UEs and non-SBFD-aware UEs (e.g., legacy UEs). For example, the configuration information can configure a preamble repetition of eight to the first network entity (e.g., SBFD-aware UE). The configuration information can configure a preamble repetition of up to four times to a second network entity (e.g., a non-SBFD-aware UE). Therefore, the first network entity can determine RO group 530 for RACH preamble repetition for eight PRACH message instances (e.g., based on a preamble repetition of eight), which includes four TDD ROs in the uplink symbols and four SBFD ROs in the SBFD symbols. In contrast, the second network entity can determine RO group 525-a or RO group 525-b for RACH preamble repetition for four PRACH message instances (e.g., based on a preamble repetition of four), which includes four TDD ROs in the uplink symbols.

[0107] In some aspects, configuration information can configure separate preambles for SBFD-aware UEs and non-SBFD-aware UEs via shared ROs. For example, RO group 530 may share a TDD RO with RO group 525-a. However, these RO groups may use different RACH preambles, different numbers of preamble repetitions, or both. In other aspects, configuration information can configure multiple PRACH repetitions for SBFD-aware UEs and non-SBFD-aware UEs via separate ROs. For example, ROs in RO group 530 may be separate from ROs in RO group 525-b (e.g., different, or otherwise non-overlapping). These RO groups may use the same or different RACH preambles, different numbers of preamble repetitions, or any combination thereof.

[0108] Figure 6 An example of a process flow 600 supporting RACH preamble repetition for SBFD operation according to one or more aspects of this disclosure is shown. Process flow 600 may include a first network entity 605 (e.g., UE 115, such as an SBFD-aware UE) and a second network entity 610 (e.g., network entity 105). The second network entity 610 may configure RACH configuration, such as reference, to the first network entity 605. Figures 3 to 5 The RACH configurations described are 300, 400, or 500. A first network entity 605 can perform RACH preamble repetition via SBFD RO based on the RACH configuration. In the following description of process flow 600, the operations performed by the first network entity 605 and the second network entity 610 may be performed in a different order than shown. Some operations may be omitted from process flow 600, and other operations may be added to process flow 600. Furthermore, although some operations or signaling are shown as occurring at different times for discussion purposes, these operations may occur simultaneously. Additionally or alternatively, other network devices may perform aspects of process flow 600.

[0109] In some aspects, at 615, the second network entity 610 may send information indicating whether the RO group supports different duplex symbol types. For example, this information may indicate that the RO group supports a single identical duplex symbol type (e.g., the RO group has SBFD RO or TDD RO, but not both). Alternatively, this information may indicate that the RO group supports different duplex symbol types (e.g., the RO group may include both SBFD RO and TDD RO). In some aspects, the second network entity 610 may send information with RACH configuration information, for example, in an RRC message or SIB1 signaling. The first network entity 605 may receive this information and determine, based on this information, whether the RO group supports the same duplex symbol type or different duplex symbol types.

[0110] At point 620, the second network entity 610 may send RACH configuration information. In some aspects, the RACH configuration information may be included within an RRC message or SIB1 signaling. The first network entity 605 may receive the RACH configuration information and determine the RO groups for PRACH transmission based on the RACH configuration information. The RACH configuration information may indicate the RO groups and the number of preamble repetitions. For example, the RACH configuration information may be configured or otherwise indicate the set of ROs corresponding to the RO groups and a value indicating the number of preamble repetitions. A group of ROs may include a set of valid PRACH moments (e.g., time-sequential) having a certain number of ROs equal to the number of preamble repetitions.

[0111] The set of valid PRACH timings may include at least one SBFD RO valid for PRACH transmission. In some aspects, the RO group for the first network entity 605 may be an example of a first RO group including SBFD ROs, and RACH configuration information may indicate a second RO group including TDD ROs. In some such aspects, the first and second RO groups may correspond to different PRACH transmission parameters, such as different PRACH sequence formats, different transmission beams, different transmission powers, different sets of frequency resources, different RACH preambles, different numbers of preamble repetitions, or any combination thereof. In some other aspects, the RO group may include one or more SBFD ROs and one or more TDD ROs.

[0112] In some respects, at 625, the first network entity 605 may determine whether an RO group supports different duplex symbol types based on a comparison of PRACH parameters configured for SBFD symbols and for non-SBFD parameters. For example, if the RACH configuration information indicates different PRACH parameters for SBFD symbols and non-SBFD symbols (e.g., TDD symbols), the first network entity 605 may implicitly determine that the RO group corresponds to a single, identical duplex symbol type (e.g., the RO group includes either SBFD RO or TDD RO). If the RACH configuration information indicates the same PRACH parameters for SBFD symbols and non-SBFD symbols (e.g., TDD symbols), the first network entity 605 may implicitly determine that the RO group may correspond to different duplex symbol types (e.g., the RO group may include both SBFD RO and TDD RO).

[0113] At 630, the first network entity 605 can send a set of multiple instances of the PRACH message via the RO group based on the number of preamble repetitions. For example, the first network entity 605 can send the corresponding PRACH message instance via each valid RO in the RO group. In this way, the first network entity 605 can send a configured number equal to the number of preamble repetitions (e.g., a value...). ,in A first network entity 605 may transmit a certain number of PRACH message instances. A PRACH message instance may include a RACH message (e.g., the preamble portion of RACH Msg1 or RACH MsgA), a portion of a RACH message, a RACH preamble sequence, or any combination thereof. The first network entity 605 may transmit the corresponding PRACH message instance using the same PRACH transmission parameters configured via RACH configuration information. For example, the first network entity 605 may transmit each instance of a PRACH message using the same PRACH sequence format, the same transmission beam, the same transmission power, the same set of frequency resources, the same RACH preamble, or any combination thereof. In some aspects, the first network entity 605 may transmit multiple PRACH message instances before monitoring RAR messages in response to that instance. The second network entity 610 may receive one or more PRACH message instances from the PRACH message instances.

[0114] At 635, the first network entity 605 may monitor RAR timing for RAR messages. For example, a set of multiple instances of PRACH messages may correspond to a single RAR timing or RAR window. The first network entity 605 may send multiple PRACH message instances as part of a single random access attempt, and in response, may monitor a single RAR message. At 640, the second network entity 610 may send a RAR message in response to at least one PRACH message instance. The first network entity 605 may receive RAR messages based on monitoring a single RAR timing or RAR window. The RAR message may be an example of RACH Msg2 or RACH MsgB. The first network entity 605 and the second network entity 610 may complete the random access procedure based on the RAR messages.

[0115] Figure 7 A block diagram 700 illustrates a device 705 supporting RACH preamble repetition for SBFD operation according to one or more aspects of this disclosure. Device 705 may be an example of aspects of a network entity (such as UE 115 or network entity 105) as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705, or one or more components of device 705 (e.g., receiver 710, transmitter 715, communication manager 720), 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).

[0116] Receiver 710 may provide components for receiving or otherwise acquiring 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 RACH preamble repetition for SBFD operation). The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a collection of antennas.

[0117] Transmitter 715 may provide components for transmitting or otherwise outputting signals generated by other components of device 705. For example, transmitter 715 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with RACH preamble repetition for SBFD operation), such as packets, user data, control information, or any combination thereof. In some aspects, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0118] The communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be examples of components used to perform various aspects of RACH preamble repetition for SBFD operation as described herein. For example, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0119] In some aspects, the communication manager 720, receiver 710, transmitter 715, 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 jointly to support components for performing the functions described herein. In some aspects, 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 jointly by one or more processors).

[0120] Additionally or alternatively, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be implemented in code (e.g., referred to as processor executable code) executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 720, receiver 710, transmitter 715, 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).

[0121] In some respects, the communication manager 720 may be configured to use or otherwise cooperate with the receiver 710, transmitter 715, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or be integrated with the receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0122] Communication manager 720 can support wireless communication according to examples disclosed herein. For example, communication manager 720 is capable of, configured to, or operable to support components for receiving configuration information for PRACH transmission, wherein the configuration information indicates RO groups and the number of preamble repetitions, wherein the RO groups include a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for PRACH transmission. Communication manager 720 is capable of, configured to, or operable to support components for a set of multiple instances of transmitting PRACH messages via RO groups based on the number of preamble repetitions.

[0123] By including or configuring a communication manager 720 according to examples as described herein, device 705 (e.g., controlling receiver 710, transmitter 715, communication manager 720, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for reducing processing associated with random access procedures and for more efficient use of communication resources. For example, device 705 can improve the reliability of random access procedures by supporting preamble repetition via SBFD resources, thereby reducing processing resources for random access procedures that fail to repeat. Additionally or alternatively, device 705 can improve resource utilization by using SBFD symbols in random access procedures.

[0124] Figure 8A block diagram 800 of a device 805 supporting RACH preamble repetition for SBFD operation according to one or more aspects of this disclosure is shown. Device 805 may be an example of aspects of a device 705 as described herein or a network entity such as UE 115 or wireless device 105. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805 or one or more components of device 805 (e.g., receiver 810, transmitter 815, communication manager 820) 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).

[0125] Receiver 810 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 RACH preamble repetition for SBFD operation). The information may be passed to other components of device 805. Receiver 810 may utilize a single antenna or a collection of antennas.

[0126] Transmitter 815 may provide components for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with RACH preamble repetition for SBFD operation), such as packets, user data, control information, or any combination thereof. In some aspects, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0127] Device 805 or its various components may be examples of parts for performing various aspects of RACH preamble repetition for SBFD operations as described herein. For example, communication manager 820 may include RACH configuration component 825, PRACH communication component 830, or any combination thereof. Communication manager 820 may be examples of various aspects of communication manager 720 as described herein. In some aspects, communication manager 820 or its various components may be configured to use or otherwise cooperate with receiver 810, transmitter 815, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 820 may receive information from receiver 810, transmit information to transmitter 815, or be integrated in combination with receiver 810, transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0128] Communication manager 820 can support wireless communication according to the examples disclosed herein. RACH configuration component 825 is capable of, configured to, or operable to support components for receiving configuration information for PRACH transmission, wherein the configuration information indicates RO groups and the number of preamble repetitions, wherein the RO groups comprise a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for PRACH transmission. PRACH communication component 830 is capable of, configured to, or operable to support components for a set of multiple instances of transmitting PRACH messages via RO groups based on the number of preamble repetitions.

[0129] Additionally or alternatively, the RACH configuration component 825 is capable of, configured to, or operable to support components for enabling the transmission of configuration information for PRACH transmission, wherein the configuration information indicates the number of RO groups and preamble repetitions, wherein the RO groups comprise a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for PRACH transmission. The PRACH communication component 830 is capable of, configured to, or operable to support components for receiving at least one instance of a set of multiple instances of PRACH messages via RO groups based on the number of preamble repetitions.

[0130] Figure 9 A block diagram 900 is shown of a communication manager 920 supporting RACH preamble repetition for SBFD operation according to one or more aspects of this disclosure. The communication manager 920 may be an example of a communication manager 720, a communication manager 820, or aspects thereof as described herein. The communication manager 920 or its various components may be examples of parts for performing various aspects of RACH preamble repetition for SBFD operation as described herein. For example, the communication manager 920 may include a RACH configuration component 925, a PRACH communication component 930, a duplex symbol support component 935, a RAR component 940, 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).

[0131] Communication manager 920 can support wireless communication according to the examples disclosed herein. RACH configuration component 925 is capable of, configured to, or operable to support components for receiving configuration information for PRACH transmission, wherein the configuration information indicates RO groups and the number of preamble repetitions, wherein the RO groups include a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for PRACH transmission. PRACH communication component 930 is capable of, configured to, or operable to support components for a set of multiple instances of transmitting PRACH messages via RO groups based on the number of preamble repetitions.

[0132] In some aspects, the RO group is a first RO group, wherein the first RO group includes SBFD ROs. In some such aspects, the configuration information further indicates a second RO group, wherein the second RO group includes TDD ROs. In some aspects, the configuration information separately indicates: a first PRACH sequence format, a first transmit beam, a first set of frequency resources, a first RACH preamble, or any combination thereof, corresponding to the first RO group; and a second PRACH sequence format different from the first PRACH sequence format, a second transmit beam different from the first transmit beam, a second set of frequency resources different from the first set of frequency resources, a second RACH preamble different from the first RACH preamble, or any combination thereof, corresponding to the second RO group. In some aspects, the number of preamble repetitions is a first number of preamble repetitions for SBFD ROs. In some such aspects, the configuration information separately indicates a second number of preamble repetitions for TDD ROs.

[0133] In some respects, the configuration information indicates for the first RO group and the second RO group the same PRACH sequence format, the same transmit beam, the same set of frequency resources, the same RACH preamble, or any combination thereof. In some respects, the number of preamble repetitions corresponds to both the first RO group and the second RO group.

[0134] In some respects, the RO group includes at least one SBFD RO and at least one TDD RO.

[0135] In some aspects, the duplex symbol support component 935 is capable of, configured to, or operable to support components for receiving information indicating that the RO group supports the same duplex symbol type. In other aspects, the duplex symbol support component 935 is capable of, configured to, or operable to support components for receiving information indicating that the RO group supports different duplex symbol types.

[0136] In some aspects, the duplex symbol support component 935 is capable of, can be configured to, or is operable to support components used for determining whether the RO group supports the same or different duplex symbol types based on a comparison of PRACH parameters configured for SBFD symbols and for non-SBFD symbols. In some aspects, PRACH parameters include PRACH sequence format, transmit beam, set of frequency resources, RACH preamble, or any combination thereof.

[0137] In some aspects, the number of preamble repetitions is a first number of preamble repetitions for a network entity that supports at least one SBFDRO valid for PRACH transmission. In some aspects, the configuration information further indicates a second number of preamble repetitions for a second network entity that fails to recognize (e.g., is not recognized or otherwise disregarded) a valid SBFD RO for PRACH transmission. In some aspects, the RO group for the network entity shares one or more ROs with a second RO group for the second network entity. In some such aspects, the RO group and the second RO group correspond to different RACH preambles for one or more shared ROs. In some other aspects, a first corresponding RO in the RO group for the network entity differs from a second corresponding RO in the second RO group for the second network entity.

[0138] In some aspects, RAR component 940 is capable of, configured to, or operable to support components for receiving RAR messages for at least one instance of a set of multiple instances based on PRACH messages. In some aspects, the set of multiple instances of PRACH messages corresponds to a single RAR, and RAR component 940 is capable of, configured to, or operable to support components for monitoring RAR messages via monitoring timing associated with the single RAR.

[0139] In some aspects, at least one SBFD RO is configured within a subband for uplink transmission within an SBFD symbol. In some aspects, the set of valid PRACH opportunities includes a set of multiple PRACH opportunities that span the same set of frequency resources, correspond to the same transmit beam, correspond to the same transmit power, correspond to the same RACH preamble, or correspond to the same duplex symbol type.

[0140] In some aspects, configuration information includes RRC signals or SIBs.

[0141] In some respects, the set of multiple instances of a PRACH message is equal to the number of preamble repetitions. In some respects, the number of preamble repetitions is greater than one. In some respects, the set of valid PRACH opportunities is equal to the number of preamble repetitions.

[0142] Additionally or alternatively, according to the examples disclosed herein, the communication manager 920 may support wireless communication. The RACH configuration component 925 is capable of, configured to, or operable to support components for enabling the transmission of configuration information for PRACH transmission, wherein the configuration information indicates RO groups and the number of preamble repetitions, wherein the RO groups comprise a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for PRACH transmission. The PRACH communication component 930 is capable of, configured to, or operable to support components for receiving at least one instance of a set of multiple instances of PRACH messages via RO groups based on the number of preamble repetitions.

[0143] In some respects, the RO group is the first RO group, which includes SBFD RO, and the configuration information further indicates the second RO group, which includes TDD RO.

[0144] In some aspects, the configuration information separately indicates: a first PRACH sequence format, a first transmit beam, a first set of frequency resources, a first RACH preamble, or any combination thereof, corresponding to a first RO group; and a second PRACH sequence format different from the first PRACH sequence format, a second transmit beam different from the first transmit beam, a second set of frequency resources different from the first set of frequency resources, a second RACH preamble different from the first RACH preamble, or any combination thereof, corresponding to a second RO group. In some aspects, the number of preamble repetitions is a first number of preamble repetitions for SBFD RO. In some such aspects, the configuration information separately indicates a second number of preamble repetitions for TDD RO. In some aspects, the number of preamble repetitions is a first number of preamble repetitions for SBFD RO, and the configuration information separately indicates a second number of preamble repetitions for TDD RO.

[0145] In some respects, the configuration information indicates for the first RO group and the second RO group the same PRACH sequence format, the same transmit beam, the same set of frequency resources, the same RACH preamble, or any combination thereof. In some respects, the number of preamble repetitions corresponds to both the first RO group and the second RO group.

[0146] In some aspects, configuration information includes RRC signals or SIBs.

[0147] Figure 10A diagram of a system 1000 including device 1005 supporting RACH preamble repetition for SBFD operation is shown, according to one or more aspects of this disclosure. Device 1005 may be an example of device 705, device 805, or network entity (such as UE 115 or network entity 105) as described herein, or a component including such devices. Device 1005 may communicate with one or more other devices (e.g., network entities, such as network entity 105, UE 115, or combinations thereof) (e.g., wirelessly). Device 1005 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1020, an input / output (I / O) controller (such as I / O controller 1010), a transceiver 1015, one or more antennas 1025, at least one memory 1030, code 1035, and at least one processor 1040. These components may be electronically communicated or otherwise coupled via one or more buses (e.g., bus 1045).

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

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

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

[0151] At least one processor 1040 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 1040 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 1040. At least one processor 1040 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1030) to cause device 1005 to perform various functions (e.g., functions or tasks supporting RACH preamble repetition for SBFD operations). For example, device 1005 or components thereof may include at least one processor 1040 and at least one memory 1030 coupled to or coupled to the at least one processor 1040, the at least one processor 1040 and the at least one memory 1030 being configured to perform the various functions described herein.

[0152] In some aspects, at least one processor 1040 may include multiple processors, and at least one memory 1030 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 aspects, at least one processor 1040 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1040) and memory circuitry (which may include at least one memory 1030)) or components that receive or receive 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 1040 or a processing system including at least one processor 1040 may be configured, capable of being configured, or operable to cause device 1005 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” can be used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code 1035 (e.g., processor-executable code) stored in at least one memory 1030 or otherwise executing the code.

[0153] Communication manager 1020 can support wireless communication according to the examples disclosed herein. For example, communication manager 1020 is capable of, configured to, or operable to support components for receiving configuration information for PRACH transmission, wherein the configuration information indicates RO groups and the number of preamble repetitions, wherein the RO groups include a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for PRACH transmission. Communication manager 1020 is capable of, configured to, or operable to support components for a set of multiple instances for transmitting PRACH messages via RO groups based on the number of preamble repetitions.

[0154] Additionally or alternatively, the communication manager 1020 is capable of, configured to, or operable to support components for enabling the transmission of configuration information for PRACH transmission, wherein the configuration information indicates RO groups and the number of preamble repetitions, wherein the RO groups comprise a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for PRACH transmission. The communication manager 1020 is capable of, configured to, or operable to support components for receiving at least one instance of a set of multiple instances of PRACH messages via RO groups based on the number of preamble repetitions.

[0155] By including or configuring a communication manager 1020 according to an example as described herein, device 1005 can support techniques for improving communication reliability (e.g., including improving connection establishment via random access procedures), reducing latency of random access procedures, and more efficiently utilizing communication resources (e.g., including SBFD symbol resources).

[0156] In some aspects, the communication manager 1020 may be configured to use or otherwise coordinate with the transceiver 1015, one or more antennas 1025, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 1020 is illustrated as a separate component, in some aspects, one or more functions described with reference to the communication manager 1020 may be supported or executed by at least one processor 1040, at least one memory 1030, code 1035, or any combination thereof. For example, code 1035 may include instructions that can be executed by at least one processor 1040 to cause the device 1005 to perform various aspects of RACH preamble repetition for SBFD operation as described herein, or at least one processor 1040 and at least one memory 1030 may be otherwise configured to perform or support such operations individually or jointly.

[0157] Figure 11A flowchart illustrating a method 1100 for supporting RACH preamble repetition for SBFD operation, according to one or more aspects of this disclosure, is shown. The operation of method 1100 may be implemented by a network entity (e.g., a UE) or its components as described herein. For example, the operation of method 1100 may be implemented by, as referenced... Figures 1 to 10 The network entity described herein performs the function. In some aspects, 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.

[0158] At 1105, the method may include: receiving configuration information for PRACH transmission, wherein the configuration information indicates RO groups and the number of preamble repetitions, wherein the RO groups include a set of valid PRACH timings based on the number of preamble repetitions, and wherein the set of valid PRACH timings includes at least one SBFD RO valid for PRACH transmission. The set of valid PRACH timings includes a certain number of PRACH timings equal to the number of preamble repetitions, and the set of valid PRACH timings may be based on the number of preamble repetitions. The operation of 1105 may be performed according to the examples disclosed herein. In some aspects, aspects of the operation of 1105 may be derived from references... Figure 9 The described RACH configuration component 925 is executed.

[0159] At 1110, the method may include: a set of multiple instances of sending a PRACH message via the RO group based on the number of preamble repetitions. The operation of 1110 may be performed according to the examples disclosed herein. In some aspects, aspects of the operation of 1110 may be derived from references... Figure 9 The described PRACH communication component 930 is executed.

[0160] Figure 12 A flowchart illustrating a method 1200 for supporting RACH preamble repetition for SBFD operation, according to one or more aspects of this disclosure, is shown. The operation of method 1200 can be implemented by a network entity (e.g., a UE) or its components as described herein. For example, the operation of method 1200 can be implemented by, as referenced... Figures 1 to 10 The network entity described herein performs the function. In some aspects, 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.

[0161] In some aspects, at 1205, the method may include: receiving information indicating whether the RO group supports different duplex symbol types. The operation of 1205 may be performed according to the examples disclosed herein. In some aspects, aspects of the operation of 1205 may be derived from references... Figure 9 The described duplex symbol supports component 935 for execution.

[0162] At 1210, the method may include: receiving configuration information for PRACH transmission, wherein the configuration information indicates RO groups and the number of preamble repetitions, wherein the RO groups comprise a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for PRACH transmission. The operation of 1210 may be performed according to the examples disclosed herein. In some aspects, aspects of the operation of 1210 may be derived from references... Figure 9 The described RACH configuration component 925 is executed.

[0163] In some aspects, at 1215, the method may include: determining whether the RO group supports different duplex symbol types based on a comparison of PRACH parameters configured for SBFD symbols and for non-SBFD symbols. The operation of 1215 may be performed according to examples as disclosed herein. In some aspects, aspects of the operation of 1215 may be derived from references... Figure 9 The described duplex symbol supports component 935 for execution.

[0164] At 1220, the method may include: a set of multiple instances of sending a PRACH message via the RO group based on the number of preamble repetitions. The operation of 1220 may be performed according to the examples disclosed herein. In some aspects, aspects of the operation of 1220 may be derived from references... Figure 9 The described PRACH communication component 930 is executed.

[0165] Figure 13 A flowchart illustrating a method 1300 for supporting RACH preamble repetition for SBFD operation, according to one or more aspects of this disclosure, is shown. The operation of method 1300 may be implemented by a network entity (e.g., a UE) or its components as described herein. For example, the operation of method 1300 may be implemented by, as referenced... Figures 1 to 10 The network entity described herein performs the function. In some aspects, 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.

[0166] At 1305, the method may include: receiving configuration information for PRACH transmission, wherein the configuration information indicates RO groups and the number of preamble repetitions, wherein the RO groups comprise a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for PRACH transmission. The operation of 1305 may be performed according to the examples disclosed herein. In some aspects, aspects of the operation of 1305 may be derived from references... Figure 9 The described RACH configuration component 925 is executed.

[0167] At 1310, the method may include: a set of multiple instances of sending a PRACH message via a RO group based on the number of preamble repetitions. The operation of 1310 may be performed according to the examples disclosed herein. In some aspects, aspects of the operation of 1310 may be derived from references... Figure 9 The described PRACH communication component 930 is executed.

[0168] At 1315, the method may include: monitoring a RAR message via a monitoring timing associated with a single RAR of a set of multiple instances of a PRACH message. The operation of 1315 may be performed according to examples as disclosed herein. In some aspects, aspects of the operation of 1315 may be derived from references... Figure 9 The described RAR component 940 is executed.

[0169] At 1320, the method may include: receiving a RAR message from at least one instance of a set of multiple instances of a PRACH message. The operation of 1320 may be performed according to examples as disclosed herein. In some aspects, aspects of the operation of 1320 may be derived from references... Figure 9 The described RAR component 940 is executed.

[0170] Figure 14 A flowchart illustrating a method 1400 for supporting RACH preamble repetition for SBFD operation according to one or more aspects of this disclosure is shown. The operation of method 1400 can be implemented by a network entity (e.g., a base station or other network node) or its components as described herein. For example, the operation of method 1400 can be implemented by, as referenced... Figures 1 to 10 The network entity described herein performs the function. In some aspects, 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.

[0171] At 1405, the method may include: causing configuration information for PRACH transmission to be transmitted, wherein the configuration information indicates RO groups and the number of preamble repetitions, wherein the RO groups comprise a set of valid PRACH timings based on the number of preamble repetitions, and wherein the set of valid PRACH timings comprises at least one SBFD RO valid for PRACH transmission. The set of valid PRACH timings comprises a certain number of PRACH timings equal to the number of preamble repetitions, the set of valid PRACH timings being based on the number of preamble repetitions. The operation of 1405 may be performed according to the examples disclosed herein. In some aspects, aspects of the operation of 1405 may be derived from references... Figure 9 The described RACH configuration component 925 is executed.

[0172] At 1410, the method may include: receiving at least one instance from a set of multiple instances receiving PRACH messages via the RO group based on the number of preamble repetitions. The operation of 1410 may be performed according to the examples disclosed herein. In some aspects, aspects of the operation of 1410 may be derived from references... Figure 9 The described PRACH communication component 930 is executed.

[0173] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication performed by a network entity, the method comprising: receiving configuration information for PRACH transmission, wherein the configuration information indicates RO groups and a number of preamble repetitions, wherein the RO groups include a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for the PRACH transmission; and a plurality of instances of transmitting PRACH messages via the RO groups based on the number of preamble repetitions.

[0174] Aspect 2: According to the method of aspect 1, the RO group is a first RO group, wherein the first RO group includes SBFD RO; and the configuration information further indicates a second RO group, wherein the second RO group includes TDD RO.

[0175] Aspect 3: According to the method of aspect 2, wherein the configuration information individually indicates: a first PRACH sequence format, a first transmit beam, a first set of frequency resources, a first RACH preamble, or any combination thereof, corresponding to the first RO group, and a second PRACH sequence format different from the first PRACH sequence format, a second transmit beam different from the first transmit beam, a second set of frequency resources different from the first set of frequency resources, a second RACH preamble different from the first RACH preamble, or any combination thereof, corresponding to the second RO group.

[0176] Aspect 4: The method according to any one of Aspect 2 or 3, wherein the number of preamble repetitions is a first number of preamble repetitions for the SBFD RO; and the configuration information separately indicates a second number of preamble repetitions for the TDD RO.

[0177] Aspect 5: According to the method of aspect 2, wherein the configuration information indicates the same PRACH sequence format, the same transmit beam, the same set of frequency resources, the same RACH preamble, or any combination thereof for the first RO group and the second RO group.

[0178] Aspect 6: The method according to any one of Aspect 2 or 5, wherein the number of preamble repetitions corresponds to both the first RO group and the second RO group.

[0179] Aspect 7: According to the method of aspect 1, the RO group includes at least one SBFD RO and at least one TDD RO.

[0180] Aspect 8: The method according to any one of aspects 1 to 6, the method further comprising: receiving information indicating that the RO group supports the same duplex symbol type.

[0181] Aspect 9: The method according to any one of Aspect 1 or 7, the method further comprising: receiving information indicating that the RO group supports different duplex symbol types.

[0182] Aspect 10: The method according to any one of Aspects 1 to 7, the method further comprising: determining, based on a comparison of PRACH parameters configured for SBFD symbols and for non-SBFD symbols, whether the RO group supports the same duplex symbol type or different duplex symbol types.

[0183] Aspect 11: The method according to aspect 10, wherein the PRACH parameters include a PRACH sequence format, a transmission beam, a set of frequency resources, a RACH preamble, or any combination thereof.

[0184] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the number of preamble repetitions is a first number of preamble repetitions for the network entity that supports the transmission of the at least one SBFD RO valid for the PRACH; and the configuration information further indicates a second number of preamble repetitions for a second network entity that fails to identify the transmission of the SBFD RO valid for the PRACH.

[0185] Aspect 13: According to the method of aspect 12, wherein the RO group for the network entity shares one or more ROs with the second RO group for the second network entity; and the RO group and the second RO group correspond to different RACH preambles for the one or more shared ROs.

[0186] Aspect 14: The method according to aspect 12, wherein the first corresponding RO in the RO group for the network entity is different from the second corresponding RO in the second RO group for the second network entity.

[0187] Aspect 15: The method according to any one of aspects 1 to 14, the method further comprising: receiving a RAR message based on at least one of the plurality of instances of the PRACH message.

[0188] Aspect 16: The method according to aspect 15, wherein the plurality of instances of the PRACH message correspond to a single RAR, the method further comprising: monitoring the RAR message via a monitoring timing associated with the single RAR.

[0189] Aspect 17: The method according to any one of Aspects 1 to 16, wherein the at least one SBFD RO is configured for uplink transmission within a subband of the SBFD symbol.

[0190] Aspect 18: The method according to any one of Aspects 1 to 17, wherein the set of valid PRACH timings includes a plurality of PRACH timings that span the same set of frequency resources, correspond to the same transmit beam, correspond to the same transmit power, correspond to the same RACH preamble, or correspond to the same duplex symbol type.

[0191] Aspect 19: The method according to any one of Aspects 1 to 18, wherein the configuration information includes an RRC signal or an SIB.

[0192] Aspect 20: The method according to any one of aspects 1 to 19, wherein the number of the plurality of instances of the PRACH message is equal to the number of preamble repetitions.

[0193] Aspect 21: The method according to any one of aspects 1 to 20, wherein the number of preamble repetitions is greater than one.

[0194] Aspect 22: The method according to any one of aspects 1 to 21, wherein the number of opportunities in the set of valid PRACH opportunities is equal to the number of preamble repetitions.

[0195] Aspect 23: A network entity for wireless communication, the network entity comprising: a processing system configured to perform the method according to any one of aspects 1 to 22.

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

[0197] Aspect 25: A non-transitory computer-readable medium having stored thereon code for wireless communication, said code causing the network entity to perform the method according to any one of aspects 1 to 22 when executed by the network entity.

[0198] Aspect 26: A method for wireless communication performed by a network entity, the method comprising: causing the transmission of configuration information for PRACH transmission, wherein the configuration information indicates RO groups and a number of preamble repetitions, wherein the RO groups include a set of valid PRACH opportunities based on the number of preamble repetitions, and wherein the set of valid PRACH opportunities includes at least one SBFD RO valid for the PRACH transmission; and at least one instance of a plurality of instances of receiving a PRACH message via the RO groups based on the number of preamble repetitions.

[0199] Aspect 27: The method according to aspect 26, wherein: the RO group is a first RO group, wherein the first RO group includes SBFD RO; and the configuration information further indicates a second RO group, wherein the second RO group includes TDD RO.

[0200] Aspect 28: According to the method of aspect 27, wherein the configuration information individually indicates: a first PRACH sequence format, a first transmit beam, a first set of frequency resources, a first RACH preamble, or any combination thereof, corresponding to the first RO group, and a second PRACH sequence format different from the first PRACH sequence format, a second transmit beam different from the first transmit beam, a second set of frequency resources different from the first set of frequency resources, a second RACH preamble different from the first RACH preamble, or any combination thereof, corresponding to the second RO group.

[0201] Aspect 29: The method according to any one of Aspects 27 or 28, wherein the number of preamble repetitions is a first number of preamble repetitions for the SBFD RO; and the configuration information separately indicates a second number of preamble repetitions for the TDD RO.

[0202] Aspect 30: The method according to aspect 27, wherein the configuration information indicates the same PRACH sequence format, the same transmit beam, the same set of frequency resources, the same RACH preamble, or any combination thereof for the first RO group and the second RO group.

[0203] Aspect 31: The method according to any one of Aspects 27 or 30, wherein the number of preamble repetitions corresponds to both the first RO group and the second RO group.

[0204] Aspect 32: The method according to any one of Aspects 26 to 31, wherein the configuration information includes an RRC signal or an SIB.

[0205] Aspect 33: A network entity for wireless communication, the network entity comprising: a processing system configured to perform the method according to any one of aspects 26 to 32.

[0206] Aspect 34: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 26 to 32.

[0207] Aspect 35: A non-transitory computer-readable medium having stored thereon code for wireless communication, the code causing the network entity to perform the method according to any one of aspects 26 to 32 when executed by the network entity.

[0208] The methods described herein outline possible specific implementations. Operations and steps may be rearranged or otherwise modified, and other specific implementations are possible. Furthermore, aspects from two or more of these methods can be combined.

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

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

[0211] 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 combined 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.

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

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

[0214] As used herein, the term "or" is inclusive unless restrictive language is used relative to the listed alternatives. For example, a reference to "X is based on A or B" should be interpreted as including, within its scope, X is based on A, X is based on B, and X is based on both A and B. In this respect, a reference to "X is based on A or B" means "at least one of A or B" or "one or more of A or B," because "or" is inclusive. Similarly, a reference to "X is based on A, B, or C" should be interpreted as including, within its scope, X is based on A, X is based on B, X is based on C, X is based on both A and B, X is based on both A and C, X is based on both B and C, and X is based on both A, B, and C. In this respect, a reference to "X is based on A, B, or C" means "at least one of A, B, or C" or "one or more of A, B, or C," because "or" is inclusive. As an example of restrictive language, a reference to “X is based on either A or B” should be interpreted as including, within its scope, both X based on A and X based on B, but excluding X based on both A and B. Furthermore, as used herein, the phrase “based on” should not be interpreted as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless specifically stated otherwise. Additionally, unless specifically disclosed otherwise, “set” refers to one or more items (e.g., a set of multiple items), and unless specifically disclosed otherwise, “subset” refers to a non-empty portion smaller than the whole set (e.g., a subset of zero or more items in a set of one or more items).

[0215] 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” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as 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” can 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".

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

[0217] 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 reference numeral to differentiate between similar components. If only the first reference numeral is used in the description, the description applies to any of the similar components having the same first reference numeral, regardless of the second reference numeral or other subsequent reference numerals.

[0218] The description herein, illustrated in conjunction with the accompanying drawings, describes exemplary configurations and does not represent all examples that can be implemented or that are within the scope of the claims. The terms "aspect" or "example" as used herein mean "used as an aspect, example, instance, or illustration," and not "preferred" or "advantageous over other aspects." 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 of the drawings, structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0219] 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 network entity for wireless communication, the network entity comprising: Processing system, the processing system being configured to: Receive configuration information for physical random access channel transmission, wherein the configuration information indicates a random access channel timing group and a number of preamble repetitions, wherein the random access channel timing group comprises a set of valid physical random access channel timings according to the number of preamble repetitions, and wherein the set of valid physical random access channel timings includes at least one subband non-overlapping full-duplex (SBFD) random access channel timing valid for the physical random access channel transmission; and Multiple instances of physical random access channel messages are sent via the random access channel timing group based on the number of preamble repetitions.

2. The network entity according to claim 1, wherein: The random access channel timing group is a first random access channel timing group, wherein the first random access channel timing group includes SBFD random access channel timing; and The configuration information further indicates a second random access channel timing group, wherein the second random access channel timing group includes time division duplex (TDD) random access channel timings.

3. The network entity according to claim 2, wherein the configuration information specifically indicates: The first physical random access channel sequence format, the first transmit beam, the first set of frequency resources, the first random access channel preamble, or any combination thereof, corresponding to the first random access channel timing group, and The second physical random access channel sequence format that is different from the first physical random access channel sequence format, the second transmission beam that is different from the first transmission beam, the second set of frequency resources that is different from the first set of frequency resources, the second random access channel preamble that is different from the first random access channel preamble, or any combination thereof.

4. The network entity according to claim 2, wherein: The number of preamble repetitions is a first number of preamble repetitions for the timing of the SBFD random access channel; and The configuration information specifically indicates a second number of preamble repetitions for the TDD random access channel timing.

5. The network entity of claim 2, wherein the configuration information indicates, for the first random access channel timing group and the second random access channel timing group, the same physical random access channel sequence format, the same transmit beam, the same set of frequency resources, the same random access channel preamble, or any combination thereof.

6. The network entity of claim 2, wherein the number of preamble repetitions corresponds to both the first random access channel timing group and the second random access channel timing group.

7. The network entity according to claim 1, wherein: The number of preamble repetitions is a first number of preamble repetitions for the network entity that supports the transmission of the at least one SBFD random access channel timing valid for the physical random access channel; and The configuration information further indicates a second number of preamble repetitions for a second network entity that failed to identify a valid SBFD random access channel timing for the physical random access channel.

8. The network entity according to claim 7, wherein: The random access channel timing group for the network entity and the second random access channel timing group for the second network entity share one or more random access channel timings; and The random access channel timing group and the second random access channel timing group correspond to different random access channel preambles used for the one or more shared random access channel timings.

9. The network entity of claim 7, wherein the first corresponding random access channel timing in the random access channel timing group for the network entity is different from the second corresponding random access channel timing in the second random access channel timing group for the second network entity.

10. The network entity of claim 1, wherein the processing system is configured to: The random access response message is received based on at least one of the plurality of instances of the physical random access channel message.

11. The network entity of claim 10, wherein the plurality of instances of the physical random access channel message correspond to a single random access response, and the processing system is configured to: The random access response message is monitored via a monitoring timing associated with the individual random access response.

12. The network entity of claim 1, wherein the at least one SBFD random access channel timing is within a subband configured for uplink transmission within the SBFD symbol.

13. The network entity of claim 1, wherein the set of valid physical random access channel opportunities comprises a plurality of physical random access channel opportunities, the plurality of physical random access channel opportunities spanning the same set of frequency resources, corresponding to the same transmit beam, corresponding to the same transmit power, corresponding to the same random access channel preamble, or corresponding to the same duplex symbol type.

14. The network entity of claim 1, wherein the configuration information includes radio resource control signals or system information blocks.

15. The network entity of claim 1, wherein the number of the plurality of instances of the physical random access channel message is equal to the number of preamble repetitions.

16. The network entity of claim 1, wherein the number of preamble repetitions is greater than one.

17. The network entity of claim 1, wherein the number of opportunities in the set of valid physical random access channel opportunities is equal to the number of preamble repetitions.

18. A network entity for wireless communication, the network entity comprising: Processing system, the processing system being configured to: This enables the transmission of configuration information for physical random access channel transmission, wherein the configuration information indicates a random access channel timing group and a number of preamble repetitions, wherein the random access channel timing group includes a set of valid physical random access channel timings according to the number of preamble repetitions, and wherein the set of valid physical random access channel timings includes at least one subband non-overlapping full-duplex (SBFD) random access channel timing valid for the transmission of the physical random access channel. as well as At least one instance of receiving physical random access channel messages via the random access channel timing group based on the number of preamble repetitions.

19. The network entity according to claim 18, wherein: The random access channel timing group is a first random access channel timing group, wherein the first random access channel timing group includes SBFD random access channel timing; and The configuration information further indicates a second random access channel timing group, wherein the second random access channel timing group includes time division duplex (TDD) random access channel timings.

20. The network entity of claim 19, wherein the configuration information specifically indicates: The first physical random access channel sequence format, the first transmit beam, the first set of frequency resources, the first random access channel preamble, or any combination thereof, corresponding to the first random access channel timing group, and The second physical random access channel sequence format that is different from the first physical random access channel sequence format, the second transmission beam that is different from the first transmission beam, the second set of frequency resources that is different from the first set of frequency resources, the second random access channel preamble that is different from the first random access channel preamble, or any combination thereof.

Images