Response enhancements for multiple random access procedures

Through the improved RAR enhancement method, the UE can execute multiple RACH procedures in parallel based on multiple PDCCH commands and instructions in RAR, which solves the problem that existing technologies cannot process multiple RACH procedures in parallel, and improves the efficiency and flexibility of the access process.

CN118901274APending Publication Date: 2024-11-05QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280093820.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-03-31
Publication Date
2024-11-05

AI Technical Summary

Technical Problem

In the prior art, when performing the Random Access Channel (RACH) procedure, the User Equipment (UE) cannot execute multiple RACH procedures in parallel at the same time, resulting in low efficiency of the access process.

Method used

With the improved Random Access Response (RAR) enhancement method, the UE can receive multiple PDCCH commands, determine the parallel execution of multiple RACH procedures based on the random access preamble identifier and timing advance group indication in the RAR, and support the transmission of multiple random access preambles and the association of RARs.

Benefits of technology

This enables the UE to process multiple RACH procedures in parallel, improving the efficiency and flexibility of the access process and reducing access latency and resource conflicts.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118901274A_ABST
    Figure CN118901274A_ABST
Patent Text Reader

Abstract

Methods, systems, and devices for wireless communication are described. A wireless communication system may support techniques for random access response (RAR) enhancements for multiple random access channel (RACH) procedures. In some cases, a user equipment (UE) may receive a plurality of physical downlink control channel (PDCCH) commands that trigger a respective RACH procedure, each PDCCH command indicating a preamble identifier associated with the respective RACH procedure. In some cases, the preamble identifiers may be the same or different. The UE may transmit a random access preamble corresponding to the preamble identifier indicated in the PDCCH command, and may receive a random access response associated with the respective RACH procedure based at least in part on the indication included in the random access response. In some cases, the indication may be associated with a preamble identifier indication. In some other cases, the indication may be associated with a timing advance group.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The following relates to wireless communications including random access response (RAR) enhancements for multiple random access channel (RACH) 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, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may use technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication of a communication device, which may be referred to as a user equipment (UE). Summary of the invention

[0003] The described technology relates to improved methods, systems, devices and apparatuses for supporting random access response (RAR) enhancement for multiple random access channel (RACH) procedures. In general, the described technology enables a user equipment (UE) to determine which random access procedure (e.g., RACH procedure) the RAR corresponds to based on an indication in the RAR (e.g., when one or more random access procedures are triggered while a first (e.g., initial) random access procedure is ongoing). For example, the UE may receive multiple physical downlink control channel (PDCCH) commands, each of which is associated with a corresponding random access procedure. The PDCCH command may allocate or assign a random access preamble identifier associated with the corresponding random access procedure. In some cases, the random access preamble identifier may be the same for multiple PDCCH commands, or in other cases, the random access preamble identifier may be different. The UE may send a random access preamble in response to each received PDCCH command, wherein each random access preamble is associated with a random access preamble identifier indicated in the corresponding PDCCH command. The UE may monitor or receive at least one RAR associated with one of the random access procedures.

[0004] In some cases (e.g., when each PDCCH command allocates a unique random access preamble identifier), the UE may receive the RAR and determine which random access procedure the RAR is associated with based on the random access preamble identifier indication included in the RAR. Additionally or alternatively, the UE may receive the RAR and determine which random access procedure the RAR is associated with based on an indication of a timing advance group included in the RAR. In some cases, the timing advance group may be indicated by: a timing advance group indicator field in the RAR, a combination of a reserved field and a channel state information (CSI) request field in the RAR, a random access temporary identifier for scrambling a PDCCH in the RAR, one or more reserved bits in a PDCCH in the RAR, or a control resource set (CORESET) pool index associated with a PDCCH in the RAR.

[0005] In some examples, the UE may determine that the timing advance group is associated with the random access procedure based on a CORESET pool index associated with a PDCCH command or a random access opportunity associated with a random access preamble. For example, a network entity may send a PDCCH command associated with a CORESET pool index that triggers a random access procedure, and the UE may determine that the CORESET pool index corresponds to the timing advance group. Therefore, the UE may determine that the random access procedure triggered by the PDCCH command is associated with the timing advance group.

[0006] A method for wireless communication at a UE is described. The method may include: receiving a first control message in a first PDCCH command triggering a first random access procedure, the first control message indicating a first preamble identifier associated with the first random access procedure; receiving a second control message in a second PDCCH command triggering a second random access procedure during the first random access procedure, the second control message indicating a second preamble identifier associated with the second random access procedure, wherein the first preamble identifier is different from the second preamble identifier; sending a first random access preamble corresponding to the first preamble identifier and a second random access preamble corresponding to the second preamble identifier; and receiving a RAR, the RAR being associated with one of the first random access procedure or the second random access procedure based on the preamble identifier indication included in the RAR.

[0007] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a first control message in a first PDCCH command that triggers a first random access procedure, the first control message indicating a first preamble identifier associated with the first random access procedure; receive a second control message in a second PDCCH command that triggers a second random access procedure during the first random access procedure, the second control message indicating a second preamble identifier associated with the second random access procedure, wherein the first preamble identifier is different from the second preamble identifier; send a first random access preamble corresponding to the first preamble identifier and a second random access preamble corresponding to the second preamble identifier; and receive a RAR that is associated with one of the first random access procedure or the second random access procedure based on the preamble identifier indication included in the RAR.

