Random access and uplink shared channel opportunity mapping mode for random access procedures

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive control signaling indicating a time domain mapping pattern between one or more random access occasions and one or more physical uplink shared channel (PUSCH) occasions. The UE may transmit one or more preambles of a random access message for a random access procedure in the one or more random access opportunities according to the time domain mapping pattern. In addition, the UE may transmit one or more PUSCHs (e.g., uplink payload transmissions) of the random access message in the one or more PUSCH occasions according to the time domain mapping pattern. In some examples, the UE may receive a random access response message based on the preamble and timing of PUSCH transmissions.

Description

Technical Field

[0001] The following relates to wireless communications, including random access and uplink shared channel opportunity mapping patterns for random access procedures. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. 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 communications for communication devices, which may be referred to as user equipment (UE).

[0003] In some wireless communication systems, as part of a random access procedure, a user equipment (UE) may send a random access message. In some cases, the UE may send a preamble and an uplink payload in the random access message during the corresponding resource period. However, in some cases, different time domain behaviors may be considered for such transmissions. Summary of the invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses that support random access and uplink shared channel timing mapping patterns for random access procedures. For example, the described technology provides mapping patterns for RACH timings and uplink shared channel timings for a two-step random access (RACH) procedure. In some examples, a user equipment (UE) may receive control signaling from a network entity indicating a time domain mapping pattern between one or more RACH timings and one or more uplink shared channel timings. The UE may send one or more preambles of a RACH message in one or more RACH timings according to the indicated time domain mapping pattern. In addition, the UE may send one or more uplink payloads of a RACH message in one or more uplink shared channel timings according to the indicated time domain mapping pattern. In some examples, different RACH and uplink shared channel timing mapping patterns may be associated with one or more repetition levels or synchronization signal blocks (SSBs).

[0005] A method for wireless communication at a UE is described. The method may include: receiving control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure; sending one or more preambles of the random access message of the random access procedure in the one or more random access opportunities according to the time domain mapping pattern; and sending one or more uplink payloads of the random access message of the random access procedure in the one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0006] A device for wireless communication at a UE is described. The device 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 device to: receive control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure; send one or more preambles of a random access message of a random access procedure in one or more random access opportunities according to the time domain mapping pattern; and send one or more uplink payloads of a random access message of a random access procedure in one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0007] Another apparatus for wireless communication at a UE is described. The apparatus may include: a component for receiving control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure; a component for sending one or more preambles of a random access message of the random access procedure in the one or more random access opportunities according to the time domain mapping pattern; and a component for sending one or more uplink payloads of a random access message of the random access procedure in the one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0008] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions that can be executed by a processor to perform the following operations: receiving control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure; sending one or more preambles of the random access message of the random access procedure in the one or more random access opportunities according to the time domain mapping pattern; and sending one or more uplink payloads of the random access message of the random access procedure in the one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0009] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending one or more preambles in one or more consecutive random access opportunities and sending one or more uplink payload transmissions in one or more consecutive uplink shared channel opportunities according to a time domain mapping pattern, wherein the one or more consecutive uplink shared channel opportunities may be after the one or more consecutive random access opportunities.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving control signaling indicating a time domain mapping pattern, wherein the time domain mapping pattern indicates that one or more random access opportunities and one or more uplink shared channel opportunities may be interleaved in the time domain; and sending one or more preamble codes and one or more uplink payload transmissions, wherein the one or more preamble codes and the one or more uplink payload transmissions may be interleaved based on the time domain mapping pattern.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending one or more preambles may include operations, features, components, or instructions for sending one or more preambles in one or more consecutive random access opportunities according to a time domain mapping pattern, and the one or more consecutive random access opportunities may be time division multiplexed (TDM) within one or more random access slots.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending one or more uplink payload transmissions may include operations, features, components, or instructions for sending one or more uplink payload transmissions in one or more consecutive uplink shared channel opportunities that can be TDMed according to a time domain mapping pattern, wherein the one or more uplink payload transmissions may be associated with a subset of one or more preamble codes.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending one or more preambles in one or more random access opportunities and sending a first uplink payload transmission in a first uplink shared channel opportunity in one or more uplink shared channel opportunities according to a time domain mapping pattern.

[0014] 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 first preamble of one or more preambles in a first random access opportunity in one or more random access opportunities and sending one or more uplink payload transmissions in one or more uplink shared channel opportunities according to a time domain mapping pattern.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for the following actions: receiving control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities, the time domain mapping pattern being based on a set of joint preamble and uplink payload transmission repetitions associated with one or more repetition levels, wherein the set of joint preamble and uplink payload transmission repetitions may be TDM, frequency division multiplexed (FDM), or code division multiplexed (CDM).

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, for a set of joint preamble and uplink payload transmission repetitions that may be CDMed, a first joint payload and uplink payload transmission repetition may be associated with one or more repetition levels.

[0017] 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 random access response (RAR) message in a RAR window, wherein a start of the RAR window may be based on a last preamble of one or more preambles associated with a first repetition level or a last symbol of a last uplink payload transmission of one or more uplink payload transmissions.

[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 set of joint preamble and uplink payload transmission repetitions, wherein the set of joint preamble and uplink payload transmission repetitions may be associated with one or more SSBs of a given repetition level.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for selecting a first joint preamble and uplink payload transmission repetition from a set of joint preamble and uplink payload transmission repetitions based on an SSB associated with the first joint preamble and uplink payload transmission repetition that corresponds to a highest identified reference signal received power (RSRP).

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a number of SSBs associated with a highest identified RSRP may be associated with a repetition level.

[0021] A method for wireless communication at a network entity is described. The method may include: sending control signaling indicating a time domain mapping pattern between one or more random access opportunities for sending a random access message of a random access procedure and one or more uplink shared channel opportunities; receiving one or more preambles of the random access message of the random access procedure in the one or more random access opportunities according to the time domain mapping pattern; and receiving one or more uplink payload transmissions of the random access message of the random access procedure in the one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0022] 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 control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure; receive one or more preambles of a random access message of the random access procedure in the one or more random access opportunities according to the time domain mapping pattern; and receive one or more uplink payload transmissions of a random access message of the random access procedure in the one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0023] Another apparatus for wireless communication at a network entity is described. The apparatus may include: a component for sending control signaling indicating a time domain mapping pattern between one or more random access opportunities for sending a random access message of a random access procedure and one or more uplink shared channel opportunities; a component for receiving one or more preambles of a random access message of the random access procedure in the one or more random access opportunities according to the time domain mapping pattern; and a component for receiving one or more uplink payload transmissions of a random access message of the random access procedure in the one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0024] 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 perform the following operations: sending control signaling indicating a time domain mapping pattern between one or more random access opportunities for sending a random access message of a random access procedure and one or more uplink shared channel opportunities; receiving one or more preambles of the random access message of the random access procedure in the one or more random access opportunities according to the time domain mapping pattern; and receiving one or more uplink payload transmissions of the random access message of the random access procedure in the one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving one or more preambles in one or more consecutive random access opportunities and receiving one or more uplink payload transmissions in one or more consecutive uplink shared channel opportunities according to a time domain mapping pattern, wherein the one or more consecutive uplink shared channel opportunities may be after the one or more consecutive random access opportunities.

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: sending control signaling indicating a time domain mapping pattern, wherein the time domain mapping pattern indicates that one or more random access opportunities and one or more uplink shared channel opportunities may be interleaved in the time domain; and receiving one or more preamble codes and one or more uplink payload transmissions, wherein the one or more preamble codes and the one or more uplink payload transmissions may be interleaved based on the time domain mapping pattern.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving one or more preambles may include operations, features, components, or instructions for receiving one or more preambles in one or more consecutive random access opportunities according to a time domain mapping pattern, the one or more consecutive random access opportunities being TDM within one or more random access slots.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving one or more uplink payload transmissions may include operations, features, components, or instructions for receiving one or more uplink payload transmissions in one or more consecutive uplink shared channel opportunities that may be TDMed according to a time domain mapping pattern, wherein the one or more uplink payload transmissions may be associated with a subset of one or more preamble codes.

[0029] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving one or more preambles in one or more random access opportunities and receiving a first uplink payload transmission in a first uplink shared channel opportunity in one or more uplink shared channel opportunities according to a time domain mapping pattern.

[0030] 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 first preamble of one or more preambles in a first random access opportunity in one or more random access opportunities according to a time domain mapping pattern and receiving one or more uplink payload transmissions in one or more uplink shared channel opportunities.

[0031] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities, the time domain mapping pattern being based on a set of joint preamble and uplink payload transmission repetitions associated with one or more repetition levels, wherein the set of joint preamble and uplink payload transmission repetitions may be TDM, FDM, or CDM.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, for a set of joint preamble and uplink payload transmission repetitions that may be CDMed, a first joint payload and uplink payload transmission repetition may be associated with one or more repetition levels.

[0033] 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 RAR message in a RAR window, wherein the start of the RAR window may be based on a last preamble of one or more preambles associated with a first repetition level or a last symbol of a last uplink payload transmission of one or more uplink payload transmissions.

[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 set of joint preamble and uplink payload transmission repetitions, wherein the set of joint preamble and uplink payload transmission repetitions may be associated with one or more SSBs of a given repetition level.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a number of SSBs associated with a highest identified RSRP may be associated with a repetition level. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 An example of a wireless communication system supporting random access and uplink shared channel opportunity mapping patterns for a random access procedure according to one or more aspects of the present disclosure is illustrated.

[0037] Figure 2 An example of a wireless communication system supporting random access and uplink shared channel opportunity mapping patterns for a random access procedure according to one or more aspects of the present disclosure is illustrated.

[0038] Figures 3 to 9 An example of a time domain mapping pattern supporting random access and uplink shared channel opportunity mapping pattern for a random access procedure according to one or more aspects of the present disclosure is illustrated.

[0039] Fig.10 An example of a process flow supporting random access and uplink shared channel opportunity mapping patterns for a random access procedure in accordance with one or more aspects of the present disclosure is illustrated.

[0040] Fig.11 and Fig.12 A block diagram of an apparatus supporting random access and uplink shared channel opportunity mapping patterns for a random access procedure in accordance with one or more aspects of the present disclosure is shown.

[0041] Fig.13 A block diagram of a communication manager supporting random access and uplink shared channel opportunity mapping patterns for a random access procedure is shown in accordance with one or more aspects of the present disclosure.

[0042] Fig.14 A diagram of a system including a device supporting random access and uplink shared channel opportunity mapping patterns for a random access procedure in accordance with one or more aspects of the present disclosure is shown.

[0043] Fig.15 and Fig.16 A block diagram of an apparatus supporting random access and uplink shared channel opportunity mapping patterns for a random access procedure in accordance with one or more aspects of the present disclosure is shown.

[0044] Fig.17 A block diagram of a communication manager supporting random access and uplink shared channel opportunity mapping patterns for a random access procedure is shown in accordance with one or more aspects of the present disclosure.

[0045] Fig.18 A diagram of a system including a device supporting random access and uplink shared channel opportunity mapping patterns for a random access procedure in accordance with one or more aspects of the present disclosure is shown.

[0046] Figures 19 to 24 A flow chart illustrating a method of supporting random access and uplink shared channel opportunity mapping patterns for a random access procedure according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0047] A user equipment (UE) may perform a two-step random access procedure (also referred to herein as a RACH procedure). The two-step random access procedure may include the transmission of a first message (e.g., MsgA) and a second message (e.g., MsgB), wherein the first message may include a RACH preamble transmission and an uplink payload transmission. In some cases, because of the minimum transmission gap between the preamble and the uplink payload, the UE may use a specific mapping pattern to map the RACH opportunity to the physical uplink shared channel (PUSCH) opportunity for the transmission of the first message. For example, the UE may map each consecutive number of preamble indices from a valid RACH opportunity in a given time slot to a valid PUSCH opportunity in an associated demodulation reference signal (DMRS) resource. However, specifying the details of the RACH opportunity-PUSCH opportunity mapping pattern when considering the joint transmission of the preamble and uplink payload repetitions may reduce the latency of the RACH process without limiting the coverage of the UE. For example, the UE may consider some different time domain behaviors for a specific joint RACH opportunity and PUSCH opportunity repetition, repetition level, and synchronization signal block (SSB), which may affect the mapping pattern.

[0048] The described techniques support mapping patterns of RACH opportunities and uplink shared channel (e.g., PUSCH) opportunities for a two-step RACH procedure. In some examples, a UE may receive control signaling from a network entity indicating a time domain mapping pattern between one or more RACH opportunities and one or more uplink shared channel opportunities. The UE may send one or more preambles of a RACH message in one or more RACH opportunities according to the indicated time domain mapping pattern. In addition, the UE may send one or more uplink payloads of a RACH message in one or more uplink shared channel opportunities according to the indicated time domain mapping pattern. In some examples, different RACH and uplink shared channel opportunity mapping patterns may be associated with one or more repetition levels or SSBs, and the UE may select a specific mapping pattern for a RACH procedure.

[0049] Various aspects of the present disclosure are first described in the context of a wireless communication system. Various aspects of the present disclosure are then described in the context of a time domain mapping pattern and process flow. Various aspects of the present disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow diagrams related to random access and uplink shared channel opportunity mapping patterns for a random access procedure.

[0050] Figure 1 An example of a wireless communication system 100 that supports random access and uplink shared channel opportunity mapping patterns for a random access procedure 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.

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

[0052] 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 be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices, such as Figure 1 Other UEs 115 or network entities 105 are shown.

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

[0054] 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 via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication links 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication links 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, the midhaul communication links 162, or the 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 .

[0055] 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 terminology). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in a converged (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).

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

[0057] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functions, 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 can be employed between CU 160 and DU 165, such that CU 160 can support one or more layers of a protocol stack and DU 165 can support one or more different layers of a protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions 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) functions 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 DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 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 a protocol layer (e.g., some functions of a 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 a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) 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., an open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to an interface (eg, a channel) between layers of a protocol stack supported by respective network entities 105 that communicate via such communication links.

[0058] In some wireless communication systems (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 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., 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 (e.g., of the RU 170) of the IAB node 104 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.

[0059] In the case 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 random access and uplink shared channel opportunity mapping patterns for random access procedures as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

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

[0061] 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, or relay base stations, etc. Figure 1 shown.

[0062] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. 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 of an RF spectrum band (e.g., a bandwidth portion (BWP)) 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) 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 portion (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 portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

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

[0064] 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, among other transmission configurations. A carrier may carry either downlink communications or uplink communications (e.g., in an FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in a TDD mode).

[0065] 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 (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz) of a carrier of a particular radio access technology. A device (e.g., a network entity 105, a UE 115, or both) of the wireless communication system 100 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 a 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 sub-band, a BWP) or all of a carrier bandwidth.

[0066] The signal waveform transmitted via the carrier may include 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 technology, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a resource of a 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 rate of communication. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0067] One or more parameter sets for a carrier may be supported, and a parameter set may include a subcarrier spacing ( ) and cyclic prefix. 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.

[0068] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period. Seconds, for this may indicate the supported subcarrier spacing, and 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., ranging from 0 to 1023).

[0069] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may 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., The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0070] A subframe, a slot, a mini-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)).

[0071] According to various techniques, physical channels may be multiplexed using carriers for communication. Physical control channels and physical data channels may be multiplexed for signaling via downlink carriers, 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 of a carrier or a subset of that system bandwidth. 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 multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0072] 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 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) on 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, and the like.

[0073] A macro cell generally 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. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) (compared to a macro cell), and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell 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 the small cell (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.

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

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

[0076] 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 synchronous or asynchronous operation.

[0077] Some UEs 115 may be configured to employ an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports unidirectional 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 UEs 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 subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.

[0078] 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 or low-latency or critical functions. Ultra-reliable communications may include private communications or group communications 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.

[0079] In some examples, a UE 115 may be configured to support communication directly with other UEs 115 via 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.

[0080] 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 stratum (NAS) functions such as mobility, authentication, and bearer management of UEs 115 served by network entities 105 (e.g., base stations 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 services 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.

[0081] 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) compared to communications using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0082] The wireless communication system 100 may also operate using a super high frequency (SHF) region (also known as a centimeter band) that may be in the range of 3 GHz to 30 GHz or 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) communications between a UE 115 and a network entity 105 (e.g., a base station 140, a RU 170), and the EHF antennas of the corresponding devices may be smaller and closer together than UHF antennas. In some examples, such technology may facilitate the use of antenna arrays within a device. However, the propagation of EHF transmissions may be affected by 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.

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

[0084] 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) communication, 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 set of antenna ports of multiple rows and columns 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.

