Techniques for frequency resource allocation in random access channels

Abstract

Methods, systems, and devices are described for a method of wireless communication. A user equipment (UE) may receive, from a network entity, an indication of an uplink bandwidth portion associated with a random access procedure, and the uplink bandwidth portion may include a plurality of sub-bands corresponding to a set of random access opportunities. The UE may select a random access opportunity from the set of random access opportunities based on an offset parameter, and the UE may transmit an uplink random access channel message at the random access opportunity of the set of random access opportunities.

Description

Technical Field

[0001] The following relates to methods for wireless communications, including techniques for frequency resource allocation in a random access channel. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to 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, advanced LTE (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 techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication for a communication device, which may be referred to as a user equipment (UE).

[0003] In some wireless communication networks, network entities and user equipment (UE) may communicate using a random access channel (RACH) procedure, which may include the UE performing transmissions using a RACH opportunity (RO) and a subband of a bandwidth portion. However, in some examples, the UE may operate at a lower frequency band, and the UE may not be able to define a frequency domain resource allocation to map the RO and subband for transmission. Summary of the invention

[0004] The described technology relates to improved methods, systems, devices and apparatuses for supporting technology for frequency resource allocation in a random access channel. In general, the described technology allows a user equipment (UE) to perform a random access channel (RACH) process by mapping a RACH opportunity (RO) to a subband set based on a frequency resource allocation. For example, the UE, a network entity, or both may define multiple frequency offsets for dividing an uplink bandwidth portion into subbands. For example, the UE may determine to map a physical RACH (PRACH) transmission (e.g., msg1) to an RO in an uplink bandwidth portion. Additionally or alternatively, the UE may determine to map a physical uplink shared channel (PUSCH) transmission (e.g., msg3) to a subband overlapping with the selected RO. The UE may use the subband to send a PUSCH transmission to a network entity. Additionally or alternatively, the network entity may send a mapping of ROs and subbands to the UE. In some examples, if the UE performs multiple RACH transmissions, the UE may determine the subband for the PUSCH transmission based on one or more ROs in the RO used for the last RACH transmission. Additionally or alternatively, the network entity may send a physical downlink shared channel (PDSCH) transmission to the UE, and the UE may send a physical uplink control channel (PUCCH) transmission with hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback to the network entity using a subband previously used for a PUSCH transmission.

[0005] A method for wireless communication at a UE is described. The method may include: receiving an indication of an uplink bandwidth portion associated with a random access procedure, the uplink bandwidth portion including a set of multiple subbands corresponding to a set of multiple ROs; selecting an RO from the set of multiple ROs based on an offset parameter; and sending a PUSCH message at the RO in the set of multiple ROs.

[0006] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive an indication of an uplink bandwidth portion associated with a random access procedure, the uplink bandwidth portion including a set of multiple subbands corresponding to a set of multiple ROs; select an RO from the set of multiple ROs based on an offset parameter; and send an uplink RACH message at the RO in the set of multiple ROs.

[0007] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving an indication of an uplink bandwidth portion associated with a random access procedure, the uplink bandwidth portion including a set of multiple subbands corresponding to a set of multiple ROs; means for selecting an RO from the set of multiple ROs based on an offset parameter; and means for sending an uplink RACH message at the RO in the set of multiple ROs.

[0008] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive an indication of an uplink bandwidth portion associated with a random access procedure, the uplink bandwidth portion including a set of multiple subbands corresponding to a set of multiple ROs; select an RO from the set of multiple ROs based on an offset parameter; and send an uplink RACH message at the RO in the set of multiple ROs.

[0009] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a system information message including the offset parameter, and determining the offset parameter based on receiving the system information message.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying a subband in the set of multiple subbands that overlaps in frequency with the RO in the set of multiple ROs, and sending an initial subset of a physical uplink shared channel in a first resource block of the subband in the set of multiple subbands.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a second uplink RACH message in a subband in the set of multiple subbands that overlaps in frequency with an RO in the set of multiple ROs, wherein the uplink RACH message includes a physical RACH preamble code and the second uplink RACH message includes a PUSCH.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the second uplink RACH message in the subband in the set of multiple subbands may include operations, features, components, or instructions for: receiving a mapping between the set of multiple ROs and the set of multiple subbands from a network entity, and selecting the subband in the set of multiple subbands for sending the second uplink RACH message based on the mapping.

[0013] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the mapping includes at least one of: a one-to-one mapping between the set of multiple ROs and the set of multiple subbands, a mapping between ROs in the set of multiple ROs and the set of multiple subbands, a mapping between subbands in the set of multiple subbands and the set of multiple ROs, or a combination thereof.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending an uplink RACH message may include operations, features, components, or instructions for: sending one or more uplink random access preambles at one or more ROs in the set of multiple ROs, wherein each uplink random access message instance of the one or more uplink random access message instances corresponding to the first message of the random access process may be sent on a different RO, wherein the same preamble may be repeated in each random access message instance.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more ROs in the set of multiple ROs may be different in time, frequency, or a combination thereof.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a PUSCH message in a subband in the set of multiple subbands that overlaps in frequency with the RO in the one or more ROs, wherein the RO includes an RO at which a last uplink random access message instance of the one or more uplink random access message instances is sent, wherein the one or more uplink random access message instances correspond to a first message of the random access procedure.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a PUSCH message in a subband in the set of multiple subbands that overlaps in frequency with the RO in the one or more ROs, wherein the RO includes an RO at which a first uplink random access message instance corresponding to the first message of the random access procedure is sent.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a second uplink RACH message in a subband in the set of multiple subbands that overlaps in frequency with an RO in the set of multiple ROs, wherein the uplink RACH message includes a physical RACH preamble code and the second uplink random access channel message includes a physical uplink control channel.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the offset parameter indicates at least one of: the same offset for each subband in the set of multiple subbands, a different offset for each subband in the set of multiple subbands, or a combination thereof.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the offset parameter may be based on at least one of: a maximum bandwidth of the UE, an initial physical resource block of the uplink bandwidth portion, a subcarrier spacing of the uplink bandwidth portion, or a combination thereof.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a subband in the set of a plurality of subbands includes a predefined number of resource blocks.

[0022] A method for wireless communication at a network entity is described. The method may include: sending an indication of an uplink bandwidth portion associated with a random access procedure to a UE, the uplink bandwidth portion including a set of multiple subbands corresponding to a set of multiple ROs; and receiving an uplink random access channel message at an RO in the set of multiple ROs, wherein the RO in the set of multiple ROs is based on an offset parameter.

[0023] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: send an indication of an uplink bandwidth portion associated with a random access procedure to a UE, the uplink bandwidth portion including a set of multiple subbands corresponding to a set of multiple ROs; and receive an uplink random access channel message at an RO in the set of multiple ROs, wherein the RO in the set of multiple ROs is based on an offset parameter.

[0024] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for sending an indication of an uplink bandwidth portion associated with a random access procedure to a UE, the uplink bandwidth portion including a set of multiple subbands corresponding to a set of multiple ROs; and means for receiving an uplink random access channel message at an RO in the set of multiple ROs, wherein the RO in the set of multiple ROs is based on an offset parameter.

[0025] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to: send an indication of an uplink bandwidth portion associated with a random access procedure to a UE, the uplink bandwidth portion including a set of multiple subbands corresponding to a set of multiple ROs; and receive an uplink random access channel message at an RO in the set of multiple ROs, wherein the RO in the set of multiple ROs is based on an offset parameter.

[0026] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a system information message including the offset parameter to the UE.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: identifying a subband in the set of multiple subbands that overlaps in frequency with the RO in the set of multiple ROs; and receiving an initial subset of PUSCH channels in a first resource block of the subband in the set of multiple subbands.

[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second uplink random access channel message in a subband in the set of multiple subbands that overlaps in frequency with an RO in the set of multiple ROs, wherein the uplink random access channel message includes a physical random access channel preamble, and the second uplink random access channel message includes a physical uplink shared channel.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the second uplink random access channel message in the subband in the set of multiple subbands may include operations, features, components, or instructions for: sending a mapping between the set of multiple ROs and the set of multiple subbands to the UE, wherein the subband in the set of multiple subbands for sending the second uplink random access channel message may be selected based on the mapping.

[0030] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the mapping includes at least one of: a one-to-one mapping between the set of multiple ROs and the set of multiple subbands, a mapping between ROs in the set of multiple ROs and the set of multiple subbands, a mapping between subbands in the set of multiple subbands and the set of multiple ROs, or a combination thereof.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the uplink random access channel message may include operations, features, components, or instructions for: receiving one or more uplink random access preambles at one or more ROs in the set of multiple ROs, wherein each uplink random access message instance of the one or more uplink random access message instances corresponding to the first message of the random access process may be sent on a different RO, wherein the same preamble may be repeated in each random access message instance.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the one or more ROs in the set of multiple ROs may be different in time, frequency, or a combination thereof.

[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a physical uplink sharing message in a subband in the set of multiple subbands that overlaps in frequency with the RO in the one or more ROs, wherein the RO includes an RO at which a last uplink random access message instance of the one or more uplink random access instances is received, wherein the one or more uplink random access message instances correspond to a first message of the random access procedure.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a physical uplink sharing message in a subband in the set of multiple subbands that overlaps in frequency with the RO in the one or more ROs, wherein the RO includes an RO at which a first uplink random access message instance corresponding to the first message of the random access procedure is sent.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second uplink random access channel message in a subband in the set of multiple subbands that overlaps in frequency with an RO in the set of multiple ROs, wherein the uplink random access channel message includes a physical random access channel preamble code, and the second uplink random access channel message includes a physical uplink control channel.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the offset parameter indicates at least one of: the same offset for each subband in the set of multiple subbands, a different offset for each subband in the set of multiple subbands, or a combination thereof.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the offset parameter may be based on at least one of: a maximum bandwidth of the UE, an initial physical resource block of the uplink bandwidth portion, a subcarrier spacing of the uplink bandwidth portion, or a combination thereof.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a subband in the set of a plurality of subbands includes a predefined number of resource blocks. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 An example of a wireless communication system supporting techniques for frequency resource allocation in a random access channel (RACH) in accordance with one or more aspects of the present disclosure is illustrated.

[0040] Figure 2 An example of a wireless communication system supporting techniques for frequency resource allocation in RACH according to one or more aspects of the present disclosure is illustrated.

[0041] Figure 3 An example of a frequency resource allocation scheme supporting techniques for frequency resource allocation in RACH according to one or more aspects of the present disclosure is illustrated.

[0042] Figure 4 An example of a frequency resource allocation scheme supporting techniques for frequency resource allocation in RACH according to one or more aspects of the present disclosure is illustrated.

[0043] Figure 5A and Figure 5B An example of a frequency mapping scheme supporting techniques for frequency resource allocation in RACH according to one or more aspects of the present disclosure is illustrated.

[0044] Figure 6 An example of a frequency resource allocation scheme supporting techniques for frequency resource allocation in RACH according to one or more aspects of the present disclosure is illustrated.

[0045] Figure 7 An example of a process flow supporting techniques for frequency resource allocation in RACH in accordance with one or more aspects of the present disclosure is illustrated.

[0046] Figure 8 and Fig. 9 A block diagram is shown of a technique supporting frequency resource allocation in RACH in accordance with one or more aspects of the present disclosure.

[0047] Fig.10 A block diagram of a communications manager supporting techniques for frequency resource allocation in a RACH is shown in accordance with one or more aspects of the present disclosure.

[0048] Fig.11

[0013] A diagram of a system including devices supporting techniques for frequency resource allocation in RACH in accordance with one or more aspects of the present disclosure is shown.

[0049] Fig.12 and Fig.13 A block diagram of a device supporting techniques for frequency resource allocation in RACH according to one or more aspects of the present disclosure is shown.

[0050] Fig.14 A block diagram of a communications manager supporting techniques for frequency resource allocation in a RACH is shown in accordance with one or more aspects of the present disclosure.

[0051] Fig.15

[0013] A diagram of a system including devices supporting techniques for frequency resource allocation in RACH in accordance with one or more aspects of the present disclosure is shown.

[0052] Figures 16 to 19 A flow chart illustrating a method of supporting techniques for frequency resource allocation in RACH according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0053] In some wireless communication networks, a network entity and a user equipment (UE) may communicate using a random access channel (RACH) procedure (e.g., a two-step RACH procedure, a four-step RACH procedure, etc.). The RACH procedure may include an uplink message and a downlink message, wherein the message may be sent over a bandwidth range specific to the UE. In some examples, the network entity, the UE, or both may define an initial uplink bandwidth portion of the frequency resource allocation for the message. The UE may send each message (e.g., msg1, msg3, or both) using a bandwidth portion of the uplink bandwidth portion based on the subcarrier spacing, and each bandwidth portion may be associated with multiple RACH opportunities (ROs). For example, the UE may determine to map a physical RACH (PRACH) transmission (e.g., msg1) to the RO based on the frequency resource allocation. In some examples, the UE may send another message (e.g., msg3) of the RACH procedure using a subband that overlaps with the selected RO in frequency. However, some UEs (e.g., eRedcap (enhanced reduced capability) UEs) may operate on a limited frequency range (e.g., 5 MHz), and the UEs may not be able to define frequency resource allocations for messages within the limited frequency range, which may result in increased latency and inefficient communications.

[0054] Features described herein generally relate to a UE (e.g., an eRedcap UE) mapping a RO to a set of subbands based on frequency resource allocation. For example, a UE, a network entity, or both may define a plurality of frequency offsets for dividing an uplink bandwidth portion into subbands. Each subband may include a predefined number of resource blocks (RBs), and each subband may overlap with a plurality of ROs in frequency. For example, a UE may determine to map a physical RACH (PRACH) transmission (e.g., msg1) to a RO in an uplink bandwidth portion. As part of a RACH procedure, the UE may use the RO to send a PRACH transmission to a network entity. Additionally or alternatively, the UE may determine to map a physical uplink shared channel (PUSCH) transmission (e.g., msg3) to a subband overlapping with a selected RO. As part of a RACH procedure, the UE may use the subband to send a PUSCH transmission to a network entity. Additionally or alternatively, the network entity may send a mapping of ROs and subbands to the UE. In this example, the UE may determine the ROs and subbands for PRACH and PUSCH transmissions based on the configured mapping. Additionally or alternatively, if the UE performs multiple RACH transmissions, the UE may determine the subband for the PUSCH transmission based on one or more of the ROs used for the last RACH transmission. Additionally or alternatively, the network entity may send a physical downlink shared channel (PDSCH) transmission to the UE. The UE may send a physical uplink control channel (PUCCH) transmission to the network entity using the subband previously used for the PUSCH transmission, and the PUCCH transmission may include hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback.

[0055] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated and described by frequency resource allocation schemes, frequency mapping methods, and process flows. Aspects of the present disclosure are further illustrated and described by apparatus diagrams, system diagrams, and flow charts related to frequency resource allocation for RACH.

[0056] Figure 1 An example of a wireless communication system 100 supporting techniques for frequency resource allocation in RACH according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0057] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0058] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or both stationary and mobile at different times. The UEs 115 may take different forms or devices with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1 . The UEs 115 described herein may be capable of supporting communication with various types of devices (such as other UEs 115 or network entities 105), such as Figure 1 shown.

