Performing multiple parallel random access procedures

By allowing the UE to execute multiple parallel random access procedures simultaneously in multi-TRP or multi-TAG scenarios, the problems of increased latency and resource waste in existing technologies in multi-TRP or multi-TAG scenarios are solved, achieving more efficient communication.

CN118947203APending Publication Date: 2024-11-12QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

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

AI Technical Summary

Technical Problem

In existing wireless communication systems, the parallel random access procedure of user equipment (UE) in multiple transmit/receive points (TRPs) or different timing advance groups (TAGs) suffers from increased latency, communication failures, and resource waste. In particular, in multi-TRP or multi-TAG scenarios, the UE can only execute one RACH procedure at a time.

Method used

The UE supports multiple parallel random access procedures for CCs in multiple TRPs or different TAGs. It receives control messages that trigger random access procedures, sends random access preambles, and performs multiple parallel random access procedures simultaneously under certain conditions, including up to four parallel procedures.

Benefits of technology

It reduces uplink synchronization latency, improves communication efficiency, avoids delays and resource waste, and enhances user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118947203A_ABST
    Figure CN118947203A_ABST
Patent Text Reader

Abstract

Methods, systems, and devices for wireless communication are described. In some systems, if one or more conditions are satisfied, a user equipment (UE) may support multiple parallel random access procedures for multiple transmit receive points (TRPs) or for component carriers (CCs) in different TAGs. The UE may support parallel random access procedures for the same CC configured with two TAGs (e.g., if control resource set (CORESET) pool indices for the random access procedures are different). The UE may support parallel random access procedures for different CCs associated with different TAGs. The UE may support a parallel random access procedure for different CCs across or within a CC set. If random access procedures associated with the same CC have different CORESET pool indices, and additional random access procedures are associated with different CCs and different TAGs, the UE may support these random access procedures for the same CC or different CCs.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The following relates to wireless communications including performing multiple parallel random access procedures. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication of communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0003] The described technology relates to improved methods, systems, devices and apparatuses for supporting the execution of multiple parallel random access procedures. For example, the described technology provides a communication device that can support multiple parallel random access procedures for multiple transmit receive points (TRPs) or for component carriers (CCs) in different timing advance groups (TAGs) when one or more conditions are met. For example, the communication device can support up to two parallel random access procedures for the same CC configured with two TAGs and two control resource set (CORESET) pool indexes. In some examples, the communication device can support up to four parallel random access procedures for different CCs each associated with a different TAG. In some examples, the communication device can support up to four parallel random access procedures for different CCs across CC sets or within a CC set (for example, two parallel RACH procedures in different CC sets defined by different TAGs can be supported, and if the two random access procedures are triggered by PDCCH commands associated with different CORESET pool indexes, up to two parallel random access procedures within a CC set can also be supported for one or two CCs). In some examples, if two random access procedures associated with the same CC have different CORESET pool indexes, and an additional random access procedure is associated with a different CC and a different TAG, the communications device may support up to four random access procedures for the same CC or different CCs.

[0004] A method for wireless communication at a user equipment (UE) is described. The method may include: receiving a first control message triggering a first random access procedure; sending a first random access preamble message associated with the first random access procedure based on receiving the first control message; receiving a second control message triggering a second random access procedure; and sending a second random access preamble message associated with the second random access procedure based on receiving the second control message before completing the first random access procedure and based on satisfying one or more conditions.

[0005] 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 that triggers a first random access procedure; receive a first control message that triggers the first random access procedure; send a first random access preamble message associated with the first random access procedure based on receiving the first control message; receive a second control message that triggers a second random access procedure; and send a second random access preamble message associated with the second random access procedure based on receiving the second control message before completing the first random access procedure and based on satisfying one or more conditions.

[0006] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving a first control message that triggers a first random access procedure; means for sending a first random access preamble message associated with the first random access procedure based on receiving the first control message; means for receiving a second control message that triggers a second random access procedure; and means for sending a second random access preamble message associated with the second random access procedure based on receiving the second control message before completing the first random access procedure and based on satisfying one or more conditions.

[0007] 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 triggering a first random access procedure; send a first random access preamble message associated with the first random access procedure based on receiving the first control message; receive a second control message triggering a second random access procedure; and send a second random access preamble message associated with the second random access procedure based on receiving the second control message before completing the first random access procedure and based on satisfying one or more conditions.

[0008] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may also include operations, features, apparatus, or instructions for the following actions: receiving signaling indicating the configuration of a first component carrier associated with a first timing advance group and a second timing advance group, wherein a first random access procedure and a second random access procedure may be associated with the first component carrier; and determining that one or more conditions can be satisfied based on that a first control resource set pool index associated with the first control message is different from a second control resource set pool index associated with the second control message.

[0009] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may also include operations, features, apparatus, or instructions for the following actions: receiving signaling indicating the configuration of a first timing advance group associated with a first component carrier and a second timing advance group associated with a second component carrier, wherein a first random access procedure may be associated with the first component carrier and a second random access procedure may be associated with the second component carrier; and determining that one or more conditions may be satisfied based on the first component carrier being associated with the first timing advance group and the second component carrier being associated with a second timing advance group that may be different from the first timing advance group.

[0010] Some examples of the methods, devices (apparatus) and non-transitory computer-readable media described herein may also include operations, features, apparatuses or instructions for the following actions: receiving signaling indicating the configuration of a first component carrier set and a second component carrier set, wherein each component carrier in the first component carrier set may be associated with one or more timing advance groups in the first timing advance group set, and each component carrier in the second component carrier set may be associated with one or more timing advance groups in the second timing advance group set; and determining that one or more conditions can be satisfied based on triggering a first random access procedure for a first component carrier in the first component carrier set and triggering a second random access procedure for a first component carrier in the second component carrier set.

[0011] In some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein, the UE supports up to two random access procedures that are at least partially overlapping in time for a first set of component carriers and up to two random access procedures that are at least partially overlapping in time for a second set of component carriers based on satisfying one or more conditions.

[0012] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may also include operations, features, apparatus, or instructions for the following actions: determining that one or more conditions can be satisfied based on each random access procedure associated with a corresponding component carrier set being associated with a different control resource set pool index.

[0013] Some examples of the methods, devices (apparatus) and non-transitory computer-readable media described herein may also include operations, features, apparatuses or instructions for the following actions: receiving signaling indicating the configuration of a first component carrier associated with a first timing advance group and a second timing advance group and a second component carrier associated with at least a third timing advance group, and wherein the first random access process and the second random access process may be associated with the first component carrier; determining that one or more conditions can be satisfied based on that a first control resource pool index associated with the first control message is different from a second control resource pool index associated with the second control message; receiving a third control message that triggers a third random access process associated with the second component carrier and the third timing advance group; determining that one or more conditions can be satisfied based on that the third timing advance group is different from the first timing advance group and the second timing advance group; and sending a third random access preamble message associated with the third random access process based on receiving the third control message before completing the first random access process based on satisfying one or more conditions.

[0014] Some examples of the methods, devices (apparatus) and non-transitory computer-readable media described herein may also include operations, features, apparatuses or instructions for the following actions: receiving a first random access response message associated with a first random access process based on sending a first random access preamble message; and receiving a second random access response message associated with a second random access process based on sending a second random access preamble message.

[0015] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may also include operations, features, apparatus, or instructions for the following actions: sending a capability message indicating that the UE may be able to support multiple random access procedures that at least partially overlap in time, wherein receiving a second control message triggering a second random access procedure may be based on sending the capability message.

[0016] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the capability message includes: an indication of a threshold number of random access procedures that the UE may be able to support that at least partially overlap in time, an indication of one or more conditions, or both.

[0017] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may also include operations, features, apparatus, or instructions for the following actions: receiving a third control message that triggers a third random access process before completing the first random access process; determining that one or more conditions may not be satisfied for the third random access process; and based on the determination, suppressing initiation of the third random access process, or initiating the third random access process and terminating the first random access process.

[0018] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may also include operations, features, apparatuses, or instructions for the following actions: receiving a third control message that triggers a third random access procedure before completing the first random access procedure; determining that the third random access procedure exceeds a threshold number of random access procedures supported by the UE that at least partially overlap in time; and based on the determination, suppressing initiation of the third random access procedure.

[0019] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, devices, or instructions for the following actions: receiving a first control message, which includes receiving the first control message from a first network entity; and receiving a second control message, which includes receiving a second control message from a second network entity. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 An example of a wireless communication system supporting execution of multiple parallel random access procedures according to one or more aspects of the present disclosure is illustrated.

[0021] Figure 2 An example of a timeline supporting execution of multiple parallel random access procedures according to one or more aspects of the present disclosure is illustrated.

[0022] Figure 3 An example of a timeline supporting execution of multiple parallel random access procedures according to one or more aspects of the present disclosure is illustrated.

[0023] Figure 4 An example of a process flow supporting execution of multiple parallel random access procedures according to one or more aspects of the present disclosure is illustrated.

[0024] Figure 5 An example of a process flow supporting execution of multiple parallel random access procedures according to one or more aspects of the present disclosure is illustrated.

[0025] Figure 6 An example of a process flow supporting execution of multiple parallel random access procedures according to one or more aspects of the present disclosure is illustrated.

[0026] Figure 7 An example of a process flow supporting execution of multiple parallel random access procedures according to one or more aspects of the present disclosure is illustrated.

[0027] Figure 8 and Fig. 9 A block diagram of a device supporting execution of multiple parallel random access procedures according to one or more aspects of the present disclosure is shown.

[0028] Fig.10A block diagram of a communication manager supporting execution of multiple parallel random access procedures in accordance with one or more aspects of the present disclosure is shown.

[0029] Fig.11 A diagram of a system including a device that supports performing multiple parallel random access procedures in accordance with one or more aspects of the present disclosure is shown.

[0030] Figures 12 to 15 A flow chart is shown illustrating a method of supporting execution of multiple parallel random access procedures according to one or more aspects of the present disclosure. DETAILED DESCRIPTION

[0031] In some wireless communication systems, a user equipment (UE) and a network entity (e.g., one or more transmit / receive points (TRPs)) may perform a random access channel (RACH) procedure. The TRP may trigger a first RACH procedure by sending a physical downlink control channel (PDCCH) command to the UE. The UE may then send a first RACH message to the TRP during the first RACH procedure and may monitor a second RACH message from the TRP during a time window. If the UE receives a second RACH message including a RACH preamble identifier that matches the preamble sent in the first RACH message, the UE may consider the first RACH procedure to be successfully completed. If the UE does not receive the second RACH message, or if the second RACH message received after the time window expires does not include a preamble that matches the preamble of the first RACH message, the TRP may trigger a RACH retransmission. When one of the retransmitted second RACH messages is successfully received, the UE may consider the first RACH procedure to be successfully completed. When the number of retransmissions meets a threshold, the UE may consider the first RACH procedure to be unsuccessful.

[0032] Some UEs may support no more than one RACH procedure at any point in time. For a multiple TRP (mTRP) environment, the UE may perform a RACH procedure to synchronize with each of the multiple TRPs. However, performing a first RACH procedure using a first TRP, and then performing a second RACH procedure using a second TRP after completing the first procedure, may introduce increased uplink synchronization delays. Similarly, for multiple component carriers (CCs) in different timing advance groups (TAGs), the RACH procedure for the second serving cell may not be performed until after the RACH procedure for the first serving cell is completed, which may introduce additional delays for timing adjustment. If the UE supports no more than a single RACH procedure at a time, the UE experiences increased latency, communication failures or drops, inefficient use of available system resources, and a reduced user experience.

[0033] If one or more conditions are met, the UE may support multiple parallel random access procedures for multiple TRPs or for CCs in different TAGs. For example, the UE may support up to two parallel random access procedures for the same CC configured with two TAGs and two CORESET pool indexes. In some examples, the UE may support up to four parallel random access procedures for different CCs each associated with a different TAG. In some examples, the UE may support up to four parallel random access procedures for different CCs across CC sets or within a CC set (for example, two parallel RACH procedures in different CC sets defined by different TAGs may be supported, and if the two random access procedures are triggered by PDCCH commands associated with different CORESET pool indexes, up to two parallel random access procedures within a CC set may also be supported for one or two CCs). In some examples, if two random access procedures associated with the same CC have different CORESET pool indexes, and additional random access procedures are associated with different CCs and different TAGs, the UE may support up to four random access procedures for the same CC or different CCs.

[0034] Various aspects of the present disclosure are first described in the context of a wireless communication system. Various aspects of the present disclosure are further illustrated by and described with reference to timelines and process flows. Various aspects of the present disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to performing multiple parallel random access procedures.

[0035] Figure 1 An example of a wireless communication system 100 that supports performing multiple parallel random access 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).

[0036] 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 different 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) over 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 over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0037] 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 able to communicate with various types of devices (such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[0038] 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, 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 the second node.

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

[0040] 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 physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0041] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RTRIC), 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)).

[0042] 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 DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within 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 a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., 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.

[0043] In a wireless communication system (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as a donor entity or an IAB donor. 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., an IAB donor) may communicate with one or more additional network entities 105 (e.g., an IAB node 104) via supported access and backhaul links (e.g., a backhaul communication link 120). The IAB node 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. 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 a case, 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.

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

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

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

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

[0048] 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 electrical appliances or vehicles, meters, etc.

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

[0050] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a defined physical layer structure to support the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any 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).

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

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

[0053] 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). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communication over a particular carrier bandwidth, or may be configurable to support communication over one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

[0054] The signal waveform sent on the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM technology, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a subcarrier resource, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the 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 increase the data rate or data integrity used for communication with UE 115.