[0085] 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), for which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are sent to multiple devices.

[0086] 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 communicated via antenna elements of an antenna array so that some signals propagating along a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated 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 direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

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

[0088] A UE 115 in the wireless communication system 100 may perform a random access procedure (also referred to as a RACH procedure). In some examples, a first transmission of a RACH procedure may be referred to as a Msg1 preamble for a 4-step RACH procedure (e.g., a physical random access channel (PRACH)) or a message A (MsgA) preamble or PUSCH for a 2-step RACH procedure. A second transmission of a RACH procedure may be referred to as a message 2 preamble for a 4-step RACH procedure (e.g., a random access response (RAR) message) and a message B (MsgB) message for a 2-step RACH procedure. The 4-step RACH procedure may additionally include a third transmission referred to as a scheduled transmission (e.g., a PUSCH repetition) of Msg3, and a fourth transmission referred to as a contention resolution message of Msg4.

[0089] In some examples, UE 115 may request Msg3 PUSCH repetition via one or more PRACH resources, where the criteria for Msg3 repetition request may be based on synchronization signal reference signal received power (SS-RSRP). In some cases, UE 115 may use PRACH repetition for 4-step RACH and preamble repetition for 4-step RACH.

[0090] Some UEs 115 may use a RACH opportunity-PUSCH opportunity mapping pattern to perform a two-step RACH procedure. In some examples, the minimum transmission gap (eg, T gap ) can be 2 symbols (e.g., µ = 0 or 1) or 4 symbols (e.g., µ = 2 or 3). In addition, the RACH opportunity and the associated PUSCH opportunity can be located in different time slots. In this RACH opportunity-PUSCH opportunity mapping pattern, each consecutive number N of valid RACH opportunities in a RACH time slot (also called PRACH opportunities in a PRACH time slot) is preamble The preamble index may be mapped to a valid PUSCH opportunity and associated DMRS resources. That is, there may be one or more RACH opportunities associated with a preamble mapped to a single PUSCH opportunity, where the PUSCH opportunity may be intra-slot or inter-slot.

[0091] In some examples, the network entity 105 may map the RACH opportunities in increasing order of preamble index within a single RACH opportunity, in increasing order of frequency resource index of RACH opportunities for frequency reuse, or in increasing order of time resource index of RACH opportunities for time reuse within a RACH slot. Thus, the RACH opportunities may be mapped in increasing order of frequency resource index of PUSCH opportunities for frequency reuse. id The DMRS resource index DMRS is mapped to the PUSCH opportunity in the increasing order of the DMRS resource index within the PUSCH opportunity, where the DMRS resource index DMRS id First, in ascending order of DMRS port index, then in ascending order of DMRS resource index, and then in ascending order of time resource index t for PUSCH timing used for time multiplexing within PUSCH time slot. id In ascending order, or in the order used for N s The increasing order of the index of the PUSCH time slots is determined. ,in may represent the total number of RACH opportunities per associated mode period multiplied by the number of preambles per RACH opportunity provided by rach-ConfigCommonTwoStepRA, and The total number of PUSCH opportunities per PUSCH configuration per associated mode period may be represented by multiplying the number of DMRS resource indices per valid PUSCH opportunity provided by msgA-DMRS-Config.

[0092] In some cases, when considering joint MsgA preamble and MsgA payload (e.g., PUSCH) repetition, details of the RACH opportunity-PUSCH opportunity mapping pattern may be lacking. For example, the network entity 105 may consider different time domain behaviors of joint preamble and PUSCH repetition. In some examples, the network entity 105 may repeat the MsgA preamble first and then repeat the MsgA PUSCH transmission. Alternatively, the network entity 105 may interleave the MsgA preamble and PUSCH repetition. When the network entity 105 uses different repetition levels, the RACH opportunity-PUSCH opportunity mapping patterns of different repetition levels may be time division multiplexed (TDM), frequency division multiplexed (FDM), or code division multiplexed (CDM). If the network entity 105 uses different SSBs, the different repetitions may be associated with the same SSB or different SSBs. Therefore, if the network entity 105 fails to specify the time domain behavior, repetition level usage, and SSB association for the RACH opportunity-PUSCH opportunity mapping pattern, the UE 115 may experience increased latency and reduced signaling throughput.

[0093] The wireless communication system 100 supports including additional details to the 2-step RACH procedure RACH opportunity-PUSCH opportunity mapping pattern, which can support joint MsgA preamble and MsgA PUSCH repetition. Using the techniques described herein, the network entity 105 can include time domain behavior, repetition level, and SSB in the RACH opportunity-PUSCH opportunity mapping pattern. The UE 115 can receive control signaling indicating a time domain mapping pattern between one or more RACH opportunities and one or more PUSCH (e.g., uplink shared channel) opportunities for sending random access messages in the RACH process. The UE 115 can send one or more preambles (e.g., MsgA preambles) of the random access message in one or more RACH opportunities according to the time domain mapping pattern, and send one or more uplink payload transmissions (e.g., MsgA PUSCH transmissions) in one or more PUSCH opportunities according to the time domain mapping pattern. In this way, the UE 115 can achieve reduced latency and increased signaling throughput while maintaining its coverage.

[0094] Figure 2An example of a wireless communication system 200 that supports random access and uplink shared channel opportunity mapping patterns for a random access procedure in accordance with one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100, or may be implemented by aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a UE 115-a and a network entity 105-a (which may be examples of corresponding devices as described herein). In some examples, the UE 115-a may perform a 2-step RACH procedure, during which the UE 115-a may send one or more preambles and one or more uplink payload transmissions (e.g., PUSCH transmissions) of a random access message for the RACH procedure.

[0095] The wireless communication system 200 may support communication between the UE 115-a and the network entity 105-a. For example, the UE 115-a may receive downlink transmissions from the network entity 105-a and send uplink transmissions to the network entity 105-a via the corresponding communication link 205, which may be a reference Figure 1 An example of a communication link 125 described. In some examples, UE 115-a may receive control signaling 210 from network entity 105-a. Control signaling 210 may indicate a time domain mapping pattern between one or more RACH opportunities 215 and one or more PUSCH opportunities 220 (e.g., uplink shared channel opportunities) for sending a random access message of a RACH procedure. That is, the random access message may be a MsgA transmission (e.g., a first transmission) of a RACH procedure.

[0096] In some cases, the UE 115-a may send one or more preambles 225 in one or more RACH opportunities 215 according to the time domain mapping pattern. The preamble 225 may be part of a random access message (e.g., MsgA) of the RACH process. In addition, the UE 115-a may send one or more uplink payload transmissions 230 in one or more PUSCH opportunities 220 according to the time domain mapping pattern. In some cases, the UE 115-a may send one or more repetitions of the preamble 225 and the uplink payload transmission 230 based on the pattern of the RACH opportunities 215 and the PUSCH opportunities 220. For example, the UE 115-a may repeat the preamble 225 and then continuously repeat the uplink payload transmission 230, or the UE 115-a may interleave the preamble 225 and the uplink payload transmission 230 based on interleaved RACH opportunities and PUSCH opportunities.

[0097] The time domain mapping pattern may detail the mapping between RACH opportunities 215 and PUSCH opportunities 220. In some cases, the time domain mapping pattern may specify the time domain behavior of the RACH opportunities 215 and the PUSCH opportunities 220. For example, the network entity 105-a may continuously repeat the RACH opportunities 215 and then continuously repeat the PUSCH opportunities 220, or the network entity 105-a may interleave the PUSCH opportunities 220 between the RACH opportunities 215. The network entity 105-a may also map the RACH opportunities 215 and the PUSCH opportunities 220 to specific resources (e.g., PRACH time slots and PUSCH time slots, respectively). The UE 115-a may use the RACH opportunities 215 and the PUSCH opportunities 220 to send a preamble and a PUSCH transmission of a random access message, respectively. Reference is made to Figure 3 and Figure 4 Such time domain behavior of the RACH occasion 215 and the PUSCH occasion 220 is described.

[0098] In some examples, the network entity 105-a may configure a time domain mapping pattern so that the UE 115-a may only repeat the preamble or PUSCH transmission of the random access message. For example, the UE 115-a may send preamble repetitions in multiple RACH opportunities 215 and send a single PUSCH in a single PUSCH opportunity 220, or the UE 115-a may send a single preamble in a single RACH opportunity 215 and send one or more PUSCH repetitions in one or more PUSCH opportunities 220 according to the time domain mapping pattern. Figure 5 and Figure 6 Such repetitive patterns are described.

[0099] Additionally or alternatively, the network entity 105-a may multiplex the RACH opportunities 215 and the PUSCH opportunities 220 between different repetition levels. For example, the mapped RACH opportunity-PUSCH opportunity pairs associated with different repetition levels may be TDM, FDM, or CDM. As indicated by the network entity 105-a, the UE 115-a may send different preambles and DMRS resources for the corresponding RACH opportunities 215 and PUSCH opportunities 220 based on the corresponding repetition levels. Figure 7 A repeating horizontal configuration is described.

[0100] In some cases, the network entity 105-a may send a RAR message (e.g., the second message of the RACH process, MsgB) to the UE 115-a based on the time domain mapping pattern. For example, the network entity 105-a may determine the start of the RAR window based on the last preamble of a particular repetition level or the last symbol of the PUSCH repetition. The RAR window may be based on the repeated preamble 225 and the corresponding RACH opportunity 215, the repeated uplink payload transmission 230 and the corresponding PUSCH opportunity 220, or a combination thereof. Figure 8 RAR messaging is described.

[0101] In some examples, the network entity 105-a may multiplex different RACH opportunities 215 and PUSCH opportunities 220 based on different SSBs. For example, different joint preambles and PUSCH repetitions may be associated with the same SSB or different SSBs, and the UE 115-a may select a particular time domain mapping mode based on the measured RSRP of one or more SSBs. Fig. 9 Describes the time domain mapping mode based on one or more SSBs.

[0102] Figure 3 An example of a time domain mapping pattern 300 that supports random access and uplink shared channel timing mapping patterns for a random access procedure according to one or more aspects of the present disclosure is illustrated. In some examples, the time domain mapping pattern 300 may implement aspects of the wireless communication systems 100 and 200, or may be implemented by aspects of the wireless communication systems 100 and 200. For example, the network entity 105-a may configure the time domain mapping pattern 300-a and the time domain mapping pattern 300-b to each include one or more RACH opportunities 305 and one or more PUSCH opportunities 315 (e.g., uplink shared channel opportunities). In some examples, the time domain mapping pattern 300-a may include consecutive RACH opportunities and PUSCH opportunities, and the time domain mapping pattern 300-b may include interleaved RACH opportunities and PUSCH opportunities.

[0103] The UE 115-a may identify one or more RACH opportunities 305 and one or more PUSCH opportunities 315 for joint MsgA preamble and MsgAPUSCH transmission based on the configuration indicated from the network entity 105-a. For example, the UE 115-a may receive control signaling indicating the time domain mapping mode 300-a or the time domain mapping mode 300-b, wherein the time domain mapping mode 300 may include one or more RACH opportunities 305 and one or more PUSCH opportunities 315 for transmitting a random access message of a RACH procedure. That is, the random access message (e.g., MsgA) may be the first transmission of a 2-step RACH procedure including a preamble and a PUSCH (e.g., uplink payload) transmission. The network entity 105-a may transmit the control signaling via remaining minimum system information (RMSI) or UE-specific RRC signaling.

[0104] The time domain mapping pattern 300-a may be based on repetition of RACH opportunities 305 including corresponding preambles and PUSCH opportunities 315 including corresponding uplink payload transmissions (e.g., PUSCH transmissions). For example, the network entity 105-a may configure the time domain mapping pattern 300-a such that the UE 115-a repeats one or more MsgA preambles based on a corresponding set of RACH opportunities 305 and then repeats one or more MsgA PUSCH transmissions based on a corresponding set of PUSCH opportunities 315.

[0105] With respect to the time domain mapping pattern 300-a, the network entity 105-a may configure a set of twelve RACH opportunities (also referred to herein as RO) across the time domain, the frequency domain, and the preamble-based domain in the PRACH slot 325-a. The twelve RACH opportunities may include four RACH opportunities 305 and eight RACH opportunity repetitions 310. The RACH opportunities 305 may include RACH opportunities 305 RO#1, RO#4, RO#7, and RO#10 repeated in the time domain. In addition, RO#1 may correspond to two RACH opportunity repetitions 310 RO#2 and RO#3 in the frequency domain, RO#4 may correspond to two RACH opportunity repetitions 310 RO#5 and RO#6 in the frequency domain, RO#7 may correspond to two RACH opportunity repetitions 310 RO#8 and RO#9 in the frequency domain, and RO#10 may correspond to two RACH opportunity repetitions 310 RO#11 and RO#12 in the frequency domain.