[0059] As described herein, a node of 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, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

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

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

[0062] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration initiated by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0063] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165, such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 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 the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and the RUs 170, such that the DUs 165 may support one or more layers of the protocol stack, and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 that communicate via those communication links.

[0064] In a wireless communication system (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports 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., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0065] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. The IAB donor may facilitate a connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with an alternative IAB donor) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0066] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., an IAB donor may relay transmissions to a UE through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104 , and the DU interface (eg, DU 165 ) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115 .

[0067] For example, the IAB node 104 may be referred to as a parent node supporting communications to a child IAB node or as a child node associated with an IAB donor, or both. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay transmissions to the UE 115 via the IAB node 104, or may directly signal the transmissions to the UE 115, or both. The CU 160 of the IAB donor may signal the establishment of a communication link to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling via the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0068] Where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support the techniques for frequency resource allocation in the RACH as described herein. For example, some operations described as being performed by the UE 115 or the network entity 105 (e.g., the base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., the IAB node 104, the DU 165, the CU 160, the RU 170, the RIC 175, the SMO 180).

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

[0070] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1shown.

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

[0072] In some examples, such as in a carrier aggregation configuration, a carrier may also 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 based on a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

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

[0074] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communications using a particular carrier bandwidth, or may be capable of being configured to support communications using one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

[0075] The signal waveform transmitted via the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM techniques, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and the 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 coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may increase the data rate or data integrity of communications with UE 115.

[0076] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0077] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, T s =1 / (Δf max ·N f ) seconds sampling period, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., in the range of 0 to 1023).

[0078] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of 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., N f The duration of a symbol period may depend on the subcarrier spacing or the operating band.

[0079] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a 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 of a shortened TTI (sTTI)).

[0080] Carrier multiplexing physical channels may be used for communication according to various techniques. Physical control channels and physical data channels may be multiplexed via downlink carriers for signaling, for example, using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may 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 sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0081] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier) ​​used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) within which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, etc.

[0082] A macro cell typically covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. Small cells may be associated with lower power network entities 105 (e.g., lower power base stations 140) than macro cells, and small cells may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with small cells (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

[0083] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0084] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0085] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for either synchronous operation or asynchronous operation.

[0086] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from a device with integrated sensors or meters that measures or captures information and relays such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0087] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UE 115 include entering a power saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

[0088] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). The UE 115 may be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication may include private communication 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 prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency may be used interchangeably herein.

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

[0090] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, vehicles in the V2X system can communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0091] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The 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), an 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), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access layer (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0092] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about 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 may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than communications using smaller frequencies and longer wavelengths in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0093] The wireless communication system 100 may also operate in a super high frequency (SHF) region (also known as a centimeter band) in the range of 3 GHz to 30 GHz or in an extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as a millimeter band) using a spectrum. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communication between a UE 115 and a network entity 105 (e.g., a base station 140, a RU 170), and the EHF antenna of the corresponding device may be smaller and closer than the UHF antenna. In some examples, such technology may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may have even greater attenuation and a shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0094] The wireless communication system 100 may utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations performed using unlicensed bands may be based on carrier aggregation configuration in conjunction with component carriers (e.g., LAA) that operate using licensed bands. Operations performed using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0095] The 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 technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0096] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technologies include: single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

[0097] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other orientation).

[0098] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different beamforming weight sets associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) beam directions for later transmission or reception by the network entity 105.

[0099] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, a beam direction associated with transmission along a single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0100] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or unprecoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-faceted codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0101] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

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

[0103] UE 115 and network entity 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve the throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received in a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot or according to some other time interval.

[0104] The wireless communication system 100 may be configured to support techniques for frequency resource allocation to perform a RACH procedure. A device in the wireless communication system 100, such as a UE 115, may perform a RACH procedure. In some examples, an IoT device, such as a UE, may be associated with enhanced mobile broadband (eMBB) communications and ultra-reliable low latency communications (URLLC) with other IoT 5G devices. For example, the UE 115 may perform communications in eMBB at a minimum data transfer rate level, which may be associated with increased bandwidth and reduced latency in a 5G wireless network. In some examples, the UE 115, such as a RedCap (e.g., reduced capability) UE, may be associated with NR lightweight (e.g., reduced capability NR device) communications. The RedCap UE may support lower latency communications in eMBB communications or millimeter wave (mmW) communications in a low power wide area network (LPWA). mmW communications in LPWA networks (e.g., spectrum bands between 30 GHz and 300 GHz) may be associated with efficient long-range communications between 5G devices. For example, RedCap devices may operate in the mmW frequency range in the LPWA network, and RedCap devices may include logical trackers, wearable devices, video monitoring devices, health monitors, smart phones, industrial wireless sensors, etc. In some examples, UE 115, such as eRedCap (enhanced RedCap) UE, may be associated with one or more NR ultra-lightweight communications in NR ultra-lightweight communications. NR ultra-lightweight communications may include LTE enhanced machine type communications (eMTC), narrowband (NB)-IoT communications (e.g., narrowband may be associated with LPWA communications), or large-scale IoT. eMTC may be a type of LPWA communication technology that supports communications between IoT devices with relatively low device complexity and extended wireless range. For example, ERedCap devices may include asset trackers, wearable devices, utility meters, agricultural sensors, parking sensors, industrial sensors, etc. Large-scale IoT may include communications with a relatively large number (e.g., billions) of connected devices, which may include RedCap UEs, eRedCap UEs, and other UEs 115.

[0105] In some examples, the eRedCap UE may operate within a relatively smaller frequency range (e.g., 5 MHz) compared to RedCap UEs (e.g., 20 MHz) and other devices for eMBB communications. In some examples, the eRedCap UE may support half-duplex (HD), full-duplex (FD)-frequency division duplex (FDD), or time division duplex (TDD) duplexing of sub-bands within the bandwidth portion for transmission. In some examples, the eRedCap UE may have one antenna for reception and transmission, one MIMO layer for uplink transmission, and one MIMO layer for downlink reception. In some examples, the eRedCap UE may use up to 3 Mbps (e.g., megabits per second) (e.g., peak data rate) for uplink and downlink communications, and these communications may be associated with a 164 dB maximum coupling loss (e.g., device attenuation / interference). In some examples, the eRedCap UE may use polarization channel coding, rate matching coding, low density parity check (LDPC) data coding, 64 quadrature amplitude modulation (QAM) for downlink reception, and 16QAM for uplink transmission. Additionally or alternatively, the eRedCap UE may be configured with enhancements for wake-up signals, extended discontinuous reception (eDRX), positioning within wireless range, early data transmission, and pre-configured uplink resources.

