Random access enhancements for multiple transmit and receive points

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive a random access command message from a network entity that commands the UE to perform a random access procedure using a random access configuration associated with a control resource set pool (CORESET) index or a physical cell identifier (PCI). The UE may transmit a random access preamble, and may receive a random access response (RAR) in a RAR window. The UE may transmit a feedback message indicating whether the UE successfully receives the RAR according to a feedback configuration based on the RAR. In some examples, the UE may monitor transmission of an RAR data message based on an RAR control message for the RAR. The UE may also transmit a second random access preamble at a power level based on the power adjustment size and the random access attempt counter.

Description

Technical Field

[0001] The following relates to wireless communications, including random access enhancements for multiple transmission and reception points. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication for 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 random access enhancements for multiple transmission and reception points (multi-TRPs). For example, the described technology allows a user equipment (UE) to receive a random access command message from a network entity, the random access command message instructing the UE to perform a random access procedure using a random access configuration associated with a control resource set (CORESET) pool index or a physical cell identifier (PCI). The UE may send a random access preamble associated with the CORESET pool index or PCI in response to the random access command message. In response to the preamble, the network entity may send a random access response (RAR) to the UE within a RAR window. In some examples, the UE may respond to the RAR by sending a feedback message to the network entity indicating whether the UE successfully received the RAR according to a feedback configuration, wherein the feedback configuration may be based on the RAR. Additionally or alternatively, the UE may receive a RAR control message as part of the RAR and may monitor multiple blind transmissions of the RAR data message based on a retransmission configuration that the UE may determine using the RAR control message. In some examples, the UE may receive a random access command message and may transmit a random access preamble at a transmit power level based on a power adjustment size and a random access attempt counter. In some examples, the random access attempt counter may be based on whether a preamble index, PCI, and synchronization signal block (SSB) associated with the random access command message are the same as the preamble index, PCI, and synchronization signal block (SSB) of a previous random access command message.

[0004] A method for wireless communication at a UE is described. The method may include: receiving a random access command message from a network entity, the random access command message instructing the UE to perform a random access procedure using a random access configuration associated with a coreset pool index or a personal information component (PCI); sending a random access preamble associated with the coreset pool index or the PCI for the random access procedure to the network entity in response to the random access command message; receiving a random access report (RAR) for the random access procedure from the network entity in a RAR window; and sending a feedback message to the network entity indicating whether the UE successfully received the RAR according to a feedback configuration based on the RAR.

[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 random access command message from a network entity, the random access command message instructing the UE to perform a random access procedure using a random access configuration associated with a coreset pool index or a personal information component (PCI); in response to the random access command message, send a random access preamble associated with the coreset pool index or the PCI for the random access procedure to the network entity; receive a random access report (RAR) for the random access procedure from the network entity within a RAR window; and send a feedback message to the network entity indicating whether the UE successfully received the RAR according to a feedback configuration based on the RAR.

[0006] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving a random access command message from a network entity, the random access command message instructing the UE to perform a random access procedure using a random access configuration associated with a CORESET pool index or a PCI; means for sending a random access preamble associated with the CORESET pool index or the PCI for the random access procedure to the network entity in response to the random access command message; means for receiving a Random Access Response (RAR) for the random access procedure from the network entity within a RAR window; and means for sending a feedback message to the network entity indicating whether the UE successfully received the RAR according to a feedback configuration, the feedback configuration being based on the RAR.

[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 random access command message from a network entity, the random access command message instructing the UE to perform a random access procedure using a random access configuration associated with a coreset pool index or a personal information component (PCI); in response to the random access command message, send a random access preamble associated with the coreset pool index or the PCI for the random access procedure to the network entity; receive a random access report (RAR) for the random access procedure from the network entity within a RAR window; and send a feedback message to the network entity indicating whether the UE successfully received the RAR according to a feedback configuration based on the RAR.

[0008] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the feedback configuration may include at least one of: a feedback timing indicator indicating a timing offset between reception of the RAR and transmission of the feedback message; a physical uplink control channel (PUCCH) resource indicator indicating a PUCCH resource used for transmission of the feedback message; or a transmit power control (TPC) command indicating a transmit power-related parameter used for transmission of the feedback message.

[0009] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the feedback configuration may be based on a payload of the RAR.

[0010] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: sending the feedback message according to the feedback configuration may be associated with the PCIs including the inactive PCIs based on the RAR.

[0011] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: sending the feedback message according to the feedback configuration may be based on an indication in the random access command message.

[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: Sending a feedback message according to a feedback configuration may be based on a format of a payload.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the feedback configuration may be based on one or more reserved bits in a physical downlink control channel (PDCCH) order scrambled by a random access radio network temporary identifier (RA-RNTI).

[0014] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: Sending the feedback message according to the feedback configuration may be based on a radio resource control (RRC) configuration.

[0015] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: Sending the feedback message based on the one or more reserved bits may be based on an indication in the random access command message.

[0016] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: sending the feedback message according to the feedback configuration may be based on an indication in the random access command message.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a payload of the random access command message indicating an RAR indicates a feedback configuration, or one or more reserved bits in a PDCCH order scrambled by an RA-RNTI indicates a feedback configuration.

[0018] A method for wireless communication at a UE is described. The method may include: receiving a random access command message from a network entity, the random access command message instructing the UE to perform a random access procedure using a random access configuration associated with a CORESET pool index or a PCI; sending a random access preamble associated with the CORESET pool index or the PCI for the random access procedure to the network entity in response to the random access command message; receiving a RAR control message for the random access procedure from the network entity in a RAR window, the RAR control message indicating a retransmission configuration identifying a number of transmissions of a RAR data message; and monitoring the number of transmissions of the RAR data message based on the RAR control message.

[0019] 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 random access command message from a network entity, the random access command message instructing the UE to perform a random access procedure using a random access configuration associated with a core set pool index or a personal information component (PCI); in response to the random access command message, send a random access preamble associated with the core set pool index or the PCI for the random access procedure to the network entity; receive a retransmission configuration (RAR) control message for the random access procedure from the network entity in a retransmission window (RAR window), the RAR control message indicating a retransmission configuration identifying a number of transmissions of a RAR data message; and monitor the number of transmissions of the RAR data message based on the RAR control message.

[0020] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving a random access command message from a network entity, the random access command message instructing the UE to perform a random access procedure using a random access configuration associated with a CORESET pool index or a PCI; means for sending a random access preamble associated with the CORESET pool index or the PCI for the random access procedure to the network entity in response to the random access command message; means for receiving a RAR control message for the random access procedure from the network entity in a RAR window, the RAR control message indicating a retransmission configuration identifying a number of transmissions of a RAR data message; and means for monitoring the number of transmissions of the RAR data message based on the RAR control message.

[0021] 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 random access command message from a network entity, the random access command message instructing the UE to perform a random access procedure using a random access configuration associated with a core set pool index or a personal computer identifier (PCI); in response to the random access command message, send a random access preamble associated with the core set pool index or the PCI for the random access procedure to the network entity; receive a retransmission configuration (RAR) control message for the random access procedure from the network entity in a retransmission window (RAR window), the RAR control message indicating a retransmission configuration identifying a number of transmissions of a RAR data message; and monitor the number of transmissions of the RAR data message based on the RAR control message.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a RAR control message may include operations, features, components, or instructions for: receiving a RAR control message indicating a redundant version sequence mapped to a set of multiple RAR data message opportunities, wherein monitoring a number of RAR data message transmissions occurs within the set of multiple RAR data message opportunities according to the redundant version sequence.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a RAR control message indicating a redundant version sequence may include operations, features, components, or instructions for: receiving a RAR control message indicating a retransmission configuration that identifies a starting redundant version value of a redundant version sequence, wherein the redundant version values ​​of the redundant version sequence may be cyclically mapped to a set of multiple RAR data message opportunities starting from the starting redundant version value in a defined order.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a RAR control message may include operations, features, components, or instructions for: receiving a RAR control message including one or more reserved bits indicating a retransmission configuration, the one or more reserved bits being processed based on the RAR control message being associated with a PCI including an inactive PCI.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a RAR control message may include operations, features, components, or instructions for: receiving a RAR control message including one or more reserved bits indicating a retransmission configuration, the one or more reserved bits being processed based on an indication in a random access command message.

[0026] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a RAR data message based on monitoring a transmission quantity.

[0027] A method for wireless communication at a UE is described. The method may include: receiving a first random access command message for a random access procedure from a network entity, the first random access command message instructing the UE to transmit a first random access preamble associated with a first preamble index, a first PCI, and a first SSB index; transmitting the first random access preamble of the random access procedure to the network entity at a first transmit power level in response to the first random access command message; receiving a second random access command message from the network entity, the second random access command message instructing the UE to transmit a second random access preamble associated with a second preamble index, a second PCI, and a second SSB index; and transmitting the second random access preamble to the network entity at a second transmit power level, wherein the second transmit power level is based on a power adjustment size and a random access attempt counter, the random access attempt counter being based at least in part on whether the second preamble index, the second PCI, and the second SSB index are the same as the first preamble index, the first PCI, and the first SSB index.

[0028] 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 random access command message for a random access procedure from a network entity, the first random access command message instructing the UE to transmit a first random access preamble associated with a first preamble index, a first PCI, and a first SSB index; in response to the first random access command message, transmit the first random access preamble of the random access procedure to the network entity at a first transmit power level; receive a second random access command message from the network entity, the second random access command message instructing the UE to transmit a second random access preamble associated with a second preamble index, a second PCI, and a second SSB index; and transmit the second random access preamble to the network entity at a second transmit power level, wherein the second transmit power level is based on a power adjustment size and a random access attempt counter, the random access attempt counter being based at least in part on whether the second preamble index, the second PCI, and the second SSB index are the same as the first preamble index, the first PCI, and the first SSB index.

[0029] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving a first random access command message for a random access procedure from a network entity, the first random access command message instructing the UE to transmit a first random access preamble associated with a first preamble index, a first PCI, and a first SSB index; means for transmitting the first random access preamble of the random access procedure to the network entity at a first transmit power level in response to the first random access command message; means for receiving a second random access command message from the network entity, the second random access command message instructing the UE to transmit a second random access preamble associated with a second preamble index, a second PCI, and a second SSB index; and means for transmitting the second random access preamble to the network entity at a second transmit power level, wherein the second transmit power level is based on a power adjustment size and a random access attempt counter, the random access attempt counter being based at least in part on whether the second preamble index, the second PCI, and the second SSB index are the same as the first preamble index, the first PCI, and the first SSB index.

[0030] 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 random access command message for a random access procedure from a network entity, the first random access command message instructing the UE to transmit a first random access preamble associated with a first preamble index, a first PCI, and a first SSB index; in response to the first random access command message, transmit the first random access preamble of the random access procedure to the network entity at a first transmit power level; receive a second random access command message from the network entity, the second random access command message instructing the UE to transmit a second random access preamble associated with a second preamble index, a second PCI, and a second SSB index; and transmit the second random access preamble to the network entity at a second transmit power level, wherein the second transmit power level is based on a power adjustment size and a random access attempt counter, the random access attempt counter being based at least in part on whether the second preamble index, the second PCI, and the second SSB index are the same as the first preamble index, the first PCI, and the first SSB index.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the second transmit power level can be further based on a power ramp-up counter based on whether the second preamble index, second PCI, and second SSB index can be the same as the first preamble index, first PCI, and first SSB index.

[0032] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for incrementing a random access attempt counter based on the second preamble index, second PCI, and second SSB index being the same as the first preamble index, first PCI, and first SSB index.

[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for resetting a random access attempt counter based on a second preamble index, a second PCI, or a second SSB index being different from a first preamble index, a first PCI, or a first SSB index.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for incrementing a random access attempt counter based on the second preamble index and the second PCI being the same as the first preamble index and the first PCI; and incrementing a power ramp counter based on the second preamble index, the second PCI, and the second SSB index being the same as the first preamble index, the first PCI, and the first SSB index.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: incrementing a random access attempt counter based on the second preamble index and the second PCI being the same as the first preamble index and the first PCI; and maintaining a power ramp counter unchanged based on the second preamble index and the second PCI being the same as the first preamble index and the first PCI and the second SSB index being different from the first SSB index.

[0036] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a control element message from a network entity in response to the first random access preamble transmission, wherein one or more of the random access attempt counter and the power ramp-up counter may be based on the receipt of the control element message.

[0037] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for resetting a random access attempt counter based on receipt of a control element message indicating a timing advance corresponding to a timing advance group identifier associated with a random access procedure.

[0038] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for resetting a power ramp-up counter based on receipt of a control element message indicating a timing advance corresponding to a timing advance group identifier associated with a random access procedure.

[0039] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for resetting a random access attempt counter and a power ramp-up counter based on the random access attempt counter reaching a maximum count number. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 An example of a wireless communication system supporting random access enhancements for multiple transmission and reception points (multi-TRP) according to one or more aspects of the present disclosure is illustrated.

[0041] Figure 2 An example of a wireless communication system supporting random access enhancements for multiple TRPs according to one or more aspects of the present disclosure is illustrated.

[0042] Figure 3 An example of a Transmit Configuration Indication (TCI) state assignment diagram supporting random access enhancement for multiple TRPs according to one or more aspects of the present disclosure is illustrated.

[0043] Figure 4A and Figure 4B Examples of process flows and payload formats supporting random access enhancements for multiple TRPs according to one or more aspects of the present disclosure are respectively illustrated.

[0044] Figure 5 An example of a process flow supporting random access enhancements for multiple TRPs in accordance with one or more aspects of the present disclosure is illustrated.

[0045] Figure 6A and Figure 6B An example of a payload format supporting random access enhancements for multiple TRPs according to one or more aspects of the present disclosure is illustrated.

[0046] Figure 7 An example of a physical downlink control channel (PDCCH) format supporting random access enhancement for multiple TRPs according to one or more aspects of the present disclosure is illustrated.

[0047] Figure 8 An example of a process flow supporting random access enhancements for multiple TRPs in accordance with one or more aspects of the present disclosure is illustrated.

[0048] Figure 9An example of a process flow supporting random access enhancements for multiple TRPs in accordance with one or more aspects of the present disclosure is illustrated.

[0049] Figure 10A and Figure 10B An example of a process flow supporting random access enhancements for multiple TRPs in accordance with one or more aspects of the present disclosure is illustrated.

[0050] Figure 11A and Figure 11B An example of a process flow supporting random access enhancements for multiple TRPs in accordance with one or more aspects of the present disclosure is illustrated.

[0051] Figure 12 and Figure 13 A block diagram of a device supporting random access enhancements for multiple TRPs according to one or more aspects of the present disclosure is illustrated.

[0052] Figure 14 A block diagram of a communication manager supporting random access enhancements for multiple TRPs according to one or more aspects of the present disclosure is illustrated.

[0053] Figure 15 A diagram illustrating a system including a device supporting random access enhancements for multiple TRPs according to one or more aspects of the present disclosure is illustrated.

[0054] Figures 16 to 19 A flowchart illustrating a method for supporting random access enhancements for multiple TRPs according to one or more aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0055] A UE may communicate with a network entity via multiple transmit and receive points (TRPs) within a multiple transmit and receive point (multi-TRP) configuration. For example, a UE may communicate with a network entity via two TRPs while performing a random access channel (RACH) procedure, such as a physical RACH (PRACH) procedure, including contention-free random access (CFRA). In some examples, during a CFRA, the network entity may determine whether the UE successfully received a random access response (RAR) based on receiving an uplink signal from the UE. However, in a multi-TRP configuration, the UE may transmit a PRACH to a TRP with a physical cell identifier (PCI) that is an inactive PCI (e.g., there is limited or no ongoing communication between the UE and the TRP via the cell corresponding to the PCI) to measure a timing advance (TA) for the inactive PCI. Therefore, there may be a delay after the CFRA before any uplink information is transmitted, which may make it difficult for the network entity to determine whether the RAR was successfully received, which may result in additional retransmissions and delays in further signaling. In addition, for CFRA-triggered TA acquisition, the network entity may send a medium access control element (MAC-CE) in response to the random access preamble instead of the RAR to signal the TA to the UE, which may be referred to as RAR-less PRACH. However, the power ramp-up procedure for the retransmission of the random access preamble may not yet be defined for RAR-less PRACH.

[0056] The wireless communication system may support HARQ-ACK feedback for RAR messages in a RACH procedure (e.g., CFRA). For example, a UE may receive a random access command message (e.g., a physical downlink control channel (PDCCH) command) from a network entity, which command the UE to perform a RACH procedure using a random access configuration associated with a control resource set (CORESET) pool index or PCI. The UE may send a RACH preamble associated with the CORESET pool index or PCI in response to the PDCCH command, and in response to the preamble, the network entity may send a RAR to the UE within the RAR window. In some examples, the UE may respond to the RAR by sending a feedback message to the network entity based on a feedback configuration that the UE may determine using the RAR.

[0057] In some examples, by sending a feedback message in response to the RAR, the UE can indicate the successful completion of the RACH procedure to the network entity 105. Thus, the network entity can save resources and power by avoiding retransmission of the random access command message, and can increase the speed of operation by allowing the network entity and the UE to perform post-RACH procedures without delay.

[0058] Additionally or alternatively, the UE may receive a RAR control message (e.g., a RAR PDCCH message) as part of the RAR and may monitor multiple blind transmissions of a RAR data message (e.g., a RAR physical downlink shared channel (PDSCH) message) based on a retransmission configuration that the UE may determine using the RAR PDCCH message. By enabling blind retransmission of RAR data messages, the network entity may improve the reliability of the RAR by increasing the chance that the UE will successfully receive the RAR data message. Furthermore, for PRACH without RAR, the UE may support a power ramp-up procedure for retransmitting a RACH preamble based on receiving one or more PDCCH commands. By implementing power ramping for PRACH without RAR, the UE may increase the reliability of preamble retransmissions by increasing the preamble transmit power while also utilizing fewer resources by reducing the amount of preamble retransmissions.

[0059] 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 and described by and with reference to a wireless communication system, a Transmit Configuration Indication (TCI) state assignment diagram, a process flow, a payload format, and a PDCCH format. Various aspects of the present disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow diagrams related to random access enhancements for multiple TRPs.

[0060] Figure 1 An example of a wireless communication system 100 supporting random access enhancement for multiple TRPs 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.

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

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

[0063] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.

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

[0065] 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 base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home Node B, a Home evolved Node B, or other suitable terminology). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in a converged (e.g., monolithic, stand-alone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as the base station 140).

[0066] In some examples, the network entity 105 can be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that can 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 can include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmit receive point (TRP). One or more components of the network entity 105 in the disaggregated 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 disaggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0067] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a functional split of the protocol stack can be employed between CU 160 and DU 165 such that CU 160 can support one or more layers of the protocol stack and DU 165 can support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functions and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DUs 165 and RUs 170, such that the DUs 165 may support one or more layers of the protocol stack and the RUs 170 may support one or more different layers of the protocol stack. The DUs 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between the CU 160 and the DU 165 or between the DU 165 and the RU 170 can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, DU 165, or RU 170). The CU 160 can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU 160 can be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and the DU 165 can 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 according to interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating via these communication links.