[0106] In addition, each RACH opportunity 305 and each RACH opportunity repetition 310 (including RO#1 to RO#12) may correspond to one or more preambles. For example, the RACH opportunity 305 corresponding to RO#1 may correspond to two preamble repetitions (such as the two RACH opportunities 305 RO#1 shown). RO#4, RO#7, and RO#10 may each correspond to two different preambles. In this way, the PRACH time slot 325-a may include four MsgA preamble repetitions 335-a for two different preambles.

[0107] In addition, the network entity 105-a may configure a set of twelve PUSCH opportunities (also referred to herein as PO) across the time domain, frequency domain, and DMRS-based domain in the PUSCH time slot 330. The twelve PUSCH opportunities may include four PUSCH opportunities 315 and eight PUSCH opportunity repetitions 320. The PUSCH time slot 330-a may include PUSCH opportunities 315 PO#1 and PO#4 repeated in the time domain. In addition, PO#1 may correspond to two PUSCH opportunity repetitions 320 PO#2 and PO#3 in the frequency domain, and PO#4 may correspond to two PUSCH opportunity repetitions 320 PO#5 and PO#6 in the frequency domain. The PUSCH time slot 330-b may include PUSCH opportunities 315 PO#7 and PO#10 repeated in the time domain. In addition, PO#7 may correspond to two PUSCH opportunity repetitions 320 PO#8 and PO#9 in the frequency domain, and PO#10 may correspond to two PUSCH opportunity repetitions 320 PO#11 and PO#12 in the frequency domain. Thus, the network entity 105-a may repeat four PUSCH opportunities 315 across PUSCH time slots 330-a and PUSCH time slots 330-b, wherein each PUSCH opportunity 315 is associated with a DMRS resource.

[0108] In this way, the network entity 105-a can map the PRACH repetitions 340-a for two different preambles to the same set of MsgAPUSCH repetitions 335-a. In addition, according to the time domain mapping pattern 300-a, the UE 115-a can send one or more preambles in one or more consecutive RACH opportunities 305 and send one or more uplink payload transmissions in one or more consecutive PUSCH opportunities 315, wherein the consecutive PUSCH opportunities 315 are after the consecutive RACH opportunities 305.

[0109] The time domain mapping pattern 300-b may be based on the interleaving of RACH opportunities 305 including corresponding preambles and PUSCH opportunities 315 including corresponding uplink payload transmissions (e.g., PUSCH transmissions). For example, the network entity 105-a may configure the time domain mapping pattern 300-b such that the UE 115-a interleaves (e.g., staggers) MsgA preamble repetitions and MsgA PUSCH repetitions in the time domain based on interleaving the RACH opportunities 305 and the PUSCH opportunities 315 in the time domain. The UE 115-a may receive control signaling from the network entity 105-a indicating the time domain mapping pattern 300-b, the time domain mapping pattern indicating that one or more RACH opportunities 305 and one or more PUSCH opportunities 315 are interleaved in the time domain.

[0110] As described with reference to the time domain mapping pattern 300-a, the time domain mapping pattern 300-b may include a set of twelve RACH opportunities across the time domain, frequency domain, and preamble-based domain in the PRACH slot 325-b and the PRACH slot 325-c. The PRACH slot 325-b may include RACH opportunities 305 RO#1 and RO#4 repeated in the time domain. In addition, RO#1 may correspond to two RACH opportunity repetitions 310 RO#2 and RO#3 in the frequency domain, and RO#4 may correspond to two RACH opportunity repetitions 310 RO#5 and RO#6 in the frequency domain. The PRACH slot 325-c may include RACH opportunities 305 RO#7 and RO#10 repeated in the time domain. In addition, RO#7 may correspond to two RACH opportunity repetitions 310 RO#8 and RO#9 in the frequency domain, and RO#10 may correspond to two RACH opportunity repetitions 310 RO#11 and RO#12 in the frequency domain. As described herein, each RACH opportunity 305 may correspond to two preambles that UE 115-a may transmit.Thus, there may be four RACH opportunities 305 that are repeated across PRACH slots 325-b and PRACH slots 325-c.

[0111] In addition, the network entity 105-a may configure a PUSCH time slot 330-c after the PRACH time slot 325-b and before the PRACH time slot 325-c, and configure a PUSCH time slot 330-d after the PRACH time slot 325-c, so that the PRACH time slot 325 and the PUSCH time slot 330 are interleaved. The PUSCH time slot 330-c may include PUSCH opportunities 315 PO#1 and PO#4 repeated in the time domain. In addition, PO#1 may correspond to two PUSCH opportunity repetitions 320 PO#2 and PO#3 in the frequency domain, and PO#4 may correspond to two PUSCH opportunity repetitions 320 PO#5 and PO#6 in the frequency domain. The PUSCH time slot 330-d may include PUSCH opportunities 315 PO#7 and PO#10 repeated in the time domain. Furthermore, PO#7 may correspond to two PUSCH opportunity repetitions 320 PO#8 and PO#9 in the frequency domain, and PO#10 may correspond to two PUSCH opportunity repetitions 320 PO#11 and PO#12 in the frequency domain. Each PUSCH opportunity 315 may correspond to a DMRS resource.

[0112] Thus, PUSCH slot 330-c and PUSCH slot 330-d may include four MsgA PUSCH repetitions 340-b. UE 115-a may send one or more preambles and one or more uplink payload transmissions (e.g., PUSCH transmissions), where the preambles and uplink payload transmissions may be interleaved based on the interleaved RACH opportunities and PUSCH opportunities of the time domain mapping pattern 300-b.

[0113] In some examples, the time domain mapping pattern 300 may include a MsgA preamble repetition resource mapping. That is, the network entity 105-a may map repetitions of the MsgA preamble to consecutive TDM RACH opportunities 305 within a single PRACH slot 325, or to consecutive TDM RACH opportunities 305 across multiple PRACH slots 325 (e.g., repeated between or within slots). For example, four MsgA preamble repetitions 335-a (corresponding to RO#1, RO#4, RO#7, and RO#10 of the time domain mapping pattern 300-a) may be TDMed within the PRACH slot 325-a. Alternatively, the preamble repetitions 335-b (corresponding to RO#1, RO#4, RO#7, and RO#10 of the time domain mapping pattern 300-b) may be TDMed across multiple PRACH slots 325 (including PRACH slots 325-b and PRACH slots 325-c). Thus, the UE 115 - a may send one or more preambles in one or more consecutive RACH opportunities 215 TDMed with one or more PRACH slots 325 of the time domain mapping pattern 300 - a.

[0114] Additionally or alternatively, the time domain mapping pattern 300 may specify MsgA PUSCH repetition resources with respect to a given MsgA preamble. That is, the network entity 105-a may map the MsgA PUSCH repetitions associated with a particular set of MsgA preamble repetitions to consecutive intra-slot or inter-slot TDM PUSCH opportunities 315. If the network entity 105-a uses consecutive inter-slot TDM PUSCH opportunities 315, the network entity 105-a may define a priority order between the intra-slot and inter-slot TDM PUSCH opportunities 315. For example, when considering the mapping priority order, a group of consecutive TDM PUSCH opportunities 315 may be considered as a "bit virtual" PUSCH opportunity, where the PUSCH opportunity ordering may first be based on the PUSCH opportunity group, then the frequency domain, then the DMRS-based domain, and then the time domain, regardless of whether the PUSCH opportunity 315 is intra-slot or inter-slot. The UE 115 - a may send one or more uplink payload transmissions in one or more consecutive PUSCH opportunities 315 that are TDMed according to the time-domain mapping pattern 300 - a , wherein the one or more uplink payload transmissions are associated with a subset of one or more preamble codes.

[0115] Figure 4 An example of a time domain mapping pattern 400 that supports random access and uplink shared channel timing mapping patterns for a random access procedure according to one or more aspects of the present disclosure is illustrated. In some examples, the time domain mapping pattern 400 may implement aspects of the wireless communication systems 100 and 200, or may be implemented by aspects of the wireless communication systems 100 and 200. For example, the network entity 105-a may configure the time domain mapping pattern 400-a and the time domain mapping pattern 400-b to include one or more RACH opportunities 405 and one or more PUSCH opportunities 415 (e.g., uplink shared channel opportunities). In some examples, the time domain mapping pattern 400 may include an example of time domain interleaving between the RACH opportunities 405 and the PUSCH opportunities 415, such as reference 105-a. Figure 3 as described.

[0116] The time domain mapping pattern 400 may be based on interleaving of RACH opportunities 405 including corresponding preambles and RACH opportunity repetitions 410 and PUSCH opportunities 415 including corresponding uplink payload transmissions (e.g., PUSCH transmissions) and PUSCH opportunity repetitions 420. For example, the network entity 105-a may configure the time domain mapping pattern 400 such that the UE 115-a interleaves (e.g., staggers) MsgA preamble repetitions and MsgA PUSCH repetitions in the time domain based on interleaving the RACH opportunities 405 and the PUSCH opportunities 415 in the time domain.

[0117] With respect to the time domain mapping pattern 400-a, the network entity 105-a may configure a set of twelve RACH opportunities (also referred to herein as RO) across the time domain, the frequency domain, and the preamble-based domain in the PRACH slot 425. The twelve RACH opportunities may include four RACH opportunities 405 and eight RACH opportunity repetitions 410. In addition, the network entity 105-a may configure a set of twelve PUSCH opportunities (also referred to herein as PO) across the time domain, the frequency domain, and the DMRS-based domain in the PUSCH slot 430.

[0118] The time domain mapping pattern 400-a may include a PRACH slot 425-a that includes a RACH opportunity 405 RO#1 with RACH opportunity repetitions 410 RO#2 and RO#3 in the frequency domain. In some examples, RO#1 may correspond to two different preambles. The time domain mapping pattern 400-a may then specify a PUSCH slot 430-a that includes a PUSCH opportunity 415 PO#1 with PUSCH opportunity repetitions 420 PO#2 and PO#3 in the frequency domain. PO#1 may correspond to a single DMRS or other uplink payload transmission. Since the PUSCH slot 430-a is after the PRACH slot 425-a, the PRACH slot 425 and the PUSCH slot 430 (and the corresponding RACH opportunity 405 and PUSCH opportunity 415) of the time domain mapping pattern 400-a are interlaced.

[0119] In addition, the time domain mapping pattern 400-a may include a PRACH slot 425-b, which includes a RACH opportunity 405 RO#4 in the frequency domain and RACH opportunity repetitions 410 RO#5 and RO#6. The PRACH slot 425-b may be followed by a PUSCH slot 430-b, which includes a PUSCH opportunity 415 PO#4 and PUSCH opportunity repetitions 420 PO#5 and PO#6 in the frequency domain. In addition, the time domain mapping pattern 400-a may include a PRACH slot 425-c, which includes a RACH opportunity 405 RO#7 in the frequency domain and RACH opportunity repetitions 410 RO#8 and RO#9. The PRACH slot 425-c may be followed by a PUSCH slot 430-c, which includes a PUSCH opportunity 415 PO#7 in the frequency domain and PUSCH opportunity repetitions 420 PO#8 and PO#9. In some examples, the time domain mapping pattern 400-a may include a PRACH slot 425-d, which includes a RACH opportunity 405 RO#10 in the frequency domain and RACH opportunity repetitions 410 RO#11 and RO#12. The PRACH slot 425-d may be followed by a PUSCH slot 430-d, which includes a PUSCH opportunity 415 PO#10 in the frequency domain and PUSCH opportunity repetitions 420 PO#11 and PO#12. In this way, the PRACH slot 425 may include four MsgA preamble repetitions 435-a for two different preambles, and the PUSCH slot 430 may include four MsgA PUSCH repetitions 440-a for one PUSCH transmission. That is, the network entity 105-a may map the MsgA preamble repetitions 435-a for two different preambles to the same set of MsgA PUSCH repetitions 440-a. Additionally, UE 115-a may send interleaved preamble and PUSCH repetitions based on interleaved RACH and PUSCH opportunities.

[0120] With respect to the time domain mapping pattern 400-b, the network entity 105-a may configure a set of twelve RACH opportunities (also referred to herein as RO) across the time domain, the frequency domain, and the preamble-based domain in the PRACH slot 425. The twelve RACH opportunities may include two RACH opportunities 405 and ten RACH opportunity repetitions 410. In addition, the network entity 105-a may configure a set of twelve PUSCH opportunities (also referred to herein as PO) across the time domain, the frequency domain, and the DMRS-based domain in the PUSCH slot 430.

[0121] The time domain mapping pattern 400-b may include a PRACH slot 425-e that includes a RACH opportunity 405 RO#1 and RACH opportunity repetitions 410 RO#2 and RO#3. In addition, the PRACH slot 425-e may include RACH opportunity repetitions 410 RO#4, RO#5, and RO#6 in the time domain and frequency domain. In some examples, RO#1 may correspond to two different preambles. In addition, the time domain mapping pattern 400-b may specify a PUSCH slot 430-e that includes a PUSCH opportunity 415 PO#1 and PUSCH opportunity repetitions 420 PO#2 and PO#3. In addition, the PUSCH slot 430-e may include a PUSCH opportunity 415 PO#4 in the frequency domain and PUSCH opportunity repetitions 420 PO#5 and PO#6. PO#1 and PO#4 may correspond to a single DMRS or other uplink payload transmission. Since the PUSCH time slot 430 - e is continuous with the PRACH time slot 425 - e , the PRACH time slot 425 and the PUSCH time slot 430 (and the corresponding RACH opportunity 405 and PUSCH opportunity 415 ) of the time domain mapping pattern 400 - b are interlaced.

[0122] In addition, the time domain mapping pattern 400-b may include a PRACH time slot 425-f, which includes a RACH opportunity 405 RO#7 in the frequency domain and RACH opportunity repetitions 410 RO#8 and RO#9, and RACH opportunity repetitions 410 RO#10, RO#11, and RO#12 in the time domain and the frequency domain. After the PRACH time slot 425-f, the time domain mapping pattern 400-b may include a PUSCH time slot 430-f, which includes a PUSCH opportunity 415 PO#7 in the frequency domain and PUSCH opportunity repetitions 420 PO#8 and PO#9, and a PUSCH opportunity 415 PO#10 in the frequency domain and PUSCH opportunity repetitions 420 PO#11 and PO#12. Thus, the PRACH slot 425 may correspond to two MsgA preamble repetitions 435-b for two different preambles, and the PUSCH slot 430 may include four MsgA PUSCH repetitions 440-b for one PUSCH transmission. That is, the network entity 105-a may map the MsgA preamble repetitions 435-b for two different preambles to the same set of MsgA PUSCH repetitions 440-b, wherein the RACH opportunities 405 and the PUSCH opportunities 415 may correspond to different repetition levels (e.g., 2 and 4, respectively). In addition, the UE 115-a may transmit interleaved preambles and PUSCH repetitions based on interleaved RACH and PUSCH opportunities.

[0123] Figure 5An example of a time domain mapping pattern 500 that supports random access and uplink shared channel timing mapping patterns for a random access procedure according to one or more aspects of the present disclosure is illustrated. In some examples, the time domain mapping pattern 500 may implement aspects of the wireless communication systems 100 and 200, or may be implemented by aspects of the wireless communication systems 100 and 200. For example, the network entity 105-a may configure the time domain mapping pattern 500 to include one or more RACH opportunities 505 and one or more PUSCH opportunities 515 (e.g., uplink shared channel opportunities). In some cases, the time domain mapping pattern 500 may include repeated PUSCH opportunities 515 for corresponding PUSCH transmission repetitions, but may lack repeated RACH opportunities 505 for corresponding preamble repetitions.

[0124] In some examples, the network entity 105-a may configure the time domain mapping mode 500 such that the UE 115-a may send a single MsgA preamble based on a single associated RACH opportunity and may send multiple repetitions of MsgA PUSCH transmissions based on a set of associated PUSCH opportunities (e.g., the UE 115-a may suppress repeated MsgA preambles and may repeat MsgAPUSCH transmissions).

[0125] The network entity 105-a may configure RACH opportunities 505 (also referred to herein as RO) across the time domain, frequency domain, and preamble-based domain in the PRACH slot 525. For example, the PRACH slot 525 may include a RACH opportunity 505 RO#1 having two RACH opportunity repetitions 510 RO#2 and RO#3 in the frequency domain. The RACH opportunity 505 RO#1 may be associated with two different preambles (e.g., the RACH opportunity 505 RO#1 is shown twice, indicating two different preambles).

[0126] In addition, the network entity 105-a may configure a set of PUSCH opportunities 515 (also referred to herein as PO) across the time domain, frequency domain, and DMRS-based domain in the PUSCH time slot 530-a and the PUSCH time slot 530-b following the PRACH time slot 525. Each PUSCH time slot 530 may include a PUSCH opportunity 515 and two PUSCH opportunity repetitions 520. In the PUSCH time slot 530-a, the PUSCH opportunity 515 may include PO#1 having PUSCH opportunity repetitions 520 PO#2 and PO#3 in the frequency domain, and PO#4 having PUSCH opportunity repetitions 520 PO#5 and PO#6 in the frequency domain. In addition, the PUSCH slot 530-b may include a PUSCH opportunity 515 PO#7 with PUSCH opportunity repetitions 520 PO#8 and PO#9, and a PUSCH opportunity 515 PO#10 with PUSCH opportunity repetitions 520 PO#11 and PO#12. The UE 115-a may send a preamble 535 without repetition and with respect to two different preambles in a RACH opportunity 505RO#1 in the PRACH slot 525 before sending four PUSCH repetitions 540 in PUSCH opportunities 515PO#1, PO#4, PO#7, and PO#10 in the PUSCH slot 530-a and the PUSCH slot 530-b. That is, the UE 115-a may send a first preamble of one or more preambles in a first RACH opportunity 505 according to the time domain mapping mode, and send one or more uplink payloads (e.g., PUSCH transmissions) in one or more PUSCH opportunities 515.

[0127] Figure 6 An example of a time domain mapping pattern 600 that supports random access and uplink shared channel timing mapping patterns for a random access procedure according to one or more aspects of the present disclosure is illustrated. In some examples, the time domain mapping pattern 600 may implement aspects of the wireless communication systems 100 and 200, or may be implemented by aspects of the wireless communication systems 100 and 200. For example, the network entity 105-a may configure the time domain mapping pattern 600-a and the time domain mapping pattern 600-b to each include one or more RACH opportunities 605 and one or more PUSCH opportunities 615 (e.g., uplink shared channel opportunities). In some cases, the time domain mapping pattern 600 may include repeated RACH opportunities 605 for corresponding preamble repetitions, but may lack repeated PUSCH opportunities 615 for corresponding PUSCH transmission repetitions.

[0128] In some examples, the network entity 105-a may configure the time domain mapping pattern 600-a so that the UE 115-a may send multiple MsgA preamble repetitions and a single MsgA PUSCH transmission. In some examples, the UE 115-a may repeat the MsgA preamble and suppress repeating the MsgA PUSCH based on the following operations: first repeating the MsgA preamble based on a set of RACH opportunities 605 configured in the time domain mapping pattern 600-a, and then sending a single MsgA PUSCH based on a single PUSCH opportunity 615 configured in the time domain mapping pattern 600-a.

[0129] With respect to the time domain mapping pattern 600-a, the network entity 105-a may configure a set of twelve RACH opportunities (also referred to herein as RO) across the time domain, frequency domain, and preamble-based domain in the PRACH slot 625-a. The twelve RACH opportunities may include four RACH opportunities 605 and eight RACH opportunity repetitions 610. The PRACH slot 625-a may include RACH opportunities 605 RO#1, RO#4, RO#7, and RO#10 repeated in the time domain. In addition, RO#1 may correspond to two RACH opportunity repetitions 610 RO#2 and RO#3 in the frequency domain, RO#4 may correspond to two RACH opportunity repetitions 610 RO#5 and RO#6 in the frequency domain, RO#7 may correspond to two RACH opportunity repetitions 610 RO#8 and RO#9 in the frequency domain, and RO#10 may correspond to two RACH opportunity repetitions 610 RO#11 and RO#12 in the frequency domain. In addition, each RACH opportunity 605 may correspond to two different preambles (eg, two RACH opportunities 605 RO#1 are shown, indicating two different preambles). Thus, the PRACH slot 625-a may include four MsgA preamble repetitions 635-a for two different preambles.

[0130] In addition, the network entity 105-a may configure a set of PUSCH opportunities (also referred to herein as PO) across the time domain, frequency domain, and DMRS-based domain in the PUSCH time slot 630-a. The PUSCH opportunity may include a PUSCH opportunity 615 and two PUSCH opportunity repetitions 620. The PUSCH time slot 630-a may include a PUSCH opportunity 615 PO#1 with PUSCH opportunity repetitions 620 PO#2 and PO#3 in the frequency domain. The UE 115-a may send four preamble repetitions in RACH opportunities 605 RO#1, RO#4, RO#7, and RO#10 in the PRACH time slot 625-a before sending a PUSCH 640-a without repetition in the PUSCH time slot 630-a. That is, UE115-a may send one or more preamble codes in one or more RACH opportunities 605 RO#1, RO#4, RO#7 and RO#10 according to the time domain mapping pattern 600-a, and send a first uplink payload (e.g., PUSCH) in the PUSCH opportunity 615 PO#1.

[0131] Alternatively, the network entity 105-a may configure the time domain mapping pattern 600-b such that the UE 115-a may send a single MsgA preamble, followed by a single MsgA PUSCH, followed by one or more additional MsgA preamble repetitions. With respect to the time domain mapping pattern 600-b, the network entity 105-a may configure a set of twelve RACH opportunities (also referred to herein as RO) across the time domain, frequency domain, and preamble-based domain in the PRACH slot 625-b and the PRACH slot 625-c. In the PRACH slot 625-b, the RACH opportunity 605 RO#1 may correspond to two RACH opportunity repetitions 610 RO#2 and RO#3 in the frequency domain. After the PRACH slot 625-b, the network entity 105-a may configure a set of PUSCH opportunities (also referred to herein as PO) across the time domain, frequency domain, and DMRS-based domain in the PUSCH slot 630-b. The PUSCH slot 630 - b may include a PUSCH opportunity 615 PO# 1 with PUSCH opportunity repetitions 620 PO# 2 and PO# 3 in the frequency domain.

[0132] In addition, after the PUSCH time slot 630-b, the network entity 105-a may configure a set of RACH opportunities in the PRACH time slot 625-c. In the PRACH time slot 625-c, the RACH opportunity 605 RO#4 may correspond to two RACH opportunity repetitions 610 RO#5 and RO#6 in the frequency domain, the RACH opportunity 605 #7 may correspond to two RACH opportunity repetitions 610 RO#8 and RO#9 in the frequency domain, and the RACH opportunity 605 RO#10 may correspond to two RACH opportunity repetitions 610 RO#11 and RO#12 in the frequency domain. Thus, UE115-a may send one preamble repetition in RACH opportunity 605 RO#1 in PRACH slot 625-b, send PUSCH 640-b without repetition in PUSCH slot 630-b, and then send three additional preamble repetitions in RACH opportunities 605 RO#4, RO#7, and RO#10 in PRACH slot 625-c, such that PUSCH 640-b is between preamble repetitions 635-b.

[0133] Figure 7 An example of a time domain mapping pattern 700 that supports random access and uplink shared channel opportunity mapping patterns for a random access procedure according to one or more aspects of the present disclosure is illustrated. In some examples, the time domain mapping pattern 700 may implement aspects of the wireless communication systems 100 and 200, or may be implemented by aspects of the wireless communication systems 100 and 200. For example, the network entity 105-a may configure the time domain mapping pattern 700 to include one or more RACH opportunities and one or more PUSCH opportunities (e.g., uplink shared channel opportunities), wherein the network entity 105-a may multiplex the RACH opportunities and the PUSCH opportunities between different repetition levels.

[0134] In some examples, UE 115-a may identify one or more RACH opportunities and one or more PUSCH opportunities for joint MsgA preamble and MsgA PUSCH transmission based on a configuration indicated from network entity 105-a. For example, UE 115-a may receive control signaling indicating a time domain mapping pattern 700, which may include one or more RACH opportunities and one or more PUSCH opportunities for sending a random access message for a RACH procedure. That is, the random access message (e.g., MsgA) may be the first transmission of a 2-step RACH procedure that includes a preamble and a PUSCH (e.g., uplink payload) transmission. Network entity 105-a may send control signaling via RMSI or UE-specific RRC signaling.

[0135] In some cases, the network entity 105-a may configure different repetition levels on different sets of RACH opportunity-PUSCH opportunity groupings. For example, the RACH opportunity-PUSCH opportunity mappings associated with different repetition levels may be TDM, FDM, or CDM based on at least a preamble sequence, a DMRS port or sequence, or both. That is, the UE 115-a may receive control signaling indicating a time domain mapping pattern 700 between one or more RACH opportunities and one or more PUSCH opportunities, the time domain mapping pattern 700 being based on a set of joint preamble and uplink payload (PUSCH) transmission repetitions associated with one or more repetition levels 735, and wherein the set of joint preamble and uplink payload transmission repetitions is TDM, FDM, or CDM.

[0136] In some cases, for CDM RACH opportunity-PUSCH opportunity mapping, the network entity 105-a may use the same RACH opportunity-PUSCH opportunity pair for different repetition levels 735. That is, for a set of joint preamble and uplink payload transmission repetitions that are CDMed, the first joint payload and uplink payload transmission repetitions may be associated with one or more repetition levels 735. For example, the time domain mapping pattern 700 may include a repetition level 735-a, a repetition level 735-b, and a repetition level 735-c, wherein each repetition level 735 may correspond to a different mapped RACH opportunity-PUSCH opportunity pair. In some cases, the network entity 105-a may configure a given repetition level 735 and a RACH opportunity-PUSCH opportunity pair based on at least two RSRP thresholds (a first threshold Th1 and a second threshold Th2) predefined or configured by the network entity 105-a, and the UE 115-a may select to use the given repetition level and RACH opportunity-PUSCH opportunity pair.

[0137] Each repetition level 735 may be associated with a different repetition of a RACH opportunity (also referred to herein as RO) and a PUSCH opportunity (also referred to herein as PO), which may be sequentially TDMed. For example, the RACH opportunity and the PUSCH opportunity may include a first RO-PO pair 705 (e.g., RO#1 and PO#1), a second RO-PO pair 710 (e.g., RO#2 and PO#2), a third RO-PO pair 715 (e.g., RO#3 and PO#3), and a fourth RO-PO pair 720 (e.g., RO#4 and PO#4). For each repetition level 735, the UE 115-a may use the RACH opportunity in the PRACH time slot 725 to send one or more preamble codes, and use the PUSCH opportunity and corresponding DMRS resources in the PUSCH time slot 730 to send one or more uplink payload transmissions. For example, UE 115-a may send RACH opportunity RO#1 of the first RO-PO pair 705 in PRACH slot 725-a, and send PUSCH opportunity PO#1 in PUSCH slot 730-a. In addition, UE 115-a may send one or more RACH opportunities RO#2, RO#3, and RO#4 in PRACH slot 725-b, PRACH slot 725-c, and PRACH slot 725-d, respectively, and send one or more PUSCH opportunities PO#2, PO#3, and PO#4 in PUSCH slot 730-b, PUSCH slot 730-c, and PUSCH slot 730-d, respectively.

[0138] The UE may send different preambles and PUSCH repetitions according to the repetition level 735 based on comparing the measured RSRP with one or more RSRP thresholds. For example, if the measured RSRP is greater than a second threshold (e.g., RSRP>Th2), the UE 115-a may use the preamble #1-DMRS#1 with the first RO-PO pair 705 (e.g., RO#1-PO#1), the second RO-PO pair 710 (e.g., RO#2-PO#2), the third RO-PO pair 715 (e.g., RO#3-PO#3), or the fourth RO-PO pair 720 (e.g., RO#4-PO#4). That is, the UE 115-a may send two preambles in RO#1 and one DMRS resource in PO#1 based on the first RO-PO pair 705 associated with the repetition level 735-a. The second RO-PO pair 710, the third RO-PO pair 715, and the fourth RO-PO pair 720 may be repetitions of the first RO-PO pair 705, wherein the network entity 105-a may map repetitions regarding two different MsgA preambles to the same set of MsgA PUSCH repetitions (e.g., the two preambles associated with RO#2 correspond to the PUSCH associated with PO#2). In this way, the UE 115-a may send four preamble repetitions and four PUSCH repetitions in the corresponding RO-PO pair at repetition level 735-a (e.g., repetition level 4). The RACH timings and PUSCH timings associated with the RO-PO pair of repetition level 735-a may be as described herein with reference to Figure 3 and Figure 4 Intertwined as described.

[0139] If the measured RSRP is greater than a first threshold and less than a second threshold (e.g., Th1 < RSRP < Th2), then UE 115-a may use preamble #2-DMRS#2 together with the first RO-PO pair 705 (e.g., RO#1-PO#1), the second RO-PO pair 710 (e.g., RO#2-PO#2), the third RO-PO pair 715 (e.g., RO#3-PO#3), or the fourth RO-PO pair 720 (e.g., RO#4-PO#4), or use preamble #3-DMRS#3 together with the second RO-PO pair 710 or the third RO-PO pair 715. That is, UE 115-a may send two preambles in RO#1 and one DMRS resource in PO#1 based on the first RO-PO pair 705 associated with the repetition level 735-b, where the preambles and DMRS resources of the repetition level 735-b are different from those of the repetition level 735-a. The second RO-PO pair 710, the third RO-PO pair 715, and the fourth RO-PO pair 720 may be repetitions of the first RO-PO pair 705, where the network entity 105-a may map the repetitions of two different MsgA preambles to the same set of MsgA PUSCH repetitions (e.g., the two preambles associated with RO#2 correspond to the PUSCH associated with PO#2). In this way, UE 115-a may send two preamble repetitions and two PUSCH repetitions at the repetition level 735-b (e.g., repetition level 2) in the corresponding RO-PO pair. The RACH occasion and the PUSCH occasion associated with the RO-PO pair of the repetition level 735-b may be interleaved as described herein Figure 3 and Figure 4 as described.

[0140] In addition, the two RACH occasions and the PUSCH occasion repetitions associated with the repetition level 735-b may be linked to a given RAR window. For example, the first RO-PO pair 705 and the second RO-PO pair 710 may be two repetitions linked to the first RAR window (e.g., RAR window #1), the second RO-PO pair 710 and the third RO-PO pair 715 may be linked to the second RAR window (e.g., RAR window #2), and the third RO-PO pair 715 and the fourth RO-PO pair 720 may be linked to the third RAR window (e.g., RAR window #3). Using the repetition level 735-b, UE 115-a may select which set of two repetitions to use.

[0141] In some cases, the network entity 105-a may configure when the UE 115-a will receive a RAR message. The RAR message may be a MsgB (e.g., the second transmission of a two-step RACH process), and the MsgB RAR window may start based on the preamble and PUSCH repetitions as described herein. The network entity 105-a may configure or determine the start of the MsgB RAR window based on the last MsgA preamble or the last symbol of the MsgA PUSCH repetition among all MsgA preambles and PUSCH repetitions associated with the same repetition level. For example, the UE 115-a may select a first RO-PO pair 705 and a second RO-PO pair 710 for a repetition level 735-b, which may result in a RAR window #1 starting at the first symbol (e.g., symbol #1). Alternatively, UE 115-a may select the second RO-PO pair 710 and the third RO-PO pair 715, which may cause RAR window #2 to start at the second symbol (e.g., symbol #2), or UE 115-a may select the third RO-PO pair 715 and the fourth RO-PO pair 720, which may cause RAR window #3 to start at the third symbol (e.g., symbol #3), wherein the first symbol is earlier than the second symbol, and wherein the second symbol is earlier than the third symbol. In this way, UE 115-a may receive a RAR message from network entity 105-a in the RAR window, wherein the start of the RAR window is based on the last preamble of one or more preambles associated with repetition level 735 or the last symbol of the last uplink payload transmission of one or more uplink payload transmissions.

[0142] If the measured RSRP is less than a first threshold (e.g., RSRP < Th1), the UE 115-a may use the preamble #3-DMRS#3 together with the first RO-PO pair 705 (e.g., RO#1-PO#1), the second RO-PO pair 710 (e.g., RO#2-PO#2), the third RO-PO pair 715 (e.g., RO#3-PO#3), or the fourth RO-PO pair 720 (e.g., RO#4-PO#4). That is, the UE 115-a may send two preambles in RO#1 and one DMRS resource in PO#1 based on the first RO-PO pair 705 associated with the repetition level 735-c, where the preamble and DMRS resource of the repetition level 735-c are different from those of the repetition levels 735-a and 735-a. The second RO-PO pair 710, the third RO-PO pair 715, and the fourth RO-PO pair 720 may be repetitions of the first RO-PO pair 705, where the network entity 105-a may map the repetition of two different MsgA preambles to the same set of MsgA PUSCH repetitions (e.g., the two preambles associated with RO#2 correspond to the PUSCH associated with PO#2). In this way, the UE 115-a may send the preamble and PUSCH without repetition in the corresponding RO-PO pair at the repetition level 735-c (e.g., repetition level 1). The RACH occasion and PUSCH occasion associated with the RO-PO pair of the repetition level 735-c may be interleaved as described herein with reference to Figure 3 and Figure 4 as described. In this way, the network entity 105-a may configure a specific RO-PO pair and the corresponding preamble and DMRS resource for the UE 115-a according to how many repetitions the UE 115-a may optionally send.

[0143] Figure 8 Illustrates an example of a time-domain mapping pattern 800 that supports a random access and uplink shared channel occasion mapping pattern for a random access procedure according to one or more aspects of the present disclosure. In some examples, the time-domain mapping pattern 800 may implement aspects of the wireless communication systems 100 and 200, or may be implemented by aspects of the wireless communication systems 100 and 200. For example, the network entity 105-a may configure the time-domain mapping pattern 800-a or the time-domain mapping pattern 800-b to include one or more RACH occasions and one or more PUSCH occasions (e.g., uplink shared channel occasions), where the network entity 105-a may multiplex the RACH occasions and PUSCH occasions between different repetition levels.

[0144] As described herein, UE 115-a may identify one or more RACH opportunities and one or more PUSCH opportunities for joint MsgA preamble and MsgA PUSCH transmission based on a configuration indicated from network entity 105-a. For example, UE 115-a may receive control signaling indicating a time domain mapping pattern 800, which may include one or more RACH opportunities and one or more PUSCH opportunities for sending a random access message for a RACH procedure. That is, the random access message (e.g., MsgA) may be the first transmission of a 2-step RACH procedure that includes a preamble and a PUSCH (e.g., uplink payload) transmission. Network entity 105-a may send control signaling via RMSI or UE-specific RRC signaling.

[0145] In some cases, the network entity 105-a may configure different repetition levels on different sets of RACH opportunity-PUSCH opportunity groupings. For example, the RACH opportunity-PUSCH opportunity mappings associated with different repetition levels may be TDM, FDM, or CDM based on at least the preamble sequence, the DMRS port or sequence, or both. In some cases, for CDM RACH opportunity-PUSCH opportunity mappings, the network entity 105-a may use the same RACH opportunity-PUSCH opportunity pair for different repetition levels 835. That is, for a set of joint preamble and uplink payload transmission repetitions that are CDM, a first joint payload and uplink payload transmission repetition may be associated with one or more repetition levels 835.

[0146] Time domain mapping pattern 800-a and time domain mapping pattern 800-b may be examples of RACH timing and PUSCH timing mapping based only on preamble repetition or only on PUSCH (e.g., uplink payload transmission) repetition. Time domain mapping pattern 800-a may include repetition level 835-a, repetition level 835-b, and repetition level 835-c, wherein each repetition level 835 may correspond to a different mapped RACH timing-PUSCH timing pair. In some cases, network entity 105-a may configure a given repetition level 835 and RACH timing-PUSCH timing pair based on at least two RSRP thresholds (a first threshold Th1 and a second threshold Th2) predefined or configured (e.g., signaled) by network entity 105-a, and UE 115-a may select to use the given repetition level and RACH timing-PUSCH timing pair.

[0147] Each repetition level 835 may be associated with a different repetition of a RACH opportunity (also referred to herein as RO) and a PUSCH opportunity (also referred to herein as PO), which may be sequentially TDMed. For example, the RACH opportunity and the PUSCH opportunity may include a first RO-PO pair 805 (e.g., RO#1 and PO#1), a second RO-PO pair 810 (e.g., RO#2 and PO#2), a third RO-PO pair 815 (e.g., RO#3 and PO#3), and a fourth RO-PO pair 820 (e.g., RO#4 and PO#4). For each repetition level 835, the UE 115-a may use the RACH opportunity in the PRACH time slot 825 to send one or more preamble codes, and in some cases, use the PUSCH opportunity and corresponding DMRS resources in the PUSCH time slot 830 to send one or more uplink payload transmissions. In the example of the time domain mapping pattern 800-a, the repetition level 835 may be based only on the preamble code repetition (and a single PUSCH transmission). For example, UE 115-a may send RACH opportunity RO#1 of the first RO-PO pair 805 in PRACH slot 825-a, and send PUSCH opportunity PO#1 in PUSCH slot 830-a. In addition, UE 115-a may send one or more RACH opportunities RO#2, RO#3, and RO#4 in PRACH slot 825-b, PRACH slot 825-c, and PRACH slot 825-d, respectively. That is, UE 115-a may send preamble code repetition and PUSCH without repetition based on time domain mapping pattern 800-a including RACH opportunity repetition and PUSCH opportunity without repetition.

[0148] The UE may send different preambles and PUSCH repetitions according to the repetition level 835 based on comparing the measured RSRP with one or more RSRP thresholds. For example, if the measured RSRP is greater than the second threshold (e.g., RSRP>Th2), the UE 115-a may use the preamble #1-DMRS#1 with the first RO-PO pair 805 (e.g., RO#1-PO#1). That is, the UE 115-a may send two preambles in RO#1 and one DMRS resource in PO#1 based on the first RO-PO pair 805 associated with the repetition level 835-a. The network entity 105-a may map the repetitions of two different MsgA preambles to the same set of MsgA PUSCH repetitions (e.g., the two preambles associated with RO#1 correspond to the PUSCH associated with PO#1). In this way, the UE 115-a may send one preamble and one PUSCH repetition in the corresponding RO-PO pair at the repetition level 835-a (e.g., repetition level 1).

[0149] If the measured RSRP is greater than a first threshold and less than a second threshold (e.g., Th1 < RSRP < Th2), then UE 115-a may use the preamble #2-DMRS #2 together with the RACH opportunity of the first RO-PO pair 805 (e.g., RO#1-PO#1) and the second RO-PO pair 810 (e.g., RO#2). That is, UE 115-a may transmit two preambles in RO#1 and one DMRS resource in PO#1 based on the first RO-PO pair 805 associated with the repetition level 835-b, where the preamble and DMRS resource of the repetition level 835-b are different from those of the repetition level 835-a. The second RO-PO pair 810 may be a repetition of the first RO-PO pair 805, where the network entity 105-a may map the repetition of two different MsgA preambles to the same set of MsgA PUSCH repetitions (e.g., the two preambles associated with RO#1 correspond to the PUSCH associated with PO#1). In this way, UE 115-a may transmit two preamble repetitions and one PUSCH repetition at the repetition level 835-b (e.g., repetition level 2) in the corresponding RO-PO pair.

[0150] If the measured RSRP is less than a first threshold (e.g., RSRP < Th1), the UE 115-a may use the preamble #3-DMRS#3 together with the first RO-PO pair 805 (e.g., RO#1-PO#1), the second RO-PO pair 810 (e.g., RO#2-PO#2), the third RO-PO pair 815 (e.g., RO#3-PO#3), or the fourth RO-PO pair 820 (e.g., RO#4-PO#4). That is, the UE 115-a may transmit two preambles in RO#1 and one DMRS resource in PO#1 based on the first RO-PO pair 805 associated with the repetition level 835-c, where the preambles and DMRS resources of the repetition level 835-c are different from those of the repetition levels 835-a and 835-b. The second RO-PO pair 810, the third RO-PO pair 815, and the fourth RO-PO pair 820 may be repetitions of the first RO-PO pair 805, where the network entity 105-a may map the repetitions of two different MsgA preambles to the same set of MsgA PUSCH repetitions (e.g., the two preambles associated with RO#1 correspond to the PUSCH associated with PO#1), and the UE 115-a may only repeat the RACH opportunities of each RO-PO pair. In this way, the UE 115-a may transmit four preamble repetitions and a non-repeated PUSCH in the corresponding RO-PO pair at the repetition level 835-c (e.g., repetition level 4). Therefore, the network entity 105-a may configure a specific RO-PO pair and the corresponding preambles and DMRS resources for the UE 115-a according to how many preambles and PUSCH repetitions the UE 115-a may choose to transmit.

[0151] In addition, each repetition level 835 may be associated with a RAR window. For example, a single RACH opportunity associated with the repetition level 835-a may be linked to the RAR window #1, two RACH opportunity repetitions associated with the repetition level 835-b may be linked to the RAR window #2, and four RACH opportunity repetitions associated with the repetition level 835-c may be linked to the RAR window #3.

[0152] Alternatively, in the example of time domain mapping pattern 800-b, the repetition level 835 may be based only on PUSCH repetitions (and a single preamble transmission). For example, UE 115-a may send RACH opportunity RO#1 of the first RO-PO pair 805 in PRACH slot 825-e, and send PUSCH opportunity PO#1 in PUSCH slot 830-b. In addition, UE 115-a may send one or more PUSCH opportunities PO#2, PO#3, and PO#4 in PUSCH slot 830-c, PUSCH slot 830-d, and PUSCH slot 830-e, respectively. That is, UE 115-a may send a preamble without repetition and multiple PUSCH repetitions based on time domain mapping mode 800-b that includes PUSCH opportunity repetitions and RACH opportunities without repetitions.

[0153] The UE may send different preambles and PUSCH repetitions according to the repetition level 835 based on comparing the measured RSRP with one or more RSRP thresholds. For example, if the measured RSRP is greater than the second threshold (e.g., RSRP>Th2), the UE 115-a may use the preamble #1-DMRS#1 with the first RO-PO pair 805 (e.g., RO#1-PO#1). That is, the UE 115-a may send two preambles in RO#1 and one DMRS resource in PO#1 based on the first RO-PO pair 805 associated with the repetition level 835-d. The network entity 105-a may map the repetitions of two different MsgA preambles to the same set of MsgA PUSCH repetitions (e.g., the two preambles associated with RO#1 correspond to the PUSCH associated with PO#1). In this way, the UE 115-a may send one preamble and one PUSCH repetition in the corresponding RO-PO pair at the repetition level 835-d (e.g., repetition level 1).

[0154] If the measured RSRP is greater than a first threshold and less than a second threshold (e.g., Th1 < RSRP < Th2), the UE 115-a may use the preamble #2-DMRS #2 together with the PUSCH occasions of the first RO-PO pair 805 (e.g., RO#1-PO#1) and the second RO-PO pair 810 (e.g., PO#2). That is, the UE 115-a may transmit two preambles in RO#1 and one DMRS resource in PO#1 based on the first RO-PO pair 805 associated with the repetition level 835-e, where the preamble and DMRS resource of the repetition level 835-e are different from those of the repetition level 835-d. The second RO-PO pair 810 may be a repetition of the first RO-PO pair 805, where the network entity 105-a may map the repetitions of two different MsgA preambles to the same set of MsgA PUSCH repetitions (e.g., the two preambles associated with RO#1 correspond to the PUSCH associated with PO#1). In this way, the UE 115-a may transmit two PUSCH repetitions and one preamble repetition at the repetition level 835-e (e.g., repetition level 2) in the corresponding RO-PO pair.

[0155] If the measured RSRP is less than a first threshold (e.g., RSRP < Th1), the UE 115-a may use the preamble #3-DMRS #3 together with the first RO-PO pair 805 (e.g., RO#1-PO#1), the second RO-PO pair 810 (e.g., RO#2-PO#2), the third RO-PO pair 815 (e.g., RO#3-PO#3), or the fourth RO-PO pair 820 (e.g., RO#4-PO#4). That is, the UE 115-a may send two preambles in RO#1 and one DMRS resource in PO#1 based on the first RO-PO pair 805 associated with the repetition level 835-f, where the preamble and DMRS resource of the repetition level 835-f are different from those of the repetition levels 835-d and 835-e. The second RO-PO pair 810, the third RO-PO pair 815, and the fourth RO-PO pair 820 may be repetitions of the first RO-PO pair 805, where the network entity 105-a may map the repetitions of two different MsgA preambles to the same set of MsgA PUSCH repetitions (e.g., the two preambles associated with RO#1 correspond to the PUSCH associated with PO#1), and the UE 115-a may only repeat the RACH occasions of each RO-PO pair. In this way, the UE 115-a may send four PUSCH repetitions and a non-repeated preamble in the corresponding RO-PO pair at the repetition level 835-f (e.g., repetition level 4). Therefore, the network entity 105-a may configure a specific RO-PO pair and the corresponding preamble and DMRS resources for the UE 115-a according to how many preambles and PUSCH repetitions the UE 115-a can optionally send.

[0156] In addition, each repetition level 835 may be associated with a RAR window. For example, a single RACH occasion associated with the repetition level 835-d may be linked to the RAR window #1, two RACH occasion repetitions associated with the repetition level 835-e may be linked to the RAR window #2, and four RACH occasion repetitions associated with the repetition level 835-f may be linked to the RAR window #3.

[0157] Fig. 9An example of a time domain mapping pattern 900 that supports random access and uplink shared channel timing mapping patterns for a random access procedure according to one or more aspects of the present disclosure is illustrated. In some examples, the time domain mapping pattern 900 may implement aspects of the wireless communication systems 100 and 200, or may be implemented by aspects of the wireless communication systems 100 and 200. For example, the network entity 105-a may configure the time domain mapping pattern 900-a or the time domain mapping pattern 900-b to include one or more RACH opportunities and one or more PUSCH opportunities (e.g., uplink shared channel opportunities), wherein the network entity 105-a may multiplex the RACH opportunities and the PUSCH opportunities between different SSBs.

[0158] As referenced in this article Figure 7 and Figure 8 As described, the network entity 105-a may multiplex different RACH opportunities and PUSCH opportunity pairs for different repetition levels. Additionally or alternatively, the network entity 105-a may multiplex RACH opportunities and PUSCH opportunity pairs for different SSBs. In some examples, for a given repetition level, different joint MsgA preambles and MsgAPUSCH repetitions may be associated with the same SSB or different SSBs. In some cases, the network entity 105-a may send a set of joint preamble and uplink payload transmission (e.g., PUSCH) repetitions, where the set of joint preamble and uplink payload transmission repetitions is associated with one or more SSBs of a given repetition level.

[0159] The network entity 105-a may configure the time domain mapping pattern 900-a based on different joint MsgA preamble codes and MsgA PUSCH repetitions being associated with the same SSB. For a given repetition level, the UE 115-a may select a RACH opportunity-PUSCH opportunity mapping based on identifying a single strongest SSB and selecting a RACH opportunity-PUSCH opportunity mapping from one or more RO-PO pairs associated with the SSB. For example, the UE 115-a may identify the strongest SSB RSRP, identify a repetition level (e.g., 2), identify a single strongest SSB (e.g., SSB#1), and randomly select from one of the first RO-PO pair 905 (e.g., RO#1-PO#1), the second RO-PO pair 910 (e.g., RO#2-PO#2), or the third RO-PO pair 915 (e.g., RO#3-PO#3), or the fourth RO-PO pair 920 (e.g., RO#4-PO#4).

[0160] The network entity 105-a may configure the time domain mapping pattern 900-b based on different joint MsgA preambles and MsgA PUSCH repetitions being associated with different SSBs. For a given repetition level, the UE 115-a may select a RACH opportunity-PUSCH opportunity mapping based on one or more SSBs with respect to one or more highest identified (or measured) RSRPs. That is, the UE 115-a may select a first joint preamble and uplink payload transmission repetition in a set of joint preamble and uplink payload transmission repetitions based on the SSB associated with the first joint preamble and uplink payload transmission repetition corresponding to the highest identified RSRP. In some examples, a certain number of SSBs associated with the highest identified RSRP is associated with the repetition level.

[0161] Each repetition level may be associated with a different repetition of a RACH opportunity (also referred to herein as RO) and a PUSCH opportunity (also referred to herein as PO), which may be sequentially TDMed. For example, the RACH opportunity and the PUSCH opportunity may include a first RO-PO pair 905 (e.g., RO#1 and PO#1), a second RO-PO pair 910 (e.g., RO#2 and PO#2), a third RO-PO pair 915 (e.g., RO#3 and PO#3), and a fourth RO-PO pair 920 (e.g., RO#4 and PO#4). For each repetition level, the UE 115-a may use a RACH opportunity in a PRACH time slot to send one or more preamble codes, and use a PUSCH opportunity and corresponding DMRS resources in a PUSCH time slot to send one or more uplink payload transmissions. In addition, each RO-PO pair may be associated with an SSB. For example, the first RO-PO pair 905 may be associated with SSB #1, the second RO-PO pair 910 may be associated with SSB #2, the third RO-PO pair 915 may be associated with SSB #3, and the fourth RO-PO pair 920 may be associated with SSB #4.

[0162] One or more UEs 115 may identify one or more RACH occasion - PUSCH occasion repetitions (e.g., MsgA repetitions). For example, a first UE (e.g., UE #1), a second UE (e.g., UE #2), and a third UE (e.g., UE #3) may each identify two repetitions of MsgA. In some examples, each UE 115 may identify the strongest measured SSB RSRP, identify the repetition level, and then identify the corresponding strongest SSBs. For example, based on a repetition level of 2, the first UE may identify that the two strongest SSBs are SSB #1 and SSB #2, and thus the first UE may select a first RO - PO pair 905 (e.g., RO #1 - PO #1) and a second RO - PO pair 910 (e.g., RO #2 - PO #2) to transmit two MsgA repetitions using two preambles and one DMRS (e.g., preamble #1 / #2 and DMRS #1). Additionally, the second UE may identify that the two strongest SSBs are SSB #2 and SSB #3, and thus the first UE may select the second RO - PO pair 910 (e.g., RO #2 - PO #2) and a third RO - PO pair 915 (e.g., RO #3 - PO #3) to transmit two MsgA repetitions using two preambles and one DMRS (e.g., preamble #3 / #4 and DMRS #2). In some examples, the third UE may identify that the two strongest SSBs are SSB #3 and SSB #4, and thus the first UE may select the third RO - PO pair 915 (e.g., RO #3 - PO #3) and a fourth RO - PO pair 920 (e.g., RO #4 - PO #4) to transmit two MsgA repetitions using two preambles and one DMRS (e.g., preamble #1 / #2 and DMRS #1).

[0163] In some examples, the number of different strongest SSBs identified may be associated with the repetition level (or the RSRP level of the strongest SSBs). For example, a first UE (which measures the RSRP of the strongest SSB > a second threshold Th2) may identify only a single strongest SSB and its associated RACH occasion - PUSCH occasion mapping (including the preambles and DMRS to be used). Additionally, a second UE (which measures the RSRP of the strongest SSB: a first RSRP threshold Th1 < RSRP < Th2) may identify only two strongest SSBs and their associated RACH occasion - PUSCH occasion mapping (including the preambles and DMRS to be used). In some cases, a third UE (which measures the RSRP of the strongest SSB < Th1) may identify only four strongest SSBs and their associated RACH occasion - PUSCH occasion mapping (including the preambles and DMRS to be used).

[0164] In some cases, UE 115-a may send a preamble and PUSCH repetitions using time domain mapping pattern 900-b based on one or more SSBs. In some examples, UE 115-a may repeat only the preamble. In this way, the first UE may identify that the two strongest SSBs are SSB#1 and SSB#2, and therefore the first UE may select the RACH timing of the first RO-PO pair 905 (e.g., RO#1-PO#1) and the second RO-PO pair 910 (e.g., RO#2) for sending two MsgA repetitions using two preambles and one DMRS (e.g., preamble #1 / #2 and DMRS#1). In addition, the second UE may identify that the two strongest SSBs are SSB#2 and SSB#3, and thus the first UE may select the RACH timing of the second RO-PO pair 910 (e.g., RO#2-PO#2) and the third RO-PO pair 915 (e.g., RO#3) for sending two MsgA repetitions using two preambles and one DMRS (e.g., preamble #3 / #4 and DMRS#2). In some examples, the third UE may identify that the two strongest SSBs are SSB#3 and SSB#4, and thus the first UE may select the RACH timing of the third RO-PO pair 915 (e.g., RO#3-PO#3) and the fourth RO-PO pair 920 (e.g., RO#4) for sending two MsgA repetitions using two preambles and one DMRS (e.g., preamble #1 / #2 and DMRS#1).

[0165] Alternatively, UE 115-a may only repeat the PUSCH transmission. In this way, the first UE may identify that the two strongest SSBs are SSB#1 and SSB#2, and therefore the first UE may select the PUSCH timing of the first RO-PO pair 905 (e.g., RO#1-PO#1) and the second RO-PO pair 910 (e.g., PO#2) for sending two MsgA repetitions using two preambles and one DMRS (e.g., preamble #1 / #2 and DMRS#1). In addition, the second UE may identify that the two strongest SSBs are SSB#2 and SSB#3, and therefore the first UE may select the PUSCH timing of the second RO-PO pair 910 (e.g., RO#2-PO#2) and the third RO-PO pair 915 (e.g., PO#3) for sending two MsgA repetitions using two preambles and one DMRS (e.g., preamble #3 / #4 and DMRS#2). In some examples, the third UE may identify that the two strongest SSBs are SSB#3 and SSB#4, and therefore the first UE may select the PUSCH timing of the third RO-PO pair 915 (e.g., RO#3-PO#3) and the fourth RO-PO pair 920 (e.g., PO#4) for sending two MsgA repetitions using two preambles and one DMRS (e.g., preamble #1 / #2 and DMRS#1).

[0166] Fig.10 An example of a process flow 1000 for supporting random access and uplink shared channel timing mapping patterns for a random access procedure according to one or more aspects of the present disclosure is illustrated. The process flow 1000 may implement aspects of the wireless communication systems 100 and 200, or may be implemented by aspects of the wireless communication systems 100 and 200. For example, the process flow 1000 may illustrate operations between a UE 115-b and a network entity 105-b (which may be examples of corresponding devices described herein). In the following description of the process flow 1000, the operations between the UE 115-b and the network entity 105-b may be sent in an order different from the example order shown, or the operations performed by the UE 115-b and the network entity 105-b may be performed in a different order or at a different time. Some operations may also be omitted from the process flow 1000, and other operations may be added to the process flow 1000.

[0167] At 1005, UE 115-b may receive control signaling from network entity 105-b indicating a time domain mapping pattern between one or more RACH opportunities and one or more uplink shared channel (e.g., PUSCH) opportunities for sending RACH messages for a RACH procedure. In some examples, network entity 105-a may configure the time domain mapping pattern based on repeating RACH opportunities and then continuously repeating uplink shared channel opportunities or based on interleaving RACH and uplink shared channel opportunities. In some examples, the time domain mapping pattern may be based on one or more repetition levels associated with joint preamble and uplink payload transmission repetitions, SSBs, or both.

[0168] At 1010, UE 115-b may send one or more preambles of a RACH message of a RACH procedure to network entity 105-b in one or more RACH occasions according to a time domain mapping pattern. For example, UE 115-a may send multiple preamble (e.g., MsgA preamble) repetitions based on a time domain mapping pattern including multiple RACH occasion repetitions.

[0169] At 1015, UE 115-b may transmit one or more uplink payloads of a RACH message for a RACH procedure to network entity 105-b according to a time domain mapping pattern and in one or more uplink shared channel opportunities. For example, UE 115-a may transmit multiple PUSCH (e.g., MsgA PUSCH) repetitions based on a time domain mapping pattern that includes multiple uplink shared channel opportunity repetitions.

[0170] At 1020, UE 115-b may receive a RAR message from network entity 105-b in a RAR window, where a start of the RAR window is based on a last preamble of one or more preambles associated with a first repetition level or a last symbol of a last uplink payload transmission of one or more uplink payload transmissions. For example, network entity 105-b may send the RAR message based on when UE 115-a sends a preamble and a PUSCH transmission according to a time domain mapping pattern.

[0171] Fig.11 A block diagram 1100 of a device 1105 supporting random access and uplink shared channel opportunity mapping patterns for a random access procedure according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of a UE 115 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0172] The receiver 1110 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to random access and uplink shared channel opportunity mapping patterns for random access procedures), user data, control information, or any combination thereof. The information may be communicated to other components of the device 1105. The receiver 1110 may utilize a single antenna or a collection of multiple antennas.

[0173] The transmitter 1115 may provide means for transmitting signals generated by other components of the device 1105. For example, the transmitter 1115 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to random access and uplink shared channel opportunity mapping patterns for random access procedures), user data, control information, or any combination thereof. In some examples, the transmitter 1115 may be co-located with the receiver 1110 in a transceiver module. The transmitter 1115 may utilize a single antenna or a collection of multiple antennas.

[0174] The communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of random access and uplink shared channel opportunity mapping patterns for random access procedures as described herein. For example, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may support methods for performing one or more of the functions described herein.

[0175] In some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, 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 components, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. 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).

[0176] Additionally or alternatively, in some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, 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 functions of the communication manager 1120, the receiver 1110, the transmitter 1115, 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 functions 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 1120 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated in conjunction with receiver 1110, transmitter 1115, 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 1120 may support wireless communications at the UE. For example, the communication manager 1120 may be configured to or otherwise support a component for receiving control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure. The communication manager 1120 may be configured to or otherwise support a component for sending one or more preambles of a random access message of a random access procedure in one or more random access opportunities according to the time domain mapping pattern. The communication manager 1120 may be configured to or otherwise support a component for sending one or more uplink payloads of a random access message of a random access procedure in one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0179] By including or configuring a communication manager 1120 according to examples as described herein, a device 1105 (e.g., a processor controlling or otherwise coupled with a receiver 1110, a transmitter 1115, a communication manager 1120, or a combination thereof) may support techniques for including time domain behavior in a RACH opportunity-to-PUSCH opportunity mapping pattern, which may increase signaling throughput, reduce latency, and improve signaling efficiency.

[0180] Fig.12A block diagram 1200 of a device 1205 supporting random access and uplink shared channel opportunity mapping patterns for a random access procedure according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of aspects of the device 1105 or UE 115 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).

[0181] The receiver 1210 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to random access and uplink shared channel opportunity mapping patterns for random access procedures), user data, control information, or any combination thereof. The information may be communicated to other components of the device 1205. The receiver 1210 may utilize a single antenna or a collection of multiple antennas.

[0182] The transmitter 1215 may provide means for transmitting signals generated by other components of the device 1205. For example, the transmitter 1215 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to random access and uplink shared channel opportunity mapping patterns for random access procedures), user data, control information, or any combination thereof. In some examples, the transmitter 1215 may be co-located with the receiver 1210 in a transceiver module. The transmitter 1215 may utilize a single antenna or a collection of multiple antennas.