[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include: a means for receiving a first control message in a first PDCCH command triggering a first random access procedure, the first control message indicating a first preamble identifier associated with the first random access procedure; a means for receiving a second control message in a second PDCCH command triggering a second random access procedure during the first random access procedure, the second control message indicating a second preamble identifier associated with the second random access procedure, wherein the first preamble identifier is different from the second preamble identifier; a means for sending a first random access preamble corresponding to the first preamble identifier and a second random access preamble corresponding to the second preamble identifier; and a means for receiving a RAR, the RAR being associated with one of the first random access procedure or the second random access procedure based on the preamble identifier indication included in the RAR.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive a first control message in a first PDCCH order triggering a first random access procedure, the first control message indicating a first preamble identifier associated with the first random access procedure; receive a second control message in a second PDCCH order triggering a second random access procedure during the first random access procedure, the second control message indicating a second preamble identifier associated with the second random access procedure, wherein the first preamble identifier is different from the second preamble identifier; send a first random access preamble corresponding to the first preamble identifier and a second random access preamble corresponding to the second preamble identifier; and receive a RAR, the RAR being associated with one of the first random access procedure or the second random access procedure based on the preamble identifier indication included in the RAR.

[0010] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for monitoring the RAR associated with the first random access procedure, and monitoring the RAR associated with the second random access procedure.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a RAR may include operations, features, components, or instructions for: receiving the RAR, which is associated with a first random access procedure based on a preamble identifier indicating that it corresponds to a first preamble identifier; and receiving the RAR, which is associated with a second random access procedure based on a preamble identifier indicating that it corresponds to a second preamble identifier.

[0012] 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 PDSCH associated with a first random access procedure or a second random access procedure based on a preamble identifier indication included in a RAR, wherein the RAR includes the PDSCH.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a first control message and a second control message may include operations, features, components, or instructions for: receiving a first PDCCH command from a first network entity; and receiving a second PDCCH command from a second network entity different from the first network entity.

[0014] A method for wireless communication at a UE is described. The method may include: sending a first random access preamble corresponding to a first preamble identifier as part of a first random access procedure; sending a second random access preamble corresponding to a second preamble identifier during the first random access procedure, the second random access preamble associated with the second random access procedure; and receiving a RAR, the RAR being associated with one of the first random access procedure or the second random access procedure based on an indication of a timing advance group in the RAR.

[0015] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: send a first random access preamble corresponding to a first preamble identifier as part of a first random access procedure; send a second random access preamble corresponding to a second preamble identifier during the first random access procedure, the second random access preamble being associated with a second random access procedure; and receive a RAR, the RAR being associated with one of the first random access procedure or the second random access procedure based on an indication of a timing advance group in the RAR.

[0016] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for sending a first random access preamble corresponding to a first preamble identifier as part of a first random access procedure; means for sending a second random access preamble corresponding to a second preamble identifier during the first random access procedure, the second random access preamble associated with the second random access procedure; and means for receiving a RAR, the RAR associated with one of the first random access procedure or the second random access procedure based on an indication of a timing advance group in the RAR.

[0017] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: send a first random access preamble corresponding to a first preamble identifier as part of a first random access procedure; send a second random access preamble corresponding to a second preamble identifier during the first random access procedure, the second random access preamble associated with the second random access procedure; and receive a RAR, the RAR being associated with one of the first random access procedure or the second random access procedure based on an indication of a timing advance group in the RAR.

[0018] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for monitoring the RAR associated with the first random access procedure, and monitoring the RAR associated with the second random access procedure.

[0019] 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 control message in a first PDCCH command associated with the first random access procedure, the first control message indicating a first preamble identifier; and receiving a second control message in a second PDCCH command associated with the second random access procedure, the second control message indicating a second preamble identifier.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the first control message and the second control message may include operations, features, components, or instructions for: receiving the first control message in the first PDCCH command from a first network entity; and receiving the second control message in the second PDCCH command from a second network entity different from the first network entity.

[0021] 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 PDSCH associated with the first random access procedure or the second random access procedure based on the indication of the timing advance group included in the RAR, wherein the RAR includes the PDSCH.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the RAR may include operations, features, components, or instructions for: receiving a timing advance group identifier in a field of the RAR, wherein the indication of the timing advance group may be based on the timing advance group identifier.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the RAR may include operations, features, components, or instructions for receiving the indication of the timing advance group in one or more fields of the RAR, wherein the one or more fields include a reserved field and a CSI request field.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the RAR may include operations, features, components, or instructions for: receiving a PDCCH scrambled by a random access temporary identifier, wherein the indication of the timing advance group may be based on the random access temporary identifier, and wherein the RAR includes the PDCCH scrambled by the random access temporary identifier.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the PDCCH scrambled by the random access temporary identifier may include operations, features, components, or instructions for receiving an indication of a CORESET pool index in the PDCCH scrambled by the random access temporary identifier, wherein the CORESET pool index may be based on the random access temporary identifier and may be associated with the first random access procedure or the second random access procedure.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the PDCCH scrambled by the random access temporary identifier may include operations, features, components, or instructions for receiving an indication of a timing advance group identifier in the PDCCH scrambled by the random access temporary identifier, wherein the timing advance group identifier may be based on the random access temporary identifier and may be associated with the first random access procedure or the second random access procedure.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the RAR may include operations, features, components, or instructions for receiving the indication of the timing advance group in one or more reserved bits in a PDCCH scrambled by a random access temporary identifier, wherein the RAR includes the PDCCH.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the RAR may include operations, features, components, or instructions for receiving an indication of a CORESET pool index in one or more reserved bits in a PDCCH scrambled by a random access temporary identifier, wherein the CORESET pool index may be associated with the timing advance group, and wherein the RAR includes the PDCCH.

[0029] A method for wireless communication at a UE is described. The method may include: receiving a radio resource control message indicating that a component carrier is associated with both a first timing advance group and a second timing advance group; receiving a first control message triggering a first random access procedure via a first PDCCH command, wherein the first PDCCH command is associated with a first CORESET pool index; receiving a second control message triggering a second random access procedure via a second PDCCH command and during the first random access procedure, wherein the second PDCCH command is associated with a second CORESET pool index; sending a first random access preamble via a first random access opportunity on the component carrier and sending a second random access preamble via a second random access opportunity on the component carrier; and receiving a RAR including an indication of a timing advance group, wherein the RAR is associated with the first random access procedure based on the timing advance group corresponding to the first CORESET pool index or the first random access opportunity, or the RAR is associated with the second random access procedure based on the timing advance group corresponding to the second CORESET pool index or the second random access opportunity.

[0030] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a radio resource control message indicating that a component carrier is associated with both a first timing advance group and a second timing advance group; receive a first control message triggering a first random access procedure via a first PDCCH command, wherein the first PDCCH command is associated with a first CORESET pool index; receive a second control message triggering a second random access procedure via a second PDCCH command and during the first random access procedure, wherein the second PDCCH command is associated with a second CORESET pool index; send a first random access preamble via a first random access opportunity on the component carrier and send a second random access preamble via a second random access opportunity on the component carrier; and receive a RAR including an indication of a timing advance group, wherein the RAR is associated with the first random access procedure based on the timing advance group corresponding to the first CORESET pool index or the first random access opportunity, or the RAR is associated with the second random access procedure based on the timing advance group corresponding to the second CORESET pool index or the second random access opportunity.

[0031] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving a radio resource control message indicating that a component carrier is associated with both a first timing advance group and a second timing advance group; means for receiving a first control message triggering a first random access procedure via a first PDCCH command, wherein the first PDCCH command is associated with a first CORESET pool index; means for receiving a second control message triggering a second random access procedure via a second PDCCH command and during the first random access procedure, wherein the second PDCCH command is associated with a second CORESET pool index; means for sending a first random access preamble via a first random access opportunity on a component carrier and sending a second random access preamble via a second random access opportunity on the component carrier; and means for receiving a RAR including an indication of a timing advance group, wherein the RAR is associated with the first random access procedure based on the timing advance group corresponding to the first CORESET pool index or the first random access opportunity, or the RAR is associated with the second random access procedure based on the timing advance group corresponding to the second CORESET pool index or the second random access opportunity.

[0032] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive a radio resource control message indicating that a component carrier is associated with both a first timing advance group and a second timing advance group; receive a first control message triggering a first random access procedure via a first PDCCH command, wherein the first PDCCH command is associated with a first CORESET pool index; receive a second control message triggering a second random access procedure via a second PDCCH command and during the first random access procedure, wherein the second PDCCH command is associated with a second CORESET pool index; send a first random access preamble via a first random access opportunity on the component carrier and send a second random access preamble via a second random access opportunity on the component carrier; and receive a RAR including an indication of a timing advance group, wherein the RAR is associated with the first random access procedure based on the timing advance group corresponding to the first CORESET pool index or the first random access opportunity, or the RAR is associated with the second random access procedure based on the timing advance group corresponding to the second CORESET pool index or the second random access opportunity.

[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: determining that the first random access procedure may be associated with the timing advance group based on the first PDCCH command being associated with the first CORESET pool index and the first CORESET pool index being associated with the timing advance group, or the first random access opportunity being associated with the timing advance group; and determining that the second random access procedure may be associated with the timing advance group based on the second PDCCH command being associated with the second CORESET pool index and the second CORESET pool index being associated with the timing advance group, or the second random access opportunity being associated with the timing advance group.

[0034] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for monitoring the RAR associated with the first random access procedure, and monitoring the RAR associated with the second random access procedure.

[0035] A method of wireless communication at a network entity is described. The method may include: receiving a first control message indicating a first random access procedure for a UE; receiving a second control message indicating a second random access procedure during the first random access procedure, the second random access procedure being for the UE; and sending a RAR associated with one of the first random access procedure or the second random access procedure to the UE, the RAR including an indication of the one of the first random access procedure or the second random access procedure.

[0036] 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: receive a first control message indicating a first random access procedure for a UE; receive a second control message indicating a second random access procedure during the first random access procedure, the second random access procedure being for the UE; and send a RAR associated with one of the first random access procedure or the second random access procedure to the UE, the RAR including an indication of the first random access procedure or the second random access procedure.

[0037] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for receiving a first control message indicating a first random access procedure for a UE; means for receiving a second control message indicating a second random access procedure during the first random access procedure, the second random access procedure being for the UE; and means for sending a RAR associated with one of the first random access procedure or the second random access procedure to the UE, the RAR including an indication of the one of the first random access procedure or the second random access procedure.

[0038] 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: receive a first control message indicating a first random access procedure for a UE; receive a second control message indicating a second random access procedure during the first random access procedure, the second random access procedure being for the UE; and send a RAR associated with one of the first random access procedure or the second random access procedure to the UE, the RAR including an indication of the first random access procedure or the second random access procedure.

[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the RAR may include operations, features, components, or instructions for sending a preamble identifier associated with the first random access procedure or the second random access procedure, wherein the indication included in the RAR may be based on the preamble identifier.

[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the RAR may include operations, features, components, or instructions for sending an indication of a timing advance group associated with the first random access procedure or the second random access procedure, wherein the indication included in the RAR may be the indication of the timing advance group.

[0041] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the indication of the timing advance group may include operations, features, components, or instructions for sending a timing advance group identifier in a field of the RAR, wherein the indication of the timing advance group may be based on the timing advance group identifier.

[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the indication of the timing advance group may include operations, features, components, or instructions for sending the indication of the timing advance group in one or more fields of the RAR, wherein the one or more fields include a reserved field, a CSI request field, or both.

[0043] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the indication of the timing advance group may include operations, features, components, or instructions for: sending a PDCCH scrambled by a random access temporary identifier, wherein the indication of the timing advance group may be based on the random access temporary identifier, and wherein the RAR includes the PDCCH scrambled by the random access temporary identifier.

[0044] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the PDCCH scrambled by the random access temporary identifier may include operations, features, components, or instructions for sending an indication of a CORESET pool index in the PDCCH scrambled by the random access temporary identifier, wherein the CORESET pool index may be based on the random access temporary identifier and may be associated with the first random access procedure or the second random access procedure.

[0045] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the PDCCH scrambled by the random access temporary identifier may include operations, features, components, or instructions for sending an indication of a timing advance group identifier in the PDCCH scrambled by the random access temporary identifier, wherein the timing advance group identifier may be based on the random access temporary identifier and may be associated with the first random access procedure or the second random access procedure.

[0046] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the indication of the timing advance group may include operations, features, components, or instructions for sending the indication of the timing advance group in one or more reserved bits in a PDCCH scrambled by a random access temporary identifier, wherein the RAR includes the PDCCH.

[0047] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the RAR may include operations, features, components, or instructions for sending an indication of a CORESET pool index in one or more bits in a PDCCH scrambled by a random access temporary identifier, wherein the RAR includes the PDCCH. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1 An example of a wireless communication system supporting RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is illustrated.

[0049] Figure 2An example of a wireless communication system supporting RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is illustrated.

[0050] Figure 3 An example of a wireless communication system supporting RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is illustrated.

[0051] Figure 4A and Figure 4B An example of a wireless communication system supporting RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is illustrated.

[0052] Figure 5 An example of a process flow supporting RAR enhancement for multiple RACH procedures in accordance with one or more aspects of the present disclosure is illustrated.

[0053] Figure 6 and Figure 7 A block diagram of an apparatus supporting RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is shown.

[0054] Figure 8 A block diagram of a communications manager supporting RAR enhancement for multiple RACH procedures in accordance with one or more aspects of the present disclosure is shown.

[0055] Fig. 9 A diagram of a system including a device supporting RAR enhancement for multiple RACH procedures in accordance with one or more aspects of the present disclosure is shown.

[0056] Fig.10 and Fig.11 A block diagram of an apparatus supporting RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is shown.

[0057] Fig.12 A block diagram of a communications manager supporting RAR enhancement for multiple RACH procedures in accordance with one or more aspects of the present disclosure is shown.

[0058] Fig.13 A diagram of a system including a device supporting RAR enhancement for multiple RACH procedures in accordance with one or more aspects of the present disclosure is shown.

[0059] Figures 14 to 17 A flow chart illustrating a method of supporting RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0060] Some wireless communication systems may support a random access channel (RACH) procedure. In the RACH procedure, a network entity may send a physical downlink control channel (PDCCH) command to a user equipment (UE), which allocates or assigns a random access preamble (e.g., a physical random access channel (PRACH)) identifier to the UE for a given RACH procedure triggered by the PDCCH command. The UE may send a random access preamble (e.g., a physical RACH (PRACH) preamble) associated with the random access preamble identifier. The UE may monitor for a random access response (RAR) from the network (e.g., another network entity), and the network may send a RAR including an indication of a random access preamble identifier (RAPID). The RAR may include a PDCCH scrambled by a random access temporary identifier (e.g., a random access radio network temporary identifier (RA-RNTI)) and a physical downlink shared channel (PDSCH). The UE may identify that the RAPID in the RAR corresponds to a random access preamble identifier associated with a random access preamble sent by the UE, and may forward the PDSCH to a higher layer at the UE (e.g., from the physical layer to the medium access control (MAC) layer), thereby completing the RACH procedure. However, in some cases, a second or subsequent RACH procedure may be triggered at the UE while a current RACH procedure is already in progress at the UE. In such cases, the UE may determine whether to continue the current RACH procedure and ignore the second RACH procedure or to stop the current RACH procedure and start the second RACH procedure. That is, the UE may not be able to perform multiple RACH procedures simultaneously (e.g., in parallel).

[0061] The techniques described herein may support a UE to perform multiple random access (e.g., RACH) procedures in parallel. In some cases, the UE may receive multiple PDCCH commands, each of which triggers a RACH procedure and each of which indicates a random access preamble identifier. In some cases, the random access preamble identifiers in each PDCCH command may be the same, while in some other cases, they may be different. The UE may send multiple random access preambles in response to multiple PDCCH commands, each of which is associated with a random access preamble identifier assigned by a corresponding PDCCH command. The UE may then monitor the RAR in response to the random access preamble, and may receive at least one RAR associated with a random access preamble identifier indicated by one of the PDCCH commands.

[0062] In some cases (e.g., when each PDCCH order indicates a unique random access preamble identifier), the UE may determine which RACH procedure corresponds to the RAR based on the RAPID in the RAR. For example, the UE may determine that the RAR corresponds to the corresponding RACH procedure based on the RAPID in the RAR corresponding to the random access preamble identifier associated with the corresponding RACH procedure.

[0063] Additionally or alternatively, the UE may determine which RACH procedure corresponds to the RAR based on an indication of a timing advance group. For example, the UE may receive a RAR including an indication of a timing advance group associated with a first component carrier, and the UE may determine that the RAR is associated with a RACH procedure that is also associated with the component carrier. In some cases, the timing advance group may be indicated by: a timing advance group indicator field in the RAR, a combination of a reserved field and a channel state information (CSI) request field in the RAR, a random access temporary identifier for scrambling a PDCCH in the RAR, one or more reserved bits in the RAR, or a control resource set (CORESET) pool index associated with the RAR.

[0064] Additionally or alternatively, the UE may determine that the timing advance group is associated with the RACH procedure based on a CORESET pool index associated with a PDCCH command or a RACH opportunity associated with a random access preamble. For example, the network entity sends a PDCCH command associated with a CORESET pool index that triggers a RACH procedure. The UE may determine that the CORESET pool index is associated with the timing advance group, and therefore determine that the timing advance group is associated with the RACH procedure triggered by the PDCCH command associated with the CORESET pool index.

[0065] Various aspects of the disclosure are first described in the context of a wireless communication system. Various aspects of the disclosure are then described in the context of a process flow. Various aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to RAR enhancement for multiple RACH procedures.

[0066] Figure 1 An example of a wireless communication system 100 supporting RAR enhancement for multiple RACH procedures 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).

[0067] 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, etc. 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).

[0068] 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 communicating with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

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

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

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

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

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

[0074] 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., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0075] 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 RAR enhancement for multiple RACH 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).

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

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

[0078] UE 115 and network entity 105 can communicate with each other wirelessly via one or more communication links 125 (e.g., access links) through one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a physical layer structure defined to support communication link 125. For example, a carrier for communication link 125 may include a portion of an RF spectrum band (e.g., 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-APro, 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 communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can 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 part (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send", "receive", or "communicate" when referring to the network entity 105 may refer to any part of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0079] 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 located 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 a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

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

[0081] 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 the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., the network entity 105, the UE 115, or both) may have a hardware configuration that supports communication over a particular carrier bandwidth, or may be configurable to support communication over one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate over a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

[0082] The signal waveform transmitted over 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 techniques, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a subcarrier resource, 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 the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device may be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources may improve the data rate or data integrity of communications with UE 115.

[0083] One or more parameter sets for a carrier may be supported, where the parameter set may include subcarrier spacing (Δf) 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.

[0084] The time interval of the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, T s =1 / (Δf max ·N f ) seconds sampling period, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. 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).

[0085] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, the time slot may be further divided into multiple micro time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating band.

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

[0087] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier using, for example, one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search a control region to obtain 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 .

[0088] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, 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., via a carrier), and may be associated with an identifier used to distinguish adjacent cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) within which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

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

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

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

[0092] 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). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication, and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0093] In some examples, a UE 115 may be able to communicate 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), and the one or more UEs may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside 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 other UE 115 in the group. In some examples, the network entity 105 may facilitate scheduling resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

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

[0095] 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, and these waves 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. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0096] The wireless communication system 100 may utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations in an unlicensed band may be combined with component carriers (e.g., LAA) operating in a licensed band based on a carrier aggregation configuration. Operations in an unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0097] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which 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 can 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 in different geographic locations. The network entity 105 may have an antenna array having a set of rows and columns of antenna ports that the network entity 105 can use to support beamforming for communication with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

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

[0099] The wireless communication system 100 may support RAR enhancement for multiple RACH procedures. For example, the UE 115 may receive multiple PDCCH commands, such as a first PDCCH command and a second PDCCH command, each PDCCH command triggering a corresponding RACH procedure, and each PDCCH command indicating a random access preamble identifier of the corresponding RACH procedure. The UE 115 may send a random access preamble in response to each PDCCH command, and each random access preamble may be associated with a random access preamble identifier allocated in the corresponding PDCCH command. In some cases, the UE 115 may receive a RAR and determine that the RAR is associated with the corresponding RACH procedure based on a random access preamble identifier indication (e.g., RAPID) in the RAR. For example, the RAR may include a RAPID corresponding to a random access preamble identifier associated with a random access preamble sent by the UE 115. Therefore, the UE 115 may determine that the RAR is associated with the random access preamble, and since the random access preamble is associated with the PDCCH order that triggers the RACH procedure, the UE may determine that the RAR is associated with the RACH procedure.

