WO2025208615A1

WO2025208615A1 - Physical downlink control channel (pdcch) -ordered physical random access channel (prach) for an uplink-only transmission and reception point (trp)

Info

Publication number: WO2025208615A1
Application number: PCT/CN2024/086236
Authority: WO
Inventors: Shaozhen GUO; Mostafa KHOSHNEVISAN; Yan Zhou; Yi Huang; Xiaoxia Zhang
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2024-04-05
Filing date: 2024-04-05
Publication date: 2025-10-09
Anticipated expiration: 2026-10-05
Also published as: WO2025209014A1

Abstract

Methods, systems, and devices for wireless communication are described. In some aspects, a user equipment (UE) may use an indicated transmission configuration indication (TCI) state for a random access message, such as a random access preamble that the UE may transmit via a physical random access channel (PRACH). In scenarios in which a single TCI state is indicated to the UE, the UE may use the indicated TCI state for the PRACH transmission in accordance with a rule that defines use of an indicated TCI state for a physical downlink control channel (PDCCH) -ordered PRACH transmission. In scenarios in which two TCI states are indicated to the UE, the UE may select one of the two indicated TCI states for the PRACH transmission in accordance with a fixed rule and/or a signaled indication from the network entity.

Description

PHYSICAL DOWNLINK CONTROL CHANNEL (PDCCH) -ORDERED PHYSICAL RANDOM ACCESS CHANNEL (PRACH) FOR AN UPLINK-ONLY TRANSMISSION AND RECEPTION POINT (TRP)

TECHNICAL FIELD

The following relates to wireless communication, including physical downlink control channel (PDCCH) -ordered physical random access channel (PRACH) for an uplink-only transmission and reception point (TRP) .

DESCRIPTION OF THE RELATED TECHNOLOGY

Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (such as time, frequency, and power) . Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (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 technologies such as code division multiple access (CDMA) , time division multiple access (TDMA) , frequency division multiple access (FDMA) , orthogonal FDMA (OFDMA) , or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM) . A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE) .

A UE may support one or more configurations associated with directional communication to a network entity. Such configurations associated with directional communication may relate to one or more transmission configuration indication (TCI) states. For example, a first TCI state may correspond to a first configuration associated with directional communication and a second TCI state may correspond to a second configuration associated with directional communication. A UE may receive an indication to use one or two TCI states from a network entity, such as via downlink control information (DCI) . Further, a configuration associated with directional communication may be understood as a configuration for one or more antennas/antenna arrays according to which a wireless communication device may form a transmit beam and/or a receive beam.

SUMMARY

The systems, methods, and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

A method for wireless communication by a user equipment (UE) is described. The method may include receiving a first downlink control information (DCI) message including an indication of one or more transmission configuration indication (TCI) states, receiving a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion, and transmitting the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states.

A UE for wireless communication is described. The UE may include a processing system that includes processor circuitry and memory circuitry that stores code. The processing system may be configured to cause the UE to receive a first DCI message including an indication of one or more transmission configuration indication (TCI) states, receive a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion, and transmit the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states.

Another UE for wireless communication is described. The UE may include means for receiving a first DCI message including an indication of one or more transmission configuration indication (TCI) states, means for receiving a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion, and means for transmitting the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states.

A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to receive a first DCI message including an indication of one or more transmission configuration indication (TCI) states, receive a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion, and transmit the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, receiving the first DCI message may include operations, features, means, or instructions for receiving an indication of a single TCI state, where the one or more TCI states consists of the single TCI state, and where the first TCI state may be the single TCI state.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the UE transmits the random access message in accordance with the single TCI state in accordance with a rule defining that the UE may be to use an indicated TCI state for the random access message indicated by the second DCI message.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, receiving the first DCI message may include operations, features, means, or instructions for receiving an indication of a set of multiple TCI states via the first DCI message, where the one or more TCI states include the set of multiple TCI states, and where the set of multiple TCI states includes the first TCI state.

Some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for selecting the first TCI state from the set of multiple TCI states in accordance with a rule defining a TCI state selection criterion associated with the random access message indicated by the second DCI message, where transmitting the random access message in accordance with the first TCI state may be in association with selecting the first TCI state.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the rule defines that an initially indicated TCI state, of the set of multiple TCI states, may be to be used for the random access message and the first TCI state may be the initially indicated TCI state of the set of multiple TCI states.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the rule defines that a TCI state associated with a lowest TCI state identifier, of the set of multiple TCI states, may be to be used for the random access message and the first TCI state may be associated with the lowest TCI state identifier of the set of multiple TCI states.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the rule defines that an initially indicated TCI state, of a subset of the set of multiple TCI states associated with a pathloss offset, may be to be used for the random access message and the first TCI state may be the initially indicated TCI state of the subset of the set of multiple TCI states.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the rule defines that a TCI state associated with a lowest TCI state identifier, of a subset of the set of multiple TCI states associated with a pathloss offset, may be to be used for the random access message and the first TCI state may be associated with the lowest TCI state identifier of the subset of the set of multiple TCI states.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the rule defines the TCI state selection criterion for physical downlink control channel (PDCCH) -ordered random access message transmissions and the random access message indicated by the second DCI message may be a PDCCH-ordered random access message transmission.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, receiving the second DCI message may include operations, features, means, or instructions for receiving information indicative of the first TCI state via the second DCI message, where transmitting the random access message in accordance with the first TCI state may be in association with receiving the information indicative of the first TCI state via the second DCI message.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, a field of the second DCI message includes the information indicative of the first TCI state.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the field includes one or more bits, a first codepoint associated with the one or more bits indicates that the UE may be to transmit the random access message in accordance with the first TCI state and a second codepoint associated with the one or more bits indicates that the UE may be to transmit the random access message in accordance with a second TCI state of the set of multiple TCI states, and the one or more bits indicate the first codepoint.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the field may be a TCI selection field of the second DCI message.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the field may be a PRACH association indicator field of the second DCI message.

Some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving control signaling that indicates that the UE may be to transmit the random access message in accordance with the first TCI state, where transmitting the random access message in accordance with the first TCI state may be in association with receiving the control signaling.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the control signaling includes one or more radio resource control (RRC) information elements that indicate that the UE may be to transmit the random access message in accordance with the first TCI state.

Some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining whether to transmit the random access message in accordance with the first TCI state in accordance with a presence of at least one indicated TCI state or an absence of at least one indicated TCI state at a transmission time associated with the random access message, where transmitting the random access message in accordance with the first TCI state may be in association with determining whether to transmit the random access message in accordance with the first TCI state.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the presence of at least one indicated TCI state at the transmission time associated with the random access message indicates that the UE may be to transmit the random access message in accordance with the first TCI state and the absence of at least one indicated TCI state at the transmission time associated with the random access message indicates that the UE may be to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, receiving the second DCI message may include operations, features, means, or instructions for receiving information indicative of whether the UE may be to transmit the random access message in accordance with the first TCI state, where transmitting the random access message in accordance with the first TCI state may be in association with receiving the information.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, a field of the second DCI message includes the information indicative of whether the UE may be to transmit the random access message in accordance with the first TCI state.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the field includes one or more bits, a first codepoint associated with the one or more bits indicates that random access message transmissions in accordance with an indicated TCI state may be enabled and a second codepoint associated with the one or more bits indicates that random access message transmissions in accordance with the indicated TCI state may be disabled, and the one or more bits indicate the first codepoint.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the field may be a dedicated field of the second DCI message that may be associated with enabling or disabling use of the indicated TCI state for random access message transmissions.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the field includes one or more bits, a first codepoint associated with the one or more bits indicates that the UE may be to transmit the random access message in accordance with the first TCI state and a second codepoint associated with the one or more bits indicates that the UE may be to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion, and the one or more bits indicate the first codepoint.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the field includes a set of multiple bits, a first codepoint associated with the set of multiple bits indicates that the UE may be to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion, a second codepoint associated with the set of multiple bits indicates that the UE may be to transmit the random access message in accordance with the first TCI state, and a third codepoint associated with the set of multiple bits indicates that the UE may be to transmit the random access message in accordance with a second TCI state of the set of multiple TCI states, and the set of multiple bits indicates the second codepoint.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, transmitting the random access message may include operations, features, means, or instructions for transmitting the random access message using a transmission power that may be associated with the pathloss offset associated with the first TCI state.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, transmitting the random access message may include operations, features, means, or instructions for transmitting the random access message using a transmission beam associated with a source reference signal that may be associated with the first TCI state.

Some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting information indicative of a capability of the UE to perform random access message transmissions in accordance with an indicated TCI state, where transmitting the random access message in accordance with the first TCI state may be in association with transmitting the information indicative of the capability of the UE.

A method for wireless communication by a network entity is described. The method may include outputting, to a UE, a first DCI message including an indication of one or more transmission configuration indication (TCI) states, outputting, to the UE, a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion, and obtaining the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states.

A network entity for wireless communication is described. The network entity may include a processing system that includes processor circuitry and memory circuitry that stores code. The processing system may be configured to cause the network entity to output, to a UE, a first DCI message including an indication of one or more transmission configuration indication (TCI) states, output, to the UE, a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion, and obtain the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states.

Another network entity for wireless communication is described. The network entity may include means for outputting, to a UE, a first DCI message including an indication of one or more transmission configuration indication (TCI) states, means for outputting, to the UE, a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion, and means for obtaining the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states.

A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to output, to a UE, a first DCI message including an indication of one or more transmission configuration indication (TCI) states, output, to the UE, a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion, and obtain the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, outputting the first DCI message may include operations, features, means, or instructions for outputting an indication of a single TCI state, where the one or more TCI states consists of the single TCI state, and where the first TCI state may be the single TCI state.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the network entity obtains the random access message in accordance with the single TCI state in accordance with a rule defining that the UE may be to use an indicated TCI state for the random access message indicated by the second DCI message.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, outputting the first DCI message may include operations, features, means, or instructions for outputting an indication of a set of multiple TCI states via the first DCI message, where the one or more TCI states include the set of multiple TCI states, and where the set of multiple TCI states includes the first TCI state.

Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for generating the first DCI message in accordance with a rule defining a TCI state selection criterion associated with the random access message indicated by the second DCI message, where transmitting the first DCI message may be in association with generating the first DCI message.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the rule defines that an initially indicated TCI state, of the set of multiple TCI states, may be to be used for the random access message and the first TCI state may be the initially indicated TCI state of the set of multiple TCI states.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the rule defines that a TCI state associated with a lowest TCI state identifier, of the set of multiple TCI states, may be to be used for the random access message and the first TCI state may be associated with the lowest TCI state identifier of the set of multiple TCI states.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the rule defines that an initially indicated TCI state, of a subset of the set of multiple TCI states associated with a pathloss offset, may be to be used for the random access message and the first TCI state may be the initially indicated TCI state of the subset of the set of multiple TCI states.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the rule defines that a TCI state associated with a lowest TCI state identifier, of a subset of the set of multiple TCI states associated with a pathloss offset, may be to be used for the random access message and the first TCI state may be associated with the lowest TCI state identifier of the subset of the set of multiple TCI states.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the rule defines the TCI state selection criterion for PDCCH-ordered random access message transmissions and the random access message indicated by the second DCI message may be a PDCCH-ordered random access message transmission.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, outputting the second DCI message may include operations, features, means, or instructions for outputting information indicative of the first TCI state via the second DCI message, where obtaining the random access message in accordance with the first TCI state may be in association with outputting the information indicative of the first TCI state via the second DCI message.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, a field of the second DCI message includes the information indicative of the first TCI state.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the field includes one or more bits, a first codepoint associated with the one or more bits indicates that the UE may be to transmit the random access message in accordance with the first TCI state and a second codepoint associated with the one or more bits indicates that the UE may be to transmit the random access message in accordance with a second TCI state of the set of multiple TCI states, and the one or more bits indicate the first codepoint.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the field may be a TCI selection field of the second DCI message.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the field may be a PRACH association indicator field of the second DCI message.

Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting control signaling that indicates that the UE may be to transmit the random access message in accordance with the first TCI state, where obtaining the random access message in accordance with the first TCI state may be in association with outputting the control signaling.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the control signaling includes one or more RRC information elements that indicate that the UE may be to transmit the random access message in accordance with the first TCI state.

Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining whether to obtain the random access message in accordance with the first TCI state in accordance with a presence of at least one indicated TCI state or an absence of at least one indicated TCI state at a transmission time associated with the random access message, where obtaining the random access message in accordance with the first TCI state may be in association with determining whether to obtain the random access message in accordance with the first TCI state.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the presence of at least one indicated TCI state at the transmission time associated with the random access message indicates that the UE may be to transmit the random access message in accordance with the first TCI state and the absence of at least one indicated TCI state at the transmission time associated with the random access message indicates that the UE may be to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, outputting the second DCI message may include operations, features, means, or instructions for outputting information indicative of whether the UE may be to transmit the random access message in accordance with the first TCI state, where obtaining the random access message in accordance with the first TCI state may be in association with outputting the information.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, a field of the second DCI message includes the information indicative of whether the UE may be to transmit the random access message in accordance with the first TCI state.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the field includes one or more bits, a first codepoint associated with the one or more bits indicates that random access message transmissions in accordance with an indicated TCI state may be enabled and a second codepoint associated with the one or more bits indicates that random access message transmissions in accordance with the indicated TCI state may be disabled, and the one or more bits indicate the first codepoint.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the field may be a dedicated field of the second DCI message that may be associated with enabling or disabling use of the indicated TCI state for random access message transmissions.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the field includes one or more bits, a first codepoint associated with the one or more bits indicates that the UE may be to transmit the random access message in accordance with the first TCI state and a second codepoint associated with the one or more bits indicates that the UE may be to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion, and the one or more bits indicate the first codepoint.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the field includes a set of multiple bits, a first codepoint associated with the set of multiple bits indicates that the UE may be to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion, a second codepoint associated with the set of multiple bits indicates that the UE may be to transmit the random access message in accordance with the first TCI state, and a third codepoint associated with the set of multiple bits indicates that the UE may be to transmit the random access message in accordance with a second TCI state of the set of multiple TCI states, and the set of multiple bits indicates the second codepoint.

Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for obtaining information indicative of a capability of the UE to perform random access message transmissions in accordance with an indicated TCI state, where obtaining the random access message in accordance with the first TCI state may be in association with obtaining the information indicative of the capability of the UE.

Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings and the claims. Note that the relative dimensions of the following figures may not be drawn to scale.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 shows an example of a wireless communications system that supports physical downlink control channel (PDCCH) -ordered physical random access channel (PRACH) for an uplink-only transmission and reception point (TRP) .

Figure 2 shows an example of a network architecture that supports PDCCH-ordered PRACH for an uplink-only TRP.

Figure 3 shows an example of an uplink dense deployment that supports PDCCH-ordered PRACH for an uplink-only TRP.

Figures 4–9 show examples of communication timelines that support PDCCH-ordered PRACH for an uplink-only TRP.

Figure 10 shows a block diagram of a communications manager that supports PDCCH-ordered PRACH for an uplink-only TRP.

Figure 11 shows a diagram of a system including a device that supports PDCCH-ordered PRACH for an uplink-only TRP.

Figure 12 shows a block diagram of a communications manager that supports PDCCH-ordered PRACH for an uplink-only TRP.

Figure 13 shows a diagram of a system including a device that supports PDCCH-ordered PRACH for an uplink-only TRP.

Figures 14 and 15 show flowcharts illustrating methods that support PDCCH-ordered PRACH for an uplink-only TRP.

DETAILED DESCRIPTION