[0183] The device 1205 or its various components may be examples of components for performing various aspects of the random access and uplink shared channel opportunity mapping patterns for the random access process as described herein. For example, the communication manager 1220 may include a mapping pattern component 1225, a preamble component 1230, an uplink payload component 1235, or any combination thereof. The communication manager 1220 may be an example of various aspects of the communication manager 1120 as described herein. In some examples, the communication manager 1220 or its various components may be configured to use or otherwise cooperate with the receiver 1210, the transmitter 1215, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1220 may receive information from the receiver 1210, transmit information to the transmitter 1215, or be integrated with the receiver 1210, the transmitter 1215, 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 1220 may support wireless communications at the UE. The mapping pattern component 1225 may be configured to or otherwise support components for receiving control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure. The preamble component 1230 may be configured to or otherwise support components for sending one or more preambles of a random access message of a random access procedure in one or more random access opportunities according to the time domain mapping pattern. The uplink payload component 1235 may be configured to or otherwise support components for sending one or more uplink payloads of a random access message of a random access procedure in one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0185] Fig.13 A block diagram 1300 of a communication manager 1320 supporting random access and uplink shared channel timing mapping patterns for random access procedures according to one or more aspects of the present disclosure is shown. The communication manager 1320 may be an example of aspects of the communication manager 1120, the communication manager 1220, or both as described herein. The communication manager 1320 or its various components may be examples of components for performing various aspects of the random access and uplink shared channel timing mapping patterns for random access procedures as described herein. For example, the communication manager 1320 may include a mapping pattern component 1325, a preamble component 1330, an uplink payload component 1335, a continuous RACH component 1340, an interleaving component 1345, a transmission component 1350, a repetition component 1355, a repetition level component 1360, a RAR message component 1365, an SSB component 1370, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0186] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at the UE. The mapping pattern component 1325 may be configured to or otherwise support components for receiving control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure. The preamble component 1330 may be configured to or otherwise support components for sending one or more preambles of a random access message of a random access procedure in one or more random access opportunities according to the time domain mapping pattern. The uplink payload component 1335 may be configured to or otherwise support components for sending one or more uplink payloads of a random access message of a random access procedure in one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0187] In some examples, the continuous RACH component 1340 may be configured to or otherwise support components for sending one or more preamble codes in one or more continuous random access opportunities and sending one or more uplink payload transmissions in one or more continuous uplink shared channel opportunities according to a time domain mapping pattern, wherein the one or more continuous uplink shared channel opportunities are after the one or more continuous random access opportunities.