[0068] In some wireless communication systems (e.g., wireless communication system 100), the 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 the 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 IAB donor. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by the DU 165 of the 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., RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0069] Where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support random access enhancements for multiple TRPs 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).

[0070] 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 terminology, where "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects, such as appliances or vehicles, meters, etc.

[0071] 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 1 shown.

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

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

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

[0075] Each frame may include a plurality of 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 (e.g., in the time domain) into subframes, and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended to the front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of mini-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0076] A subframe, slot, mini-slot, or 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 Transmit 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 bursts of shortened TTIs (sTTIs)).

[0077] In some examples, network entities 105 (e.g., base stations 140, RUs 170) can be mobile and, therefore, provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies can overlap, but the different coverage areas 110 can be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies can be supported by different network entities 105. The wireless communication system 100 can 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.

[0078] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). The UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private communication or group communication and may be supported by one or more services (such as push-to-talk, video, or data). Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0079] In some examples, a UE 115 can be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group performing D2D communication can be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which can support aspects of such D2D communication configured (e.g., scheduled) by the network entity 105. In some examples, one or more UEs 115 in such a group can be outside of the coverage area 110 of the network entity 105 or can 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 can support a one-to-many (1:M) system, in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0080] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for UEs 115 served by network entities 105 (e.g., base stations 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 the IP services 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0081] The wireless communication system 100 can operate using one or more frequency bands that can range from 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 wavelengths range from about one decimeter to one meter in length. UHF waves can be blocked or redirected by buildings and environmental features (which can be referred to as clusters), but these waves can penetrate structures sufficiently for a macrocell to provide service to a UE 115 located indoors. Communication using UHF waves can be associated with smaller antennas and a shorter range (e.g., less than 100 kilometers) than communication using the smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

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

[0083] A network entity 105 (e.g., a base station 140, a RU 170) or a UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input, multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located at different geographic locations. The network entity 105 may include an antenna array having a set of multiple rows and columns of antenna ports that the network entity 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panels may support RF beamforming for signals transmitted via the antenna ports.

[0084] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements can 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. The adjustments associated with each of these antenna elements can be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

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

[0086] Physical channels may be multiplexed according to various techniques for communication using a carrier. For example, physical control channels and physical data channels may be multiplexed using one or more of time division multiplexing (TDM), frequency division multiplexing (FDM), or a hybrid TDM-FDM technique for signaling via a downlink carrier. A control region (e.g., CORESET) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115 .

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

[0088] The wireless communication system 100 may support HARQ-ACK feedback for RAR messages in a RACH procedure as described herein. For example, in a multi-TRP configuration, the UE 115 may receive a random access command message (e.g., a PDCCH command) from the network entity 105 via the TRP, the random access command message commanding the UE 115 to perform a RACH procedure using a random access configuration associated with a CORESET pool index or a PCI (e.g., associated with the TRP). The UE 115 may send a RACH preamble associated with the CORESET pool index or PCI in response to the PDCCH command, and in response to the preamble, the network entity 105 may send a RAR to the UE within the RAR window. In some examples, the UE 115 may respond to the RAR by sending a feedback message to the network entity 105 based on the feedback configuration that the UE 115 may determine using the RAR. Additionally or alternatively, UE 115 may receive a RAR control message (e.g., a RAR PDCCH message) as part of the RAR and may monitor multiple blind transmissions of RAR data messages (e.g., a RAR physical downlink shared channel (PDSCH) message) based on a retransmission configuration that UE 115 may determine using the RAR PDCCH message. Furthermore, for MAC-CE TA acquisition, UE 115 may support a power ramp-up procedure for retransmitting a RACH preamble based on receiving one or more PDCCH commands.

[0089] Figure 2 An example of a wireless communication system 200 supporting random access enhancement for multiple TRPs according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a network entity 105-a that communicates with a UE 115-a via one or more TRPs 205 (including a first TRP 205-a and a second TRP 205-b). In some examples, the wireless communication system 200 may support multiple TRP transmissions based on a design of multiple DCIs (multi-DCIs). For example, the network entity 105-a may send a first DCI (e.g., via TRP 205-a) to schedule PDSCH1 transmissions from TRP 205-a, and may send a second DCI to schedule PDSCH2 transmissions from TRP 205-b.

[0090] In some examples, the UE 115-a can distinguish between the TRPs 205 based on the index of one or more CORESET pools. For example, each CORESET in a CORESET set (e.g., up to 5 CORESETs) can be configured with a CORESETPoolIndex value of 1 or 0 to group the CORESETs into two groups. In some examples, the UE 115-a can be configured by a higher layer parameter PDCCH-Config with two values ​​of CORESETPoolIndex for the active BWP of the serving cell, where CORESETID=1 and CORESETID=2 can be grouped if CORESETPoolIndex=0, and where CORESETID=3 and CORESETID=4 can be grouped if CORESETPoolIndex=1. Reference Figure 2 , TRP 205 - a and TRP 205 - b can each have the same or different CORESETPoolIndex.

[0091] In some examples, TRP 205-a and TRP 205-b can each have the same PCI (e.g., in an intra-cell layout). For example, TRP 205 can both be part of the same cell (e.g., the serving cell of UE 115-a) and can be associated with different panels, RRHs, or other features of a base station (e.g., network entity 105-a). As another example, TRP 205 can have different PCIs (e.g., in an inter-cell layout). For example, TRP 205-a can be part of an active serving cell (e.g., an active PCI) and TRP 205-b can be part of an inactive neighboring cell (e.g., an inactive PCI). In such an example, UE 115-a can be aware of the PCI associated with the active serving cell and may not be aware of the PCI associated with the inactive serving cell because UE 115-a can obtain the active PCI during cell search.

[0092] Figure 3 An example of a Transmit Configuration Indication (TCI) state assignment diagram 300 supporting random access enhancement for multiple TRPs according to one or more aspects of the present disclosure is illustrated. The TCI state assignment diagram 300 may illustrate an example for implementing one or more aspects of the wireless communication systems 100 and 200. For example, the TCI state assignment diagram may illustrate TCI assignments for one or more cells including a reference cell. Figure 2A network entity 105-a is depicted in communication with a UE 115-a and a TRP 205. In some examples, the TCI state may represent an indication of a transmission configuration including a quasi-co-site (QCL) relationship between a downlink reference signal and one or more ports.

[0093] For example, at least for the purpose of QCL indication, UE 115-a may be configured (e.g., via RRC signaling) with a list of up to M candidate TCI states (e.g., M=128). The TCI states may be configured or defined in PDSCH-Config. In some examples, the TCI-StateId field may be used to configure TCI states for CORESET, for non-zero power channel state information reference signal (NZP-CSI-RS) resources (NZP-CSI-RS-Resource), for physical uplink control channel (PUCCH) resources, for sounding reference signal (SRS) resources, and to configure other parameters.

[0094] In some examples, the MAC-CE 305 may be used to activate up to 2 of the total M TCI states. N TCI states for PDSCH QCL indication for a given CORESETPoolIndex. In some examples, N bits in the DCI can dynamically indicate the TCI state for PDSCH transmission (e.g., N=3). For multiple TRPs based on multiple DCI, the PDSCH can be associated with the CORESETPoolIndex value of the CORESET in which the DCI is received. In some examples, under PDSCH-config, the TCI state configuration can be defined by tci-StatesToAddModListSEQUENCE(SIZE(1..maxNrofTCI-States))OFTCI-State and by tci-StatesToReleaseListSEQUENCE(SIZE(1..maxNrofTCI-States))OFTCI-StateId. In some examples, the TCI state configuration can indicate the CORESETPoolIndex (e.g., corresponding to TRP 205). In some cases, for PDCCH, MAC-CE 305 can activate one TCI state.

[0095] In some examples, the TCI state can be associated with one or more synchronization signal blocks (SSBs). For example, if the TCI state is associated with the SSB of the serving cell (e.g., as indicated by the RRC configuration), the TCI state can be associated with the corresponding PCI (e.g., the PCI of the active serving cell corresponding to TRP 205-a). Additionally or alternatively, if the TCI state is associated with an SSB that is different from the SSB of the serving cell, the TCI state can be associated with a non-serving PCI (e.g., the PCI of the inactive cell corresponding to TRP 205-b). In some examples, an RRC indicator or RRC signaling can be used for multiple TRPs between cells. For example, the value SSB-MTC-AdditionalPCI-r17 can be indicated in the RRC configuration to indicate the non-serving cell information (e.g., the inactive PCI corresponding to TRP 205-b) to which the TCI state and / or QCL information is associated. In some examples, the indicator or signaling may not convey a PCI value.

[0096] In some examples, a PCI may be associated with different active TCI states based on TCI state activation. For example, a serving cell PCI may be associated with one or more active TCI states in an active TCI state set, and up to 1 additional PCI may be associated with an active TCI state in an active TCI state set. As another example, for an inter-cell multi-TRP, one PCI associated with one or more of the activated TCI states for PDSCH / PDCCH may be associated with one CORESETPoolIndex, and another PCI associated with one or more of the activated TCI states for PDSCH / PDCCH may be associated with another CORESETPoolIndex. For example, a first MAC-CE 305-a may be sent to activate a first set 310-a of TCI states for CORESETPoolIndex=0, where the first set 310-a may be associated with PCIX, which may represent a PCI associated with a serving cell of UE 115-a (e.g., a PCI associated with TRP 205-a). Additionally or alternatively, a second MAC-CE 305-b may be sent to activate a second set 310-b of TCI states for CORESETPoolIndex=1, where the second set 310-b may be associated with PCI Y, which may represent a PCI associated with a non-serving cell of UE 115-a (e.g., an inactive PCI associated with TRP 205-b). In some examples, for multiple TRPs, at least one PCI may be a serving cell PCI (e.g., PCI X associated with TRP 205-a), and at most one PCI may be associated with an inactive or non-serving cell PCI (e.g., PCI Y associated with TRP 205-b).