[0106] In some examples, the eRedCap UE may perform a two-step RACH procedure or a four-step RACH procedure. In an example of a two-step RACH procedure, the network entity 105 may send a message (e.g., a synchronization signal block (SSB), a system information block (SIB), a reference signal, RRC signaling, etc.) to the connected UE 115. The SSB may correspond to a beam used to perform uplink transmission at the UE 115. The UE 115 may perform downlink synchronization, system information decoding and measurement, or both to send a message to the network entity 105. The message from the UE 115 may include a preamble (e.g., a msgA preamble) and a payload (e.g., a msgA payload). The msgA preamble may include a PRACH information block and a guard time (e.g., a buffer time) block. The message may include a transmission gap time (e.g., TxG) between the msgA preamble and the msgA payload. The msgA payload may include a demodulation reference signal (DMRS) transmission block or a PUSCH transmission block, and a guard time (e.g., a buffer time) block. In some examples, the subband of the msgA preamble and the subband of the msgA payload may be the same subband. In some examples, the subband of the msgA preamble may be a different subband from the subband of the msgA payload. The network entity 105 may process the msgA preamble and the msgA payload, and in some examples, the network entity 105 may send a physical downlink control channel (PDCCH) (e.g., msgB PDCCH) and a physical downlink shared channel (PDSCH) (e.g., msgB PDSCH) to the UE 115. In some examples, the UE 115 may send a PUSCH with HARQ ACK feedback to the network entity 105 in response to the PDCCH and PDSCH. In some examples, the subband of msgB may be based on msgA.

[0107] In some examples, the four-step RACH process may include the UE 115 sending a physical RACH (PRACH) preamble (e.g., msg1) to the network entity 105. The network entity 105 may send a PDCCH, a PDSCH, or both as part of msg2 (e.g., as multiple random access responses (RARs)). msg2 may include one or more of a timing advance for the UE 115, an uplink grant for another RACH transmission (e.g., msg3), or a temporary cell radio network temporary identifier (TC-RNTI). In response to msg2, the UE 115 may send a PUSCH transmission (e.g., msg3) to the network entity 105, and msg3 may include one or more of an RRC connection request, a scheduling request, or a buffer status. The network entity 105 may send a PDCCH or a PDSCH (e.g., msg4) to the UE 115, and msg4 may include a contention resolution message. In some examples, UE 115 may send PUCCH to network entity 105 in response to msg4.

[0108] In some examples, the eRedCap UE may perform a RACH (e.g., NRRACH) procedure using multiple RACH preamble formats that may include a cyclic prefix (CP) and multiple data sequences. In such an example, a long sequence-based format may be associated with a maximum bandwidth of 5 MHz, i.e., the bandwidth of the PRACH preamble (e.g., 5 MHz). In another example, the PRACH preamble may include a short data sequence, and the subcarrier spacing of the bandwidth may be 15 kHz. In this example, for a relatively larger subcarrier spacing (e.g., 30 kHz) in a PRACH (e.g., NR frequency 1 (FR1) PRACH) preamble format, the bandwidth may be less than 5 MHz (e.g., 4.32 kHz).

[0109] In some examples, the network entity 105 may configure the eRedCap UE with an initial uplink bandwidth portion in a SIB (e.g., SIB1) included in a first message (e.g., msg1) of a RACH procedure. The initial uplink bandwidth portion may be based on a subcarrier spacing, and the bandwidth portion may be associated with a plurality of RACH opportunities (ROs) for RACH message transmission. Each message of the RACH procedure transmitted by the UE 115 may be included in the frequency domain of the bandwidth portion. In some examples, the network entity 105 may configure the UE 115 with a first RO frequency allocation having an offset from an initial physical resource block (e.g., PRB0) of a bandwidth portion (e.g., msg1-FrequencyStart) for the UE 115 to transmit the RACH procedure. For example, the UE 115 may determine to map the PRACH transmission (e.g., msg1) to the RO based on the frequency resource allocation (e.g., PRB0). In some examples, the UE 115 may transmit a PUSCH transmission (e.g., msg3) of a RACH process using a subband that overlaps in frequency with the selected RO. In this example, the UE 115 may map the PUSCH transmission to resources based on PRB0. However, since the eRedCap UE may operate over a limited frequency range (e.g., 5 MHz), the UE 115 may have a limited number of ROs within a bandwidth portion (e.g., one or two ROs based on the PRACH transmission subcarrier spacing), and the UE 115 may not be able to define frequency resource allocations for messages within the limited frequency range. Additionally or alternatively, the eRedCap UE may not be able to communicate with Redcap UEs and other conventional UEs 115 due to limited bandwidth, which may result in increased latency and inefficient communication.

[0110] In order to reduce latency and allow eRedCap UEs to efficiently perform RACH procedures, the described techniques allow UE 115 (e.g., eRedCap UE) to map ROs to a set of subbands based on frequency resource allocation. For example, UE 115, network entity 105, or both may define multiple frequency offsets for dividing an uplink bandwidth portion into subbands. Each subband may include a predefined number of resource blocks (RBs), and each subband may overlap multiple ROs in frequency. For example, UE 115 may determine to map a PRACH transmission (e.g., msg1) to a RO in a bandwidth portion. As part of the RACH procedure, UE 115 may use the RO to send the PRACH transmission to network entity 105. Additionally or alternatively, UE 115 may determine to map a PUSCH transmission (e.g., msg3) to a subband overlapping with the selected RO. As part of the RACH procedure, UE 115 may use the subband to send the PUSCH transmission to network entity 105. Additionally or alternatively, the network entity 105 may send a mapping of ROs and subbands to the UE 115. In this example, the UE 115 may determine the ROs and subbands for PRACH and PUSCH transmissions based on the configured mapping. Additionally or alternatively, if the UE 115 performs multiple RACH transmissions, the UE 115 may determine the subbands for PUSCH transmissions based on one or more of the ROs for the last RACH transmission. Additionally or alternatively, the network entity 105 may send a PDSCH to the UE 115. The UE 115 may send a PUCCH to the network entity 105 using the subband previously used for PUSCH transmission, and the PUCCH transmission may include HARQ-ACK feedback.

[0111] Figure 2 An example of a wireless communication system 200 that supports techniques for frequency resource allocation in a RACH according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 can implement aspects of the wireless communication system 100. For example, the wireless communication system 200 can support communications between a network entity 105-a and a UE 115-a, which can be as described in reference to Figure 1 Examples of corresponding network entities 105 and UEs 115. In some examples, the network entity 105-a can communicate with one or more UEs 115 within a geographic coverage area.