[0100] Additionally or alternatively, the UE 115 may determine which RACH procedure corresponds to the RAR based on an indication of the timing advance group. In some cases, the timing advance group may be indicated by: a timing advance group indicator field in the RAR, a combination of a reserved field and a CSI request field in the RAR, a random access temporary identifier used to scramble the PDCCH in the RAR, one or more reserved bits in the RAR, or a control resource set (CORESET) pool index associated with the RAR. Additionally, the UE may determine that the timing advance group is associated with the RACH procedure based on a CORESET pool index associated with a PDCCH order or a RACH opportunity associated with a random access preamble.

[0101] Figure 2 An example of a wireless communication system 200 that supports RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may implement aspects of the wireless communication system 100 or be implemented by these aspects. For example, the wireless communication system 200 may include a network entity 105-a, a network entity 105-b, a network entity 105-c, and a UE 115-a. The UE 115-a may represent a wireless communication system as described herein (including references Figure 1 ) is an example of a UE 115 as described herein. Network entity 105-a, network entity 105-b, and network entity 105-c may represent a network entity as described herein (including references Figure 1) is an example of a network entity 105 described in detail. In some cases, the UE 115-a may receive multiple PDCCH commands 205 that trigger multiple RACH procedures, and may perform multiple random access procedures simultaneously (e.g., in parallel).

[0102] Some wireless communication systems may support random access procedures (e.g., RACH procedures). For example, the network entity 105 may send a PDCCH command 205 to the UE 115, the PDCCH command including an indication of a random access preamble identifier (e.g., preamble index) associated with a first RACH procedure. In response, the UE 115 may send a random access preamble 210 (e.g., message (MSG) 1) corresponding to the random access preamble identifier associated with the first RACH procedure, and monitor for a response (e.g., RAR 215) during a response window (e.g., a time duration that may be configured via higher layer signaling, preconfigured, or dynamically indicated to the UE 115-a for a given RACH procedure).

[0103] In some cases, the UE 115 may fail to receive a RAR 215 (e.g., MSG2) including a random access preamble identifier indication (e.g., RAPID) corresponding to a random access preamble identifier associated with the random access preamble 210. In such cases, the UE 115 may consider the random access reception unsuccessful and increment the preamble transmission counter by one. In some cases, before retransmission of the PDCCH command 205 (e.g., due to random access reception failure), the UE 115 may change the spatial domain filter at the UE 115 and may suspend the power ramp counter associated with the first RACH procedure. In some other cases, before retransmission of the PDCCH command 205, the UE 115 may prohibit changing the spatial domain filter and may increment the power ramp counter by one. In some cases, the value of the preamble transmission counter may exceed a threshold value (e.g., the preamble transmission counter maximum value plus 1), and the UE 115 may consider the first RACH procedure unsuccessful.

[0104] In some examples, the UE 115 may receive a RAR 215 including a RAPID (e.g., in a MAC subpacket data unit (subPDU)) corresponding to a random access preamble identifier associated with the random access preamble 210. Additionally, the RAR 215 may include a PDSCH and a PDCCH scrambled by a random access radio network temporary identifier (RA-RNTI). In such a case, the UE 115 may decode the RAR 215 (e.g., the received transport block) and forward the PDSCH to a higher layer at the UE 115 (e.g., from the physical layer to the MAC layer). Additionally, the UE 115 may determine that the RAR 215 is successful (e.g., the first RACH procedure is successful) and apply the received timing advance command (e.g., from the RAR 215) to the network entity 105 (e.g., the serving cell in which the random access preamble 210 is sent).

[0105] In some cases, the UE 115 may receive a second PDCCH command 205 that triggers a second RACH procedure while the first RACH procedure is ongoing (e.g., during the first RACH procedure). In such cases, the UE 115 may determine whether to stop the first RACH procedure and execute (e.g., start) the second RACH procedure, or ignore the second RACH procedure and continue to execute the first RACH procedure. That is, the UE 115 may not be able to execute the first RACH procedure and the second RACH procedure (e.g., multiple RACH procedures) in parallel.

[0106] The techniques described herein may support RAR enhancement for multiple RACH procedures. In some cases, UE 115-a may receive a PDCCH command 205-a (e.g., a control message) from network entity 105-a that triggers a first RACH procedure (e.g., a random access procedure). In addition, the PDCCH command 205-a may indicate a first random access preamble identifier associated with the first RACH procedure (e.g., a physical random access channel (PRACH) preamble index). Additionally, UE 115-a may receive a PDCCH command 205-b (e.g., during the first random access procedure) from network entity 105-b that triggers a second RACH procedure. In addition, the PDCCH command 205-b may indicate a second random access preamble identifier associated with the second RACH procedure. In some cases, the first random access preamble identifier and the second random access preamble identifier may be the same, while in other cases, the first random access preamble identifier and the second random access preamble identifier may be different (e.g., unique).

[0107] In some cases, UE 115-a may send a random access preamble 210-a (e.g., a PRACH preamble) corresponding to a first random access preamble identifier to network entity 105-a, and send a random access preamble 210-b corresponding to a second random access preamble identifier to network entity 105-b. Additionally, UE 115-a may monitor RAR 215 from a network (such as network entity 105-c) during a response window (e.g., a configured monitoring window). In some cases, network entity 105-c may send RAR 215 to UE 115-a during the response window, and UE 115-a may determine, based on an indication in RAR 215, which RACH procedure (e.g., the first RACH procedure or the second RACH procedure) the RAR 215 is associated with (e.g., corresponds to).

[0108] In some cases (e.g., when the first random access preamble identifier and the second random access preamble identifier are different), UE 115-a may determine which random RACH RAR 215 corresponds to based on the RAPID (e.g., random access preamble identifier indication) in RAR 215, as described with respect to Figure 3 For example, the RAR 215 may include a RAPID corresponding to a first random access preamble identifier, and the UE 115-a may determine that the RAR 215 is associated with a first RACH procedure based on the RAPID corresponding to the first random access preamble. In another example, the RAR 215 may include a RAPID corresponding to a second random access preamble identifier, and the UE 115-a may determine that the RAR 215 is associated with a second RACH procedure based on the RAPID corresponding to the second random access preamble. In some cases, the UE 115-a may be configured such that the UE 115-a does not expect to receive multiple PDCCH commands 205 indicating the same random access preamble identifier (e.g., when a RACH procedure is already in progress).

[0109] Additionally or alternatively, UE 115-a may determine which RACH procedure RAR 215 corresponds to based on an indication of a timing advance group in RAR 215, such as with respect to Figure 4A and Figure 4B For example, RAR 215 may include an indication of a first timing advance group, and UE 115-a may determine that RAR 215 is associated with a first RACH procedure based on the indication of the first timing advance group. In another example, RAR 215 may include an indication of a second timing advance group, and UE 115-a may determine that RAR 215 is associated with a second RACH procedure based on the indication of the second timing advance group.

[0110] Additionally, the UE 115-a may determine that the timing advance group is associated with the corresponding RACH procedure based on the CORESET pool index of the CORESET 220 in which the PDCCH command 205 is received. For example, the RACH procedure may be associated with a timing advance group that is further associated with the CORESET pool index of the CORESET 220 in which the PDCCH command 205 triggering the RACH procedure is received. As an illustrative example, the UE 115-a may receive a PDCCH command 205-a triggering a first RACH procedure via a CORESET 220-a, the CORESET corresponding to a first CORESET pool index associated with a first timing advance group. Therefore, the UE 115-a may determine that the first RACH procedure is associated with the first timing advance group. In another example, the UE 115-a may receive a PDCCH command 205-b triggering a second RACH procedure via a CORESET 220-b, the CORESET corresponding to a second CORESET pool index associated with a second timing advance group. Thus, UE 115-a may determine that the second RACH procedure is associated with the second timing advance group.

[0111] Additionally or alternatively, the UE 115-a may determine that the timing advance group is associated with the corresponding RACH procedure based on the timing advance group of the network entity 105 (e.g., or component carrier or TRP) receiving the random access preamble 210. In some cases (e.g., when the network entity 105 is associated with a single timing advance group or is configured with a single timing advance group), the UE 115-a may determine that the RACH procedure is associated with a timing advance group that is further associated with the network entity 105 in which the random access preamble 210 is received. For example, the network entity 105-a may be associated with a first timing advance group. Additionally, the network entity 105-a may send a PDCCH command 205-a that triggers a first RACH procedure. The UE 115-a may send the random access preamble 210-a to the network entity 105-a during the first RACH procedure, and the UE 115-a may determine that the first RACH procedure is associated with the first timing advance group based on the network entity 105-a being associated with the first timing advance group.

[0112] In some other cases (e.g., when the network entity 105 is associated with or configured with multiple timing advance groups), the UE 115-a may determine that the RACH procedure is associated with the timing advance group based on the CORESET pool index of the CORESET 220 in which the PDCCH command 205 (e.g., random access opportunity) is received or the RACH opportunity indicated in the PDCCH command 205. For example, as previously described, the CORESET pool index of the CORESET 220 may be associated with the timing advance group, and the network entity 105 may trigger the RACH procedure via the PDCCH command 205 associated with the same CORESET pool index of the CORESET 220. Therefore, the RACH procedure may be associated with the timing advance group. Alternatively, the UE 115-a may determine that the RACH procedure is associated with the timing advance group based on the RACH opportunity (which may also be referred to as a random access opportunity) indicated in the PDCCH command 205 (e.g., or a synchronization signal block (SSB) index).

[0113] Figure 3 An example of a wireless communication system 300 that supports RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is illustrated. The communication scheme 300 may implement or be implemented by aspects of the wireless communication system 100 and the wireless communication system 200. For example, the wireless communication system 300 may include a network entity 105-d and a UE 115-b. The UE 115-b may represent a wireless communication system as described herein (including references Figure 1 ) as an example of a UE 115 as described herein. The network entity 105-d may represent an example of a UE 115 as described herein (including references Figure 1 ) is an example of a network entity 105 described in detail. In some cases, UE 115-b may receive a RAR 305 including a random access preamble identifier indication (e.g., RAPID 320) from network entity 105-d and may determine a random access procedure associated with RAR 305 based on the indication.

[0114] In some cases, UE 115-b may receive multiple PDCCH commands that each trigger a corresponding RACH procedure. In some cases, each PDCCH command may assign a random access preamble identifier (e.g., a preamble index) associated with the corresponding RACH procedure to UE 115-b. Additionally, UE 115-b may send multiple random access preambles (e.g., PRACH preambles), each of which corresponds to a random access preamble identifier indicated in the PDCCH command. For example, UE 115-b may receive a first PDCCH command that assigns a first random access preamble identifier associated with a first RACH procedure and a second PDCCH command that assigns a second random access preamble identifier associated with a second RACH procedure. In this way, UE 115-b may send a first random access preamble corresponding to the first random access preamble identifier and a second random access preamble corresponding to the second random access preamble identifier. Additionally, UE 115-b may receive RAR 305 in response to the first random access preamble or the second random access preamble.

[0115] In some cases, UE 115-b may be configured such that UE 115-b may not expect to receive multiple PDCCH commands that assign (e.g., indicate) the same random access preamble identifier (e.g., for parallel RACH procedures). For example, when UE 115-b is executing a first RACH procedure associated with a first PDCCH command that assigns a first random access preamble identifier, UE 115-b may not expect to receive a second PDCCH command associated with a second RACH procedure that assigns a second random access preamble identifier that is the same as the first random access preamble identifier. In this way, when UE 115-b is executing multiple RACH procedures in parallel, a given random access preamble identifier may be associated with a single RACH procedure (e.g., multiple RACH procedures may be supported when the PDCCH command that triggers the RACH procedure indicates different random access preamble identifiers).

[0116] In such cases, UE 115-b may determine that RAR 305 is associated with a corresponding RACH procedure based on the preamble identifier indication (e.g., RAPID 320) in RAR 305. For example, UE 115-b may receive RAR 305 including MAC subheader 310 and MAC RAR 315. MAC RAR 315 may include one or more reserved bit fields, a timing advance command field, an uplink grant field (indicated by UL grant), a temporary cell radio network temporary identifier (TC-RNTI) field, or any combination thereof. Additionally, MAC subheader 310 may include an extension (E) field, a type field (T), and a RAPID 320 field. In some cases, RAPID 320 may correspond to a random access preamble identifier associated with a random access preamble sent by UE 115-b. In such cases, UE 115 - b may determine that RAR 305 , and more specifically, the PDSCH of RAR 305 , corresponds to the RACH procedure associated with RAPID 320 .

[0117] For example, UE 115-b may receive a first PDCCH command indicating a first random access preamble identifier associated with a first RACH procedure and a second PDCCH command indicating a second random access preamble identifier associated with a second RACH procedure (e.g., triggered during the first RACH procedure), wherein the first random access preamble identifier and the second random access preamble identifier are different. UE 115-b may send a first random access preamble corresponding to the first random access preamble identifier and a second random access preamble corresponding to the second random access preamble identifier. UE 115-b may then receive RAR 305 including RAPID 320. In the first example, RAPID 320 may correspond to (e.g., indicate) the first random access preamble identifier, and UE 115-b may determine, based on RAPID 320, that RAR 305 corresponds to the first RACH procedure. In a second example, RAPID 320 may correspond to a second random access preamble identifier, and UE 115 - b may determine, based on RAPID 320 , that RAR 305 corresponds to a second random RACH.