[0055] 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 for a UE 115 may be constrained to one or more active BWPs.

[0056] 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 communication resources may be organized according to radio frames, each radio frame 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).

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

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

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

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

[0061] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. Small cells may be associated with lower power network entities 105 (e.g., lower power base stations 140) than macro cells, and small cells may operate 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). A 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.

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

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

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

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

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

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

[0068] In some examples, a UE 115 may be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, 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 .

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

[0070] 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 transferred through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for 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.

[0071] 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 range is approximately one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. 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.

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

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

[0074] 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, the antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may have an antenna array having antenna ports of a set of rows and columns 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.

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

[0076] 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 in a particular direction 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 direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

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

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

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

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

[0081] The wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication of the bearer or PDCP layer can be IP-based. The RLC layer can perform packet segmentation and reorganization to communicate on the logical channel. The MAC layer can perform priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection technology, error correction technology, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer can provide the establishment, configuration and maintenance of the RRC connection of the radio bearer that supports user plane data between the UE 115 and the network entity 105 or the core network 130. At the PHY layer, the transport channel can be mapped to the physical channel.

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

[0083] In some examples, UE 115 and a network entity (e.g., one or more TRPs) may perform a random access channel (RACH) procedure. For a physical RACH (PRACH) transmission performed by UE 115 and triggered by a physical downlink control channel (PDCCH) order, if the value of the RACH preamble index field is not zero, the PRACH mask index field may indicate a PRACH opportunity for the PRACH transmission, where the PRACH opportunity is associated with a SS / PBCH block index indicated by a synchronization symbol (SS) / physical broadcast channel (PBCH) block index field of the PDCCH order.

[0084] In response to the PRACH transmission, the UE 115 may monitor for a RACH response (RAR). Thus, the UE 115 may attempt to detect a DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI during a window controlled by a higher layer. In some examples, the window may start at the first symbol of the earliest control resource set (CORESET), where the UE 115 is configured to receive a PDCCH for a Type1-PDCCH CSS set after the last symbol of a PRACH opportunity corresponding to the PRACH transmission, where the symbol duration corresponds to a subcarrier spacing (SCS) for the Type1-PDCCH CSS set. Based on the SCS for the Type1-PDCCH CSS set, the window length in number of slots may be provided by ra-ResponseWindow.

[0085] If the UE 115 detects a DCI format 1_0 with a cyclic redundancy check (CRC) scrambled by a corresponding random access radio network temporary identifier (RA-RNTI), and the least significant bit (LSB) of the system frame number (SFN) field in the DCI format 1_0 (if included and applicable) is the same as the corresponding LSB of the SFN of the UE 115 transmitting the PRACH, and if the UE 115 receives a transport block (TB) in the corresponding physical downlink shared channel (PDSCH) within the window, the UE 115 may pass the TB to a higher layer. The higher layer may parse the TB for a RACH preamble identifier (RAPID) associated with the PRACH transmission. If the higher layer identifies the RAPID in one or more RAR messages of the TB, the higher layer may indicate an uplink grant to the physical layer. This may be referred to as a RAR uplink (UL) grant in the physical layer.

[0086] If UE 115 does not detect a DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI within the window, or if UE 115 detects a DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI within the window and the LSB of the SFN field in DCI format 1_0 (if included and applicable) is different from the corresponding LSB of the SFN of the PRACH transmitted by UE 115, or if UE 115 does not correctly receive a TB in the corresponding PDSCH within the window, or if higher layers do not identify the RAPID associated with the PRACH transmission from UE 115, then the higher layers may indicate to the physical layer to transmit the PRACH. If requested by higher layers, UE 115 may be expected to transmit the PRACH no later than N symbols after the last symbol of the window or the last symbol of the PDSCH reception. T,1 +0.75 ms to send PRACH, where N T,1It may be N corresponding to the PDSCH processing time for UE processing capability 1 T,1 symbols, assuming that u corresponds to the minimum SCS configuration among the SCS configurations used to carry the PDCCH of DCI format 1_0, the corresponding PDSCH when additional PDSCH DM-RS is configured, and the corresponding PRACH. For u=0, UE 115 may assume that N T,1 = 14. For PRACH transmissions using 1.25 kHz or 5 kHz SCS, UE 115 may determine N1 assuming an SCS configuration of u=0.

[0087] In some examples, if a valid downlink allocation has been received on the PDCCH for the RA-RNTI and the received TB is successfully decoded, the RAR may contain a MAC sub-protocol data unit (sub-PDU) with a backoff indicator. In such examples, the UE 115 may set the PREAMBLE_BACKOFF parameter to the value of the backoff indicator (BI) field of the MAC PDU multiplied by a scaling factor (e.g., a SCALING_FACTOR_BI parameter) using a reference table. Additionally or alternatively, the UE 115 may set PREAMBLE_BACKOFF to 0ms.

[0088] In some cases, if the RAR includes a MAC sub-PDU with a RAPID corresponding to the sent PREAMBLE_INDEX, the UE 115 may consider the RAR to be received successfully. If the UE 115 considers the RAR to be received successfully, and if the RAR includes a MAC sub-PDU with only RAPID, the UE 115 may consider the random access procedure to be successfully completed. Additionally or alternatively, the UE 115 may indicate to the upper layer the receipt of an acknowledgment of the SI request. If the RAR does not include a MAC sub-PDU with only RAPID, the UE 115 may apply certain actions to the serving cell that sent the RACH preamble. In some examples, the UE 115 may process the received timing advance command. The UE 115 may indicate to the lower layer the preamble receive target power (e.g., preambleReceivedTargetPower parameter) and the amount of power ramp that can be applied to the latest RACH preamble transmission (e.g., (PREAMBLE_POWER_RAMPING_COUNTER-1)×PREAMBLE_POWER_RAMPING_STEP). Additionally or alternatively, if the random access procedure of the SCell is performed on an uplink carrier that is not configured with a PUSCH configuration (eg, pusch-Config parameter), the UE 115 may ignore the received UL grant. The UE 115 may process the received UL grant value and indicate it to lower layers.

[0089] If the UE 115 (e.g., the MAC entity) does not select a RACH preamble among one or more contention-based RACH preambles, the UE 115 may consider the random access procedure to be successfully completed. Additionally or alternatively, the UE 115 may set the TEMPORARY_C-RNTI parameter to the value received in the RAR. In some examples, if the RAR is the first successfully received RAR in the random access procedure and if no transmission is made for the common control channel (CCCH) logical channel, the UE 115 may indicate to the multiplexing and assembly entity to include a cell RNTI (C-RNTI) MAC CE in subsequent uplink transmissions. If the random access procedure is initiated for special cell (SPCell) beam failure recovery (BFR) and the spCell-BFR-CBRA parameter with a value of true is configured, the UE 115 may indicate to the multiplexing and assembly entity to include a BFR MAC-CE or a truncated BFR MAC-CE in subsequent uplink transmissions. UE 115 may obtain the MAC PDU to be transmitted from the multiplexing and assembly entity and store it in the Msg3 buffer.

[0090] In some examples, if the ra-ResponseWindow configured in RACH-ConfigCommon expires, and if a RAR containing one or more RAPIDs matching the sent PREAMBLE_INDEX has not been received, the UE 115 may consider that the RAR reception is unsuccessful. Therefore, the UE 115 may increment the preamble transmission counter (e.g., PREAMBLE_TRANSMISSION_COUNTER parameter) by 1. If PREAMBLE_TRANSMISSION_COUNTER=preambleTransMax+1, where preambleTransMax is a threshold for the preamble transmission counter, and if a RACH preamble is sent on the SpCell, the UE 115 may indicate a RACH problem to the upper layer. Additionally or alternatively, if a random access procedure is triggered for a system information (SI) request, the UE 115 may consider that the random access procedure is not successfully completed. If a RACH preamble is sent on the SCell, the UE 115 may consider that the random access procedure is not successfully completed.

[0091] In some examples, if the random access procedure is not completed, the UE 115 may select a random backoff time according to a uniform distribution between 0 and the time indicated by the PREAMBLE_BACKOFF parameter. If the criteria for selecting a contention-free RACH resource are met during the backoff time, the UE 115 may perform a RACH resource selection procedure. Additionally or alternatively, if a random access procedure for an SCell is performed on an uplink carrier that is not configured with pusch-Config, the UE 115 may delay subsequent RACH transmissions until a PDCCH command with the same ra-PreambleIndex, ra-ssb-OccasionMaskIndex, and UL / SUL indicator triggers the random access procedure. Additionally or alternatively, the UE 115 may perform a RACH resource selection procedure after the backoff time.

[0092] In some examples, UE 115 (e.g., a MAC entity) may perform additional steps as part of the random access procedure. For example, if PREAMBLE_TRANSMISSION_COUNTER is greater than one, if UE 115 has not received notification from lower layers to suspend the power ramp counter, if UE 115 has not received an LFT failure indication from lower layers for the last RACH preamble transmission, and if UE 115 has not changed the SSB or CSI-RS selection based on the selection made in the last RACH preamble transmission, then UE 115 may increment PREAMBLE_POWER_RAMPING_COUNTER by one.

[0093] In some examples, UE 115 may select a value for DELTA_PREAMBLE. In some examples, UE 115 may set PREAMBLE_RECEIVED_TARGET_POWER to a value based on Equation 1.

[0094] Formula 1:

[0095] PREAMBLE_RECEIVED_TARGET_POWER=

[0096] preambleReceivedTargetPower+DELTA_PREAMBLE+

[0097] (PREAMBLE_POWER_RAMPING_COUNTER–1)×

[0098] PREAMBLE_POWER_RAMPING_STEP+POWER_OFFSET_2STEP_RA

[0099] In some examples, excluding the example of a contention-free RACH preamble for a beam failure recovery request, the UE 115 may calculate the RA-RNTI associated with the PRACH opportunity in which the RACH preamble is sent. Additionally or alternatively, the UE 115 may instruct the physical layer to send the RACH preamble using the selected PRACH opportunity, the corresponding RA-RNTI (if available), PREAMBLE_INDEX, and PREAMBLE_RECEIVED_TARGET_POWER.

[0100] In some cases, the RA-RNTI associated with the PRACH opportunity in which the RACH preamble is sent may be calculated as described in Equation 2.

[0101] Formula 2: RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×

[0102] 80×8×ul_carrier_id

[0103] In Formula 2, s_id may be an index of the first OFDM symbol of a PRACH opportunity (0≤s_id<14), and t_id may be an index of the first time slot of a PRACH opportunity in a system frame (0≤t_id<80). In some examples, the subcarrier spacing used by UE 115 to determine t_id may be based on the value of μ. Additionally, in Formula 2, f_id may be an index of a PRACH opportunity in the frequency domain (0≤f_id<8), and ul_carrier_id may be a UL carrier for RACH preamble transmission (e.g., 0 for NUL carrier and 1 for SUL carrier).

[0104] In some examples, UE 115 may initiate a random access procedure based on a PDCCH command, by a specific implementation of UE 115 (e.g., the MAC entity itself), or by radio resource control (RRC) for the occurrence of an event for the random access procedure. In some cases, UE 115 (e.g., the MAC entity) may be able to support an ongoing random access procedure at any point in time. In some examples, the random access procedure on the SCell may be initiated only by a PDCCH command with a ra-PreambleIndex different from 0b000000. In some cases, if a new random access procedure is triggered while another random access procedure is already in progress in the MAC entity, UE 115 may decide whether to continue the ongoing procedure or start a new procedure (e.g., for an SI request). If the ongoing random access procedure is triggered by a PDCCH command and UE 115 receives another PDCCH command indicating the same RACH preamble, PRACH mask index, and uplink carrier, UE 115 may consider the new random access procedure to be the same random access procedure as the ongoing random access procedure. Therefore, UE 115 may not perform initialization again.

[0105] In some examples, if a random access procedure is initiated on the serving cell, the MAC entity will perform one or more procedures. In some aspects, the UE 115 may refresh the MSG.3 buffer. Additionally or alternatively, the UE 115 may refresh the MSG. buffer. The UE 115 may set PREAMBLE_TRANSMISSION_COUNTER to 1. The UE 115 may set PREAMBLE_POWER_RAMPING_COUNTER to 1. The UE 115 may set PREAMBLE_BACKOFF to 0ms. The UE 115 may set POWER_OFFSET_2STEP_RA to 0dB.

[0106] In some aspects, if one or more conditions are met, the UE 115 may support multiple parallel RACH processes for multiple TRPs or for CCs in different TAGs (e.g., network entity 105). For example, the UE 115 may support up to two parallel random access processes for the same CC configured with two TAGs and two CORESET pool indexes. In some examples, the UE 115 may support up to four parallel random access processes for different CCs each associated with a different TAG. In some examples, the UE 115 may support up to four parallel random access processes for different CCs across CC sets or within a CC set (e.g., two parallel RACH processes in different CC sets defined by different TAGs may be supported, and if the two random access processes are triggered by PDCCH commands associated with different CORESET pool indexes, up to two parallel random access processes within a CC set may also be supported for one or two CCs). In some examples, if two random access processes associated with the same CC have different CORESET pool indexes, and the additional random access process is associated with different CCs and different TAGs, the UE 115 may support up to four random access processes for the same CC or different CCs.

[0107] Figure 2 An example of a timeline 200 for supporting execution of multiple parallel random access procedures in accordance with one or more aspects of the present disclosure is illustrated. In some examples, timeline 200 may be implemented by one or more aspects of wireless communication system 100. For example, UE 115-a may be an example of UE 115, and network entity 105-a may be an example of network entity 105, as described with reference to FIG. Figure 1 described.