[0112] UE 115-a may transmit transmissions to network entity 105-a via uplink communication link 210, and network entity 105-a may transmit transmissions to UE 115-a via downlink communication link 205. For example, UE 115-a may be an eRedCap UE (as described in reference Figure 1The UE 115-a may transmit a bandwidth portion indication to the UE 115-a via the downlink communication link 205 for the UE 115-a to perform a RACH process. The UE 115-a may perform a RACH process by sending one or more random access messages 220 via the uplink communication link 210. The bandwidth portion indication 215 may indicate a bandwidth portion 225, and the bandwidth portion 225 may include multiple ROs (e.g., RO 1, RO 2, RO 3, and RO 4). In some examples, the network entity 105-a may configure a first RO frequency allocation to the UE 115, the first RO frequency allocation having an offset from PRB0 of the bandwidth portion 225 (e.g., a frequency domain resource allocation (FDRA) may start at the first PRB). The UE 115-a may use the first RO frequency allocation to send a first message (e.g., msg1) of the RACH process.

[0113] In some examples, UE 115-a may select a random access opportunity from a set of ROs based on an offset parameter. For example, UE 115-a may define a plurality of frequency offsets for dividing bandwidth portion 225 into subbands. One or more offsets may be based on PRB0 and the subcarrier spacing of bandwidth portion 225. In some examples, network entity 105-a may send system information to UE 115-a, and the system information may include an indication of one or more offsets. UE 115-a may determine to map a PRACH transmission (e.g., msg1) to a RO based on a frequency resource allocation (e.g., PRB0) such that the start of a frequency resource allocation for msg1 may be associated with PRB0. In some examples, UE 115-a may use a RO (e.g., RO 2) to send a first random access message 220 (e.g., msg1). Additionally or alternatively, UE 115-a may determine to use a subband to send a second random access message 220 (e.g., msg3) to network entity 105-a. The subband may overlap in frequency with the selected RO (e.g., RO 2). In some examples, the subband used for the payload of MsgA (e.g., PUSCH) may be the same as the subband of the MsgA preamble. In some examples, the subband used for the payload of MsgA (e.g., PUSCH) may be different from the subband of the MsgA preamble and based on the mapping. Additionally, alternatively, the subband used for MsgB feedback (e.g., ACK) may also depend on MsgA.

[0114] Figure 3An example of a frequency resource allocation scheme 300 that supports techniques for frequency resource allocation in a RACH according to one or more aspects of the present disclosure is illustrated. In some examples, the frequency resource allocation scheme 300 can implement aspects of the wireless communication system 100 and the wireless communication system 200. For example, the frequency resource allocation scheme 300 can illustrate aspects of the techniques performed by the network entity 105 and the UE 115, which can be as described in reference to Figure 1 and Figure 2 The examples of the network entity 105 and the UE 115 are described. For example, the network entity 105 may send a bandwidth portion indication of the bandwidth portion 315 to the UE 115, and the UE 115 may determine a frequency resource allocation for transmission based on the bandwidth portion indication.

[0115] For example, a UE 115, such as a RedCap UE and other UEs 115, may be configured with a relatively larger bandwidth portion 310 (e.g., 20 MHz) than a bandwidth portion allocated to an eRedCap UE (e.g., 5 MHz). In some examples, the eRedCap UE may receive an indication of a bandwidth portion 315, and the bandwidth portion 315 may be associated with a plurality of ROs 305 (e.g., RO 1, RO 2, RO 3, and RO 4). The UE 115 (e.g., an eRedCap UE) may define a plurality of frequency offsets (e.g., FDRA start offset 0, FDRA start offset 1, FDRA start offset 2, and FDRA start offset 3) within the bandwidth portion 315. The UE 115 may use the plurality of frequency offsets to divide the bandwidth portion 315 into subbands 320 (e.g., subbands spanning 5 MHz), and the subbands 320 may overlap the ROs in frequency. The subbands 320 may include a predefined number N of subbands. rb If a subband 320 includes a predefined number of RBs, the subband 320 may be considered valid.

[0116] In some examples, the frequency offset may be based on an initial PRB (e.g., PRB0) and a subcarrier spacing of bandwidth portion 315. In some examples, network entity 105 may configure the frequency offset to UE 115. Additionally or alternatively, the frequency offset may be based on a maximum UE bandwidth. For example, the offset k may be equal to the offset divided by the number of RBs N included in the maximum UE bandwidth. rb The product of (for example, k = k * N rb). UE 115 may select an RO to perform transmission for a RACH process. For example, UE 115 may select RO 2 to transmit msg1 of the RACH process, and msg1 may be associated with the frequency width start of bandwidth portion 315. Additionally or alternatively, UE 115 may select a subband (e.g., subband 320-b) overlapping with the selected RO (e.g., RO 2) to transmit msg3 of the RACH process. Msg3 may be associated with the frequency width start of bandwidth portion 315, and the frequency width start may be the first RB of effective subband 320.

[0117] Figure 4 An example of a frequency resource allocation scheme 400 supporting techniques for frequency resource allocation in a RACH according to one or more aspects of the present disclosure is illustrated. In some examples, the frequency resource allocation scheme 400 can implement aspects of the wireless communication system 100, the wireless communication system 200, and the frequency resource allocation scheme 300. For example, the frequency resource allocation scheme 300 can illustrate aspects of the techniques performed by the network entity 105 and the UE 115, which can be as described in reference Figures 1 to 3 The examples of the network entity 105 and the UE 115 are described. For example, the network entity 105 may send a bandwidth portion indication of the bandwidth portion 410 to the UE 115, and the UE 115 may determine a frequency resource allocation for transmission based on the bandwidth portion indication.

[0118] In some examples, UE 115 may select an RO (e.g., RO 3) among multiple ROs 405 to send msg1 of a RACH process (e.g., PRACH transmission) to network entity 105. Additionally or alternatively, UE 115 may determine a subband 415 to send msg3 of a RACH process (e.g., PUSCH transmission). The subband (e.g., subband 415-c) may completely overlap with the selected RO (e.g., RO 3) in frequency (e.g., frequency domain). Additionally or alternatively, network entity 105 may configure a mapping between the RO (e.g., RO 3) and the subband (e.g., subband 415-c). For example, network entity 105 may send the mapping to UE 115. The mapping may be one or more of a one-to-one mapping between RO 405 and subband 415, a mapping between a selected RO (e.g., RO 3) and multiple subbands 415, or a mapping between a selected subband (e.g., subband 415-c) and RO 405. UE 115 may use the mapping and the selected RO (e.g., RO 3) to send msg3 to network entity 105 on the selected subband 415. Network entity 105 may send msg4 of the RACH procedure in response to receiving msg3.

[0119] Additionally or alternatively, in response to receiving msg4 (e.g., PDSCH transmission), UE 115 may send a PUCCH to network entity 105. The PUCCH may include HARQ-ACK feedback, and UE 115 may send the PUCCH on the same subband 415 (e.g., subband 415-c) used to send msg3, such that the PUCCH transmission may overlap in frequency with the selected RO (e.g., RO 3).

[0120] Figure 5A and Figure 5B An example of a frequency mapping scheme supporting techniques for frequency resource allocation in a RACH according to one or more aspects of the present disclosure is illustrated. In some examples, the frequency mapping schemes 500-a and 500-b may implement aspects of the wireless communication system 100, the wireless communication system 200, the frequency resource allocation scheme 300, and the frequency resource allocation scheme 400. For example, the frequency mapping schemes 500-a and 500-b may illustrate aspects of the techniques performed by the UE 115, which may be as described in reference to Figures 1 to 3 An example of UE 115. For example, UE 115 may use one or more ROs to send a first message (eg, msg1) of a RACH procedure.

[0121] In the frequency mapping scheme 500-a, the UE 115 may perform multiple PRACH (e.g., msg1) transmissions using different beams, which may allow for increased wireless coverage of the eRedCap UE. For example, as part of a four-step RACH process, the UE 115 may transmit multiple PRACH transmissions (e.g., msg1#0 and msg1#1) using a set of beams associated with a set of SSBs (e.g., SSB#0 and SSB#1). The SSBs may be associated with multiple ROs (e.g., RO 0, RO 1, RO 2, and RO 3). The PRACH transmission may be associated with a short sequence PRACH format, a long sequence PRACH format, or both. In some examples, as illustrated in the frequency mapping scheme 500-a, the UE 115-a may transmit multiple PRACH transmissions using ROs (e.g., RO 0 and RO 1) that are different in frequency range (e.g., these transmissions may be frequency division multiplexed using these ROs). For example, UE 115 may send a first portion of a PRACH transmission (e.g., msg1#0) on RO 0 using SSB#0, and UE 115 may send a second portion of a PRACH transmission (e.g., msg1#1) on RO 1 using SSB#0. In this case, multiple PRACH transmissions are sent using the same beam (e.g., the beam associated with SSB#0). In the example of frequency mapping scheme 500-a, repetition may be equal to 2, may be equal to 2, N may be equal to 1 / 2, and MSG1-FDM may be equal to 2, where is the number of synchronization signal blocks, N is the number of synchronization signal / physical block channel indices associated with one random access opportunity, and MSG1-FDM may be frequency division multiplexing for uplink transmission.

[0122] Additionally or alternatively, UE 115 may transmit msg3 of the RACH procedure. For example, if UE 115 transmits multiple PRACH transmissions, UE 115 may transmit msg3 using a subband that completely overlaps (e.g., is completely included in) the RO used for the last PRACH transmission (e.g., msg1#1) in frequency. Additionally or alternatively, UE 115 may transmit msg3 using a subband that completely overlaps (e.g., is completely included in) the RO used for the first PRACH transmission (e.g., msg1#0) in frequency.

[0123] In the frequency mapping scheme 500-b, the UE 115 may perform multiple PRACH (e.g., msg1) transmissions using different beams at different time periods (e.g., association periods), which may allow for increased wireless coverage of the eRedCap UE. For example, the UE 115 may transmit multiple PRACH transmissions (e.g., msg1#0 and msg1#1) using a set of beams associated with a set of SSBs (e.g., SSB#0 and SSB#1). The SSBs may be associated with multiple ROs (e.g., RO 0, RO 1, RO 2, and RO3) at different association periods. In some examples, as illustrated in the frequency mapping scheme 500-b, the UE 115-a may transmit multiple PRACH transmissions (e.g., the transmissions may be frequency-hopped using the ROs) using different ROs in the frequency range and time domain (e.g., RO 0 in the first association period and RO 1 in the second association period). For example, UE 115 may send a first part of a PRACH transmission (e.g., msg1#0) on RO 0 in a first association period using SSB#0, and UE 1115 may send a second part of a PRACH transmission (e.g., msg1#1) on RO 1 in a second association period using SSB#0. In this case, multiple PRACH transmissions are sent using the same beam (e.g., the beam associated with SSB#0).

[0124] Additionally or alternatively, UE 115 may transmit msg3 of the RACH process. For example, if UE 115 transmits multiple PRACH transmissions, UE 115 may transmit msg3 using a subband that completely overlaps (e.g., is completely included in) the RO used for the last PRACH transmission (e.g., msg1#1) in frequency. Additionally or alternatively, UE 115 may transmit msg3 using a subband that completely overlaps (e.g., is completely included in) the RO used for the first PRACH transmission (e.g., msg1#0) in frequency. In the example of frequency mapping scheme 500-b, repetition may be equal to 2, may be equal to 2, N may be equal to 1 / 2, and MSG1-FDM may be equal to 2, where is the number of synchronization signal blocks, N is the number of synchronization signal / physical block channel indices associated with one random access opportunity, and MSG1-FDM may be frequency division multiplexing for uplink transmission.

[0125] Figure 6 An example of a frequency resource allocation scheme 600 supporting techniques for frequency resource allocation in a RACH according to one or more aspects of the present disclosure is illustrated. In some examples, the frequency resource allocation scheme 600 may implement aspects of the wireless communication system 100, the wireless communication system 200, the frequency resource allocation scheme 300, the frequency resource allocation scheme 400, and the frequency mapping schemes 500-a and 500-b. For example, the frequency resource allocation scheme 600 may illustrate aspects of the techniques performed by the network entity 105 and the UE 115, which may be as described in reference to Figures 1 to 3 The examples of the network entity 105 and the UE 115 are described. For example, the network entity 105 may send a bandwidth portion indication of the bandwidth portion 610 to the UE 115, and the UE 115 may determine a frequency resource allocation for transmission based on the bandwidth portion indication.

[0126] In some examples, UE 115 may use multiple ROs 605 to perform multiple PRACH transmissions (e.g., PRACH Tx#0 and PRACH Tx#1). For example, UE 115 may select a first RO (e.g., RO 3) among the multiple ROs 605 to send msg1#0 (e.g., PRACH Tx#0) of a RACH procedure to network entity 105. Additionally or alternatively, UE 115 may select a second RO (e.g., RO 2) among the multiple ROs 605 to send msg1#1 (e.g., PRACH Tx#1) of a RACH procedure to network entity 105. In some examples, UE 115 may determine a subband 415 to send msg3 (e.g., PUSCH transmission) based on the ROs used for the multiple PRACH transmissions (e.g., RO 2 and RO 3). In one example, UE 115 may transmit msg3 using a subband (e.g., subband 615-b) that overlaps in frequency with the RO used for the last PRACH transmission (e.g., RO 2). Additionally or alternatively, UE 115 may transmit msg3 using a subband (e.g., subband 615-c) that completely overlaps in frequency with (e.g., completely included in) the RO used for the first PRACH transmission (e.g., RO 3).

[0127] Figure 7 An example of a process flow 700 supporting techniques for frequency resource allocation in RACH according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 700 can implement aspects of the wireless communication system 100, the wireless communication system 200, the frequency resource allocation scheme 300, the frequency resource allocation scheme 400, the frequency mapping scheme 500-a, the frequency mapping scheme 500-b, and the frequency resource allocation scheme 600.

[0128] Process flow 700 may illustrate an example of a UE 115-b (e.g., an eRedCap UE) and a network entity 105-b performing a RACH procedure based on frequency resource allocation according to one or more aspects of the present disclosure, the UE and the network entity may be as described in reference to Figures 1 to 6 The examples of the network entity 105 and the UE 115 described above. The following alternative examples may be implemented in which some of the processes are performed in a different order than described or are not performed. In some cases, each process may include additional features not mentioned below, or further processes may be added.

[0129] At 705, the network entity 105-b may send an indication of an uplink bandwidth portion associated with the random access procedure to the UE 115-b. In some examples, the uplink bandwidth portion may include multiple subbands corresponding to multiple ROs.

[0130] At 710, in some examples, the network entity 105-b may optionally send a system information message including an offset parameter to the UE 115-b. The offset parameter may indicate the same offset for each of the plurality of subbands, a different offset for each of the plurality of subbands, or both. The offset parameter may be based on one or more of a maximum bandwidth of the UE 115-b, an initial physical resource block of the uplink bandwidth portion, or a subcarrier spacing of the uplink bandwidth portion. Each of the plurality of subbands may include a predefined number of resource blocks (RBs).

[0131] At 715, in some examples, UE 115-b may optionally determine an offset parameter based on receiving a system information message. At 720, UE 115-b may select a RO from a plurality of ROs based on the offset parameter.

[0132] At 725, UE 115-b may send an uplink random access (e.g., RACH) message at an RO (e.g., a selected RO) among the plurality of ROs. In some examples, UE 115-b may send one or more uplink RACH preambles at one or more ROs among the plurality of ROs, wherein each uplink random access message instance of one or more uplink random access message instances corresponding to a first message (e.g., msg1) of a RACH procedure may be sent on a different RO, and wherein the same preamble may be repeated in each random access message instance. In this example, the one or more ROs may be different in time, frequency, or both. In some examples, UE 115-b may send a physical uplink sharing (e.g., PUSCH) message in a subband that overlaps in frequency with an RO among the one or more ROs among the plurality of subbands, wherein the RO may include the RO at which the last uplink random access message instance of the one or more random access message instances is sent, and wherein the one or more uplink random access message instances may correspond to the first message of the random access (e.g., RACH) procedure. In some examples, UE 115-b may send a physical uplink sharing (e.g., PUSCH) message in a subband among multiple subbands that overlaps in frequency with an RO in one or more ROs, where the RO may include an RO at which a first uplink random access message instance of one or more random access message instances is sent.

[0133] At 730, in some examples, network entity 105-b may optionally send a mapping between the plurality of ROs and the plurality of subbands to UE 115-b. The mapping may be one or more of a one-to-one mapping between the plurality of ROs and the plurality of subbands, a mapping between an RO in the plurality of ROs and the plurality of subbands, or a mapping between a subband in the plurality of subbands and the plurality of ROs. In some examples, network entity 105-b may identify a subband in the plurality of subbands that overlaps in frequency with an RO in the plurality of ROs.

[0134] At 735, UE 115-b may identify a subband in the plurality of subbands that overlaps in frequency with an RO in the plurality of ROs. In some examples, UE 115-b may select a subband in the plurality of subbands for sending a second uplink RACH message based on the mapping. The second uplink RACH message may be a PUSCH transmission, a PUCCH transmission, or both. In some examples, UE 115-b may send an initial subset of PUSCH in a first resource block of a subband in the plurality of subbands.

[0135] At 740, UE 115-b may send a second uplink RACH message to network entity 105-b in a subband in the plurality of subbands that overlaps in frequency with a RO in the plurality of ROs, wherein the uplink RACH message may include a PRACH preamble, and the second uplink RACH message may include a PUSCH. In some examples, UE 115-b may send a second uplink RACH message in a subband in the plurality of subbands that overlaps in frequency with a RO in the plurality of ROs, wherein the uplink RACH message may include a physical random access preamble, and the second uplink RACH message may include a PUCCH.

[0136] Figure 8 A block diagram 800 of a device 805 supporting techniques for frequency resource allocation in a RACH according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of a UE 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0137] The receiver 810 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to techniques for frequency resource allocation in RACH, data channels, information channels). The information may be communicated to other components of the device 805. The receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0138] The transmitter 815 may provide means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to techniques for frequency resource allocation in RACH, data channels, information channels). In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0139] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the techniques for frequency resource allocation in the RACH described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.

[0140] In some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described herein. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0141] Additionally or alternatively, in some examples, the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functionality described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0142] In some examples, the communication manager 820 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 810, the transmitter 815, or both. For example, the communication manager 820 can receive information from the receiver 810, transmit information to the transmitter 815, or integrate with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0143] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a UE. For example, the communication manager 820 may be configured to or otherwise support a component for receiving an indication of an uplink bandwidth portion associated with a random access procedure, the uplink bandwidth portion including a set of multiple subbands corresponding to a set of multiple random access opportunities. The communication manager 820 may be configured to or otherwise support a component for selecting a random access opportunity from a set of multiple random access opportunities based on an offset parameter. The communication manager 820 may be configured to or otherwise support a component for sending an uplink RACH message at a random access opportunity in the set of multiple random access opportunities.