[0097] Figure 4A and Figure 4B 4 and 5. Examples of a process flow 401 and a payload format 402, respectively, are illustrated for supporting random access enhancements for multiple TRPs according to one or more aspects of the present disclosure. The process flow 401 and the payload format 402 may illustrate examples for implementing one or more aspects of the wireless communication systems 100 and 200 and the TCI state assignment diagram 300. For example, the process flow 401 may illustrate signaling between a UE 115-b and a network entity 105-b via TRP 205-c, TRP 205-d, or both, which may represent, respectively, Figure 2 UE 115-a, network entity 105-a, TRP 205-a and TRP 205-b as described in the . In addition, the payload format 402 may represent the . Figures 1 to 3RAR payload format described by RAR.

[0098] Figure 4A The process flow 401 may represent a random access procedure performed between the UE 115-b and the network entity 105-b. For example, the process flow may represent top-down signaling over time for a 2-step contention-free RACH (e.g., CFRA) procedure. For example, Figure 4A The illustrated 2-step contention-free RACH procedure may include two messages, including MSG 1 (e.g., RACH preamble) and MSG 2 (e.g., RAR). In some examples, in preparation for the 2-step procedure, the network entity 105-a may send MSG 0 or a random access command message (such as PDCCH order 405-a) that commands the UE to perform random access using a random access configuration associated with CORESETPoolIndex or PCI. For example, the network entity 105-b may send PDCCH order 405-a (MSG 0) indicating a random access configuration that indicates CORESETPoolIndex=1 or an inactive PCI associated with TRP 205-d (e.g., PCI Y associated with an inactive cell), and one or more resources for the RACH procedure. In some examples, additional signaling (such as RRC signaling, MAC-CE signaling, DCI, a previous PDCCH order, or other signaling) may indicate the random access configuration. In some examples, CORESETPoolIndex may indicate use of the PCI associated with TRP 205-d, or vice versa. In some examples, network entity 105-b may send a PDCCH order 405-a to UE 115-b via TRP 205-c, which may indicate the TRP 205 with which UE 115-b has performed CFRA. In some cases, the PDCCH order may indicate resource allocation for a random access preamble 410 for UE 115-b as well as a dedicated preamble assignment.

[0099] In response to the PDCCH order 405-a, as part of the 2-step CFRA procedure, the UE 115-b may send MSG 1, such as a random access preamble associated with the CORESETPoolIndex or PCI. For example, the UE 115-b may send the random access preamble 410-a (MSG 1) to the network entity 105-b via the TRP 205-d (e.g., based on a dedicated random access preamble assignment). After sending the random access preamble 410-a, the UE 115-b may receive the MSG 2, such as the RAR 415, from the network entity 105-a during a RAR window (e.g., configured by RRC). For example, during the RAR window, the network entity 105-b may send the RAR 415-a (MSG 2) to the UE 115-b via the TRP 205-d based on the random access preamble 410-a. In some examples, if UE 115-b fails to receive RAR 415-a, UE 115-b may refrain from sending one or more signals to network entity 105-b (or performing other communications in connected mode) based on UE 115-b being out of synchronization. For example, if UE 115-b sends one or more signals after a failed CFRA procedure (or other RACH procedure), the signals may be sent according to incorrect timing or other parameters because UE 115-b has not yet acquired the TA for TRP 205-d, which may result in a failed reception of the signals at network entity 105-b.

[0100] Additionally or alternatively, Figure 4A4 , the process flow 401 may represent a contention-based RACH process. For example, in a 4-step contention-based RACH process, the process flow 401 may include four messages, including MSG 1 (preamble), MSG 2 (RAR), MSG 3 (scheduled transmission), and MSG 4 (contention resolution). In the example of FIG. 4 , UE 115-b may transmit a preamble 410-a (in response to PDCCH order 405-a) and may receive RAR 415-a. After receiving RAR 415-a, UE 115-b may transmit a scheduled transmission to network entity 105-b (e.g., using information in RAR 415-a). Based on this transmission, network entity 105-b may send a contention resolution message to UE 115-b. For example, network entity 105-b may send a downlink message to UE 115-b to confirm that the process was successful, and if UE 115-b receives and successfully decodes the downlink message for contention resolution, UE 115-b may send a HARQ message for confirmation. Additionally or alternatively, UE 115-b and network entity 105-b may exchange MSG A (including MSG 1 and MSG 3) and MSG B (including MSG 2 and MSG 4) as part of a 2-step contention-based RACH process.

[0101] Figure 4B The payload format 402 may represent a configuration of a format for an RAR payload or RAR PDSCH 420 for an RAR 415 (e.g., as defined in Section 6.2.3 of 3GPP standard TS 38.321, Version 17.3.0). For example, an RAR 415-a may include a RAR PDSCH 420-a and a control message PDCCH 425 (e.g., RAR PDCCH 425). The RAR PDSCH 420-a may include one or more fields 430 spanning one or more resources (e.g., time, frequency, spatial resources). In some examples, the RAR PDSCH 420-a may include fields for indicating one or more TA commands, one or more UL grants, one or more temporary cell radio network temporary identifiers (C-RNTIs), and other fields. In some cases, the RAR PDSCH 420-a may include one or more reserved bits (R). The RAR PDSCH 420-a may also be octet-aligned (e.g., spanning 7 octets).

[0102] In some examples, UE 115-b may communicate one or more signals with network entity 105-b based on performing CFRA. For example, UE 115-b may use CFRA (e.g., associated with TRP 205-c) to obtain a TA for an active cell and may use the obtained TA and one or more active TCI states to send one or more uplink signals to network entity 105-b. In some cases, UE 115-b may not yet have a TA for an inactive PCI associated with TRP 205-d and may therefore perform the CFRA process described herein to obtain and / or measure a TA for an inactive PCI. In some examples, network entity 105-b may determine successful completion of CFRA based on receiving one or more uplink signals from UE 115-b.

[0103] In some examples, UE 115-b performs a reference Figure 4A The described CFRA process may then experience a delay before sending one or more uplink signals to the network entity 105-b. For example, the TRP 205-d may be as described in reference Figure 2 4 is associated with the inactive PCI described by TRP 205-b in . UE 115-b may perform CFRA to obtain a TA for the inactive PCI and TRP 205-d. However, since the PCI is inactive, UE 115-b may wait to perform communication with network entity 105-b using TRP 205-d. For example, UE 115-b may wait until MAC-CE 305 activates the TCI state associated with the inactive PCI and the TCI state of the corresponding CORESETPoolIndex (e.g., CORESETPoolIndex=1). However, the delay in the uplink transmission after CFRA may make it difficult for network entity 105-b to determine whether RAR 415-a was successfully received, and therefore whether the CFRA was successfully completed, because no feedback is currently defined for CFRA. This may result in the network entity 105-a being unable to transmit a retransmission to UE 115-b, or may generate unnecessary retransmissions when no retransmission is needed. Thus, the techniques described herein may enable the UE 115 to indicate successful RAR 415 acquisition and CFRA completion to the network entity 105 by utilizing HARQ-ACK feedback for RAR messages in CFRA or blind RAR payload retransmissions, as described with respect to Figures 5 to 8 described.

[0104] Figure 5An example of a process flow 500 for supporting random access enhancements for multiple TRPs according to one or more aspects of the present disclosure is illustrated. The process flow 500 may illustrate an example for implementing one or more aspects of the wireless communication systems 100 and 200, the TCI state assignment diagram 300, the process flow 401, and the payload format 402. For example, the process flow 500 may illustrate signaling between a UE 115-c and a network entity 105-c via TRPs 205-e and 205-f, which may represent TRPs 205-e and 205-f, respectively. Figure 4A 5. In some examples, process flow 500 may illustrate a CFRA procedure between UE 115-c and network entity 105-c, including communicating a feedback message 505 to indicate successful RAR acquisition based on feedback configuration 510. For example, process flow 500 may illustrate indicating HARQ feedback-related information.

[0105] For example, UE 115-c and network entity 105-c may exchange PDCCH commands 405-b (e.g., via TRP 205-e) and exchange random access preambles 410-b in response to the PDCCH commands 405-b (e.g., via TRP 205-f), as described with respect to Figure 4Aas described. In an example, the PDCCH command 405-b may be a PDCCH including a DCI commanding the UE 115-c to perform a random access procedure with the TRP 205-f. Based on the random access preamble 410-b, the network entity 105-c may send a RAR 415-b via the TRP 205-f, and the UE 115-c may receive the RAR 415-b via the TRP 205-f. In some examples, the UE 115-c may determine a feedback configuration 510-a for sending a feedback message 505-a to indicate whether the UE 115-c successfully received the RAR, wherein the UE 115-c may determine the feedback configuration 510-a based on the RAR 415-b. For example, the RAR 415-b may indicate the feedback configuration 510-a for sending the feedback message 505. After determining the feedback configuration 510-a, the UE 115-c may send a feedback message 505-a (e.g., MSG 3) to the network entity 105-c in accordance with the feedback configuration 510-a (e.g., via the TRP 205-f). For example, the UE 115-c may send a HARQ-ACK feedback message indicating successful reception of the RAR 415-b. In some examples, the network entity 105-c may determine that the RAR 415-b was successfully received based on receiving the feedback message 505-a. By sending the HARQ-ACK feedback, the UE 115-c may enable the network entity 105-c to determine that the CFRA was successfully completed, which may mitigate one or more delayed and lost messages, as well as save resources at the UE 115-c and the network entity 105-c.

[0106] In some examples, indicating the feedback configuration 510 (or indicating other information) may refer to indicating one or more indexes or including data. For example, the RAR 415-b may indicate the feedback configuration 510-b by indicating an index associated with the feedback configuration 510-a. In an example, the RAR 415-b may indicate an index in a set of indexes mapped to a table of different feedback configurations 510 stored at the UE 115-c. Based on determining the index indicated within the RAR 415-b, the UE 115-c may determine the feedback configuration 510-a by locating the corresponding feedback configuration 510 within the table using the index. As another example, the RAR 415-b may include the feedback configuration 510-a within one or more fields of the RAR 415-b. For example, the RAR 415-b may include the feedback configuration 510-a, wherein the feedback configuration 510-a may include one or more indexes associated with one or more parameter values, wherein the UE 115-b may select the one or more parameter values ​​using a parameter value table defined at the UE 115-b and the one or more indexes. Additionally or alternatively, the feedback configuration 510-a within the RAR 415-b may explicitly indicate (e.g., included within one or more fields of the RAR 415-b) data defining values ​​for one or more parameter values ​​(e.g., timing indicators, resources, transmit power levels, etc., as described herein).

[0107] In some examples, the feedback configuration 510-a in the RAR 415-b may include or indicate different HARQ feedback-related information for the UE 115-c. For example, the HARQ feedback-related information may be a feedback timing indicator, a control channel resource indicator, a transmit power level, or any combination thereof. In an example, the feedback configuration 510-a may indicate a feedback timing indicator, such as a K1 timing offset for feedback. Specifically, the feedback timing indicator may identify a timing offset between the reception of the RAR 415-b (e.g., RARPDSCH) and the transmission of the HARQ feedback, where the UE 115-c may send the feedback message 505-a based on the offset. Additionally or alternatively, the feedback configuration 510-a may indicate a control channel resource indicator identifying resources for HARQ feedback. For example, the feedback configuration 510-a may include or indicate a PUCCH resource indicator identifying one or more PUCCH resources, where the feedback message 505-a may be sent on the resources. The feedback configuration 510-a may also indicate a transmit power level at which the UE 115-a is to send the feedback message 505-a, such as a transmit / transmission power control (TPC) command indicating a transmit power (or other transmit power-related parameter) for HARQ feedback. The feedback message 505-a may be sent according to the TPC command.

[0108] In some examples, the feedback configuration may be indicated in an existing UL grant field of the payload of the RAR 415-b (e.g., PDSCH), as described in relation to Figure 6A Additionally or alternatively, the feedback configuration may be indicated in the RAR PDSCH format, as described in relation to Figure 6B In some cases, the feedback configuration may be indicated within a reserved bit of a control message (e.g., PDCCH) for the RAR 415-b, as described in relation to Figure 7 Additionally or alternatively, the network entity 105 may support performing multiple blind retransmissions of the RAR PDSCH, as described with respect to Figure 8 described.

[0109] Figure 6A and Figure 6B Examples of payload formats 601 and 602 supporting random access enhancements for multiple TRPs according to one or more aspects of the present disclosure are illustrated. The payload formats 601 and 602 may illustrate examples for implementing one or more aspects of the wireless communication systems 100 and 200, the TCI state assignment diagram 300, the process flows 401 and 500, and the payload format 402. For example, the payload formats 601 and 602 may illustrate examples for use with RAR 415 (such as in Figure 5 5-a). In some examples, the feedback configuration 510 may be based on the payload (e.g., PDSCH 420) of the RAR 415-b as described herein. For example, payload formats 601 and 602 may represent different configurations of the feedback configuration 510 that enable the RAR 415-b to indicate the feedback configuration 510 for the UE 115-c to send the feedback message 505, where the feedback configuration 510 may represent the feedback configuration 510-a.

[0110] Figure 6A The payload format 601 may illustrate reusing an existing bit within the UL grant of the RAR 415 to indicate the feedback configuration 510. For example, the payload format 601 may represent an example of the payload format 402, including information about Figure 4B For example, the payload format 601 may include a field 430 for a reserved bit R, a TA command, an UL grant 605, and a temporary C-RNTI field. Figure 6A As shown, one or more bits within the UL grant 605 may be reused to indicate HARQ feedback information instead of UL grant information. Figure 6AOne or more bits of an UL grant 605-a of the illustrated RAR PDSCH 420-b and at least a portion of the UL grant 605-b determine feedback configuration 510-b, wherein the one or more bits may indicate HARQ feedback-related information as described herein. By utilizing the existing UL grant in this manner, UE 115 may obtain HARQ feedback-related information without additional signaling or overhead.