[0108] In some examples, UE 115-a may perform a random access procedure to establish a connection with a network such as a special cell (SpCell) served by network entity 105-a, network entity 105-b, or a different network entity. Additionally or alternatively, UE 115-a may perform a random access procedure to achieve uplink synchronization between UE 115-a and the network. For example, network entity 105-a (e.g., a transmitting and receiving point) may send a physical downlink control channel (PDCCH) command 210-a, and UE 115-a may receive a physical downlink control channel (PDCCH) command that may trigger the random access procedure. In some examples, the PDCCH command 210-a may indicate a RACH preamble identifier (e.g., RAPID), which may also be referred to as a RACH preamble index. Based on receiving the PDCCH command 210-a, the UE 115-a may send (e.g., as part of a triggered random access procedure) a message 215-a (e.g., a RACH preamble (PRACH) transmission, such as message 1 of a four-step random access procedure or message A of a two-step random access procedure) to the network entity 105-a. The message 215-a may include a RAPID, one or more RACH timings, and other transmission-related parameters. Based on sending the message 215-a, the UE 115-a may monitor for a random access response message (e.g., a random access response (RAR)) from the network (e.g., from the network entity 105-a, the network entity 105-b, or a different network entity) during the RAR window 235. For example, the network entity 105-a may send a message RAR to the UE 115-a. The RAR may include a PDCCH portion and a PDSCH portion. For example, the RAR may include a message 220-a, which may include a PDCCH scrambled by a random access radio network temporary identifier (RA-RNTI). Additionally or alternatively, the RAR may include a message 225 - a , which may include a physical downlink shared channel (PDSCH).

[0109] In some examples, UE 115-a may decode message 220-a and message 225-a at a physical layer of UE 115-a. Based on decoding message 220-a and message 225-a, UE 115-a may transmit information 230-a (e.g., information received on the PDSCH via message 225-a of the received RAR) to a higher layer 205-a of UE 115-a. For example, based on decoding message 220-a and message 225-a, UE 115-a may forward a transport block (TB) from the physical layer of UE 115-a to a medium access control (MAC) layer (e.g., higher layer 205-a). Information 230-a may include a RAPID received via the RAR. The higher layer 205-a may interpret the contents of the information 230-a (e.g., may parse the transport block) to identify whether the RAPID in the information 230-a matches the RAPID from the message 215-a (e.g., the preamble sent by the UE 115-a). If the RAPID associated with the information 230-a and the RAPID associated with the message 215-a are the same, the UE 115-a may determine that the random access procedure was successfully completed. Alternatively, if the RAPID associated with the information 230-a and the RAPID associated with the message 215-a are different, or if the UE 115-a does not successfully receive or decode the message 220-a, the message 225-a, or both, the UE 115-a may continue to monitor the RAR from the network during the RAR window 235 until the timer expires. If the timer expires and the UE 115-a does not detect a PDSCH with a RAPID that is the same as the RAPID associated with the message 215-a (e.g., the UE 115-a receives one or more RARs from other network entities 105, or receives a RAR associated with a different random access procedure from the network entity 105-a, or the UE 115-a does not successfully receive or decode the message 220-a and / or the message 225-a), the random access procedure may be considered unsuccessful at T1. After initiating the random access procedure, the UE 115-a may set the preamble transmission counter to 1. Therefore, if the random access procedure is considered unsuccessful at T1, the UE 115-a may increment the preamble transmission counter by 1 so that the preamble transmission counter may be equal to 2.

[0110] If the random access process is unsuccessful, the network entity 105-a may trigger a RACH retransmission by repeating the process as described herein. The network entity 105-a may continue to trigger RACH retransmissions until the UE 115-a increments the preamble transmission counter to a threshold value. For example, if the UE 115-a starts the random access process with the preamble transmission counter set to a value of 1, the UE 115-a may complete three attempts to achieve a successful random access process until the threshold value of the preamble transmission counter is reached (e.g., at this time, the UE 115-a may consider that the random access process was not successfully completed). Therefore, if the UE 115-a or the network entity 105 configures the preamble transmission counter to have a threshold value of 4, then if the UE 115-a increments the preamble transmission counter to a value of 4 after one RACH transmission and two RACH retransmissions, the UE 115-a may consider that the random access process was not successfully completed.

[0111] For example, the network entity 105-a may send a PDCCH command 210-c, and the UE 115-a may receive the PDCCH command. In some examples, the UE 115-a may change the spatial domain transmit filter (e.g., may change the transmit beam) before PRACH retransmission (e.g., before the UE 115-a sends message 215-b). Additionally or alternatively, the physical layer of the UE 115-a may notify the higher layer of the UE 115-a (e.g., the higher layer 205-a) to suspend the power ramp counter. After initiating the random access process, the UE 115-a may set the power ramp counter to 1. If the UE 115-a does not change the spatial domain transmit filter before the PRACH retransmission, the physical layer of the UE 115-a may notify the higher layer (e.g., the higher layer 205-a) to increment the power ramp counter by 1, so that the UE 115-a may set the power ramp counter to 2. At T2, UE 115-a may adjust the preamble reception target power accordingly. In order to continue RACH retransmission, UE 115-a may send message 215-b to network entity 105-a. Based on receiving message 215-b, network entity 105-a may transmit RAR during second RAR window 235 by transmitting message 220-b, message 225-b, or both. After decoding the RAR, the physical layer of UE 115-a may send information 230-b to higher layer 205-a. If the RAPID from the RAR is different from the RAPID included in message 215-b, UE 115-a may continue to monitor the RAR during RAR window 235 until the timer expires. If the timer expires at T3 and UE 115-a does not detect a PDSCH with the same RAPID as the RAPID associated with message 215-b, UE 115-a may consider the random access process unsuccessful. Therefore, if the random access procedure is deemed unsuccessful, the UE 115 - a may increment the preamble transmission counter by 1, thereby setting the preamble transmission counter to 3.

[0112] In some examples, UE 115-a may increment the power ramp counter by 1 and set the power ramp counter to 3 at T4. Network entity 105-a may send a PDCCH command 210-d, and UE 115-a may receive the PDCCH command. In some examples, UE 115-a may change the spatial domain transmit filter before the second PRACH retransmission (e.g., before UE 115-a sends message 215-c). Additionally or alternatively, the physical layer of UE 115-a may notify the higher layer 205-a to suspend the power ramp counter. If UE 115-a does not change the spatial domain transmit filter before the second PRACH retransmission, the physical layer of UE 115-a may notify the higher layer 205-a to increment the power ramp counter by 1, so that UE 115-a may set the power ramp counter to 3. At T4, UE 115-a may adjust the preamble reception target power accordingly. To continue the second RACH retransmission, the UE 115-a may send a message 215-c to the network entity 105-a. Based on receiving the message 215-c, the network entity 105-a may transmit a RAR during the third RAR window 235 by transmitting a message 220-c, a message 225-c, or both. After decoding the RAR, the physical layer of the UE 115-a may send information 230-c to the higher layer 205-a. If the RAPID from the RAR is different from the RAPID included in the message 215-c, the UE 115-a may continue to monitor the RAR during the RAR window 235 until the timer expires. If the timer expires and the UE 115-a does not detect a PDSCH with a RAPID that is the same as the RAPID associated with the message 215-c, the UE 115-a may deem the random access procedure unsuccessful, and the UE 115-a may increment the preamble transmission counter by 1, so that the preamble transmission counter may be equal to 4. If the UE 115 - a or the network entity 105 configures the preamble transmission counter to have a threshold of 4, the UE 115 - a may consider that the random access procedure is not successfully completed at T5 .

[0113] In some cases, a MAC entity (e.g., at UE 115-a) may not be able to perform multiple random access procedures in parallel. For example, a serving cell may include multiple TRPs and may be associated with one or more (e.g., two) different timing advance groups (TAGs). In some examples, a first TRP may be associated with a network entity 105-a and a second TRP may be associated with a second network entity 105-b. Additionally or alternatively, the first TAG may include a first TRP and the second TAG may include a second TRP. Because the first TRP and the second TRP may be associated with different TAGs, uplink communications between the first TRP and the second TRP and UE 115-a may be asynchronous. When uplink communications from UE 115-a to the first TRP and the second TRP in the serving cell are asynchronous, once the random access procedure of the first TRP is completed, the random access procedure of the second TRP may be restricted to being performed by UE 115-a. In other words, uplink synchronization of the second TRP may not begin until uplink synchronization of the first TRP is completed. In some cases, UE 115-a may not be able to perform multiple random access procedures in parallel for a carrier aggregation scenario. For example, a serving cell may be associated with a first component carrier, and a second serving cell may be associated with a second component carrier. The component carriers may be associated with different TAGs. Therefore, UE 115-c may not be able to perform a random access procedure for a second serving cell associated with a second TAG until the random access procedure for a first serving cell associated with a first TAG is completed. Because UE 115-a may not be able to perform multiple random access procedures in parallel, the wireless communication network may experience additional delays in uplink synchronization of the TRP or component carriers in order to establish timing adjustment of the TRP or component carriers.

[0114] For example, if the network entity 105-b triggers the second random access procedure by transmitting the PDCCH command 210-b during the initial random access procedure triggered by the network entity 105-a, the UE 115-a may determine whether to continue the initial random access procedure and ignore the second random access procedure, or to end the initial random access procedure and start the second random access procedure. In other words, if the UE 115-a decides to continue the ongoing random access procedure initiated by the network entity 105-a, the UE 115-a may not have the ability to support another random access procedure at the same time. If the initial random access procedure is not successfully completed at T5, the UE 115-a may support the second random access procedure at T5 after the network entity 105-b triggers the second random access procedure by transmitting the PDCCH command 210-e. Additionally or alternatively, if the initial random access procedure completes successfully (e.g., if UE 115-a determines that the RAPID associated with information 230-b and the RAPID associated with message 215-b are the same), UE 115-a may support the second random access procedure. Thus, network entity 105-b may not be able to initiate the second random access procedure until after the initial random access procedure completes successfully or unsuccessfully.

[0115] In some examples, such as reference Figures 4 to 7 In more detail, UE 115-a may be able to support multiple parallel random access procedures rather than weighting to initiate a second random access procedure until after a first random access procedure has been successfully or unsuccessfully completed.

[0116] Figure 3 An example of a timeline 300 for supporting execution of multiple parallel random access procedures in accordance with one or more aspects of the present disclosure is illustrated. In some examples, the timeline 300 may be implemented by one or more aspects of the wireless communication system 100. For example, the UE 115-b may be an example of the UE 115, and the network entity 105-c may be an example of the network entity 105, as described with reference to FIG. Figure 1 In some examples, UE 115-b may initiate a second random access procedure by terminating the first ongoing random access procedure while performing the first ongoing random access procedure.

[0117] The higher layers 305-a of UE 115-b may start a random access procedure and may initiate a preamble transmission counter and a power ramp counter at T0. These counters may be associated with UE 115-b. In some examples, UE 115-a may set the preamble transmission counter to 1 and may set the power ramp counter to 1. In order to trigger a first random access procedure, the network entity 105-c (e.g., TRP) may send a PDCCH command 310-a, and UE 115-b may receive the PDCCH command. In some examples, the PDCCH command 310-a may indicate a RAPID, which may also be referred to as a RACH preamble index. Based on receiving the PDCCH command 310-a, UE 115-b may send (e.g., as part of a triggered random access procedure) a message 320-a (e.g., a RACH preamble (PRACH) transmission, such as message 1 of a four-step random access procedure or message A of a two-step random access procedure) to the network entity 105-c. Message 320-a may include a RAPID, a RACH timing, and other transmission-related parameters. Based on sending message 320-a, UE 115-b may monitor a random access response message (e.g., RAR) from the network (e.g., from network entity 105-c, network entity 105-d, or a different network entity) during the RAR window 340. For example, network entity 105-c may send a RAR message to UE 115-b. The RAR may include a PDCCH portion and a PDSCH portion. For example, the RAR may include message 325-a, which may include a PDCCH scrambled by a random access radio network temporary identifier (RA-RNTI). Additionally or alternatively, the RAR may include message 330-a, which may include a physical downlink shared channel (PDSCH).

[0118] In some examples, UE 115-b may decode message 325-a and message 330-a at a physical layer of UE 115-b. Based on decoding message 325-a and message 330-a, UE 115-b may transmit information 335-a (e.g., information received on the PDSCH by message 325-a via the received RAR) to a higher layer 205-a of UE 115-b. For example, based on decoding message 325-a and message 330-a, UE 115-b may forward a TB from the physical layer of UE 115-b to a medium access control (MAC) layer (e.g., higher layer 205-a). Information 335-a may include a RAPID received via the RAR. Higher layer 205-a may interpret the content of information 335-a (e.g., may parse the TB) to identify whether the RAPID in information 335-a matches the RAPID from message 320-a (e.g., a preamble sent by UE 115-b). If the RAPID associated with the information 335-a and the RAPID associated with the message 320-a are the same, the UE 115-b may determine that the random access procedure was successfully completed. Alternatively, if the RAPID associated with the information 335-a and the RAPID associated with the message 320-a are different, or if the UE 115-b did not successfully receive or decode the message 325-a, the message 330-a, or both, the UE 115-b may continue to monitor the RAR from the network during the RAR window 340 until the timer expires. If the timer expires and UE 115-b does not detect a PDSCH with a RAPID identical to the RAPID associated with message 320-a (e.g., UE 115-b receives one or more RARs from other network entities 105, or receives a RAR associated with a different random access procedure from network entity 105-c, or UE 115-b does not successfully receive or decode message 325-a and / or message 330-a), the random access procedure may be considered unsuccessful at T1. Therefore, if the random access procedure is considered unsuccessful at T1, UE 115-b may increment the preamble transmission counter by 1, thereby setting the preamble transmission counter to 2.