[0144] By including or configuring a communication manager 820 according to examples as described herein, a device 805 (e.g., a processor controlling or otherwise coupled with a receiver 810, a transmitter 815, a communication manager 820, or a combination thereof) may support techniques for frequency resource allocation in a RACH, which may result in reduced processing, reduced power consumption, and more efficient use of communication resources.

[0145] Fig. 9 A block diagram 900 of a device 905 supporting techniques for frequency resource allocation in a RACH according to one or more aspects of the present disclosure is shown. The device 905 may be an example of aspects of the device 805 or UE 115 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0146] The receiver 910 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to techniques for frequency resource allocation in RACH, data channels, information channels). The information may be communicated to other components of the device 905. The receiver 910 may utilize a single antenna or a collection of multiple antennas.

[0147] The transmitter 915 may provide means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to techniques for frequency resource allocation in RACH, data channels, information channels). In some examples, the transmitter 915 may be co-located with the receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0148] The device 905 or its various components may be examples of components for performing various aspects of the techniques for frequency resource allocation in the RACH as described herein. For example, the communication manager 920 may include an uplink bandwidth portion component 925, a random access opportunity selection component 930, an uplink component 935, or any combination thereof. The communication manager 920 may be an example of various aspects of the communication manager 820 as described herein. In some examples, the communication manager 920 or its various components may be configured to use or otherwise cooperate with the receiver 910, the transmitter 915, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0149] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a UE. An uplink bandwidth portion component 925 may be configured to or otherwise support means for receiving an indication of an uplink bandwidth portion associated with a random access procedure, the uplink bandwidth portion comprising a set of multiple subbands corresponding to a set of multiple random access opportunities. A random access opportunity selection component 930 may be configured to or otherwise support means for selecting a random access opportunity from a set of multiple random access opportunities based on an offset parameter. An uplink component 935 may be configured to or otherwise support means for sending an uplink RACH message at a random access opportunity in the set of multiple random access opportunities.

[0150] Fig.10A block diagram 1000 of a communication manager 1020 supporting techniques for frequency resource allocation in a RACH in accordance with one or more aspects of the present disclosure is shown. The communication manager 1020 may be an example of aspects of the communication manager 820, the communication manager 920, or both as described herein. The communication manager 1020 or its various components may be examples of means for performing various aspects of the techniques for frequency resource allocation in a RACH as described herein. For example, the communication manager 1020 may include an uplink bandwidth portion component 1025, a random access opportunity selection component 1030, an uplink component 1035, an offset parameter component 1040, a subband identification component 1045, a mapping component 1050, a subband selection component 1055, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0151] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a UE. An uplink bandwidth portion component 1025 may be configured to or otherwise support means for receiving an indication of an uplink bandwidth portion associated with a random access procedure, the uplink bandwidth portion comprising a set of multiple subbands corresponding to a set of multiple random access opportunities. A random access opportunity selection component 1030 may be configured to or otherwise support means for selecting a random access opportunity from a set of multiple random access opportunities based on an offset parameter. An uplink component 1035 may be configured to or otherwise support means for sending an uplink RACH message at a random access opportunity in the set of multiple random access opportunities.

[0152] In some examples, offset parameter component 1040 can be configured or otherwise support components for receiving a system information message including an offset parameter. In some examples, offset parameter component 1040 can be configured or otherwise support components for determining an offset parameter based on receiving a system information message.

[0153] In some examples, subband identification component 1045 can be configured or otherwise support means for identifying a subband in a set of multiple subbands that overlaps in frequency with a random access opportunity in a set of multiple random access opportunities. In some examples, uplink component 1035 can be configured or otherwise support means for transmitting an initial subset of a physical uplink shared channel in a first resource block of a subband in the set of multiple subbands.

[0154] In some examples, uplink component 1035 may be configured to or otherwise support components for sending a second uplink RACH message in a subband in a set of multiple subbands that overlaps in frequency with a random access opportunity in a set of multiple random access opportunities, wherein the uplink RACH message includes a physical RACH preamble and the second uplink RACH message includes a physical uplink shared channel.

[0155] In some examples, to support sending the second uplink RACH message in a subband in the set of multiple subbands, mapping component 1050 can be configured or otherwise supports means for receiving a mapping between a set of multiple random access opportunities and a set of multiple subbands from a network entity. In some examples, to support sending the second uplink RACH message in a subband in the set of multiple subbands, subband selection component 1055 can be configured or otherwise supports means for selecting a subband in the set of multiple subbands for sending the second uplink RACH message based on the mapping.

[0156] In some examples, the mapping includes at least one of: a one-to-one mapping between a set of multiple random access opportunities and a set of multiple subbands, a mapping between random access opportunities in a set of multiple random access opportunities and a set of multiple subbands, a mapping between subbands in a set of multiple subbands and a set of multiple random access opportunities, or a combination thereof.

[0157] In some examples, to support sending an uplink RACH message, the uplink component 1035 may be configured to or otherwise support means for sending one or more uplink random access message instances at one or more random access opportunities in a set of multiple random access opportunities, wherein each of the one or more uplink random access message instances corresponding to a first message of a random access procedure is sent at a different random access opportunity, wherein the same preamble is repeated in each random access message instance. In some examples, one or more random access opportunities in the set of multiple random access opportunities are different in time, frequency, or a combination thereof.

[0158] In some examples, the uplink component 1035 may be configured to or otherwise support components for sending a physical uplink shared message in a subband that overlaps in frequency with a random access opportunity in one or more random access opportunities in a set of multiple subbands, where the random access opportunity includes a random access opportunity at which a last uplink random access message instance of one or more uplink random access message instances is sent, where the one or more uplink random access message instances correspond to a first message of a random access procedure.

[0159] In some examples, uplink component 1035 may be configured as or otherwise support components for sending a physical uplink shared message in a subband that overlaps in frequency with a random access opportunity in one or more random access opportunities in a set of multiple subbands, wherein the random access opportunity includes a random access opportunity at which a first uplink random access message instance corresponding to a first message of a random access process is sent.

[0160] In some examples, uplink component 1035 may be configured to or otherwise support components for sending a second uplink RACH message in a subband in a set of multiple subbands that overlaps in frequency with a random access opportunity in a set of multiple random access opportunities, wherein the uplink RACH message includes a physical RACH preamble and the second uplink RACH message includes a physical uplink control channel.

[0161] In some examples, the offset parameter indicates at least one of: a same offset for each subband in the set of multiple subbands, a different offset for each subband in the set of multiple subbands, or a combination thereof.

[0162] In some examples, the offset parameter is based on at least one of: a maximum bandwidth of the UE, an initial physical resource block of the uplink bandwidth portion, a subcarrier spacing of the uplink bandwidth portion, or a combination thereof. In some examples, a subband in the set of multiple subbands includes a predefined number of resource blocks.

[0163] Fig.11 A diagram of a system 1100 including a device 1105 supporting techniques for frequency resource allocation in a RACH according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of a device 805, a device 905, or a UE 115 as described herein, or include components thereof. The device 1105 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1105 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1120, an input / output (I / O) controller 1110, a transceiver 1115, an antenna 1125, a memory 1130, a code 1135, and a processor 1140. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1145).

[0164] I / O controller 1110 can manage input signals and output signals of device 1105. I / O controller 1110 can also manage peripheral devices that are not integrated into device 1105. In some cases, I / O controller 1110 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1110 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 1110 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1110 may be implemented as part of a processor such as processor 1140. In some cases, a user may interact with device 1105 via I / O controller 1110 or via hardware components controlled by I / O controller 1110.

[0165] In some cases, the device 1105 may include a single antenna 1125. However, in some other cases, the device 1105 may have more than one antenna 1125, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1115 may communicate bidirectionally via one or more antennas 1125, wired or wireless links as described herein. For example, the transceiver 1115 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1115 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 1125 for transmission, and demodulating packets received from one or more antennas 1125. The transceiver 1115 or the transceiver 1115 and one or more antennas 1125 may be examples of transmitters 815, transmitters 915, receivers 810, receivers 910, or any combination thereof or components thereof as described herein.

[0166] The memory 1130 may include random access memory (RAM) and read-only memory (ROM). The memory 1130 may store computer-readable, computer-executable code 1135 including instructions that, when executed by the processor 1140, cause the device 1105 to perform various functions described herein. The code 1135 may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. In some cases, the code 1135 may not be directly executable by the processor 1140, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 1130 may also include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0167] The processor 1140 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1140 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1140. The processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1130) to cause the device 1105 to perform various functions (e.g., functions or tasks that support techniques for frequency resource allocation in the RACH). For example, the device 1105 or a component of the device 1105 may include a processor 1140 and a memory 1130 coupled to or to the processor 1140, and the processor 1140 and the memory 1130 are configured to perform various functions described herein.