[0111] In some examples, UE 115-c may determine, based on one or more indications or configurations, whether the UL grant indicates grant information or HARQ information (e.g., K1 timing, TPC, or resource information) associated with feedback configuration 510-b. In a representative example, UE 115-c may determine to process one or more of UL grants 605 (e.g., including UL grants 605-a to 605-d) based on whether RAR 415 is associated with an inactive PCI (e.g., based on an indication of an inactive PCI within a PDCCH command 405-b). For example, if UE 115-c receives RAR 415 in response to a random access preamble 410 sent in response to an inactive PCI (e.g., of an inactive cell), UE 115-c may be configured (e.g., via RRC signaling) to process UL grant 605 to determine HARQ feedback-related information. If the UE 115 - c is performing CFRA with active PCI, the UE 115 - c may instead be configured to process the UL grant 605 to determine grant-related information.

[0112] As another example, UE 115-c may process UL grant 605 to determine feedback configuration 510-b based on an explicit indication in PDCCH order 405. For example, UE 115-c may receive PDCCH order 405 that includes a 1-bit indicator in a field of PDCCH order 405. If the bit field is set to 0, UE 115-c may process UL grant 605 in RAR PDSCH 420-a as including grant-related information. Otherwise, if the bit field is set to 1, UE 115-c may treat UL grant 605 as including HARQ feedback-related information for transmission of feedback message 505. By including the indication in PDCCH order 405, additional signaling may be avoided and resources may be saved.

[0113] Figure 6B The payload format 602 may be used to indicate HARQ related information and include a reference Figure 4BThe RAR PDSCH 420-c may include an RAR payload format with different fields than the payload format 402 described. For example, the RAR PDSCH 420-c may include a format with three reserved bits (instead of one reserved bit) and two TA commands. In addition, the payload format 602 may be octet-aligned to three octets (instead of seven octets) and may not include additional fields for temporary C-RNTI or UL grant. The RAR PDSCH 420-c may also include a specific feedback field 610 for indicating a feedback configuration 510 (such as feedback configuration 510-c). For example, the RAR PDSCH 420-c may include a feedback field 610 for TPC, a feedback field 610 for a K1 timing indicator, and a feedback field 610 for a PUCCH resource indicator for transmitting HARQ feedback. In some examples, the UE 115-c may process information related to HARQ feedback based on the format of the RAR PDSCH 420-c. For example, if UE 115-c determines that RAR PDSCH 420-c has a payload format, UE 115-c may send feedback message 505 based on feedback configuration 510-c within PDSCH 420-c (e.g., using the included TPC, K1 timing indicator, and PUCCH resource information). In some examples, UE 115-c may refrain from sending feedback message 505 if the UE receives RAR PDSCH 420 in a different format (e.g., the format of RAR PDSCH 420-a or 420-b).

[0114] Figure 7 An example of a PDCCH format 700 supporting random access enhancement for multiple TRPs according to one or more aspects of the present disclosure is illustrated. The PDCCH DCI format 700 may illustrate an example for implementing one or more aspects of the wireless communication systems 100 and 200, the TCI state diagram 300, the process flows 401 and 500, and the payload formats 402, 601, and 602. For example, the PDCCH format 700 may illustrate an example for use in Figure 5 In some examples, PDCCH format 700 may represent a configuration for RAR PDCCH 425-a to indicate a feedback configuration 510-d for UE 115-c to send feedback message 505, where feedback configuration 510-d may represent a configuration for RAR PDCCH 425-a to indicate a feedback configuration 510-d for UE 115-c to send feedback message 505. Figure 5 、 Figure 6A and Figure 6B Feedback configuration 510 in.

[0115] The RAR PDCCH 425-a may be a DCI format 1_0 scrambled by a random access radio network temporary identifier (RA-RNTI). For example, the PDCCH 425-a may include a DCI having one or more fields 430 including bits, where the bits of field 430 are scrambled by the RA-RNTI. Scrambling with the RA-RNTI may indicate to the UE 115-c that the reserved bits of the PDCCH 425-a include or indicate a feedback configuration. The PDCCH 425-a DCI may include fields 430 for one or more least significant bits (LSBs) for frequency domain resource allocation (FDRA), time domain resource allocation (TDRA), virtual resource block (VRB) to physical resource block (PRB) mapping, modulation and coding scheme (MCS), transport block (TB) scaling, and SFN. The PDCCH 425-a DCI may also include one or more reserved bits 705. In some examples, the UE 115-c may determine the feedback configuration 510-d based on the one or more reserved bits in the PDCCH 425. For example, the PDCCH 425-a DCI may indicate the feedback configuration 510-d within one or more reserved bits 705-a. Specifically, the reserved bits 705-a1 may indicate the TPC, K1 timing indicator, and PUCCH resource indicator as described herein (e.g., an index associated with the TPC, K1 timing indicator, and PUCCH resource indicator, or a value of the TPC, K1 timing indicator, and PUCCH resource indicator). The reserved bits 705-a may also include additional unused reserved bits 705-a2. In some examples, the reserved bits 705-a indicating the TPC, K1 timing indicator, and PUCCH resource indicator may also be scrambled by the RA-RNTI, where scrambling with the RA-RNTI may indicate to the UE 115-c that the reserved bits of the PDCCH 425-a include or indicate those parameters of the feedback configuration. In some examples, by determining HARQ feedback-related information from the reserved bits 705 of the PDCCH 425, the UE 115-c may avoid additional signaling and save one or more resources and power.

[0116] In some examples, the UE 115-c may determine whether to process or ignore the reserved bits 705 based on one or more indications or configurations. In a representative example, the UE 115-c may determine to process the reserved bits 705-a based on the RAR 415 including the RAR PDCCH 425-a being associated with an inactive PCI (e.g., based on an indication of the inactive PCI within the PDCCH command 405-b). For example, if the UE 115-c receives the RAR 415 in response to a random access preamble 410 sent associated with an inactive PCI, the UE 115-c may be configured (e.g., via RRC signaling) to process the reserved bits 705-a1 to determine the feedback configuration 510-d. If the UE 115-c is performing CFRA with an active PCI, the UE 115-c may otherwise be configured to ignore the reserved bits 705-a, including the reserved bits 705-a1 and 705-a2.

[0117] As another example, UE 115 c may process reserved bit 705-a1 to determine feedback configuration 510-d based on an explicit indication in PDCCH order 405. For example, UE 115-c may receive PDCCH order 405 that includes a 1-bit indicator in a field of PDCCH order 405. If the bit field is set to 0, UE 115-c may ignore reserved bit 705. Otherwise, if the bit field is set to 1, UE 115-c may process reserved bit 705-a1 to obtain information for scheduling feedback message 505.

[0118] In some examples, whether HARQ feedback information is being provided (e.g., by the network entity 105-c) may be indicated by a PDCCH order 405. If the PDCCH order indicates that HARQ feedback information is being provided, the PDCCH order 405 may further indicate whether the relevant feedback configuration 510 is indicated in the RAR PDSCH 420 or the RAR PDCCH 425. For example, the PDCCH order 405 may indicate whether the PDSCH 420 indicates the feedback configuration 510, or whether one or more reserved bits 705 in the PDCCH 425 of the RAR 415 indicate the feedback configuration 510. Based on the indication, the UE 115-c may determine the feedback configuration 510 and may send the feedback message 505 according to the correct TPC, K1 timing indicator, and resources for reception at the network entity 105-c. Thus, by determining the feedback configuration 510 that indicates HARQ feedback-related information from the PDSCH 420 or PDCCH 425 of the RAR 415 , the UE 115 - c may be able to accurately send feedback to the network entity 105 - c .

[0119] Figure 8An example of a process flow 800 for supporting random access enhancements for multiple TRPs in accordance with one or more aspects of the present disclosure is illustrated. The process flow 800 may illustrate implementing one or more aspects of the wireless communication systems 100 and 200, the TCI state assignment diagram 300, the process flows 401 and 500, the payload formats 402, 601, and 602, and the PDCCH format 700. For example, the process flow 800 may illustrate transmitting one or more RAR PDCCHs 425 and PDSCHs 420 of a RAR 415 between a UE 115-d and a network entity 105-d via one or more TRPs 205, which may represent references to the RARs. Figures 1 to 7 Similar CFRA signaling between the UE 115 and the network entity 105 is described. In some examples, the process flow 800 can perform one or more blind retransmissions of the RAR PDSCH 420 as described herein. In some examples, the process flow 800 can support blind retransmissions for RAR in 4-step CFRA or other random access procedures.

[0120] For example, the network entity 105-d may send a PDCCH command 405-c (e.g., a PDCCH including a DCI instructing the UE 115-d to perform a random access procedure with the TRP 205-g) to the UE 115-d via the TRP 205-g (e.g., associated with an active PCI), wherein the PDCCH command 405-c may instruct the UE 115-d to perform a CFRA procedure using a random access configuration associated with the CORESETPoolIndex or PCI, as described herein. For example, the PDCCH command 405-c may indicate an inactive PCI associated with the TRP 205-h, such that the UE 115-d may perform CFRA with the TRP 205-h. The UE 115 - d may send a RACH (eg, physical RACH (PRACH)) preamble associated with the PCI (or CORESETPoolIndex) to the network entity 105 - d via the TRP 205 - h in response to the PDCCH order 405 - c .

[0121] Based on the preamble 410-c, the network entity 105-d may transmit one or more blind RARPDSCH 420 retransmissions within the RAR window 805 to increase the reliability of the RAR 415 transmission. For example, the UE 115-d may receive a RARPDCCH 425-b transmitted by the RAR 415, where the RAR PDCCH indicates a retransmission configuration 810-a that identifies a number of transmissions of the RAR PDSCH 420-d, where the UE 115-d may monitor the number of transmissions received within the RAR window 805-a (e.g., duration) based on the RAR PDCCH 425-b. That is, after transmitting the RAR PDCCH 425-b, the network entity 105-d may transmit the RAR PDSCH 420-d multiple times within the RAR window 805-a (e.g., including a first transmission and three retransmissions). Thus, by including multiple transmissions of the RAR PDSCH 420-d, the network entity 105-d may improve the reliability of the RAR 415 transmissions and increase the chances that the UE 115-d successfully receives the RAR PDSCH 420-d. For example, the UE 115-d may successfully receive the PDSCH 420-d based on the number of monitored transmissions.

[0122] In some examples, the RAR PDCCH 425-b may indicate a redundancy version (RV) sequence that may be mapped to multiple RAR PDSCH opportunities within the RAR window 805-a for communicating RAR PDSCH 420-d transmissions. For example, the RAR PDCCH 425-b may indicate a retransmission configuration that identifies a starting RV value within one or more fields of the RAR PDCCH 425-b (e.g., within one or more reserved bits 705). The RV values ​​of the RV sequence may be cyclically mapped to one or more RAR PDSCH opportunities based on a predefined order and starting from the starting RV value (e.g., by the UE 115-d or the network entity 105-d). For example, the order of RV values ​​{0, 2, 3, 1} may be mapped to four RAR PDSCH opportunities occurring within the RAR window 805-a. In some examples, the UE 115-d may monitor the number of RAR PDSCH 420-d transmissions within the multiple RAR PDSCH opportunities based on the mapped RV sequence. In some examples, a default RV sequence may be used by UE 115 - d and mapped without any indication of an RV starting value within the RAR PDCCH 425 - b .

[0123] In some examples, blind retransmission related information can be indicated by reusing some reserved bits in the RAR PDCCH 425-b (e.g., DCI format 1_0 scrambled by RA-RNTI). For example, the UE 115-c can determine whether one or more reserved bits 705 of the RAR PDCCH 425-b indicate a retransmission configuration based on one or more indications or configurations. The blind retransmission related information can indicate, for example, the number of transmissions or retransmissions or both of the RAR PDCCH 425-b, the RV sequence, the starting RV value, or any combination thereof. In some examples, RRC signaling can indicate whether the UE 115-c is to use the reserved bits of the PDCCH 425-b to obtain blind retransmission related information. For example, the UE 115-c can be configured by RRC signaling to determine the reserved bits 705 for processing the PDCCH 425-b. In some examples, if RACH (e.g., PRACH) is enabled for an inactive PCI (e.g., via signaling from a network entity), the RRC configuration may indicate that the UE 115-c may use the reserved bit 705 to determine blind retransmission related information. Otherwise, if the UE 115-c is performing CFRA with an active PCI, the UE 115c may be configured to ignore the reserved bit 705 and may refrain from monitoring retransmissions of the RAR PDSCH 420-d. As another example, the UE 115-c may process the reserved bit 705 based on an explicit indication in the PDCCH order 405-c to determine the feedback configuration 510-d. For example, the PDCCH order 405-c (e.g., via DCI) may indicate whether the UE 115-c is to process the reserved bit 705.

[0124] Figure 9 An example of a process flow 900 for supporting random access enhancements for multiple TRPs according to one or more aspects of the present disclosure is illustrated. Process flow 900 may illustrate implementing one or more aspects of wireless communication systems 100 and 200, TCI state diagram 300, process flows 401, 500, and 800, payload formats 402, 601, and 602, and PDCCH format 700. For example, process flow 900 may illustrate a CFRA procedure between UE 115-b and network entity 105-b of FIG. 4 using TRPs 205-c and 205-d.

[0125] In some examples, the CFRA process may include a power ramp for retransmissions. For example, the UE 115-b and the network entity 105-b may exchange PDCCH commands 405-a, random access preambles 410-a, and RARs 415-a as described with reference to FIG4 with or without performing HARQ feedback. However, the UE 115-b may fail to receive the RAR 415-a due to interference, due to the network entity 105-b failing to receive the random access preamble 410-a and therefore failing to send the RAR 415-a, or due to one or more other factors. In response to failed RAR reception at the UE 115-b, the UE 115-b may retransmit the random access preamble 410 according to a power ramp configuration to increase the chance of successful preamble transmission. For example, the UE 115-b may include a preambleReceivedTargetPower configured by RRC to define the initial random access preamble transmit power. The overall equation for the transmit power with ramping can then be defined to set the total transmit power or PREAMBLE_RECEIVED_TARGET_POWER to the following equation 1:

[0126]