[0119] In some cases, the network entity 105-d may initiate a second random access procedure by terminating the first ongoing random access procedure during the first ongoing random access procedure. For example, the network entity 105-d may send a PDCCH command 310-b and the UE 115-b may receive the PDCCH command to trigger the second random access procedure. Based on receiving the PDCCH command 310-b, the UE 115-b may end the first ongoing random access procedure so as to start the second random access procedure at T2. The UE 115-b may set the preamble transmission counter to 1. Additionally or alternatively, the UE 115-b may set the power ramp counter to 1. In order to continue performing the second random access procedure, the UE 115-b may send a message 320-b to the network entity 105-d. Based on receiving the message 320-b, the network entity 105-d may transmit a RAR during the second RAR window 345 (e.g., the network entity 105-d may transmit a message 325-b and a message 330-b). After decoding the RAR, the physical layer of UE 115-b may send information 335-b to higher layers 305-a. If the RAPID from the RAR is different from the RAPID included in the message 320-b, UE 115-b may continue to monitor the RAR during the RAR window 345 until the timer expires. If the timer expires at T3 and UE 115-b does not detect a PDSCH with a RAPID that is the same as the RAPID associated with message 320-b, UE 115-b may consider the random access procedure to be unsuccessful. Therefore, UE 115-b may increment the preamble transmission counter by 1 at T3, thereby setting the preamble transmission counter to 2.

[0120] In some examples, UE 115-b may change the spatial domain transmit filter (e.g., may change the transmit beam) before PRACH retransmission (e.g., before UE 115-b sends message 320-c). Additionally or alternatively, the physical layer of UE 115-b may notify a higher layer of UE 115-b (e.g., higher layer 305-a) to suspend the power ramp counter. In other examples, UE 115-b may increment the power ramp counter by 1 to set the power ramp counter to 2 at T4. Thus, UE 115-b may adjust the preamble reception target power.

[0121] Because UE 115-b may consider the random access procedure to be unsuccessful, network entity 105-d may trigger RACH retransmission by repeating the process as described herein. Network entity 105-d may continue to trigger RACH retransmission until UE 115-a increments the preamble transmission counter to a threshold, or until UE 115-a determines that the RAPID indicated by the RAR matches the RAPID indicated by message A of the second random access procedure. For example, network entity 105-d may send a PDCCH order 310-c, and UE 115-b may receive the PDCCH order. In addition, UE 115-b may send message 320-c to network entity 105-d. Based on receiving message 320-c, network entity 105-d may transmit a RAR during a third RAR window 345 by transmitting message 325-c, message 330-c, or both. After decoding the RAR, the physical layer of UE 115-b may send information 335-c to the higher layer 305-a. If the RAPID associated with the information 335-c is the same as the RAPID associated with the message 320-c, the UE 115-b may consider that the second random access procedure is successful at T5. Therefore, the UE 115-b may support a new random access procedure after T5. For example, if the network entity 105-c may trigger a new random access procedure by transmitting a PDCCH command 310-d to the UE 115-b after T5. Therefore, the network entity 105-d may not be able to initiate a new random access procedure until the UE 115-b considers that the first random access procedure and the second random access procedure are completed successfully or unsuccessfully, respectively.

[0122] In some examples, such as reference Figures 4 to 7 As described in more detail, one or more UEs may support multiple parallel random access procedures (eg, random access procedures that at least partially overlap in time) if one or more conditions are met.

[0123] Figure 4 An example of a process flow 400 for supporting execution of multiple parallel random access procedures according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 400 can implement one or more aspects of the wireless communication system 100. For example, the UE 115-c can be as described in reference Figure 1 Additionally or alternatively, each of the network entities 105-e, 105-f, and 105-g may be as described in reference Figure 1 An example of the network entity 105 is described.

[0124] In some examples, if one or more conditions are met, a UE (e.g., UE 115-c) may support multiple parallel random access procedures being performed at any point in time in a MAC entity. For example, for two random access procedures associated with the same component carrier but different TAGs, if the control message used to trigger each random access procedure is associated with a different CORESET pool index, the UE 115-c may support multiple (e.g., up to two) ongoing random access procedures. For example, if a first random access procedure and a second random access procedure are associated with a first component carrier associated with a first TAG and a second TAG, the UE 115-c may determine that the random access procedures are supported simultaneously under the following condition: the first CORESET pool index of the PDCCH command included in the first control message received at 405-a is different from the second CORESET pool index of the PDCCH command included in the second control message received at 405-b.

[0125] In some examples, UE 115-c may receive signaling indicating a configuration associated with a network. For example, the signaling may indicate a configuration of a first component carrier associated with a first TAG and a second TAG. Additionally or alternatively, the signaling may indicate that a first random access procedure and a second random access procedure may be associated with the first component carrier. In some examples, a first TRP may be associated with a network entity 105-f and a second TRP may be associated with a network entity 105-g. Thus, the signaling may indicate that the first TRP and the second TRP are associated with a first component carrier and different TAGs, respectively. The first TRP and the second TRP may receive or utilize resources for performing communications with UE 115-c (e.g., from a SpCell or SCell). In some examples, UE 115-c may send a capability message to the network (e.g., via one or more network entities 105). The capability message may indicate that UE 115-c is capable of supporting multiple random access procedures that at least partially overlap in time. The capability message may include an indication of a threshold number of random access procedures that the UE is capable of supporting that at least partially overlap in time, an indication of one or more conditions under which the UE 115-c is capable of supporting random access procedures that at least partially overlap in time, or a combination thereof. In some examples, the UE 115-c may receive multiple PDCCH commands that trigger parallel random access procedures based on having sent the capability message.

[0126] At 405-a, the network entity 105-f may send a PDCCH command in a first control message that triggers a first random access procedure (e.g., a contention-free random access procedure), and the UE 115-c may receive the PDCCH command. The PDCCH command received at 405-a may be associated with a first CORESET pool index. In some examples, at 405-b, the network entity 105-g may send a PDCCH command in a second control message that triggers a second contention-free random access procedure, and the UE 115-c may receive the PDCCH command. The PDCCH command received at 405-b may be associated with a second CORESET pool index.

[0127] Based on receiving the first control message including the PDCCH command received at 405-a, at 410-a, UE115-c may send a first RACH preamble associated with a first random access procedure (e.g., using a first beam), and network entity 105-f may receive the first RACH preamble. Because the PDCCH command included in the first control message received at 405-a and the PDCCH command included in the second control message received at 405-b may each be associated with a different CORESET pool index, UE 115-c may determine that conditions for simultaneously performing the first random access procedure and the second random access procedure are met. Therefore, based on receiving the second control message including the PDCCH command at 405-b, at 410-b, UE 115-c may send a second RACH preamble, and network entity 105-g may receive the second RACH preamble (e.g., using a second beam). The second RACH preamble may be associated with a second random access procedure. UE 115-c may send a second random access preamble at 410-b before completing the first random access procedure. In some examples (e.g., as part of two parallel random access procedures), UE 115-c may receive a RAR at 415-a (e.g., associated with the first random access procedure and the preamble sent at 410-a) and receive a RAR at 415-b (e.g., associated with the second random access procedure and the preamble sent at 410-b). In some examples, UE 115-a may receive the first RAR and the second RAR via SpCell (e.g., at 415-a and at 415-b). In some examples, UE 115-a may receive the first RAR and the second RAR from network entity 105-e. Network entity 105-e may be a different network entity (e.g., a different TRP) than network entity 105-f and network entity 105-g. In some examples, network entity 105-e and network entity 105-f may be the same network entity 105, or may be collocated with each other. In some examples, network entity 105-e and network entity 105-g may be the same network entity 105, or may be collocated with each other.

[0128] In some examples, the UE 115-c may determine whether to suppress initiating a new random access procedure, or to initiate a new random access procedure while terminating an ongoing random access procedure (e.g., based on a condition that a control message triggering the random access procedure is associated with the same CORESET pool index as the control message used to trigger the ongoing random access procedure). For example, at 405-c, the network entity 105-f may send a first control message including a PDCCH command that triggers a first random access procedure, and the UE 115-c may receive the first control message. Before completing the first random access procedure, at 405-d, the network entity 105-f may send a second control message including a PDCCH command that triggers a second random access procedure, and the UE 115-c may receive the second control message. Based on receiving the first control message, at 410-c, the UE 115-c may send a random access preamble associated with the first random access procedure, and the network entity 105-f may receive the random access preamble. UE 115-c may determine that the PDCCH command received at 405-d is associated with the same CORESET pool index value as the PDCCH command received at 405-c. In such an example, UE 115-c may not support two simultaneous random access procedures. In such an example, UE 115-c may abandon the first random access procedure and initiate a second random access procedure associated with the PDCCH command received at 405-d, or may ignore the second random access procedure and continue with the first random access procedure (e.g., a random access preamble associated with the first random access procedure may be sent at 410 and a RAR may be received at 415-c from a network entity such as network entity 105-e).

[0129] In some examples, the first PDCCH command received at 405-c and the second PDCCH command received at 405-d may be associated with the same set of parameter values ​​(e.g., the same CORESET pool index value, the same RACH preamble, the same PRACH mask index, the same uplink carrier, etc.). In such examples, UE 115-c may consider the second random access procedure to be the same as the first random access procedure (e.g., and the random access procedure has not been initialized again).

[0130] If one or more conditions are met, the UE 115-c may be able to support up to a threshold number (e.g., two) of parallel random access procedures, as described herein. In some examples, the UE 115-c may receive (e.g., from the network entity 105) a PDCCH command (e.g., a third PDCCH command) that exceeds a threshold, and may refrain from initiating additional random access procedures in parallel based on the new PDCCH command exceeding the threshold number of parallel random access procedures.

[0131] Figure 5 An example of a process flow 500 for supporting execution of multiple parallel random access procedures in accordance with one or more aspects of the present disclosure is illustrated. The process flow 500 may include a UE 115-d and one or more network entities 105 (e.g., network entity 105-i, network entity 105-j, and network entity 105-h), which may be reference Figures 1 to 4 Examples of corresponding devices described. In some examples, network entity 105-i and network entity 105-j may be different network entities 105 (e.g., different TRPs), or may be the same network entity 105 or collocated network entities 105 (e.g., a single network entity 105 operating on CC1 and CC2 in a carrier aggregation configuration). In some examples, network entity 105-h may be a different network entity from network entity 105-i and network entity 105-j. In some examples, network entity 105-h may be the same network entity or collocated with one or both of network entity 105-i and network entity 105-j.

[0132] In some examples, such as reference Figure 5 As illustrated, one or more network entities 105 may trigger multiple random access procedures for different CCs (e.g., CC1 and CC2), and each CC may be configured with a single TAG. UE 115-d may support a threshold number (e.g., four) of ongoing random access procedures by its MAC entity at any point in time. UE 115-d may initiate a first random access procedure (e.g., a first CFRA procedure) triggered by a first PDCCH command for CC1 associated with TAG1. UE 115-d may also receive a second PDCCH command that triggers another random access procedure for CC2 associated with TAG2 (e.g., which is different from TAG1). In such examples, UE 115-d may support two ongoing random access procedures.

[0133] UE 115-c may receive (e.g., from network entity 105) signaling (e.g., configuration information such as RRC signaling, system information, etc.) indicating the configuration of a first TAG (e.g., TAG1) associated with a first CC (e.g., CC1) and a second TAG (e.g., TAG2) associated with a second CC (e.g., CC2). The first random access procedure may be associated with CC1, and the second random access procedure may be associated with CC2. At 505-a, UE 115-d may receive (e.g., from a first network entity 105-i associated with CC1 and TAG1) a first PDCCH command that triggers the first random access procedure. UE 115-d may also receive (e.g., from the first network entity 105-i or from the second network entity 105-j) a second PDCCH command that triggers the second random access procedure (e.g., before completing the first random access procedure). The second PDCCH command received at 505-b may be associated with CC2 and TAG2.

[0134] In some examples, UE 115-d may send a capability message to the network (e.g., via one or more network entities 105). The capability message may indicate that UE 115-d is capable of supporting multiple random access procedures that at least partially overlap in time. The capability message may include an indication of a threshold number of random access procedures that UE 115-d is capable of supporting that are at least partially overlapped in time, an indication of one or more conditions under which UE 115-d is capable of supporting random access procedures that are at least partially overlapped in time, or a combination thereof. In some examples, UE 115-d may receive multiple PDCCH commands that trigger parallel random access procedures based on having sent the capability message.

[0135] If TAG1 associated with CC1 (e.g., and the first PDCCH command received at 505-a) is different from TAG 2 associated with CC2 (e.g., and the second PDCCH command received at 505-b), UE 115-d may determine that one or more conditions are met. Because the TAGs of the two CCs triggered by the two PDCCH commands are different, UE 115-d may support multiple (e.g., up to four) parallel random access procedures. In such an example, UE 115-d may send a random access preamble for a first random access procedure at 510-a (e.g., using a first beam to network entity 105-i) before the first random access procedure expires, and may send a second preamble for a second random access procedure at 510-b (e.g., using a second beam to network entity 105-j). UE 115-d may send the first preamble at 510-a using the first beam, and may send the second preamble at 510-b using the second beam. At 515-a, UE 115-d may receive a first RAR associated with a first random access procedure (e.g., via SpCell). At 515-b, UE 115-d may receive a second RAR associated with a second random access procedure (e.g., via SpCell). UE 115-d may receive one or both of the first RAR and the second RAR via network entity 105-h (e.g., or any other network entity such as network entity 105-i and network entity 105-j).