[0118] Figure 4A An example of a wireless communication system 400-a that supports RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is illustrated. The wireless communication system 400-a may implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, and the wireless communication system 300. For example, the wireless communication system 400-a may include a network entity 105-e and a UE 115-c. The UE 115-c represents a wireless communication system as described herein (including references Figure 1 ) as an example of a UE 115 as described herein. The network entity 105-e may represent an example of a UE 115 as described herein (including references Figure 1 ) as described above. In some cases, the UE 115-c may receive a RAR 405-a including an indication of a timing advance group from the network entity 105-e, and may determine a RACH procedure associated with the RAR 405-a based on the indication of the timing advance group.

[0119] In some cases, the UE 115-c may receive multiple PDCCH commands that each trigger a corresponding RACH procedure. In some cases, each PDCCH command may assign a random access preamble identifier (e.g., a preamble index) associated with the corresponding RACH procedure to the UE 115-c. In some cases, the random access preamble identifier assigned by the multiple PDCCH commands may be the same random access preamble identifier (e.g., the UE 115-c may be configured such that the UE 115-c may support PDCCH commands indicating the same random access preamble for parallel RACH procedures), while in some other cases, each random access preamble identifier may be unique (e.g., different). Additionally, the UE 115-c may send multiple random access preambles (e.g., PRACH preambles), where each random access preamble corresponds to a random access preamble identifier indicated in the PDCCH command. The network entity 105 - e may send a RAR 405 - a including an indication of the timing advance group in response to one of the random access preambles sent by the UE 115 - c .

[0120] In some cases, the timing advance group may be indicated by a timing advance group indicator in a field in the RAR 405-a (e.g., a new MAC RAR 405-a). For example, the RAR 405-a may include a plurality of reserved fields (R), a timing advance command field, a UL grant field, and a temporary C-RNTI field. The RAR 405-a may also include a timing advance group field 410 (e.g., indicated by a TAG), which includes a timing advance group indicator for the RAR 405-a. The UE 115-c may identify the timing advance group indicator in the TAG field 410 and determine that the RAR 405-a corresponds to a corresponding RACH procedure based on the timing advance group indicator in the TAG field 410. In some cases, the UE 115-c may determine a relationship between the timing advance group indicated in the RAR 405-a and the corresponding RACH procedure, such as regarding Figure 2 described.

[0121] Figure 4BAn example of a wireless communication system 400-b that supports RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is illustrated. The wireless communication system 400-b may implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the wireless communication system 300, and the wireless communication system 400-a. For example, the wireless communication system 400-b may include a network entity 105-f and a UE 115-d. The UE 115-d may represent a wireless communication system as described herein (including references to Figure 1 ) as an example of a UE 115 as described herein. The network entity 105-f may represent an example of a UE 115 as described herein (including references Figure 1 ) is an example of a network entity 105 described in detail. In some cases, the UE 115-d receives a RAR 405-b including an indication of a timing advance group from the network entity 105-f, and may determine a RACH procedure associated with the RAR 405-b based on the indication of the timing advance group.

[0122] In some cases, UE 115-d may receive multiple PDCCH commands that each trigger a corresponding RACH procedure. In some cases, each PDCCH command may assign a random access preamble identifier (e.g., a preamble index) associated with the corresponding random access procedure to UE 115-d. In some cases, the random access preamble identifier assigned by multiple PDCCH commands may be the same random access preamble identifier (e.g., UE 115-d may be configured so that UE 115-d may support PDCCH commands indicating the same random access preamble for parallel RACH procedures), while in some other cases, each random access preamble identifier may be unique (e.g., different). Additionally, UE 115-d may send multiple random access preambles (e.g., PRACH preambles), each of which corresponds to a random access preamble identifier indicated in the PDCCH command. The network entity 105 - f may send a RAR 405 - b including an indication of a timing advance group in response to one of the random access preambles sent by the UE 115 - d .

[0123] In some cases, the network entity 105-f may use multiple fields in the RAR 405-b to indicate the timing advance group. For example, the RAR 405-b may include a reserved (R) field 415, a timing advance command field, an UL grant field 420, and a temporary C-RNTI field. In addition, the UL grant field 420 may include a frequency hopping flag field, a physical uplink shared channel (PUSCH) frequency resource allocation field, a PUSCH time resource allocation field, a modulation and coding scheme (MCS) field, a transmit power control (TPC) command field, a CSI request field 425, and a channel access CPtext field. In some cases, the network entity 105-f may indicate a timing advance group identifier associated with the timing advance group corresponding to the RAR 405-b in the R field 415 and the CSI request field 425 in the UL grant field 420 (e.g., a 1-bit R field 415 and a 1-bit CSI request field 425). That is, the RAR 405-b may correspond to a RACH procedure associated with the timing advance group indicated by the R field 415 and the CSI request field 425 (e.g., in combination). In some cases, the UE 115-d determines the relationship between the timing advance group indicated in the RAR 405-b and the corresponding RACH procedure, such as with respect to Figure 2 described.

[0124] In some cases, the network entity 105-f may indicate the timing advance group based on a random access temporary identifier (e.g., a random access radio network temporary identifier (RA-RNTI)) scrambled for a PDCCH (e.g., the PDCCH scheduling the PDSCH) in the RAR 405-b. For example, the random access temporary identifier may vary with a CORESET pool index (e.g., a CORESET pool index associated with a PDCCH command). As an illustrative example, the network entity 105-f may determine the random access temporary identifier according to Equation 1:

[0125]

[0126] where s id The index of the first symbol (eg, OFDM symbol) that may correspond to a random access opportunity (eg, PRACH opportunity, 0≤s id <14), t id The index of the first time slot of the random access opportunity in the system frame (eg, where the index used to determine t id The subcarrier spacing can be based on the value of μ, 0≤t id <80), f id It may correspond to the index of the random access opportunity in the frequency domain (eg, 0≤f id <8), ul carrier idCORESETpoolindex may correspond to the uplink carrier used for random access preamble transmission (eg, 0 for a normal uplink carrier and 1 for a supplementary uplink carrier), and CORESETpoolindex may correspond to the CORESET pool index associated with the random access procedure.

[0127] In this manner, the UE 115-d may identify the random access temporary identifier in the RAR 405-b and determine that the radio access temporary identifier is associated with a CORESET pool index (e.g., and CORESET) that is further associated with the corresponding RACH procedure. In another example, the random access temporary identifier may vary with a timing advance group identifier (e.g., a timing advance group associated with the random access procedure). As an illustrative example, the network entity 105-f may determine the random access temporary identifier according to Equation 2:

[0128] RA-RNTI=1+s id +14×t id +14×80×f id +14×80×8

[0129] ×ul carrier id +14×80×8×2×TAG id (2)

[0130] where s id The index of the first symbol (eg, OFDM symbol) that may correspond to a random access opportunity (eg, PRACH opportunity, 0≤s id <14), t id The index of the first time slot of the random access opportunity in the system frame (eg, where the index used to determine t id The subcarrier spacing can be based on the value of μ, 0≤t id <80), f id It may correspond to the index of the random access opportunity in the frequency domain (eg, 0≤f id <8), ul carrier id may correspond to the uplink carrier used for random access preamble transmission (eg, 0 for a normal uplink carrier and 1 for a supplementary uplink carrier), and TAG id May correspond to a timing advance group associated with a RACH procedure.

[0131] In this manner, the UE 115-d may identify the random access temporary identifier in the RAR 405-b and determine that the radio access temporary identifier is associated with a timing advance group that is further associated with a corresponding RACH procedure. In some cases, the UE 115-d may determine a relationship between the CORESET pool index or the timing advance group indicated by the random access temporary identifier in the RAR 405-b and the corresponding RACH procedure, such as with respect to Figure 2 described.

[0132] Additionally or alternatively, the network entity 105-f may indicate the timing advance group based on one or more reserved bits (e.g., a new field) in the PDCCH scrambled by the random access temporary identifier. For example, a value in the one or more reserved bits (e.g., a 1-bit first value) may indicate a CORESET pool index. Additionally, the CORESET pool index may be associated with a RACH procedure that may be associated with the RAR 405-b (e.g., the RAR 405-bPDSCH). That is, the UE 115-d may determine that the RAR 405-b is associated with the RACH procedure based on the value in the one or more reserved bits associated with the CORESET pool index. As an illustrative example, a value of 0 may correspond to a CORESET pool index of 0 (e.g., TRP 1), and a value of 1 may correspond to a CORESET pool index of 1 (e.g., TRP2). In another example, a value in the one or more reserved bits (e.g., 2 bits) may indicate a timing advance group. That is, each possible bit field value (e.g., 00, 01, 10, 11) may be associated with a timing advance group. Additionally, the timing advance group may be associated with a RACH procedure that may be associated with RAR 405-b (e.g., RAR 405-b PDSCH). That is, UE 115-d may determine that RAR 405-b is associated with the RACH procedure based on the value associated with the timing advance group in one or more reserved bits. As an illustrative example, a bit field index of 0 may correspond to a first timing advance group, a bit field index of 1 may correspond to a second timing advance group, a bit field index of 2 may correspond to a third timing advance group, and a bit field index of 3 may correspond to a fourth timing advance group. In some cases, UE 115-d may determine the relationship between the CORESET pool index or the timing advance group indicated via the random access temporary identifier in RAR 405-b and the corresponding RACH procedure, such as with respect to Figure 2 described.

[0133] Additionally or alternatively, UE 115-e may determine that RAR 405-b corresponds to a RACH procedure based on the CORESET pool index of the PDCCH scrambled by the random access temporary identifier in RAR 405-b (e.g., when the serving cell is configured with two CORESET pool indexes and the random access procedure is triggered for the serving cell). In some cases, UE 115-d may determine the relationship between the CORESET pool index of the PDCCH scrambled by the random access temporary identifier in RAR 405-b and the corresponding RACH procedure, such as with respect to Figure 2 described.

[0134] In some cases, UE 115-d may communicate the RAR PDSCH (e.g., PDSCH in RAR 405-b, transport block) to higher layers at the UE and may notify the higher layers that the RAR PDSCH is associated with a corresponding random access procedure.

[0135] Figure 5 An example of a process flow 500 for supporting RAR enhancement for multiple RACH procedures in accordance with one or more aspects of the present disclosure is illustrated. The process flow 500 may implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, the wireless communication system 300, and the wireless communication system 400. For example, the process flow 500 may include a network entity 105-g, a network entity 105-h, a network entity 105-j, and a UE 115-e. The UE 115-e may represent a wireless communication system as described herein (including references Figure 1 ) as an example of a UE 115 as described herein. The network entity 105-g, the network entity 105-h, and the network entity 105-j may represent a network entity as described herein (including references Figure 1 ) as described above. In some cases, the UE 115-e may receive a random first random access response from the network entity 105-g and may determine a random access procedure associated with the random access response based on an indication in the first random access response.

[0136] In some cases, at 505, the network entity 105-g (e.g., a network entity 105 not in communication with the UE 115-e) may receive a first control message from the network entity 105-h (e.g., a network entity 105 in communication with the UE 115-e) indicating a first random access (e.g., RACH) procedure for the UE 115-e. In some cases, the first control message may include an indication of a timing advance group or a random access preamble identifier associated with the first random access procedure.

[0137] In some cases, the network entity 105-g may receive a first control message from a network entity 105-j (e.g., a network entity 105 in communication with the UE 115-e) at 510, the first control message indicating a second random access procedure for the UE 115-e during the first random access procedure. In some cases, the second control message may include an indication of a timing advance group or a preamble identifier (e.g., a random access preamble identifier) ​​associated with the second RACH procedure.

[0138] In some cases, at 515, UE 115-e may receive a third control message (e.g., an RRC message) indicating that a component carrier (e.g., or a TRP) is associated with both the first timing advance group and the second timing advance group.

[0139] In some cases, at 520, the UE 115-e may receive a first PDCCH command (e.g., a fourth control message in the first PDCCH command) from the network entity 105-h that triggers a first random access procedure. The first PDCCH command may also indicate (e.g., allocate) a first preamble identifier associated with the first random access procedure. In some cases, the first PDCCH command may be associated with a first CORESET pool index.

[0140] In some cases, at 525, UE 115-e may receive a second PDCCH order (e.g., a fifth control message in the second PDCCH order) triggering a second random access procedure from network entity 105-j (e.g., a different network entity 105 than network entity 105-h). The second PDCCH order may also indicate (e.g., allocate) a second preamble identifier associated with the second random access procedure. In some cases, the second PDCCH order may be associated with a second CORESET pool index.

[0141] At 530, the UE 115-e may send a first random access preamble corresponding to the first preamble identifier and monitor the RAR associated with the first random access preamble. In some cases, the UE 115-e may send the first random access preamble via a first random access (e.g., RACH) opportunity.

[0142] At 535, the UE 115-e may send a second random access preamble corresponding to the second preamble identifier and monitor the RAR associated with the second random access preamble. In some cases, the UE 115-e may send the second random access preamble via a second random access opportunity.