[0168] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a UE. For example, the communication manager 1120 may be configured as or otherwise support a component for receiving an indication of an uplink bandwidth portion associated with a random access procedure, the uplink bandwidth portion including a set of multiple subbands corresponding to a set of multiple random access opportunities. The communication manager 1120 may be configured as or otherwise support a component for selecting a random access opportunity from a set of multiple random access opportunities based on an offset parameter. The communication manager 1120 may be configured as or otherwise support a component for sending an uplink RACH message at a random access opportunity in the set of multiple random access opportunities.

[0169] By including or configuring a communication manager 1120 according to examples as described herein, the device 1105 can support techniques for frequency resource allocation in the RACH, which can result in improved communication reliability, reduced latency, lower power consumption, and more efficient use of communication resources.

[0170] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1115, one or more antennas 1125, or any combination thereof. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or performed by the processor 1140, the memory 1130, the code 1135, or any combination thereof. For example, the code 1135 may include instructions executable by the processor 1140 to cause the device 1105 to perform various aspects of the techniques for frequency resource allocation in the RACH as described herein, or the processor 1140 and the memory 1130 may be otherwise configured to perform or support such operations.

[0171] Fig.12 A block diagram 1200 of a device 1205 supporting techniques for frequency resource allocation in a RACH according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of aspects of a network entity 105 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0174] The communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the techniques for frequency resource allocation in the RACH described herein. For example, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof, or components thereof may support methods for performing one or more of the functions described herein.

[0175] In some examples, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described herein. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0176] Additionally or alternatively, in some examples, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functionality described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0177] In some examples, communication manager 1220 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1210, transmitter 1215, or both. For example, communication manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or be integrated in conjunction with receiver 1210, transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0178] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. For example, the communication manager 1220 may be configured to or otherwise support components for sending an indication of an uplink bandwidth portion associated with a random access procedure to a UE, the uplink bandwidth portion comprising a set of a plurality of subbands corresponding to a set of a plurality of random access opportunities. The communication manager 1220 may be configured to or otherwise support components for receiving an uplink RACH message at a random access opportunity in the set of a plurality of random access opportunities, wherein the random access opportunity in the set of a plurality of random access opportunities is based on an offset parameter.

[0179] By including or configuring a communication manager 1220 according to examples as described herein, a device 1205 (e.g., a processor controlling or otherwise coupled to a receiver 1210, a transmitter 1215, a communication manager 1220, or a combination thereof) may support techniques for frequency resource allocation in a RACH, which may result in reduced processing, reduced power consumption, and more efficient use of communication resources.

[0180] Fig.13 A block diagram 1300 of a device 1305 supporting techniques for frequency resource allocation in a RACH according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of aspects of the device 1205 or the network entity 105 as described herein. The device 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. The device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0183] The device 1305 or its various components may be examples of components for performing various aspects of the techniques for frequency resource allocation in the RACH as described herein. For example, the communication manager 1320 may include an uplink bandwidth portion component 1325, a random access channel message component 1330, or any combination thereof. The communication manager 1320 may be an example of various aspects of the communication manager 1220 as described herein. In some examples, the communication manager 1320 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 1310, the transmitter 1315, or both. For example, the communication manager 1320 may receive information from the receiver 1310, transmit information to the transmitter 1315, or be integrated in combination with the receiver 1310, the transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.

[0184] According to examples as disclosed herein, the communication manager 1320 can support wireless communications at a network entity. The uplink bandwidth portion component 1325 can be configured to or otherwise support means for sending an indication of an uplink bandwidth portion associated with a random access procedure to a UE, the uplink bandwidth portion comprising a set of a plurality of subbands corresponding to a set of a plurality of random access opportunities. The random access channel message component 1330 can be configured to or otherwise support means for receiving an uplink RACH message at a random access opportunity in the set of a plurality of random access opportunities, wherein the random access opportunity in the set of a plurality of random access opportunities is based on an offset parameter.

[0185] Fig.14 A block diagram 1400 of a communication manager 1420 supporting techniques for frequency resource allocation in RACH according to one or more aspects of the present disclosure is shown. The communication manager 1420 may be an example of aspects of the communication manager 1220, the communication manager 1320, or both as described herein. The communication manager 1420 or its various components may be examples of components for performing various aspects of the techniques for frequency resource allocation in RACH as described herein. For example, the communication manager 1420 may include an uplink bandwidth portion component 1425, a random access channel message component 1430, a downlink component 1435, a sub-band identification component 1440, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0186] According to examples as disclosed herein, the communication manager 1420 can support wireless communications at a network entity. The uplink bandwidth portion component 1425 can be configured to or otherwise support means for sending an indication of an uplink bandwidth portion associated with a random access procedure to a UE, the uplink bandwidth portion comprising a set of a plurality of subbands corresponding to a set of a plurality of random access opportunities. The random access channel message component 1430 can be configured to or otherwise support means for receiving an uplink RACH message at a random access opportunity in the set of a plurality of random access opportunities, wherein the random access opportunity in the set of a plurality of random access opportunities is based on an offset parameter.

[0187] In some examples, downlink component 1435 may be configured or otherwise support components for sending a system information message including an offset parameter to a UE.

[0188] In some examples, subband identification component 1440 can be configured or otherwise support means for identifying a subband in a set of multiple subbands that overlaps in frequency with a random access opportunity in a set of multiple random access opportunities. In some examples, random access channel message component 1430 can be configured or otherwise support means for receiving an initial subset of a physical uplink shared channel in a first resource block of a subband in the set of multiple subbands.

[0189] In some examples, the random access channel message component 1430 may be configured to or otherwise support components for receiving a second uplink RACH message in a subband in a set of multiple subbands that overlaps in frequency with a random access opportunity in a set of multiple random access opportunities, wherein the uplink RACH message includes a physical RACH preamble and the second uplink RACH message includes a physical uplink shared channel.

[0190] In some examples, to support receiving a second uplink RACH message in a subband in a set of multiple subbands, the downlink component 1435 may be configured as or otherwise support components for sending a mapping between a set of multiple random access opportunities and a set of multiple subbands to the UE, wherein the subband in the set of multiple subbands for sending the second uplink RACH message is selected based on the mapping.

[0191] In some examples, the mapping includes at least one of: a one-to-one mapping between a set of multiple random access opportunities and a set of multiple subbands, a mapping between random access opportunities in a set of multiple random access opportunities and a set of multiple subbands, a mapping between subbands in a set of multiple subbands and a set of multiple random access opportunities, or a combination thereof.

[0192] In some examples, to support receiving an uplink RACH message, the random access channel message component 1430 may be configured to or otherwise support means for receiving one or more uplink random access message instances at one or more random access opportunities in a set of multiple random access opportunities, wherein each of the one or more uplink random access message instances corresponding to a first message of a random access procedure is sent at a different random access opportunity, wherein the same preamble is repeated in each random access message instance. In some examples, one or more random access opportunities in the set of multiple random access opportunities are different in time, frequency, or a combination thereof.

[0193] In some examples, the random access channel message component 1430 may be configured as or otherwise support components for receiving a physical uplink shared message in a subband that overlaps in frequency with a random access opportunity in one or more random access opportunities in a set of multiple subbands, wherein the random access opportunity includes a random access opportunity at which a last uplink random access message instance of one or more uplink random access instances is received, wherein the one or more uplink random access message instances correspond to a first message of a random access procedure.

[0194] In some examples, the random access channel message component 1430 may be configured to or otherwise support components for receiving a physical uplink shared message in a subband in a set of multiple subbands that overlaps in frequency with a random access opportunity in one or more random access opportunities, wherein the random access opportunity includes a random access opportunity at which a first uplink random access message instance corresponding to a first message of a random access process is sent.

[0195] In some examples, the random access channel message component 1430 may be configured to or otherwise support components for receiving a second uplink RACH message in a subband in a set of multiple subbands that overlaps in frequency with a random access opportunity in a set of multiple random access opportunities, wherein the uplink RACH message includes a physical RACH preamble and the second uplink RACH message includes a physical uplink control channel.

[0196] In some examples, the offset parameter indicates at least one of: a same offset for each subband in the set of multiple subbands, a different offset for each subband in the set of multiple subbands, or a combination thereof.

[0197] In some examples, the offset parameter is based on at least one of: a maximum bandwidth of the UE, an initial physical resource block of the uplink bandwidth portion, a subcarrier spacing of the uplink bandwidth portion, or a combination thereof. In some examples, a subband in the set of multiple subbands includes a predefined number of resource blocks.

[0198] Fig.15A diagram of a system 1500 including a device 1505 supporting techniques for frequency resource allocation in a RACH according to one or more aspects of the present disclosure is shown. The device 1505 may be an example of a device 1205, a device 1305, or a network entity 105 as described herein, or include components thereof. The device 1505 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1505 may include components that support output and acquisition of communications, such as a communication manager 1520, a transceiver 1510, an antenna 1515, a memory 1525, a code 1530, and a processor 1535. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1540).

[0199] The transceiver 1510 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1510 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1510 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1505 may include one or more antennas 1515, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1510 may also include a modem for: modulating a signal, providing the modulated signal for transmission (e.g., through one or more antennas 1515, through a wired transmitter), receiving the modulated signal (e.g., from one or more antennas 1515, from a wired receiver), and demodulating the signal. In some implementations, the transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1515 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1515 configured to support various transmitting operations or output operations, or a combination thereof. In some implementations, the transceiver 1510 may include or be configured to be coupled to one or more processors or memory components that are operable to: perform or support operations based on received or obtained information or signals, or generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1510, or the transceiver 1510 and one or more antennas 1515, or the transceiver 1510 and one or more antennas 1515 and one or more processors or memory components (e.g., processor 1535, or memory 1525, or both) may be included in a chip or chip assembly installed in the device 1505. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0200] Memory 1525 may include RAM and ROM. Memory 1525 may store computer-readable, computer-executable code 1530 including instructions that, when executed by processor 1535, cause device 1505 to perform various functions described herein. Code 1530 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1530 may not be directly executable by processor 1535, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1525 may also contain, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0201] The processor 1535 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1535 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1535. The processor 1535 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1525) to cause the device 1505 to perform various functions (e.g., functions or tasks that support techniques for frequency resource allocation in RACH). For example, the device 1505 or a component of the device 1505 may include a processor 1535 and a memory 1525 coupled to the processor 1535, the processor 1535 and the memory 1525 being configured to perform the various functions described herein. The processor 1535 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software, such as an operating system, a virtual machine, or a container example) that can host functions (e.g., by executing code 1530) to perform functions of the device 1505. The processor 1535 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1505 (such as in the memory 1525). In some specific implementations, the processor 1535 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce a set of outputs (which may be delivered to, for example, other systems or components of the device 1505). For example, the processing system of the device 1505 may refer to a system including various other components or subcomponents of the device 1505, such as the processor 1535, or the transceiver 1510, or the communication manager 1520, or other components or combinations of components of the device 1505. The processing system of device 1505 can be docked with other components of device 1505, and can process information (such as input or signal) received from other components or output information to other components. For example, the chip or modem of device 1505 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between the processing system of a chip or modem and a transmitter, so that device 1505 can send information output from the chip or modem. Additionally or alternatively, in some specific implementations, one or more interfaces may refer to an interface between the processing system of a chip or modem and a receiver, so that device 1505 can obtain information or signal input, and the information can be passed to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0202] In some examples, bus 1540 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1540 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1505, or communications performed between different components of device 1505 that may be co-located or may be located in different locations (e.g., where device 1505 may refer to a system in which one or more of communication manager 1520, transceiver 1510, memory 1525, code 1530, and processor 1535 may be located in one of the different components or divided between the different components).

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