[0136] If multiple random access procedures do not meet one or more conditions, UE 115-d may not support multiple parallel random access procedures. For example, if an ongoing random access procedure for CC1 associated with TAG1 triggered by a first PDCCH command is interrupted by a second PDCCH command that triggers another random access procedure for CC2 associated with a second TAG that is the same as the first TAG (e.g., TAG1), UE 115-d may not support parallel random access procedures. For example, at 505-c, UE 115-d may receive a first PDCCH command at 505-c that triggers a first random access procedure for CC1 associated with TAG1. At 505-d, before completing the first random access procedure, UE 115-d may receive a second PDCCH command for CC2 associated with TAG1. Because the TAGs of the first CC and the second CC triggered by the first PDCCH command and the second PDCCH command are the same, UE 115-d may refrain from initiating the second random access procedure before completing the first random access command.

[0137] The UE may determine (e.g., autonomously through a specific UE implementation) whether to continue an ongoing random access procedure or to start from a new random access procedure. In some examples, if one of CC1 and CC2 is SpCel, the UE 115-d may continue the current (e.g., first) random access procedure of the SpCell (e.g., Pcell or PScell) and may stop the current random access procedure of the other CC. In some examples, the UE 115-d may continue the current random access procedure of the lower CC (e.g., CC1) and may stop the random access procedure of the higher CC (e.g., CC2). For example, the UE 115-d may send a random access preamble for the first random access procedure at 510-c (e.g., to the network entity 105-i) (e.g., but may not initiate a second random access procedure). At 515-c, the UE 115-d may receive a RAR (e.g., via the SpCell). In some examples, UE 115 - d may receive a RAR at 515 - c from a network entity 105 - h (e.g., which may be the same network entity 105 as one or both of network entity 105 - i and network entity 105 - j or a different network entity 105 ).

[0138] If one or more conditions are met, UE 115-d may be able to support up to a threshold number (e.g., four) of parallel random access procedures, as described herein. In some examples, UE 115-d may receive (e.g., from network entity 105) a PDCCH command that exceeds a threshold (e.g., a fifth PDCCH command) and may refrain from initiating additional random access procedures in parallel based on the new PDCCH command exceeding the threshold number of parallel random access procedures.

[0139] Figure 6 An example of a process flow 600 for supporting execution of multiple parallel random access procedures in accordance with one or more aspects of the present disclosure is illustrated. The process flow 600 may include a UE 115-e and one or more network entities 105 (e.g., network entity 105-1, network entity 105-m, and network entity 105-k), which may be reference Figures 1 to 5 Examples of corresponding devices described. In some examples, network entity 105-1 and network entity 105-m may be different network entities 105 (e.g., different TRPs), or may be the same network entity 105 or collocated network entities 105 (e.g., a single network entity 105 operating on CC1 and CC2 in a carrier aggregation configuration). In some examples, network entity 105-h may be a different network entity from network entity 105-i and network entity 105-j. In some examples, network entity 105-h may be the same network entity or collocated with one or both of network entity 105-i and network entity 105-j.

[0140] In some examples, the UE 115-e may send a capability message to the network (e.g., via one or more network entities 105). The capability message may indicate that the UE 115-e is capable of supporting multiple random access procedures that at least partially overlap in time. The capability message may include an indication of a threshold number of random access procedures that the UE 115-e is capable of supporting that are at least partially overlapped in time, an indication of one or more conditions under which the UE 115-e is capable of supporting random access procedures that are at least partially overlapped in time, or a combination thereof. In some examples, the UE 115-e may receive multiple PDCCH commands that trigger parallel random access procedures based on having sent the capability message.

[0141] In some examples, one or more network entities 105 may trigger multiple random access procedures for the same CC or different CCs, where at least one CC is configured with two TAGs. For example, UE 115-e may receive (e.g., from a network entity) signaling (e.g., RRC signaling, system information, dynamic signaling, etc.) indicating the configuration of a first CC set (e.g., CC1 and CC2) and a second CC set (e.g., CC3 and CC4). Each CC in the first CC set may be associated with one or more TAGs in the first TAG set, and each CC in the second CC set may be associated with one or more TAGs in the second TAG set. In such examples, if one or more conditions are met, UE 115-e may support a threshold number (e.g., four) of random access procedures in progress at any point in time at its MAC entity. For example, UE 115-e may receive a first PDCCH command that triggers an ongoing random access procedure for a first CC (e.g., CC1) belonging to a first CC set. UE 115-e may receive a second PDCCH command that triggers another random access procedure (e.g., a CFRA procedure) for a second CC (e.g., CC3) belonging to a second CC set. In such an example, if CC1 belongs to a first CC set and CC3 belongs to a second CC set, the UE 115-e may determine that one or more conditions are met. For example, the set of CCs may be determined based on TAGs (e.g., different TAG sets associated with CCs in each group of CCs). The UE 115-e may support parallel random access procedures for CCs in different CC sets.

[0142] For example, the UE may receive at 605-a (e.g., from the network entity 105-1) a first PDCCH command that triggers a first random access procedure for CC1 in the first CC set. At 605-c, the UE 115-e may receive (e.g., from the network entity 105-1) a second PDCCH command that triggers a second random access procedure for CC3 in the second CC set. Because the CCs are different, because the CCs belong to different CC sets, or both, the UE 115-e may support both the first random access procedure and the second random access procedure. In such an example, the UE 115-e may send a random access preamble associated with the first random access procedure at 605-a (e.g., to the network entity 105-1), and may send a second random access preamble associated with the second random access procedure at 605-c (e.g., to the network entity 105-1). Similarly, UE 115-e may receive a first RAR for a first random access procedure via SpCell (e.g., from network entity 105-k) at 615-a, and may receive a second RAR for a second random access procedure via SpCell (e.g., from network entity 105-k) at 615-c. Thus, UE 115-e may support parallel random access procedures across different CC sets.

[0143] In some examples, the UE 115-e may also support parallel random access procedures within a CC set. For example, the UE 115-e may perform a triggered ongoing random access procedure for a first CC belonging to a first CC set, the first CC being triggered by a first PDCCH command associated with a first CORESET pool index. The UE 115-e may also receive a second PDCCH command before completing the ongoing random access procedure, the second PDCCH command triggering another random access procedure for a second CC belonging to the same CC set as the first CC having a different CORESET pool index. The first CC and the second CC within the CC set may be the same CC or different CCs. In such examples, if the CORESET pool indexes of two PDCCH commands associated with the same CC set are different, the UE 115-e may determine that one or more conditions are satisfied.

[0144] For example, before completing the triggered first random access procedure at 605-a, UE 115-e may receive a PDCCH command at 605-b (e.g., from network entity 105-m) that triggers a third random access procedure for CC2 in the first CC set. The CORESET pool index (e.g., CORESETPoolindex 0) of the first PDCCH command received at 605-a may be different from the CORESET pool index (e.g., CORESETPoolindex 1) of the third PDCCH command received at 605-b. Because the CORESET pool index of the PDCCH command received at 605-a and the CORESET pool index of the PDCCH command received at 605-b are different, UE 115-e may support two parallel random access procedures. Similarly, if the UE receives a fourth PDCCH command triggering a fourth random access procedure associated with CC4 in the second CC set (e.g., from the network entity 105-m before the random access procedure triggered at 605-c expires), when the CORESET pool index of the PDCCH command is different, UE115-e may support parallel random access procedures for the random access procedures triggered at 605-c and 605-d.

[0145] In such an example, the UE 115-e may support a first random access procedure triggered at 605-a and a second random access procedure triggered at 605-c, provided that the two random access procedures are associated with CCs in different CC sets (e.g., CC1 in the first CC set and CC3 in the second CC set). Additionally or alternatively, if the CORESET pool indexes of the random access procedures triggered for the same CC set are different, the UE 115-e may also support parallel random access procedures triggered at 605-a and 605-b, and parallel random access procedures triggered at 605-c and 605-d. In such an example, the UE 115-e may support up to four parallel random access procedures. In such an example, UE 115-e may send random access preambles for four corresponding random access processes at 610-a (e.g., using a first beam), 610-b (e.g., using a second beam), 610-c (e.g., using a first beam), and 610-d (e.g., using a second beam), and may receive RARs at 615-a, 615-b, 615-c, and 615-d, respectively.

[0146] If one or more conditions are not met, the UE 115-e may not support parallel random access procedures at the same time. For example, the UE 115-e may perform an ongoing random access procedure for a first CC belonging to a first CC set, the first CC being triggered by a first PDCCH command associated with a first CORESET pool index value. The UE 115-e may receive a second PDCCH command associated with a second CORESET pool index value that is the same as the first CORESET pool index value, the second PDCCH command triggering a second random access procedure for a second CC belonging to the same CC set as the first CC. In such examples, the UE 115-e may not support two random access procedures in parallel (e.g., at least partially overlapping in time). For example, CCs may be divided into CC sets, and each group of CCs may be configured with a different TAG (e.g., each CC in the first CC set may be associated with one or both of TAG1 and TAG2, and each CC in the second CC set may be associated with one or both of TAG3 and TAG4).

[0147] For example, at 605-e, UE 115-e may receive a PDCCH command that triggers a first random access procedure for CC1 in the first CC set. At 605-f (e.g., before completing the first random access procedure), UE 115-e may receive a second PDCCH command that triggers a second random access procedure for CC1 or CC2 in the first CC set. If both the first PDCCH command and the second PDCCH command are associated with the same CORESET pool index (e.g., CORESETPoolindex0), UE 115-e may not support both the first random access procedure and the second random access procedure. Similarly, at 605-g, UE 115-e may receive a third PDCCH command that triggers a random access procedure for CC3 in the second CC set.

[0148] At 605-h (e.g., before completing the third random access procedure, the first random access procedure, or both), the UE 115-e may receive a fourth PDCCH command that triggers a random access procedure for CC3 or CC4 in the second CC set. If both the third PDCCH command and the fourth PDCCH command are associated with the same CORESET pool index (e.g., CORESETPoolindex 1), the UE 115-e may not support both the third random access procedure and the fourth random access procedure in parallel (e.g., at least partially overlapping in time). Therefore, the UE 115-e may support one random access procedure associated with the first CC set (e.g., the first random access procedure triggered at 605-e) and one random access procedure associated with the second CC set (e.g., the fourth random access procedure triggered at 605-h), but may not support the second random access procedure or the third random access procedure. In such an example, UE 115-e may send a first random access preamble associated with a first random access procedure at 610-e (e.g., to network entity 105-l), and may send a second random access preamble associated with a fourth random access procedure at 610-f (e.g., to network entity 105-m). At 615-e, UE 115-e may receive a first RAR associated with the first random access procedure via SpCell (e.g., from network entity 105-k). At 615-f, UE 115-e may receive a second RAR associated with the fourth random access procedure via SpCell (e.g., from network entity 105-k).

[0149] If one or more conditions are met, the UE 115-e may be able to support up to a threshold number (e.g., four) of parallel random access procedures, as described herein. In some examples, the UE 115-e may receive (e.g., from the network entity 105) a PDCCH command that exceeds the threshold (e.g., a fifth PDCCH command) and may refrain from initiating additional random access procedures in parallel based on the new PDCCH command exceeding the threshold number of parallel random access procedures.

[0150] Figure 7 An example of a process flow 700 for supporting execution of multiple parallel random access procedures in accordance with one or more aspects of the present disclosure is illustrated. The process flow 700 may include a UE 115-f and one or more network entities 105 (e.g., network entity 105-n, network entity 105-o, and network entity 105-p), which may be reference Figures 1 to 6Examples of corresponding devices described. In some examples, network entity 105-o and network entity 105-p may be different network entities 105 (e.g., different TRPs), or may be the same network entity 105 or collocated network entities 105 (e.g., a single network entity 105 operating on CC1 and CC2 in a carrier aggregation configuration). In some examples, network entity 105-n may be a different network entity from network entity 105-o and network entity 105-p. In some examples, network entity 105-n may be the same network entity or collocated with one or both of network entity 105-o and network entity 105-p.

[0151] In some examples, UE 115-f may send a capability message to the network (e.g., via one or more network entities 105). The capability message may indicate that UE 115-f is capable of supporting multiple random access procedures that at least partially overlap in time. The capability message may include an indication of a threshold number of random access procedures that UE 115-f is capable of supporting that are at least partially overlapped in time, an indication of one or more conditions under which UE 115-f is capable of supporting random access procedures that are at least partially overlapped in time, or a combination thereof. In some examples, UE 115-f may receive multiple PDCCH commands that trigger parallel random access procedures based on having sent the capability message.

[0152] In some examples, one or more network entities 105 may trigger multiple random access procedures for the same CC or different CCs or both, and at least one CC may be configured with two different TAGs. For example, UE 115-f may receive signaling (e.g., RRC signaling, system information, dynamic signaling, etc.) indicating a first CC (e.g., CC1) associated with one or more TAGs (e.g., TAG1 and TAG2) and a second CC (e.g., CC2) associated with at least a third timing advance group (e.g., associated with TAG1 and TAG3). In some examples, the first random access procedure and the second random access procedure may be associated with CC1.