[0188] In some examples, interleaving component 1345 may be configured or otherwise support means for receiving control signaling indicating a time domain mapping pattern, wherein the time domain mapping pattern indicates that one or more random access opportunities and one or more uplink shared channel opportunities are interleaved in the time domain. In some examples, transmitting component 1350 may be configured or otherwise support means for transmitting one or more preambles and one or more uplink payload transmissions, wherein the one or more preambles and the one or more uplink payload transmissions are interleaved based on the time domain mapping pattern.

[0189] In some examples, to support sending one or more preambles, the preamble component 1330 may be configured as or otherwise support components for sending one or more preambles in one or more consecutive random access opportunities according to a time domain mapping pattern, where the one or more consecutive random access opportunities are TDMed within one or more random access time slots.

[0190] In some examples, to support sending one or more uplink payload transmissions, the preamble component 1330 may be configured as or otherwise support components for sending one or more uplink payload transmissions in one or more consecutive uplink shared channel opportunities that are TDMed according to a time domain mapping pattern, wherein the one or more uplink payload transmissions are associated with a subset of one or more preamble codes.

[0191] In some examples, the repetition component 1355 may be configured as or otherwise support components for sending one or more preambles in one or more random access opportunities and sending a first uplink payload transmission in a first uplink shared channel opportunity in one or more uplink shared channel opportunities according to a time domain mapping pattern.