[0127] DELTA_PREAMBLE may represent a power offset based on the preamble format, and PREAMBLE_POWER_RAMPING_COUNTER may represent a counter used to increase the power at each additional attempt of retransmission. For example, if UE 115-b does not change beams, the counter may keep increasing at each additional preamble transmission. In some examples, if UE 115-b performs beam switching, the counter may remain unchanged (i.e., paused). PREAMBLE_POWER_RAMPING_STEP may represent a power ramping step for CFRA, which may be configured by the parameter powerRampingStep for 4-step RACH or 4-step CFRA as described herein. Additionally, POWER_OFFSET_2STEP_RA may be used when switching from 2-step RACH to 4-step RACH. If switching, POWER_OFFSET_2STEP_RA may be defined by Equation 2 below:

[0128]

[0129] Otherwise, POWER_OFFSET_2STEP_RA may be set to 0. In some examples, for CFRA triggered for TA acquisition, only the TA command indication in RAR 415 (e.g., RAR 415-a) may be used. Therefore, one or more additional fields 430 may remain empty or unused, such as Figure 4B UL grant or TC-RNTI field shown. Thus, in some cases, instead of using RAR 415 as a response to random access preamble 410 in CFRA, MAC-CE 305 may be used to indicate an absolute TA command. For example, at 905, UE 115-b may receive MAC-CE 305-c indicating an absolute TA command (e.g., associated with an inactive PCI and TRP 205-d) instead of RAR 415-a. At 910, in response, UE 115-b may send a feedback message 505-b in response to receiving MAC-CE 305-c. For example, UE 115-b may send a HARQ-ACK feedback message to indicate successful or unsuccessful reception of MAC-CE 305-c.

[0130] In some examples, UE 115-b may be configured with a RAR window 805 following transmission of the random access preamble 410 for receiving a RAR 415 as described herein, wherein if the RAR 415 is not received within the RAR window 805, the UE 115-b may perform a power ramp-up. However, when receiving the MAC-CE 305-b, the UE 115-b may not be configured with a window and, therefore, may not be able to determine a power ramp-up to retransmit the random access preamble 410-a upon receiving a later PDCCH command that includes the same PCI, the same SSB, the same preamble, or any combination thereof as a previously received PDCCH command. Furthermore, if the network entity 105-b (e.g., a gNB) does not receive the random access preamble 410-a, the UE 115-b may be triggered to retransmit the random access preamble 410-a. Thus, the techniques described herein may enable the UE 115 to define a power ramp-up procedure for RAR-free FRA, as described with reference to FIG. Figure 10A 、 Figure 10B 、 Figure 11A and Figure 11B described.

[0131] Figure 10A and Figure 10BExamples of process flows 1001 and 1002 supporting random access enhancements for multiple TRPs according to one or more aspects of the present disclosure are illustrated. The process flows 1001 and 1002 may illustrate implementing one or more aspects of the wireless communication systems 100 and 200, the TCI state assignment diagram 300, the process flows 401, 500, 800, and 900, the payload formats 402, 601, and 602, and the PDCCH format 700. For example, the process flows 1001 and 1002 may illustrate CFRA-triggered TA acquisition communicated between a UE 115-e and a network entity 105 via a TRP 205-i, which may represent the UE 115, the network entity 105, and the TRP 205, as shown in FIG. Figures 1 to 9 In some examples, process flows 1001 and 1002 can illustrate a power ramp-up process for TA acquisition using RAR-free CFRA as described herein.

[0132] For example, process flows 1001 and 1002 may represent power ramping for RAR-free CFRA based on a random access attempt counter and power adjustment as described herein. The transmit power of the random access preamble 410 for RAR-free CFRA may be defined based on the RACH attempt counter by the following equation 3:

[0133]

[0134] You can refer to Figure 9 3, and may represent a power adjustment size (e.g., a configurable step size). In some examples, the UE 115-e may adjust the power of the transmission of the random access preamble 410 according to Equation 3 as described herein.

[0135] Figure 10AThe process flow 1001 may represent a power ramp-up procedure within the same PRACH (e.g., CFRA) procedure. For example, the UE 115-e may attempt to receive one or more MAC-CEs in response to a RACH (e.g., PRACH) transmission and may perform a power ramp-up procedure for multiple RACH attempts (e.g., ramping up power for each subsequent RACH attempt) based on a RACH attempt counter and a configurable step size as described herein. Figure 10A , at 1005, the network entity 105 may transmit a first PDCCH command 405-d1 for a first PRACH procedure via the TRP 205-i, and the UE 115-e may receive the first PDCCH command, wherein the PDCCH command 405-d1 may instruct the UE 115-d to transmit a first random access preamble 410 associated with a first preamble index, a first PCI, and a first SSB index. In some examples, when the first RACH procedure is initialized, the UE 115-e may set a RACH attempt counter to 1. For example, at 1006, after receiving the PDCCH command 405-d1, the UE 115-e may set a PREAMBLE_TRANSMISSION_COUNTER to 1.

[0136] At 1010, the network entity 105 may fail to receive the random access preamble 410 for the first PRACH process. For example, the UE 115-e may transmit the first random access preamble 410-d1 at a first power level (such as an initial power level) based on Equation 3. Thus, the TRP 205-i may fail to receive the first preamble based on interference or one or more other failed messages or processes, or based on a power level that is too low to be detected by the TRP 205-i. In response to the failed preamble transmission, at 1015, the network entity 105 may transmit a second PDCCH order 405-d2 to the UE 115-e via the TRP 205-i. In some examples, the second PDCCH order 405-d2 may also instruct the UE 115-e to transmit the preamble using the first preamble index, the first PCI, and the first SSB index.

[0137] In some examples, if the UE 115-e receives a PDCCH command 405 indicating a RACH associated with the same PCI, SSB, and preamble as a previous RACH procedure, the RACH attempt counter may be incremented by one. For example, at 1020, the UE 115-e may determine a value for PREAMBLE_TRANSMISSION_COUNTER based on whether the second PDCCH command 405-d2 indicates the same preamble index, PCI, and SSB index as the first PDCCH command 405-d1. By determining such identical parameters, the UE 115-e may determine that the PDCCH command 405-d2 belongs to the same first PRACH procedure and may perform a power ramp-up accordingly (because the reception of the new PDCCH command 405 indicates a failed preamble transmission). Therefore, based on the PDCCH command 405-d2 indicating the first preamble index, PCI, and SSB index, the UE 115-e may increment the value for PREAMBLE_TRANSMISSION_COUNTER to increase the power of the next preamble transmission. For example, at 1025, the UE 115-e may transmit the second preamble 410-d2 at a second higher transmit power level based on the PREAMBLE_TRANSMISSION_COUNTER incremented to 1 according to Equation 3. Thus, based on the second higher transmit power level, the network entity 105 may transmit a MAC-CE 305 via the TRP 205-i at 1030, the MAC-CE indicating a TA command for a timing advance group (TAG) identifier (e.g., TAG-ID) corresponding to the first PRACH process. The UE 115-e may receive the MAC-CE 305 and may transmit a HARQ-ACK response (e.g., ACK) to indicate successful receipt of the MAC-CE 305.

[0138] In some examples, when the UE 115-e receives a MAC-CE indicating a TA command for the corresponding TAG ID (e.g., 3 ms after the ACK corresponding to the PDSCH carrying the MAC CE), the RACH attempt counter can be reset to 1 at 1035. For example, the UE 115-e can reset the PREAMBLE_TRANSMISSION_COUNTER to 1 based on receiving the MAC-CE 305 for the same PRACH process. That is, the UE 115-e can reset the attempt counter based on determining that the MAC-CE indicates a TA command for the TAG-ID associated with the first PRACH process. In some examples, the UE 115-e can reset the attempt counter after a duration X (e.g., 3 ms) after sending the HARQ-ACK to the network entity 105.

[0139] Figure 10B The process flow 1002 may illustrate a power ramp-up process performed in accordance with the start of a new PRACH process. In some examples, if the UE 115-e receives a PDCCH command 405 indicating a PRACH associated with a different PCI, a different SSB, and a different preamble, or associated with a different TAG ID, the UE 115-e may reset the RACH attempt counter to 1. For example, the UE 115-e and the network entity 105 (via the TRP 205-i) may exchange one or more PDCCH commands and preambles 410-d1 and 410-d2 and perform a power ramp-up, as described with reference to FIG. Figure 10A As described. However, in some examples, UE 115-d may receive a PDCCH command 405 for a second PRACH procedure (e.g., before receiving the MAC-CE). For example, at 1040, UE 115-e may receive a third PDCCH command 405-d3 commanding UE 115-e to send a random access preamble 410 associated with a second preamble index, a second PCI, and a second SSB index. Based on determining that the second preamble index, the second PCI, and the second SSB index are different from the first preamble index, PCI, and SSB index, UE 115-e may determine that PDCCH command 405-d3 corresponds to a second PRACH procedure (e.g., sent by another TRP 205 or network entity 105) and may reset PREAMBLE_TRANSMISSION_COUNTER to 1 at 1045. In some examples, upon receiving a PDCCH command 405 indicating a different PCI, a different SSB, and a different preamble during an ongoing RACH procedure, the UE 115-e may assume the start of a new RACH procedure. At 1050, the UE 115-e may transmit a random access preamble 410-d3 for a second PRACH procedure. In some examples, the UE 115-e may also determine that the PDCCH command 405-d3 corresponds to a different TAG ID and may accordingly reset the counter to 1. Additionally or alternatively, the UE 115-e may reset the PREAMBLE_TRANSMISSION_COUNTER to 1 based on the PREAMBLE_TRANSMISSION_COUNTER reaching a maximum count.

[0140] In some examples, by implementing an attempt counter, the UE 115 - e can achieve successful retransmission of the preamble during the PRACH. Additionally or alternatively, the UE 115 - e can save one or more resources by mitigating failed transmissions or miscommunications with the network entity 105 .

[0141] Figure 11A and Figure 11BExamples of process flows 1101 and 1102 supporting random access enhancements for multiple TRPs according to one or more aspects of the present disclosure are illustrated. The process flows 1101 and 1102 may illustrate one or more aspects of implementing the wireless communication systems 100 and 200, the TCI state assignment diagram 300, the process flows 401, 500, 800, 900, 1001, and 1002, the payload formats 402, 601, and 602, and the PDCCH format 700. For example, the process flows 1101 and 1102 may illustrate CFRA-triggered TA acquisition and power ramp-up for a UE 115-f in communication with a network entity 105 via a TRP 205-j, as described with reference to FIG. Figure 10A and Figure 10B As described, UE 115-f may represent UE 115-e and TRP 205-j may represent TRP 205-i. In some examples, process flows 1101 and 1102 may illustrate power ramping for RAR-free CFRA based on random access attempt counters, power adjustment sizes, and power ramp-up counters as described herein.

[0142] For example, the power ramp up of the transmit power of the random access preamble 410 for the UE 115 - f may be defined based on a power ramp up counter for the preamble according to Equation 4 below:

[0143]

[0144] For example, Equation 4 may represent the same factors as in Equation 3, but PREAMBLE_POWER_RAMPING_COUNTER may be substituted for PREAMBLE_TRANSMISSION_COUNTER. That is, PREAMBLE_POWER_RAMPING_COUNTER may represent a power ramp-up counter for a preamble (e.g., a preamble ramp-up counter) as described herein, and PREAMBLE_POWER_RAMPING_STEP may represent a power adjustment size (e.g., a configurable step size).

[0145] In such Figure 11AIn the illustrative example shown in process flow 1101 of FIGURE 10, UE 115-f may attempt to receive MAC-CE 305 in response to a PRACH transmission of preamble 410 and may perform power ramping for multiple RACH attempts based on a RACH attempt counter, a power ramp-up counter, and a power adjustment size. For example, when a RACH for a first PCI, SSB, and preamble is initialized, UE 115-f may set both PREAMBLE_TRANSMISSION_COUNTER and PREAMBLE_POWER_RAMPING_COUNTER to 1, as described with reference to FIGURE 10. Figure 11A described.

[0146] In some examples, if the UE receives a PDCCH command indicating a RACH associated with the same PCI / preamble as the previous RACH, the RACH attempt counter may be incremented by 1. For example, at 1105, UE 115-f may receive PDCCH command 405-e2, which may indicate the same preamble index and the same PCI as the previous PDCCH command 405-e1 used to transmit the first preamble 410-e1, and may increment the RACH attempt counter at 1110. However, if PDCCH command 405-e2 indicates a different SSB than PDCCH command 405-e1, the power ramp-up counter may not be changed. Therefore, at 1110, UE 115-f may increment the PREAMBLE_TRANSMISSION_COUNTER based on the same PCI and preamble index, but may leave the PREAMBLE_POWER_RAMPING_COUNTER unchanged based on the different SSB index. Based on the unchanged ramp-up counter, UE 115 - f may not increase the power of the next transmission and may send the random access preamble 410 - e 2 according to the same initial transmit power level.

[0147] In some examples, when the UE 115-f receives a MAC-CE 305 indicating a TA command for the corresponding TAG ID (e.g., 3 ms after the ACK corresponding to the PDSCH 420 carrying the MAC-CE), the RACH attempt counter and the power ramp-up counter may be reset to 1. For example, the UE 115-f may receive the MAC-CE 305, send a HARQ-ACK response, and reset both the PREAMBLE_TRANSMISSION_COUNTER and the PREAMBLE_POWER_RAMPING_COUNTER after a duration X (e.g., 3 ms) based on the MAC-CE 305 indicating that the TA associated with the same TAG-ID resets both the PREAMBLE_TRANSMISSION_COUNTER and the PREAMBLE_POWER_RAMPING_COUNTER, as described with reference to FIG. Figure 10A and Figure 10BWhen the RACH attempt counter reaches the maximum number of preamble transmissions, the UE 115-f may additionally reset the RACH attempt counter and the power ramp-up counter.

[0148] Additionally or alternatively, such as Figure 11B As shown in process flow 1102 of , if the UE 115-f receives a PDCCH command with the same preamble index and PCI as a previous PDCCH command and the same SSB index, the power ramp-up counter may be incremented by 1 and the RACH attempt counter may be incremented by 1. For example, at 1115, the UE 115-f may increment both the PREAMBLE_TRANSMISSION_COUNTER and the PREAMBLE_POWER_RAMPING_COUNTER in response to the PDCCH command 405 indicating the same PCI / preamble / SSB. The UE 115-f may also perform power ramping according to Equation 4 based on the incremented counter and transmit a random access preamble 410-e2 at a higher transmit power level, and may reset the counter after successfully receiving a MAC-CE 305 with a TA associated with the same TAG as the corresponding PRACH. Furthermore, if UE 115-f receives a PDCCH indicating a different PCI, a different preamble index, and a different SSB, UE 115-a may continue the ongoing PRACH process or initiate a new PRACH process. In some examples, if parallel RACH processes are supported at UE 115-f, the present disclosure may include the following: Figure 10A 、 Figure 10B 、 Figure 11A and Figure 11B The described procedures may be applied individually to each RACH procedure associated with the corresponding PCI / preamble.