[0153] If one or more conditions are met, the UE 115-f may support a threshold number (e.g., four) of parallel random access procedures. For example, the UE 115-f may perform an ongoing random access procedure for CC1 triggered by a first PDCCH command associated with a first CORESET pool index value. The UE 115-f may receive a second PDCCH command that triggers another random access procedure for a second CC associated with a second CORESET pool index value different from the first CORESET pool index value. In such an example, the UE 115-f may support two parallel random access procedures (e.g., as described in reference to FIG. 1 ). Figure 4 Such techniques may also be performed for different CCs, and the first random access procedure and the second random access procedure may be used for different TAGs (e.g., TAG1 and TAG2). Additionally, the UE 115-f may receive another PDCCH command triggering another random access procedure for a CC (e.g., CC2), and the same CORESET pool index as the first PDCCH command. In such examples, if the additional CORESET pool index value is not associated with a common TAG between the first CC and the second CC (e.g., the first CC and the second CC are different), the UE 115-f may support the additional random access procedure.

[0154] For example, at 705-a, UE 115-f may receive a first PDCCH command associated with a first random access procedure for CC1. The first PDCCH command may be associated with a first CORESET pool index associated with TAG1. At 705-b, UE 115-f may receive a second PDCCH command associated with a second random access procedure for CC1. The second PDCCH command may be associated with a second CORESET pool index associated with TAG 2 and may be different from the first CORESET pool index. In such examples, if the CORESET pool indexes are different, UE 115-f may determine that one or more rules are satisfied and may support both the first random access procedure and the second random access procedure in parallel (e.g., a random access preamble may be sent at 710-a using a first beam for the first random access procedure and a RAR may be received at 715-a, and a second random access preamble may be sent at 710-b using a second beam for the second random access procedure and a second RAR may be received at 715-b).

[0155] At 705-c, UE 115-f may receive a third PDCCH command (e.g., before completing the first random access procedure, the second random access procedure, or both). The third PDCCH command may be associated with TAG3 and CC2, but may have the same CORESET pool index as the first PDCCH command received at 705-a. In such an example, if the CORESET pool index values ​​of the first PDCCH command and the third PDCCH command are not associated with a common TAG between the first CC and the second CC, UE 115-e may determine that one or more conditions are met. That is, if the third PDCCH command is associated with a CORESET pool index associated with TAG1 (e.g., a common TAG between the first PDCCH command and the third PDCCH command), UE 115-f may not support the third random access procedure. However, if the third PDCCH command received at 705-c is associated with TAG3 (e.g., which is different from TAG1), UE 115-f may support the first random access procedure and the third random access procedure in parallel (e.g., UE 115-f may send a third random access preamble code at 710-c using the second beam and may receive a third RAR at 715-c).

[0156] If a second PDCCH command associated with a second CC associated with a second CORESET pool index value (e.g., the same as the first CORESET pool index value) is associated with a common TAG between the first CC and the second CC, then the UE 115-f may not support multiple random access procedures in parallel. This may occur because different CCs may be associated with the same TAG (e.g., CC1 may be associated with TAG1 and TAG2, and CC2 may be associated with TAG2 and TAG3, or CC1 may be associated with TAG 1 and TAG2, and CC2 may be associated with TAG 1 and TAG 2).

[0157] If one or more conditions are met, UE 115-f may be able to support up to a threshold number (e.g., four) of parallel random access procedures, as described herein. In some examples, UE 115-f may receive (e.g., from network entity 105) a PDDCH (e.g., a fifth PDCCH order) that exceeds a threshold, and may refrain from initiating additional random access procedures in parallel based on the new PDCCH order exceeding the threshold number of parallel random access procedures.

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

[0159] The receiver 810 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to performing multiple parallel random access procedures), user data, control information, or any combination thereof. The information may be communicated to other components of the device 805. The receiver 810 may utilize a single antenna or a set of multiple antennas.

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

[0161] The communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof or various components thereof may be examples of means for performing aspects of performing multiple parallel random access procedures as described herein. For example, the communication manager 820, the receiver 810, the transmitter 815, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

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

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

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

[0165] Additionally or alternatively, according to the examples disclosed herein, the communication manager 820 may support wireless communications at the UE. For example, the communication manager 820 may be configured to or otherwise support a device for receiving a first control message that triggers a first random access procedure. The communication manager 820 may be configured to or otherwise support a device for sending a first random access preamble message associated with a first random access procedure based on receiving the first control message. The communication manager 820 may be configured to or otherwise support a device for receiving a second control message that triggers a second random access procedure. The communication manager 820 may be configured to or otherwise support a device for sending a second random access preamble message associated with a second random access procedure based on receiving a second control message before completing the first random access procedure and based on satisfying one or more conditions.

[0166] By including or configuring the communication manager 820 according to the examples described herein, the device 805 (e.g., a processor that controls or otherwise couples the receiver 810, the transmitter 815, the communication manager 820, or a combination thereof) may support techniques for random access procedures that result in more efficient use of communication resources, reduced latency, and high reliability communications. For example, the device 805 may support the execution of multiple parallel random access procedures with multiple TRPs or CCs. By supporting multiple parallel random access procedures with multiple TRPs or CCs, the latency of uplink synchronization may be reduced. Supporting multiple random access procedures simultaneously may provide improved resource utilization compared to performing multiple random access procedures individually. In addition, supporting multiple parallel random access procedures may reduce the amount of failed or discarded communications. For example, if a second random access procedure is triggered before completing a first random access procedure, the device 805 may support the simultaneous execution of a first RACH procedure and a second RACH procedure, rather than discarding one of the first RACH procedure and the second RACH procedure. By reducing the amount of failed or discarded communications, the device 805 may support improved communication reliability, reduced latency, and an improved user experience.

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

[0168] The receiver 910 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to performing multiple parallel random access procedures), user data, control information, or any combination thereof. The information may be communicated to other components of the device 905. The receiver 910 may utilize a single antenna or a set of multiple antennas.

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

[0170] The device 905 or its various components may be examples of means for performing various aspects of performing multiple parallel random access procedures as described herein. For example, the communication manager 920 may include a control message interface 925, a preamble message interface 930, or any combination thereof. The communication manager 920 may be an example of various aspects of the communication manager 820 as described herein. In some examples, the communication manager 920 or its various components may be configured to use or otherwise cooperate with the receiver 910, the transmitter 915, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0171] According to the examples disclosed herein, the communication manager 920 may support wireless communications at the UE. The control message interface 925 may be configured to or otherwise support a device for receiving a first control message that triggers a first random access procedure. The preamble message interface 930 may be configured to or otherwise support a device for sending a first random access preamble message associated with a first random access procedure based on receiving the first control message. The control message interface 925 may be configured to or otherwise support a device for receiving a second control message that triggers a second random access procedure. The preamble message interface 930 may be configured to or otherwise support a device for sending a second random access preamble message associated with a second random access procedure based on receiving a second control message before completing the first random access procedure and based on satisfying one or more conditions.

[0172] Fig.10 A block diagram 1000 of a communication manager 1020 supporting execution of multiple parallel random access procedures according to one or more aspects of the present disclosure is shown. The communication manager 1020 may be an example of aspects of the communication manager 820, the communication manager 920, or both as described herein. The communication manager 1020 or its various components may be an example of an apparatus for performing various aspects of executing multiple parallel random access procedures as described herein. For example, the communication manager 1020 may include a control message interface 1025, a preamble message interface 1030, a configuration message interface 1035, a condition determination component 1040, a RA message interface 1045, a RAR message interface 1050, a capability message interface 1055, a RACH message interface 1060, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0173] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1020 may support wireless communications at the UE. The control message interface 1025 may be configured to or otherwise support a device for receiving a first control message that triggers a first random access procedure. The preamble message interface 1030 may be configured to or otherwise support a device for sending a first random access preamble message associated with a first random access procedure based on receiving the first control message. In some examples, the control message interface 1025 may be configured to or otherwise support a device for receiving a second control message that triggers a second random access procedure. In some examples, the preamble message interface 1030 may be configured to or otherwise support a device for sending a second random access preamble message associated with a second random access procedure based on receiving a second control message before completing the first random access procedure and based on satisfying one or more conditions.

[0174] In some examples, the configuration message interface 1035 can be configured to or otherwise support means for receiving signaling indicating configuration of a first component carrier associated with a first timing advance group and a second timing advance group, wherein the first random access procedure and the second random access procedure are associated with the first component carrier. In some examples, the condition determination component 1040 can be configured to or otherwise support means for determining that one or more conditions are satisfied based on a first control resource set pool index associated with the first control message being different from a second control resource set pool index associated with the second control message.

[0175] In some examples, the configuration message interface 1035 can be configured to or otherwise support means for receiving signaling indicating configuration of a first timing advance group associated with a first component carrier and a second timing advance group associated with a second component carrier, wherein the first random access procedure is associated with the first component carrier and the second random access procedure is associated with the second component carrier. In some examples, the condition determination component 1040 can be configured to or otherwise support means for determining that one or more conditions are satisfied based on the first component carrier being associated with the first timing advance group and the second component carrier being associated with a second timing advance group different from the first timing advance group.

[0176] In some examples, the configuration message interface 1035 may be configured as or otherwise support means for receiving signaling indicating configuration of a first component carrier set and a second component carrier set, wherein each component carrier in the first component carrier set is associated with one or more timing advance groups in the first timing advance group set, and each component carrier in the second component carrier set is associated with one or more timing advance groups in the second timing advance group set. In some examples, the condition determination component 1040 may be configured as or otherwise support means for determining that one or more conditions are satisfied based on triggering a first random access procedure for a first component carrier in the first component carrier set and triggering a second random access procedure for a first component carrier in the second component carrier set.

[0177] In some examples, the UE supports up to two random access procedures that at least partially overlap in time for the first set of component carriers and up to two random access procedures that at least partially overlap in time for the second set of component carriers based on satisfying one or more conditions.

[0178] In some examples, condition determination component 1040 may be configured or otherwise support means for determining that one or more conditions are satisfied based on each random access procedure associated with a corresponding component carrier set being associated with a different control resource set pool index.

[0179] In some examples, the configuration message interface 1035 may be configured as or otherwise support a device for receiving signaling indicating the configuration of a first component carrier associated with a first timing advance group and a second timing advance group and a second component carrier associated with at least a third timing advance group, and wherein the first random access procedure and the second random access procedure are associated with the first component carrier. In some examples, the condition determination component 1040 may be configured as or otherwise support a device for determining that one or more conditions are satisfied based on that a first control resource set pool index associated with the first control message is different from a second control resource set pool index associated with the second control message. In some examples, the control message interface 1025 may be configured as or otherwise support a device for receiving a third control message that triggers a third random access procedure associated with the second component carrier and the third timing advance group. In some examples, the condition determination component 1040 may be configured as or otherwise support a device for determining that one or more conditions are satisfied based at least in part on that the third timing advance group is different from the first timing advance group and the second timing advance group. In some examples, the preamble message interface 1030 may be configured as or otherwise support a device for sending a third random access preamble message associated with a third random access process based on receiving a third control message based on satisfying one or more conditions before completing the first random access process.

[0180] In some examples, the RA message interface 1045 may be configured as or otherwise support means for receiving a first random access response message associated with a first random access procedure based on sending a first random access preamble message. In some examples, the RAR message interface 1050 may be configured as or otherwise support means for receiving a second random access response message associated with a second random access procedure based on sending a second random access preamble message.

[0181] In some examples, the capability message interface 1055 may be configured as or otherwise support a device for sending a capability message indicating that the UE is capable of supporting multiple random access processes that at least partially overlap in time, wherein receiving a second control message that triggers a second random access process is based on sending the capability message.

[0182] In some examples, the capability message includes: an indication of a threshold number of random access procedures that the UE is capable of supporting that at least partially overlap in time, an indication of one or more conditions, or both.

[0183] In some examples, the preamble message interface 1030 may be configured or otherwise support means for receiving a third control message that triggers a third random access procedure before completing the first random access procedure. In some examples, the condition determination component 1040 may be configured or otherwise support means for determining that one or more conditions are not satisfied for the third random access procedure. In some examples, the RACH message interface 1060 may be configured or otherwise support means for suppressing initiation of the third random access procedure based on the determination, or initiating the third random access procedure and terminating the first random access procedure.

[0184] In some examples, the preamble message interface 1030 may be configured or otherwise support means for receiving a third control message that triggers a third random access procedure before completing the first random access procedure. In some examples, the condition determination component 1040 may be configured or otherwise support means for determining that the third random access procedure exceeds a threshold number of random access procedures supported by the UE that overlap at least partially in time. In some examples, the RACH message interface 1060 may be configured or otherwise support means for refraining from initiating the third random access procedure based on the determination.

[0185] In some examples, control message interface 1025 may be configured or otherwise support means for receiving a first control message, including receiving a first control message from a first network entity. In some examples, control message interface 1025 may be configured or otherwise support means for receiving a second control message, including receiving a second control message from a second network entity.

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

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

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

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

[0190] Processor 1140 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1140 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1140. Processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1130) so that device 1105 performs various functions (e.g., supporting functions or tasks of executing multiple parallel random access processes). For example, device 1105 or a component of device 1105 may include processor 1140 and memory 1130 coupled to processor 1140, and processor 1140 and memory 1130 are configured to perform various functions described herein.

[0191] Additionally or alternatively, according to the examples disclosed herein, the communication manager 1120 may support wireless communications at the UE. For example, the communication manager 1120 may be configured to or otherwise support a device for receiving a first control message that triggers a first random access procedure. The communication manager 1120 may be configured to or otherwise support a device for sending a first random access preamble message associated with the first random access procedure based on receiving the first control message. The communication manager 1120 may be configured to or otherwise support a device for receiving a second control message that triggers a second random access procedure. The communication manager 1120 may be configured to or otherwise support a device for sending a second random access preamble message associated with the second random access procedure based on receiving the second control message before completing the first random access procedure and based on satisfying one or more conditions.