[0192] In some examples, the repetition component 1355 may be configured to or otherwise support components for sending a first preamble of one or more preambles in a first random access opportunity in one or more random access opportunities and sending one or more uplink payload transmissions in one or more uplink shared channel opportunities according to a time domain mapping pattern.

[0193] In some examples, repetition level component 1360 may be configured as or otherwise support components for receiving control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities, the time domain mapping pattern being based on a set of joint preamble and uplink payload transmission repetitions associated with one or more repetition levels, wherein the set of joint preamble and uplink payload transmission repetitions is TDM, FDM, or CDM.

[0194] In some examples, for a set of joint preamble and uplink payload transmission repetitions that are CDMed, a first joint payload and uplink payload transmission repetition is associated with one or more repetition levels.

[0195] In some examples, the RAR message component 1365 may be configured as or otherwise support components for receiving a RAR message in a RAR window, where the start of the RAR window is based on a last preamble of one or more preambles associated with a first repetition level or a last symbol of a last uplink payload transmission of one or more uplink payload transmissions.

[0196] In some examples, SSB component 1370 may be configured or otherwise support components for sending a set of joint preamble and uplink payload transmission repetitions, where the set of joint preamble and uplink payload transmission repetitions is associated with one or more SSBs of a given repetition level.

[0197] In some examples, SSB component 1370 can be configured or otherwise support means for selecting a first joint preamble and uplink payload transmission repetition in a set of joint preamble and uplink payload transmission repetitions based on the SSB associated with the first joint preamble and uplink payload transmission repetition corresponding to the highest identified RSRP. In some examples, the number of SSBs associated with the highest identified RSRP is associated with the repetition level.

[0198] Fig.14 A diagram of a system 1400 including a device 1405 supporting random access and uplink shared channel opportunity mapping patterns for a random access procedure according to one or more aspects of the present disclosure is shown. The device 1405 may be an example of a device 1105, a device 1205, or a UE 115 as described herein, or include components thereof. The device 1405 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1405 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1420, an input / output (I / O) controller 1410, a transceiver 1415, an antenna 1425, a memory 1430, a code 1435, and a processor 1440. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1445).

[0199] I / O controller 1410 can manage input signals and output signals of device 1405. I / O controller 1410 can also manage peripheral devices that are not integrated into device 1405. In some cases, I / O controller 1410 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1410 can utilize an operating system, such as iOS. ® ANDROID ® , MS-DOS ® 、MS-WINDOWS ® , OS / 2 ® ,UNIX ® 、LINUX ® or another known operating system. Additionally or alternatively, I / O controller 1410 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1410 may be implemented as part of a processor, such as processor 1440. In some cases, a user may interact with device 1405 via I / O controller 1410 or via hardware components controlled by I / O controller 1410.

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

[0201] Memory 1430 may include random access memory (RAM) and read-only memory (ROM). Memory 1430 may store computer-readable, computer-executable code 1435 including instructions that, when executed by processor 1440, cause device 1405 to perform various functions described herein. Code 1435 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, code 1435 may not be directly executable by processor 1440, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1430 may 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.

[0202] Processor 1440 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, processor 1440 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1440. Processor 1440 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1430) to enable device 1405 to perform various functions (e.g., functions or tasks supporting random access and uplink shared channel opportunity mapping modes for random access procedures). For example, device 1405 or a component of device 1405 may include processor 1440 and memory 1430 coupled to or coupled to processor 1440, and processor 1440 and memory 1430 are configured to perform various functions described herein.

[0203] According to examples as disclosed herein, the communication manager 1420 may support wireless communications at the UE. For example, the communication manager 1420 may be configured to or otherwise support a component for receiving control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure. The communication manager 1420 may be configured to or otherwise support a component for sending one or more preambles of a random access message of a random access procedure in one or more random access opportunities according to the time domain mapping pattern. The communication manager 1420 may be configured to or otherwise support a component for sending one or more uplink payloads of a random access message of a random access procedure in one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0204] By including or configuring the communication manager 1420 according to examples as described herein, the device 1405 can support techniques for including time domain behavior in a RACH opportunity-PUSCH opportunity mapping pattern, which can increase signaling throughput, reduce latency, and improve signaling efficiency.

[0205] In some examples, the communication manager 1420 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1415, one or more antennas 1425, or any combination thereof. Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the processor 1440, the memory 1430, the code 1435, or any combination thereof. For example, the code 1435 may include instructions that are executable by the processor 1440 to cause the device 1405 to perform various aspects of the random access and uplink shared channel opportunity mapping patterns for the random access procedure as described herein, or the processor 1440 and the memory 1430 may be otherwise configured to perform or support such operations.

[0206] Fig.15 A block diagram 1500 of a device 1505 supporting random access and uplink shared channel opportunity mapping patterns for a random access procedure according to one or more aspects of the present disclosure is shown. The device 1505 may be an example of aspects of the network entity 105 as described herein. The device 1505 may include a receiver 1510, a transmitter 1515, and a communication manager 1520. The device 1505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0207] Receiver 1510 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 passed to other components of device 1505. In some examples, receiver 1510 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1510 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0208] The transmitter 1515 may provide a means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1505. For example, the transmitter 1515 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 1515 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1515 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 1515 and the receiver 1510 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0209] The communication manager 1520, the receiver 1510, the transmitter 1515, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of random access and uplink shared channel opportunity mapping patterns for random access procedures as described herein. For example, the communication manager 1520, the receiver 1510, the transmitter 1515, or various combinations or components thereof may support methods for performing one or more of the functions described herein.

[0210] In some examples, the communication manager 1520, the receiver 1510, the transmitter 1515, 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 components, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. 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).

[0211] Additionally or alternatively, in some examples, the communication manager 1520, the receiver 1510, the transmitter 1515, 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 1520, the receiver 1510, the transmitter 1515, 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 functions 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.

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

[0213] 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 a component for sending control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure. The communication manager 1520 may be configured to or otherwise support a component for receiving one or more preambles of a random access message of a random access procedure in one or more random access opportunities according to the time domain mapping pattern. The communication manager 1520 may be configured to or otherwise support a component for receiving one or more uplink payload transmissions of a random access message of a random access procedure in one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0214] By including or configuring a communication manager 1520 according to examples as described herein, a device 1505 (e.g., a processor controlling or otherwise coupled with a receiver 1510, a transmitter 1515, a communication manager 1520, or a combination thereof) may support techniques for including time domain behavior in a RACH opportunity-PUSCH opportunity mapping pattern, which may increase signaling throughput, reduce latency, and improve signaling efficiency.