[0143] At 540, the UE 115-e may receive a first RAR that is associated with the first random access procedure or the second random access procedure based at least in part on an indication included in the first random access response. In some cases, the first RAR may include a PDSCH, and the UE 115-e may receive the PDSCH that is associated with the first RAR or the second RAR based on the preamble identifier indication. Additionally, the UE 115-e may receive a PDCCH scrambled by a random access temporary identifier, wherein the first RAR includes the PDCCH scrambled by the random access temporary identifier.

[0144] In some cases, the indication may be a preamble identifier indication (e.g., RAPID). In some cases, the first RAR may be associated with a first random access procedure based on the preamble identifier indication corresponding to the first preamble identifier. In some other cases, the first RAR may be associated with a second random access procedure based on the preamble identifier indication corresponding to the second preamble identifier.

[0145] In some cases, the indication may be an indication of a timing advance group.In some cases, the UE 115-e may receive a timing advance group identifier in a field of the RAR, wherein the indication of the timing advance group is based on the timing advance group identifier.

[0146] In some cases, the UE 115-e may receive an indication of a timing advance group in one or more fields of the RAR, wherein the one or more fields include a reserved field and a CSI request field. In some cases, the indication of the timing advance group is based on a random access temporary identifier. For example, the UE 115-e may receive an indication of a third CORESET pool index in a PDCCH scrambled by a random access temporary identifier, wherein the third CORESET pool index is associated with a first random access procedure or a second random access procedure. In some cases, the third CORESET pool index is based on the random access temporary identifier. In another example, the UE 115-e may receive an indication of a timing advance group identifier in a PDCCH scrambled by a random access temporary identifier, wherein the timing advance group identifier is based on the random access temporary identifier and is associated with a first random access procedure or a second random access procedure. In some cases, the UE 115-e may receive an indication of a timing advance group in one or more reserved bits in a PDCCH scrambled by a random access temporary identifier.

[0147] In some cases, at 545, the UE 115-e may determine that the first random access procedure is associated with the timing advance group based on the first PDCCH order being associated with the first CORESET pool index and the first CORESET pool index being associated with the timing advance group, or the first random access opportunity being associated with the timing advance group. In some other cases, the UE 115-e may determine that the second random access procedure is associated with the timing advance group based on the second PDCCH order being associated with the second CORESET pool index and the second CORESET pool index being associated with the timing advance group, or the second random access opportunity being associated with the timing advance group.

[0148] Figure 6 A block diagram 600 of a device 605 supporting RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is shown. The device 605 may be an example of aspects of the UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0149] The receiver 610 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to RAR enhancement for multiple RACH procedures, data channels, information channels). The information may be communicated to other components of the device 605. The receiver 610 may utilize a single antenna or a collection of multiple antennas.

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

[0151] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of RAR enhancement for multiple RACH procedures as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

[0153] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, 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 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, or any combination of these or other programmable logic devices.

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

[0155] According to examples as disclosed herein, the communication manager 620 may support wireless communications at a UE. For example, the communication manager 620 may be configured to or otherwise support a component for receiving a first control message in a first PDCCH order triggering a first random access procedure, the first control message indicating a first preamble identifier associated with the first random access procedure. The communication manager 620 may be configured to or otherwise support a component for receiving a second control message in a second PDCCH order triggering a second random access procedure during the first random access procedure, the second control message indicating a second preamble identifier associated with the second random access procedure, wherein the first preamble identifier is different from the second preamble identifier. The communication manager 620 may be configured to or otherwise support a component for sending a first random access preamble corresponding to the first preamble identifier and a second random access preamble corresponding to the second preamble identifier. The communication manager 620 may be configured to or otherwise support a component for receiving a random access response, the random access response being associated with one of the first random access procedure or the second random access procedure based on the preamble identifier indication included in the random access response.

[0156] Additionally or alternatively, according to examples as disclosed herein, the communication manager 620 may support wireless communications at the UE. For example, the communication manager 620 may be configured to or otherwise support a component for sending a first random access preamble corresponding to a first preamble identifier as part of a first random access procedure. The communication manager 620 may be configured to or otherwise support a component for sending a second random access preamble corresponding to a second preamble identifier during the first random access procedure, the second random access preamble being associated with a second random access procedure. The communication manager 620 may be configured to or otherwise support a component for receiving a random access response, the random access response being associated with one of the first random access procedure or the second random access procedure based on an indication of a timing advance group in the random access response.

[0157] Additionally or alternatively, according to examples as disclosed herein, the communication manager 620 may support wireless communications at the UE. For example, the communication manager 620 may be configured to or otherwise support means for receiving an RRC message indicating that the component carrier is associated with both the first timing advance group and the second timing advance group. The communication manager 620 may be configured to or otherwise support means for receiving a first control message triggering a first random access procedure via a first PDCCH order, wherein the first PDCCH order is associated with a first CORESET pool index. The communication manager 620 may be configured to or otherwise support means for receiving a second control message triggering a second random access procedure via a second PDCCH order and during the first random access procedure, wherein the second PDCCH order is associated with a second CORESET pool index. The communication manager 620 may be configured to or otherwise support means for sending a first random access preamble via a first random access opportunity on the component carrier and sending a second random access preamble via a second random access opportunity on the component carrier. The communication manager 620 may be configured to or otherwise support means for receiving a random access response including an indication of a timing advance group, wherein the random access response is associated with a first random access procedure based on the timing advance group corresponding to a first CORESET pool index or a first random access opportunity, or the random access response is associated with a second random access procedure based on the timing advance group corresponding to a second CORESET pool index or a second random access opportunity.

[0158] By including or configuring the communication manager 620 according to the examples described herein, the device 605 (e.g., a processor controlling the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof or otherwise coupled thereto) can support techniques for RAR enhancement for multiple RACH procedures, which can result in reduced processing, reduced power consumption, and more efficient utilization of communication resources, among other advantages.

[0159] Figure 7 A block diagram 700 of a device 705 supporting RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0160] The receiver 710 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels related to RAR enhancement for multiple RACH procedures, data channels, information channels). The information may be communicated to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

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

[0162] The device 705 or its various components may be examples of components for performing various aspects of RAR enhancement for multiple RACH procedures as described herein. For example, the communication manager 720 may include a PDCCH command component 725, a random access preamble component 730, a random access response component 735, a timing advance group component 740, or any combination thereof. The communication manager 720 may be an example of various aspects of the communication manager 620 as described herein. In some examples, the communication manager 720 or its various components may be configured to use or otherwise cooperate with the receiver 710, the transmitter 715, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or be integrated with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0163] According to examples as disclosed herein, the communication manager 720 may support wireless communications at a UE. The PDCCH command component 725 may be configured to or otherwise support a component for receiving a first control message in a first PDCCH command that triggers a first random access procedure, the first control message indicating a first preamble identifier associated with the first random access procedure. The PDCCH command component 725 may be configured to or otherwise support a component for receiving a second control message in a second PDCCH command that triggers a second random access procedure during the first random access procedure, the second control message indicating a second preamble identifier associated with the second random access procedure, wherein the first preamble identifier is different from the second preamble identifier. The random access preamble component 730 may be configured to or otherwise support a component for sending a first random access preamble corresponding to the first preamble identifier and a second random access preamble corresponding to the second preamble identifier. The random access response component 735 may be configured to or otherwise support means for receiving a random access response associated with one of the first random access procedure or the second random access procedure based on a preamble identifier indication included in the random access response.

[0164] Additionally or alternatively, according to examples as disclosed herein, the communication manager 720 may support wireless communications at the UE. The random access preamble component 730 may be configured to or otherwise support a means for sending a first random access preamble corresponding to a first preamble identifier as part of a first random access procedure. The random access preamble component 730 may be configured to or otherwise support a means for sending a second random access preamble corresponding to a second preamble identifier during the first random access procedure, the second random access preamble being associated with a second random access procedure. The random access response component 735 may be configured to or otherwise support a means for receiving a random access response, the random access response being associated with one of the first random access procedure or the second random access procedure based on an indication of a timing advance group in the random access response.

[0165] Additionally or alternatively, according to examples as disclosed herein, the communication manager 720 may support wireless communications at the UE. The timing advance group component 740 may be configured to or otherwise support means for receiving an RRC message indicating that a component carrier is associated with both a first timing advance group and a second timing advance group. The PDCCH command component 725 may be configured to or otherwise support means for receiving a first control message triggering a first random access procedure via a first PDCCH command, wherein the first PDCCH command is associated with a first CORESET pool index. The PDCCH command component 725 may be configured to or otherwise support means for receiving a second control message triggering a second random access procedure via a second PDCCH command and during the first random access procedure, wherein the second PDCCH command is associated with a second CORESET pool index. The random access preamble component 730 may be configured to or otherwise support means for sending a first random access preamble via a first random access opportunity on a component carrier and sending a second random access preamble via a second random access opportunity on a component carrier. The random access response component 735 may be configured to or otherwise support means for receiving a random access response including an indication of a timing advance group, wherein the random access response is associated with a first random access procedure based on the timing advance group corresponding to a first CORESET pool index or a first random access opportunity, or the random access response is associated with a second random access procedure based on the timing advance group corresponding to a second CORESET pool index or a second random access opportunity.

[0166] Figure 8 A block diagram 800 of a communication manager 820 supporting RAR enhancement for multiple RACH procedures in accordance with one or more aspects of the present disclosure is shown. The communication manager 820 may be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of means for performing various aspects of RAR enhancement for multiple RACH procedures as described herein. For example, the communication manager 820 may include a PDCCH command component 825, a random access preamble component 830, a random access response component 835, a timing advance group component 840, a monitoring component 845, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0167] According to examples as disclosed herein, the communication manager 820 may support wireless communications at the UE. The PDCCH command component 825 may be configured to or otherwise support a component for receiving a first control message in a first PDCCH command that triggers a first random access procedure, the first control message indicating a first preamble identifier associated with the first random access procedure. In some examples, the PDCCH command component 825 may be configured to or otherwise support a component for receiving a second control message in a second PDCCH command that triggers a second random access procedure during the first random access procedure, the second control message indicating a second preamble identifier associated with the second random access procedure, wherein the first preamble identifier is different from the second preamble identifier. The random access preamble component 830 may be configured to or otherwise support a component for sending a first random access preamble corresponding to the first preamble identifier and a second random access preamble corresponding to the second preamble identifier. The random access response component 835 may be configured to or otherwise support means for receiving a random access response associated with one of the first random access procedure or the second random access procedure based on a preamble identifier indication included in the random access response.

[0168] In some examples, monitoring component 845 can be configured or otherwise support means for monitoring random access responses associated with the first random access procedure. In some examples, monitoring component 845 can be configured or otherwise support means for monitoring random access responses associated with the second random access procedure.

[0169] In some examples, to support receiving a random access response, the random access response component 835 may be configured to or otherwise support means for receiving a random access response associated with a first random access procedure based on the preamble identifier indicating corresponding to the first preamble identifier. In some examples, to support receiving a random access response, the random access response component 835 may be configured to or otherwise support means for receiving a random access response associated with a second random access procedure based on the preamble identifier indicating corresponding to the second preamble identifier.

[0170] In some examples, the random access response component 835 may be configured to or otherwise support components for receiving a PDSCH associated with a first random access procedure or a second random access procedure based on a preamble identifier indication included in a random access response, wherein the random access response includes the PDSCH.

[0171] In some examples, to support receiving the first control message and the second control message, the PDCCH command component 825 can be configured to or otherwise support means for receiving the first PDCCH command from the first network entity. In some examples, to support receiving the first control message and the second control message, the PDCCH command component 825 can be configured to or otherwise support means for receiving the second PDCCH command from a second network entity different from the first network entity.

[0172] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communications at the UE. In some examples, the random access preamble component 830 may be configured to or otherwise support a component for sending a first random access preamble corresponding to a first preamble identifier as part of a first random access procedure. In some examples, the random access preamble component 830 may be configured to or otherwise support a component for sending a second random access preamble corresponding to a second preamble identifier during a first random access procedure, the second random access preamble being associated with a second random access procedure. In some examples, the random access response component 835 may be configured to or otherwise support a component for receiving a random access response, the random access response being associated with one of the first random access procedure or the second random access procedure based on an indication of a timing advance group in the random access response.

[0173] In some examples, monitoring component 845 can be configured or otherwise support means for monitoring random access responses associated with the first random access procedure. In some examples, monitoring component 845 can be configured or otherwise support means for monitoring random access responses associated with the second random access procedure.

[0174] In some examples, the PDCCH order component 825 may be configured to or otherwise support means for receiving a first control message in a first PDCCH order associated with a first random access procedure, the first control message indicating a first preamble identifier. In some examples, the PDCCH order component 825 may be configured to or otherwise support means for receiving a second control message in a second PDCCH order associated with a second random access procedure, the second control message indicating a second preamble identifier.

[0175] In some examples, to support receiving the first control message and the second control message, the PDCCH order component 825 can be configured to or otherwise support means for receiving the first control message in a first PDCCH order from the first network entity. In some examples, to support receiving the first control message and the second control message, the PDCCH order component 825 can be configured to or otherwise support means for receiving the second control message in a second PDCCH order from a second network entity different from the first network entity.