[0192] By including or configuring a communication manager 1120 according to an example as described herein, the device 1105 may support techniques for random access procedures that result in more efficient use of communication resources, reduced latency, improved communication reliability, and improved user experience. For example, the device 805 may support the execution of multiple parallel random access procedures with multiple TRPs or CCs. By supporting multiple parallel random access procedures with multiple TRPs or CCs, the latency of uplink synchronization may be reduced. Compared to performing multiple random access procedures individually, supporting multiple random access procedures simultaneously may provide improved resource utilization. In addition, supporting multiple parallel random access procedures may reduce the amount of failed or discarded communications. For example, if a second random access procedure is triggered before completing the first random access procedure, the device 805 may support the simultaneous execution of a first RACH procedure and a second RACH procedure, rather than discarding one of the first RACH procedure and the second RACH procedure. By reducing the amount of failed or discarded communications, the device 805 may support improved communication reliability and improved user experience.

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

[0194] Fig.12 A flowchart is shown that illustrates a method 1200 for supporting execution of multiple parallel random access procedures according to one or more aspects of the present disclosure. The operations of the method 1200 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a UE or a component thereof as described herein. Figures 1 to 11 The UE 115 described herein performs. 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.

[0195] At 1205, the method may include receiving a first control message that triggers a first random access procedure. The operations of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed as described in reference to Fig.10 The control message interface 1025 described above is implemented.

[0196] At 1210, the method may include sending a first random access preamble message associated with a first random access procedure based on receiving the first control message. The operations of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed as described in reference to Fig.10 The preamble message interface 1030 described above is implemented.

[0197] At 1215, the method may include receiving a second control message that triggers a second random access procedure. The operations of 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1215 may be performed as described in reference to Fig.10 The control message interface 1025 described above is implemented.

[0198] At 1220, the method may include: before completing the first random access procedure and based on satisfying one or more conditions, sending a second random access preamble message associated with the second random access procedure based on receiving the second control message. The operations of 1220 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1220 may be performed as described in reference to Fig.10 The preamble message interface 1030 described above is implemented.

[0199] Fig.13 A flowchart is shown that illustrates a method 1300 for supporting execution of multiple parallel random access procedures according to one or more aspects of the present disclosure. The operations of the method 1300 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 11The UE 115 described herein performs. 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.

[0200] At 1305, the method may include receiving signaling indicating configuration of a first component carrier associated with a first timing advance group and a second timing advance group, wherein the first random access procedure and the second random access procedure are associated with the first component carrier. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Fig.10 The configuration message interface 1035 described is implemented.

[0201] At 1310, the method may include receiving a first control message that triggers a first random access procedure. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Fig.10 The control message interface 1025 described above is implemented.

[0202] At 1315, the method may include sending a first random access preamble message associated with the first random access procedure based on receiving the first control message. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference to Fig.10 The preamble message interface 1030 described above is implemented.

[0203] At 1320, the method may include receiving a second control message that triggers a second random access procedure. The operations of 1320 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1320 may be performed as described in reference to Fig.10 The control message interface 1025 described above is implemented.

[0204] At 1325, the method may include determining that one or more conditions are satisfied based on that a first control resource set pool index associated with the first control message is different from a second control resource set pool index associated with the second control message. The operations of 1325 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1325 may be performed as described in reference to Fig.10 The described condition determines the component 1040 to execute.

[0205] At 1330, the method may include: before completing the first random access procedure and based on satisfying one or more conditions, sending a second random access preamble message associated with the second random access procedure based on receiving the second control message. The operations of 1330 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1330 may be performed as described in reference to Fig.10 The preamble message interface 1030 described above is implemented.

[0206] Fig.14 A flow chart is shown that illustrates a method 1400 for supporting execution of multiple parallel random access procedures according to one or more aspects of the present disclosure. 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 herein. Figures 1 to 11 The UE 115 described herein performs. 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.

[0207] At 1405, the method may include receiving signaling indicating configuration of a first timing advance group associated with a first component carrier and a second timing advance group associated with a second component carrier, wherein the first random access procedure is associated with the first component carrier and the second random access procedure is associated with the second component carrier. 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 Fig.10 The configuration message interface 1035 described is implemented.

[0208] At 1410, the method may include receiving a first control message that triggers a first random access procedure. 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 Fig.10 The control message interface 1025 described above is implemented.

[0209] At 1415, the method may include sending a first random access preamble message associated with the first random access procedure based on receiving the first control message. 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 Fig.10 The preamble message interface 1030 described above is implemented.

[0210] At 1420, the method may include receiving a second control message that triggers a second random access procedure. 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 Fig.10The control message interface 1025 described above is implemented.

[0211] At 1425, the method may include determining that one or more conditions are satisfied based on the first component carrier being associated with the first timing advance group and the second component carrier being associated with a second timing advance group different from the first timing advance group. The operations of 1425 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1425 may be performed as described in reference to Fig.10 The described condition determines the component 1040 to execute.

[0212] At 1430, the method may include: before completing the first random access procedure and based on satisfying one or more conditions, sending a second random access preamble message associated with the second random access procedure based on receiving the second control message. The operations of 1430 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1430 may be performed as described in reference to Fig.10 The preamble message interface 1030 described above is implemented.

[0213] Fig.15 A flowchart is shown that illustrates a method 1500 for supporting execution of multiple parallel random access procedures according to one or more aspects of the present disclosure. 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 11 The UE 115 described herein performs. 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.

[0214] At 1505, the method may include receiving signaling indicating a configuration of a first component carrier set and a second component carrier set, wherein each component carrier in the first component carrier set is associated with one or more timing advance groups in the first timing advance group set, and each component carrier in the second component carrier set is associated with one or more timing advance groups in the second timing advance group set. 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 Fig.10 The configuration message interface 1035 described is implemented.

[0215] At 1510, the method may include receiving a first control message that triggers a first 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 Fig.10 The control message interface 1025 described above is implemented.

[0216] At 1515, the method may include sending a first random access preamble message associated with the first random access procedure based on receiving the first control message. 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 Fig.10 The preamble message interface 1030 described above is implemented.

[0217] At 1520, the method may include receiving a second control message that triggers a second random access procedure. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Fig.10 The control message interface 1025 described above is implemented.

[0218] At 1525, the method may include determining that one or more conditions are satisfied based on triggering a first random access procedure for a first component carrier in a first component carrier set and triggering a second random access procedure for a first component carrier in a second component carrier set. The operations of 1525 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1525 may be performed as described in reference to Fig.10 The described condition determines the component 1040 to execute.

[0219] At 1530, the method may include: before completing the first random access procedure and based on satisfying one or more conditions, sending a second random access preamble message associated with the second random access procedure based on receiving the second control message. The operations of 1530 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1530 may be performed as described in reference to Fig.10 The preamble message interface 1030 described above is implemented.

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

[0221] Aspect 1: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receive a first control message triggering a first random access procedure; send a first random access preamble message associated with the first random access procedure based at least in part on receiving the first control message; receive a second control message triggering a second random access procedure; and before completing the first random access procedure and based at least in part on satisfying one or more conditions, send a second random access preamble message associated with the second random access procedure based at least in part on receiving the second control message.

[0222] Aspect 2: An apparatus according to Aspect 1, wherein the instructions are also executable by the processor to cause the apparatus to: receive signaling indicating the configuration of a first component carrier associated with a first timing advance group and a second timing advance group, wherein the first random access procedure and the second random access procedure are associated with the first component carrier; and determine that the one or more conditions are satisfied based at least in part on the fact that a first control resource pool index associated with the first control message is different from a second control resource pool index associated with the second control message.

[0223] Aspect 3: An apparatus according to any one of Aspects 1 to 2, wherein the instruction is also executable by the processor to cause the apparatus to: receive signaling indicating the configuration of a first timing advance group associated with a first component carrier and a second timing advance group associated with a second component carrier, wherein the first random access procedure is associated with the first component carrier and the second random access procedure is associated with the second component carrier; and determine that the one or more conditions are satisfied based at least in part on the first component carrier being associated with the first timing advance group and the second component carrier being associated with the second timing advance group different from the first timing advance group.

[0224] Aspect 4: An apparatus according to any one of Aspects 1 to 3, wherein the instruction is also executable by the processor to cause the apparatus to: receive signaling indicating the configuration of a first component carrier set and a second component carrier set, wherein each component carrier in the first component carrier set is associated with one or more timing advance groups in a first timing advance group set, and each component carrier in the second component carrier set is associated with one or more timing advance groups in a second timing advance group set; and determine that the one or more conditions are satisfied based at least in part on triggering the first random access process for the first component carrier in the first component carrier set and triggering the second random access process for the first component carrier in the second component carrier set.

[0225] Aspect 5: An apparatus according to Aspect 4, wherein the UE supports a maximum of two random access procedures that are at least partially overlapping in time for the first component carrier set and a maximum of two random access procedures that are at least partially overlapping in time for the second component carrier set based at least in part on satisfying the one or more conditions.

[0226] Aspect 6: An apparatus according to Aspect 5, wherein the instructions are also executable by the processor to enable the apparatus to: determine that the one or more conditions are satisfied based at least in part on each random access process associated with the corresponding component carrier set being associated with a different control resource set pool index.

[0227] Aspect 7: An apparatus according to any one of Aspects 1 to 6, wherein the instruction is also executable by the processor to cause the apparatus to: receive signaling indicating the configuration of a first component carrier associated with a first timing advance group and a second timing advance group and a second component carrier associated with at least a third timing advance group, and wherein the first random access procedure and the second random access procedure are associated with the first component carrier; determine that the one or more conditions are satisfied based at least in part on the first control resource pool index associated with the first control message being different from the second control resource pool index associated with the second control message; receive a third control message triggering a third random access procedure associated with the second component carrier and the third timing advance group; determine that the one or more conditions are satisfied based at least in part on the third timing advance group being different from the first timing advance group and the second timing advance group; and send a third random access preamble message associated with the third random access procedure based at least in part on satisfying the one or more conditions and at least in part on receiving the third control message before completing the first random access procedure.

[0228] Aspect 8: An apparatus according to any one of Aspects 1 to 7, wherein the instructions are also executable by the processor to enable the apparatus to: receive a first random access response message associated with the first random access process based at least in part on sending the first random access preamble message; and receive a second random access response message associated with the second random access process based at least in part on sending the second random access preamble message.

[0229] Aspect 9: An apparatus according to any one of Aspects 1 to 8, wherein the instruction is also executable by the processor to cause the apparatus to: send a capability message indicating that the UE is capable of supporting multiple random access processes that at least partially overlap in time, wherein receiving the second control message that triggers the second random access process is at least partially based on sending the capability message.

[0230] Aspect 10: An apparatus according to aspect 9, wherein the capability message includes: an indication of a threshold number of random access procedures that are at least partially overlapping in time that the UE can support, an indication of the one or more conditions, or both.

[0231] Aspect 11: An apparatus according to any one of Aspects 1 to 10, wherein the instructions are also executable by the processor to cause the apparatus to: receive a third control message that triggers a third random access process before completing the first random access process; determine that the one or more conditions are not met for the third random access process; and suppress initiation of the third random access process based at least in part on the determination, or initiate the third random access process and terminate the first random access process.

[0232] Aspect 12: An apparatus according to any one of Aspects 1 to 11, wherein the instructions are also executable by the processor to cause the apparatus to: receive a third control message triggering a third random access process before completing the first random access process; determine that the third random access process exceeds a threshold number of random access processes supported by the UE that at least partially overlap in time; and suppress initiation of the third random access process based at least in part on the determination.

[0233] Aspect 13: An apparatus according to any one of Aspects 1 to 12, wherein the instructions are also executable by the processor to cause the apparatus to: receive the first control message, including receiving the first control message from a first network entity; and receive the second control message, including receiving the second control message from a second network entity.

[0234] Aspect 14: A method for performing wireless communications at a UE, the method comprising: receiving a first control message that triggers a first random access procedure; sending a first random access preamble message associated with the first random access procedure based at least in part on receiving the first control message; receiving a second control message that triggers a second random access procedure; and before completing the first random access procedure and at least in part based on satisfying one or more conditions, sending a second random access preamble message associated with the second random access procedure based at least in part on receiving the second control message.

[0235] Aspect 15: According to the method described in Aspect 14, the method also includes: receiving signaling indicating the configuration of a first component carrier associated with a first timing advance group and a second timing advance group, wherein the first random access procedure and the second random access procedure are associated with the first component carrier; and determining that the one or more conditions are satisfied based at least in part on the fact that a first control resource set pool index associated with the first control message is different from a second control resource set pool index associated with the second control message.

[0236] Aspect 16: According to the method described in any one of Aspects 14 to 15, the method further includes: receiving signaling indicating the configuration of a first timing advance group associated with a first component carrier and a second timing advance group associated with a second component carrier, wherein the first random access procedure is associated with the first component carrier and the second random access procedure is associated with the second component carrier; and determining that the one or more conditions are satisfied based at least in part on the first component carrier being associated with the first timing advance group and the second component carrier being associated with the second timing advance group different from the first timing advance group.

[0237] Aspect 17: According to the method described in any one of Aspects 14 to 16, the method further includes: receiving signaling indicating the configuration of a first component carrier set and a second component carrier set, wherein each component carrier in the first component carrier set is associated with one or more timing advance groups in a first timing advance group set, and each component carrier in the second component carrier set is associated with one or more timing advance groups in a second timing advance group set; and determining that the one or more conditions are satisfied based at least in part on triggering the first random access process for the first component carrier in the first component carrier set and triggering the second random access process for the first component carrier in the second component carrier set.

[0238] Aspect 18: A method according to Aspect 17, wherein the UE supports up to two random access procedures that are at least partially overlapping in time for the first component carrier set and up to two random access procedures that are at least partially overlapping in time for the second component carrier set based at least in part on satisfying the one or more conditions.