[0215] Fig.16A block diagram 1600 of a device 1605 supporting random access and uplink shared channel opportunity mapping patterns for a random access procedure according to one or more aspects of the present disclosure is shown. The device 1605 may be an example of aspects of the device 1505 or network entity 105 as described herein. The device 1605 may include a receiver 1610, a transmitter 1615, and a communication manager 1620. The device 1605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0216] Receiver 1610 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 passed to other components of device 1605. In some examples, receiver 1610 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1610 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0217] The transmitter 1615 may provide a means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of the device 1605. For example, the transmitter 1615 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 1615 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1615 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 1615 and the receiver 1610 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0218] The device 1605 or its various components may be examples of components for performing various aspects of random access and uplink shared channel timing mapping patterns for random access procedures as described herein. For example, the communication manager 1620 may include a control signaling component 1625, a RACH timing component 1630, a PUSCH timing component 1635, or any combination thereof. The communication manager 1620 may be an example of various aspects of the communication manager 1520 as described herein. In some examples, the communication manager 1620 or its various components may be configured to use or otherwise cooperate with the receiver 1610, the transmitter 1615, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 1620 may receive information from the receiver 1610, transmit information to the transmitter 1615, or be integrated with the receiver 1610, the transmitter 1615, or both to obtain information, output information, or perform various other operations as described herein.

[0219] According to examples as disclosed herein, the communication manager 1620 may support wireless communications at a network entity. The control signaling component 1625 may be configured to or otherwise support components for sending control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure. The RACH opportunity component 1630 may be configured to or otherwise support components for receiving one or more preambles of a random access message of a random access procedure in one or more random access opportunities according to the time domain mapping pattern. The PUSCH opportunity component 1635 may be configured to or otherwise support components for receiving one or more uplink payload transmissions of a random access message of a random access procedure in one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0220] Fig.17A block diagram 1700 of a communication manager 1720 supporting random access and uplink shared channel timing mapping patterns for random access procedures in accordance with one or more aspects of the present disclosure is shown. The communication manager 1720 may be an example of aspects of the communication manager 1520, the communication manager 1620, or both as described herein. The communication manager 1720 or its various components may be examples of components for performing various aspects of the random access and uplink shared channel timing mapping patterns for random access procedures as described herein. For example, the communication manager 1720 may include a control signaling component 1725, a RACH timing component 1730, a PUSCH timing component 1735, a continuous transmission component 1740, an interleaved transmission component 1745, a transmission repetition component 1750, a joint transmission component 1755, a response component 1760, or any combination thereof. Each of these components may communicate directly or indirectly with each other (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 the 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.

[0221] According to examples as disclosed herein, the communication manager 1720 may support wireless communications at a network entity. The control signaling component 1725 may be configured to or otherwise support components for sending control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure. The RACH opportunity component 1730 may be configured to or otherwise support components for receiving one or more preambles of a random access message of a random access procedure in one or more random access opportunities according to the time domain mapping pattern. The PUSCH opportunity component 1735 may be configured to or otherwise support components for receiving one or more uplink payload transmissions of a random access message of a random access procedure in one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0222] In some examples, the continuous transmission component 1740 may be configured as or otherwise support components for receiving one or more preamble codes in one or more consecutive random access opportunities and receiving one or more uplink payload transmissions in one or more consecutive uplink shared channel opportunities according to a time domain mapping pattern, wherein the one or more consecutive uplink shared channel opportunities are after the one or more consecutive random access opportunities.

[0223] In some examples, interleaved transmission component 1745 may be configured to or otherwise support means for transmitting control signaling indicating a time domain mapping pattern, wherein the time domain mapping pattern indicates that one or more random access opportunities and one or more uplink shared channel opportunities are interleaved in the time domain. In some examples, interleaved transmission component 1745 may be configured to or otherwise support means for receiving one or more preambles and one or more uplink payload transmissions, wherein the one or more preambles and the one or more uplink payload transmissions are interleaved based on the time domain mapping pattern.

[0224] In some examples, to support receiving one or more preambles, the RACH opportunity component 1730 may be configured as or otherwise support components for receiving one or more preambles in one or more consecutive random access opportunities according to a time domain mapping pattern, where the one or more consecutive random access opportunities are TDMed within one or more random access slots.

[0225] In some examples, to support reception of one or more uplink payload transmissions, the PUSCH opportunity component 1735 may be configured as or otherwise support components for receiving one or more uplink payload transmissions in one or more consecutive uplink shared channel opportunities that are TDMed according to a time domain mapping pattern, wherein the one or more uplink payload transmissions are associated with a subset of one or more preamble codes.

[0226] In some examples, the transmit repetition component 1750 may be configured as or otherwise support components for receiving one or more preamble codes in one or more random access opportunities and receiving a first uplink payload transmission in a first uplink shared channel opportunity in one or more uplink payload transmissions according to a time domain mapping pattern.

[0227] In some examples, the transmit repetition component 1750 may be configured as or otherwise support components for receiving a first preamble of one or more preambles in a first random access opportunity in one or more random access opportunities and receiving one or more uplink payload transmissions in one or more uplink shared channel opportunities according to a time domain mapping pattern.

[0228] In some examples, the joint transmit component 1755 may be configured to or otherwise support components for transmitting control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities, the time domain mapping pattern being based on a set of joint preamble and uplink payload transmission repetitions associated with one or more repetition levels, wherein the set of joint preamble and uplink payload transmission repetitions is TDM, FDM, or CDM.

[0229] In some examples, for a set of joint preamble and uplink payload transmission repetitions that are CDMed, a first joint payload and uplink payload transmission repetition is associated with one or more repetition levels.

[0230] In some examples, response component 1760 may be configured as or otherwise support components for sending a RAR message in a RAR window, where the start of the RAR window is based on a last preamble of one or more preambles associated with a first repetition level or a last symbol of a last uplink payload transmission of one or more uplink payload transmissions.

[0231] In some examples, the joint transmission component 1755 can be configured to or otherwise support components for receiving a set of joint preamble and uplink payload transmission repetitions, wherein the set of joint preamble and uplink payload transmission repetitions is associated with one or more SSBs of a given repetition level. In some examples, the number of SSBs associated with the highest identified RSRP is associated with the repetition level.

[0232] Fig.18 A diagram of a system 1800 including a device 1805 supporting random access and uplink shared channel opportunity mapping patterns for a random access procedure according to one or more aspects of the present disclosure is shown. The device 1805 may be an example of a device 1505, a device 1605, or a network entity 105 as described herein, or include components thereof. The device 1805 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 1805 may include components that support output and acquisition of communications, such as a communication manager 1820, a transceiver 1810, an antenna 1815, a memory 1825, a code 1830, and a processor 1835. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1840).

[0233] The transceiver 1810 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1810 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1810 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1805 may include one or more antennas 1815, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1810 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1815, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1815, from a wired receiver); and demodulating the signal. In some implementations, the transceiver 1810 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1815 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1815 configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1810 may include or be configured to be coupled to one or more processors or memory components, which are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1810, or the transceiver 1810 and one or more antennas 1815, or the transceiver 1810 and one or more antennas 1815 and one or more processors or memory components (e.g., processor 1835 or memory 1825 or both) may be included in a chip or chip assembly installed in the device 1805. 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 ).

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

[0235] The processor 1835 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 component, a discrete hardware component, or any combination thereof). In some cases, the processor 1835 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 1835. The processor 1835 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1825) to enable the device 1805 to perform various functions (e.g., functions or tasks supporting random access and uplink shared channel opportunity mapping modes for random access procedures). For example, the device 1805 or a component of the device 1805 may include a processor 1835 and a memory 1825 coupled to the processor 1835, and the processor 1835 and the memory 1825 are configured to perform various functions described herein. The processor 1835 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 instance) that may host functions for performing the functions of the device 1805 (e.g., by executing code 1830). The processor 1835 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1805 (such as in the memory 1825). In some specific implementations, the processor 1835 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 1805). For example, the processing system of the device 1805 may refer to a system including various other components or subcomponents of the device 1805 (such as the processor 1835, or the transceiver 1810, or the communication manager 1820, or other components or combinations of components of the device 1805). The processing system of device 1805 can be docked with other components of device 1805, and can process information (such as input or signal) received from other components or output information to other components. For example, a chip or modem of device 1805 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 a processing system of a chip or modem and a transmitter, so that device 1805 can send information output from the chip or modem.Additionally or alternatively, in some implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, such that the device 1805 can obtain information or signal input, and the information can be passed to the processing system. Those of ordinary skill in the art will readily recognize that a first interface can also obtain information or signal input, and a second interface can also output information or signal output.

[0236] In some examples, bus 1840 may support communications of protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1840 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 1805, or communications performed between different components of device 1805 that may be co-located or may be located in different locations (e.g., where device 1805 may refer to a system in which one or more of communication manager 1820, transceiver 1810, memory 1825, code 1830, and processor 1835 may be located in one component of different components or divided between different components).

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

[0238] According to examples as disclosed herein, the communication manager 1820 may support wireless communications at a network entity. For example, the communication manager 1820 may be configured to or otherwise support a component for sending control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure. The communication manager 1820 may be configured to or otherwise support a component for receiving one or more preambles of a random access message of a random access procedure in one or more random access opportunities according to the time domain mapping pattern. The communication manager 1820 may be configured to or otherwise support a component for receiving one or more uplink payload transmissions of a random access message of a random access procedure in one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0239] By including or configuring the communication manager 1820 according to examples as described herein, the device 1805 can support techniques for including time domain behavior in a RACH opportunity-PUSCH opportunity mapping pattern, which can increase signaling throughput, reduce latency, and improve signaling efficiency.

[0240] In some examples, the communication manager 1820 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1810, one or more antennas 1815 (e.g., where applicable), or any combination thereof. Although the communication manager 1820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1820 may be supported or performed by the transceiver 1810, the processor 1835, the memory 1825, the code 1830, or any combination thereof. For example, the code 1830 may include instructions that are executable by the processor 1835 to cause the device 1805 to perform various aspects of the random access and uplink shared channel opportunity mapping patterns for the random access process as described herein, or the processor 1835 and the memory 1825 may be otherwise configured to perform or support such operations.

[0241] Fig.19 A flow chart illustrating a method 1900 for supporting random access and uplink shared channel timing mapping patterns for a random access procedure according to one or more aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a UE or a component thereof as described herein. Figures 1 to 14 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.

[0242] At 1905, the method may include receiving control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure. 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.13 The described mapping mode component 1325 is executed.

[0243] At 1910, the method may include sending one or more preambles of a random access message of a random access procedure in one or more random access opportunities according to a time domain mapping pattern. 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 to Fig.13The described preamble component 1330 is performed.

[0244] At 1915, the method may include sending one or more uplink payloads of a random access message of a random access procedure in one or more uplink shared channel opportunities according to a time domain mapping pattern. 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 to Fig.13 The described uplink payload component 1335 is performed.

[0245] Fig. 20 A flow chart illustrating a method 2000 for supporting random access and uplink shared channel timing mapping patterns for a random access procedure according to one or more aspects of the present disclosure is shown. The operations of the method 2000 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 2000 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 14 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.

[0246] At 2005, the method may include receiving control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure. The operations of 2005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed as described in reference to Fig.13 The described mapping mode component 1325 is executed.

[0247] At 2010, the method may include sending one or more preambles in one or more consecutive random access opportunities and sending one or more uplink payloads in one or more consecutive uplink shared channel opportunities according to a time domain mapping pattern, wherein the one or more consecutive uplink shared channel opportunities are after the one or more consecutive random access opportunities. The operations of 2010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed as described in reference to Fig.13 The continuous RACH component 1340 performs.

[0248] Fig.21 A flow chart illustrating a method 2100 for supporting random access and uplink shared channel timing mapping patterns for a random access procedure according to one or more aspects of the present disclosure is shown. The operations of the method 2100 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 2100 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 14The 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.

[0249] At 2105, the method may include receiving control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure, wherein the time domain mapping pattern indicates that the one or more random access opportunities and the one or more uplink shared channel opportunities are interleaved in the time domain. The operations of 2105 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2105 may be performed as described in reference to Fig.13 The interleaving component 1345 is used to perform.

[0250] At 2110, the method may include sending one or more preambles and one or more uplink payload transmissions, wherein the one or more preambles and the one or more uplink payload transmissions are interleaved based on a time domain mapping pattern. The operations of 2110 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2110 may be performed as described in reference to Fig.13 The sending component 1350 executes.

[0251] Fig. 22 A flow chart illustrating a method 2200 for supporting random access and uplink shared channel timing mapping patterns for a random access procedure according to one or more aspects of the present disclosure is shown. The operations of the method 2200 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2200 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 10 as well as Figures 15 to 18 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.

[0252] At 2205, the method may include sending control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure. The operations of 2205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2205 may be performed as described in reference to Fig.17 The control signaling component 1725 is used to execute.

[0253] At 2210, the method may include receiving one or more preambles of a random access message of a random access procedure in one or more random access opportunities according to a time domain mapping pattern. The operations of 2210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2210 may be performed as described in reference to Fig.17 The RACH timing component 1730 is executed.

[0254] At 2215, the method may include receiving one or more uplink payload transmissions of a random access message of a random access procedure in one or more uplink shared channel opportunities according to a time domain mapping pattern. The operations of 2215 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2215 may be performed as described in reference to Fig.17 The PUSCH timing component 1735 is used to perform.

[0255] Fig.23 A flow chart illustrating a method 2300 for supporting random access and uplink shared channel timing mapping patterns for a random access procedure according to one or more aspects of the present disclosure is shown. The operations of the method 2300 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2300 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 10 as well as Figures 15 to 18 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.

[0256] At 2305, the method may include sending control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities, the time domain mapping pattern being based on a set of joint preamble and uplink payload transmission repetitions associated with one or more repetition levels, wherein the set of joint preamble and uplink payload transmission repetitions is TDM, FDM, or CDM. The operations of 2305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2305 may be performed as described in reference to Fig.17 The described joint sending component 1755 performs.

[0257] At 2310, the method may include sending control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure. The operations of 2310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2310 may be performed as described in reference to Fig.17 The control signaling component 1725 is used to execute.

[0258] At 2315, the method may include receiving one or more preambles of a random access message of a random access procedure in one or more random access opportunities according to the time domain mapping pattern. The operations of 2315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2315 may be performed as described in reference to Fig.17 The RACH timing component 1730 is executed.

[0259] Fig.24 A flow chart illustrating a method 2400 for supporting random access and uplink shared channel timing mapping patterns for a random access procedure according to one or more aspects of the present disclosure is shown. The operations of the method 2400 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2400 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 10 as well as Figures 15 to 18 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.

[0260] At 2405, the method may include sending control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure. The operations of 2405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2405 may be performed as described in reference to Fig.17 The control signaling component 1725 is used to execute.

[0261] At 2410, the method may include receiving one or more preambles of a random access message of a random access procedure in one or more random access opportunities according to a time domain mapping pattern. The operations of 2410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2410 may be performed as described in reference to Fig.17 The RACH timing component 1730 is executed.

[0262] At 2415, the method may include receiving one or more uplink payload transmissions of a random access message of a random access procedure in one or more uplink shared channel opportunities according to a time domain mapping pattern. The operations of 2415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2415 may be performed as described in reference to Fig.17 The PUSCH timing component 1735 is used to perform.

[0263] At 2420, the method may include sending a RAR message in a RAR window, wherein the start of the RAR window is based on a last preamble of one or more preambles associated with the first repetition level or a last symbol of a last uplink payload transmission of one or more uplink payload transmissions. The operations of 2420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2420 may be performed as described in reference to Fig.17 The described response component 1760 is executed.

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

[0265] Aspect 1: A method for performing wireless communication at a UE, the method comprising: receiving control signaling, the control signaling indicating a time domain mapping pattern between one or more random access opportunities for sending a random access message of a random access process and one or more uplink shared channel opportunities; sending one or more preamble codes of the random access message of the random access process in the one or more random access opportunities according to the time domain mapping pattern; and sending one or more uplink payloads of the random access message of the random access process in the one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0266] Aspect 2: According to the method described in Aspect 1, the method also includes: sending the one or more preamble codes in one or more consecutive random access opportunities according to the time domain mapping pattern and sending the one or more uplink payloads in one or more consecutive uplink shared channel opportunities, wherein the one or more consecutive uplink shared channel opportunities are after the one or more consecutive random access opportunities.

[0267] Aspect 3: According to the method described in any one of Aspects 1 to 2, the method further includes: receiving the control signaling indicating the time domain mapping pattern, wherein the time domain mapping pattern indicates that the one or more random access opportunities and the one or more uplink shared channel opportunities are interlaced in the time domain; and sending the one or more preamble codes and the one or more uplink payload transmissions, wherein the one or more preamble codes and the one or more uplink payload transmissions are interlaced at least in part based on the time domain mapping pattern.