[0176] In some examples, the random access response component 835 may be configured to or otherwise support components for receiving a PDSCH associated with a first random access procedure or a second random access procedure based on an indication of a timing advance group included in a random access response, wherein the random access response includes the PDSCH.

[0177] In some examples, to support receiving a random access response, the timing advance group component 840 may be configured or otherwise support means for receiving a timing advance group identifier in a field of the random access response, wherein the indication of the timing advance group is based on the timing advance group identifier.

[0178] In some examples, to support receiving a random access response, the timing advance group component 840 may be configured to or otherwise support components for receiving an indication of a timing advance group in one or more fields of a random access response, wherein the one or more fields include a reserved field and a CSI request field.

[0179] In some examples, to support receiving a random access response, the timing advance group component 840 may be configured to or otherwise support means for receiving a PDCCH scrambled by a random access temporary identifier, wherein an indication of the timing advance group is based on the random access temporary identifier, and wherein the random access response includes the PDCCH scrambled by the random access temporary identifier.

[0180] In some examples, to support receiving a PDCCH scrambled by a random access temporary identifier, the timing advance group component 840 may be configured to or otherwise support means for receiving an indication of a CORESET pool index in a PDCCH scrambled by a random access temporary identifier, wherein the CORESET pool index is based on the random access temporary identifier and is associated with a first random access procedure or a second random access procedure.

[0181] In some examples, to support receiving a PDCCH scrambled by a random access temporary identifier, the timing advance group component 840 may be configured to or otherwise support a component for receiving an indication of a timing advance group identifier in a PDCCH scrambled by a random access temporary identifier, wherein the timing advance group identifier is based on the random access temporary identifier and is associated with the first random access procedure or the second random access procedure.

[0182] In some examples, to support receiving a random access response, the timing advance group component 840 may be configured to or otherwise support means for receiving an indication of a timing advance group in one or more reserved bits in a PDCCH scrambled by a random access temporary identifier, wherein the random access response includes the PDCCH.

[0183] In some examples, to support receiving a random access response, the timing advance group component 840 may be configured to or otherwise support means for receiving an indication of a CORESET pool index in one or more reserved bits in a PDCCH scrambled by a random access temporary identifier, wherein the CORESET pool index is associated with a timing advance group, and wherein the random access response includes the PDCCH.

[0184] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communications at the UE. The timing advance group component 840 may be configured to or otherwise support means for receiving an RRC message indicating that the component carrier is associated with both the first timing advance group and the second timing advance group. In some examples, the PDCCH command component 825 may be configured to or otherwise support means for receiving a first control message triggering a first random access procedure via a first PDCCH command, wherein the first PDCCH command is associated with a first CORESET pool index. In some examples, the PDCCH command component 825 may be configured to or otherwise support means for receiving a second control message triggering a second random access procedure via a second PDCCH command and during the first random access procedure, wherein the second PDCCH command is associated with a second CORESET pool index. In some examples, the random access preamble component 830 may be configured to or otherwise support means for sending a first random access preamble via a first random access opportunity on a component carrier and sending a second random access preamble via a second random access opportunity on a component carrier. In some examples, the random access response component 835 may be configured to or otherwise support a component for receiving a random access response including an indication of a timing advance group, wherein the random access response is associated with a first random access procedure based on the timing advance group corresponding to a first CORESET pool index or a first random access opportunity, or the random access response is associated with a second random access procedure based on the timing advance group corresponding to a second CORESET pool index or a second random access opportunity.

[0185] In some examples, the timing advance group component 840 may be configured to or otherwise support means for determining that a first random access procedure is associated with the timing advance group based on the first PDCCH command being associated with the first CORESET pool index and the first CORESET pool index being associated with the timing advance group, or the first random access opportunity being associated with the timing advance group. In some examples, the timing advance group component 840 may be configured to or otherwise support means for determining that a second random access procedure is associated with the timing advance group based on the second PDCCH command being associated with the second CORESET pool index and the second CORESET pool index being associated with the timing advance group, or the second random access opportunity being associated with the timing advance group.

[0186] In some examples, random access response component 835 may be configured or otherwise support means for monitoring random access responses associated with a first random access procedure. In some examples, random access response component 835 may be configured or otherwise support means for monitoring random access responses associated with a second random access procedure.

[0187] Fig. 9 A diagram of a system 900 including a device 905 supporting RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is shown. The device 905 may be an example of a device 605, a device 705, or a UE 115 as described herein, or include components thereof. The device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 905 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, a code 935, and a processor 940. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 945).

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

[0189] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 915 may communicate bidirectionally via one or more antennas 925, a wired link, or a wireless link, as described herein. For example, the transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 915 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 925 for transmission; and demodulating packets received from one or more antennas 925. The transceiver 915 or the transceiver 915 and one or more antennas 925 may be examples of transmitters 615, transmitters 715, receivers 610, receivers 710, or any combination thereof or components thereof as described herein.

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

[0191] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 940 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 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks that support RAR enhancement for multiple RACH procedures). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to the processor 940, and the processor 940 and the memory 930 are configured to perform the various functions described herein.

[0192] According to the examples disclosed herein, the communication manager 920 may support wireless communication at the UE. For example, the communication manager 920 may be configured to or otherwise support a component for receiving a first control message in a first PDCCH order triggering a first random access procedure, the first control message indicating a first preamble identifier associated with the first random access procedure. The communication manager 920 may be configured to or otherwise support a component for receiving a second control message in a second PDCCH order triggering a second random access procedure during the first random access procedure, the second control message indicating a second preamble identifier associated with the second random access procedure, wherein the first preamble identifier is different from the second preamble identifier. The communication manager 920 may be configured to or otherwise support a component for sending a first random access preamble corresponding to the first preamble identifier and a second random access preamble corresponding to the second preamble identifier. The communication manager 920 may be configured to or otherwise support a component for receiving a random access response, the random access response being associated with one of the first random access procedure or the second random access procedure based on the preamble identifier indication included in the random access response.

[0193] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at the UE. For example, the communication manager 920 may be configured to or otherwise support a component for sending a first random access preamble corresponding to a first preamble identifier as part of a first random access procedure. The communication manager 920 may be configured to or otherwise support a component for sending a second random access preamble corresponding to a second preamble identifier during the first random access procedure, the second random access preamble being associated with the second random access procedure. The communication manager 920 may be configured to or otherwise support a component for receiving a random access response, the random access response being associated with one of the first random access procedure or the second random access procedure based on an indication of a timing advance group in the random access response.

[0194] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communications at the UE. For example, the communication manager 920 may be configured to or otherwise support a means for receiving an RRC message indicating that a component carrier is associated with both a first timing advance group and a second timing advance group. The communication manager 920 may be configured to or otherwise support a means for receiving a first control message triggering a first random access procedure via a first PDCCH order, wherein the first PDCCH order is associated with a first CORESET pool index. The communication manager 920 may be configured to or otherwise support a means for receiving a second control message triggering a second random access procedure via a second PDCCH order and during the first random access procedure, wherein the second PDCCH order is associated with a second CORESET pool index. The communication manager 920 may be configured to or otherwise support a means for sending a first random access preamble via a first random access opportunity on a component carrier and sending a second random access preamble via a second random access opportunity on a component carrier. The communication manager 920 may be configured to or otherwise support means for receiving a random access response including an indication of a timing advance group, wherein the random access response is associated with a first random access procedure based on the timing advance group corresponding to a first CORESET pool index or a first random access opportunity, or the random access response is associated with a second random access procedure based on the timing advance group corresponding to a second CORESET pool index or a second random access opportunity.

[0195] By including or configuring the communication manager 920 according to the examples described herein, the device 905 can support RAR enhanced techniques for multiple RACH procedures, which can result in improved communication reliability, reduced latency, an improved user experience associated with reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, and improved utilization of processing power, among other advantages.

[0196] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 915, one or more antennas 925, or any combination thereof. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions that are executable by the processor 940 to cause the device 905 to perform various aspects of RAR enhancement for multiple RACH procedures as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0197] Fig.10 A block diagram 1000 of a device 1005 supporting RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

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

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

[0200] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of RAR enhancement for multiple RACH procedures as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

[0202] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, 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 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, or any combination of these or other programmable logic devices.

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

[0204] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a network entity. For example, the communication manager 1020 may be configured to or otherwise support a component for receiving a first control message indicating a first random access procedure for a UE. The communication manager 1020 may be configured to or otherwise support a component for receiving a second control message indicating a second random access procedure during a first random access procedure, the second random access procedure being for the UE. The communication manager 1020 may be configured to or otherwise support a component for sending a random access response associated with one of the first random access procedure or the second random access procedure to the UE, the random access response including an indication of one of the first random access procedure or the second random access procedure.

[0205] By including or configuring the communication manager 1020 according to the examples described herein, the device 1005 (e.g., a processor controlling the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof or otherwise coupled thereto) can support RAR enhanced techniques for multiple RACH procedures, which can result in reduced processing, reduced power consumption, and more efficient utilization of communication resources, among other advantages.

[0206] Fig.11 A block diagram 1100 of a device 1105 supporting RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or network entity 105 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).

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

[0208] The transmitter 1115 may provide means for outputting (e.g., sending, providing, communicating, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 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 1115 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by sending signals via one or more wired (e.g., electrical, optical fiber) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0209] The device 1105 or its various components may be examples of means for performing various aspects of RAR enhancement for multiple RACH procedures as described herein. For example, the communication manager 1120 may include a random access procedure component 1125, a random access response component 1130, or any combination thereof. The communication manager 1120 may be an example of various aspects of the communication manager 1020 as described herein. In some examples, the communication manager 1120 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 1110, the transmitter 1115, or both. For example, the communication manager 1120 may receive information from the receiver 1110, transmit information to the transmitter 1115, or be integrated with the receiver 1110, the transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0210] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. The random access procedure component 1125 may be configured to or otherwise support a means for receiving a first control message indicating a first random access procedure for the UE. The random access procedure component 1125 may be configured to or otherwise support a means for receiving a second control message indicating a second random access procedure during the first random access procedure, the second random access procedure being for the UE. The random access response component 1130 may be configured to or otherwise support a means for sending a random access response associated with one of the first random access procedure or the second random access procedure to the UE, the random access response including an indication of one of the first random access procedure or the second random access procedure.

[0211] Fig.12 A block diagram 1200 of a communication manager 1220 supporting RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is shown. The communication manager 1220 may be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components may be examples of means for performing various aspects of RAR enhancement for multiple RACH procedures as described herein. For example, the communication manager 1220 may include a random access procedure component 1225, a random access response component 1230, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0212] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. The random access procedure component 1225 may be configured to or otherwise support a component for receiving a first control message indicating a first random access procedure for the UE. In some examples, the random access procedure component 1225 may be configured to or otherwise support a component for receiving a second control message indicating a second random access procedure during the first random access procedure, the second random access procedure being for the UE. The random access response component 1230 may be configured to or otherwise support a component for sending a random access response associated with one of the first random access procedure or the second random access procedure to the UE, the random access response including an indication of one of the first random access procedure or the second random access procedure.

[0213] In some examples, to support sending a random access response, the random access response component 1230 may be configured to or otherwise support components for sending a preamble identifier associated with a first random access procedure or a second random access procedure, wherein the indication included in the random access response is based on the preamble identifier.

[0214] In some examples, to support sending a random access response, the random access response component 1230 may be configured as or otherwise support a component for sending an indication of a timing advance group associated with a first random access procedure or a second random access procedure, wherein the indication included in the random access response is an indication of a timing advance group.

[0215] In some examples, to support sending an indication of a timing advance group, the random access response component 1230 may be configured to or otherwise support a component for sending a timing advance group identifier in a field of a random access response, wherein the indication of the timing advance group is based on the timing advance group identifier.

[0216] In some examples, to support sending an indication of a timing advance group, the random access response component 1230 may be configured as or otherwise support a component for sending an indication of a timing advance group in one or more fields of a random access response, wherein the one or more fields include a reserved field, a CSI request field, or both.

[0217] In some examples, to support sending an indication of a timing advance group, the random access response component 1230 may be configured as or otherwise support a component for sending a PDCCH scrambled by a random access temporary identifier, wherein the indication of the timing advance group is based on the random access temporary identifier, and wherein the random access response includes the PDCCH scrambled by the random access temporary identifier.

[0218] In some examples, to support sending a PDCCH scrambled by a random access temporary identifier, the random access response component 1230 may be configured to or otherwise support a component for sending an indication of a CORESET pool index in a PDCCH scrambled by a random access temporary identifier, wherein the CORESET pool index is based on the random access temporary identifier and is associated with a first random access procedure or a second random access procedure.

[0219] In some examples, to support sending a PDCCH scrambled by a random access temporary identifier, the random access response component 1230 may be configured to or otherwise support a component for sending an indication of a timing advance group identifier in a PDCCH scrambled by a random access temporary identifier, wherein the timing advance group identifier is based on the random access temporary identifier and is associated with the first random access procedure or the second random access procedure.