[0239] Aspect 19: The method according to aspect 18 further comprises: determining that the one or more conditions are met based at least in part on each random access procedure associated with the corresponding component carrier set being associated with a different control resource set pool index.

[0240] Aspect 20: According to the method described in any one of Aspects 14 to 19, the method further includes: receiving signaling indicating the configuration of a first component carrier associated with a first timing advance group and a second timing advance group and a second component carrier associated with at least a third timing advance group, and wherein the first random access process and the second random access process are associated with the first component carrier; determining that the one or more conditions are satisfied based at least in part on the fact that a first control resource set pool index associated with the first control message is different from a second control resource set pool index associated with the second control message; receiving a third control message triggering a third random access process associated with the second component carrier and the third timing advance group; determining that the one or more conditions are satisfied based at least in part on the fact that the third timing advance group is different from the first timing advance group and the second timing advance group; and sending a third random access preamble message associated with the third random access process based at least in part on satisfying the one or more conditions and at least in part on receiving the third control message before completing the first random access process.

[0241] Aspect 21: According to any one of Aspects 14 to 20, the method further includes: receiving a first random access response message associated with the first random access process based at least in part on sending the first random access preamble message; and receiving a second random access response message associated with the second random access process based at least in part on sending the second random access preamble message.

[0242] Aspect 22: According to any one of Aspects 14 to 21, the method further includes: sending a capability message indicating that the UE is capable of supporting multiple random access processes that at least partially overlap in time, wherein receiving the second control message that triggers the second random access process is at least partially based on sending the capability message.

[0243] Aspect 23: A method according to aspect 22, wherein the capability message includes: an indication of a threshold number of random access procedures that the UE can support that at least partially overlap in time, an indication of the one or more conditions, or both.

[0244] Aspect 24: According to the method described in any one of Aspects 14 to 23, the method also includes: receiving a third control message that triggers a third random access process before completing the first random access process; determining that the one or more conditions are not met for the third random access process; and suppressing initiation of the third random access process based at least in part on the determination, or initiating the third random access process and terminating the first random access process.

[0245] Aspect 25: According to the method described in any one of Aspects 14 to 24, the method also includes: receiving a third control message triggering a third random access process before completing the first random access process; determining that the third random access process exceeds a threshold number of random access processes supported by the UE that are at least partially overlapping in time; and suppressing initiation of the third random access process based at least in part on the determination.

[0246] Aspect 26: According to the method described in any one of Aspects 14 to 25, the method further includes: receiving the first control message, including receiving the first control message from a first network entity; and receiving the second control message, including receiving the second control message from a second network entity.

[0247] Aspect 27: A device comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the device to perform a method according to any one of Aspects 1 to 13.

[0248] Aspect 28: An apparatus comprising at least one means for performing the method according to any one of aspects 1 to 13.

[0249] Aspect 29: A non-transitory computer-readable medium storing code, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 13.

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

[0251] Aspect 31: An apparatus for wireless communication at a UE, the apparatus comprising: at least one means for performing a method according to any one of aspects 14 to 26.

[0252] Aspect 32: 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 14 to 26.

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

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

[0255] 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, light fields or optical particles, or any combination thereof.

[0256] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, an 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).

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

[0258] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to transfer from one place to another.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 or other magnetic storage device or can be used for carrying or storing desired program code means and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, includes 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.

[0259] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on 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."

[0260] The terms "determine" or "determine" encompass a variety of actions, and thus, "determine" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and similar actions. Additionally, "determine" may include receiving (such as receiving information), accessing (such as accessing data in a memory), and similar actions. Additionally, "determine" may include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

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

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

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

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: Receiving a first control message triggering a first random access procedure; sending a first random access preamble message associated with the first random access procedure based at least in part on receiving the first control message; Receiving a second control message triggering a second random access procedure; as well as Prior to completing the first random access procedure and based at least in part on satisfying one or more conditions, a second random access preamble message associated with the second random access procedure is sent based at least in part on receiving the second control message.

2. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: receiving signaling indicating configuration of a first component carrier associated with a first timing advance group and a second timing advance group, wherein the first random access procedure and the second random access procedure are associated with the first component carrier; and The one or more conditions are determined to be satisfied based at least in part on a first control resource set pool index associated with the first control message being different than a second control resource set pool index associated with the second control message.

3. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: receiving signaling indicating configuration of a first timing advance group associated with a first component carrier and a second timing advance group associated with a second component carrier, wherein the first random access procedure is associated with the first component carrier and the second random access procedure is associated with the second component carrier; and The one or more conditions are determined to be satisfied based at least in part on the first component carrier being associated with the first timing advance group and the second component carrier being associated with the second timing advance group different from the first timing advance group.

4. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receiving signaling indicating configuration of a first component carrier set and a second component carrier set, wherein each component carrier in the first component carrier set is associated with one or more timing advance groups in a first timing advance group set, and each component carrier in the second component carrier set is associated with one or more timing advance groups in a second timing advance group set; and Satisfaction of the one or more conditions is determined based at least in part on triggering the first random access procedure for a first component carrier in the first set of component carriers and triggering the second random access procedure for a first component carrier in the second set of component carriers.

5. The apparatus of claim 4 , wherein the UE supports a maximum of two random access procedures that at least partially overlap in time for the first component carrier set and a maximum of two random access procedures that at least partially overlap in time for the second component carrier set based at least in part on satisfying the one or more conditions.

6. The apparatus of claim 5, wherein the instructions are further executable by the processor to cause the apparatus to: Satisfaction of the one or more conditions is determined based at least in part on each random access procedure associated with a respective set of component carriers being associated with a different control resource set pool index.

7. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receiving signaling indicating configuration of a first component carrier associated with a first timing advance group and a second timing advance group and a second component carrier associated with at least a third timing advance group, and wherein the first random access procedure and the second random access procedure are associated with the first component carrier; determining that the one or more conditions are satisfied based at least in part on a first control resource set pool index associated with the first control message being different than a second control resource set pool index associated with the second control message; receiving a third control message triggering a third random access procedure associated with the second component carrier and the third timing advance group; determining that the one or more conditions are satisfied based at least in part on the third timing advance group being different than the first timing advance group and the second timing advance group; as well as Sending a third random access preamble message associated with the third random access procedure based at least in part on satisfying the one or more conditions before completing the first random access procedure and based at least in part on receiving the third control message.

8. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receiving a first random access response message associated with the first random access procedure based at least in part on sending the first random access preamble message; and A second random access response message associated with the second random access procedure is received based at least in part on sending the second random access preamble message.

9. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: sending a capability message indicating that the UE is capable of supporting multiple random access procedures that at least partially overlap in time, wherein receiving the second control message triggering the second random access procedure is based at least in part on sending the capability message.

10. The apparatus of claim 9, wherein the capability message comprises an indication of a threshold number of random access procedures that at least partially overlap in time that the UE is capable of supporting, an indication of the one or more conditions, or both.

11. The apparatus of claim 1 , wherein the instructions are further executable by the processor to cause the apparatus to: receiving a third control message triggering a third random access procedure before completing the first random access procedure; determining that the one or more conditions are not satisfied for the third random access procedure; as well as Based at least in part on the determination, refraining from initiating the third random access procedure, or initiating the third random access procedure and terminating the first random access procedure.

12. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receiving a third control message triggering a third random access procedure before completing the first random access procedure; determining that the third random access procedure exceeds a threshold number of random access procedures supported by the UE that at least partially overlap in time; as well as and refraining from initiating the third random access procedure based at least in part on the determination.

13. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: Receiving the first control message comprises receiving the first control message from a first network entity; and Receiving the second control message includes receiving the second control message from a second network entity.

14. A method for wireless communication at a user equipment (UE), the method comprising: Receiving a first control message triggering a first random access procedure; sending a first random access preamble message associated with the first random access procedure based at least in part on receiving the first control message; Receiving a second control message triggering a second random access procedure; as well as Prior to completing the first random access procedure and based at least in part on satisfying one or more conditions, a second random access preamble message associated with the second random access procedure is sent based at least in part on receiving the second control message.

15. The method according to claim 14, further comprising: receiving signaling indicating configuration of a first component carrier associated with a first timing advance group and a second timing advance group, wherein the first random access procedure and the second random access procedure are associated with the first component carrier; and The one or more conditions are determined to be satisfied based at least in part on a first control resource set pool index associated with the first control message being different than a second control resource set pool index associated with the second control message.

16. The method according to claim 14, further comprising: receiving signaling indicating configuration of a first timing advance group associated with a first component carrier and a second timing advance group associated with a second component carrier, wherein the first random access procedure is associated with the first component carrier and the second random access procedure is associated with the second component carrier; as well as The one or more conditions are determined to be satisfied based at least in part on the first component carrier being associated with the first timing advance group and the second component carrier being associated with the second timing advance group different from the first timing advance group.

17. The method according to claim 14, further comprising: receiving signaling indicating configuration of a first component carrier set and a second component carrier set, wherein each component carrier in the first component carrier set is associated with one or more timing advance groups in a first timing advance group set, and each component carrier in the second component carrier set is associated with one or more timing advance groups in a second timing advance group set; as well as Satisfaction of the one or more conditions is determined based at least in part on triggering the first random access procedure for a first component carrier in the first set of component carriers and triggering the second random access procedure for a first component carrier in the second set of component carriers.

18. The method of claim 17, wherein the UE supports a maximum of two random access procedures at least partially overlapping in time for the first component carrier set and a maximum of two random access procedures at least partially overlapping in time for the second component carrier set based at least in part on satisfying the one or more conditions.

19. The method according to claim 18, further comprising: Satisfaction of the one or more conditions is determined based at least in part on each random access procedure associated with a respective set of component carriers being associated with a different control resource set pool index.

20. The method according to claim 14, further comprising: receiving signaling indicating configuration of a first component carrier associated with a first timing advance group and a second timing advance group and a second component carrier associated with at least a third timing advance group, and wherein the first random access procedure and the second random access procedure are associated with the first component carrier; determining that the one or more conditions are satisfied based at least in part on a first control resource set pool index associated with the first control message being different than a second control resource set pool index associated with the second control message; receiving a third control message triggering a third random access procedure associated with the second component carrier and the third timing advance group; determining that the one or more conditions are satisfied based at least in part on the third timing advance group being different than the first timing advance group and the second timing advance group; as well as Sending a third random access preamble message associated with the third random access procedure based at least in part on satisfying the one or more conditions before completing the first random access procedure and based at least in part on receiving the third control message.

21. The method according to claim 14, further comprising: receiving a first random access response message associated with the first random access procedure based at least in part on sending the first random access preamble message; as well as A second random access response message associated with the second random access procedure is received based at least in part on sending the second random access preamble message.

22. The method according to claim 14, further comprising: sending a capability message indicating that the UE is capable of supporting multiple random access procedures that at least partially overlap in time, wherein receiving the second control message triggering the second random access procedure is based at least in part on sending the capability message.

23. The method of claim 22, wherein the capability message comprises an indication of a threshold number of random access procedures that at least partially overlap in time that the UE is capable of supporting, an indication of the one or more conditions, or both.

24. The method according to claim 14, further comprising: receiving a third control message triggering a third random access procedure before completing the first random access procedure; determining that the one or more conditions are not satisfied for the third random access procedure; as well as Based at least in part on the determination, refraining from initiating the third random access procedure, or initiating the third random access procedure and terminating the first random access procedure.

25. The method according to claim 14, further comprising: receiving a third control message triggering a third random access procedure before completing the first random access procedure; determining that the third random access procedure exceeds a threshold number of random access procedures supported by the UE that at least partially overlap in time; as well as and refraining from initiating the third random access procedure based at least in part on the determination.

26. The method of claim 14, further comprising: Receiving the first control message comprises receiving the first control message from a first network entity; as well as Receiving the second control message includes receiving the second control message from a second network entity.

27. A non-transitory computer-readable medium storing code for wireless communication at a user equipment (UE), the code comprising instructions executable by a processor: Receiving a first control message triggering a first random access procedure; sending a first random access preamble message associated with the first random access procedure based at least in part on receiving the first control message; Receiving a second control message triggering a second random access procedure; as well as Prior to completing the first random access procedure and based at least in part on satisfying one or more conditions, a second random access preamble message associated with the second random access procedure is sent based at least in part on receiving the second control message.

28. The non-transitory computer readable medium of claim 27, wherein the instructions are further executable by the processor to: receiving signaling indicating configuration of a first component carrier associated with a first timing advance group and a second timing advance group, wherein the first random access procedure and the second random access procedure are associated with the first component carrier; and The one or more conditions are determined to be satisfied based at least in part on a first control resource set pool index associated with the first control message being different than a second control resource set pool index associated with the second control message.

29. The non-transitory computer readable medium of claim 27, wherein the instructions are further executable by the processor to: receiving signaling indicating configuration of a first timing advance group associated with a first component carrier and a second timing advance group associated with a second component carrier, wherein the first random access procedure is associated with the first component carrier and the second random access procedure is associated with the second component carrier; and The one or more conditions are determined to be satisfied based at least in part on the first component carrier being associated with the first timing advance group and the second component carrier being associated with the second timing advance group different from the first timing advance group.

30. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: means for receiving a first control message for triggering a first random access procedure; means for sending a first random access preamble message associated with the first random access procedure based at least in part on receiving the first control message; means for receiving a second control message for triggering a second random access procedure; and Means for sending a second random access preamble message associated with the second random access procedure based at least in part on receiving the second control message prior to completing the first random access procedure and based at least in part on satisfying one or more conditions.