[0204] According to examples as disclosed herein, the communication manager 1520 may support wireless communications at a network entity. For example, the communication manager 1520 may be configured to or otherwise support components for sending an indication of an uplink bandwidth portion associated with a random access procedure to a UE, the uplink bandwidth portion comprising a set of a plurality of subbands corresponding to a set of a plurality of random access opportunities. The communication manager 1520 may be configured to or otherwise support components for receiving an uplink RACH message at a random access opportunity in the set of a plurality of random access opportunities, wherein the random access opportunity in the set of a plurality of random access opportunities is based on an offset parameter.

[0205] By including or configuring a communication manager 1520 according to examples as described herein, the device 1505 can support techniques for frequency resource allocation in the RACH, which can result in improved communication reliability, reduced latency, lower power consumption, and more efficient use of communication resources.

[0206] In some examples, the communication manager 1520 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1510, one or more antennas 1515 (e.g., where applicable), or any combination thereof. Although the communication manager 1520 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1520 may be supported or performed by the transceiver 1510, the processor 1535, the memory 1525, the code 1530, or any combination thereof. For example, the code 1530 may include instructions that are executable by the processor 1535 to cause the device 1505 to perform various aspects of the techniques for frequency resource allocation in the RACH as described herein, or the processor 1535 and the memory 1525 may be otherwise configured to perform or support such operations.

[0207] Fig.16 A flow chart illustrating a method 1600 of supporting techniques for frequency resource allocation in RACH according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 11 The described functions may be performed by the UE 115. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0208] At 1605, the method may include receiving an indication of an uplink bandwidth portion associated with a random access procedure, the uplink bandwidth portion including a set of multiple subbands corresponding to a set of multiple random access opportunities. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig.10 The uplink bandwidth portion component 1025 is performed.

[0209] At 1610, the method may include: selecting a random access opportunity from a set of multiple random access opportunities based on an offset parameter. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference Fig.10 The random access opportunity selection component 1030 is executed.

[0210] At 1615, the method may include: sending an uplink RACH message at a random access opportunity in a set of multiple random access opportunities. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig.10 The uplink component 1035 executes.

[0211] Fig.17 A flow chart illustrating a method 1700 of supporting techniques for frequency resource allocation in RACH according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 11 The UE 115 described herein may be executed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0212] At 1705, the method may include receiving an indication of an uplink bandwidth portion associated with a random access procedure, the uplink bandwidth portion including a set of multiple subbands corresponding to a set of multiple random access opportunities. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.10 The uplink bandwidth portion component 1025 is performed.

[0213] At 1710, the method may include receiving a system information message including an offset parameter. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.10 The offset parameter component 1040 is used to perform.

[0214] At 1715, the method may include determining an offset parameter based on receiving a system information message. The operations of 1715 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig.10 The offset parameter component 1040 is used to perform.

[0215] At 1720, the method may include: selecting a random access opportunity from a set of multiple random access opportunities based on the offset parameter. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described in reference Fig.10 The random access opportunity selection component 1030 is executed.

[0216] At 1725, the method may include: sending an uplink RACH message at a random access opportunity in a set of multiple random access opportunities. The operations of 1725 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1725 may be performed as described in reference to Fig.10 The uplink component 1035 executes.

[0217] Fig.18 A flow chart illustrating a method 1800 of supporting techniques for frequency resource allocation in RACH according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 7 and Figures 12 to 15 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0218] At 1805, the method may include: sending an indication of an uplink bandwidth portion associated with a random access procedure to the UE, the uplink bandwidth portion including a set of multiple subbands corresponding to a set of multiple random access opportunities. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.14 The uplink bandwidth portion component 1425 is executed.

[0219] At 1810, the method may include: receiving an uplink RACH message at a random access opportunity in a set of multiple random access opportunities, wherein the random access opportunity in the set of multiple random access opportunities is based on an offset parameter. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.14 The RACH message component 1430 is used to perform.

[0220] Fig.19 A flow chart illustrating a method 1900 of supporting techniques for frequency resource allocation in RACH according to one or more aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 7 and Figures 12 to 15 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0221] At 1905, the method may include: sending an indication of an uplink bandwidth portion associated with a random access procedure to the UE, the uplink bandwidth portion including a set of multiple subbands corresponding to a set of multiple random access opportunities. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Fig.14The uplink bandwidth portion component 1425 is executed.

[0222] At 1910, the method may include: sending a system information message including an offset parameter to the UE. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described in reference Fig.14 The downlink component 1435 is used to perform.

[0223] At 1915, the method may include: receiving an uplink RACH message at a random access opportunity in a set of multiple random access opportunities, wherein the random access opportunity in the set of multiple random access opportunities is based on an offset parameter. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described in reference Fig.14 The RACH message component 1430 is used to perform.

[0224] The following provides an overview of various aspects of the disclosure:

[0225] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving an indication of an uplink bandwidth portion associated with a random access procedure, the uplink bandwidth portion comprising a plurality of subbands corresponding to a plurality of random access opportunities; selecting a random access opportunity from the plurality of random access opportunities based at least in part on an offset parameter; and sending an uplink random access channel message at the random access opportunity among the plurality of random access opportunities.

[0226] Aspect 2: According to the method of aspect 1, the method also includes: receiving a system information message including the offset parameter; and determining the offset parameter based at least in part on receiving the system information message.

[0227] Aspect 3: According to the method described in any one of Aspects 1 to 2, the method further includes: identifying a subband among the multiple subbands that overlaps in frequency with the random access opportunity among the multiple random access opportunities; and sending an initial subset of the physical uplink shared channel in the first resource block of the subband among the multiple subbands.

[0228] Aspect 4: The method described in any one of Aspects 1 to 3, further comprising: sending a second uplink random access channel message in a subband among the multiple subbands that overlaps in frequency with the random access opportunity among the multiple random access opportunities, wherein the uplink random access channel message includes a physical random access channel preamble code, and the second uplink random access channel message includes a physical uplink shared channel.

[0229] Aspect 5: A method according to Aspect 4, wherein sending the second uplink random access channel message in the subband among the multiple subbands includes: receiving a mapping between the multiple random access opportunities and the multiple subbands from a network entity; and selecting the subband among the multiple subbands for sending the second uplink random access channel message based at least in part on the mapping.

[0230] Aspect 6: A method according to Aspect 5, wherein the mapping includes at least one of the following: a one-to-one mapping between the multiple random access opportunities and the multiple subbands, a mapping between the random access opportunities in the multiple random access opportunities and the multiple subbands, a mapping between the subbands in the multiple subbands and the multiple random access opportunities, or a combination thereof.

[0231] Aspect 7: A method according to any one of Aspects 1 to 6, wherein sending the uplink random access channel message further includes: obtaining one or more uplink random access preamble codes at one or more random access opportunities among the multiple random access opportunities, wherein each uplink random access message instance in the one or more uplink random access message instances corresponding to the first message of the random access process is sent at a different random access opportunity, and wherein the same preamble code is repeated in each random access message instance.

[0232] Aspect 8: The method according to aspect 7, wherein the one or more random access opportunities in the plurality of random access opportunities are different in time, frequency, or a combination thereof.

[0233] Aspect 9: According to the method described in any one of Aspects 7 to 8, the method further includes: sending a physical uplink sharing message in a subband in the multiple subbands that overlaps in frequency with the random access opportunity in the one or more random access opportunities, wherein the random access opportunity includes the random access opportunity at which the last uplink random access message instance in the one or more uplink random access message instances is sent, and the one or more uplink random access message instances correspond to the first message of the random access process.

[0234] Aspect 10: According to the method described in any one of Aspects 7 to 9, the method further includes: sending a physical uplink sharing message in a subband in the multiple subbands that overlaps in frequency with the random access opportunity in the one or more random access opportunities, wherein the random access opportunity includes the random access opportunity at which the first uplink random access message instance corresponding to the first message of the random access process is sent.

[0235] Aspect 11: The method described in any one of Aspects 1 to 10, further comprising: sending a second uplink random access channel message in a subband among the multiple subbands that overlaps in frequency with the random access opportunity among the multiple random access opportunities, wherein the uplink random access channel message includes a physical random access channel preamble code, and the second uplink random access channel message includes a physical uplink control channel.

[0236] Aspect 12: A method according to any one of Aspects 1 to 11, wherein the offset parameter indicates at least one of: the same offset for each of the multiple subbands, a different offset for each of the multiple subbands, or a combination thereof.

[0237] Aspect 13: A method according to any one of Aspects 1 to 12, wherein the offset parameter is at least partially based on at least one of the following: the maximum bandwidth of the UE, the initial physical resource block of the uplink bandwidth part, the subcarrier spacing of the uplink bandwidth part, or a combination thereof.

[0238] Aspect 14: The method according to any one of aspects 1 to 13, wherein a subband of the plurality of subbands comprises a predefined number of resource blocks.

[0239] Aspect 15: A method for wireless communication at a network entity, the method comprising: sending an indication of an uplink bandwidth portion associated with a random access process to a UE, the uplink bandwidth portion comprising a plurality of subbands corresponding to a plurality of random access opportunities; and receiving an uplink random access channel message at a random access opportunity among the plurality of random access opportunities, wherein the random access opportunity among the plurality of random access opportunities is at least partially based on an offset parameter.

[0240] Aspect 16: According to the method of aspect 15, the method further includes: sending a system information message including an offset parameter to the UE.

[0241] Aspect 17: According to the method described in any one of Aspects 15 to 16, the method further includes: identifying a subband among the multiple subbands that overlaps in frequency with the random access opportunity among the multiple random access opportunities; and receiving an initial subset of the physical uplink shared channel in the first resource block of the subband among the multiple subbands.

[0242] Aspect 18: The method described in any one of Aspects 15 to 17, the method further comprising: receiving a second uplink random access channel message in a subband among the multiple subbands that overlaps in frequency with the random access opportunity among the multiple random access opportunities, wherein the uplink random access channel message includes a physical random access channel preamble code, and the second uplink random access channel message includes a physical uplink shared channel.

[0243] Aspect 19: A method according to Aspect 18, wherein receiving the second uplink random access channel message in the subband among the multiple subbands includes: sending a mapping between the multiple random access opportunities and the multiple subbands to the UE, wherein the subband among the multiple subbands for sending the second uplink random access channel message is selected at least in part based on the mapping.

[0244] Aspect 20: A method according to Aspect 19, wherein the mapping includes at least one of the following: a one-to-one mapping between the multiple random access opportunities and the multiple subbands, a mapping between the random access opportunities in the multiple random access opportunities and the multiple subbands, a mapping between the subbands in the multiple subbands and the multiple random access opportunities, or a combination thereof.