The following description is directed to some particular examples for the purposes of describing innovative aspects of this disclosure. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways. Some or all of the described examples may be implemented in any device, system or network that is capable of transmitting and receiving radio frequency (RF) signals according to one or more of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards, the IEEE 802.15 standards, the standards as defined by the Bluetooth Special Interest Group (SIG) , or the Long Term Evolution (LTE) , 3G, 4G or 5G (New Radio (NR) ) standards promulgated by the 3rd Generation Partnership Project (3GPP) , among others. The described examples can be implemented in any device, system or network that is capable of transmitting and receiving RF signals according to one or more of the following technologies or techniques: code division multiple access (CDMA) , time division multiple access (TDMA) , orthogonal frequency division multiplexing (OFDM) , frequency division multiple access (FDMA) , orthogonal FDMA (OFDMA) , single-carrier FDMA (SC-FDMA) , spatial division multiple access (SDMA) , rate-splitting multiple access (RSMA) , multi-user shared access (MUSA) , single-user (SU) multiple-input multiple-output (MIMO) and multi-user (MU) -MIMO (MU-MIMO) . The described examples also can be implemented using other wireless communication protocols or RF signals suitable for use in one or more of a wireless personal area network (WPAN) , a wireless local area network (WLAN) , a wireless wide area network (WWAN) , a wireless metropolitan area network (WMAN) , or an internet of things (IOT) network.

Various aspects relate generally to physical downlink control channel (PDCCH) -ordered physical random access channel (PRACH) transmissions. Some aspects more specifically relate to PDCCH-ordered PRACH transmissions to an uplink- only transmission and reception point (TRP) , which may be understood as an uplink-only reception point. An uplink-only TRP may receive uplink signaling from a user equipment (UE) and relay/transmit/forward (via a wireless or wired connection) the uplink signaling to a central network entity, which may deploy multiple uplink-only TRP to increase an uplink coverage. An uplink-only TRP may lack a capability to transmit downlink signaling. A UE may determine a configuration for directional communication toward an uplink-only TRP in accordance with an uplink beam management procedure, such as a sounding reference signal (SRS) -based uplink beam management procedure. Such a configuration for directional communication may be associated with a transmission configuration indication (TCI) state. A network entity may indicate one or two TCI states for a UE to use for configuration with the network entity (including via one or multiple TRPs, including, for example, an uplink-only TRP) . A network entity may indicate one or two TCI states via a field of a downlink control information (DCI) message, such as a DCI format 1_1/1_2.

In accordance with some example implementations, a UE may use an indicated TCI state for a random access message, such as a random access preamble that the UE may transmit via a physical random access channel (PRACH) . In some aspects, the UE may perform a PRACH transmission in accordance with an indicated TCI state in accordance with a mechanism associated with facilitating a determination of a timing advance (TA) value for communication from the UE to the uplink-only TRP. In scenarios in which a single TCI state is indicated to the UE, the UE may use the indicated TCI state for the PRACH transmission in accordance with a rule that defines use of an indicated TCI state for a PDCCH-ordered PRACH transmission. In scenarios in which two TCI states are indicated to the UE, the UE may select one of the two indicated TCI states for the PRACH transmission in accordance with a fixed rule and/or a signaled indication from the network entity (such as an indication in the DCI message ordering/triggering the PRACH transmission) . Additionally, or alternatively, the UE and the network entity may employ one or more signaling-or configuration-based mechanisms according to which the UE may determine whether to use an indicated TCI state for a PRACH transmission or to perform a PRACH transmission in accordance with a baseline operation (with such a baseline operation being associated with a use, by the UE, of a synchronization signal block (SSB) or a channel state information (CSI) reference signal (CSI-RS) associated with an indicated PRACH occasion to determine a transmit beam for the PRACH transmission) .

Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by transmitting a random access message in accordance with an indicated TCI state, a UE may suitably direct the random access message toward a specific TRP, such as an uplink-only TRP, which may enable the UE to efficiently obtain or facilitate a determination of one or more communication parameters that the UE may use for subsequent communication. For example, by suitably directing the random access message toward an uplink-only TRP, the UE may facilitate a determination of a TA between the UE and the uplink-only TRP and enable an absolute (as opposed to a relative) indication of the TA from a network entity. By enabling such an absolute indication, from the network entity, of the TA between the UE and the uplink-only TRP by way of the transmission of the random access message in accordance with an indicated TCI state, the UE and the network entity may experience relatively lower signaling overhead by avoiding communication of potentially multiple relative TA adjustments. For example, multiple relative TA adjustments (which may be provided in situations involving an uplink-only TRP, as the TA for the uplink-only TRP may be substantially different from a baseline TA between the UE and the central network entity) may consume a relatively larger amount of communication resources and/or incur relative more latency in TA determination/indication as compared to an absolute indication enabled by an indicated TCI state-based random access transmission. In accordance with such relatively lower signaling overhead and lower latency, an indicated TCI state-based random access transmission may further support higher data rates, greater spectral efficiency, greater communication reliability, and greater system capacity, among other benefits. Further, in accordance with providing such benefits, an indicated TCI state-based random access transmission may further encourage deployment of uplink-only reception points in more systems, which may provide better (uplink) coverage.

Figure 1 shows an example of a wireless communications system 100 that supports PDCCH-ordered PRACH for an uplink-only TRP. The wireless communications system 100 may include one or more devices, such as one or more network devices (such as network entities 105) , one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

The network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 115 may wirelessly communicate via communication link (s) 125 (such as a radio frequency (RF) access link) . For example, a network entity 105 may support a coverage area 110 (such as a geographic coverage area) over which the UEs 115 and the network entity 105 may establish the communication link (s) 125. The coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .

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