[0149] In some examples, by implementing a random access attempt counter and a power ramp-up counter, UE 115-f can implement selective power adjustment based on the transmit beam. Figure 11A As described, UE 115-f may perform power ramping when the PCI, preamble, and SSB index are the same, but may suppress power ramping when the SSBs are different, even if the PCI and preamble index are the same. This may enable UE 115-f to perform retransmissions at the same power level for different beams, which may save power at UE 115-f.

[0150] Figure 12A block diagram 1200 illustrates a device 1205 supporting random access enhancements for multiple TRPs according to one or more aspects of the present disclosure. The device 1205 may be an example of aspects of the UE 115 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0151] The receiver 1210 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to random access enhancements for multiple TRPs). The information may be passed to other components of the device 1205. The receiver 1210 may utilize a single antenna or a collection of multiple antennas.

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

[0153] The communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of random access enhancements for multiple TRPs as described herein. For example, the communication manager 1220, the receiver 1210, the transmitter 1215, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

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

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

[0157] According to examples disclosed herein, the communication manager 1220 may support wireless communications at a UE. For example, the communication manager 1220 may be configured to or otherwise support components for receiving a random access command message from a network entity, the random access command message instructing the UE to perform a random access procedure using a random access configuration associated with a coreset pool index or PCI. The communication manager 1220 may be configured to or otherwise support components for sending a random access preamble associated with the coreset pool index or PCI for the random access procedure to the network entity in response to the random access command message. The communication manager 1220 may be configured to or otherwise support components for receiving a random access replay (RAR) for the random access procedure from the network entity within a RAR window. The communication manager 1220 may be configured to or otherwise support components for sending a feedback message to the network entity indicating whether the UE successfully received the RAR based on a feedback configuration, the feedback configuration being based on the RAR.

[0158] Additionally or alternatively, according to examples disclosed herein, the communication manager 1220 may support wireless communications at a UE. For example, the communication manager 1220 may be configured to or otherwise support means for receiving a random access command message from a network entity, the random access command message instructing the UE to perform a random access procedure using a random access configuration associated with a coreset pool index or PCI. The communication manager 1220 may be configured to or otherwise support means for sending a random access preamble associated with the coreset pool index or PCI for the random access procedure to the network entity in response to the random access command message. The communication manager 1220 may be configured to or otherwise support means for receiving a RAR control message for the random access procedure from the network entity within a RAR window, the RAR control message indicating a retransmission configuration identifying a number of RAR data messages to be transmitted. The communication manager 1220 may be configured to or otherwise support means for monitoring the number of RAR data messages to be transmitted based on the RAR control message.

[0159] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1220 may support wireless communications at a UE. For example, the communication manager 1220 may be configured to or otherwise support components for receiving a first random access command message for a random access procedure from a network entity, the first random access command message instructing the UE to transmit a first random access preamble associated with a first preamble index, a first PCI, and a first SSB index. The communication manager 1220 may be configured to or otherwise support components for transmitting the first random access preamble of the random access procedure to the network entity at a first transmit power level in response to the first random access command message. The communication manager 1220 may be configured to or otherwise support components for receiving a second random access command message from the network entity, the second random access command message instructing the UE to transmit a second random access preamble associated with a second preamble index, a second PCI, and a second SSB index. The communication manager 1220 may be configured to or otherwise support components for sending a second random access preamble to a network entity at a second transmit power level, wherein the second transmit power level is based on a power adjustment size and a random access attempt counter that is based at least in part on whether the second preamble index, the second PCI, and the second SSB index are the same as the first preamble index, the first PCI, and the first SSB index.

[0160] By including or configuring a communication manager 1220 according to the examples described herein, the device 1205 (e.g., a processor controlling the receiver 1210, the transmitter 1215, the communication manager 1220, or a combination thereof or otherwise coupled thereto) may support techniques for reducing processing, lowering power consumption, and more efficiently utilizing communication resources.

[0161] Figure 13 A block diagram 1300 illustrates a device 1305 supporting random access enhancements for multiple TRPs according to one or more aspects of the present disclosure. The device 1305 may be an example of aspects of the device 1205 or UE 115 as described herein. The device 1305 may include a receiver 1310, a transmitter 1315, and a communication manager 1320. The device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0162] The receiver 1310 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to random access enhancements for multiple TRPs). The information may be passed to other components of the device 1305. The receiver 1310 may utilize a single antenna or a collection of multiple antennas.

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

[0164] Device 1305 or its various components may be examples of components for performing various aspects of random access enhancement for multiple TRPs as described herein. For example, communication manager 1320 may include a random access command component 1325, a preamble component 1330, a random access response component 1335, a feedback component 1340, or any combination thereof. Communication manager 1320 may be an example of various aspects of communication manager 1220 as described herein. In some examples, communication manager 1320 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise in conjunction with receiver 1310, transmitter 1315, or both. For example, communication manager 1320 may receive information from receiver 1310, transmit information to transmitter 1315, or be integrated with receiver 1310, transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.

[0165] According to examples disclosed herein, a communication manager 1320 can support wireless communications at a UE. A random access command component 1325 can be configured to or otherwise support means for receiving a random access command message from a network entity, the random access command message instructing the UE to perform a random access procedure using a random access configuration associated with a coreset pool index or PCI. A preamble component 1330 can be configured to or otherwise support means for sending a random access preamble associated with the coreset pool index or PCI for a random access procedure to the network entity in response to the random access command message. A random access response component 1335 can be configured to or otherwise support means for receiving a random access response (RAR) for a random access procedure from the network entity within a RAR window. A feedback component 1340 can be configured to or otherwise support means for sending a feedback message to the network entity indicating whether the UE successfully received the RAR based on a feedback configuration, the feedback configuration being based on the RAR.

[0166] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1320 can support wireless communications at a UE. A random access command component 1325 can be configured to or otherwise support means for receiving a random access command message from a network entity, the random access command message instructing the UE to perform a random access procedure using a random access configuration associated with a coreset pool index or PCI. A preamble component 1330 can be configured to or otherwise support means for sending a random access preamble associated with the coreset pool index or PCI for a random access procedure to the network entity in response to the random access command message. A random access response component 1335 can be configured to or otherwise support means for receiving a RAR control message for a random access procedure from the network entity within a RAR window, the RAR control message indicating a retransmission configuration identifying a number of RAR data messages to be transmitted. The random access response component 1335 can be configured to or otherwise support means for monitoring the number of RAR data messages to be transmitted based on the RAR control message.

[0167] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1320 can support wireless communications at a UE. The random access command component 1325 can be configured to or otherwise support components for receiving a first random access command message for a random access procedure from a network entity, the first random access command message instructing the UE to transmit a first random access preamble associated with a first preamble index, a first PCI, and a first SSB index. The preamble component 1330 can be configured to or otherwise support components for transmitting, in response to the first random access command message, a first random access preamble for a random access procedure to the network entity at a first transmit power level. The random access command component 1325 can be configured to or otherwise support components for receiving a second random access command message from the network entity, the second random access command message instructing the UE to transmit a second random access preamble associated with a second preamble index, a second PCI, and a second SSB index. The preamble component 1330 may be configured to or otherwise support components for transmitting a second random access preamble to a network entity at a second transmit power level, wherein the second transmit power level is based on a power adjustment size and a random access attempt counter that is based at least in part on whether the second preamble index, the second PCI, and the second SSB index are the same as the first preamble index, the first PCI, and the first SSB index.

[0168] Figure 14 A block diagram 1400 of a communication manager 1420 supporting random access enhancements for multiple TRPs in accordance with one or more aspects of the present disclosure is illustrated. The communication manager 1420 may be an example of aspects of the communication manager 1220, the communication manager 1320, or both as described herein. The communication manager 1420 or its various components may be examples of components for performing various aspects of random access enhancements for multiple TRPs as described herein. For example, the communication manager 1420 may include a random access command component 1425, a preamble component 1430, a random access response component 1435, a feedback component 1440, an attempt counter component 1445, a power ramp counter component 1450, a control element component 1455, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0169] According to examples disclosed herein, a communication manager 1420 can support wireless communications at a UE. A random access command component 1425 can be configured to or otherwise support means for receiving a random access command message from a network entity, the random access command message instructing the UE to perform a random access procedure using a random access configuration associated with a coreset pool index or PCI. A preamble component 1430 can be configured to or otherwise support means for sending a random access preamble associated with the coreset pool index or PCI for a random access procedure to the network entity in response to the random access command message. A random access response component 1435 can be configured to or otherwise support means for receiving a random access response (RAR) for a random access procedure from the network entity within a RAR window. A feedback component 1440 can be configured to or otherwise support means for sending a feedback message to the network entity indicating whether the UE successfully received the RAR based on a feedback configuration, the feedback configuration being based on the RAR.

[0170] In some examples, the feedback configuration may include at least one of: a feedback timing indicator indicating a timing offset between reception of the RAR and transmission of the feedback message; a PUCCH resource indicator indicating a PUCCH resource used for transmission of the feedback message; or a TPC command indicating a transmit power-related parameter used for transmission of the feedback message.

[0171] In some examples, the feedback configuration is based on the payload of the RAR.

[0172] In some examples, sending the feedback message according to the feedback configuration is based on the RAR being associated with the PCIs including the inactive PCIs.

[0173] In some examples, sending the feedback message according to the feedback configuration is based on an indication in the random access command message.

[0174] In some examples, sending a feedback message according to a feedback configuration is based on a format of a payload.

[0175] In some examples, the feedback configuration is based on one or more reserved bits in a PDCCH order scrambled by the RA-RNTI.

[0176] In some examples, sending the feedback message according to the feedback configuration is based on the RRC configuration.

[0177] In some examples, sending the feedback message based on the one or more reserved bits is based on an indication in the random access command message.

[0178] In some examples, sending the feedback message according to the feedback configuration is based on an indication in the random access command message.

[0179] In some examples, the random access command message indicates that the payload of the RAR indicates the feedback configuration, or one or more reserved bits in the PDCCH order scrambled by the RA-RNTI indicates the feedback configuration.

[0180] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1420 can support wireless communications at a UE. In some examples, the random access command component 1425 can be configured to or otherwise support means for receiving a random access command message from a network entity, the random access command message instructing the UE to perform a random access procedure using a random access configuration associated with a coreset pool index or PCI. In some examples, the preamble component 1430 can be configured to or otherwise support means for sending a random access preamble associated with the coreset pool index or PCI for a random access procedure to the network entity in response to the random access command message. In some examples, the random access response component 1435 can be configured to or otherwise support means for receiving a RAR control message for a random access procedure from the network entity in a RAR window, the RAR control message indicating a retransmission configuration identifying a number of RAR data messages to be transmitted. In some examples, the random access response component 1435 can be configured to or otherwise support means for monitoring the number of RAR data messages to be transmitted based on the RAR control message.

[0181] In some examples, to support receiving RAR control messages, the random access response component 1435 may be configured as or otherwise support components for receiving a RAR control message indicating a redundant version sequence mapped to a set of multiple RAR data message opportunities, wherein monitoring the number of RAR data message transmissions occurs within the set of multiple RAR data message opportunities based on the redundant version sequence.

[0182] In some examples, to support receiving a RAR control message indicating a redundant version sequence, the random access response component 1435 may be configured as or otherwise support components for receiving a RAR control message indicating a retransmission configuration identifying a starting redundant version value of a redundant version sequence, wherein the redundant version values ​​of the redundant version sequence are cyclically mapped to a set of multiple RAR data message opportunities starting from the starting redundant version value in a defined order.

[0183] In some examples, to support receiving a RAR control message, the random access response component 1435 may be configured as or otherwise support components for receiving a RAR control message including one or more reserved bits indicating a retransmission configuration, the one or more reserved bits being processed based on the RAR control message being associated with a PCI including an inactive PCI.

[0184] In some examples, to support receiving a RAR control message, the random access response component 1435 may be configured as or otherwise support components for receiving a RAR control message including one or more reserved bits indicating a retransmission configuration, the one or more reserved bits being processed based on an indication in the random access command message.

[0185] In some examples, random access response component 1435 can be configured or otherwise support means for receiving a RAR data message based on monitoring the transmission quantity.

[0186] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1420 may support wireless communications at a UE. In some examples, the random access command component 1425 may be configured to or otherwise support components for receiving a first random access command message for a random access procedure from a network entity, the first random access command message instructing the UE to transmit a first random access preamble associated with a first preamble index, a first PCI, and a first SSB index. In some examples, the preamble component 1430 may be configured to or otherwise support components for transmitting the first random access preamble of the random access procedure to the network entity at a first transmit power level in response to the first random access command message. In some examples, the random access command component 1425 may be configured to or otherwise support components for receiving a second random access command message from the network entity, the second random access command message instructing the UE to transmit a second random access preamble associated with a second preamble index, a second PCI, and a second SSB index. In some examples, the preamble component 1430 may be configured to or otherwise support components for sending a second random access preamble to a network entity at a second transmit power level, where the second transmit power level is based on a power adjustment size and a random access attempt counter that is based at least in part on whether the second preamble index, second PCI, and second SSB index are the same as the first preamble index, first PCI, and first SSB index.

[0187] In some examples, the second transmit power level is further based on a power ramp counter based on whether the second preamble index, second PCI, and second SSB index are the same as the first preamble index, first PCI, and first SSB index.

[0188] In some examples, attempt counter component 1445 may be configured to or otherwise support means for incrementing a random access attempt counter based on the second preamble index, second PCI, and second SSB index being the same as the first preamble index, first PCI, and first SSB index.

[0189] In some examples, the attempt counter component 1445 may be configured to or otherwise support components for resetting the random access attempt counter based on the second preamble index, second PCI, or second SSB index being different from the first preamble index, first PCI, or first SSB index.