[0268] Aspect 4: A method according to any one of Aspects 1 to 3, wherein sending the one or more preamble codes comprises: sending the one or more preamble codes in one or more consecutive random access opportunities according to the time domain mapping pattern, and the one or more consecutive random access opportunities are TDMed within one or more random access time slots.

[0269] Aspect 5: A method according to any one of Aspects 1 to 4, wherein sending the one or more uplink payload transmissions includes: sending the one or more uplink payload transmissions in one or more consecutive uplink shared channel opportunities that are TDMed according to the time domain mapping pattern, wherein the one or more uplink payload transmissions are associated with a subset of the one or more preamble codes.

[0270] Aspect 6: According to the method described in any one of Aspects 1 to 5, the method further includes: sending the one or more preamble codes in the one or more random access opportunities and sending the first uplink payload transmission among the one or more uplink payload transmissions in the first uplink shared channel opportunity in the one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0271] Aspect 7: According to the method described in any one of Aspects 1 to 6, the method further includes: sending the first preamble code among the one or more random access codes in the first random access opportunity among the one or more random access opportunities according to the time domain mapping pattern and sending the one or more uplink payloads in the one or more uplink shared channel opportunities.

[0272] Aspect 8: According to the method described in any one of Aspects 1 to 7, the method further includes: receiving the control signaling indicating the time domain mapping pattern between the one or more random access opportunities and the one or more uplink shared channel opportunities, the time domain mapping pattern being at least partially based on a set of joint preamble code and uplink payload transmission repetitions associated with one or more repetition levels, wherein the set of joint preamble code and uplink payload transmission repetitions is TDM, FDM or CDM.

[0273] Aspect 9: The method according to aspect 8, wherein, for the set of joint preamble and uplink payload transmission repetitions that are CDMed, a first joint payload and uplink payload transmission repetition is associated with one or more repetition levels.

[0274] Aspect 10: According to the method described in any one of Aspects 1 to 9, the method also includes: receiving a RAR message in a RAR window, wherein the start of the RAR window is at least partially based on the last preamble code of the one or more preamble codes associated with the first repetition level or the last symbol of the last uplink payload transmission of the one or more uplink payload transmissions.

[0275] Aspect 11: According to any one of Aspects 1 to 10, the method further includes: sending a set of joint preamble code and uplink payload sending repetitions, wherein the set of joint preamble code and uplink payload sending repetitions is associated with one or more SSBs of a given repetition level.

[0276] Aspect 12: According to the method described in Aspect 11, the method also includes: selecting the first joint preamble code and uplink payload transmission repetition in the set of joint preamble code and uplink payload transmission repetitions based at least in part on the SSB associated with the first joint preamble code and uplink payload transmission repetition corresponding to the highest identification RSRP.

[0277] Aspect 13: The method according to any one of aspects 11 to 12, wherein the number of SSBs associated with the highest identified RSRP is associated with a repetition level.

[0278] Aspect 14: A method for performing wireless communications at a network entity, the method comprising: sending control signaling, the control signaling indicating a time domain mapping pattern between one or more random access opportunities for sending a random access message of a random access process and one or more uplink shared channel opportunities; receiving one or more preamble codes of the random access message of the random access process in the one or more random access opportunities according to the time domain mapping pattern; and receiving one or more uplink payload transmissions of the random access message of the random access process in the one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0279] Aspect 15: According to the method described in Aspect 14, the method also includes: receiving the one or more preamble codes in one or more consecutive random access opportunities according to the time domain mapping pattern and receiving the one or more uplink payload transmissions in one or more consecutive uplink shared channel opportunities, wherein the one or more consecutive uplink shared channel opportunities are after the one or more consecutive random access opportunities.

[0280] Aspect 16: According to the method described in any one of Aspects 14 to 15, the method further includes: sending the control signaling indicating the time domain mapping pattern, wherein the time domain mapping pattern indicates that the one or more random access opportunities and the one or more uplink shared channel opportunities are interleaved in the time domain; and receiving the one or more preamble codes and the one or more uplink payload transmissions, wherein the one or more preamble codes and the one or more uplink payload transmissions are interleaved at least in part based on the time domain mapping pattern.

[0281] Aspect 17: A method according to any one of Aspects 14 to 16, wherein receiving the one or more preamble codes includes: receiving the one or more preamble codes in one or more consecutive random access opportunities according to the time domain mapping pattern, and the one or more consecutive random access opportunities are TDM within one or more random access time slots.

[0282] Aspect 18: A method according to any one of Aspects 14 to 17, wherein receiving the one or more uplink payload transmissions includes: receiving the one or more uplink payload transmissions in one or more consecutive uplink shared channel opportunities that are TDMed according to the time domain mapping pattern, wherein the one or more uplink payload transmissions are associated with a subset of the one or more preamble codes.

[0283] Aspect 19: According to the method described in any one of Aspects 14 to 18, the method further includes: receiving the one or more preamble codes in the one or more random access opportunities and receiving the first uplink payload transmission among the one or more uplink payload transmissions in the first uplink shared channel opportunity among the one or more uplink shared channel opportunities according to the time domain mapping pattern.

[0284] Aspect 20: According to the method described in any one of Aspects 14 to 19, the method further includes: receiving the first preamble code among the one or more random access codes in the first random access opportunity among the one or more random access opportunities according to the time domain mapping pattern and receiving the one or more uplink payload transmissions in the one or more uplink shared channel opportunities.

[0285] Aspect 21: According to the method described in any one of Aspects 14 to 20, the method further includes: sending the control signaling indicating the time domain mapping pattern between the one or more random access opportunities and the one or more uplink shared channel opportunities, the time domain mapping pattern being at least partially based on a set of joint preamble code and uplink payload transmission repetitions associated with one or more repetition levels, wherein the set of joint preamble code and uplink payload transmission repetitions is TDM, FDM or CDM.

[0286] Aspect 22: The method according to aspect 21, wherein, for the set of joint preamble and uplink payload transmission repetitions that are CDMed, a first joint payload and uplink payload transmission repetition is associated with one or more repetition levels.

[0287] Aspect 23: According to the method described in any one of Aspects 14 to 22, the method also includes: sending a RAR message in a RAR window, wherein the start of the RAR window is at least partially based on the last preamble code of the one or more preamble codes associated with the first repetition level or the last symbol of the last uplink payload transmission of the one or more uplink payload transmissions.

[0288] Aspect 24: According to any one of Aspects 14 to 23, the method further includes: receiving a set of joint preamble code and uplink payload transmission repetitions, wherein the set of joint preamble code and uplink payload transmission repetitions is associated with one or more SSBs of a given repetition level.

[0289] Aspect 25: The method according to Aspect 24, wherein the number of SSBs associated with the highest identified RSRP is associated with the repetition level.

[0290] Aspect 26: 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 13.

[0291] Aspect 27: 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 13.

[0292] Aspect 28: 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 the method according to any one of aspects 1 to 13.

[0293] Aspect 29: 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 14 to 25.

[0294] Aspect 30: 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 14 to 25.

[0295] Aspect 31: 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 the method according to any one of aspects 14 to 25.

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

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

[0298] The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips 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.

[0299] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic components, 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, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0300] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of 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 can 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 can also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0301] Computer-readable media include both non-transient computer storage media and communication media, including any media that facilitates the transfer of a computer program from one location to another. Non-transient storage media can be any available media that can be accessed by a general or special computer. By way of example and not limitation, non-transient computer-readable media may 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 to carry or store desired program code components in the form of instructions or data structures and any other non-transient media that can be accessed by a general or special computer or a general or special processor. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwaves, coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwaves are included in the definition of computer-readable media. Disks and optical disks as used herein include CDs, laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, while optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0302] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed 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" can 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".

[0303] 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, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

[0304] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the 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.

[0305] 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 implementation includes 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.

[0306] 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. A method for wireless communication at a user equipment (UE), the method comprising: receiving control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure; sending one or more preambles of the random access message of the random access procedure in the one or more random access opportunities according to the time domain mapping pattern; as well as One or more uplink payloads of the random access message of the random access procedure are transmitted in the one or more uplink shared channel opportunities according to the time domain mapping pattern.

2. The method according to claim 1, further comprising: The one or more preambles are sent in one or more consecutive random access opportunities and the one or more uplink payloads are sent in one or more consecutive uplink shared channel opportunities according to the time domain mapping pattern, wherein the one or more consecutive uplink shared channel opportunities are after the one or more consecutive random access opportunities.

3. The method according to claim 1, further comprising: receiving the control signaling indicating the time domain mapping pattern, wherein the time domain mapping pattern indicates that the one or more random access opportunities and the one or more uplink shared channel opportunities are interleaved in the time domain; and The one or more preambles and the one or more uplink payload transmissions are transmitted, wherein the one or more preambles and the one or more uplink payload transmissions are interleaved based at least in part on the time domain mapping pattern.

4. The method of claim 1 , wherein sending the one or more preambles comprises: The one or more preambles are sent in one or more consecutive random access opportunities according to the time domain mapping pattern, and the one or more consecutive random access opportunities are time-division multiplexed in one or more random access time slots.

5. The method of claim 1 , wherein sending the one or more uplink payloads comprises: The one or more uplink payload transmissions are transmitted in one or more consecutive uplink shared channel opportunities that are time division multiplexed according to the time domain mapping pattern, wherein the one or more uplink payload transmissions are associated with a subset of the one or more preambles.

6. The method according to claim 1, further comprising: The one or more preambles are sent in the one or more random access opportunities and a first uplink payload transmission of the one or more uplink payload transmissions is sent in a first uplink shared channel opportunity of the one or more uplink shared channel opportunities according to the time domain mapping pattern.

7. The method according to claim 1, further comprising: A first preamble of the one or more preambles is sent in a first random access opportunity of the one or more random access opportunities and the one or more uplink payloads are sent in the one or more uplink shared channel opportunities according to the time domain mapping pattern.

8. The method according to claim 1, further comprising: Receive the control signaling indicating the time domain mapping pattern between the one or more random access opportunities and the one or more uplink shared channel opportunities, the time domain mapping pattern being based at least in part on a set of joint preamble and uplink payload transmission repetitions associated with one or more repetition levels, wherein the set of joint preamble and uplink payload transmission repetitions is time division multiplexed, frequency division multiplexed, or code division multiplexed.

9. The method according to claim 8, wherein: For the set of code division multiplexed joint preamble and uplink payload transmission repetitions, a first joint payload and uplink payload transmission repetition is associated with one or more repetition levels.

10. The method according to claim 1, further comprising: A random access response message is received in a random access response window, wherein a start of the random access response window is based at least in part on a last preamble of the one or more preambles associated with a first repetition level or a last symbol of a last uplink payload transmission of the one or more uplink payload transmissions.

11. The method according to claim 1, further comprising: A set of joint preamble and uplink payload transmission repetitions is transmitted, wherein the set of joint preamble and uplink payload transmission repetitions is associated with one or more synchronization signal blocks of a given repetition level.

12. The method according to claim 11, further comprising: The first joint preamble and uplink payload transmission repetition in the set of joint preamble and uplink payload transmission repetitions is selected based at least in part on a synchronization signal block associated with the first joint preamble and uplink payload transmission repetition corresponding to a highest identification reference signal received power.

13. The method of claim 11, wherein the number of synchronization signal blocks associated with the highest identification reference signal received power is associated with a repetition level.

14. A method for wireless communication at a network entity, the method comprising: Sending control signaling indicating a time domain mapping mode between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure; receiving one or more preambles of the random access message of the random access procedure in the one or more random access opportunities according to the time domain mapping pattern; as well as One or more uplink payload transmissions of the random access message of the random access procedure are received in the one or more uplink shared channel opportunities according to the time domain mapping pattern.

15. The method according to claim 14, further comprising: The one or more preambles are received in one or more consecutive random access opportunities and the one or more uplink payload transmissions are received in one or more consecutive uplink shared channel opportunities according to the time domain mapping pattern, wherein the one or more consecutive uplink shared channel opportunities are subsequent to the one or more consecutive random access opportunities.

16. The method according to claim 14, further comprising: sending the control signaling indicating the time domain mapping pattern, wherein the time domain mapping pattern indicates that the one or more random access opportunities and the one or more uplink shared channel opportunities are interleaved in the time domain; as well as The one or more preambles and the one or more uplink payload transmissions are received, wherein the one or more preambles and the one or more uplink payload transmissions are interleaved based at least in part on the time domain mapping pattern.

17. The method of claim 14, wherein receiving the one or more preambles comprises: The one or more preambles are received in one or more consecutive random access opportunities according to the time domain mapping pattern, and the one or more consecutive random access opportunities are time-division multiplexed in one or more random access slots.

18. The method of claim 14, wherein receiving the one or more uplink payload transmissions comprises: The one or more uplink payload transmissions are received in one or more consecutive uplink shared channel opportunities that are time division multiplexed according to the time domain mapping pattern, wherein the one or more uplink payload transmissions are associated with a subset of the one or more preambles.

19. The method according to claim 14, further comprising: The one or more preambles are received in the one or more random access opportunities and a first uplink payload transmission of the one or more uplink payload transmissions is received in a first uplink shared channel opportunity of the one or more uplink shared channel opportunities according to the time domain mapping pattern.

20. The method according to claim 14, further comprising: A first preamble of the one or more preambles is received in a first random access opportunity of the one or more random access opportunities and the one or more uplink payload transmissions are received in the one or more uplink shared channel opportunities according to the time domain mapping pattern.

21. The method according to claim 14, further comprising: The control signaling is sent to indicate the time domain mapping pattern between the one or more random access opportunities and the one or more uplink shared channel opportunities, wherein the time domain mapping pattern is at least partially based on a set of joint preamble code and uplink payload transmission repetitions associated with one or more repetition levels, wherein the set of joint preamble code and uplink payload transmission repetitions is time division multiplexed, frequency division multiplexed, or code division multiplexed.

22. The method according to claim 21, wherein: For the set of code division multiplexed joint preamble and uplink payload transmission repetitions, a first joint payload and uplink payload transmission repetition is associated with one or more repetition levels.

23. The method according to claim 14, further comprising: A random access response message is sent in a random access response window, wherein a start of the random access response window is based at least in part on a last preamble of the one or more preambles associated with a first repetition level or a last symbol of a last uplink payload transmission of the one or more uplink payload transmissions.

24. The method according to claim 14, further comprising: A set of joint preamble and uplink payload transmission repetitions is received, wherein the set of joint preamble and uplink payload transmission repetitions is associated with one or more synchronization signal blocks of a given repetition level.

25. The method of claim 24, wherein the number of synchronization signal blocks associated with the highest identification reference signal received power is associated with a repetition level.

26. 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 control signaling indicating a time domain mapping pattern between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure; sending one or more preambles of the random access message of the random access procedure in the one or more random access opportunities according to the time domain mapping pattern; as well as One or more uplink payloads of the random access message of the random access procedure are transmitted in the one or more uplink shared channel opportunities according to the time domain mapping pattern.

27. The apparatus of claim 26, wherein the instructions are further executable by the processor to cause the apparatus to: The one or more preambles are sent in one or more consecutive random access opportunities and the one or more uplink payloads are sent in one or more consecutive uplink shared channel opportunities according to the time domain mapping pattern, wherein the one or more consecutive uplink shared channel opportunities are after the one or more consecutive random access opportunities.

28. The apparatus of claim 26, wherein the instructions are further executable by the processor to cause the apparatus to: receiving the control signaling indicating the time domain mapping pattern, wherein the time domain mapping pattern indicates that the one or more random access opportunities and the one or more uplink shared channel opportunities are interleaved in the time domain; and The one or more preambles and the one or more uplink payload transmissions are transmitted, wherein the one or more preambles and the one or more uplink payload transmissions are interleaved based at least in part on the time domain mapping pattern.

29. 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: Sending control signaling indicating a time domain mapping mode between one or more random access opportunities and one or more uplink shared channel opportunities for sending a random access message of a random access procedure; receiving one or more preambles of the random access message of the random access procedure in the one or more random access opportunities according to the time domain mapping pattern; as well as One or more uplink payload transmissions of the random access message of the random access procedure are received in the one or more uplink shared channel opportunities according to the time domain mapping pattern.

30. The apparatus of claim 29, wherein the instructions are further executable by the processor to cause the apparatus to: The one or more preambles are received in one or more consecutive random access opportunities and the one or more uplink payload transmissions are received in one or more consecutive uplink shared channel opportunities according to the time domain mapping pattern, wherein the one or more consecutive uplink shared channel opportunities are subsequent to the one or more consecutive random access opportunities.

Images