[0245] Aspect 21: A method according to any one of Aspects 15 to 20, wherein receiving the uplink random access channel message further includes: receiving one or more uplink random access preamble codes at one or more random access opportunities among the multiple random access opportunities, wherein each uplink random access message instance in the one or more uplink random access message instances corresponding to the first message of the random access process is sent at a different random access opportunity, and wherein the same preamble code is repeated in each random access message instance.

[0246] Aspect 22: The method according to aspect 21, wherein the one or more random access opportunities in the plurality of random access opportunities are different in time, frequency, or a combination thereof.

[0247] Aspect 23: According to the method described in any one of Aspects 21 to 22, the method further includes: receiving a physical uplink sharing message in a subband in the multiple subbands that overlaps in frequency with the random access opportunity in the one or more random access opportunities, wherein the random access opportunity includes the random access at which the last uplink random access message instance in the one or more uplink random access instances is received, wherein the one or more uplink random access message instances correspond to the first message of the random access process.

[0248] Aspect 24: According to the method described in any one of Aspects 21 to 23, the method further includes: receiving a physical uplink sharing message in a subband among the multiple subbands that overlaps in frequency with the random access opportunity among the one or more random access opportunities, wherein the random access opportunity includes the random access opportunity at which a first uplink random access message instance corresponding to the first message of the random access process is sent.

[0249] Aspect 25: The method described in any one of Aspects 15 to 24, the method further comprising: receiving a second uplink random access channel message in a subband among the multiple subbands that overlaps in frequency with the random access opportunity among the multiple random access opportunities, wherein the uplink random access channel message includes a physical random access channel preamble code, and the second uplink random access channel message includes a physical uplink control channel.

[0250] Aspect 26: A method according to any one of Aspects 15 to 25, wherein the offset parameter indicates at least one of: the same offset for each of the multiple subbands, a different offset for each of the multiple subbands, or a combination thereof.

[0251] Aspect 27: A method according to any one of Aspects 15 to 26, wherein the offset parameter is based at least in part on at least one of: the maximum bandwidth of the UE, the initial physical resource block of the uplink bandwidth part, the subcarrier spacing of the uplink bandwidth part, or a combination thereof.

[0252] Aspect 28: The method according to any one of aspects 15 to 27, wherein a subband of the plurality of subbands comprises a predefined number of resource blocks.

[0253] Aspect 29: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 14.

[0254] Aspect 30: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing a method according to any one of aspects 1 to 14.

[0255] Aspect 31: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform a method according to any one of aspects 1 to 14.

[0256] Aspect 32: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 15 to 28.

[0257] Aspect 33: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing a method according to any one of aspects 15 to 28.

[0258] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform a method according to any one of aspects 15 to 28.

[0259] It should be noted that the methods described herein describe possible implementations, and that the various operations and steps may be rearranged or otherwise modified, and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0260] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

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

[0262] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0263] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the functions are implemented at different physical locations.

[0264] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that promotes computer program to be transmitted from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code parts and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.In addition, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. As used herein, disks and discs include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks can reproduce data magnetically, and discs can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

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

[0266] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, etc. Additionally, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0267] In the drawings, similar components or features may have the same reference label. In addition, components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.

[0268] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific embodiments include specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0269] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present 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. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving an indication of an uplink bandwidth portion associated with a random access procedure, the uplink bandwidth portion comprising a plurality of subbands corresponding to a plurality of random access opportunities; selecting a random access opportunity from the plurality of random access opportunities based at least in part on an offset parameter; as well as An uplink random access channel message is sent at the random access opportunity among the plurality of random access opportunities.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: receiving a system information message including the offset parameter; and The offset parameter is determined based at least in part on receiving the system information message.

3. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: identifying a subband of the plurality of subbands that overlaps in frequency with the random access opportunity of the plurality of random access opportunities; and An initial subset of a physical uplink shared channel is sent in a first resource block of the subband of the plurality of subbands.

4. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: A second uplink random access channel message is sent in a subband in the plurality of subbands that overlaps in frequency with the random access opportunity in the plurality of random access opportunities, wherein the uplink random access channel message comprises a physical random access channel preamble, and the second uplink random access channel message comprises a physical uplink shared channel.

5. The apparatus of claim 4, wherein the instructions to send the second uplink random access channel message in the subband of the plurality of subbands are executable by the processor to cause the apparatus to: receiving, from a network entity, a mapping between the plurality of random access opportunities and the plurality of subbands; and The subband of the plurality of subbands for transmitting the second uplink random access channel message is selected based at least in part on the mapping.

6. The apparatus of claim 5, wherein the mapping comprises at least one of: a one-to-one mapping between the plurality of random access opportunities and the plurality of subbands, a mapping between the random access opportunities in the plurality of random access opportunities and the plurality of subbands, a mapping between the subbands in the plurality of subbands and the plurality of random access opportunities, or a combination thereof.

7. The apparatus of claim 1, wherein the instructions to send the uplink random access channel message are further executable by the processor to cause the apparatus to: One or more uplink random access message instances are sent at one or more random access opportunities among the multiple random access opportunities, wherein each of the one or more uplink random access message instances corresponding to the first message of the random access process is sent at a different random access opportunity, and wherein the same preamble code is repeated in each random access message instance.

8. The apparatus of claim 7, wherein the one or more random access opportunities of the plurality of random access opportunities are different in time, frequency, or a combination thereof.

9. The apparatus of claim 7, wherein the instructions are further executable by the processor to cause the apparatus to: A physical uplink shared message is sent in a subband in the multiple subbands that overlaps in frequency with the random access opportunity in the one or more random access opportunities, wherein the random access opportunity includes the random access opportunity at which a last uplink random access message instance in the one or more uplink random access message instances is sent, wherein the one or more uplink random access message instances correspond to a first message of the random access procedure.

10. The apparatus of claim 7, wherein the instructions are further executable by the processor to cause the apparatus to: A physical uplink shared message is sent in a subband in the plurality of subbands that overlaps in frequency with the random access opportunity in the one or more random access opportunities, wherein the random access opportunity includes the random access opportunity at which a first uplink random access message instance corresponding to the first message of the random access procedure is sent.

11. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: A second uplink random access channel message is sent in a subband in the plurality of subbands that overlaps in frequency with the random access opportunity in the plurality of random access opportunities, wherein the uplink random access channel message comprises a physical random access channel preamble, and the second uplink random access channel message comprises a physical uplink control channel.

12. The apparatus of claim 1, wherein the offset parameter indicates at least one of: a same offset for each of the plurality of subbands, a different offset for each of the plurality of subbands, or a combination thereof.

13. The apparatus of claim 1, wherein the offset parameter is based at least in part on at least one of: a maximum bandwidth of the UE, an initial physical resource block of the uplink bandwidth portion, a subcarrier spacing of the uplink bandwidth portion, or a combination thereof.

14. The apparatus of claim 1, wherein a subband of the plurality of subbands comprises a predefined number of resource blocks.

15. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: outputting an indication of an uplink bandwidth portion associated with a random access procedure, the uplink bandwidth portion comprising a plurality of subbands corresponding to a plurality of random access opportunities; as well as An uplink random access channel message is obtained at a random access opportunity in the plurality of random access opportunities, wherein the random access opportunity in the plurality of random access opportunities is based at least in part on an offset parameter.

16. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: A system information message including the offset parameter is output.

17. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: identifying a subband of the plurality of subbands that overlaps in frequency with the random access opportunity of the plurality of random access opportunities; and An initial subset of a physical uplink shared channel is obtained in a first resource block of the subband of the plurality of subbands.

18. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: A second uplink random access channel message is obtained in a subband among the multiple subbands that overlaps in frequency with the random access opportunity among the multiple random access opportunities, wherein the uplink random access channel message includes a physical random access channel preamble code, and the second uplink random access channel message includes a physical uplink shared channel.

19. The apparatus of claim 18, wherein the instructions to obtain the second uplink random access channel message in the subband of the plurality of subbands are further executable by the processor to cause the apparatus to: A mapping between the plurality of random access opportunities and the plurality of subbands is output, wherein the subband of the plurality of subbands for transmitting the second uplink random access channel message is selected based at least in part on the mapping.

20. The apparatus of claim 19, wherein the mapping comprises at least one of: a one-to-one mapping between the plurality of random access opportunities and the plurality of subbands, a mapping between the random access opportunities in the plurality of random access opportunities and the plurality of subbands, a mapping between the subbands in the plurality of subbands and the plurality of random access opportunities, or a combination thereof.

21. The apparatus of claim 15, wherein the instructions to obtain the uplink random access channel message are further executable by the processor to cause the apparatus to: One or more uplink random access message instances are obtained at one or more random access opportunities among the multiple random access opportunities, wherein each uplink random access message instance of the one or more uplink random access message instances corresponding to the first message of the random access process is sent at a different random access opportunity, and wherein the same preamble code is repeated in each random access message instance.

22. The apparatus of claim 21, wherein the one or more random access opportunities of the plurality of random access opportunities are different in time, frequency, or a combination thereof.

23. The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to: Obtaining a physical uplink shared message in a subband of the plurality of subbands that overlaps in frequency with the random access opportunity of the one or more random access opportunities, wherein the random access opportunity includes the random access opportunity at which a last uplink random access message instance of the one or more uplink random access instances is received, wherein the one or more uplink random access message instances correspond to a first message of the random access procedure.

24. The apparatus of claim 21, wherein the instructions are further executable by the processor to cause the apparatus to: A physical uplink shared message is obtained in a subband of the plurality of subbands that overlaps in frequency with the random access opportunity of the one or more random access opportunities, wherein the random access opportunity includes the random access opportunity at which a first uplink random access message instance corresponding to the first message of the random access procedure is sent.

25. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: A second uplink random access channel message is obtained in a subband among the plurality of subbands that overlaps in frequency with the random access opportunity among the plurality of random access opportunities, wherein the uplink random access channel message comprises a physical random access channel preamble, and the second uplink random access channel message comprises a physical uplink control channel.

26. The apparatus of claim 15, wherein the offset parameter indicates at least one of: a same offset for each of the plurality of subbands, a different offset for each of the plurality of subbands, or a combination thereof.

27. The apparatus of claim 15, wherein the offset parameter is based at least in part on at least one of: a maximum bandwidth of the UE, an initial physical resource block of the uplink bandwidth portion, a subcarrier spacing of the uplink bandwidth portion, or a combination thereof.

28. The apparatus of claim 15, wherein a subband of the plurality of subbands comprises a predefined number of resource blocks.

29. A method for wireless communication at a user equipment (UE), the method comprising: receiving an indication of an uplink bandwidth portion associated with a random access procedure, the uplink bandwidth portion comprising a plurality of subbands corresponding to a plurality of random access opportunities; selecting a random access opportunity from the plurality of random access opportunities based at least in part on an offset parameter; as well as An uplink random access channel message is sent at the random access opportunity among the plurality of random access opportunities.

30. A method for wireless communication at a network entity, the method comprising: outputting an indication of an uplink bandwidth portion associated with a random access procedure, the uplink bandwidth portion comprising a plurality of subbands corresponding to a plurality of random access opportunities; as well as An uplink random access channel message is obtained at a random access opportunity in the plurality of random access opportunities, wherein the random access opportunity in the plurality of random access opportunities is based at least in part on an offset parameter.

Images