[0190] In some examples, the attempt counter component 1445 can be configured to or otherwise support means for incrementing the random access attempt counter based on the second preamble index and the second PCI being the same as the first preamble index and the first PCI. In some examples, the power ramp-up counter component 1450 can be configured to or otherwise support means for incrementing the power ramp-up counter based on the second preamble index, the second PCI, and the second SSB index being the same as the first preamble index, the first PCI, and the first SSB index.

[0191] In some examples, the attempt counter component 1445 can be configured to or otherwise support means for incrementing the random access attempt counter based on the second preamble index and the second PCI being the same as the first preamble index and the first PCI. In some examples, the power ramp-up counter component 1450 can be configured to or otherwise support means for maintaining the power ramp-up counter unchanged based on the second preamble index and the second PCI being the same as the first preamble index and the first PCI and the second SSB index being different from the first SSB index.

[0192] In some examples, the control element component 1455 may be configured as or otherwise support components for receiving a control element message from a network entity in response to the first random access preamble transmission, wherein one or more of the random access attempt counter and the power ramp counter are based on receipt of the control element message.

[0193] In some examples, the attempt counter component 1445 may be configured as or otherwise support components for resetting the random access attempt counter based on receipt of a control element message indicating a TA corresponding to a timing advance group identifier (e.g., TAG-ID) associated with the random access procedure.

[0194] In some examples, the power ramp counter component 1450 may be configured as or otherwise support components for resetting the power ramp counter based on receipt of a control element message indicating a TA corresponding to a timing advance group identifier (e.g., TAG-ID) associated with a random access procedure.

[0195] In some examples, attempt counter component 1445 and power ramp-up counter component 1450 can be configured or otherwise support means for resetting the random access attempt counter and the power ramp-up counter, respectively, based on the random access attempt counter reaching a maximum count number.

[0196] Figure 15 A diagram of a system 1500 including a device 1505 supporting random access enhancements for multiple TRPs according to one or more aspects of the present disclosure is illustrated. The device 1505 can be an example of a device 1205, a device 1305, or a UE 115 as described herein, or include components thereof. The device 1505 can communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1505 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1520, an input / output (I / O) controller 1510, a transceiver 1515, an antenna 1525, a memory 1530, code 1535, and a processor 1540. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1545).

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

[0198] In some cases, device 1505 may include a single antenna 1525. However, in some other cases, device 1505 may have more than one antenna 1525, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1515 may communicate bidirectionally via one or more antennas 1525, wired, or wireless links, as described herein. For example, transceiver 1515 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1515 may also include a modem for modulating packets; providing the modulated packets to one or more antennas 1525 for transmission; and demodulating packets received from one or more antennas 1525. Transceiver 1515, or transceiver 1515 and one or more antennas 1525, may be examples of transmitter 1215, transmitter 1315, receiver 1210, receiver 1310, or any combination thereof, or components thereof, as described herein.

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

[0200] The processor 1540 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1540 may be configured to operate the memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1540. The processor 1540 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1530) to cause the device 1505 to perform various functions (e.g., functions or tasks supporting random access enhancements for multiple TRPs). For example, the device 1505 or a component of the device 1505 may include a processor 1540 and a memory 1530 coupled to or coupled to the processor 1540, the processor 1540 and the memory 1530 being configured to perform the various functions described herein.

[0201] According to examples disclosed herein, the communication manager 1520 may support wireless communications at a UE. For example, the communication manager 1520 may be configured to or otherwise support components for receiving a random access command message from a network entity, the random access command message instructing the UE to perform a random access procedure using a random access configuration associated with a coreset pool index or PCI. The communication manager 1520 may be configured to or otherwise support components for sending a random access preamble associated with the coreset pool index or PCI for the random access procedure to the network entity in response to the random access command message. The communication manager 1520 may be configured to or otherwise support components for receiving a random access preamble (RAR) for the random access procedure from the network entity within a RAR window. The communication manager 1520 may be configured to or otherwise support components for sending a feedback message to the network entity indicating whether the UE successfully received the RAR based on a feedback configuration, the feedback configuration being based on the RAR.

[0202] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1520 may support wireless communications at a UE. For example, the communication manager 1520 may be configured to or otherwise support means for receiving a random access command message from a network entity, the random access command message instructing the UE to perform a random access procedure using a random access configuration associated with a coreset pool index or PCI. The communication manager 1520 may be configured to or otherwise support means for sending a random access preamble associated with the coreset pool index or PCI for the random access procedure to the network entity in response to the random access command message. The communication manager 1520 may be configured to or otherwise support means for receiving a RAR control message for the random access procedure from the network entity within a RAR window, the RAR control message indicating a retransmission configuration identifying a number of RAR data messages to be transmitted. The communication manager 1520 may be configured to or otherwise support means for monitoring the number of RAR data messages to be transmitted based on the RAR control message.

[0203] Additionally or alternatively, according to examples as disclosed herein, the communication manager 1520 may support wireless communications at a UE. For example, the communication manager 1520 may be configured to or otherwise support components for receiving a first random access command message for a random access procedure from a network entity, the first random access command message instructing the UE to transmit a first random access preamble associated with a first preamble index, a first PCI, and a first SSB index. The communication manager 1520 may be configured to or otherwise support components for transmitting the first random access preamble of a random access procedure to the network entity at a first transmit power level in response to the first random access command message. The communication manager 1520 may be configured to or otherwise support components for receiving a second random access command message from the network entity, the second random access command message instructing the UE to transmit a second random access preamble associated with a second preamble index, a second PCI, and a second SSB index. The communication manager 1520 may be configured to or otherwise support components for sending a second random access preamble to a network entity at a second transmit power level, wherein the second transmit power level is based on a power adjustment size and a random access attempt counter that is based at least in part on whether the second preamble index, the second PCI, and the second SSB index are the same as the first preamble index, the first PCI, and the first SSB index.

[0204] By including or configuring a communication manager 1520 according to examples as described herein, the device 1505 can support techniques for improving communication reliability, reducing latency, lowering power consumption, more efficiently utilizing communication resources, improving coordination between devices, and extending battery life.

[0205] In some examples, the communication manager 1520 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise coordinating with the transceiver 1515, one or more antennas 1525, or any combination thereof. Although the communication manager 1520 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1520 may be supported or performed by the processor 1540, the memory 1530, the code 1535, or any combination thereof. For example, the code 1535 may include instructions that are executable by the processor 1540 to cause the device 1505 to perform various aspects of random access enhancements for multiple TRPs as described herein, or the processor 1540 and the memory 1530 may be otherwise configured to perform or support such operations.

[0206] Figure 16A flow chart illustrating a method 1600 for supporting random access enhancement for multiple TRPs according to one or more aspects of the present disclosure is illustrated. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described herein. Figures 1 to 15 The described functions may be performed by the UE 115. 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 1605, the method may include receiving a random access command message from a network entity, the random access command message commanding the UE to perform a random access procedure using a random access configuration associated with a CORESET pool index or PCI. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described with reference to Figure 14 The random access command component 1425 is described to perform.

[0208] At 1610, the method may include, in response to the random access command message, sending a random access preamble associated with a CORESET pool index or PCI for a random access procedure to a network entity. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described with reference to Figure 14 The described preamble component 1430 is performed.

[0209] At 1615, the method may include receiving a RAR for a random access procedure from a network entity in a RAR window. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Figure 14 The random access response component 1435 is described as performing.

[0210] At 1620, the method may include sending a feedback message to the network entity indicating whether the UE successfully received the RAR according to the feedback configuration, the feedback configuration being based on the RAR. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Figure 14 The feedback component 1440 described is executed.

[0211] Figure 17 A flowchart illustrating a method 1700 for supporting random access enhancement for multiple TRPs according to one or more aspects of the present disclosure is illustrated. The operations of the method 1700 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE or a component thereof as described herein. Figures 1 to 15The described functions may be performed by the UE 115. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0212] At 1705, the method may include receiving a random access command message from a network entity, the random access command message commanding the UE to perform a random access procedure using a random access configuration associated with a CORESET pool index or PCI. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described with reference to Figure 14 The random access command component 1425 is described to perform.

[0213] At 1710, the method may include, in response to the random access command message, sending a random access preamble associated with a CORESET pool index or PCI for a random access procedure to a network entity. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described with reference to Figure 14 The described preamble component 1430 is performed.

[0214] At 1715, the method may include receiving a RAR control message for a random access procedure from a network entity in a RAR window, the RAR control message indicating a retransmission configuration identifying a number of RAR data messages to be transmitted. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Figure 14 The random access response component 1435 is described as performing.

[0215] At 1720, the method may include monitoring the number of RAR data messages sent based on the RAR control message. The operations of 1720 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described in reference to Figure 14 The random access response component 1435 is described as performing.

[0216] Figure 18 A flow chart illustrating a method 1800 for supporting random access enhancement for multiple TRPs according to one or more aspects of the present disclosure is illustrated. The operations of the method 1800 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a UE or a component thereof as described herein. Figures 1 to 15 The described functions may be performed by the UE 115. 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.

[0217] At 1805, the method may include receiving a first random access command message of a random access procedure from a network entity, the first random access command message commanding the UE to send a first random access preamble associated with a first preamble index, a first PCI, and a first SSB index. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Figure 14 The random access command component 1425 is described to perform.

[0218] At 1810, the method may include, in response to a first random access command message, transmitting a first random access preamble of a random access procedure to a network entity at a first transmit power level. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Figure 14 The described preamble component 1430 is performed.

[0219] At 1815, the method may include receiving a second random access command message from the network entity, the second random access command message commanding the UE to send a second random access preamble associated with a second preamble index, a second PCI, and a second SSB index. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Figure 14 The random access command component 1425 is described to perform.

[0220] At 1820, the method may include transmitting a second random access preamble to the network entity at a second transmit power level, wherein the second transmit power level is based on a power adjustment size and a random access attempt counter, the random access attempt counter being based at least in part on whether the second preamble index, the second PCI, and the second SSB index are the same as the first preamble index, the first PCI, and the first SSB index. The operations of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed as described with reference to Figure 14 The described preamble component 1430 is performed.

[0221] Figure 19 A flowchart illustrating a method 1900 for supporting random access enhancement for multiple TRPs according to one or more aspects of the present disclosure is illustrated. The operations of the method 1900 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a UE or a component thereof as described herein. Figures 1 to 15 The described functions may be performed by the UE 115. 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.

[0222] At 1905, the method may include receiving a first random access command message of a random access procedure from a network entity, the first random access command message commanding the UE to send a first random access preamble associated with a first preamble index, a first PCI, and a first SSB index. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Figure 14 The random access command component 1425 is described to perform.

[0223] At 1910, the method may include, in response to a first random access command message, transmitting a first random access preamble of a random access procedure to a network entity at a first transmit power level. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described in reference to Figure 14 The described preamble component 1430 is performed.

[0224] At 1915, the method may include receiving a second random access command message from the network entity, the second random access command message commanding the UE to send a second random access preamble associated with a second preamble index, a second PCI, and a second SSB index. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described in reference to Figure 14 The random access command component 1425 is described to perform.

[0225] At 1920, the method may include transmitting a second random access preamble to a network entity at a second transmit power level, wherein the second transmit power level is based on a power adjustment size, a random access attempt counter, and a power ramp-up counter, the random access attempt counter and the power ramp-up counter being based at least in part on whether the second preamble index, the second PCI, and the second SSB index are the same as the first preamble index, the first PCI, and the first SSB index. The operations of 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed as described with reference to Figure 14 The described preamble component 1430 is performed.

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

[0227] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a random access command message from a network entity, the random access command message instructing the UE to perform a random access procedure using a random access configuration associated with a control resource set pool index or a physical cell identifier (PCI); sending a random access preamble of the random access procedure associated with the control resource set pool index or the PCI to the network entity in response to the random access command message; receiving a random access response of the random access procedure from the network entity in a random access response window; and sending a feedback message to the network entity indicating whether the UE successfully received the random access response according to a feedback configuration, the feedback configuration being at least partially based on the random access response.

[0228] Aspect 2: The method according to aspect 1, wherein the feedback configuration includes at least one of the following items: a feedback timing indicator, the feedback timing indicator indicating a timing offset between the reception of the random access response and the transmission of the feedback message; a PUCCH resource indicator, the PUCCH resource indicator indicating a PUCCH resource used for the transmission of the feedback message; or a transmit power control (TPC) command, the transmit power control (TPC) command indicating a transmit power-related parameter used for the transmission of the feedback message.

[0229] Aspect 3: The method according to any one of aspects 1 to 2, wherein the feedback configuration is based at least in part on a payload of the random access response.

[0230] Aspect 4: The method of aspect 3, wherein sending the feedback message according to the feedback configuration is based at least in part on the random access response being associated with the PCI comprising an inactive PCI.

[0231] Aspect 5: The method according to any one of aspects 3 to 4, wherein sending the feedback message according to the feedback configuration is at least partially based on an indication in the random access command message.

[0232] Aspect 6: The method according to any one of aspects 3 to 5, wherein sending the feedback message according to the feedback configuration is based at least in part on a format of the payload.

[0233] Aspect 7: The method according to any one of aspects 1 to 6, wherein the feedback configuration is based at least in part on one or more reserved bits in a PDCCH order scrambled by a random access radio network temporary identifier (RA-RNTI).

[0234] Aspect 8: The method according to aspect 7, wherein sending the feedback message according to the feedback configuration is based at least in part on an RRC configuration.

[0235] Aspect 9: The method according to any one of aspects 7 to 8, wherein sending the feedback message based at least in part on the one or more reserved bits is based at least in part on an indication in the random access command message.

[0236] Aspect 10: The method according to any one of aspects 1 to 9, wherein sending the feedback message according to the feedback configuration is based at least in part on an indication in the random access command message.

[0237] Aspect 11: The method according to aspect 10, wherein the random access command message indicates that the payload of the random access response indicates the feedback configuration, or one or more reserved bits in the PDCCH order scrambled by a random access radio network temporary identifier (RA-RNTI) indicate the feedback configuration.

[0238] Aspect 12: A method for wireless communication at a UE, the method comprising: receiving a random access command message from a network entity, the random access command message commanding the UE to perform a random access procedure using a random access configuration associated with a control resource set pool index or a physical cell identifier (PCI); sending a random access preamble associated with the control resource set pool index or the PCI for the random access procedure to the network entity in response to the random access command message; receiving a random access response control message for the random access procedure from the network entity in a random access response window, the random access response control message indicating a retransmission configuration identifying the number of transmissions of a random access response data message; and monitoring the number of transmissions of the random access response data message based at least in part on the random access response control message.