A node of the wireless communications system 100, which may be referred to as a network node, or a wireless node, may be a network entity 105 (such as any network entity described herein) , a UE 115 (such as 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, a node may be a UE 115. As another example, a node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.

In some examples, network entities 105 may communicate with a core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via backhaul communication link (s) 120 (such as in accordance with an S1, N2, N3, or other interface protocol) . In some examples, network entities 105 may communicate with one another via backhaul communication link (s) 120 (such as in accordance with an X2, Xn, or other interface protocol) either directly (such as directly between network entities 105) or indirectly (such as via the core network 130) . In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (such as in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (such as in accordance with a fronthaul interface protocol) , or any combination thereof. The backhaul communication link (s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (such as an electrical link, an optical fiber link) or one or more wireless links (such as a radio link, a wireless optical link) , among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.

One or more of the network entities 105 or network equipment described herein may include or may be referred to as a base station 140 (such as a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) . In some examples, a network entity 105 (such as a base station 140) may be implemented in an aggregated (such as monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within one network entity (such as a network entity 105 or a single RAN node, such as a base station 140) .

In some examples, a network entity 105 may be implemented in a disaggregated architecture (such as a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (such as network entities 105) , such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (such as a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (such as a cloud RAN (C-RAN) ) . For example, a network entity 105 may include one or more of a central unit (CU) , such as a CU 160, a distributed unit (DU) , such as a DU 165, a radio unit (RU) , such as an RU 170, a RAN Intelligent Controller (RIC) , such as an RIC 175 (such as a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, such as an SMO system 180, or any combination thereof. An RU 170 also may be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) . One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (such as separate physical locations) . In some examples, one or more of the network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (such as a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .

The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (such as network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (such as layer 3 (L3) , layer 2 (L2) ) functionality and signaling (such as Radio Resource Control (RRC) , service data adaptation protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) . The CU 160 (such as one or more CUs) may be connected to a DU 165 (such as one or more DUs) or an RU 170 (such as one or more RUs) , or some combination thereof, and the DUs 165, RUs 170, or both may host lower protocol layers, such as layer 1 (L1) (such as physical (PHY) layer) or L2 (such as radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (such as via one or multiple different RUs, such as an RU 170) . In some examples, a functional split between a CU 160 and a DU 165 or between a DU 165 and an RU 170 may be within a protocol layer (such as some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170) . A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to a DU 165 via a midhaul communication link 162 (such as F1, F1-c, F1-u) , and a DU 165 may be connected to an RU 170 via a fronthaul communication link 168 (such as open fronthaul (FH) interface) . In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (such as a channel) between layers of a protocol stack supported by respective network entities (such as one or more of the network entities 105) that are in communication via such communication links.

In some wireless communications systems (such as the wireless communications system 100) , infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (such as to a core network 130) . In some examples, in an IAB network, one or more of the network entities 105 (such as network entities 105 or IAB node (s) 104) may be partially controlled by each other. The IAB node (s) 104 may be referred to as a donor entity or an IAB donor. A DU 165 or an RU 170 may be partially controlled by a CU 160 associated with a network entity 105 or base station 140 (such as a donor network entity or a donor base station) . The one or more donor entities (such as IAB donors) may be in communication with one or more additional devices (such as IAB node (s) 104) via supported access and backhaul links (such as backhaul communication link (s) 120) . IAB node (s) 104 may include an IAB mobile termination (IAB-MT) controlled (such as scheduled) by one or more DUs (such as DUs 165) of a coupled IAB donor. An IAB-MT may be equipped with an independent set of antennas for relay of communications with UEs 115 or may share the same antennas (such as of an RU 170) of IAB node (s) 104 used for access via the DU 165 of the IAB node (s) 104 (such as referred to as virtual IAB-MT (vIAB-MT) ) . In some examples, the IAB node (s) 104 may include one or more DUs (such as DUs 165) that support communication links with additional entities (such as IAB node (s) 104, UEs 115) within the relay chain or configuration of the access network (such as downstream) . In such cases, one or more components of the disaggregated RAN architecture (such as the IAB node (s) 104 or components of the IAB node (s) 104) may be configured to operate according to the techniques described herein.

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

IAB node (s) 104 may refer to RAN nodes that provide IAB functionality (such as access for UEs 115, wireless self-backhauling capabilities) . A DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node (s) 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with IAB node (s) 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (such as an IAB donor may relay transmissions for UEs–other IAB node (s) 104) . Additionally, or alternatively, IAB node (s) 104 also may be referred to as parent nodes or child nodes to other IAB node (s) 104, depending on the relay chain or configuration of the AN. The IAB-MT entity of IAB node (s) 104 may provide a Uu interface for a child IAB node (such as the IAB node (s) 104) to receive signaling from a parent IAB node (such as the IAB node (s) 104) , and a DU interface (such as a DU 165) may provide a Uu interface for a parent IAB node to signal to a child IAB node or UE 115.

For example, IAB node (s) 104 may be referred to as parent nodes that support communications for child IAB nodes, or may be referred to as child IAB nodes associated with IAB donors, or both. An IAB donor may include a CU 160 with a wired or wireless connection (such as backhaul communication link (s) 120) to the core network 130 and may act as a parent node to IAB node (s) 104. For example, the DU 165 of an IAB donor may relay transmissions to UEs 115–IAB node (s) 104, or may directly signal transmissions to a UE 115, or both. The CU 160 of the IAB donor may signal communication link establishment via an F1 interface to IAB node (s) 104, and the IAB node (s) 104 may schedule transmissions (such as transmissions to the UEs 115 relayed from the IAB donor) –one or more DUs (such as DUs 165) . That is, data may be relayed to and from IAB node (s) 104 via signaling via an NR Uu interface to MT of IAB node (s) 104 (such as other IAB node (s) ) . Communications with IAB node (s) 104 may be scheduled by a DU 165 of the IAB donor or of IAB node (s) 104.

In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support various operations. For example, some operations described as being performed by a UE 115 or a network entity 105 (such as a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (such as components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180) .

A 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, in which the “device” also may be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 also may 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, a UE 115 may include or 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 communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, vehicles, or meters, among other examples.

The UEs 115 described herein may be able to communicate with various types of devices, such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in Figure 1.

The UEs 115 and the network entities 105 may wirelessly communicate with one another via the communication link (s) 125 (such as one or more access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link (s) 125. For example, a carrier used for the communication link (s) 125 may include a portion of an RF spectrum band (such as a bandwidth part (BWP) ) that is operated according to one or more PHY layer channels for a given RAT (such as LTE, LTE-A, LTE-A Pro, NR) . Each PHY layer channel may carry acquisition signaling (such as synchronization signals, system information) , control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (such as entity, sub-entity) of a network entity 105. For example, the terms “transmitting, ” “receiving, ” or “communicating, ” when referring to a network entity 105, may refer to any portion of a network entity 105 (such as a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (such as directly or via one or more other network entities, such as one or more of the network entities 105) .

In some examples, such as in a carrier aggregation configuration, a carrier may have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (such as an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN) ) and may be identified according to a channel raster for discovery by the UEs 115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (such as of the same or a different RAT) .

The communication link (s) 125 of the wireless communications system 100 may include downlink transmissions (such as forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (such as return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions. Carriers may carry downlink or uplink communications (such as in an FDD mode) or may be configured to carry downlink and uplink communications (such as in a TDD mode) .

A carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular RAT (such as 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) . Devices of the wireless communications system 100 (such as the network entities 105, the UEs 115, or both) may have hardware configurations that support communications using a particular carrier bandwidth or may be configurable to support communications using one of a set of carrier bandwidths. In some examples, the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured for operating using portions (such as a sub-band, a BWP) or all of a carrier bandwidth.

Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (such as using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) . In a system employing MCM techniques, a resource element may refer to resources of one symbol period (such as a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (such as the order of the modulation scheme, the coding rate of the modulation scheme, or both) , such that a relatively higher quantity of resource elements (such as in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (such as a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.

One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.

The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of T_x=1/ (Δf_max·N_f) seconds, for which Δf_max may represent a supported subcarrier spacing, and N_f may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (such as 10 milliseconds (ms) ) . Each radio frame may be identified by a system frame number (SFN) (such as ranging from 0 to 1023) .

Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (such as in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (such as depending on the length of the cyclic prefix prepended to each symbol period) . In some wireless communications systems, such as the wireless communications system 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (such as N_f) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (such as in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) . In some examples, the TTI duration (such as a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (such as in bursts of shortened TTIs (sTTIs) ) .

Physical channels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (such as a control resource set (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 the carrier. One or more control regions (such as CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (such as control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to UEs 115 (such as one or more UEs) or may include UE-specific search space sets for sending control information to a UE 115 (such as a specific UE) .

A network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a network entity 105 (such as using a carrier) and may be associated with an identifier for distinguishing neighboring cells (such as a physical cell identifier (PCID) , a virtual cell identifier (VCID) ) . In some examples, a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (such as a sector) over which the logical communication entity operates. Such cells may range from smaller areas (such as a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.

A macro cell generally covers a relatively large geographic area (such as several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a network entity 105 operating with lower power (such as a base station 140 operating with lower power) relative to a macro cell, and a small cell may operate using the same or different (such as licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (such as the UEs 115 in a closed subscriber group (CSG) , the UEs 115 associated with users in a home or office) . A network entity 105 may support one or more cells and also may support communications via the one or more cells using one or multiple component carriers.

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

In some examples, a network entity 105 (such as a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110. In some examples, coverage areas 110 (such as different coverage areas) associated with different technologies may overlap, but the coverage areas 110 (such as different coverage areas) may be supported by the same network entity (such as a network entity 105) . In some other examples, overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (such as the network entities 105) . The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 support communications for coverage areas 110 (such as different coverage areas) using the same or different RATs.

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

The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) . The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications 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.

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

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 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (such as a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (such as a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (such as base stations 140) associated with the core network 130. User IP packets may be transferred–the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.

The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) . Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (such as less than one hundred kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) RAT, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (such as LAA) . Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

A network entity 105 (such as a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a 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, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.

The network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (such as the same codeword) or different data streams (such as different codewords) . Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) , for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO) , for which multiple spatial layers are transmitted to multiple devices.

Beamforming, which also may be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (such as a network entity 105, a UE 115) to shape or steer an antenna beam (such as a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (such as with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .

A network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations. For example, a network entity 105 (such as a base station 140, an RU 170) may use multiple antennas or antenna arrays (such as antenna panels) to conduct beamforming operations for directional communications with a UE 115. Some signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a network entity 105 multiple times along different directions. For example, the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission. Transmissions along different beam directions may be used to identify (such as by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network entity 105.

Some signals, such as data signals associated with a particular receiving device, may be transmitted by a transmitting device (such as a network entity 105 or a UE 115) along a single beam direction (such as a direction associated with the receiving device, such as another network entity 105 or UE 115) . In some examples, the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions. For example, a UE 115 may receive one or more of the signals transmitted by the network entity 105 along different directions and may report to the network entity 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.

In some examples, transmissions by a device (such as by a network entity 105 or a UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (such as from a network entity 105 to a UE 115) . The UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands. The network entity 105 may transmit a reference signal (such as a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS) ) , which may be precoded or unprecoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (such as a multi-panel type codebook, a linear combination type codebook, a port selection type codebook) . Although these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (such as a base station 140, an RU 170) , a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (such as for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (such as for transmitting data to a receiving device) .

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

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

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

In some deployment scenarios (including uplink dense deployment scenarios) , to improve one or both of the uplink coverage or the uplink capacity of the wireless communication systems, one or more network entities 105 may deploy, support, operate, or otherwise be associated with asymmetric downlink and uplink nodes. Such a configuration of the wireless communications system 100 with asymmetric downlink and uplink nodes may include or refer to a use (such as deployment) of one or more uplink reception points (which may be referred to or understood as “UL Rx points, ” “UL-only nodes, ” or “UL-only TRPs” ) located throughout a geographic area to provide more points to which a UE 115 may transmit uplink signaling (such as in addition to a base station 140, such as a gNB, that is capable of both downlink and uplink communication) . An uplink reception point may be incapable of transmitting downlink signaling, such that a UE 115 may receive downlink signaling from a downlink transmission point (which may be a base station or collocated with the base station, and which may be referred to as a “DL Tx point” ) and may transmit signaling to an uplink reception point that is non-collocated with (such as positionally or geographically separated from) the downlink transmission point. In accordance with such non-collocation, a downlink pathloss between the UE 115 and the downlink transmission point and an uplink pathloss between the UE 115 and the uplink reception point may differ substantially.

Any one or more of the set of components, functionalities, or nodes of a network entity 105 may serve or function as a downlink transmission point or as an uplink reception point associated with the network entity 105. Additionally, or alternatively, a network entity 105 may include additional components, functionalities, or nodes that serve as a downlink transmission point or as an uplink reception point associated with the network entity 105. In some aspects, a network entity 105 may use (such as leverage or operate) one or multiple uplink reception points, in addition or as an alternative to uplink capabilities at the network entity 105 itself, to increase the uplink coverage provided by the network entity 105. A network entity 105 may refer to a base station, a gNB, or another entity or node that controls or is otherwise associated with (such as connected with via a backhaul link) one or more uplink reception points. Thus, a network entity 105 may be understood as including one or more uplink reception points and/or as being communicatively coupled with one or more uplink reception points (via, for example, one or more backhaul links, which may be wired or wireless) . Accordingly, a network entity 105 may receive or otherwise obtain uplink signaling from one or more UEs 115 via one or more uplink reception points.

A network entity 105 also may include or otherwise control the downlink transmission point via which the network entity 105 transmits downlink signals or channels. Such a downlink transmission point may be associated with (such as may be) a macro node associated with the network entity 105, a central node associated with the network entity 105, a serving cell associated with the network entity 105, or a serving base station 140 associated with the network entity 105. A network entity 105 may support both uplink and downlink communication via its collocated (or approximately collocated) antenna panels and may use the one or more uplink reception points to supplement the uplink coverage or capacity provided by the network entity 105. For example, a network entity 105 may be collocated with the downlink transmission point, may additionally include uplink reception capabilities via one or more antenna panels, and may control or otherwise be associated with the (non-collocated) uplink reception points to supplement uplink coverage and capacity.

In other words, the wireless communications system 100 (to support an uplink dense deployment) may be configured or allocated to improve coverage and/or capacity of uplink communication and may be associated with an asymmetric downlink/uplink densification. By providing and using the uplink reception points, a network entity 105 may reduce uplink pathloss, which may be helpful in scenarios in which uplink coverage is a bottleneck for uplink communication, and in terms of deployment cost and/or complexity because the uplink reception points may not transmit any downlink signaling. Instead, an uplink reception point may receive an uplink signal or channel and send (such as forward, relay, or transmit) the signal or channel (or information parsed or decoded from the signal or channel) to a network entity 105 (such as the macro node) . An uplink reception point may send the signal or channel (or information parsed or decoded therefrom) to a network entity 105 with complete or partial processing or without any processing.

In some aspects, a UE 115 may be configured with a unified transmission configuration indication (TCI) state type per component carrier. In other words, a UE 115 may receive, from a network entity 105 via configuration signaling (such as via RRC signaling) , information indicative of a unified TCI state type per component carrier. A unified (such as joint) TCI state may be a TCI state that indicates a configuration for directional communication (such as a communication beam) that may be used for uplink transmissions and downlink transmissions. If joint unified TCI state is configured (such as for a given component carrier or for a set of component carriers) , a UE 115 may be configured (such as via received RRC signaling) with a list (such as a set) of up to a threshold quantity (such as 128) TCI states by a dl-OrJointTCI-StateList parameter for downlink and uplink operation. In such cases, a TCI state may be used to provide a reference signal for a quasi-collocation (QCL) for a demodulation reference signal (DMRS) of a physical downlink shared channel (PDSCH) , a DMRS of a physical downlink control channel (PDCCH) , and/or a CSI-RS and to determine (such as indicate) an uplink transmit spatial filter for dynamic physical uplink shared channel (PUSCH) , configured grant (CG) , physical uplink control channel (PUCCH) , and/or sounding reference signal (SRS) transmissions.

Additionally, or alternatively, if separate TCI state is configured (such as for a given component carrier or for a set of component carriers) , a UE 115 may be configured with a list (such as a set) of up to a threshold quantity (such as 128) , TCI states by a dl-OrJointTCI-StateList parameter for a downlink TCI state and a list (such as a set) of up to a threshold quantity (such as 64) TCI states by an ul-TCI-ToAddModList parameter for an uplink TCI state. In such cases, a downlink TCI state may be used to provide a reference signal for the QCL for a DMRS of a PDSCH, a DMRS of a PDCCH, and/or a CSI-RS and an uplink TCI state may be used to determine an uplink transmit spatial filter for dynamic PUSCH, CG, PUCCH, and/or SRS transmissions.

In some systems, up to a threshold quantity (such as 8) TCI states and/or pairs of TCI states (with one TCI state for downlink channels or signals and/or one TCI state for uplink channels or signals) can be activated by a TCI state activation medium access control (MAC) control element (MAC-CE) . In such systems, a beam (such as a TCI state) indication DCI format (such as a DCI format 1_1/1_2 with or without a PDSCH assignment) may indicate one TCI state or one pair of TCI states of a set of activated TCI states. Such a TCI state indication may be conveyed via a TCI field, such as via a codepoint of a TCI field, or another field of a DCI format 1_1/1_2. Additionally, or alternatively, a full (such as complete) set or any subset of {first downlink TCI state, first uplink TCI state, second downlink TCI state, second uplink TCI state} may be mapped to a TCI codepoint of a beam indication DCI format (such as DCI format 1_1/1_2 with or without a PDSCH assignment) by a TCI state activation MAC-CE.

Further, in some systems, a TCI state indication by DCI may remain active (such as valid) until another DCI (such as another DCI format 1_1/1_2) indicates a different TCI state. In other words, a TCI state indication by DCI may be understood as being “sticky” (and not related to a scheduled PDSCH and not a one-time indication) . A wireless communication device (such as a UE 115 or a network entity 105) may determine, calculate, select, or otherwise identify an application time for an indicated TCI state as a first slot that is at least Y symbols (with Y being RRC configured based on or otherwise in accordance with a UE capability, such as a signaled UE capability) after a last (such as final) symbol of the PUCCH carrying the HARQ-Ack in response to the DCI. An indication of a TCI state may be for uplink or for both downlink and uplink (even though the TCI state may be indicated in downlink DCI formats 1_1/1_2) . In some aspects, whether the indication of a TCI state is for uplink or for both downlink and uplink may depend on whether separate or joint downlink/uplink TCI state is configured (such as depending on a type of a TCI field codepoint in the DCI) . Further, in some aspects, a UE 115 may apply an indication of a TCI state for multiple downlink channels or signals (such as PDSCH, PDCCH, and/or CSI-RS) and/or multiple uplink channels or signals (such as PUSCH, PUCCH, and/or SRS) .

Generally, if one TCI state is activated, DCI-based TCI state indication may be skipped. In other words, a UE 115 and a network entity 105 may employ signaling mechanisms related to DCI-based TCI state indications in scenarios in which a MAC-CE has activated two or more TCI states. Example codepoints provided or indicated by fields of a DCI format, and corresponding TCI state indications, are illustrated by Tables 1 and 2, shown below. Each TCI codepoint (of a TCI field in a DCI format 1_1/1_2) may be mapped to one TCI state or one pair TCI states (such as one downlink TCI state and one uplink TCI state) of a set of active TCI states (activated by a MAC-CE) . In Tables 1 and 2, (different) TCI states are denoted by (different) “a” and “b” values for purpose of example. In examples in which a TCI state indication is provided (by a network entity 105) via an SRS resource set indicator field, and in examples in which ‘10’ or ‘11’ is indicated, the first indicated uplink TCI state may be applied to the PUSCH occasion associated with the first SRS resource set and the second indicated uplink TCI state may be applied to the PUSCH occasion associated with the second SRS resource set. In other words, the SRS resource set indicator field may be used to indicate which one or both of the indicated TCI states is to be applied to the scheduled/activated PUSCHs.

TABLE 1: TCI Field Codepoint

TABLE 2: SRS Resource Set Indicator Field

In examples in which DCI format 1_1/1_2 is used for beam (such as TCI state) indication, a network entity 105 may set various fields to specific or default values (such as to (implicitly) convey that the DCI format is for beam indication) or to values that otherwise provide information to a receiving UE 115 to accurately and/or properly decode the DCI and employ the correct TCI state (s) . For example, within DCI format 1_1/1_2 for beam indication, a configured scheduling radio network temporary identifier (RNTI) (CS-RNTI) may be used to scramble a cyclic redundancy check (CRC) for the DCI, a redundancy version (RV) field may be set to a specific or default value (such as such as all ‘1’ s) , a modulation and coding scheme (MCS) field may be set to a specific or default value (such as such as all ‘1’ s) , a new data indicator (NDI) field may be set to a specific or default value (such as ‘0’ ) , and a frequency domain resource allocation (FDRA) field may be set to a first value (such as all ‘0’ s) for FDRA Type 0, a second value (such as all ‘1’ s) for FDRA Type 1, or a third value (such as all ‘0’ s) for dynamicSwitch.

The TCI field may be used to indicate a TCI codepoint from the multiple activated TCI codepoints in TCI state activation MAC-CE. The DCI may further include a field associated with an identifier for DCI formats, a field associated with a carrier indicator, a field associated with a bandwidth part (BWP) indicator, a field associated with a time domain resource allocation (TDRA) , a field associated with a downlink assignment index (if configured) , a field associated with a transmit power control (TPC) command for a scheduled PUCCH, a field associated with a PUCCH resource indicator, a field associated with a PDSCH-to-HARQ feedback timing indicator (optionally or conditionally present) , and a set of one or more reserved fields, bits, or codepoints.

In accordance with some example implementations, a UE 115 may use an indicated TCI state for a random access message, such as a random access preamble that the UE 115 may transmit via a PRACH. In some aspects, the UE 115 may perform a PRACH transmission in accordance with an indicated TCI state in accordance with a mechanism associated with facilitating a determination of a TA value for communication from the UE 115 to the uplink-only TRP. In scenarios in which a single TCI state is indicated to the UE 115, the UE 115 may use the indicated TCI state for the PRACH transmission in accordance with a rule that defines use of an indicated TCI state for a PDCCH-ordered PRACH transmission. In scenarios in which two TCI states are indicated to the UE 115, the UE 115 may select one of the two indicated TCI states for the PRACH transmission in accordance with a fixed rule and/or a signaled indication from the network entity 105 (such as an indication in the DCI message ordering/triggering the PRACH transmission) . Additionally, or alternatively, the UE 115 and the network entity 105 may employ one or more signaling-or configuration-based mechanisms according to which the UE 115 may determine whether to use an indicated TCI state for a PRACH transmission or to perform a PRACH transmission in accordance with a baseline operation (with such a baseline operation being associated with a use, by the UE 115, of an SSB or a CSI-RS associated with an indicated PRACH occasion to determine a transmit beam for the PRACH transmission) .

Figure 2 shows an example of a network architecture 200 (such as a disaggregated base station architecture, a disaggregated RAN architecture) that supports PDCCH-ordered PRACH for an uplink-only TRP. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communications system 100. The network architecture 200 may include one or more CUs 160-a that may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with the core network 130-a–one or more disaggregated network entities 105 (such as a Near-RT RIC 175-b via an E2 link, or a Non-RT RIC 175-a associated with an SMO 180-a (such as an SMO Framework) , or both) . A CU 160-a may communicate with one or more DUs 165-a via respective midhaul communication links 162-a (such as an F1 interface) . The DUs 165-a may communicate with one or more RUs 170-a via respective fronthaul communication links 168-a. The RUs 170-a may be associated with respective coverage areas 110-a and may communicate with UEs 115-a via one or more communication links 125-a. In some implementations, a UE 115-a may be simultaneously served by multiple RUs 170-a.

Each of the network entities 105 of the network architecture 200 (such as CUs 160-a, DUs 165-a, RUs 170-a, Non-RT RICs 175-a, Near-RT RICs 175-b, SMOs 180-a, Open Clouds (O-Clouds) 205, Open eNBs (O-eNBs) 210) may include one or more interfaces or may be coupled with one or more interfaces configured to receive or transmit signals (such as data, information) via a wired or wireless transmission medium. Each network entity 105, or an associated processor (such as controller) providing instructions to an interface of the network entity 105, may be configured to communicate with one or more of the other network entities 105 via the transmission medium. For example, the network entities 105 may include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other network entities 105. Additionally, or alternatively, the network entities 105 may include a wireless interface, which may include a receiver, a transmitter, or transceiver (such as an RF transceiver) configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other network entities 105.

In some examples, a CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, or the like. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 160-a. A CU 160-a may be configured to handle user plane functionality (such as CU-UP) , control plane functionality (such as CU-CP) , or a combination thereof. In some examples, a CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. A CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface when implemented in an O-RAN configuration. A CU 160-a may be implemented to communicate with a DU 165-a, as necessary, for network control and signaling.

A DU 165-a may correspond to a logical unit that includes one or more functions (such as base station functions, RAN functions) to control the operation of one or more RUs 170-a. In some examples, a DU 165-a may host, at least partially, one or more of an RLC layer, a MAC layer, and one or more aspects of a PHY layer (such as a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP) . In some examples, a DU 165-a may further host one or more low PHY layers. Each layer may be implemented with an interface configured to communicate signals with other layers hosted by the DU 165-a, or with control functions hosted by a CU 160-a.

In some examples, lower-layer functionality may be implemented by one or more RUs 170-a. For example, an RU 170-a, controlled by a DU 165-a, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT) , inverse FFT (iFFT) , digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like) , or both, based at least in part on the functional split, such as a lower-layer functional split. In such an architecture, an RU 170-a may be implemented to handle over the air (OTA) communication with one or more UEs 115-a. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU (s) 170-a may be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable a DU 165-a and a CU 160-a to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an O1 interface) . For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (such as an O-Cloud 205) to perform network entity life cycle management (such as to instantiate virtualized network entities 105) via a cloud computing platform interface (such as an O2 interface) . Such virtualized network entities 105 can include, but are not limited to, CUs 160-a, DUs 165-a, RUs 170-a, and Near-RT RICs 175-b. In some implementations, the SMO 180-a may communicate with components configured in accordance with a 4G RAN (such as via an O1 interface) . Additionally, or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a also may include a Non-RT RIC 175-a configured to support functionality of the SMO 180-a.

The Non-RT RIC 175-a may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence (AI) or Machine Learning (ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 175-b. The Non-RT RIC 175-a may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 175-b. The Near-RT RIC 175-b may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 160-a, one or more DUs 165-a, or both, as well as an O-eNB 210, with the Near-RT RIC 175-b.

In some examples, to generate AI/ML models to be deployed in the Near-RT RIC 175-b, the Non-RT RIC 175-a may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 175-b and may be received at the SMO 180-a or the Non-RT RIC 175-a from non-network data sources or from network functions. In some examples, the Non-RT RIC 175-a or the Near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 175-a may monitor long-term trends and patterns for performance and employ AI or ML models to perform corrective actions–the SMO 180-a (such as reconfiguration via O1) or via generation of RAN management policies (such as A1 policies) .

Figure 3 shows an example of an uplink dense deployment 300 that supports PDCCH-ordered PRACH for an uplink-only TRP. The uplink dense deployment 300 may implement or be implemented to realize aspects of the wireless communications system 100 or the network architecture 200. For example, the uplink dense deployment 300 illustrates a system including a downlink transmission point 305 and uplink reception points 310 connected with the downlink transmission point 305 via backhaul links 315. In some implementations, the downlink transmission point 305 and the uplink reception points 310 may be associated with a network entity 105, such as a network entity 105 as illustrated by or described with reference to Figures 1 and 2. Further, although illustrated as including multiple uplink reception points 310, the uplink dense deployment 300 may include any quantity of one or more uplink reception points 310.

The uplink dense deployment 300 may be understood as or associated with an asymmetric downlink single transmission and reception point (sTRP) /uplink multi-transmission and reception point (mTRP) deployment scenarios, in intra-band intra-cell non-collocated mTRP scenarios, and with a unified TCI framework for mTRP (using, such as communicating via, FR1 and/or FR2) . In some aspects, the uplink dense deployment 300 may support two closed-loop power control adjustment states for SRS, both separate from PUSCH, and pathloss offset configurations for pathloss calculation to uplink TRP (s) , when the pathloss reference signal is from a downlink sTRP (such as the downlink transmission point 305) . The uplink dense deployment 300 may further support multi-downlink control information (DCI) -based two transmitter address toward uplink TRP (s) and downlink sTRP without using CoresetPoolIndex, while assuming backwards compatible PRACH resources.

The network entity 105 may refer to a base station, a gNB, or another entity or node that controls or is otherwise associated with (such as connected with via a backhaul link) one or more uplink reception points 310. Thus, the network entity 105 may be understood as including one or more uplink reception points 310 and/or as being communicatively coupled with the one or more uplink reception points 310 (via, for example, one or more backhaul links 315, which may be wired or wireless) . Accordingly, the network entity 105 may receive or otherwise obtain uplink signaling from one or more UEs 115 via one or more uplink reception points 310.

The network entity 105 also may include or otherwise control the downlink transmission point 305 via which the network entity 105 transmits downlink signals or channels. Such a downlink transmission point 305 may be associated with (such as may be) a macro node associated with the network entity 105, a central node associated with the network entity 105, a serving cell associated with the network entity 105, or a serving base station associated with the network entity 105. The network entity 105 may support both uplink and downlink communication via its collocated (or approximately collocated) antenna panels and may use the one or more uplink reception points 310 to supplement the uplink coverage or capacity provided by the network entity 105. For example, the network entity 105 may be collocated with the downlink transmission point 305, may additionally include uplink reception capabilities via one or more antenna panels, and may control or otherwise be associated with the (non-collocated) uplink reception points 310 to supplement uplink coverage and capacity.

In other words, the uplink dense deployment 300 may be configured or allocated to improve coverage and/or capacity of uplink communication and may be associated with an asymmetric downlink/uplink densification. By providing and using the uplink reception points 310, the network entity 105 may reduce uplink pathloss, which may be helpful in scenarios in which uplink coverage is a bottleneck for uplink communication, and in terms of deployment cost and/or complexity because the uplink reception points 310 may not transmit any downlink signaling. Instead, an uplink reception point 310 may receive an uplink signal or channel and send (such as forward, relay, or transmit) the signal or channel (or information parsed or decoded from the signal or channel) to the network entity 105 (such as the macro node) . An uplink reception point 310 may send the signal or channel (or information parsed or decoded therefrom) to the network entity 105 with complete or partial processing or without any processing.

Additionally, or alternatively, one or more wireless communication devices (such as one or more UEs 115 or one or more network entities 105, or any combination thereof) may support supplementary uplink (SUL) . In accordance with SUL, a UE 115 may be configured (by a network entity 105) with two (or more) uplink carriers for one downlink carrier of a same serving cell, with uplink transmissions via the two uplink carriers being at different times (such as not being simultaneous) . For example, for TDD band + SUL, a UE 115 may transmit uplink signaling either via a TDD band (non-SUL, or “NUL” ) or via an SUL carrier.

In scenarios in which a UE 115 transmits to one or more uplink reception points 310 or in scenarios in which the UE 115 supports SUL (or in both) , downlink beams and uplink beams may be separate. In other words, for uplink beam management, a wireless communication device may not assume a beam correspondence between downlink and uplink. Thus, to indicate an uplink beam (such as via spatial relation info) , a downlink reference signal (such as SSB and/or CSI-RS) may not be used. In some aspects, uplink beam management without beam correspondence may be performed in accordance with one or more SRS transmissions (SRS for beam management) . In other words, in scenarios of no beam correspondence between downlink and uplink, different SRS resources may be transmitted with different transmit beams (with the selection of the transmit beam (s) being up to the UE 115) , and a network entity 105 may select the best transmit beam. Such SRS-based uplink beam management may be performed (by a UE 115 and a network entity 105) after an initial access (such that the UE 115 is in an RRC connected state with the network entity 105) .

In some aspects, uplink beam management associated with SRS may be used to identify (such as determine, calculate, select, or ascertain) one or more of a suitable transmit beam, a closest uplink reception point 310 at which the transmit beam can be received, and/or a suitable receive beam at the uplink reception point 310. Additionally, or alternatively, the SRS may be used to measure an uplink timing advance (TA) . In accordance with an obtainment of the TA for an uplink TRP, a MAC-CE may be used (by a network entity 105) to update the TA.

In scenarios of a single TA, some MAC-CE mechanisms for TA update may (only) indicate a relative TA compared with a latest TA associated with a same TA group (TAG) . If the relative TA change is sufficiently large, a TA command MAC-CE may be insufficient (in terms of, for example, a quantity of bits) . In such scenarios, a PDCCH-ordered PRACH may be used so that an absolute TA value may be indicated (such as by the network entity 105 via a random access response (RAR) ) .

In scenarios of two (or more) TAs, although SRS for beam management may be used for TA measurement, for the first (initial) time the TA to an uplink-only TRP is obtained, there may be no initial TA corresponding to the uplink-only TRP. In such scenarios, some TA command MAC-CEs may not be used directly to indicate the TA for the uplink-only TRP because such TA command MAC-CEs indicate a relative TA compared with a previous TA associated with a same TAG (while there is no previous TA yet associated with the TAG for (associated with) the uplink-only TRP) . In some systems, a TA command MAC-CE may indicate the TA for an uplink-only TRP in scenarios in which a TA is measured based on SRS. Additionally, or alternatively, wireless communication devices may use PRACH to measure the TA for the uplink-only TRP, in which case an absolute TA may be indicated by the RAR in response to a PRACH transmission by a UE 115. Thus, a PRACH transmission to an uplink-only TRP may be a mechanism via which a UE 115 and a network entity may determine a viable TA associated with communication from the UE 115 to the uplink-only TRP.

In accordance with some example implementations, a UE 115 may use an indicated TCI state for a PRACH transmission to an uplink-only TRP to facilitate acquirement of a TA for communication to the uplink-only TRP. In other words, for a PDCCH-ordered PRACH transmission, a UE 115 may use one indicated joint/UL TCI state from the one or two indicated joint/UL TCI state (s) . For example, for a PRACH to an uplink-only TRP, because there may already have been some previous uplink beam sweeping, an uplink transmit beam to the uplink-only TRP (such as one joint/UL TCI state or two joint/UL TCI states in case of UL mTRP) may be already indicated by a MAC-CE or a beam indication DCI. In such examples, the UE 115 may use the current indicated join/uplink TCI state for the PRACH transmission. In scenarios of uplink mTRP, more than one joint/UL TCI state may be indicated. In such scenarios, a UE 115 and a network entity 105 may employ one or more signaling-or configuration-based mechanisms to determine which joint/UL TCI state to use for a (later) PRACH transmission.

Figure 4 shows an example of a communication timeline 400 that supports PDCCH-ordered PRACH for an uplink-only TRP. The communication timeline 400 may illustrate an example of an sTRP deployment scenario associated with a unified TCI state. For example, in scenarios in which an uplink sTRP is configured and in which one joint/UL TCI state is indicated, the UE 115 may use the indicated joint/UL TCI state for a PRACH transmission. A DCI format 1_1/1_2 may be an example of a first DCI message, a PDCCH order DCI may be an example of a second DCI message, and a PRACH transmission may be an example of a random access message that a UE 115 transmits via a PRACH occasion (such as a PRACH occasion indicated by the PDCCH order DCI) .

Figure 5 shows an example of a communication timeline 500 that supports PDCCH-ordered PRACH for an uplink-only TRP. The communication timeline 500 may illustrate an example of an mTRP deployment scenario associated with a unified TCI state (such as unified TCI for single-DCI (s-DCI) mTRP) . For example, in scenarios in which uplink mTRP is configured, one or two joint/UL TCI states may be indicated. In some implementations, if two joint/UL TCI states are indicated, the UE 115 may select one of the joint/UL TCI states in accordance with a fixed rule (such as a TCI state selection rule) .

In some aspects, the rule may indicate that (1) a first (initially) indicated joint/UL TCI state or the indicated joint/UL TCI state with a lower TCI state ID is to be used for the PRACH transmission. In some other aspects, the rule may indicate that (2) a first indicated joint/UL TCI state that is associated with a pathloss offset is to be used for the PRACH transmission. In some other aspects, the rule may indicate that (3) an indicated joint/UL TCI state with a lower TCI state ID and associated with a pathloss offset is to be used for the PRACH transmission.

Figure 6 shows an example of a communication timeline 600 that supports PDCCH-ordered PRACH for an uplink-only TRP. The communication timeline 600 may illustrate an example of an mTRP deployment scenario associated with a unified TCI state (such as unified TCI for s-DCI mTRP) . For example, in scenarios in which uplink mTRP is configured, one or two joint/UL TCI states may be indicated. In some implementations, if two joint/UL TCI states are indicated, the UE 115 may be indicated by the PDCCH order DCI to use the first indicated joint/UL TCI state or the second indicated joint/UL TCI state for the PRACH transmission.

In some aspects (1) , a new field, such as a TCI selection field, may be introduced in the PDCCH order DCI. In such aspects, a reserved bit in the PDCCH order DCI may be used as the TCI selection field. In some other aspects (2) , a PRACH association indicator field in the PDCCH order DCI may be used to indicate whether the UE 115 is to use the first indicated joint/UL TCI state or the second indicated joint/UL TCI state for the PRACH transmission. Additionally, or alternatively, the UE 115 may receive an indication of whether to use the first indicated joint/UL TCI state or the second indicated joint/UL TCI state for the PRACH transmission in accordance with an RRC configuration (such as in accordance with information provided via control signaling, such as RRC signaling, indicating or carrying one or more information elements, such as RRC information elements) .

In accordance with determining the indicated joint/UL TCI state to use for PRACH transmission, the UE 115 may determine the transmit beam for the PRACH transmission in accordance with a source reference signal in the indicated joint/UL TCI state. Additionally, or alternatively, the UE 115 may determine a transmit power for the PRACH transmission in accordance with the pathloss offset associated with the indicated joint/UL TCI state. For pathloss reference signal for PRACH power control, the PL RS associated with the indicated joint/UL TCI state may be used by the UE 115.

Figure 7 shows an example of a communication timeline 700 that supports PDCCH-ordered PRACH for an uplink-only TRP. In some implementations, a UE 115 and a network entity 105 may support one or more signaling-or configuration-based mechanisms to determine whether an indicated TCI state is applied to a PRACH transmission (considering that the UE 115 may fall back to a baseline operation to transmit the PRACH to a downlink TRP, such as a gNB) . In some implementations, the UE 115 and the network entity 105 may determine that, if there is at least one indicated TCI state at a time the PRACH is triggered or transmitted, the UE 115 may transmit the PRACH in accordance with an indicated TCI; otherwise, the UE 115 may transmit the PRACH in accordance with an associated SSB/CSI-RS as in accordance with a baseline operation.

Additionally, or alternatively, the UE 115 may be indicated by the PDCCH order DCI regarding whether to use an indicated joint/UL TCI or not for the PRACH transmission. In scenarios in which sTRP is configured (unified TCI for sTRP) , a new field may be introduced to the PDCCH order DCI to enable or disable an indicated joint/UL TCI state for PRACH. In some aspects, one of the reserved bits of the PDCCH order DCI may be used to provide such information/indication of whether use of an indicated TCI state for a PRACH transmission is enabled or disabled. Additionally, or alternatively, in scenarios in which sTRP is configured (unified TCI for sTRP) and in which two TAs are supported, a PRACH association indicator field of the PDCCH order DCI may be used to provide such information/indication of whether use of an indicated TCI state for a PRACH transmission is enabled or disabled. For example, if the PRACH association indicator field is set to 0, the UE 115 may transmit PRACH in accordance with an associated SSB/CSI-RS as in a baseline operation. Alternatively, if the PRACH association indicator field is set to 1, the UE 115 may transmit PRACH in accordance with an indicated joint/UL TCI state.

Figure 8 shows an example of a communication timeline 800 that supports PDCCH-ordered PRACH for an uplink-only TRP. In some implementations, the UE 115 may be indicated by the PDCCH order DCI regarding whether to use an indicated joint/UL TCI or not for the PRACH transmission. In scenarios in which mTRP is configured (unified TCI for s-DCI mTRP) , a new field may be introduced in the PDCCH order DCI to enable or disable an indicated joint/UL TCI state for PRACH. In such aspects, one of the reserved bits of the PDCCH order DCI may be used to provide such information/indication of whether use of an indicated TCI state for a PRACH transmission is enabled or disabled. In some aspects, such a new field may be a separate field from a TCI selection field. In such aspects, if an indicated joint/UL TCI state is enabled for a PRACH transmission, which indicated joint/UL TCI state (of multiple) to use may be determined in accordance with a signaled indication (also provided via the PDCCH order DCI, such as via the TCI selection field) or in accordance with a fixed rule.

Figure 9 shows an example of a communication timeline 900 that supports PDCCH-ordered PRACH for an uplink-only TRP. In some implementations, the UE 115 may be indicated by the PDCCH order DCI regarding whether to use an indicated joint/UL TCI or not for the PRACH transmission. In scenarios in which mTRP is configured (unified TCI for s-DCI mTRP) , a TCI selection field may be used to indicate whether the UE 115 is to use an indicated TCI state for the PRACH transmission or whether the UE 115 is to fall back to a baseline operation to transmit the PRACH transmission. For example, one codepoint in the TCI selection field may be used to indicate that none of the indicated joint/UL TCI state is used. If such a codepoint is indicated by the TCI selection field, the UE 115 may transmit a PRACH in accordance with an associated SSB/CSI-RS as in a baseline operation. In some aspects, remaining codepoints of the TCI selection field may be used to indicate which one of the indicated joint/UL TCI state is to be used for the PRACH transmission.

In some implementations, the UE 115 and the network entity 105 may transmit and/or receive configuration signaling (such as RRC signaling) that provides an interpretation associated with any one or more of the various fields, codepoints, and/or bits described herein. Further, the UE 115 and the network entity 105 may transmit and/or receive signaling indicative of one or more device capabilities related to any of such interpretations including, for example, a capability relating to whether a device is able to use an indicated TCI state for a PRACH transmission. Additionally, or alternatively, various interpretations and/or field/bit uses may be activated and/or deactivated via signaling, such as via one or more MAC-CEs.

Figure 10 shows a block diagram 1000 of a UE 1020 that supports PDCCH-ordered PRACH for an uplink-only TRP. The UE 1020 may be an example of aspects of a UE as described with reference to Figures 1–7. The UE 1020, or various components thereof, may be an example of means for performing various aspects of PDCCH-ordered PRACH for an uplink-only TRP. For example, the UE 1020 may include a DCI component 1025, a random access component 1030, a TCI state selection component 1035, an RRC component 1040, or any combination thereof. Each of these components, or components or subcomponents thereof (such as one or more processors, one or more memories) , may communicate, directly or indirectly, with one another (such as via one or more buses) .

The UE 1020 may support wireless communication in accordance with examples as disclosed herein. The DCI component 1025 is capable of, configured to, or operable to support a means for receiving a first DCI message including an indication of one or more transmission configuration indication (TCI) states. In some examples, the DCI component 1025 is capable of, configured to, or operable to support a means for receiving a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion. The random access component 1030 is capable of, configured to, or operable to support a means for transmitting the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states.

In some examples, to support receiving the first DCI message, the DCI component 1025 is capable of, configured to, or operable to support a means for receiving an indication of a single TCI state, in which the one or more TCI states consists of the single TCI state, and in which the first TCI state is the single TCI state.

In some examples, the UE transmits the random access message in accordance with the single TCI state in accordance with a rule defining that the UE is to use an indicated TCI state for the random access message indicated by the second DCI message.

In some examples, to support receiving the first DCI message, the DCI component 1025 is capable of, configured to, or operable to support a means for receiving an indication of a set of multiple TCI states via the first DCI message, in which the one or more TCI states include the set of multiple TCI states, and in which the set of multiple TCI states includes the first TCI state.

In some examples, the TCI state selection component 1035 is capable of, configured to, or operable to support a means for selecting the first TCI state from the set of multiple TCI states in accordance with a rule defining a TCI state selection criterion associated with the random access message indicated by the second DCI message, in which transmitting the random access message in accordance with the first TCI state is in association with selecting the first TCI state.

In some examples, the rule defines that an initially indicated TCI state, of the set of multiple TCI states, is to be used for the random access message. In some examples, the first TCI state is the initially indicated TCI state of the set of multiple TCI states.

In some examples, the rule defines that a TCI state associated with a lowest TCI state identifier, of the set of multiple TCI states, is to be used for the random access message. In some examples, the first TCI state is associated with the lowest TCI state identifier of the set of multiple TCI states.

In some examples, the rule defines that an initially indicated TCI state, of a subset of the set of multiple TCI states associated with a pathloss offset, is to be used for the random access message. In some examples, the first TCI state is the initially indicated TCI state of the subset of the set of multiple TCI states.

In some examples, the rule defines that a TCI state associated with a lowest TCI state identifier, of a subset of the set of multiple TCI states associated with a pathloss offset, is to be used for the random access message. In some examples, the first TCI state is associated with the lowest TCI state identifier of the subset of the set of multiple TCI states.

In some examples, the rule defines the TCI state selection criterion for PDCCH-ordered random access message transmissions. In some examples, the random access message indicated by the second DCI message is a PDCCH-ordered random access message transmission.

In some examples, to support receiving the second DCI message, the DCI component 1025 is capable of, configured to, or operable to support a means for receiving information indicative of the first TCI state via the second DCI message, in which transmitting the random access message in accordance with the first TCI state is in association with receiving the information indicative of the first TCI state via the second DCI message.

In some examples, a field of the second DCI message includes the information indicative of the first TCI state.

In some examples, the field includes one or more bits. In some examples, a first codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with the first TCI state and a second codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with a second TCI state of the set of multiple TCI states. In some examples, the one or more bits indicate the first codepoint.

In some examples, the field is a TCI selection field of the second DCI message.

In some examples, the field is a PRACH association indicator field of the second DCI message.

In some examples, the RRC component 1040 is capable of, configured to, or operable to support a means for receiving control signaling that indicates that the UE is to transmit the random access message in accordance with the first TCI state, in which transmitting the random access message in accordance with the first TCI state is in association with receiving the control signaling.

In some examples, the control signaling includes one or more RRC information elements that indicate that the UE is to transmit the random access message in accordance with the first TCI state.

In some examples, the random access component 1030 is capable of, configured to, or operable to support a means for determining whether to transmit the random access message in accordance with the first TCI state in accordance with a presence of at least one indicated TCI state or an absence of at least one indicated TCI state at a transmission time associated with the random access message, in which transmitting the random access message in accordance with the first TCI state is in association with determining whether to transmit the random access message in accordance with the first TCI state.

In some examples, the presence of at least one indicated TCI state at the transmission time associated with the random access message indicates that the UE is to transmit the random access message in accordance with the first TCI state. In some examples, the absence of at least one indicated TCI state at the transmission time associated with the random access message indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion.

In some examples, to support receiving the second DCI message, the DCI component 1025 is capable of, configured to, or operable to support a means for receiving information indicative of whether the UE is to transmit the random access message in accordance with the first TCI state, in which transmitting the random access message in accordance with the first TCI state is in association with receiving the information.

In some examples, a field of the second DCI message includes the information indicative of whether the UE is to transmit the random access message in accordance with the first TCI state.

In some examples, the field includes one or more bits. In some examples, a first codepoint associated with the one or more bits indicates that random access message transmissions in accordance with an indicated TCI state are enabled and a second codepoint associated with the one or more bits indicates that random access message transmissions in accordance with the indicated TCI state are disabled. In some examples, the one or more bits indicate the first codepoint.

In some examples, the field is a dedicated field of the second DCI message that is associated with enabling or disabling use of the indicated TCI state for random access message transmissions.

In some examples, the field includes one or more bits. In some examples, a first codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with the first TCI state and a second codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion. In some examples, the one or more bits indicate the first codepoint.

In some examples, the field includes a set of multiple bits. In some examples, a first codepoint associated with the set of multiple bits indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion, a second codepoint associated with the set of multiple bits indicates that the UE is to transmit the random access message in accordance with the first TCI state, and a third codepoint associated with the set of multiple bits indicates that the UE is to transmit the random access message in accordance with a second TCI state of the set of multiple TCI states. In some examples, the set of multiple bits indicates the second codepoint.

In some examples, the field is a TCI selection field of the second DCI message.

In some examples, to support transmitting the random access message, the random access component 1030 is capable of, configured to, or operable to support a means for transmitting the random access message using a transmission power that is associated with the pathloss offset associated with the first TCI state.

In some examples, to support transmitting the random access message, the random access component 1030 is capable of, configured to, or operable to support a means for transmitting the random access message using a transmission beam associated with a source reference signal that is associated with the first TCI state.

In some examples, the random access component 1030 is capable of, configured to, or operable to support a means for transmitting information indicative of a capability of the UE to perform random access message transmissions in accordance with an indicated TCI state, in which transmitting the random access message in accordance with the first TCI state is in association with transmitting the information indicative of the capability of the UE.

Figure 11 shows a diagram of a system 1100 including a device 1105 that supports PDCCH-ordered PRACH for an uplink-only TRP. The device 1105 may communicate (such as wirelessly) with one or more other devices (such as network entities 105, UEs 115, or a combination thereof) . The device 1105 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1120, an input/output (I/O) controller, such as an I/O controller 1110, a transceiver 1115, one or more antennas 1125, at least one memory 1130, code 1135, and at least one processor 1140. These components may be in electronic communication or otherwise coupled (such as operatively, communicatively, functionally, electronically, electrically) via one or more buses (such as a bus 1145) .

The I/O controller 1110 may manage input and output signals for the device 1105. The I/O controller 1110 also may manage peripherals not integrated into the device 1105. In some examples, the I/O controller 1110 may represent a physical connection or port to an external peripheral. In some examples, the I/O controller 1110 may utilize an operating system such as or another known operating system. Additionally, or alternatively, the I/O controller 1110 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some examples, the I/O controller 1110 may be implemented as part of one or more processors, such as the at least one processor 1140. In some examples, a user may interact with the device 1105 via the I/O controller 1110 or via hardware components controlled by the I/O controller 1110.

In some examples, the device 1105 may include a single antenna. However, in some other cases, the device 1105 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1115 may communicate bi-directionally via the one or more antennas 1125 using wired or wireless links. For example, the transceiver 1115 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1115 also may include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1125 for transmission, and to demodulate packets received from the one or more antennas 1125. The transceiver 1115, or the transceiver 1115 and one or more antennas 1125, may be an example of a transmitter, a transmitter, a receiver, a receiver, or any combination thereof or component thereof.

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

The at least one processor 1140 may include one or more intelligent hardware devices (such as one or more general-purpose processors, one or more digital signal processor (DSP) s, one or more central processing unit (CPU) s, one or more graphics processing units (GPUs) , one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , one or more microcontrollers, one or more application-specific integrated circuit (ASIC) s, one or more field-programmable gate array (FPGA) s, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof) . In some examples, the at least one processor 1140 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 1140. The at least one processor 1140 may be configured to execute computer-readable instructions stored in a memory (such as the at least one memory 1130) to cause the device 1105 to perform various functions (such as functions or tasks supporting PDCCH-ordered PRACH for an uplink-only TRP) . For example, the device 1105 or a component of the device 1105 may include at least one processor 1140 and at least one memory 1130 coupled with or to the at least one processor 1140, the at least one processor 1140 and the at least one memory 1130 configured to perform various functions described herein.

In some examples, the at least one processor 1140 may include multiple processors and the at least one memory 1130 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions described herein. In some examples, the at least one processor 1140 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1140) and memory circuitry (which may include the at least one memory 1130) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1140 or a processing system including the at least one processor 1140 may be configured to, configurable to, or operable to cause the device 1105 to perform one or more of the functions described herein. Further, being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 1135 (such as processor-executable code) stored in the at least one memory 1130 or otherwise, to perform one or more of the functions described herein.

The processing system of the device 1105 includes processor (or “processing” ) circuitry in the form of one or multiple processors, microprocessors, processing units (such as CPUs, GPUs, NPUs (also referred to as neural network processors or DLPs) , or DSPs) , processing blocks, ASIC, PLDs (such as FPGAs) , or other discrete gate or transistor logic or circuitry (all of which may be generally referred to herein individually as “processors” or collectively as “the processor” or “the processor circuitry” ) . One or more of the processors may be individually or collectively configurable or configured to perform various functions or operations described herein. The processing system may further include memory circuitry in the form of one or more memory devices, memory blocks, memory elements or other discrete gate or transistor logic or circuitry, each of which may include tangible storage media such as RAM or ROM, or combinations thereof (all of which may be generally referred to herein individually as “memories” or collectively as “the memory” or “the memory circuitry” ) . One or more of the memories may be coupled with one or more of the processors and may individually or collectively store processor-executable code that, when executed by one or more of the processors, may configure one or more of the processors to perform various functions or operations described herein.

Additionally, or alternatively, in some examples, one or more of the processors may be preconfigured to perform various functions or operations described herein without requiring configuration by software. The processing system may further include or be coupled with one or more modems (such as a Wi-Fi (such as IEEE compliant) modem or a cellular (such as 3GPP 4G LTE, 5G or 6G compliant) modem) . In some implementations, one or more processors of the processing system include or implement one or more of the modems. The processing system may further include or be coupled with multiple radios (collectively “the radio” ) , multiple RF chains or multiple transceivers, each of which may in turn be coupled with one or more of multiple antennas. In some implementations, one or more processors of the processing system include or implement one or more of the radios, RF chains or transceivers.

The communications manager 1120 may support wireless communication in accordance with examples as disclosed herein. For example, the communications manager 1120 is capable of, configured to, or operable to support a means for receiving a first DCI message including an indication of one or more transmission configuration indication (TCI) states. The communications manager 1120 is capable of, configured to, or operable to support a means for receiving a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion. The communications manager 1120 is capable of, configured to, or operable to support a means for transmitting the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states.

By including or configuring the communications manager 1120 in accordance with examples, the device 1105 may support techniques for improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, and improved utilization of processing capability.

In some examples, the communications manager 1120 may be configured to perform various operations (such as receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1115, the one or more antennas 1125, or any combination thereof. Although the communications manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1120 may be supported by or performed by the at least one processor 1140, the at least one memory 1130, the code 1135, or any combination thereof. For example, the code 1135 may include instructions executable by the at least one processor 1140 to cause the device 1105 to perform various aspects of PDCCH-ordered PRACH for an uplink-only TRP, or the at least one processor 1140 and the at least one memory 1130 may be otherwise configured to, individually or collectively, perform or support such operations.

Figure 12 shows a block diagram 1200 of a network entity 1220 that supports PDCCH-ordered PRACH for an uplink-only TRP. The network entity 1220 may be an example of aspects of a network entity as described with reference to Figures 1–7. The network entity 1220, or various components thereof, may be an example of means for performing various aspects of PDCCH-ordered PRACH for an uplink-only TRP. For example, the network entity 1220 may include a DCI component 1225, a random access component 1230, an RRC component 1235, or any combination thereof. Each of these components, or components or subcomponents thereof (such as one or more processors, one or more memories) , may communicate, directly or indirectly, with one another (such as via one or more buses) . The communications may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (such as between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105) , or any combination thereof.

The network entity 1220 may support wireless communication in accordance with examples as disclosed herein. The DCI component 1225 is capable of, configured to, or operable to support a means for outputting, to a UE, a first DCI message including an indication of one or more transmission configuration indication (TCI) states. In some examples, the DCI component 1225 is capable of, configured to, or operable to support a means for outputting, to the UE, a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion. The random access component 1230 is capable of, configured to, or operable to support a means for obtaining the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states.

In some examples, to support outputting the first DCI message, the DCI component 1225 is capable of, configured to, or operable to support a means for outputting an indication of a single TCI state, in which the one or more TCI states consists of the single TCI state, and in which the first TCI state is the single TCI state.

In some examples, the network entity obtains the random access message in accordance with the single TCI state in accordance with a rule defining that the UE is to use an indicated TCI state for the random access message indicated by the second DCI message.

In some examples, to support outputting the first DCI message, the DCI component 1225 is capable of, configured to, or operable to support a means for outputting an indication of a set of multiple TCI states via the first DCI message, in which the one or more TCI states include the set of multiple TCI states, and in which the set of multiple TCI states includes the first TCI state.

In some examples, the DCI component 1225 is capable of, configured to, or operable to support a means for generating the first DCI message in accordance with a rule defining a TCI state selection criterion associated with the random access message indicated by the second DCI message, in which transmitting the first DCI message is in association with generating the first DCI message.

In some examples, to support outputting the second DCI message, the DCI component 1225 is capable of, configured to, or operable to support a means for outputting information indicative of the first TCI state via the second DCI message, in which obtaining the random access message in accordance with the first TCI state is in association with outputting the information indicative of the first TCI state via the second DCI message.

In some examples, the field is a TCI selection field of the second DCI message.

In some examples, the RRC component 1235 is capable of, configured to, or operable to support a means for outputting control signaling that indicates that the UE is to transmit the random access message in accordance with the first TCI state, in which obtaining the random access message in accordance with the first TCI state is in association with outputting the control signaling.

In some examples, the random access component 1230 is capable of, configured to, or operable to support a means for determining whether to obtain the random access message in accordance with the first TCI state in accordance with a presence of at least one indicated TCI state or an absence of at least one indicated TCI state at a transmission time associated with the random access message, in which obtaining the random access message in accordance with the first TCI state is in association with determining whether to obtain the random access message in accordance with the first TCI state.

In some examples, to support outputting the second DCI message, the random access component 1230 is capable of, configured to, or operable to support a means for outputting information indicative of whether the UE is to transmit the random access message in accordance with the first TCI state, in which obtaining the random access message in accordance with the first TCI state is in association with outputting the information.

In some examples, the field is a TCI selection field of the second DCI message.

In some examples, the random access component 1230 is capable of, configured to, or operable to support a means for obtaining information indicative of a capability of the UE to perform random access message transmissions in accordance with an indicated TCI state, in which obtaining the random access message in accordance with the first TCI state is in association with obtaining the information indicative of the capability of the UE.

Figure 13 shows a diagram of a system 1300 including a device 1305 that supports PDCCH-ordered PRACH for an uplink-only TRP. The device 1305 may communicate with other network devices or network equipment such as one or more of the network entities 105, UEs 115, or any combination thereof. The communications may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof. The device 1305 may include components that support outputting and obtaining communications, such as a communications manager 1320, a transceiver 1310, one or more antennas 1315, at least one memory 1325, code 1330, and at least one processor 1335. These components may be in electronic communication or otherwise coupled (such as operatively, communicatively, functionally, electronically, electrically) via one or more buses (such as a bus 1340) .

The transceiver 1310 may support bi-directional communications via wired links, wireless links, or both. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315, which may be capable of transmitting or receiving wireless transmissions (such as concurrently) . The transceiver 1310 also may include a modem to modulate signals, to provide the modulated signals for transmission (such as by one or more antennas 1315, by a wired transmitter) , to receive modulated signals (such as from one or more antennas 1315, from a wired receiver) , and to demodulate signals. In some implementations, the transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1315 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1315 that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1310 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver 1310, or the transceiver 1310 and the one or more antennas 1315, or the transceiver 1310 and the one or more antennas 1315 and one or more processors or one or more memory components (such as the at least one processor 1335, the at least one memory 1325, or both) , may be included in a chip or chip assembly that is installed in the device 1305. In some examples, the transceiver 1310 may be operable to support communications via one or more communications links (such as communication link (s) 125, backhaul communication link (s) 120, a midhaul communication link 162, a fronthaul communication link 168) .

The at least one memory 1325 may include RAM, ROM, or any combination thereof. The at least one memory 1325 may store computer-readable, computer-executable, or processor-executable code, such as the code 1330. The code 1330 may include instructions that, when executed by one or more of the at least one processor 1335, cause the device 1305 to perform various functions described herein. The code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some examples, the code 1330 may not be directly executable by a processor of the at least one processor 1335 but may cause a computer (such as when compiled and executed) to perform functions described herein. In some examples, the at least one memory 1325 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some examples, the at least one processor 1335 may include multiple processors and the at least one memory 1325 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions herein (as part of a processing system) .

The at least one processor 1335 may include one or more intelligent hardware devices (such as one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs) , one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof) . In some examples, the at least one processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into one or more of the at least one processor 1335. The at least one processor 1335 may be configured to execute computer-readable instructions stored in a memory (such as one or more of the at least one memory 1325) to cause the device 1305 to perform various functions (such as functions or tasks supporting PDCCH-ordered PRACH for an uplink-only TRP) . For example, the device 1305 or a component of the device 1305 may include at least one processor 1335 and at least one memory 1325 coupled with one or more of the at least one processor 1335, the at least one processor 1335 and the at least one memory 1325 configured to perform various functions described herein. The at least one processor 1335 may be an example of a cloud-computing platform (such as one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (such as by executing code 1330) to perform the functions of the device 1305. The at least one processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1305 (such as within one or more of the at least one memory 1325) .

In some examples, the at least one processor 1335 may include multiple processors and the at least one memory 1325 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 1335 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1335) and memory circuitry (which may include the at least one memory 1325) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1335 or a processing system including the at least one processor 1335 may be configured to, configurable to, or operable to cause the device 1305 to perform one or more of the functions described herein. Further, being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1325 or otherwise, to perform one or more of the functions described herein.

The processing system of the device 1305 includes processor (or “processing” ) circuitry in the form of one or multiple processors, microprocessors, processing units (such as CPUs, GPUs, NPUs (also referred to as neural network processors or DLPs) , or DSPs) , processing blocks, ASIC, PLDs (such as FPGAs) , or other discrete gate or transistor logic or circuitry (all of which may be generally referred to herein individually as “processors” or collectively as “the processor” or “the processor circuitry” ) . One or more of the processors may be individually or collectively configurable or configured to perform various functions or operations described herein. The processing system may further include memory circuitry in the form of one or more memory devices, memory blocks, memory elements or other discrete gate or transistor logic or circuitry, each of which may include tangible storage media such as RAM or ROM, or combinations thereof (all of which may be generally referred to herein individually as “memories” or collectively as “the memory” or “the memory circuitry” ) . One or more of the memories may be coupled with one or more of the processors and may individually or collectively store processor-executable code that, when executed by one or more of the processors, may configure one or more of the processors to perform various functions or operations described herein.

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

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

The communications manager 1320 may support wireless communication in accordance with examples as disclosed herein. For example, the communications manager 1320 is capable of, configured to, or operable to support a means for outputting, to a UE, a first DCI message including an indication of one or more transmission configuration indication (TCI) states. The communications manager 1320 is capable of, configured to, or operable to support a means for outputting, to the UE, a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion. The communications manager 1320 is capable of, configured to, or operable to support a means for obtaining the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states.

By including or configuring the communications manager 1320 in accordance with examples, the device 1305 may support techniques for improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, and improved utilization of processing capability.

In some examples, the communications manager 1320 may be configured to perform various operations (such as receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1310, the one or more antennas 1315 (as applicable) , or any combination thereof. Although the communications manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1320 may be supported by or performed by the transceiver 1310, one or more of the at least one processor 1335, one or more of the at least one memory 1325, the code 1330, or any combination thereof (such as by a processing system including at least a portion of the at least one processor 1335, the at least one memory 1325, the code 1330, or any combination thereof) . For example, the code 1330 may include instructions executable by one or more of the at least one processor 1335 to cause the device 1305 to perform various aspects of PDCCH-ordered PRACH for an uplink-only TRP, or the at least one processor 1335 and the at least one memory 1325 may be otherwise configured to, individually or collectively, perform or support such operations.

Figure 14 shows a flowchart illustrating a method 1400 that supports PDCCH-ordered PRACH for an uplink-only TRP. The operations of the method 1400 may be implemented by a UE or its components. For example, the operations of the method 1400 may be performed by a UE 115 as described with reference to Figures 1–11. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At 1405, the method may include receiving a first DCI message including an indication of one or more transmission configuration indication (TCI) states. The operations of 1405 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed by a DCI component 1025 as described with reference to Figure 10.

At 1410, the method may include receiving a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion. The operations of 1410 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by a DCI component 1025 as described with reference to Figure 10.

At 1415, the method may include transmitting the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states. The operations of 1415 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed by a random access component 1030 as described with reference to Figure 10.

Figure 15 shows a flowchart illustrating a method 1500 that supports PDCCH-ordered PRACH for an uplink-only TRP. The operations of the method 1500 may be implemented by a network entity or its components. For example, the operations of the method 1500 may be performed by a network entity as described with reference to Figures 1–7 and 12 and 13. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

At 1505, the method may include outputting, to a UE, a first DCI message including an indication of one or more transmission configuration indication (TCI) states. The operations of 1505 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed by a DCI component 1225 as described with reference to Figure 12.

At 1510, the method may include outputting, to the UE, a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion. The operations of 1510 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by a DCI component 1225 as described with reference to Figure 12.

At 1515, the method may include obtaining the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states. The operations of 1515 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed by a random access component 1230 as described with reference to Figure 12.

The following provides an overview of aspects of the present disclosure:

Aspect 1: A method for wireless communication at a UE, including: receiving a first DCI message including an indication of one or more transmission configuration indication (TCI) states; receiving a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion; and transmitting the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states.

Aspect 2: The method of aspect 1, wherein receiving the first DCI message includes: receiving an indication of a single TCI state, wherein the one or more TCI states consists of the single TCI state, and wherein the first TCI state is the single TCI state.

Aspect 3: The method of aspect 2, wherein the UE transmits the random access message in accordance with the single TCI state in accordance with a rule defining that the UE is to use an indicated TCI state for the random access message indicated by the second DCI message.

Aspect 4: The method of any of aspects 1–3, wherein receiving the first DCI message includes: receiving an indication of a plurality of TCI states via the first DCI message, wherein the one or more TCI states include the plurality of TCI states, and wherein the plurality of TCI states includes the first TCI state.

Aspect 5: The method of aspect 4, further including: selecting the first TCI state from the plurality of TCI states in accordance with a rule defining a TCI state selection criterion associated with the random access message indicated by the second DCI message, wherein transmitting the random access message in accordance with the first TCI state is in association with selecting the first TCI state.

Aspect 6: The method of aspect 5, wherein the rule defines that an initially indicated TCI state, of the plurality of TCI states, is to be used for the random access message, and the first TCI state is the initially indicated TCI state of the plurality of TCI states.

Aspect 7: The method of any of aspects 5–6, wherein the rule defines that a TCI state associated with a lowest TCI state identifier, of the plurality of TCI states, is to be used for the random access message, and the first TCI state is associated with the lowest TCI state identifier of the plurality of TCI states.

Aspect 8: The method of any of aspects 5–7, wherein the rule defines that an initially indicated TCI state, of a subset of the plurality of TCI states associated with a pathloss offset, is to be used for the random access message, and the first TCI state is the initially indicated TCI state of the subset of the plurality of TCI states.

Aspect 9: The method of any of aspects 5–8, wherein the rule defines that a TCI state associated with a lowest TCI state identifier, of a subset of the plurality of TCI states associated with a pathloss offset, is to be used for the random access message, and the first TCI state is associated with the lowest TCI state identifier of the subset of the plurality of TCI states.

Aspect 10: The method of any of aspects 5–9, wherein the rule defines the TCI state selection criterion for PDCCH-ordered random access message transmissions, and the random access message indicated by the second DCI message is a PDCCH-ordered random access message transmission.

Aspect 11: The method of any of aspects 4–10, wherein receiving the second DCI message includes: receiving information indicative of the first TCI state via the second DCI message, wherein transmitting the random access message in accordance with the first TCI state is in association with receiving the information indicative of the first TCI state via the second DCI message.

Aspect 12: The method of aspect 11, wherein a field of the second DCI message includes the information indicative of the first TCI state.

Aspect 13: The method of aspect 12, wherein the field includes one or more bits, a first codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with the first TCI state and a second codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with a second TCI state of the plurality of TCI states, and the one or more bits indicate the first codepoint.

Aspect 14: The method of any of aspects 12–13, wherein the field is a TCI selection field of the second DCI message.

Aspect 15: The method of any of aspects 12–14, wherein the field is a PRACH association indicator field of the second DCI message.

Aspect 16: The method of any of aspects 4–15, further including: receiving control signaling that indicates that the UE is to transmit the random access message in accordance with the first TCI state, wherein transmitting the random access message in accordance with the first TCI state is in association with receiving the control signaling.

Aspect 17: The method of aspect 16, wherein the control signaling includes one or more RRC information elements that indicate that the UE is to transmit the random access message in accordance with the first TCI state.

Aspect 18: The method of any of aspects 1–17, further including: determining whether to transmit the random access message in accordance with the first TCI state in accordance with a presence of at least one indicated TCI state or an absence of at least one indicated TCI state at a transmission time associated with the random access message, wherein transmitting the random access message in accordance with the first TCI state is in association with determining whether to transmit the random access message in accordance with the first TCI state.

Aspect 19: The method of aspect 18, wherein the presence of at least one indicated TCI state at the transmission time associated with the random access message indicates that the UE is to transmit the random access message in accordance with the first TCI state, and the absence of at least one indicated TCI state at the transmission time associated with the random access message indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion.

Aspect 20: The method of any of aspects 1–19, wherein receiving the second DCI message includes: receiving information indicative of whether the UE is to transmit the random access message in accordance with the first TCI state, wherein transmitting the random access message in accordance with the first TCI state is in association with receiving the information.

Aspect 21: The method of aspect 20, wherein a field of the second DCI message includes the information indicative of whether the UE is to transmit the random access message in accordance with the first TCI state.

Aspect 22: The method of aspect 21, wherein the field includes one or more bits, a first codepoint associated with the one or more bits indicates that random access message transmissions in accordance with an indicated TCI state are enabled and a second codepoint associated with the one or more bits indicates that random access message transmissions in accordance with the indicated TCI state are disabled, and the one or more bits indicate the first codepoint.

Aspect 23: The method of aspect 22, wherein the field is a dedicated field of the second DCI message that is associated with enabling or disabling use of the indicated TCI state for random access message transmissions.

Aspect 24: The method of any of aspects 21–23, wherein the field includes one or more bits, a first codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with the first TCI state and a second codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion, and the one or more bits indicate the first codepoint.

Aspect 25: The method of aspect 24, wherein the field is a PRACH association indicator field of the second DCI message.

Aspect 26: The method of any of aspects 21–25, wherein the field includes a plurality of bits, a first codepoint associated with the plurality of bits indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion, a second codepoint associated with the plurality of bits indicates that the UE is to transmit the random access message in accordance with the first TCI state, and a third codepoint associated with the plurality of bits indicates that the UE is to transmit the random access message in accordance with a second TCI state of the plurality of TCI states, and the plurality of bits indicates the second codepoint.

Aspect 27: The method of aspect 26, wherein the field is a TCI selection field of the second DCI message.

Aspect 28: The method of any of aspects 1–27, wherein the first TCI state is associated with a pathloss offset, and wherein transmitting the random access message includes: transmitting the random access message using a transmission power that is associated with the pathloss offset associated with the first TCI state.

Aspect 29: The method of any of aspects 1–28, wherein transmitting the random access message includes: transmitting the random access message using a transmission beam associated with a source reference signal that is associated with the first TCI state.

Aspect 30: The method of any of aspects 1–29, further including: transmitting information indicative of a capability of the UE to perform random access message transmissions in accordance with an indicated TCI state, wherein transmitting the random access message in accordance with the first TCI state is in association with transmitting the information indicative of the capability of the UE.

Aspect 31: A method for wireless communication at a network entity, including: outputting, to a UE, a first DCI message including an indication of one or more transmission configuration indication (TCI) states; outputting, to the UE, a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion; and obtaining the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states.

Aspect 32: The method of aspect 31, wherein outputting the first DCI message includes: outputting an indication of a single TCI state, wherein the one or more TCI states consists of the single TCI state, and wherein the first TCI state is the single TCI state.

Aspect 33: The method of aspect 32, wherein the network entity obtains the random access message in accordance with the single TCI state in accordance with a rule defining that the UE is to use an indicated TCI state for the random access message indicated by the second DCI message.

Aspect 34: The method of any of aspects 31–33, wherein outputting the first DCI message includes: outputting an indication of a plurality of TCI states via the first DCI message, wherein the one or more TCI states include the plurality of TCI states, and wherein the plurality of TCI states includes the first TCI state.

Aspect 35: The method of aspect 34, further including: generating the first DCI message in accordance with a rule defining a TCI state selection criterion associated with the random access message indicated by the second DCI message, wherein transmitting the first DCI message is in association with generating the first DCI message.

Aspect 36: The method of aspect 35, wherein the rule defines that an initially indicated TCI state, of the plurality of TCI states, is to be used for the random access message, and the first TCI state is the initially indicated TCI state of the plurality of TCI states.

Aspect 37: The method of any of aspects 35–36, wherein the rule defines that a TCI state associated with a lowest TCI state identifier, of the plurality of TCI states, is to be used for the random access message, and the first TCI state is associated with the lowest TCI state identifier of the plurality of TCI states.

Aspect 38: The method of any of aspects 35–37, wherein the rule defines that an initially indicated TCI state, of a subset of the plurality of TCI states associated with a pathloss offset, is to be used for the random access message, and the first TCI state is the initially indicated TCI state of the subset of the plurality of TCI states.

Aspect 39: The method of any of aspects 35–38, wherein the rule defines that a TCI state associated with a lowest TCI state identifier, of a subset of the plurality of TCI states associated with a pathloss offset, is to be used for the random access message, and the first TCI state is associated with the lowest TCI state identifier of the subset of the plurality of TCI states.

Aspect 40: The method of any of aspects 35–39, wherein the rule defines the TCI state selection criterion for PDCCH-ordered random access message transmissions, and the random access message indicated by the second DCI message is a PDCCH-ordered random access message transmission.

Aspect 41: The method of any of aspects 34–40, wherein outputting the second DCI message includes: outputting information indicative of the first TCI state via the second DCI message, wherein obtaining the random access message in accordance with the first TCI state is in association with outputting the information indicative of the first TCI state via the second DCI message.

Aspect 42: The method of aspect 41, wherein a field of the second DCI message includes the information indicative of the first TCI state.

Aspect 43: The method of aspect 42, wherein the field includes one or more bits, a first codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with the first TCI state and a second codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with a second TCI state of the plurality of TCI states, and the one or more bits indicate the first codepoint.

Aspect 44: The method of any of aspects 42–43, wherein the field is a TCI selection field of the second DCI message.

Aspect 45: The method of any of aspects 42–44, wherein the field is a PRACH association indicator field of the second DCI message.

Aspect 46: The method of any of aspects 34–45, further including: outputting control signaling that indicates that the UE is to transmit the random access message in accordance with the first TCI state, wherein obtaining the random access message in accordance with the first TCI state is in association with outputting the control signaling.

Aspect 47: The method of aspect 46, wherein the control signaling includes one or more RRC information elements that indicate that the UE is to transmit the random access message in accordance with the first TCI state.

Aspect 48: The method of any of aspects 31–47, further including: determining whether to obtain the random access message in accordance with the first TCI state in accordance with a presence of at least one indicated TCI state or an absence of at least one indicated TCI state at a transmission time associated with the random access message, wherein obtaining the random access message in accordance with the first TCI state is in association with determining whether to obtain the random access message in accordance with the first TCI state.

Aspect 49: The method of aspect 48, wherein the presence of at least one indicated TCI state at the transmission time associated with the random access message indicates that the UE is to transmit the random access message in accordance with the first TCI state, and the absence of at least one indicated TCI state at the transmission time associated with the random access message indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion.

Aspect 50: The method of any of aspects 31–49, wherein outputting the second DCI message includes: outputting information indicative of whether the UE is to transmit the random access message in accordance with the first TCI state, wherein obtaining the random access message in accordance with the first TCI state is in association with outputting the information.

Aspect 51: The method of aspect 50, wherein a field of the second DCI message includes the information indicative of whether the UE is to transmit the random access message in accordance with the first TCI state.

Aspect 52: The method of aspect 51, wherein the field includes one or more bits, a first codepoint associated with the one or more bits indicates that random access message transmissions in accordance with an indicated TCI state are enabled and a second codepoint associated with the one or more bits indicates that random access message transmissions in accordance with the indicated TCI state are disabled, and the one or more bits indicate the first codepoint.

Aspect 53: The method of aspect 52, wherein the field is a dedicated field of the second DCI message that is associated with enabling or disabling use of the indicated TCI state for random access message transmissions.

Aspect 54: The method of any of aspects 51–53, wherein the field includes one or more bits, a first codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with the first TCI state and a second codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion, and the one or more bits indicate the first codepoint.

Aspect 55: The method of aspect 54, wherein the field is a PRACH association indicator field of the second DCI message.

Aspect 56: The method of any of aspects 51–55, wherein the field includes a plurality of bits, a first codepoint associated with the plurality of bits indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion, a second codepoint associated with the plurality of bits indicates that the UE is to transmit the random access message in accordance with the first TCI state, and a third codepoint associated with the plurality of bits indicates that the UE is to transmit the random access message in accordance with a second TCI state of the plurality of TCI states, and the plurality of bits indicates the second codepoint.

Aspect 57: The method of aspect 56, wherein the field is a TCI selection field of the second DCI message.

Aspect 58: The method of any of aspects 31–57, further including: obtaining information indicative of a capability of the UE to perform random access message transmissions in accordance with an indicated TCI state, wherein obtaining the random access message in accordance with the first TCI state is in association with obtaining the information indicative of the capability of the UE.

Aspect 59: A UE for wireless communication, including one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 1–30.

Aspect 60: A UE for wireless communication, including a processing system that includes processor circuitry and memory circuitry that stores code, the processing system configured to cause the UE to perform a method of any of aspects 1–30.

Aspect 61: A UE for wireless communication, including at least one means for performing a method of any of aspects 1–30.

Aspect 62: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform a method of any of aspects 1–30.

Aspect 63: A network entity for wireless communication, including one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 31–58.

Aspect 64: A network entity for wireless communication, including a processing system that includes processor circuitry and memory circuitry that stores code, the processing system configured to cause the network entity to perform a method of any of aspects 31–58.

Aspect 65: A network entity for wireless communication, including at least one means for performing a method of any of aspects 31–58.

Aspect 66: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform a method of any of aspects 31–58.

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

Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications 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, as well as other systems and radio technologies not explicitly mentioned herein.

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

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, a graphics processing unit (GPU) , a neural processing unit (NPU) , 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 also may be implemented as a combination of computing devices (such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration) . Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.

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 or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions also may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.

As used herein, including in the claims, “or” as used in a list of items (such as a list of items prefaced by a phrase such as “at least one of” or “one or more of” ) indicates an inclusive list such 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 (Aand B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. ”

As used herein, including in the claims, the article “a” before a noun is open-ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. For example, if a claim recites “acomponent” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “acomponent” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components, ” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ”

The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database, or another data structure) , ascertaining, and the like. Also, “determining” can include receiving (such as receiving information) , accessing (such as accessing data stored in memory) , and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label or other subsequent reference label.

The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration” and not “preferred” or “advantageous over other examples. ” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some figures, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

A user equipment (UE) , comprising:

a processing system that includes processor circuitry and memory circuitry that stores code, the processing system configured to cause the UE to:

receive a first downlink control information (DCI) message including an indication of one or more transmission configuration indication (TCI) states;

receive a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion; and

transmit the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states.
The UE of claim 1, wherein, to receive the first DCI message, the processing system is configured to cause the UE to:

receive an indication of a single TCI state, wherein the one or more TCI states consists of the single TCI state, and wherein the first TCI state is the single TCI state.
The UE of claim 2, wherein the UE transmits the random access message in accordance with the single TCI state in accordance with a rule defining that the UE is to use an indicated TCI state for the random access message indicated by the second DCI message.
The UE of claim 1, wherein, to receive the first DCI message, the processing system is configured to cause the UE to:

receive an indication of a plurality of TCI states via the first DCI message, wherein the one or more TCI states include the plurality of TCI states, and wherein the plurality of TCI states includes the first TCI state.
The UE of claim 4, wherein the processing system is further configured to cause the UE to:

select the first TCI state from the plurality of TCI states in accordance with a rule defining a TCI state selection criterion associated with the random access message indicated by the second DCI message, wherein transmitting the random access message in accordance with the first TCI state is in association with selecting the first TCI state.
The UE of claim 5, wherein:

the rule defines that an initially indicated TCI state, of the plurality of TCI states, is to be used for the random access message, and

the first TCI state is the initially indicated TCI state of the plurality of TCI states.
The UE of claim 5, wherein:

the rule defines that a TCI state associated with a lowest TCI state identifier, of the plurality of TCI states, is to be used for the random access message, and

the first TCI state is associated with the lowest TCI state identifier of the plurality of TCI states.
The UE of claim 5, wherein:

the rule defines that an initially indicated TCI state, of a subset of the plurality of TCI states associated with a pathloss offset, is to be used for the random access message, and

the first TCI state is the initially indicated TCI state of the subset of the plurality of TCI states.
The UE of claim 5, wherein:

the rule defines that a TCI state associated with a lowest TCI state identifier, of a subset of the plurality of TCI states associated with a pathloss offset, is to be used for the random access message, and

the first TCI state is associated with the lowest TCI state identifier of the subset of the plurality of TCI states.
The UE of claim 5, wherein:

the rule defines the TCI state selection criterion for physical downlink control channel (PDCCH) -ordered random access message transmissions, and

the random access message indicated by the second DCI message is a PDCCH-ordered random access message transmission.
The UE of claim 4, wherein, to receive the second DCI message, the processing system is configured to cause the UE to:

receive information indicative of the first TCI state via the second DCI message, wherein transmitting the random access message in accordance with the first TCI state is in association with receiving the information indicative of the first TCI state via the second DCI message.
The UE of claim 11, wherein a field of the second DCI message includes the information indicative of the first TCI state.
The UE of claim 12, wherein:

the field includes one or more bits,

a first codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with the first TCI state and a second codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with a second TCI state of the plurality of TCI states, and

the one or more bits indicate the first codepoint.
The UE of claim 12, wherein the field is a TCI selection field of the second DCI message.
The UE of claim 12, wherein the field is a PRACH association indicator field of the second DCI message.
The UE of claim 4, wherein the processing system is further configured to cause the UE to:

receive control signaling that indicates that the UE is to transmit the random access message in accordance with the first TCI state, wherein transmitting the random access message in accordance with the first TCI state is in association with receiving the control signaling.
The UE of claim 16, wherein the control signaling includes one or more radio resource control (RRC) information elements that indicate that the UE is to transmit the random access message in accordance with the first TCI state.
The UE of claim 1, wherein the processing system is further configured to cause the UE to:

determine whether to transmit the random access message in accordance with the first TCI state in accordance with a presence of at least one indicated TCI state or an absence of at least one indicated TCI state at a transmission time associated with the random access message, wherein transmitting the random access message in accordance with the first TCI state is in association with determining whether to transmit the random access message in accordance with the first TCI state.
The UE of claim 18, wherein:

the presence of at least one indicated TCI state at the transmission time associated with the random access message indicates that the UE is to transmit the random access message in accordance with the first TCI state, and

the absence of at least one indicated TCI state at the transmission time associated with the random access message indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion.
The UE of claim 1, wherein, to receive the second DCI message, the processing system is configured to cause the UE to:

receive information indicative of whether the UE is to transmit the random access message in accordance with the first TCI state, wherein transmitting the random access message in accordance with the first TCI state is in association with receiving the information.
The UE of claim 20, wherein a field of the second DCI message includes the information indicative of whether the UE is to transmit the random access message in accordance with the first TCI state.
The UE of claim 21, wherein:

the field includes one or more bits,

a first codepoint associated with the one or more bits indicates that random access message transmissions in accordance with an indicated TCI state are enabled and a second codepoint associated with the one or more bits indicates that random access message transmissions in accordance with the indicated TCI state are disabled, and

the one or more bits indicate the first codepoint.
The UE of claim 22, wherein the field is a dedicated field of the second DCI message that is associated with enabling or disabling use of the indicated TCI state for random access message transmissions.
The UE of claim 21, wherein:

the field includes one or more bits,

a first codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with the first TCI state and a second codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion, and

the one or more bits indicate the first codepoint.
The UE of claim 24, wherein the field is a PRACH association indicator field of the second DCI message.
The UE of claim 21, wherein:

the field includes a plurality of bits,

a first codepoint associated with the plurality of bits indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion, a second codepoint associated with the plurality of bits indicates that the UE is to transmit the random access message in accordance with the first TCI state, and a third codepoint associated with the plurality of bits indicates that the UE is to transmit the random access message in accordance with a second TCI state of the plurality of TCI states, and

the plurality of bits indicates the second codepoint.
The UE of claim 26, wherein the field is a TCI selection field of the second DCI message.
The UE of claim 1, wherein, to transmit the random access message, the processing system is configured to cause the UE to:

transmit the random access message using a transmission power that is associated with the pathloss offset associated with the first TCI state.
The UE of claim 1, wherein, to transmit the random access message, the processing system is configured to cause the UE to:

transmit the random access message using a transmission beam associated with a source reference signal that is associated with the first TCI state.
The UE of claim 1, wherein the processing system is further configured to cause the UE to:

transmit information indicative of a capability of the UE to perform random access message transmissions in accordance with an indicated TCI state, wherein transmitting the random access message in accordance with the first TCI state is in association with transmitting the information indicative of the capability of the UE.
A network entity, comprising:

a processing system that includes processor circuitry and memory circuitry that stores code, the processing system configured to cause the network entity to:

output, to a user equipment (UE) , a first downlink control information (DCI) message including an indication of one or more transmission configuration indication (TCI) states;

output, to the UE, a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion; and

obtain the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states.
The network entity of claim 31, wherein, to output the first DCI message, the processing system is configured to cause the network entity to:

output an indication of a single TCI state, wherein the one or more TCI states consists of the single TCI state, and wherein the first TCI state is the single TCI state.
The network entity of claim 32, wherein the network entity obtains the random access message in accordance with the single TCI state in accordance with a rule defining that the UE is to use an indicated TCI state for the random access message indicated by the second DCI message.
The network entity of claim 31, wherein, to output the first DCI message, the processing system is configured to cause the network entity to:

output an indication of a plurality of TCI states via the first DCI message, wherein the one or more TCI states include the plurality of TCI states, and wherein the plurality of TCI states includes the first TCI state.
The network entity of claim 34, wherein the processing system is further configured to cause the network entity to:

generate the first DCI message in accordance with a rule defining a TCI state selection criterion associated with the random access message indicated by the second DCI message, wherein transmitting the first DCI message is in association with generating the first DCI message.
The network entity of claim 35, wherein:

the rule defines that an initially indicated TCI state, of the plurality of TCI states, is to be used for the random access message, and

the first TCI state is the initially indicated TCI state of the plurality of TCI states.
The network entity of claim 35, wherein:

the rule defines that a TCI state associated with a lowest TCI state identifier, of the plurality of TCI states, is to be used for the random access message, and

the first TCI state is associated with the lowest TCI state identifier of the plurality of TCI states.
The network entity of claim 35, wherein:

the rule defines that an initially indicated TCI state, of a subset of the plurality of TCI states associated with a pathloss offset, is to be used for the random access message, and

the first TCI state is the initially indicated TCI state of the subset of the plurality of TCI states.
The network entity of claim 35, wherein:

the rule defines that a TCI state associated with a lowest TCI state identifier, of a subset of the plurality of TCI states associated with a pathloss offset, is to be used for the random access message, and

the first TCI state is associated with the lowest TCI state identifier of the subset of the plurality of TCI states.
The network entity of claim 35, wherein:

the rule defines the TCI state selection criterion for physical downlink control channel (PDCCH) -ordered random access message transmissions, and

the random access message indicated by the second DCI message is a PDCCH-ordered random access message transmission.
The network entity of claim 34, wherein, to output the second DCI message, the processing system is configured to cause the network entity to:

output information indicative of the first TCI state via the second DCI message, wherein obtaining the random access message in accordance with the first TCI state is in association with outputting the information indicative of the first TCI state via the second DCI message.
The network entity of claim 41, wherein a field of the second DCI message includes the information indicative of the first TCI state.
The network entity of claim 42, wherein:

the field includes one or more bits,

a first codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with the first TCI state and a second codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with a second TCI state of the plurality of TCI states, and

the one or more bits indicate the first codepoint.
The network entity of claim 42, wherein the field is a TCI selection field of the second DCI message.
The network entity of claim 42, wherein the field is a PRACH association indicator field of the second DCI message.
The network entity of claim 34, wherein the processing system is further configured to cause the network entity to:

output control signaling that indicates that the UE is to transmit the random access message in accordance with the first TCI state, wherein obtaining the random access message in accordance with the first TCI state is in association with outputting the control signaling.
The network entity of claim 46, wherein the control signaling includes one or more radio resource control (RRC) information elements that indicate that the UE is to transmit the random access message in accordance with the first TCI state.
The network entity of claim 31, wherein the processing system is further configured to cause the network entity to:

determine whether to obtain the random access message in accordance with the first TCI state in accordance with a presence of at least one indicated TCI state or an absence of at least one indicated TCI state at a transmission time associated with the random access message, wherein obtaining the random access message in accordance with the first TCI state is in association with determining whether to obtain the random access message in accordance with the first TCI state.
The network entity of claim 48, wherein:

the presence of at least one indicated TCI state at the transmission time associated with the random access message indicates that the UE is to transmit the random access message in accordance with the first TCI state, and

the absence of at least one indicated TCI state at the transmission time associated with the random access message indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion.
The network entity of claim 31, wherein, to output the second DCI message, the processing system is configured to cause the network entity to:

output information indicative of whether the UE is to transmit the random access message in accordance with the first TCI state, wherein obtaining the random access message in accordance with the first TCI state is in association with outputting the information.
The network entity of claim 50, wherein a field of the second DCI message includes the information indicative of whether the UE is to transmit the random access message in accordance with the first TCI state.
The network entity of claim 51, wherein:

the field includes one or more bits,

a first codepoint associated with the one or more bits indicates that random access message transmissions in accordance with an indicated TCI state are enabled and a second codepoint associated with the one or more bits indicates that random access message transmissions in accordance with the indicated TCI state are disabled, and

the one or more bits indicate the first codepoint.
The network entity of claim 52, wherein the field is a dedicated field of the second DCI message that is associated with enabling or disabling use of the indicated TCI state for random access message transmissions.
The network entity of claim 51, wherein:

the field includes one or more bits,

a first codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with the first TCI state and a second codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion, and

the one or more bits indicate the first codepoint.
The network entity of claim 54, wherein the field is a PRACH association indicator field of the second DCI message.
The network entity of claim 51, wherein:

the field includes a plurality of bits,

a first codepoint associated with the plurality of bits indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion, a second codepoint associated with the plurality of bits indicates that the UE is to transmit the random access message in accordance with the first TCI state, and a third codepoint associated with the plurality of bits indicates that the UE is to transmit the random access message in accordance with a second TCI state of the plurality of TCI states, and

the plurality of bits indicates the second codepoint.
The network entity of claim 56, wherein the field is a TCI selection field of the second DCI message.
The network entity of claim 31, wherein the processing system is further configured to cause the network entity to:

obtain information indicative of a capability of the UE to perform random access message transmissions in accordance with an indicated TCI state, wherein obtaining the random access message in accordance with the first TCI state is in association with obtaining the information indicative of the capability of the UE.
A method for wireless communication at a user equipment (UE) , comprising:

receiving a first downlink control information (DCI) message including an indication of one or more transmission configuration indication (TCI) states;

receiving a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion; and

transmitting the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states.
The method of claim 59, wherein receiving the first DCI message comprises:

receiving an indication of a single TCI state, wherein the one or more TCI states consists of the single TCI state, and wherein the first TCI state is the single TCI state.
The method of claim 60, wherein the UE transmits the random access message in accordance with the single TCI state in accordance with a rule defining that the UE is to use an indicated TCI state for the random access message indicated by the second DCI message.
The method of claim 59, wherein receiving the first DCI message comprises:

receiving an indication of a plurality of TCI states via the first DCI message, wherein the one or more TCI states include the plurality of TCI states, and wherein the plurality of TCI states includes the first TCI state.
The method of claim 62, further comprising:

selecting the first TCI state from the plurality of TCI states in accordance with a rule defining a TCI state selection criterion associated with the random access message indicated by the second DCI message, wherein transmitting the random access message in accordance with the first TCI state is in association with selecting the first TCI state.
The method of claim 63, wherein

the rule defines that an initially indicated TCI state, of the plurality of TCI states, is to be used for the random access message, and

the first TCI state is the initially indicated TCI state of the plurality of TCI states.
The method of claim 63, wherein

the rule defines that a TCI state associated with a lowest TCI state identifier, of the plurality of TCI states, is to be used for the random access message, and

the first TCI state is associated with the lowest TCI state identifier of the plurality of TCI states.
The method of claim 63, wherein

the rule defines that an initially indicated TCI state, of a subset of the plurality of TCI states associated with a pathloss offset, is to be used for the random access message, and

the first TCI state is the initially indicated TCI state of the subset of the plurality of TCI states.
The method of claim 63, wherein

the rule defines that a TCI state associated with a lowest TCI state identifier, of a subset of the plurality of TCI states associated with a pathloss offset, is to be used for the random access message, and

the first TCI state is associated with the lowest TCI state identifier of the subset of the plurality of TCI states.
The method of claim 63, wherein

the rule defines the TCI state selection criterion for physical downlink control channel (PDCCH) -ordered random access message transmissions, and

the random access message indicated by the second DCI message is a PDCCH-ordered random access message transmission.
The method of claim 62, wherein receiving the second DCI message comprises:

receiving information indicative of the first TCI state via the second DCI message, wherein transmitting the random access message in accordance with the first TCI state is in association with receiving the information indicative of the first TCI state via the second DCI message.
The method of claim 69, wherein a field of the second DCI message includes the information indicative of the first TCI state.
The method of claim 70, wherein

the field includes one or more bits,

a first codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with the first TCI state and a second codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with a second TCI state of the plurality of TCI states, and

the one or more bits indicate the first codepoint.
The method of claim 70, wherein the field is a TCI selection field of the second DCI message.
The method of claim 70, wherein the field is a PRACH association indicator field of the second DCI message.
The method of claim 62, further comprising:

receiving control signaling that indicates that the UE is to transmit the random access message in accordance with the first TCI state, wherein transmitting the random access message in accordance with the first TCI state is in association with receiving the control signaling.
The method of claim 74, wherein the control signaling includes one or more radio resource control (RRC) information elements that indicate that the UE is to transmit the random access message in accordance with the first TCI state.
The method of claim 59, further comprising:

determining whether to transmit the random access message in accordance with the first TCI state in accordance with a presence of at least one indicated TCI state or an absence of at least one indicated TCI state at a transmission time associated with the random access message, wherein transmitting the random access message in accordance with the first TCI state is in association with determining whether to transmit the random access message in accordance with the first TCI state.
The method of claim 76, wherein

the presence of at least one indicated TCI state at the transmission time associated with the random access message indicates that the UE is to transmit the random access message in accordance with the first TCI state, and

the absence of at least one indicated TCI state at the transmission time associated with the random access message indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion.
The method of claim 59, wherein receiving the second DCI message comprises:

receiving information indicative of whether the UE is to transmit the random access message in accordance with the first TCI state, wherein transmitting the random access message in accordance with the first TCI state is in association with receiving the information.
The method of claim 78, wherein a field of the second DCI message includes the information indicative of whether the UE is to transmit the random access message in accordance with the first TCI state.
The method of claim 79, wherein

the field includes one or more bits,

a first codepoint associated with the one or more bits indicates that random access message transmissions in accordance with an indicated TCI state are enabled and a second codepoint associated with the one or more bits indicates that random access message transmissions in accordance with the indicated TCI state are disabled, and

the one or more bits indicate the first codepoint.
The method of claim 80, wherein the field is a dedicated field of the second DCI message that is associated with enabling or disabling use of the indicated TCI state for random access message transmissions.
The method of claim 79, wherein

the field includes one or more bits,

a first codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with the first TCI state and a second codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion, and

the one or more bits indicate the first codepoint.
The method of claim 82, wherein the field is a PRACH association indicator field of the second DCI message.
The method of claim 79, wherein

the field includes a plurality of bits,

a first codepoint associated with the plurality of bits indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion, a second codepoint associated with the plurality of bits indicates that the UE is to transmit the random access message in accordance with the first TCI state, and a third codepoint associated with the plurality of bits indicates that the UE is to transmit the random access message in accordance with a second TCI state of the plurality of TCI states, and

the plurality of bits indicates the second codepoint.
The method of claim 84, wherein the field is a TCI selection field of the second DCI message.
The method of claim 59, wherein the first TCI state is associated with a pathloss offset, and wherein transmitting the random access message comprises:

transmitting the random access message using a transmission power that is associated with the pathloss offset associated with the first TCI state.
The method of claim 59, wherein transmitting the random access message comprises:

transmitting the random access message using a transmission beam associated with a source reference signal that is associated with the first TCI state.
The method of claim 59, further comprising:

transmitting information indicative of a capability of the UE to perform random access message transmissions in accordance with an indicated TCI state, wherein transmitting the random access message in accordance with the first TCI state is in association with transmitting the information indicative of the capability of the UE.
A method for wireless communication at a network entity, comprising:

outputting, to a user equipment (UE) , a first downlink control information (DCI) message including an indication of one or more transmission configuration indication (TCI) states;

outputting, to the UE, a second DCI message indicating the UE to transmit a random access message via a physical random access channel (PRACH) occasion; and

obtaining the random access message via the PRACH occasion in accordance with a first TCI state of the one or more TCI states.
The method of claim 89, wherein outputting the first DCI message comprises:

outputting an indication of a single TCI state, wherein the one or more TCI states consists of the single TCI state, and wherein the first TCI state is the single TCI state.
The method of claim 90, wherein the network entity obtains the random access message in accordance with the single TCI state in accordance with a rule defining that the UE is to use an indicated TCI state for the random access message indicated by the second DCI message.
The method of claim 89, wherein outputting the first DCI message comprises:

outputting an indication of a plurality of TCI states via the first DCI message, wherein the one or more TCI states include the plurality of TCI states, and wherein the plurality of TCI states includes the first TCI state.
The method of claim 92, further comprising:

generating the first DCI message in accordance with a rule defining a TCI state selection criterion associated with the random access message indicated by the second DCI message, wherein transmitting the first DCI message is in association with generating the first DCI message.
The method of claim 93, wherein

the rule defines that an initially indicated TCI state, of the plurality of TCI states, is to be used for the random access message, and

the first TCI state is the initially indicated TCI state of the plurality of TCI states.
The method of claim 93, wherein

the rule defines that a TCI state associated with a lowest TCI state identifier, of the plurality of TCI states, is to be used for the random access message, and

the first TCI state is associated with the lowest TCI state identifier of the plurality of TCI states.
The method of claim 93, wherein

the rule defines that an initially indicated TCI state, of a subset of the plurality of TCI states associated with a pathloss offset, is to be used for the random access message, and

the first TCI state is the initially indicated TCI state of the subset of the plurality of TCI states.
The method of claim 93, wherein

the rule defines that a TCI state associated with a lowest TCI state identifier, of a subset of the plurality of TCI states associated with a pathloss offset, is to be used for the random access message, and

the first TCI state is associated with the lowest TCI state identifier of the subset of the plurality of TCI states.
The method of claim 93, wherein

the rule defines the TCI state selection criterion for physical downlink control channel (PDCCH) -ordered random access message transmissions, and

the random access message indicated by the second DCI message is a PDCCH-ordered random access message transmission.
The method of claim 92, wherein outputting the second DCI message comprises:

outputting information indicative of the first TCI state via the second DCI message, wherein obtaining the random access message in accordance with the first TCI state is in association with outputting the information indicative of the first TCI state via the second DCI message.
The method of claim 99, wherein a field of the second DCI message includes the information indicative of the first TCI state.
The method of claim 100, wherein

the field includes one or more bits,

a first codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with the first TCI state and a second codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with a second TCI state of the plurality of TCI states, and

the one or more bits indicate the first codepoint.
The method of claim 100, wherein the field is a TCI selection field of the second DCI message.
The method of claim 100, wherein the field is a PRACH association indicator field of the second DCI message.
The method of claim 92, further comprising:

outputting control signaling that indicates that the UE is to transmit the random access message in accordance with the first TCI state, wherein obtaining the random access message in accordance with the first TCI state is in association with outputting the control signaling.
The method of claim 104, wherein the control signaling includes one or more radio resource control (RRC) information elements that indicate that the UE is to transmit the random access message in accordance with the first TCI state.
The method of claim 89, further comprising:

determining whether to obtain the random access message in accordance with the first TCI state in accordance with a presence of at least one indicated TCI state or an absence of at least one indicated TCI state at a transmission time associated with the random access message, wherein obtaining the random access message in accordance with the first TCI state is in association with determining whether to obtain the random access message in accordance with the first TCI state.
The method of claim 106, wherein

the presence of at least one indicated TCI state at the transmission time associated with the random access message indicates that the UE is to transmit the random access message in accordance with the first TCI state, and

the absence of at least one indicated TCI state at the transmission time associated with the random access message indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion.
The method of claim 89, wherein outputting the second DCI message comprises:

outputting information indicative of whether the UE is to transmit the random access message in accordance with the first TCI state, wherein obtaining the random access message in accordance with the first TCI state is in association with outputting the information.
The method of claim 108, wherein a field of the second DCI message includes the information indicative of whether the UE is to transmit the random access message in accordance with the first TCI state.
The method of claim 109, wherein

the field includes one or more bits,

a first codepoint associated with the one or more bits indicates that random access message transmissions in accordance with an indicated TCI state are enabled and a second codepoint associated with the one or more bits indicates that random access message transmissions in accordance with the indicated TCI state are disabled, and

the one or more bits indicate the first codepoint.
The method of claim 110, wherein the field is a dedicated field of the second DCI message that is associated with enabling or disabling use of the indicated TCI state for random access message transmissions.
The method of claim 109, wherein

the field includes one or more bits,

a first codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with the first TCI state and a second codepoint associated with the one or more bits indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion, and

the one or more bits indicate the first codepoint.
The method of claim 112, wherein the field is a PRACH association indicator field of the second DCI message.
The method of claim 109, wherein

the field includes a plurality of bits,

a first codepoint associated with the plurality of bits indicates that the UE is to transmit the random access message in accordance with a downlink reference signal associated with the PRACH occasion, a second codepoint associated with the plurality of bits indicates that the UE is to transmit the random access message in accordance with the first TCI state, and a third codepoint associated with the plurality of bits indicates that the UE is to transmit the random access message in accordance with a second TCI state of the plurality of TCI states, and

the plurality of bits indicates the second codepoint.
The method of claim 114, wherein the field is a TCI selection field of the second DCI message.
The method of claim 89, further comprising:

obtaining information indicative of a capability of the UE to perform random access message transmissions in accordance with an indicated TCI state, wherein obtaining the random access message in accordance with the first TCI state is in association with obtaining the information indicative of the capability of the UE.