[0220] In some examples, to support sending an indication of a timing advance group, the random access response component 1230 may be configured as or otherwise support components for sending an indication of a timing advance group in one or more reserved bits in a PDCCH scrambled by a random access temporary identifier, wherein the random access response includes the PDCCH.

[0221] In some examples, to support sending a random access response, the random access response component 1230 may be configured to or otherwise support means for sending an indication of a CORESET pool index in one or more bits in a PDCCH scrambled by a random access temporary identifier, wherein the random access response includes the PDCCH.

[0222] Fig.13 A diagram of a system 1300 including a device 1305 supporting RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a network entity 105 as described herein, or include components thereof. The device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1305 may include components that support output and acquisition of communications, such as a communication manager 1320, a transceiver 1310, an antenna 1315, a memory 1325, a code 1330, and a processor 1335. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

[0223] The transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315 that may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1310 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1315, from a wired receiver); and demodulating the signal. The transceiver 1310 or transceiver 1310 and one or more antennas 1315 or wired interfaces (where applicable) may be examples of transmitter 1015, transmitter 1115, receiver 1010, receiver 1110, or any combination thereof or components thereof as described herein. In some examples, the transceiver may be operable to support communications via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

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

[0225] The processor 1335 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor 1335 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 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1325) to cause the device 1305 to perform various functions (e.g., functions or tasks that support RAR enhancement for multiple RACH procedures). For example, the device 1305 or a component of the device 1305 may include a processor 1335 and a memory 1325 coupled to the processor 1335, and the processor 1335 and the memory 1325 are configured to perform the various functions described herein. Processor 1335 can be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functionality for performing functions of device 1305 (e.g., by executing code 1330).

[0226] In some examples, bus 1340 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1340 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1305, or communications performed between different components of device 1305 that may be co-located or located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one of these different components or divided between different components).

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

[0228] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at a network entity. For example, the communication manager 1320 may be configured to or otherwise support a component for receiving a first control message indicating a first random access procedure for a UE. The communication manager 1320 may be configured to or otherwise support a component for receiving a second control message indicating a second random access procedure during a first random access procedure, the second random access procedure being for the UE. The communication manager 1320 may be configured to or otherwise support a component for sending a random access response associated with one of the first random access procedure or the second random access procedure to the UE, the random access response including an indication of one of the first random access procedure or the second random access procedure.

[0229] By including or configuring the communication manager 1320 according to the examples described herein, the device 1305 can support RAR enhanced techniques for multiple RACH procedures, which can result in improved communication reliability, reduced latency, an improved user experience associated with reduced processing, reduced power consumption, more efficient use of communication resources, improved coordination between devices, longer battery life, and improved use of processing power, among other advantages.

[0230] In some examples, the communication manager 1320 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the processor 1335, the memory 1325, the code 1330, the transceiver 1310, or any combination thereof. For example, the code 1330 may include instructions that are executable by the processor 1335 to cause the device 1305 to perform various aspects of RAR enhancement for multiple RACH procedures as described herein, or the processor 1335 and the memory 1325 may be otherwise configured to perform or support such operations.

[0231] Fig.14 A flow chart illustrating a method 1400 for supporting RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 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.

[0232] At 1405, the method may include: receiving a first control message in a first PDCCH command triggering a first random access procedure, the first control message indicating a first preamble identifier associated with the first random access procedure. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 8 The PDCCH command component 825 is used to execute.

[0233] At 1410, the method may include: receiving a second control message in a second PDCCH command during the first random access procedure triggering a second random access procedure, the second control message indicating a second preamble identifier associated with the second random access procedure, wherein the first preamble identifier is different from the second preamble identifier. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 8 The PDCCH command component 825 is used to execute.

[0234] At 1415, the method may include sending a first random access preamble corresponding to the first preamble identifier and a second random access preamble corresponding to the second preamble identifier. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 8 The random access preamble component 830 is used to perform.

[0235] At 1420, the method may include receiving a random access response that is associated with one of the first random access procedure or the second random access procedure based on a preamble identifier indication included in the random access response. The operations of 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1420 may be performed as described in reference to Figure 8 The random access response component 835 is used to perform.

[0236] Fig.15 A flow chart illustrating a method 1500 for supporting RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 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.

[0237] At 1505, the method may include: sending a first random access preamble corresponding to a first preamble identifier as part of a first random access procedure. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 8 The random access preamble component 830 is used to perform.

[0238] At 1510, the method may include: sending a second random access preamble corresponding to a second preamble identifier during the first random access procedure, the second random access preamble being associated with the second random access procedure. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 8 The random access preamble component 830 is used to perform.

[0239] At 1515, the method may include receiving a random access response associated with one of the first random access procedure or the second random access procedure based on an indication of a timing advance group in the random access response. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Figure 8 The random access response component 835 is used to perform.

[0240] Fig.16 A flow chart illustrating a method 1600 for supporting RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 9 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.

[0241] At 1605, the method may include receiving an RRC message indicating that the component carrier is associated with both the first timing advance group and the second timing advance group. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Figure 8 The timing advance group component 840 is executed.

[0242] At 1610, the method may include receiving a first control message triggering a first random access procedure via a first PDCCH command, wherein the first PDCCH command is associated with a first CORESET pool index. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Figure 8 The PDCCH command component 825 is used to execute.

[0243] At 1615, the method may include receiving a second control message triggering a second random access procedure via a second PDCCH command and during the first random access procedure, wherein the second PDCCH command is associated with a second CORESET pool index. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Figure 8 The PDCCH command component 825 is used to execute.

[0244] At 1620, the method may include: sending a first random access preamble code via a first random access opportunity on the component carrier and sending a second random access preamble code via a second random access opportunity on the component carrier. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference Figure 8 The random access preamble component 830 is used to perform.

[0245] At 1625, the method may include receiving a random access response including an indication of a timing advance group, wherein the random access response is associated with a first random access procedure based on the timing advance group corresponding to a first CORESET pool index or a first random access opportunity, or the random access response is associated with a second random access procedure based on the timing advance group corresponding to a second CORESET pool index or a second random access opportunity. The operations of 1625 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1625 may be performed as described in reference to Figure 8 The random access response component 835 is used to perform.

[0246] Fig.17 A flow chart illustrating a method 1700 for supporting RAR enhancement for multiple RACH procedures according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13In 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.

[0247] At 1705, the method may include: receiving (e.g., from a first network entity) a first control message indicating a first random access procedure for the UE. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.12 The random access procedure component 1225 is executed.

[0248] At 1710, the method may include: receiving (e.g., from a second network entity) a second control message indicating a second random access procedure during the first random access procedure, the second random access procedure being for the UE. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.12 The random access procedure component 1225 is executed.

[0249] At 1715, the method may include: sending a random access response associated with one of the first random access procedure or the second random access procedure to the UE, the random access response including an indication of one of the first random access procedure or the second random access procedure. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig.12 The random access response component 1230 is executed.

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

[0251] Aspect 1: A method for wireless communication at a UE, comprising: receiving a first control message in a first PDCCH command that triggers a first random access procedure, the first control message indicating a first preamble identifier associated with the first random access procedure; receiving a second control message in a second PDCCH command that triggers a second random access procedure during the first random access procedure, the second control message indicating a second preamble identifier associated with the second random access procedure, wherein the first preamble identifier is different from the second preamble identifier; sending a first random access preamble corresponding to the first preamble identifier and a second random access preamble corresponding to the second preamble identifier; and receiving a RAR, the RAR being associated with one of the first random access procedure or the second random access procedure based at least in part on the preamble identifier indication included in the RAR.

[0252] Aspect 2: The method according to aspect 1 further includes: monitoring the RAR associated with the first random access procedure; and monitoring the RAR associated with the second random access procedure.

[0253] Aspect 3: A method according to any one of Aspects 1 to 2, wherein receiving the RAR comprises: receiving the RAR associated with the first random access procedure based at least in part on the preamble identifier indicating the first preamble identifier; or receiving the RAR associated with the second random access procedure based at least in part on the preamble identifier indicating the second preamble identifier.

[0254] Aspect 4: The method according to any one of Aspects 1 to 3 further includes: receiving a PDSCH, wherein the PDSCH is associated with the first random access procedure or the second random access procedure at least in part based on the preamble identifier indication included in the RAR, wherein the RAR includes the PDSCH.

[0255] Aspect 5: A method according to any one of Aspects 1 to 4, wherein receiving the first control message and the second control message comprises: receiving the first PDCCH command from a first network entity; and receiving the second PDCCH command from a second network entity different from the first network entity.

[0256] Aspect 6: A method for wireless communication at a UE, comprising: sending a first random access preamble corresponding to a first preamble identifier as part of a first random access procedure; sending a second random access preamble corresponding to a second preamble identifier during the first random access procedure, the second random access preamble being associated with the second random access procedure; and receiving the RAR, the RAR being associated with one of the first random access procedure or the second random access procedure based at least in part on an indication of a timing advance group in the RAR.

[0257] Aspect 7: The method according to aspect 6 further includes: monitoring the RAR associated with the first random access procedure; and monitoring the RAR associated with the second random access procedure.

[0258] Aspect 8: The method according to any one of Aspects 6 to 7 also includes: receiving a first control message in a first PDCCH command associated with the first random access procedure, the first control message indicating the first preamble code identifier; and receiving a second control message in a second PDCCH command associated with the second random access procedure, the second control message indicating the second preamble code identifier.

[0259] Aspect 9: A method according to Aspect 8, wherein receiving the first control message and the second control message includes: receiving the first control message in the first PDCCH command from a first network entity; and receiving the second control message in the second PDCCH command from a second network entity different from the first network entity.

[0260] Aspect 10: The method according to any one of Aspects 6 to 9 further includes: receiving a PDSCH, wherein the PDSCH is associated with the first random access procedure or the second random access procedure at least in part based on the indication of the timing advance group included in the RAR, wherein the RAR includes the PDSCH.

[0261] Aspect 11: A method according to any one of aspects 6 to 10, wherein receiving the RAR comprises: receiving a timing advance group identifier in a field of the RAR, wherein the indication of the timing advance group is at least partially based on the timing advance group identifier.

[0262] Aspect 12: A method according to any one of Aspects 6 to 11, wherein receiving the RAR comprises: receiving the indication of the timing advance group in one or more fields of the RAR, wherein the one or more fields comprise a reserved field and a CSI request field.

[0263] Aspect 13: A method according to any one of Aspects 6 to 12, wherein receiving the RAR includes: receiving a PDCCH scrambled by a random access temporary identifier, wherein the indication of the timing advance group is at least partially based on the random access temporary identifier, and wherein the RAR includes the PDCCH scrambled by the random access temporary identifier.

[0264] Aspect 14: A method according to Aspect 13, wherein receiving the PDCCH scrambled by the random access temporary identifier includes: receiving an indication of a CORESET pool index in the PDCCH scrambled by the random access temporary identifier, wherein the CORESET pool index is at least partially based on the random access temporary identifier and is associated with the first random access procedure or the second random access procedure.

[0265] Aspect 15: A method according to any one of Aspects 13 to 14, wherein receiving the PDCCH scrambled by the random access temporary identifier includes: receiving an indication of a timing advance group identifier in the PDCCH scrambled by the random access temporary identifier, wherein the timing advance group identifier is at least partially based on the random access temporary identifier and is associated with the first random access procedure or the second random access procedure.

[0266] Aspect 16: A method according to any one of Aspects 6 to 15, wherein receiving the RAR comprises: receiving the indication of the timing advance group in one or more reserved bits in a PDCCH scrambled by a random access temporary identifier, wherein the RAR includes the PDCCH.

[0267] Aspect 17: A method according to any one of Aspects 6 to 16, wherein receiving the RAR includes: receiving an indication of a CORESET pool index in one or more reserved bits in a PDCCH scrambled by a random access temporary identifier, wherein the CORESET pool index is associated with the timing advance group, and wherein the RAR includes the PDCCH.

[0268] Aspect 18: A method for wireless communication at a UE, comprising: receiving an RRC message indicating that a component carrier is associated with both a first timing advance group and a second timing advance group; receiving a first control message triggering a first random access procedure via a first PDCCH command, wherein the first PDCCH command is associated with a first CORESET pool index; receiving a second control message triggering a second random access procedure via a second PDCCH command and during the first random access procedure, wherein the second PDCCH command is associated with a second CORESET pool index; sending a first random access preamble via a first random access opportunity on the component carrier and sending a second random access preamble via a second random access opportunity on the component carrier; and receiving a RAR including an indication of a timing advance group, wherein the RAR is associated with the first random access procedure based at least in part on the timing advance group corresponding to the first CORESET pool index or the first random access opportunity, or the RAR is associated with the second random access procedure based at least in part on the timing advance group corresponding to the second CORESET pool index or the second random access opportunity.

[0269] Aspect 19: The method according to Aspect 18 also includes: determining that the first random access procedure is associated with the timing advance group based at least in part on the first PDCCH command being associated with the first CORESET pool index and the first CORESET pool index being associated with the timing advance group, or the first random access opportunity being associated with the timing advance group; or determining that the second random access procedure is associated with the timing advance group based at least in part on the second PDCCH command being associated with the second CORESET pool index and the second CORESET pool index being associated with the timing advance group, or the second random access opportunity being associated with the timing advance group.