[0239] Aspect 13: A method according to Aspect 12, wherein receiving the random access response control message includes: receiving the random access response control message indicating a redundant version sequence mapped to multiple random access response data message opportunities, wherein monitoring the number of transmissions of the random access response data message occurs within the multiple random access response data message opportunities according to the redundant version sequence.

[0240] Aspect 14: A method according to Aspect 13, wherein receiving the random access response control message indicating the redundant version sequence includes: receiving the random access response control message indicating the retransmission configuration identifying the starting redundant version value of the redundant version sequence, wherein the redundant version values ​​of the redundant version sequence are cyclically mapped to the multiple random access response data message opportunities starting from the starting redundant version value in a defined order.

[0241] Aspect 15: A method according to any one of Aspects 12 to 14, wherein receiving the random access response control message includes: receiving the random access response control message including one or more reserved bits indicating the retransmission configuration, and the one or more reserved bits are processed at least in part based on the association of the random access response control message with the PCI including the inactive PCI.

[0242] Aspect 16: A method according to any one of Aspects 12 to 15, wherein receiving the random access response control message includes: receiving the random access response control message including one or more reserved bits indicating the retransmission configuration, and the one or more reserved bits are processed at least in part based on the indication in the random access command message.

[0243] Aspect 17: The method according to any one of aspects 12 to 16, further comprising: receiving the random access response data message based at least in part on monitoring the number of transmissions.

[0244] Aspect 18: A method for wireless communication at a UE, the method comprising: receiving a first random access command message for a random access procedure from a network entity, the first random access command message commanding the UE to send a first random access preamble associated with a first preamble index, a first physical cell identifier (PCI), and a first synchronization signal block (SSB) index; in response to the first random access command message, sending the first random access preamble of the random access procedure to the network entity at a first transmit power level; receiving a second random access command message from the network entity, the second random access command message commanding the UE to send a second random access preamble associated with a second preamble index, a second PCI, and a second SSB index; and sending the second random access preamble to the network entity at a second transmit power level, wherein the second transmit power level is at least partially based on a power adjustment size and a random access attempt counter, the random access attempt counter being at least partially based on whether the second preamble index, the second PCI, and the second SSB index are the same as the first preamble index, the first PCI, and the first SSB index.

[0245] Aspect 19: A method according to Aspect 18, wherein the second transmit power level is further based at least in part on a power ramp counter, and the power ramp counter is based at least in part on whether the second preamble index, the second PCI and the second SSB index are the same as the first preamble index, the first PCI and the first SSB index.

[0246] Aspect 20: The method according to any one of Aspects 18 to 19, further comprising: incrementing the random access attempt counter based at least in part on the second preamble index, the second PCI, and the second SSB index being the same as the first preamble index, the first PCI, and the first SSB index.

[0247] Aspect 21: According to the method described in any one of Aspects 18 to 19, the method further includes: resetting the random access attempt counter at least in part based on the second preamble code index, the second PCI or the second SSB index being different from the first preamble code index, the first PCI or the first SSB index.

[0248] Aspect 22: According to the method described in any one of Aspects 18 to 19, the method further includes: incrementing the random access attempt counter based at least in part on the second preamble index and the second PCI being the same as the first preamble index and the first PCI; and incrementing the power ramp counter based at least in part on the second preamble index, the second PCI and the second SSB index being the same as the first preamble index, the first PCI and the first SSB index.

[0249] Aspect 23: According to any one of Aspects 18 to 19, the method further includes: incrementing the random access attempt counter at least in part based on the second preamble index and the second PCI being the same as the first preamble index and the first PCI; and maintaining the power ramp counter unchanged at least in part based on the second preamble index and the second PCI being the same as the first preamble index and the first PCI and the second SSB index being different from the first SSB index.

[0250] Aspect 24: The method according to any one of Aspects 18 to 23, further comprising: receiving a control element message from the network entity in response to the first random access preamble code being sent, wherein one or more of the random access attempt counter and the power ramp counter are at least partially based on the reception of the control element message.

[0251] Aspect 25: The method according to aspect 24 further comprises: resetting the random access attempt counter based at least in part on the reception of the control element message indicating the timing advance corresponding to the timing advance group identifier associated with the random access procedure.

[0252] Aspect 26: The method according to any one of Aspects 24 to 25, further comprising: resetting the power ramp counter based at least in part on the reception of the control element message indicating the timing advance corresponding to the timing advance group identifier associated with the random access procedure.

[0253] Aspect 27: The method according to any one of aspects 18 to 26, further comprising: resetting the random access attempt counter and the power ramp-up counter based at least in part on the random access attempt counter reaching a maximum count number.

[0254] Aspect 28: An apparatus for wireless communication at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of aspects 1 to 11.

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

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

[0257] Aspect 31: An apparatus for wireless communication 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 12 to 17.

[0258] Aspect 32: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing the method according to any one of aspects 12 to 17.

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

[0260] Aspect 34: An apparatus for wireless communication 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 18 to 27.

[0261] Aspect 35: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing the method according to any one of aspects 18 to 27.

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

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

[0264] 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 throughout much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0265] The information and signals described herein may be represented by any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips referred to throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0266] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using 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 the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

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

[0268] Computer readable medium includes both non-transient computer storage medium and communication medium, and this communication medium includes any medium that promotes computer program to be transferred from one location to another location.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, disk storage or other magnetic storage device or can be used for carrying or storing desired program code components and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.In addition, any connection is appropriately referred to as computer readable medium.For example, if software is to be sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer readable medium. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Magnetic disks can reproduce data magnetically, and optical discs can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

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

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

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

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

[0273] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those 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 accorded 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; as well as instructions stored in the memory and executable by the processor to cause the apparatus to: receiving a random access command message from a network entity, the random access command message commanding the UE to perform a random access procedure using a random access configuration associated with a control resource set pool index or a physical cell identifier (PCI); In response to the random access command message, sending a random access preamble code of the random access procedure associated with the control resource set pool index or the PCI to the network entity; receiving a random access response for the random access procedure from the network entity within a random access response window; as well as A feedback message is sent to the network entity according to a feedback configuration, the feedback configuration being based at least in part on the random access response, indicating whether the UE successfully received the random access response.

2. The apparatus of claim 1 , wherein the feedback configuration comprises at least one of: A feedback timing indicator indicates a timing offset between reception of the random access response and transmission of the feedback message; a physical uplink control channel (PUCCH) resource indicator indicates a PUCCH resource used for transmission of the feedback message; or A transmit power control (TPC) command indicates transmit power related parameters used for transmission of the feedback message.

3. The apparatus of claim 1, wherein the feedback configuration is based at least in part on a payload of the random access response. 4 . The apparatus of claim 3 , wherein sending the feedback message according to the feedback configuration is based at least in part on the random access response being associated with the PCI comprising an inactive PCI.

5. The apparatus of claim 3, wherein sending the feedback message according to the feedback configuration is based at least in part on an indication in the random access command message. The apparatus of claim 3 , wherein sending the feedback message according to the feedback configuration is based at least in part on a format of the payload.

7. The apparatus of claim 1 , wherein the feedback configuration is based at least in part on one or more reserved bits in a physical downlink control channel (PDCCH) order scrambled by a random access radio network temporary identifier (RA-RNTI).

8. The apparatus of claim 7, wherein sending the feedback message according to the feedback configuration is based at least in part on a radio resource control (RRC) configuration.

9. The apparatus of claim 7, wherein sending the feedback message based at least in part on the one or more reserved bits is based at least in part on an indication in the random access command message.

10. The apparatus of claim 1, wherein sending the feedback message according to the feedback configuration is based at least in part on an indication in the random access command message.

11. The apparatus of claim 10 , wherein the random access command message indicates that a payload of the random access response indicates the feedback configuration, or one or more reserved bits in a physical downlink control channel (PDCCH) order scrambled by a random access radio network temporary identifier (RA-RNTI) indicates the feedback configuration.

12. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the apparatus to: receiving a random access command message from a network entity, the random access command message commanding the UE to perform a random access procedure using a random access configuration associated with a control resource set pool index or a physical cell identifier (PCI); In response to the random access command message, sending a random access preamble code of the random access procedure associated with the control resource set pool index or the PCI to the network entity; receiving a random access response control message of the random access procedure from the network entity in a random access response window, the random access response control message indicating a retransmission configuration identifying a number of transmissions of a random access response data message; and The number of transmitted random access response data messages is monitored based at least in part on the random access response control message.

13. The apparatus of claim 12, wherein the instructions for receiving the random access response control message are executable by the processor to cause the apparatus to: The random access response control message is received indicating a redundancy version sequence mapped to a plurality of random access response data message opportunities, wherein monitoring the number of transmissions of the random access response data messages occurs within the plurality of random access response data message opportunities according to the redundancy version sequence.

14. The apparatus of claim 13, wherein the instructions for receiving the random access response control message indicating the redundancy version sequence are executable by the processor to cause the apparatus to: receiving the random access response control message indicating the retransmission configuration identifying a starting redundancy version value of the redundancy version sequence, wherein the redundancy version values ​​of the redundancy version sequence are cyclically mapped to the plurality of random access response data message opportunities starting from the starting redundancy version value in a defined order.

15. The apparatus of claim 12, wherein the instructions for receiving the random access response control message are executable by the processor to cause the apparatus to: The random access response control message is received including one or more reserved bits indicating the retransmission configuration, the one or more reserved bits being processed based at least in part on the random access response control message being associated with the PCI including an inactive PCI.

16. The apparatus of claim 12, wherein the instructions for receiving the random access response control message are executable by the processor to cause the apparatus to: The random access response control message is received including one or more reserved bits indicating the retransmission configuration, the one or more reserved bits being processed based at least in part on the indication in the random access command message.

17. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: receive the random access response data message based at least in part on monitoring the number of transmissions.

18. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the apparatus to: receiving a first random access command message of a random access procedure from a network entity, the first random access command message commanding the UE to send a first random access preamble associated with a first preamble index, a first physical cell identifier (PCI), and a first synchronization signal block (SSB) index; In response to the first random access command message, sending the first random access preamble of the random access procedure to the network entity at a first transmit power level; receiving a second random access command message from the network entity, the second random access command message commanding the UE to send a second random access preamble associated with a second preamble index, a second PCI, and a second SSB index; and The second random access preamble is sent to the network entity at a second transmit power level, wherein the second transmit power level is based at least in part on a power adjustment size and a random access attempt counter, and the random access attempt counter is based at least in part on whether the second preamble index, the second PCI, and the second SSB index are the same as the first preamble index, the first PCI, and the first SSB index.

19. The apparatus of claim 18, wherein the second transmit power level is further based at least in part on a power ramp counter, the power ramp counter being based at least in part on whether the second preamble index, the second PCI, and the second SSB index are the same as the first preamble index, the first PCI, and the first SSB index.

20. The apparatus of claim 18, wherein the instructions are further executable by the processor to cause the apparatus to: increment the random access attempt counter based at least in part on the second preamble index, the second PCI, and the second SSB index being the same as the first preamble index, the first PCI, and the first SSB index.

21. An apparatus according to claim 18, wherein the instructions are further executable by the processor to cause the apparatus to: reset the random access attempt counter based at least in part on the second preamble index, the second PCI, or the second SSB index being different from the first preamble index, the first PCI, or the first SSB index.

22. The apparatus of claim 18, wherein the instructions are further executable by the processor to cause the apparatus to: increment the random access attempt counter based at least in part on the second preamble index and the second PCI being the same as the first preamble index and the first PCI; and A power ramp-up counter is incremented based at least in part on the second preamble index, the second PCI, and the second SSB index being the same as the first preamble index, the first PCI, and the first SSB index.

23. The apparatus of claim 18, wherein the instructions are further executable by the processor to cause the apparatus to: increment the random access attempt counter based at least in part on the second preamble index and the second PCI being the same as the first preamble index and the first PCI; and A power ramp-up counter is maintained based at least in part on the second preamble index and the second PCI being the same as the first preamble index and the first PCI and the second SSB index being different than the first SSB index.

24. The apparatus of claim 18, wherein the instructions are further executable by the processor to cause the apparatus to: receive a control element message from the network entity in response to a first random access preamble transmission, wherein one or more of the random access attempt counter and the power ramp counter are based at least in part on the reception of the control element message.

25. The apparatus of claim 24, wherein the instructions are further executable by the processor to cause the apparatus to: reset the random access attempt counter based at least in part on the receipt of the control element message indicating a timing advance corresponding to a timing advance group identifier associated with the random access procedure.

26. The apparatus of claim 24, wherein the instructions are further executable by the processor to cause the apparatus to: reset the power ramp counter based at least in part on the receipt of the control element message indicating a timing advance corresponding to a timing advance group identifier associated with the random access procedure.

27. The apparatus of claim 18, wherein the instructions are further executable by the processor to cause the apparatus to: reset the random access attempt counter and a power ramp-up counter based at least in part on the random access attempt counter reaching a maximum count number.

28. A method for wireless communication at a user equipment (UE), the method comprising: receiving a random access command message from a network entity, the random access command message commanding the UE to perform a random access procedure using a random access configuration associated with a control resource set pool index or a physical cell identifier (PCI); In response to the random access command message, sending a random access preamble code of the random access procedure associated with the control resource set pool index or the PCI to the network entity; receiving a random access response for the random access procedure from the network entity within a random access response window; as well as A feedback message is sent to the network entity according to a feedback configuration, the feedback configuration being based at least in part on the random access response, indicating whether the UE successfully received the random access response.

29. The method of claim 28, wherein the feedback configuration comprises at least one of: a feedback timing indicator indicating a timing offset between reception of the random access response and transmission of the feedback message; a physical uplink control channel (PUCCH) resource indicator, wherein the physical uplink control channel (PUCCH) resource indicator indicates a PUCCH resource used for sending the feedback message; or A transmit power control (TPC) command indicates a transmit power related parameter used for transmitting the feedback message.

30. The method of claim 28, wherein the feedback configuration is based at least in part on a payload of the random access response or at least in part on one or more reserved bits in a physical downlink control channel (PDCCH) order scrambled by a random access radio network temporary identifier (RA-RNTI).

Images