[0270] Aspect 20: The method according to any one of aspects 18 to 19, further comprising: monitoring the RAR associated with the first random access procedure; and monitoring the RAR associated with the second random access procedure.

[0271] Aspect 21: A method for wireless communication at a network entity, comprising: receiving a first control message indicating a first random access procedure for a UE; receiving a second control message indicating a second random access procedure during the first random access procedure, the second random access procedure being for the UE; and sending a RAR associated with one of the first random access procedure or the second random access procedure to the UE, the RAR including an indication of one of the first random access procedure or the second random access procedure.

[0272] Aspect 22: The method according to aspect 21, wherein sending the RAR comprises: sending a preamble identifier associated with the first random access procedure or the second random access procedure, wherein the indication included in the RAR is at least partially based on the preamble identifier.

[0273] Aspect 23: A method according to any one of Aspects 21 to 22, wherein sending the RAR comprises: sending an indication of a timing advance group associated with the first random access procedure or the second random access procedure, wherein the indication included in the RAR is the indication of the timing advance group.

[0274] Aspect 24: The method according to aspect 23, wherein sending the indication of the timing advance group comprises: sending a timing advance group identifier in a field of the RAR, wherein the indication of the timing advance group is at least partially based on the timing advance group identifier.

[0275] Aspect 25: A method according to any one of Aspects 23 to 24, wherein sending the indication of the timing advance group includes: sending the indication of the timing advance group in one or more fields of the RAR, wherein the one or more fields include a reserved field, a CSI request field, or both.

[0276] Aspect 26: A method according to any one of Aspects 23 to 25, wherein sending the indication of the timing advance group includes: sending a PDCCH scrambled by a random access temporary identifier, wherein the indication of the timing advance group is at least partially based on the random access temporary identifier, and wherein the RAR includes the PDCCH scrambled by the random access temporary identifier.

[0277] Aspect 27: A method according to aspect 26, wherein sending the PDCCH scrambled by the random access temporary identifier comprises: sending an indication of a CORESET pool index in the PDCCH scrambled by the random access temporary identifier, wherein the CORESET pool index is based at least in part on the random access temporary identifier and is associated with the first random access procedure or the second random access procedure

[0278] Aspect 28: A method according to any one of Aspects 26 to 27, wherein sending the PDCCH scrambled by the random access temporary identifier includes: sending an indication of a timing advance group identifier in the PDCCH scrambled by the random access temporary identifier, wherein the timing advance group identifier is at least partially based on the random access temporary identifier and is associated with the first random access procedure or the second random access procedure.

[0279] Aspect 29: A method according to any one of Aspects 23 to 28, wherein sending the indication of the timing advance group includes: sending the indication of the timing advance group in one or more reserved bits in a PDCCH scrambled by a random access temporary identifier, wherein the RAR includes the PDCCH.

[0280] Aspect 30: A method according to any one of aspects 21 to 29, wherein sending the RAR comprises: sending an indication of a CORESET pool index in one or more bits in a PDCCH scrambled by a random access temporary identifier, wherein the RAR comprises the PDCCH.

[0281] Aspect 31: An apparatus for performing wireless communication at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to enable the apparatus to perform a method according to any one of Aspects 1 to 5.

[0282] Aspect 32: An apparatus for wireless communication at a UE, comprising at least one component for performing a method according to any one of aspects 1 to 5.

[0283] Aspect 33: 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 5.

[0284] Aspect 34: An apparatus for performing wireless communications at a UE, 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 6 to 17.

[0285] Aspect 35: An apparatus for wireless communication at a UE, comprising at least one means for performing a method according to any one of aspects 6 to 17.

[0286] Aspect 36: A non-transitory computer-readable medium storing 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 6 to 17.

[0287] Aspect 37: An apparatus for performing wireless communications at a UE, 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 18 to 20.

[0288] Aspect 38: An apparatus for wireless communication at a UE, comprising at least one means for performing a method according to any one of aspects 18 to 20.

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

[0290] Aspect 40: An apparatus for wireless communication at a network entity, 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 21 to 30.

[0291] Aspect 41: An apparatus for wireless communication at a network entity, comprising at least one means for performing a method according to any one of aspects 21 to 30.

[0292] Aspect 42: 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 21 to 30.

[0293] 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 that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

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

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

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

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

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

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

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

[0301] 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 or other subsequent reference labels.

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

[0303] 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), comprising: receiving a first control message triggering a first random access procedure in a first physical downlink control channel command, the first control message indicating a first preamble identifier associated with the first random access procedure; receiving, during the first random access procedure, a second control message in a second physical downlink control channel command triggering a second random access procedure, the second control message indicating a second preamble identifier associated with the second random access procedure, wherein the first preamble identifier is different from the second preamble identifier; sending a first random access preamble corresponding to the first preamble identifier and a second random access preamble corresponding to the second preamble identifier; as well as A random access response is received, the random access response being associated with one of the first random access procedure or the second random access procedure based at least in part on a preamble identifier indication included in the random access response.

2. The method according to claim 1, further comprising: monitoring the random access response associated with the first random access procedure; as well as The random access response associated with the second random access procedure is monitored.

3. The method of claim 1 , wherein receiving the random access response comprises: receiving the random access response associated with the first random access procedure corresponding to the first preamble identifier based at least in part on the preamble identifier indication; or The random access response associated with the second random access procedure corresponding to the second preamble identifier based at least in part on the preamble identifier indication is received.

4. The method according to claim 1, further comprising: A physical downlink shared channel is received, the physical downlink shared channel being associated with the first random access procedure or the second random access procedure based at least in part on the preamble identifier indication included in the random access response, wherein the random access response includes the physical downlink shared channel.

5. The method of claim 1 , wherein receiving the first control message and the second control message comprises: receiving the first physical downlink control channel command from a first network entity; as well as The second physical downlink control channel command is received from a second network entity different from the first network entity.

6. A method for wireless communication at a user equipment (UE), comprising: sending a first random access preamble corresponding to a first preamble identifier as part of a first random access procedure; transmitting, during the first random access procedure, a second random access preamble corresponding to a second preamble identifier, the second random access preamble being associated with a second random access procedure; as well as A random access response is received, the random access response being associated with one of the first random access procedure or the second random access procedure based at least in part on an indication of a timing advance group in the random access response.

7. The method according to claim 6, further comprising: monitoring the random access response associated with the first random access procedure; as well as The random access response associated with the second random access procedure is monitored.

8. The method according to claim 6, further comprising: receiving a first control message in a first physical downlink control channel order associated with the first random access procedure, the first control message indicating the first preamble identifier; as well as A second control message is received in a second physical downlink control channel order associated with the second random access procedure, the second control message indicating the second preamble identifier.

9. The method of claim 8, wherein receiving the first control message and the second control message comprises: receiving the first control message in the first physical downlink control channel order from a first network entity; as well as The second control message is received in the second physical downlink control channel order from a second network entity different from the first network entity.

10. The method according to claim 6, further comprising: A physical downlink shared channel is received, the physical downlink shared channel being associated with the first random access procedure or the second random access procedure based at least in part on the indication of the timing advance group included in the random access response, wherein the random access response includes the physical downlink shared channel.

11. The method of claim 6, wherein receiving the random access response comprises: A timing advance group identifier is received in a field of the random access response, wherein the indication of the timing advance group is based at least in part on the timing advance group identifier.

12. The method of claim 6, wherein receiving the random access response comprises: The indication of the timing advance group is received in one or more fields of the random access response, wherein the one or more fields include a reserved field and a channel state information request field.

13. The method of claim 6, wherein receiving the random access response comprises: receiving a physical downlink control channel scrambled by a random access temporary identifier, wherein the indication of the timing advance group is based at least in part on the random access temporary identifier, and wherein the random access response comprises the physical downlink control channel scrambled by the random access temporary identifier.

14. The method of claim 13, wherein receiving the physical downlink control channel scrambled by the random access temporary identifier comprises: An indication of a control resource set pool index in the physical downlink control channel scrambled by the random access temporary identifier is received, wherein the control resource set pool index is based at least in part on the random access temporary identifier and is associated with the first random access procedure or the second random access procedure.

15. The method of claim 13, wherein receiving the physical downlink control channel scrambled by the random access temporary identifier comprises: An indication of a timing advance group identifier is received in the physical downlink control channel scrambled by the random access temporary identifier, wherein the timing advance group identifier is based at least in part on the random access temporary identifier and is associated with the first random access procedure or the second random access procedure.

16. The method of claim 6, wherein receiving the random access response comprises: receiving the indication of the timing advance group in one or more reserved bits in a physical downlink control channel scrambled by a random access temporary identifier, wherein the random access response comprises the physical downlink control channel.

17. The method of claim 6, wherein receiving the random access response comprises: receiving an indication of a control resource set pool index in one or more reserved bits in a physical downlink control channel scrambled by a random access temporary identifier, wherein the control resource set pool index is associated with the timing advance group, and wherein the random access response includes the physical downlink control channel.

18. A method for wireless communication at a user equipment (UE), comprising: receiving a radio resource control message indicating that a component carrier is associated with both a first timing advance group and a second timing advance group; receiving a first control message triggering a first random access procedure via a first physical downlink control channel command, wherein the first physical downlink control channel command is associated with a first control resource set pool index; receiving, via a second physical downlink control channel command and during the first random access procedure, a second control message triggering a second random access procedure, wherein the second physical downlink control channel command is associated with a second control resource set pool index; transmitting a first random access preamble via a first random access opportunity on the component carrier and transmitting a second random access preamble via a second random access opportunity on the component carrier; and Receive a random access response including an indication of a timing advance group, wherein the random access response is associated with the first random access procedure based at least in part on the timing advance group corresponding to the first control resource set pool index or the first random access opportunity, or the random access response is associated with the second random access procedure based at least in part on the timing advance group corresponding to the second control resource set pool index or the second random access opportunity.

19. The method according to claim 18, further comprising: determining that the first random access procedure is associated with the timing advance group based at least in part on the first physical downlink control channel command being associated with the first control resource set pool index and the first control resource set pool index being associated with the timing advance group, or the first random access opportunity being associated with the timing advance group; or Determining that the second random access procedure is associated with the timing advance group is based at least in part on the second physical downlink control channel command being associated with the second control resource set pool index and the second control resource set pool index being associated with the timing advance group, or the second random access opportunity being associated with the timing advance group.

20. The method of claim 18, further comprising: monitoring the random access response associated with the first random access procedure; as well as The random access response associated with the second random access procedure is monitored.

21. A method for wireless communication at a network entity, comprising: receiving a first control message indicating a first random access procedure for a user equipment (UE); receiving, during the first random access procedure, a second control message indicating a second random access procedure, the second random access procedure being for the UE; as well as A random access response associated with one of the first random access procedure or the second random access procedure is sent to the UE, the random access response including an indication of one of the first random access procedure or the second random access procedure.

22. The method of claim 21 , wherein sending the random access response comprises: A preamble identifier associated with the first random access procedure or the second random access procedure is sent, wherein the indication included in the random access response is based at least in part on the preamble identifier.

23. The method of claim 21 , wherein sending the random access response comprises: An indication of a timing advance group associated with the first random access procedure or the second random access procedure is sent, wherein the indication included in the random access response is the indication of the timing advance group.

24. The method of claim 23, wherein sending the indication of the timing advance group comprises: A timing advance group identifier in a field of the random access response is transmitted, wherein the indication of the timing advance group is based at least in part on the timing advance group identifier.

25. The method of claim 23, wherein sending the indication of the timing advance group comprises: The indication of the timing advance group in one or more fields of the random access response is transmitted, wherein the one or more fields include a reserved field, a channel state information request field, or both.

26. The method of claim 23, wherein sending the indication of the timing advance group comprises: sending a physical downlink control channel scrambled by a random access temporary identifier, wherein the indication of the timing advance group is based at least in part on the random access temporary identifier, and wherein the random access response includes the physical downlink control channel scrambled by the random access temporary identifier.

27. The method of claim 26, wherein sending the physical downlink control channel scrambled by the random access temporary identifier comprises: An indication of a control resource set pool index in the physical downlink control channel scrambled by the random access temporary identifier is sent, wherein the control resource set pool index is based at least in part on the random access temporary identifier and is associated with the first random access procedure or the second random access procedure.

28. The method of claim 26, wherein sending the physical downlink control channel scrambled by the random access temporary identifier comprises: An indication of a timing advance group identifier in the physical downlink control channel scrambled by the random access temporary identifier is transmitted, wherein the timing advance group identifier is based at least in part on the random access temporary identifier and is associated with the first random access procedure or the second random access procedure.

29. The method of claim 23, wherein sending the indication of the timing advance group comprises: The indication of the timing advance group is transmitted in one or more reserved bits in a physical downlink control channel scrambled by a random access temporary identifier, wherein the random access response comprises the physical downlink control channel.

30. The method of claim 21 , wherein sending the random access response comprises: An indication of a control resource set pool index in one or more bits in a physical downlink control channel scrambled by a random access temporary identifier is sent, wherein the random access response includes the physical downlink control channel.