WO2025118216A1

WO2025118216A1 - Power headroom enhancement for dense uplink deployment

Info

Publication number: WO2025118216A1
Application number: PCT/CN2023/136986
Authority: WO
Inventors: Shaozhen GUO; Mostafa KHOSHNEVISAN; Xiaoxia Zhang
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2023-12-07
Filing date: 2023-12-07
Publication date: 2025-06-12
Anticipated expiration: 2026-06-07

Abstract

Methods, systems, and devices for wireless communications are described. A user equipment (UE) may receive a message indicating a trigger-based power headroom report status of the UE, the trigger-based power headroom report status indicating whether to enable transmission of a power headroom report triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold. The UE may selectively transmit the power headroom report in accordance with the trigger-based power headroom report status and the pathloss change on the at least one uplink carrier.

Description

POWER HEADROOM ENHANCEMENT FOR DENSE UPLINK DEPLOYMENT

FIELD OF TECHNOLOGY

The following relates to wireless communications, including power headroom enhancement for dense uplink deployment.

BACKGROUND

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 (e.g., 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) .

SUMMARY

The described techniques relate to improved methods, systems, devices, and apparatuses that support power headroom enhancement for dense uplink deployment. In some aspects, the techniques described herein provide for enablement and/or disablement of a power headroom report (PHR) triggered for example based on (e.g., by) a threshold pathloss change. For example, a user equipment (UE) may receive a message that indicates a trigger-based PHR status of the UE. This status may be used to indicate whether to enable (or disable) transmission of a PHR that has been triggered based on the pathloss change on at least one uplink carrier satisfying a pathloss threshold. The UE may selectively transmit the PHR based on the trigger-based PHR status and the pathloss change on the uplink carrier. For example, the UE may transmit the PHR when the trigger-based PHR status enables transmission or may refrain from transmitting the PHR when the trigger-based PHR status disables transmission (e.g., upon detecting the pathloss change satisfying the pathloss threshold) .

In some aspects, the techniques described herein provide for transmitting an actual PHR report or a virtual PHR report on one or more additional uplink carriers. For example, the UE may transmit a PHR on a first uplink carrier of the UE during a slot, such as in a physical uplink shared channel (PUSCH) transmission. Additional PUSCH transmissions scheduled on a second uplink carrier of the UE may overlap in the time domain in the slot with the PUSCH transmission on the first uplink carrier. The UE may provide PHR value for the second uplink carrier of the UE during the slot. The PHR value may include the actual PHR or a virtual PHR. The UE may select between the actual or virtual PHR for the second uplink carrier based on, for example, the overlap in the time domain between the first uplink carrier PUSCH and second PUSCH transmission on the second uplink carrier, and/or based on, for example, the uplink transmission type used for the PUSCH transmission (s) on the second uplink carrier. The uplink transmission type may generally refer to a specified or specific uplink transmission type that may be identified based on, for example, the uplink transmission being associated with a downlink node or an uplink-only node, specified by the network, and other techniques.

In some aspects, the techniques described herein provide for different techniques to estimate the channel performance metrics when transmitting a virtual PHR. For example, the UE may select a virtual PHR for an uplink carrier. A power control parameter may be configured for the uplink carrier or based on the UE not being configured with a sounding reference signal (SRS) resource set, a physical uplink control channel (PUCCH) , a PUSCH, and/or a transmission configuration indicator (TCI) state, for the uplink carrier. The UE may compute or otherwise determine the virtual PHR value based on a set PUSCH reference parameters a pathloss offset or both. The virtual PHR may be based on, for example, a pathloss offset that is included along with the estimation of the channel performance metrics. That is, the pathloss offset may be configured or otherwise indicated to the UE, which the UE uses as part of the formula used to calculate the virtual PHR.

A method for wireless communications by a UE is described. The method may include receiving a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold and selectively transmitting the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier.

A UE for wireless communications is described. The UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively operable to execute the code to cause the UE to receive a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold and selectively transmit the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier.

Another UE for wireless communications is described. The UE may include means for receiving a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold and means for selectively transmitting the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier.

A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to receive a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold and selectively transmit the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the message includes a RRC 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 an indication of a power control parameter configured for at least one of a sounding reference signal (SRS) transmission, a PUCCH transmission, or a PUSCH transmission, where the trigger-based PHR status indicating whether to enable transmission of the PHR may be based on the power control parameter.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, the power control parameter includes at least one of a pathloss value or a pathloss offset.

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 an indication of a power control parameter configured for an uplink TCI state, where the trigger-based PHR status indicating whether to enable transmission of the PHR may be based on the power control parameter.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, receiving the message may include operations, features, means, or instructions for detecting whether a pathloss reference signal may be configured for at least one of: an SRS transmission, a PUCCH transmission, or an PUSCH transmission, where the trigger-based PHR status indicating whether to enable transmission of the PHR may be based on the detecting.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, receiving the message may include operations, features, means, or instructions for detecting whether a pathloss reference signal may be configured for an uplink TCI state, where the trigger-based PHR status indicating whether to enable transmission of the PHR may be based on the detecting.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, selectively transmitting the PHR may include operations, features, means, or instructions for transmitting the PHR based on the trigger-based PHR status indicating to enable transmission of the PHR and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold.

In some examples of the method, user equipment (UEs) , and non-transitory computer-readable medium described herein, selectively transmitting the PHR may include operations, features, means, or instructions for detecting that the pathloss change on the at least one uplink carrier may have satisfied the pathloss threshold and refraining from transmitting the PHR based on the trigger-based PHR status indicating to disable transmission of the PHR.

A method for wireless communications by a UE is described. The method may include transmitting a PHR in an PUSCH transmission on a first uplink carrier of the UE during a slot, where a set of PUSCH transmissions in a second uplink carrier overlap in a time domain in the slot with the PUSCH transmission on the first uplink carrier and providing a PHR value for the second uplink carrier of the UE, the PHR value for the second uplink carrier including an actual PHR or a virtual PHR, where selection of the actual PHR or the virtual PHR for the second uplink carrier is based on an uplink transmission type of each PUSCH transmission in the set of PUSCH transmissions.

A UE for wireless communications is described. The UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively operable to execute the code to cause the UE to transmit a PHR in an PUSCH transmission on a first uplink carrier of the UE during a slot, where a set of PUSCH transmissions in a second uplink carrier overlap in a time domain in the slot with the PUSCH transmission on the first uplink carrier and provide a PHR value for the second uplink carrier of the UE, the PHR value for the second uplink carrier including an actual PHR or a virtual PHR, where selection of the actual PHR or the virtual PHR for the second uplink carrier is based on an uplink transmission type of each PUSCH transmission in the set of PUSCH transmissions.

Another UE for wireless communications is described. The UE may include means for transmitting a PHR in an PUSCH transmission on a first uplink carrier of the UE during a slot, where a set of PUSCH transmissions in a second uplink carrier overlap in a time domain in the slot with the PUSCH transmission on the first uplink carrier and means for providing a PHR value for the second uplink carrier of the UE, the PHR value for the second uplink carrier including an actual PHR or a virtual PHR, where selection of the actual PHR or the virtual PHR for the second uplink carrier is based on an uplink transmission type of each PUSCH transmission in the set of PUSCH transmissions.

A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to transmit a PHR in an PUSCH transmission on a first uplink carrier of the UE during a slot, where a set of PUSCH transmissions in a second uplink carrier overlap in a time domain in the slot with the PUSCH transmission on the first uplink carrier and provide a PHR value for the second uplink carrier of the UE, the PHR value for the second uplink carrier including an actual PHR or a virtual PHR, where selection of the actual PHR or the virtual PHR for the second uplink carrier is based on an uplink transmission type of each PUSCH transmission in the set of PUSCH transmissions.

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 detecting that at least one PUSCH transmission in the set of PUSCH transmissions may be associated with a specific uplink transmission type and selecting the actual PHR for the second uplink carrier, where the actual PHR may be based on the at least one PUSCH transmission being a first PUSCH transmission in the set of PUSCH transmissions that may be associated with the specific uplink transmission type.

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 detecting that each PUSCH transmission in the set of PUSCH transmissions may be associated with a non-specific transmission type and selecting the actual PHR for the second uplink carrier based on the detecting, where the actual PHR may be based on a first PUSCH transmission in the set of PUSCH transmissions.

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 detecting that each PUSCH transmission in the set of PUSCH transmissions may be associated with a non-specific uplink transmission type and selecting the virtual PHR for the second uplink carrier based on the detecting.

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 detecting that a first PUSCH transmission in the set of PUSCH transmissions may be associated with a specific uplink transmission type and selecting the actual PHR for the second uplink carrier, where the actual PHR may be based on the first PUSCH transmission in the set of PUSCH transmissions.

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 detecting that a first PUSCH transmission in the set of PUSCH transmissions may be associated with a non-specific uplink transmission type and selecting the virtual PHR for the second uplink carrier based on the detecting.

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 detecting whether at least one PUSCH transmission in the set of PUSCH transmissions may be associated with a specific uplink transmission type based on a pathloss reference signal being associated with the at least one PUSCH transmission and on a non-configuration status for a pathloss or a pathloss offset associated with the at least one PUSCH transmission.

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 detecting whether at least one PUSCH transmission in the set of PUSCH transmissions may be associated with a specific uplink transmission type based on an uplink TCI state associated with the at least one PUSCH transmission, where the uplink TCI state may be associated with a downlink pathloss reference signal, a source downlink reference signal, a timing advance group identifier, any combination thereof.

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 detecting whether at least one PUSCH transmission in the set of PUSCH transmissions may be associated with a specific uplink transmission type based on a grant scheduling the at least one PUSCH transmission.

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 detecting whether at least one PUSCH transmission in the set of PUSCH transmissions may be associated with a specific uplink transmission type based on a pathloss, a pathloss offset, or both, being associated with the at least one PUSCH transmission.

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 detecting whether at least one PUSCH transmission in the set of PUSCH transmissions may be associated with a specific uplink transmission type based on an uplink TCI state associated with the at least one PUSCH transmission, where the uplink TCI state may be associated with a pathloss, a pathloss offset, an SRS resource, a timing advance group identifier, or any combination thereof.

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 an RRC message indicating a specific uplink transmission type.

A method for wireless communications by a UE is described. The method may include selecting a virtual PHR for an uplink carrier, where a power control parameter is configured for the uplink carrier or a pathloss reference signal non-configuration status exists for at least one of an SRS resource set, a PUCCH, an PUSCH, or a TCI state, or any combination thereof, for the uplink carrier and computing, based on the selecting, the virtual PHR based on a set of PUSCH reference parameters, a pathloss offset, or both.

A UE for wireless communications is described. The UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively operable to execute the code to cause the UE to select a virtual PHR for an uplink carrier, where a power control parameter is configured for the uplink carrier or a pathloss reference signal non-configuration status exists for at least one of an SRS resource set, a PUCCH, an PUSCH, or a TCI state, or any combination thereof, for the uplink carrier and computing, base at least in part on the selecting, the virtual PHR based on a set of PUSCH reference parameters, a pathloss offset, or both.

Another UE for wireless communications is described. The UE may include means for selecting a virtual PHR for an uplink carrier, where a power control parameter is configured for the uplink carrier or a pathloss reference signal non-configuration status exists for at least one of an SRS resource set, a PUCCH, an PUSCH, or a TCI state, or any combination thereof, for the uplink carrier and means for computing, based on the selecting, the virtual PHR based on a set of PUSCH reference parameters, a pathloss offset, or both.

A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to select a virtual PHR for an uplink carrier, where a power control parameter is configured for the uplink carrier or a pathloss reference signal non-configuration status exists for at least one of an SRS resource set, a PUCCH, an PUSCH, or a TCI state, or any combination thereof, for the uplink carrier and computing, base at least in part on the selecting, the virtual PHR based on a set of PUSCH reference parameters, a pathloss offset, or both.

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 identifying the pathloss offset based on at least one of a default pathloss reference signal identifier, a default P0 nominal power level, a default uplink TCI state, a default pathloss value, an indicated TCI state, or any combination thereof.

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 to use the pathloss offset for the virtual PHR based on an indicated TCI state of the UE, where the indicated TCI state may be associated with the pathloss offset.

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 to use the set of PUSCH reference parameters for the virtual PHR based on an indicated TCI state of the UE, where the pathloss offset may be in a non-configuration state for the indicated 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 receiving an RRC message indicating whether to use the pathloss offset for the virtual PHR.

A method for wireless communications by a UE is described. The method may include selecting an actual PHR or a virtual PHR for transmission in a first PUSCH transmission on an uplink carrier of the UE, the selecting based on a previously received grant that schedules a second PUSCH transmission that is associated with an uplink transmission type, where previously received grant is received prior to or during a physical downlink control channel (PDCCH) monitoring occasion where the UE detects a grant that schedules the first PUSCH transmission on the first uplink carrier and transmitting the actual PHR or the virtual PHR in the first PUSCH transmission on the uplink carrier of the UE in accordance with the selecting.

A UE for wireless communications is described. The UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively operable to execute the code to cause the UE to select an actual PHR or a virtual PHR for transmission in a first PUSCH transmission on an uplink carrier of the UE, the selecting based on a previously received grant that schedules a second PUSCH transmission that is associated with an uplink transmission type, where previously received grant is received prior to or during a PDCCH monitoring occasion where the UE detects a grant that schedules the first PUSCH transmission on the first uplink carrier and transmit the actual PHR or the virtual PHR in the first PUSCH transmission on the uplink carrier of the UE in accordance with the selecting.

Another UE for wireless communications is described. The UE may include means for selecting an actual PHR or a virtual PHR for transmission in a first PUSCH transmission on an uplink carrier of the UE, the selecting based on a previously received grant that schedules a second PUSCH transmission that is associated with an uplink transmission type, where previously received grant is received prior to or during a PDCCH monitoring occasion where the UE detects a grant that schedules the first PUSCH transmission on the first uplink carrier and means for transmitting the actual PHR or the virtual PHR in the first PUSCH transmission on the uplink carrier of the UE in accordance with the selecting.

A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to select an actual PHR or a virtual PHR for transmission in a first PUSCH transmission on an uplink carrier of the UE, the selecting based on a previously received grant that schedules a second PUSCH transmission that is associated with an uplink transmission type, where previously received grant is received prior to or during a PDCCH monitoring occasion where the UE detects a grant that schedules the first PUSCH transmission on the first uplink carrier and transmit the actual PHR or the virtual PHR in the first PUSCH transmission on the uplink carrier of the UE in accordance with the selecting.

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 actual PHR for transmission in the first PUSCH transmission based on the second PUSCH transmission being associated with a specific uplink transmission type, where the uplink transmission type includes the specific uplink transmission type.

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 virtual PHR for transmission in the first PUSCH transmission based on the second PUSCH transmission being associated with a non-specific uplink transmission type, where the uplink transmission type includes the non-specific uplink transmission type.

A method for wireless communications by a network entity is described. The method may include transmitting, to a UE, a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold and selectively receiving the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier.

A network entity for wireless communications is described. The network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively operable to execute the code to cause the network entity to transmit, to a UE, a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold and selectively receive the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier.

Another network entity for wireless communications is described. The network entity may include means for transmitting, to a UE, a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold and means for selectively receiving the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier.

A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to transmit, to a UE, a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold and selectively receive the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the message includes an RRC 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 transmitting an indication of a power control parameter configured for at least one of an SRS transmission, a PUCCH transmission, or an PUSCH transmission, where the trigger-based PHR status indicating whether to enable transmission of the PHR may be based on the power control parameter.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the power control parameter includes at least one of a pathloss value or a pathloss offset.

Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting an indication of a power control parameter configured for an uplink TCI state, where the trigger-based PHR status indicating whether to enable transmission of the PHR may be based on the power control parameter.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, receiving the message may include operations, features, means, or instructions for detecting whether a pathloss reference signal may be configured for at least one of: an SRS transmission, a PUCCH transmission, or an PUSCH transmission, where the trigger-based PHR status indicating whether to enable transmission of the PHR may be based on the detecting.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, transmitting the message may include operations, features, means, or instructions for detecting whether a pathloss reference signal may be configured for an uplink TCI state, where the trigger-based PHR status indicating whether to enable transmission of the PHR may be based on the detecting.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, selectively receiving the PHR may include operations, features, means, or instructions for receiving the PHR based on the trigger-based PHR status indicating to enable transmission of the PHR and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold.

In some examples of the method, network entities, and non-transitory computer-readable medium described herein, selectively receiving the PHR may include operations, features, means, or instructions for refraining from receiving the PHR based on the trigger-based PHR status indicating to disable transmission of the PHR.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example of a wireless communications system that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure.

FIG. 2 shows an example of a wireless communications system that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure.

FIGs. 3A and 3B show examples of a scheduling configuration that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure.

FIGs. 4A and 4B show examples of a scheduling configuration that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure.

FIGs. 5 and 6 show block diagrams of devices that support power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure.

FIG. 7 shows a block diagram of a communications manager that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure.

FIG. 8 shows a diagram of a system including a device that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure.

FIGs. 9 and 10 show block diagrams of devices that support power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure.

FIG. 11 shows a block diagram of a communications manager that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure.

FIG. 12 shows a diagram of a system including a device that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure.

FIGs. 13 through 17 show flowcharts illustrating methods that support power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure.

DETAILED DESCRIPTION

Wireless networks may use power headroom report (PHR) techniques for power-aware packet scheduling by a user equipment (UE) . The power headroom may indicate the amount of available transmit power that the UE has, such as a difference between the UE’s maximum transmit power and the transmit power being used for an uplink transmission. The uplink transmission may include a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, among other options. The power headroom is generally calculated based on a downlink reference signal (e.g., a dedicated pathloss reference signal or other reference signal) that is measured by the UE on a downlink carrier. Some network deployments, however, may include an uplink-only cell or a downlink-only cell where the cell is configured with an uplink (but no downlink) carrier or a downlink (but no uplink) carrier, respectively. However, triggering a PHR may be inefficient or ineffective when the downlink reference signal is associated with a downlink-only cell. That is, PHR techniques are used to report available transmit power for uplink transmissions on an uplink carrier, and a pathloss change on a downlink carrier that would normally trigger a PHR from the UE may be inappropriate when the downlink-only cell and the uplink-only cell are associated with different propagation paths.

Accordingly, the techniques described herein provide for enablement and/or disablement of a PHR triggered by a threshold pathloss change. For example, a UE may receive a message that indicates a trigger-based PHR status of the UE. This status may be used to indicate whether to enable (or disable) transmission of a PHR that has been triggered by the pathloss change on at least one uplink carrier satisfying a pathloss threshold. The UE may selectively transmit the PHR based on the trigger-based PHR status and the pathloss change on the uplink carrier. For example, the UE may transmit the PHR when the trigger-based PHR status enables transmission or may refrain from transmitting the PHR when the trigger-based PHR status disables transmission (e.g., upon detecting the pathloss change satisfying the pathloss threshold) .

In some aspects, the techniques described herein provide for transmitting an actual PHR report or a virtual PHR report on one or more additional uplink carriers. For example, the UE may transmit a PHR on a first uplink carrier of the UE during a slot, such as in a PUSCH transmission. Additional PUSCH transmissions scheduled on a second uplink carrier of the UE may overlap in the time domain in the slot with the PUSCH transmission on the first uplink carrier. The UE may provide PHR value for the second uplink carrier of the UE during the slot. The PHR value may include the actual PHR or a virtual PHR. The UE may select between the actual or virtual PHR for the second uplink carrier based on, for example, the overlap in the time domain between the first uplink carrier PUSCH and second PUSCH transmission on the second uplink carrier, as well as based on, for example, the uplink transmission type used for the PUSCH transmission (s) on the second uplink carrier. The uplink transmission type may generally refer to a specified or specific uplink transmission type that may be identified based on, for example, the uplink transmission being associated with a downlink node or an uplink-only node, specified by the network, and other techniques.

In some aspects, the techniques described herein provide for different techniques to estimate the channel performance metrics when transmitting a virtual PHR. For example, the UE may select a virtual PHR for an uplink carrier. A power control parameter may be configured for the uplink carrier or based on, for example, the UE not being configured with a SRS resource set, a PUCCH, a PUSCH, and/or a transmission configuration indicator (TCI) state, for the uplink carrier. The UE may compute or otherwise determine the virtual PHR value based on, for example, a set PUSCH reference parameters a pathloss offset or both. The virtual PHR may be based on, for example, a pathloss offset that is included along with the estimation of the channel performance metrics. That is, the pathloss offset may be configured or otherwise indicated to the UE, which the UE uses as part of the formula used to calculate the virtual PHR.

Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to power headroom enhancement for dense uplink deployment.

FIG. 1 shows an example of a wireless communications system 100 that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless 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 one or more communication links 125 (e.g., a radio frequency (RF) access link) . For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which 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 FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices, such as other UEs 115 or network entities 105, as shown in FIG. 1.

As described herein, 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 (e.g., any network entity described herein) , a UE 115 (e.g., any UE described herein) , a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, 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 the core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol) . In some examples, network entities 105 may communicate with one another via a backhaul communication link 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via a core network 130) . In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) , one or more wireless links (e.g., 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 described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or a 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 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140) .

In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., 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 two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) . For example, a network entity 105 may include one or more of a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) 180 system, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a 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 (e.g., separate physical locations) . In some examples, one or more network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., 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 (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and 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 (e.g., layer 3 (L3) , layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) . The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between 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 (e.g., via one or more RUs 170) . In some cases, 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 (e.g., 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 one or more DUs 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., 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 (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that are in communication via such communication links.

In wireless communications systems (e.g., 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 (e.g., to a core network 130) . In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as a donor entity or an IAB donor. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140) . The one or more donor network entities 105 (e.g., IAB donors) may be in communication with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120) . IAB nodes 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by DUs 165 of a coupled IAB donor. An IAB-MT may include an independent set of antennas for relay of communications with UEs 115, or may share the same antennas (e.g., of an RU 170) of an IAB node 104 used for access via the DU 165 of the IAB node 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) . In some examples, the IAB nodes 104 may include DUs 165 that support communication links with additional entities (e.g., IAB nodes 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream) . In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of IAB nodes 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 (e.g., an IAB donor) , IAB nodes 104, and one or more UEs 115. The IAB donor may facilitate connection between the core network 130 and the AN (e.g., 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 core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170) , in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link) . IAB donor and IAB nodes 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol) . Additionally, or alternatively, the CU 160 may communicate with the core network via an interface, which may be an example of a portion of backhaul link, and may communicate with other CUs 160 (e.g., a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of a portion of a backhaul link.

An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., 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 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with the IAB node 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through one or more other IAB nodes 104) . Additionally, or alternatively, an IAB node 104 may also be referred to as a parent node or a child node to other IAB nodes 104, depending on the relay chain or configuration of the AN. Therefore, the IAB-MT entity of IAB nodes 104 may provide a Uu interface for a child IAB node 104 to receive signaling from a parent IAB node 104, and the DU interface (e.g., DUs 165) may provide a Uu interface for a parent IAB node 104 to signal to a child IAB node 104 or UE 115.

For example, IAB node 104 may be referred to as a parent node that supports communications for a child IAB node, or referred to as a child IAB node associated with an IAB donor, or both. The IAB donor may include a CU 160 with a wired or wireless connection (e.g., a backhaul communication link 120) to the core network 130 and may act as parent node to IAB nodes 104. For example, the DU 165 of IAB donor may relay transmissions to UEs 115 through IAB nodes 104, or may directly signal transmissions to a UE 115, or both. The CU 160 of IAB donor may signal communication link establishment via an F1 interface to IAB nodes 104, and the IAB nodes 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through the DUs 165. That is, data may be relayed to and from IAB nodes 104 via signaling via an NR Uu interface to MT of the IAB node 104. Communications with IAB node 104 may be scheduled by a DU 165 of IAB donor and communications with IAB node 104 may be scheduled by DU 165 of IAB node 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 power headroom enhancement for dense uplink deployment as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., IAB nodes 104, DUs 165, CUs 160, RUs 170, RIC 175, SMO 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, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer. In some examples, 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, or vehicles, meters, among other examples.

The UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes act 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 FIG. 1.

The UEs 115 and the network entities 105 may wirelessly communicate with one another via one or more communication links 125 (e.g., an access link) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined physical layer structure for supporting the communication links 125. For example, a carrier used for a communication link 125 may include a portion of a RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR) . Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information) , control signaling 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 (e.g., 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 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105) .

In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., 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 (e.g., of the same or a different radio access technology) .

The communication links 125 shown in the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., 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 (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., 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 radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) . Devices of the wireless communications system 100 (e.g., 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 (e.g., a sub-band, a BWP) or all of a carrier bandwidth.

Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) . In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., 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 (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) , such that a relatively higher quantity of resource elements (e.g., 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 (e.g., 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_s=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 (e.g., 10 milliseconds (ms) ) . Each radio frame may be identified by a system frame number (SFN) (e.g., 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 (e.g., 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 (e.g., depending on the length of the cyclic prefix prepended to each symbol period) . In some wireless communications systems 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 (e.g., 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 (e.g., 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 (e.g., 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 (e.g., 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 (e.g., 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 (e.g., 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 (e.g., 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 multiple UEs 115 and UE-specific search space sets for sending control information to a specific UE 115.

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 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) , or others) . In some examples, a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., 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 (e.g., 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 lower-powered network entity 105 (e.g., a lower-powered base station 140) , as compared with a macro cell, and a small cell may operate using the same or different (e.g., 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 (e.g., 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 multiple cells and may also 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 (e.g., 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 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, the overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

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

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

Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., 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 include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., 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 (e.g., 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 115 via a device-to-device (D2D) communication link 135 (e.g., 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 (e.g., a base station 140, an RU 170) , which may support aspects of such D2D communications being configured by (e.g., 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 each of the other 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.

In some systems, a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115) . In some examples, vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities 105, base stations 140, RUs 170) using vehicle-to-network (V2N) communications, or with both.

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 (e.g., 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 (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation 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 (e.g., less than 100 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 also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) , also known as the millimeter band. In some examples, the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170) , and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, such techniques may facilitate using antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.

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) radio access technology, 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 (e.g., LAA) . Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

A network entity 105 (e.g., 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 (e.g., the same codeword) or different data streams (e.g., 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 may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming 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 (e.g., 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 (e.g., a base station 140, an RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE 115. Some signals (e.g., 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 (e.g., 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 transmitting device (e.g., a transmitting network entity 105, a transmitting UE 115) along a single beam direction (e.g., a direction associated with the receiving device, such as a receiving network entity 105 or a receiving 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 (e.g., 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 (e.g., 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 (e.g., 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 (e.g., 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 (e.g., a base station 140, an RU 170) , a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device) .

A receiving device (e.g., a UE 115) may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a transmitting device (e.g., 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 (e.g., 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 (e.g., 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 (e.g., 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 (e.g., a communication link 125, a D2D communication link 135) . HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC) ) , forward error correction (FEC) , and retransmission (e.g., automatic repeat request (ARQ) ) . HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., 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.

A UE 115 may receive a message indicating a trigger-based PHR status of the UE 115, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE 115 satisfying a pathloss threshold. The UE 115 may selectively transmit the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier.

A UE 115 may transmit a PHR in a PUSCH transmission on a first uplink carrier of the UE 115 during a slot, wherein a set of PUSCH transmissions in a second uplink carrier overlap in a time domain in the slot with the PUSCH transmission on the first uplink carrier. The UE 115 may provide a PHR value for the second uplink carrier of the UE 115, the PHR value for the second uplink carrier comprising an actual PHR or a virtual PHR, wherein selection of the actual PHR or the virtual PHR for the second uplink carrier is based at least in part on an uplink transmission type of each PUSCH transmission in the set of PUSCH transmissions.

A UE 115 may select a virtual PHR for an uplink carrier, wherein a power control parameter is configured for the uplink carrier or a pathloss reference signal non-configuration status exists for at least one of a SRS resource set, a PUCCH, a PUSCH, or a TCI state, or any combination thereof, for the uplink carrier. The UE 115 may compute, based at least in part on the selecting, the virtual PHR based at least in part on a set of PUSCH reference parameters, a pathloss offset, or both.

A UE 115 may select an actual PHR or a virtual PHR for transmission in a first PUSCH transmission on an uplink carrier of the UE 115, the selecting based at least in part on a previously received grant that schedules a second PUSCH transmission that is associated with an uplink transmission type, wherein previously received grant is received prior to or during a PDCCH monitoring occasion where the UE 115 detects a grant that schedules the first PUSCH transmission on the first uplink carrier. The UE 115 may transmit the actual PHR or the virtual PHR in the first PUSCH transmission on the uplink carrier of the UE 115 in accordance with the selecting.

A network entity 105 may transmit, to a UE 115, a message indicating a trigger-based PHR status of the UE 115, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE 115 satisfying a pathloss threshold. The network entity 105 may selectively receive the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier.

FIG. 2 shows an example of a wireless communications system 200 that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure. Wireless communications system 200 may implement aspects of wireless communications system 100. Wireless communications system 200 may include a UE 205, a network entity 210, an uplink-only device 215, an uplink-only device 220, and an uplink-only device 225, which may be examples of the corresponding devices described herein.

For example, wireless communications system 200 may be a non-limiting example of a dense uplink deployment scenario where one or more uplink receive points are configured within the network and associated with a network entity, such as the network entity 210. To improve uplink capacity and coverage, a dense uplink deployment may provide asymmetric downlink/uplink densification. The uplink signals or channels from the UE 205 are received at the uplink receive point. Downlink signals or channels are transmitted from the network entity 210, which can also be referred to as a macro node, a central node, a serving cell, a serving base station, or similar terms. The uplink receive points may be connected to the network entity 210 via a backhaul connection. The uplink receive points may provide the uplink communications from the UE 205 to the network entity 210 via the backhaul network. The dense uplink deployment may reduce the uplink pathloss (PL) , which may be helpful when the uplink coverage area is a bottleneck. This may also improve deployment costs and complexity of the wireless network since the uplink receive points may not transmit any downlink signals. That is, the uplink receive points may receive the uplink signal from the UE 205 and send the information to the network entity 210 via the backhaul with or without some processing. The uplink-only device 215, the uplink-only device 220, and the uplink-only device 225, may be non-limiting examples of the uplink receive points in the dense uplink deployment.

PHR techniques provide mechanisms for the UE 205 to transmit or otherwise provide an indication of an available uplink transmit power of the UE 205. That is, each UE may have a maximum transmit power that it can provide for a wireless transmission. The maximum transmit power may be designed for the UE and the wireless network in general based on permissible exposure limits defined in various regulations or governing standards. The maximum transmit power may be based, at least to some degree, on the operating capabilities or configuration of the UE 205. The PHR may generally carry or otherwise convey an indication of the power headroom of the UE 205, which is generally the difference between the maximum transmit power of the UE 205 and the current transmit power being used for an uplink transmission over a channel.

There are generally three types of PHR that may be reported by the UE 205. A Type 1 PHR may be used for a PUSCH (e.g., uplink transmissions on the PUSCH) , a Type 2 PHR may be used for a PUCCH (e.g., uplink transmissions on the PUCCH) , and a Type 3 PHR may be used for an SRS (e.g., for SCells configured with SRS only) .

Further, PHR techniques may generally define two types of PHR that can be reported, an actual PHR or a virtual PHR. Broadly, an actual PHR may be used to calculate the PHR for a specific PUSCH transmission occasion (i) while the virtual PHR may be used to calculate the PHR for a reference PUSCH transmission.

More particularly, the actual PHR reported by the UE 205 for PUSCH (e.g., Type 1) may be computed, calculated, or otherwise determined using:

where P_CMAX, f, c (i) is the UE configured maximum output power after power backoff due to power management (e.g., backoff due to maximum permissible reduction (MPR) limits) and the remaining parameters are the parameters used for determining the PUSCH transmit power to be used for the specific PUSCH transmission occasion (i) .

The virtual PHR reported by the UE 205 may be computed, calculated, or otherwise determined using:

whereis computed assuming non backoff (e.g., MPR values assumed to be 0dB) and the remaining parameters are based on default or reference parameters for j, i, l, and q_d.

The UE 205 may transmit the PHR to the network entity 210 based on a number of triggers. One example trigger may be based on a set of timers configured for PHR reporting (e.g., phr-PeriodicTimer, phr-ProhibitTimer) . Another trigger may be based on a pathloss change that is larger than a configured threshold (e.g., a pathloss threshold) for at least one pathloss reference signal (PL-RS) used for power control in any uplink carrier. Other examples of triggers may be based on activation of an SCell, activation of a BWP of a configured CC being changed from dormant to non-dormant, or vice versa.

Once triggered, the PHR may be reported in a PHR MAC-CE on a first available PUSCH that corresponds to an initial transmission of a transport block (TB) that can accommodate the MAC-CE as a result of logical channel prioritization (LCP) . The PUSCH may be a dynamic PUSCH (e.g., scheduled by a DCI grant) or the PUSCH may be semi-persistent in nature (e.g., configured grant-based PUSCH) . The UE 205 may be configured with multiple CCs (e.g., multiple uplink carriers) for the PUSCH transmission. For example, the PHR MAC-CE may include the PHR report for more than on carrier if a multiplePHR parameter is enabled, such as enabled using RRC signaling. Otherwise, the PHR may be reported for the PCell and a single-entry MAC-CE format may be used. When a first PUSCH in a first uplink carrier carries the MAC-CE PHR, for a second uplink carrier the MAC-CE may include either the actual PHR or the virtual PHR. This may depend on whether there is a PUSCH transmission on the second uplink carrier at the time of PHR reporting (e.g., in the same slot as the PUSCH on the first uplink carrier) or whether the PUSCH transmission on the second uplink carrier is scheduled by a DCI that satisfies a timeline condition. Otherwise, a virtual PHR may be reported by the UE 205.

A single-entry PHR MAC-CE may include a set of bits being used to convey the PHR. A multiple entry PHR MAC-CE may use a bitmap, where each bit represents a PHR for a specific uplink carrier (other than the PCell) . The PHR MAC-CE may also indicate a P parameter associated with whether the MAC entity applies power backoff due to power management (e.g., due to MPR related power backoff) . The PHR MAC-CE may also indicate a V parameter associated with whether the actual or virtual PHR is being reported, where the correspondingfield may be present when the actual PHR is being reported) .

However, in a dense uplink deployment scenario there may be no downlink reference signal from the uplink receive point (e.g., the uplink-only device 215, the uplink-only device 220, or the uplink-only device 225) . The determine the uplink transmit power, two schemes may be applied. One scheme may include power control due to the uplink pathloss change being configured or indicated by the network entity 210. For example, a transmit power control (TPC) command in a MAC-CE or a DCI may be used to update the close loop power, P0, or pathloss values.

Another scheme may be that a pathloss offset may be indicated to the UE 205 and the UE 205 may derive the uplink pathloss based on the downlink pathloss measured on a downlink reference signal and the indicated pathloss offset. That is, the pathloss offset may be measured, computed, or otherwise determined based on a real or estimated difference between the downlink pathloss associated with the network entity 210 and the uplink pathloss associated with the uplink-only device 215, for example. For a downlink node (such as the network entity 210) , a downlink reference signal and the uplink transmit power may be determined based on the pathloss measured on the downlink reference signal (e.g., since the downlink path and the uplink path are at least somewhat reciprocal) .

However, such techniques may become an issue in some scenarios. In particular, the PHR is generally provided to the network entity 210 to support power aware scheduling. For a PUSCH transmission to an uplink receive point (e.g., the uplink-only device 215, in this example) , either scheme may be used for the PHR. In the first scheme, the uplink transmit power may be fully controlled by the network entity 210 and therefore the PHR to the uplink-only device 215 may be unnecessary. In the second scheme, although a pathloss offset may be indicated to the UE 205, the downlink pathloss for the downlink channel may be unknown by the network entity 210. Therefore, the UE 205 may still need to provide the PHR to the network entity 210 when the pathloss change is larger than the configured threshold in order to support the power aware scheduling.

For a downlink receive point, whether the PHR is needed may be based on whether the PUSCH transmission to the downlink receive point is allowed. If so, the PHR for the downlink receive point may be needed when the pathloss changes satisfy a configured threshold (e.g., the pathloss threshold) . If not, the PHR may not be needed when the pathloss changes satisfy the configured threshold.

Accordingly, in some wireless networks the PHR may be triggered when the pathloss change is larger than the configured pathloss threshold for at least one pathloss reference signal used for power control in the uplink carrier. For the first scheme, when the PUSCH is not transmitted to the downlink receive point, triggering the PHR when the pathloss change satisfies the pathloss threshold may be inefficient since the uplink transmit power is controlled by the network entity 210. When the PUSCH is transmitted to the downlink receive point, the PHR triggering may be needed. In some aspects, the PHR for the PUSCH to the downlink receive point may be relatively more useful than that for the uplink receive point.

Moreover, in the second scheme when the PUSCH is transmitted to either the downlink receive point or the uplink receive point, if there are more than one PUSCHs in the slot of the PHR MAC-CE, it is unclear which PHR is to be reported (actual or virtual PHR) . For both schemes, when the virtual PHR is reported, such networks may not properly define how to compute the PHR considering different power control formula may be used between PUSCH to the uplink receive point and the downlink receive point.

Accordingly, aspects of the techniques describe herein provide for various improvements for such PHR reporting techniques. Aspects of the techniques described herein may be implemented in a dense uplink deployment scenario, such as a wireless network using uplink receive point (s) , downlink receive point (s) , or both devices. In some aspects, the described techniques may be applied when the UE 205 is configured with multiple uplink carriers (e.g., two or more uplink carriers) .

Aspects of the described techniques provide for PHR triggering based on the pathloss change being larger than a configured pathloss threshold for at least one pathloss reference signal in any uplink carrier of the UE 205. For example, the UE 205 may receive or otherwise obtain (and the network entity 210 may transmit or otherwise provide for output) a message indicating a trigger-based PHR status of the UE 205. The trigger-based PHR status may indicate whether to enable (or disable) transmission of PHR that has been triggered by a pathloss change on at least one uplink carrier of the UE 205 that satisfies a pathloss threshold (e.g., the configured threshold) . In some examples, whether to disable the PHR triggering condition may be (pre) defined or received in an RRC message.

The UE 205 may selectively transmit the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier. For example, the UE may transmit the PHR when the trigger-based PHR status indicates to enable PHR transmissions based on the pathloss change satisfying the pathloss threshold. The UE may refrain from transmitting the PHR when the trigger-based PHR status indicates to disable PHR transmissions based on the pathloss change satisfying the pathloss threshold. For example, the UE 205 may identify, detect, or otherwise determine that the pathloss change has satisfied the pathloss threshold for at least one uplink carrier of the UE 205 and yet refrain from transmitting the PHR in accordance with the trigger-based PHR status.

In some aspects, the trigger-based PHR status may be based on the uplink-only device 215 being configured for at least one uplink carrier or for all uplink carriers of the UE 205. Whether or not the uplink-only device 215 has been configured for one or more uplink carriers of the UE 205 may be identified or otherwise determined using different techniques. One technique may be that the UE 205 is explicitly configured with information identifying the uplink-only device 215 for the UE 205. The explicit configuration may be based on RRC signaling or other signaling mechanisms.

Another technique may be based on a new power control parameter (e.g., a pathloss or pathloss offset) being configured for an SRS transmission, a PUCCH transmission, or a PUSCH transmission. For example, the trigger-based PHR status may be based on the power control parameter (e.g., the pathloss or the pathloss offset) configured for the SRS/PUCCH/PUSCH. The UE 205 may receive or otherwise obtain an indication of the power control parameter configured for the SRS/PUCCH/PUSCH from the network entity 210. When the power control parameter is configured, this may indicate to the UE 205 that the uplink-only device 215 has been configured for the UE 205.

Another technique may be based on a new power control parameter (e.g., pathloss or pathloss offset) being configured for at least one uplink TCI state (e.g., when unified TCI state is configured) . For example, the UE 205 may receive or otherwise obtain an indication of the uplink TCI state from the network entity 210. The trigger-based PHR status may be based on the power control parameter. For example, when the power control parameter is configured for the uplink TCI state, this may indicate to the UE 205 that the uplink-only device 215 has been configured for the UE 205.

Another technique may be based on a pathloss reference signal not being configured (e.g., the pathloss reference signal in a non-configuration state or status) for at least one SRS resource set, a PUCCH, or a PUSCH. For example, the UE 205 may identify, detect, or otherwise determine whether the pathloss reference signal is configured for at least one of the SRS transmission, the PUCCH transmission, or the PUSCH transmission. Again, the trigger-based PHR status may be based on whether the pathloss reference signal has been configured for the UE 205 by the network entity 210. That is, the pathloss reference signal not being configured for the SRS resource set, the PUCCH, or the PUSCH, this may indicate to the UE 205 that the uplink-only device 215 has been configured for the UE 205.

A final technique may be based on the pathloss reference signal not being configured (e.g., in a non-configuration state or status) for at least one uplink TCI state (again, when the unified TCI state is configured) . For example, the UE 205 may identify, detect, or otherwise determine whether the pathloss reference signal is configured for the uplink TCI state. The trigger-based PHR status may be based on whether the pathloss reference signal has been configured for the UE 205 by the network entity 210. That is, the pathloss reference signal not being configured for the uplink TCI state may indicate to the UE 205 that the uplink-only device 215 has been configured for the UE 205.

Accordingly, the UE 205 may receive, detect, or otherwise determine whether the uplink-only device 215 has been configured for an uplink carrier using such techniques and apply the trigger-based PHR status accordingly.

FIGs. 3A and 3B show examples of a scheduling configuration 300 that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure. Scheduling configuration 300 may implement aspects of wireless communications system 100 or wireless communications system 200. Aspects of scheduling configuration 300 may be implemented at or implemented by a UE, a network entity, or an uplink-only device, which may be examples of the corresponding devices described herein.

Scheduling configuration 300 illustrates a non-limiting example of techniques to select, identify, or otherwise determine the PHR to be indicated for a second uplink carrier of the UE. As discussed above, when the UE is configured with multiple uplink carriers (e.g., CC1 and CC2, in this non-limiting example) and a first PUSCH in a first uplink carrier carries or otherwise conveys a PHR MAC-CE, the MAC-CE may either carry an actual PHR or a virtual PHR for the second uplink carrier (s) . In some wireless networks, whether the actual or virtual PHR is sent may depend on whether there is a PUSCH transmission on the second uplink carrier in the same slot and whether the DCI scheduling the PUSCH transmission on the second uplink carrier satisfies the timeline condition relative to the DCI that schedules the PUSCH transmission on the first uplink carrier. However, these techniques for determining whether the actual or virtual PHR is provided for the second uplink carrier may be inefficient or otherwise become an issue in some scenarios.

Accordingly, aspects of the techniques described herein provide improved mechanisms to determine whether to provide an actual or virtual PHR for the second uplink carrier based on the uplink transmission type of the PUSCH transmission (s) that are scheduled in the second uplink carrier. In particular, aspects of the techniques described herein use the uplink transmission type of each PUSCH transmission scheduled in the second uplink carrier to identify or otherwise determine whether the actual PHR value or the virtual PHR value is reported.

For example, the UE may transmit or otherwise provide for output (and a network entity may receive or otherwise obtain) a PHR in a PUSCH transmission on a first uplink carrier of the UE during a slot (e.g., during slot n) . In this non-limiting example, this may include the UE receiving a DCI grant 305 during slot n-2 on the first uplink carrier (e.g., CC1) . The DCI grant 305 received on CC1 during slot n-2 may schedule a PUSCH transmission on CC1 during slot n.

A set of PUSCH transmissions in the second uplink carrier (e.g., CC2) may overlap in the time domain in the slot n with the PUSCH transmission on CC1. For example, the UE may receive or otherwise obtain (and the network entity may transmit or otherwise provide for output) a DCI grant 305 during slot n-3 that schedules a PUSCH transmission on CC2 during slot n. The UE may also receive or otherwise obtain (and the network entity may transmit or otherwise provide for output) a DCI grant 305 during slot n-2 on CC2 that schedules a PUSCH transmission on CC2 during slot n. Thus, in this non-limiting example, the set of PUSCH transmissions on CC2 during slot n includes two PUSCH transmission. The overlap in the time domain may correspond to one or more symbols of the PUSCH transmissions scheduled on CC2 being the same symbol as is used to carry the PUSCH transmission scheduled on CC1 that carriers the PHR MAC-CE. The UE may select, compute, or otherwise provide an actual PHR or a virtual PHR as the PHR value for CC2 based on the uplink transmission type of each PUSCH transmission scheduled on CC2.

In particular, the uplink transmission type may be either a specific PUSCH 310 or a non-specific PUSCH 315. Various approach may be applied to identify or otherwise determine whether a PUSCH transmission is a specific PUSCH 310 or a non-specific PUSCH 315. In some aspects, this may be based on whether the PUSCH is associated with a downlink receive point or with an uplink receive point.

For example, a first approach may include the specific PUSCH 310 being identified or otherwise detected based on whether or not the PUSCH transmission is associated with a downlink receive point. A specific PUSCH 310 may be a PUSCH that is associated with a downlink pathloss reference signal, but is not associated with a pathloss or pathloss offset being configured for the PUSCH. For example, the UE may identify or otherwise detect whether at least one PUSCH transmission on CC2 is a specific PUSCH 310 based on the pathloss reference signal being associated with the PUSCH transmission and on the pathloss or pathloss offset not being configured (e.g., in a non-configuration state or status) for the PUSCH transmission. A specific PUSCH 310 in this example may include the PUSCH transmission that is associated with the pathloss reference signal, but is not associated with a pathloss or pathloss offset value.

Another approach may include the specific PUSCH 310 being identified or otherwise detected based on whether or not the PUSCH transmission is associated with an uplink TCI state, where the uplink TCI state is associated with a downlink pathloss reference signal, associated with a source downlink reference signal, or is associated with a specific timing advance group (TAG) (e.g., the first TAG or the lowest TAG) . The specific PUSCH 310 in this example may be a PUSCH transmission that is associated with the uplink TCI state when the uplink TCI state is associated with the downlink pathloss reference signal, the source downlink reference signal, or the specific TAG identifier. Accordingly, the UE may identify or otherwise detect that at least one PUSCH transmission on CC2 based on the uplink TCI state being associated with the downlink pathloss reference signal, the source downlink reference signal, the TAG identifier, or any combination of these associations.

One approach may include the specific PUSCH 310 being identified or otherwise detected based on the scheduling DCI. That is, the UE may identify or otherwise detect that at least one PUSCH transmission on CC2 is a specific PUSCH 310 based on the DCI grant that schedules the PUSCH transmission.

Additionally, or alternatively, the specific PUSCH 310 may be identified or otherwise detected based on whether or not the PUSCH transmission is associated with an uplink receive point. Different approaches may be used to identify or otherwise determine whether a PUSCH transmission on CC2 is the specific PUSCH 310 associated with the uplink receive point. One approach may include whether or not the PUSCH transmission is associated with a pathloss of pathloss offset. For example, the UE may identify or otherwise detect whether at least one PUSCH transmission scheduled on CC2 is associated with the pathloss or the pathloss offset. If so, this may indicate that the PUSCH transmission is a specific PUSCH 310.

Another approach may be based on whether the PUSCH transmission is associated with an uplink TCI state, where the uplink TCI state is associated with a pathloss or pathloss offset, associated with a source SRS resource, or associated with a specific TAG identifier (e.g., the second TAG or highest TAG identifier) . For example, the UE may identify or otherwise detect at least one PUSCH transmission on CC2 based on the uplink TCI state associated with the PUSCH transmission, where the uplink TCI state is associated with the pathloss, the pathloss offset, the SRS resource, or the TAG identifier.

Additionally, or alternatively, another approach to identify, detect, or otherwise distinguish the specific PUSCH 310 from the non-specific PUSCH 315 may include RRC signaling being used to indicate or otherwise identify the specific PUSCH 310 for the UE. That is, the specific PUSCH 310 may be configured for the UE using an RRC message. For example, the RRC message may indicate whether the specific PUSCH 310 transmission is associated with a downlink receive point or a uplink receive point.

Accordingly, this may include the UE identifying, determining, or otherwise detecting that at least one of the PUSCH transmissions in the set of PUSCH transmissions scheduled on CC2 is associated with a specific uplink transmission type (e.g., the specific PUSCH 310) , in some examples. If at least one PUSCH transmission scheduled on CC2 is a specific PUSCH 310, the UE may select the actual PHR for CC2. The actual PHR may be based on the first PUSCH transmission scheduled on CC2 that is a specific PUSCH 310.

Scheduling configuration 300-a of FIG. 3A illustrates a non-limiting example of at least one PUSCH transmission (the second PUSCH transmission) scheduled on CC2 being associated with a specific uplink transmission type (e.g., the specific PUSCH 310) . Scheduling configuration 300-b of FIG. 3B illustrates a non-limiting example of no PUSCH transmissions scheduled on CC2 being associated with the specific uplink transmission type. Different options may be applied for selection between the actual PHR or the virtual PHR values to be reported for CC2 based on the uplink transmission type associated with each PUSCH transmission scheduled on CC2 during slot n.

One option may include selecting the actual PHR for the second uplink carrier (CC2) if at least one PUSCH transmission on CC2 is a specific PUSCH 310. In the non-limiting example illustrated in scheduling configuration 300-a of FIG. 3A, the UE may detect, identify, or otherwise determine that at least one PUSCH in CC2 is a specific PUSCH 310. For example, the DCI grant 305 received on CC2 during slot n-2 may schedule a specific PUSCH 310 for the UE during slot n. The DCI grant 305 received on CC2 during slot n-2 satisfies the timeline requirement with respect to the DCI grant 305 received on CC1 that schedules the PHR MAC-CE for the PUSCH scheduled on CC1 during slot n. Moreover, the specific PUSCH 310 scheduled on CC2 may overlap in the time domain with respect to the PHR MAC-CE scheduled on CC1. Accordingly, in this option the UE may select the actual PHR for CC2 during slot n. The actual PHR may be based on the first of the specific PUSCH 310 transmission (s) that overlaps with the PHR MAC-CE being carried or otherwise conveyed on CC1 during slot n.

In the non-limiting example illustrated in scheduling configuration 300-b of FIG. 3B, the UE may detect, identify, or otherwise determine that each PUSCH in CC2 is a non-specific PUSCH 315. For example, the DCI grant 305 received on CC2 during slot n-3 and the DCI grant 305 received during slot n-2 may both schedule non-specific PUSCH 315 transmissions for the UE during slot n. The DCI grant 305 received on CC2 during slot n-3 and the DCI grant 305 received on CC2 during slot n-2 may both satisfy the timeline requirement with respect to the DCI grant 305 received on CC1 that schedules the PHR MAC-CE for the PUSCH scheduled on CC1 during slot n. Moreover, the non-specific PUSCH 315 transmissions scheduled on CC2 may overlap in the time domain with respect to the PHR MAC-CE scheduled on CC1. Accordingly, in this option the UE may select the actual PHR for CC2 during slot n. Moreover, the actual PHR may be based on the first of the non-specific PUSCH 315 transmission that overlaps with the PHR MAC-CE being carried or otherwise conveyed on CC1 during slot n.

Another option may include the UE selecting the actual PHR or the virtual PHR based on whether or not a specific PUSCH 310 is schedule on CC2 that overlaps with the PHR MAC-CE carried in the PUSCH transmission on CC1. In the non-limiting example illustrated in scheduling configuration 300-a of FIG. 3A, the UE may detect, identify, or otherwise determine that at least one PUSCH in CC2 is a specific PUSCH 310. Accordingly, in this option the UE may select the actual PHR for CC2 during slot n. Moreover, the actual PHR may be based on the first of the specific PUSCH 310 transmissions that overlaps with the PHR MAC-CE being carried or otherwise conveyed on CC1 during slot n.

In the non-limiting example illustrated in scheduling configuration 300-b of FIG. 3B, the UE may detect, identify, or otherwise determine that no PUSCH on CC2 is a specific PUSCH 310 (e.g., each PUSCH transmission scheduled on CC2 is a non-specific PUSCH 315 transmission) . Accordingly, in this option the UE may select the virtual PHR for CC2 during slot n. Moreover, the virtual PHR may be based on a reference PUSCH. Aspects of this option may be used for the first scheme discussed above where the uplink transmit power is fully controlled by the network entity. In this situation, there may be no PUSCH transmission towards a downlink receive point in slot n, which may enable prioritizing the virtual PHR to the downlink receive point over the actual PHR to an uplink receive point.

Another option may include the UE selecting the actual PHR or the virtual PHR based on whether or not the first PUSCH in the set of PUSCH transmissions scheduled on CC2 is a specific PUSCH 310 or a non-specific PUSCH. In the non-limiting examples illustrated in both scheduling configuration 300-a of FIG. 3A and scheduling configuration 300-b of FIG. 3B, the UE may detect, identify, or otherwise determine that a first PUSCH transmission (e.g., the first PUSCH transmission in the time domain) that is scheduled on CC2 is a non-specific PUSCH 315. Accordingly, in this option the UE may select the virtual PHR for CC2 during slot n. Moreover, the virtual PHR may be based on the first PUSCH transmission on CC2 being a non-specific PUSCH 315. Conversely, in an example where the UE detects, identifies, or otherwise determines that the first PUSCH transmission scheduled on CC2 that overlaps with the PHR MAC-CE on CC1 is a specific PUSCH 310, the UE may select the actual PHR for CC2. The actual PHR may be based on the first PUSCH transmission scheduled on CC2 during slot n. Accordingly, in this option if the first PUSCH of the set of PUSCHs scheduled on CC2 are a specific PUSCH 310, the UE may report the actual PHR based on the first PUSCH. Otherwise, the UE may report the virtual PHR.

Additionally, or alternatively, aspects of the techniques described herein provide for, when the virtual PHR is reported, the PHR may be identified, selected, or otherwise computed based on a pathloss offset. For example, the UE may identify, select, or otherwise determine a virtual PHR for an uplink carrier based on a power control parameter configured for the uplink carrier or based on a pathloss reference signal not being configured (e.g., in a non-configuration status or state) for a SRS resource set, a PUCCH, a PUSCH, a TCI state, or any combination of these for the uplink carrier. For example, the UE may select the virtual PHR for the uplink carrier and compute the virtual PHR in accordance with the PUSCH reference parameters or a pathloss offset. In particular, one example of the formula used to calculate or otherwise compute the virtual PHR may be based on:

However, aspects of the described techniques may include the virtual PHR being computed based on a default pathloss offset. For example, the formula above used to compute the virtual PHR may be modified to include or otherwise be based on the pathloss offset configured for the UE, along with the PUSCH reference parameters. One non-limiting example of this modification may include:

The UE may identify or otherwise determine the pathloss offset (e.g., whether the default pathloss is configured and, if so, its value) according to different metrics. For example, the UE may identify or otherwise determine the pathloss offset based on a default pathloss reference signal identifier. For example, the pathloss offset may be based on or otherwise associated with a default pathloss reference signal identifier, such as pusch-PathlossReferenceRS-Id being equal to zero. The pathloss offset may be determined based on a default P0 nominal power level. For example, the pathloss offset may be associated with a default p0-PUSCH-AlphaSetId being set to zero. The pathloss offset may be determined based on a default uplink TCI state. For example, the pathloss offset may be associated with a default uplink TCI state identifier, such as uplink TCI state identifier being equal to zero. The pathloss offset may be determined based on a default pathloss value (e.g., the pathloss offset may be set to zero) . The pathloss offset may be determined based on an indicated TCI state of the UE (e.g., the indicated TCI state configured for the UE may be associated with the pathloss offset) .

Whether or not the pathloss offset is used to compute the virtual PHR may be based on the indicated TCI state of the UE. For example, if the indicated TCI state is not associated with a pathloss offset (e.g., the pathloss offset is in a non-configuration state or status for the indicated TCI state) , then the UE may compute the virtual PHR without the pathloss offset modification. If the indicated TCI state is associated with a pathloss offset, then the UE may compute the virtual PHR using the pathloss offset modification.

In another option, the UE may be configured (e.g., using RRC signaling) with an indicator of whether or not to use the pathloss offset when computing the virtual PHR for the uplink carrier.

FIGs. 4A and 4B show examples of a scheduling configuration 400 that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure. Scheduling configuration 400 may implement aspects of wireless communications system 100 or wireless communications system 200 or aspects of scheduling configuration 300. Aspects of scheduling configuration 400 may be implemented at or implemented by a UE, a network entity, or an uplink-only device, which may be examples of the corresponding devices described herein.

Scheduling configuration 400 illustrates a non-limiting example of techniques to select, identify, or otherwise determine the PHR (e.g., actual PHR or virtual PHR) to be indicated for an uplink carrier of the UE (e.g., CC1, in this non-limiting example) . Aspects of the techniques described herein provide improved mechanisms to determine whether to provide an actual or virtual PHR for the uplink carrier based on the uplink transmission type of the PUSCH transmission that is scheduled on the uplink carrier. In particular, aspects of the techniques described herein use the uplink transmission type of the PUSCH transmission carrying the PHR MAC-CE that is scheduled on the first uplink carrier to identify or otherwise determine whether the actual PHR value or the virtual PHR value is reported.

For example, the UE may identify, select, or otherwise determine an actual PHR or a virtual PHR for transmission in a first PUSCH transmission on an uplink carrier of the UE. This selection may be based on a previously received grant that schedules a second PUSCH transmission associated with an uplink transmission type. In this example, the previously received grant may be received prior to (or during) a PDCCH monitoring occasion where the detects the grant that schedules the first PUSCH transmission on the uplink carrier. In this non-limiting example, this may include the UE receiving a DCI grant 405 during slot n-2 on the first uplink carrier (e.g., CC1) . The DCI grant 305 received on CC1 during slot n-2 may schedule a PUSCH transmission on CC1 during slot n. For example, the UE may monitor the PDCCH during the monitoring occasion to receive the DCI grant 405 scheduling the PUSCH transmission that carries the PHR MAC-CE on CC1.

In the scheduling configuration 400-a of FIG. 4A, the PUSCH transmission scheduled on CC1 during slot n may be a specific PUSCH 410. In the scheduling configuration 400-b of FIG. 4B, the PUSCH transmission scheduled on CC1 during slot n may be a non-specific PUSCH 415. Techniques to identify, determine, or otherwise differentiate the specific PUSCH 410 from the non-specific PUSCH 415 are discussed above.

A set of PUSCH transmissions in the second uplink carrier (e.g., CC2) may overlap in the time domain in the slot n with the PUSCH transmission on CC1. For example, the UE may receive or otherwise obtain (and the network entity may transmit or otherwise provide for output) a DCI grant 405 during slot n-3 that schedules a PUSCH transmission on CC2 during slot n. The UE may also receive or otherwise obtain (and the network entity may transmit or otherwise provide for output) a DCI grant 405 during slot n-2 on CC2 that schedules a PUSCH transmission on CC2 during slot n. Thus, in this non-limiting example, the set of PUSCH transmissions on CC2 during slot n includes two PUSCH transmission. The UE may select, compute, or otherwise provide an actual PHR or a virtual PHR as the PHR value for CC2 based on the uplink transmission type of each PUSCH transmission scheduled on CC2, such as is discussed above.

With respect to the PHR being reported in the PUSCH transmission on CC1 during slot n, the UE may select the actual or virtual PHR depending on whether or not the PUSCH transmission is a specific PUSCH 410. In the non-limiting example scheduling configuration 400-a of FIG. 4A, the PUSCH transmission scheduled on CC1 during slot n may be a specific PUSCH 410. In this example, the UE may select the actual PHR to be reported in the MAC-CE of the specific PUSCH 410 transmission.

In the non-limiting example scheduling configuration 400-b of FIG. 4B, the PUSCH transmission scheduled on CC1 during slot n may be a non-specific PUSCH 415. In this example, the UE may select the virtual PHR to be reported in the MAC-CE of the non-specific PUSCH 415 transmission.

Accordingly, scheduling configuration 400 illustrates a non-limiting example of the UE determining whether the PHR for the uplink carrier is based on an actual transmission (e.g., an actual PHR) or a reference format (e.g., a virtual PHR) based at least in part on the DCI that schedules a specific PUSCH 410 the UE receives until and including (e.g., prior to and during) the PDCCH monitoring occasion where the UE detects the first DCI format scheduling an initial transmission of a TB since a PHR was triggered if the PHR is reported on a PUSCH triggered by the first DCI format.

FIG. 5 shows a block diagram 500 of a device 505 that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure. The device 505 may be an example of aspects of a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communications manager 520. The device 505, or one or more components of the device 505 (e.g., the receiver 510, the transmitter 515, and the communications manager 520) , may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .

The receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to power headroom enhancement for dense uplink deployment) . Information may be passed on to other components of the device 505. The receiver 510 may utilize a single antenna or a set of multiple antennas.

The transmitter 515 may provide a means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to power headroom enhancement for dense uplink deployment) . In some examples, the transmitter 515 may be co-located with a receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a set of multiple antennas.

The communications manager 520, the receiver 510, the transmitter 515, or various combinations thereof or various components thereof may be examples of means for performing various aspects of power headroom enhancement for dense uplink deployment as described herein. For example, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

In some examples, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include at least one of a processor, a digital signal processor (DSP) , a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .

Additionally, or alternatively, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functions of the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .

In some examples, the communications manager 520 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 510, the transmitter 515, or both. For example, the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager 520 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 520 is capable of, configured to, or operable to support a means for receiving a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold. The communications manager 520 is capable of, configured to, or operable to support a means for selectively transmitting the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier.

Additionally, or alternatively, the communications manager 520 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 520 is capable of, configured to, or operable to support a means for transmitting a PHR in an PUSCH transmission on a first uplink carrier of the UE during a slot, where a set of PUSCH transmissions in a second uplink carrier overlap in a time domain in the slot with the PUSCH transmission on the first uplink carrier. The communications manager 520 is capable of, configured to, or operable to support a means for providing a PHR value for the second uplink carrier of the UE, the PHR value for the second uplink carrier including an actual PHR or a virtual PHR, where selection of the actual PHR or the virtual PHR for the second uplink carrier is based on an uplink transmission type of each PUSCH transmission in the set of PUSCH transmissions.

Additionally, or alternatively, the communications manager 520 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 520 is capable of, configured to, or operable to support a means for selecting a virtual PHR for an uplink carrier, where a power control parameter is configured for the uplink carrier or a pathloss reference signal non-configuration status exists for at least one of an SRS resource set, a PUCCH, an PUSCH, or a TCI state, or any combination thereof, for the uplink carrier. The communications manager 520 is capable of, configured to, or operable to support a means for computing, basing at least in part on the selecting, the virtual PHR based on a set of PUSCH reference parameters, a pathloss offset, or both.

Additionally, or alternatively, the communications manager 520 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 520 is capable of, configured to, or operable to support a means for selecting an actual PHR or a virtual PHR for transmission in a first PUSCH transmission on an uplink carrier of the UE, the selecting based on a previously received grant that schedules a second PUSCH transmission that is associated with an uplink transmission type, where previously received grant is received prior to or during a PDCCH monitoring occasion where the UE detects a grant that schedules the first PUSCH transmission on the first uplink carrier. The communications manager 520 is capable of, configured to, or operable to support a means for transmitting the actual PHR or the virtual PHR in the first PUSCH transmission on the uplink carrier of the UE in accordance with the selecting.

By including or configuring the communications manager 520 in accordance with examples as described herein, the device 505 (e.g., at least one processor controlling or otherwise coupled with the receiver 510, the transmitter 515, the communications manager 520, or a combination thereof) may support techniques for improved PHR triggering and reporting in a dense uplink deployment scenario that is based, in some examples, on the uplink transmission type of the PUSCH transmission.

FIG. 6 shows a block diagram 600 of a device 605 that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure. The device 605 may be an example of aspects of a device 505 or a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. The device 605, or one of more components of the device 605 (e.g., the receiver 610, the transmitter 615, and the communications manager 620) , may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .

The receiver 610 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to power headroom enhancement for dense uplink deployment) . Information may be passed on to other components of the device 605. The receiver 610 may utilize a single antenna or a set of multiple antennas.

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

The device 605, or various components thereof, may be an example of means for performing various aspects of power headroom enhancement for dense uplink deployment as described herein. For example, the communications manager 620 may include an PHR status manager 625, an PHR selection manager 630, a grant manager 635, or any combination thereof. The communications manager 620 may be an example of aspects of a communications manager 520 as described herein. In some examples, the communications manager 620, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both. For example, the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager 620 may support wireless communications in accordance with examples as disclosed herein. The PHR status manager 625 is capable of, configured to, or operable to support a means for receiving a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold. The PHR status manager 625 is capable of, configured to, or operable to support a means for selectively transmitting the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier.

Additionally, or alternatively, the communications manager 620 may support wireless communications in accordance with examples as disclosed herein. The PHR selection manager 630 is capable of, configured to, or operable to support a means for transmitting a PHR in an PUSCH transmission on a first uplink carrier of the UE during a slot, where a set of PUSCH transmissions in a second uplink carrier overlap in a time domain in the slot with the PUSCH transmission on the first uplink carrier. The PHR selection manager 630 is capable of, configured to, or operable to support a means for providing a PHR value for the second uplink carrier of the UE, the PHR value for the second uplink carrier including an actual PHR or a virtual PHR, where selection of the actual PHR or the virtual PHR for the second uplink carrier is based on an uplink transmission type of each PUSCH transmission in the set of PUSCH transmissions.

Additionally, or alternatively, the communications manager 620 may support wireless communications in accordance with examples as disclosed herein. The PHR selection manager 630 is capable of, configured to, or operable to support a means for selecting a virtual PHR for an uplink carrier, where a power control parameter is configured for the uplink carrier or a pathloss reference signal non-configuration status exists for at least one of an SRS resource set, a PUCCH, an PUSCH, or a TCI state, or any combination thereof, for the uplink carrier. The PHR selection manager 630 is capable of, configured to, or operable to support a means for computing, based on the selecting, the virtual PHR based on a set of PUSCH reference parameters, a pathloss offset, or both.

Additionally, or alternatively, the communications manager 620 may support wireless communications in accordance with examples as disclosed herein. The grant manager 635 is capable of, configured to, or operable to support a means for selecting an actual PHR or a virtual PHR for transmission in a first PUSCH transmission on an uplink carrier of the UE, the selecting based on a previously received grant that schedules a second PUSCH transmission that is associated with an uplink transmission type, where previously received grant is received prior to or during a PDCCH monitoring occasion where the UE detects a grant that schedules the first PUSCH transmission on the first uplink carrier. The grant manager 635 is capable of, configured to, or operable to support a means for transmitting the actual PHR or the virtual PHR in the first PUSCH transmission on the uplink carrier of the UE in accordance with the selecting.

FIG. 7 shows a block diagram 700 of a communications manager 720 that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure. The communications manager 720 may be an example of aspects of a communications manager 520, a communications manager 620, or both, as described herein. The communications manager 720, or various components thereof, may be an example of means for performing various aspects of power headroom enhancement for dense uplink deployment as described herein. For example, the communications manager 720 may include an PHR status manager 725, an PHR selection manager 730, a grant manager 735, a power control parameter manager 740, a PL-RS manager 745, an uplink transmission type manager 750, a TCI manager 755, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories) , may communicate, directly or indirectly, with one another (e.g., via one or more buses) .

The communications manager 720 may support wireless communications in accordance with examples as disclosed herein. The PHR status manager 725 is capable of, configured to, or operable to support a means for receiving a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold. In some examples, the PHR status manager 725 is capable of, configured to, or operable to support a means for selectively transmitting the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier. In some examples, the message includes an RRC message.

In some examples, the power control parameter manager 740 is capable of, configured to, or operable to support a means for receiving an indication of a power control parameter configured for at least one of an SRS transmission, a PUCCH transmission, or an PUSCH transmission, where the trigger-based PHR status indicating whether to enable transmission of the PHR is based on the power control parameter. In some examples, the power control parameter includes at least one of a pathloss value or a pathloss offset.

In some examples, the power control parameter manager 740 is capable of, configured to, or operable to support a means for receiving an indication of a power control parameter configured for an uplink TCI state, where the trigger-based PHR status indicating whether to enable transmission of the PHR is based on the power control parameter.

In some examples, to support receiving the message, the PL-RS manager 745 is capable of, configured to, or operable to support a means for detecting whether a pathloss reference signal is configured for at least one of: an SRS transmission, a PUCCH transmission, or an PUSCH transmission, where the trigger-based PHR status indicating whether to enable transmission of the PHR is based on the detecting. In some examples, to support receiving the message, the PL-RS manager 745 is capable of, configured to, or operable to support a means for detecting whether a pathloss reference signal is configured for an uplink TCI state, where the trigger-based PHR status indicating whether to enable transmission of the PHR is based on the detecting.

In some examples, to support selectively transmitting the PHR, the PHR status manager 725 is capable of, configured to, or operable to support a means for transmitting the PHR based on the trigger-based PHR status indicating to enable transmission of the PHR and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold.

In some examples, to support selectively transmitting the PHR, the PHR status manager 725 is capable of, configured to, or operable to support a means for detecting that the pathloss change on the at least one uplink carrier has satisfied the pathloss threshold. In some examples, to support selectively transmitting the PHR, the PHR status manager 725 is capable of, configured to, or operable to support a means for refraining from transmitting the PHR based on the trigger-based PHR status indicating to disable transmission of the PHR.

Additionally, or alternatively, the communications manager 720 may support wireless communications in accordance with examples as disclosed herein. The PHR selection manager 730 is capable of, configured to, or operable to support a means for transmitting a PHR in an PUSCH transmission on a first uplink carrier of the UE during a slot, where a set of PUSCH transmissions in a second uplink carrier overlap in a time domain in the slot with the PUSCH transmission on the first uplink carrier. In some examples, the PHR selection manager 730 is capable of, configured to, or operable to support a means for providing a PHR value for the second uplink carrier of the UE, the PHR value for the second uplink carrier including an actual PHR or a virtual PHR, where selection of the actual PHR or the virtual PHR for the second uplink carrier is based on an uplink transmission type of each PUSCH transmission in the set of PUSCH transmissions.

In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support a means for detecting that at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type. In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support a means for selecting the actual PHR for the second uplink carrier, where the actual PHR is based on the at least one PUSCH transmission being a first PUSCH transmission in the set of PUSCH transmissions that is associated with the specific uplink transmission type.

In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support a means for detecting that each PUSCH transmission in the set of PUSCH transmissions are associated with a non-specific transmission type. In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support a means for selecting the actual PHR for the second uplink carrier based on the detecting, where the actual PHR is based on a first PUSCH transmission in the set of PUSCH transmissions.

In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support a means for detecting that each PUSCH transmission in the set of PUSCH transmissions is associated with a non-specific uplink transmission type. In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support a means for selecting the virtual PHR for the second uplink carrier based on the detecting.

In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support a means for detecting that a first PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type. In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support a means for selecting the actual PHR for the second uplink carrier, where the actual PHR is based on the first PUSCH transmission in the set of PUSCH transmissions.

In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support a means for detecting that a first PUSCH transmission in the set of PUSCH transmissions is associated with a non-specific uplink transmission type. In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support a means for selecting the virtual PHR for the second uplink carrier based on the detecting.

In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support a means for detecting whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based on a pathloss reference signal being associated with the at least one PUSCH transmission and on a non-configuration status for a pathloss or a pathloss offset associated with the at least one PUSCH transmission.

In some examples, the TCI manager 755 is capable of, configured to, or operable to support a means for detecting at least one PUSCH transmission in the set of PUSCH transmissions based on an uplink TCI state associated with the at least one PUSCH transmission, where the uplink TCI state is associated with a downlink pathloss reference signal, a source downlink reference signal, a timing advance group identifier, any combination thereof.

In some examples, the grant manager 735 is capable of, configured to, or operable to support a means for detecting at least one PUSCH transmission in the set of PUSCH transmissions based on a grant scheduling the at least one PUSCH transmission.

In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support a means for detecting at least one PUSCH transmission in the set of PUSCH transmissions based on a pathloss, a pathloss offset, or both, being associated with the at least one PUSCH transmission. In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support a means for detecting at least one PUSCH transmission in the set of PUSCH transmissions based on an uplink TCI state associated with the at least one PUSCH transmission, where the uplink TCI state is associated with a pathloss, a pathloss offset, an SRS resource, a timing advance group identifier, or any combination thereof.

In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support a means for receiving an RRC message indicating a specific uplink transmission type.

Additionally, or alternatively, the communications manager 720 may support wireless communications in accordance with examples as disclosed herein. In some examples, the PHR selection manager 730 is capable of, configured to, or operable to support a means for selecting a virtual PHR for an uplink carrier, where a power control parameter is configured for the uplink carrier or a pathloss reference signal non-configuration status exists for at least one of an SRS resource set, a PUCCH, an PUSCH, or a TCI state, or any combination thereof, for the uplink carrier. In some examples, the PHR selection manager 730 is capable of, configured to, or operable to support a means for computing, based on the selecting, the virtual PHR based on a set of PUSCH reference parameters, a pathloss offset, or both.

In some examples, the TCI manager 755 is capable of, configured to, or operable to support a means for identifying the pathloss offset based on at least one of a default pathloss reference signal identifier, a default P0 nominal power level, a default uplink TCI state, a default pathloss value, an indicated TCI state, or any combination thereof.

In some examples, the TCI manager 755 is capable of, configured to, or operable to support a means for determining to use the pathloss offset for the virtual PHR based on an indicated TCI state of the UE, where the indicated TCI state is associated with the pathloss offset. In some examples, the TCI manager 755 is capable of, configured to, or operable to support a means for determining to use the set of PUSCH reference parameters for the virtual PHR based on an indicated TCI state of the UE, where the pathloss offset is in a non-configuration state for the indicated TCI state.

In some examples, the PHR selection manager 730 is capable of, configured to, or operable to support a means for receiving an RRC message indicating whether to use the pathloss offset for the virtual PHR.

Additionally, or alternatively, the communications manager 720 may support wireless communications in accordance with examples as disclosed herein. The grant manager 735 is capable of, configured to, or operable to support a means for selecting an actual PHR or a virtual PHR for transmission in a first PUSCH transmission on an uplink carrier of the UE, the selecting based on a previously received grant that schedules a second PUSCH transmission that is associated with an uplink transmission type, where previously received grant is received prior to or during a PDCCH monitoring occasion where the UE detects a grant that schedules the first PUSCH transmission on the first uplink carrier. In some examples, the grant manager 735 is capable of, configured to, or operable to support a means for transmitting the actual PHR or the virtual PHR in the first PUSCH transmission on the uplink carrier of the UE in accordance with the selecting.

In some examples, the grant manager 735 is capable of, configured to, or operable to support a means for selecting the actual PHR for transmission in the first PUSCH transmission based on the second PUSCH transmission being associated with a specific uplink transmission type, where the uplink transmission type includes the specific uplink transmission type.

In some examples, the grant manager 735 is capable of, configured to, or operable to support a means for selecting the virtual PHR for transmission in the first PUSCH transmission based on the second PUSCH transmission being associated with a non-specific uplink transmission type, where the uplink transmission type includes the non-specific uplink transmission type.

FIG. 8 shows a diagram of a system 800 including a device 805 that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure. The device 805 may be an example of or include the components of a device 505, a device 605, or a UE 115 as described herein. The device 805 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 805 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 820, an input/output (I/O) controller 810, a transceiver 815, an antenna 825, at least one memory 830, code 835, and at least one processor 840. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845) .

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

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

The at least one memory 830 may include random access memory (RAM) and read-only memory (ROM) . The at least one memory 830 may store computer-readable, computer-executable code 835 including instructions that, when executed by the at least one processor 840, cause the device 805 to perform various functions described herein. The code 835 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 835 may not be directly executable by the at least one processor 840 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 830 may contain, 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 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some cases, the at least one processor 840 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 840. The at least one processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting power headroom enhancement for dense uplink deployment) . For example, the device 805 or a component of the device 805 may include at least one processor 840 and at least one memory 830 coupled with or to the at least one processor 840, the at least one processor 840 and at least one memory 830 configured to perform various functions described herein. In some examples, the at least one processor 840 may include multiple processors and the at least one memory 830 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 840 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 840) and memory circuitry (which may include the at least one memory 830) ) , 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 840 or a processing system including the at least one processor 840 may be configured to, configurable to, or operable to cause the device 805 to perform one or more of the functions described herein. Further, as described herein, 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 830 or otherwise, to perform one or more of the functions described herein.

The communications manager 820 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 820 is capable of, configured to, or operable to support a means for receiving a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold. The communications manager 820 is capable of, configured to, or operable to support a means for selectively transmitting the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier.

Additionally, or alternatively, the communications manager 820 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 820 is capable of, configured to, or operable to support a means for transmitting a PHR in an PUSCH transmission on a first uplink carrier of the UE during a slot, where a set of PUSCH transmissions in a second uplink carrier overlap in a time domain in the slot with the PUSCH transmission on the first uplink carrier. The communications manager 820 is capable of, configured to, or operable to support a means for providing a PHR value for the second uplink carrier of the UE, the PHR value for the second uplink carrier including an actual PHR or a virtual PHR, where selection of the actual PHR or the virtual PHR for the second uplink carrier is based on an uplink transmission type of each PUSCH transmission in the set of PUSCH transmissions.

Additionally, or alternatively, the communications manager 820 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 820 is capable of, configured to, or operable to support a means for selecting a virtual PHR for an uplink carrier, where a power control parameter is configured for the uplink carrier or a pathloss reference signal non-configuration status exists for at least one of an SRS resource set, a PUCCH, an PUSCH, or a TCI state, or any combination thereof, for the uplink carrier. The communications manager 820 is capable of, configured to, or operable to support a means for computing, basing at least in part on the selecting, the virtual PHR based on a set of PUSCH reference parameters, a pathloss offset, or both.

Additionally, or alternatively, the communications manager 820 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 820 is capable of, configured to, or operable to support a means for selecting an actual PHR or a virtual PHR for transmission in a first PUSCH transmission on an uplink carrier of the UE, the selecting based on a previously received grant that schedules a second PUSCH transmission that is associated with an uplink transmission type, where previously received grant is received prior to or during a PDCCH monitoring occasion where the UE detects a grant that schedules the first PUSCH transmission on the first uplink carrier. The communications manager 820 is capable of, configured to, or operable to support a means for transmitting the actual PHR or the virtual PHR in the first PUSCH transmission on the uplink carrier of the UE in accordance with the selecting.

By including or configuring the communications manager 820 in accordance with examples as described herein, the device 805 may support techniques for improved PHR triggering and reporting in a dense uplink deployment scenario that is based, in some examples, on the uplink transmission type of the PUSCH transmission.

In some examples, the communications manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 815, the one or more antennas 825, or any combination thereof. Although the communications manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 820 may be supported by or performed by the at least one processor 840, the at least one memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions executable by the at least one processor 840 to cause the device 805 to perform various aspects of power headroom enhancement for dense uplink deployment as described herein, or the at least one processor 840 and the at least one memory 830 may be otherwise configured to, individually or collectively, perform or support such operations.

FIG. 9 shows a block diagram 900 of a device 905 that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure. The device 905 may be an example of aspects of a network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communications manager 920. The device 905, or one or more components of the device 905 (e.g., the receiver 910, the transmitter 915, and the communications manager 920) , may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .

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

The transmitter 915 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 905. For example, the transmitter 915 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) . In some examples, the transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include or be coupled with a modem.

The communications manager 920, the receiver 910, the transmitter 915, or various combinations thereof or various components thereof may be examples of means for performing various aspects of power headroom enhancement for dense uplink deployment as described herein. For example, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

In some examples, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .

Additionally, or alternatively, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functions of the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .

In some examples, the communications manager 920 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both. For example, the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager 920 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 920 is capable of, configured to, or operable to support a means for transmitting, to a UE, a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold. The communications manager 920 is capable of, configured to, or operable to support a means for selectively receiving the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier.

By including or configuring the communications manager 920 in accordance with examples as described herein, the device 905 (e.g., at least one processor controlling or otherwise coupled with the receiver 910, the transmitter 915, the communications manager 920, or a combination thereof) may support techniques for improved PHR triggering and reporting in a dense uplink deployment scenario that is based, in some examples, on the uplink transmission type of the PUSCH transmission.

FIG. 10 shows a block diagram 1000 of a device 1005 that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure. The device 1005 may be an example of aspects of a device 905 or a network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020. The device 1005, or one of more components of the device 1005 (e.g., the receiver 1010, the transmitter 1015, and the communications manager 1020) , may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .

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

The transmitter 1015 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1005. For example, the transmitter 1015 may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack) . In some examples, the transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include or be coupled with a modem.

The device 1005, or various components thereof, may be an example of means for performing various aspects of power headroom enhancement for dense uplink deployment as described herein. For example, the communications manager 1020 may include a trigger manager 1025 an PHR manager 1030, or any combination thereof. The communications manager 1020 may be an example of aspects of a communications manager 920 as described herein. In some examples, the communications manager 1020, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager 1020 may support wireless communications in accordance with examples as disclosed herein. The trigger manager 1025 is capable of, configured to, or operable to support a means for transmitting, to a UE, a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold. The PHR manager 1030 is capable of, configured to, or operable to support a means for selectively receiving the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier.

FIG. 11 shows a block diagram 1100 of a communications manager 1120 that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure. The communications manager 1120 may be an example of aspects of a communications manager 920, a communications manager 1020, or both, as described herein. The communications manager 1120, or various components thereof, may be an example of means for performing various aspects of power headroom enhancement for dense uplink deployment as described herein. For example, the communications manager 1120 may include a trigger manager 1125, an PHR manager 1130, a power control parameter manager 1135, a PL-RS manager 1140, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories) , may communicate, directly or indirectly, with one another (e.g., via one or more buses) which may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105) , or any combination thereof.

The communications manager 1120 may support wireless communications in accordance with examples as disclosed herein. The trigger manager 1125 is capable of, configured to, or operable to support a means for transmitting, to a UE, a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold. The PHR manager 1130 is capable of, configured to, or operable to support a means for selectively receiving the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier. In some examples, the message includes an RRC message.

In some examples, the power control parameter manager 1135 is capable of, configured to, or operable to support a means for transmitting an indication of a power control parameter configured for at least one of an SRS transmission, a PUCCH transmission, or an PUSCH transmission, where the trigger-based PHR status indicating whether to enable transmission of the PHR is based on the power control parameter. In some examples, the power control parameter includes at least one of a pathloss value or a pathloss offset.

In some examples, the power control parameter manager 1135 is capable of, configured to, or operable to support a means for transmitting an indication of a power control parameter configured for an uplink TCI state, where the trigger-based PHR status indicating whether to enable transmission of the PHR is based on the power control parameter.

In some examples, to support receiving the message, the PL-RS manager 1140 is capable of, configured to, or operable to support a means for detecting whether a pathloss reference signal is configured for at least one of: an SRS transmission, a PUCCH transmission, or an PUSCH transmission, where the trigger-based PHR status indicating whether to enable transmission of the PHR is based on the detecting. In some examples, to support transmitting the message, the PL-RS manager 1140 is capable of, configured to, or operable to support a means for detecting whether a pathloss reference signal is configured for an uplink TCI state, where the trigger-based PHR status indicating whether to enable transmission of the PHR is based on the detecting.

In some examples, to support selectively receiving the PHR, the trigger manager 1125 is capable of, configured to, or operable to support a means for receiving the PHR based on the trigger-based PHR status indicating to enable transmission of the PHR and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold. In some examples, to support selectively receiving the PHR, the trigger manager 1125 is capable of, configured to, or operable to support a means for refraining from receiving the PHR based on the trigger-based PHR status indicating to disable transmission of the PHR.

FIG. 12 shows a diagram of a system 1200 including a device 1205 that supports power headroom enhancement for dense uplink deployment in accordance with one or more aspects of the present disclosure. The device 1205 may be an example of or include the components of a device 905, a device 1005, or a network entity 105 as described herein. The device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support outputting and obtaining communications, such as a communications manager 1220, a transceiver 1210, an antenna 1215, at least one memory 1225, code 1230, and at least one processor 1235. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1240) .

The transceiver 1210 may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently) . The transceiver 1210 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1215, by a wired transmitter) , to receive modulated signals (e.g., from one or more antennas 1215, from a wired receiver) , and to demodulate signals. In some implementations, the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1215 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1215 that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1210 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 1210, or the transceiver 1210 and the one or more antennas 1215, or the transceiver 1210 and the one or more antennas 1215 and one or more processors or one or more memory components (e.g., the at least one processor 1235, the at least one memory 1225, or both) , may be included in a chip or chip assembly that is installed in the device 1205. In some examples, the transceiver 1210 may be operable to support communications via one or more communications links (e.g., a communication link 125, a backhaul communication link 120, a midhaul communication link 162, a fronthaul communication link 168) .

The at least one memory 1225 may include RAM, ROM, or any combination thereof. The at least one memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by one or more of the at least one processor 1235, cause the device 1205 to perform various functions described herein. The code 1230 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1230 may not be directly executable by a processor of the at least one processor 1235 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1225 may contain, 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 1235 may include multiple processors and the at least one memory 1225 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 (for example, as part of a processing system) .

The at least one processor 1235 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, a discrete hardware component, or any combination thereof) . In some cases, the at least one processor 1235 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 1235. The at least one processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1225) to cause the device 1205 to perform various functions (e.g., functions or tasks supporting power headroom enhancement for dense uplink deployment) . For example, the device 1205 or a component of the device 1205 may include at least one processor 1235 and at least one memory 1225 coupled with one or more of the at least one processor 1235, the at least one processor 1235 and the at least one memory 1225 configured to perform various functions described herein. The at least one processor 1235 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1230) to perform the functions of the device 1205. The at least one processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1205 (such as within one or more of the at least one memory 1225) . In some examples, the at least one processor 1235 may include multiple processors and the at least one memory 1225 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 1235 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 1235) and memory circuitry (which may include the at least one memory 1225) ) , 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 1235 or a processing system including the at least one processor 1235 may be configured to, configurable to, or operable to cause the device 1205 to perform one or more of the functions described herein. Further, as described herein, 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 1225 or otherwise, to perform one or more of the functions described herein.

In some examples, a bus 1240 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1240 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack) , which may include communications performed within a component of the device 1205, or between different components of the device 1205 that may be co-located or located in different locations (e.g., where the device 1205 may refer to a system in which one or more of the communications manager 1220, the transceiver 1210, the at least one memory 1225, the code 1230, and the at least one processor 1235 may be located in one of the different components or divided between different components) .

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

The communications manager 1220 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1220 is capable of, configured to, or operable to support a means for transmitting, to a UE, a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold. The communications manager 1220 is capable of, configured to, or operable to support a means for selectively receiving the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier.

By including or configuring the communications manager 1220 in accordance with examples as described herein, the device 1205 may support techniques for improved PHR triggering and reporting in a dense uplink deployment scenario that is based, in some examples, on the uplink transmission type of the PUSCH transmission.

In some examples, the communications manager 1220 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1210, the one or more antennas 1215 (e.g., where applicable) , or any combination thereof. Although the communications manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1220 may be supported by or performed by the transceiver 1210, one or more of the at least one processor 1235, one or more of the at least one memory 1225, the code 1230, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1235, the at least one memory 1225, the code 1230, or any combination thereof) . For example, the code 1230 may include instructions executable by one or more of the at least one processor 1235 to cause the device 1205 to perform various aspects of power headroom enhancement for dense uplink deployment as described herein, or the at least one processor 1235 and the at least one memory 1225 may be otherwise configured to, individually or collectively, perform or support such operations.

FIG. 13 shows a flowchart illustrating a method 1300 that supports power headroom enhancement for dense uplink deployment in accordance with aspects of the present disclosure. The operations of the method 1300 may be implemented by a UE or its components as described herein. For example, the operations of the method 1300 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. 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 1305, the method may include receiving a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold. The operations of block 1305 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed by an PHR status manager 725 as described with reference to FIG. 7.

At 1310, the method may include selectively transmitting the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier. The operations of block 1310 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by an PHR status manager 725 as described with reference to FIG. 7.

FIG. 14 shows a flowchart illustrating a method 1400 that supports power headroom enhancement for dense uplink deployment in accordance with aspects of the present disclosure. The operations of the method 1400 may be implemented by a UE or its components as described herein. For example, the operations of the method 1400 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. 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 transmitting a PHR in an PUSCH transmission on a first uplink carrier of the UE during a slot, where a set of PUSCH transmissions in a second uplink carrier overlap in a time domain in the slot with the PUSCH transmission on the first uplink carrier. The operations of block 1405 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed by an PHR selection manager 730 as described with reference to FIG. 7.

At 1410, the method may include providing a PHR value for the second uplink carrier of the UE, the PHR value for the second uplink carrier including an actual PHR or a virtual PHR, where selection of the actual PHR or the virtual PHR for the second uplink carrier is based on an uplink transmission type of each PUSCH transmission in the set of PUSCH transmissions. The operations of block 1410 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by an PHR selection manager 730 as described with reference to FIG. 7.

FIG. 15 shows a flowchart illustrating a method 1500 that supports power headroom enhancement for dense uplink deployment in accordance with aspects of the present disclosure. The operations of the method 1500 may be implemented by a UE or its components as described herein. For example, the operations of the method 1500 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. 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 1505, the method may include selecting a virtual PHR for an uplink carrier, where a power control parameter is configured for the uplink carrier or a pathloss reference signal non-configuration status exists for at least one of an SRS resource set, a PUCCH, an PUSCH, or a transmission configuration indicator (TCI) state, or any combination thereof, for the uplink carrier. The operations of block 1505 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed by an PHR selection manager 730 as described with reference to FIG. 7.

At 1510, the method may include computing, based on the selecting, the virtual PHR based on a set of PUSCH reference parameters, a pathloss offset, or both. The operations of block 1510 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by an PHR selection manager 730 as described with reference to FIG. 7.

FIG. 16 shows a flowchart illustrating a method 1600 that supports power headroom enhancement for dense uplink deployment in accordance with aspects of the present disclosure. The operations of the method 1600 may be implemented by a UE or its components as described herein. For example, the operations of the method 1600 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. 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 1605, the method may include selecting an actual PHR or a virtual PHR for transmission in a first PUSCH transmission on an uplink carrier of the UE, the selecting based on a previously received grant that schedules a second PUSCH transmission that is associated with an uplink transmission type, where previously received grant is received prior to or during a PDCCH monitoring occasion where the UE detects a grant that schedules the first PUSCH transmission on the first uplink carrier. The operations of block 1605 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed by a grant manager 735 as described with reference to FIG. 7.

At 1610, the method may include transmitting the actual PHR or the virtual PHR in the first PUSCH transmission on the uplink carrier of the UE in accordance with the selecting. The operations of block 1610 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed by a grant manager 735 as described with reference to FIG. 7.

FIG. 17 shows a flowchart illustrating a method 1700 that supports power headroom enhancement for dense uplink deployment in accordance with aspects of the present disclosure. The operations of the method 1700 may be implemented by a network entity or its components as described herein. For example, the operations of the method 1700 may be performed by a network entity as described with reference to FIGs. 1 through 4 and 9 through 12. 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 1705, the method may include transmitting, to a UE, a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold. The operations of block 1705 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed by a trigger manager 1125 as described with reference to FIG. 11.

At 1710, the method may include selectively receiving the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier. The operations of block 1710 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by an PHR manager 1130 as described with reference to FIG. 11.

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

Aspect 1: A method for wireless communications at a UE, comprising: receiving a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold; and selectively transmitting the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier.

Aspect 2: The method of aspect 1, wherein the message comprises an RRC message.

Aspect 3: The method of any of aspects 1 through 2, further comprising: receiving an indication of a power control parameter configured for at least one of an SRS transmission, a PUCCH transmission, or an PUSCH transmission, wherein the trigger-based PHR status indicating whether to enable transmission of the PHR is based at least in part on the power control parameter.

Aspect 4: The method of aspect 3, wherein the power control parameter comprises at least one of a pathloss value or a pathloss offset.

Aspect 5: The method of any of aspects 1 through 4, further comprising: receiving an indication of a power control parameter configured for an uplink TCI state, wherein the trigger-based PHR status indicating whether to enable transmission of the PHR is based at least in part on the power control parameter.

Aspect 6: The method of any of aspects 1 through 5, wherein receiving the message comprises: detecting whether a pathloss reference signal is configured for at least one of: an SRS transmission, a PUCCH transmission, or an PUSCH transmission, wherein the trigger-based PHR status indicating whether to enable transmission of the PHR is based at least in part on the detecting.

Aspect 7: The method of any of aspects 1 through 6, wherein receiving the message comprises: detecting whether a pathloss reference signal is configured for an uplink TCI state, wherein the trigger-based PHR status indicating whether to enable transmission of the PHR is based at least in part on the detecting.

Aspect 8: The method of any of aspects 1 through 7, wherein selectively transmitting the PHR comprises: transmitting the PHR based at least in part on the trigger-based PHR status indicating to enable transmission of the PHR and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold.

Aspect 9: The method of any of aspects 1 through 8, wherein selectively transmitting the PHR comprises: detecting that the pathloss change on the at least one uplink carrier has satisfied the pathloss threshold; and refraining from transmitting the PHR based at least in part on the trigger-based PHR status indicating to disable transmission of the PHR.

Aspect 10: A method for wireless communications at a UE, comprising: transmitting a PHR in an PUSCH transmission on a first uplink carrier of the UE during a slot, wherein a set of PUSCH transmissions in a second uplink carrier overlap in a time domain in the slot with the PUSCH transmission on the first uplink carrier; and providing a PHR value for the second uplink carrier of the UE, the PHR value for the second uplink carrier comprising an actual PHR or a virtual PHR, wherein selection of the actual PHR or the virtual PHR for the second uplink carrier is based at least in part on an uplink transmission type of each PUSCH transmission in the set of PUSCH transmissions.

Aspect 11: The method of aspect 10, further comprising: detecting that at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type; and selecting the actual PHR for the second uplink carrier, wherein the actual PHR is based on the at least one PUSCH transmission being a first PUSCH transmission in the set of PUSCH transmissions that is associated with the specific uplink transmission type.

Aspect 12: The method of any of aspects 10 through 11, further comprising: detecting that each PUSCH transmission in the set of PUSCH transmissions are associated with a non-specific transmission type; and selecting the actual PHR for the second uplink carrier based at least in part on the detecting, wherein the actual PHR is based at least in part on a first PUSCH transmission in the set of PUSCH transmissions.

Aspect 13: The method of any of aspects 10 through 12, further comprising: detecting that each PUSCH transmission in the set of PUSCH transmissions is associated with a non-specific uplink transmission type; and selecting the virtual PHR for the second uplink carrier based at least in part on the detecting.

Aspect 14: The method of any of aspects 10 through 13, further comprising: detecting that a first PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type; and selecting the actual PHR for the second uplink carrier, wherein the actual PHR is based at least in part on the first PUSCH transmission in the set of PUSCH transmissions.

Aspect 15: The method of any of aspects 10 through 14, further comprising: detecting that a first PUSCH transmission in the set of PUSCH transmissions is associated with a non-specific uplink transmission type; and selecting the virtual PHR for the second uplink carrier based at least in part on the detecting.

Aspect 16: The method of any of aspects 10 through 15, further comprising: detecting whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on a pathloss reference signal being associated with the at least one PUSCH transmission and on a non-configuration status for a pathloss or a pathloss offset associated with the at least one PUSCH transmission.

Aspect 17: The method of any of aspects 10 through 16, further comprising: detecting whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on an uplink TCI state associated with the at least one PUSCH transmission, wherein the uplink TCI state is associated with a downlink pathloss reference signal, a source downlink reference signal, a timing advance group identifier, any combination thereof.

Aspect 18: The method of any of aspects 10 through 17, further comprising: detecting whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on a grant scheduling the at least one PUSCH transmission.

Aspect 19: The method of any of aspects 10 through 18, further comprising: detecting whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on a pathloss, a pathloss offset, or both, being associated with the at least one PUSCH transmission.

Aspect 20: The method of any of aspects 10 through 19, further comprising: detecting whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on an uplink TCI state associated with the at least one PUSCH transmission, wherein the uplink TCI state is associated with a pathloss, a pathloss offset, an SRS resource, a timing advance group identifier, or any combination thereof.

Aspect 21: The method of any of aspects 10 through 20, further comprising: receiving an RRC message indicating a specific uplink transmission type.

Aspect 22: A method for wireless communications at a UE, comprising: selecting a virtual PHR for an uplink carrier, wherein a power control parameter is configured for the uplink carrier or a pathloss reference signal non-configuration status exists for at least one of an SRS resource set, a PUCCH, an PUSCH, or a TCI state, or any combination thereof, for the uplink carrier; and computing, based at least in part on the selecting, the virtual PHR based at least in part on a set of PUSCH reference parameters, a pathloss offset, or both.

Aspect 23: The method of aspect 22, further comprising: identifying the pathloss offset based on at least one of a default pathloss reference signal identifier, a default P0 nominal power level, a default uplink TCI state, a default pathloss value, an indicated TCI state, or any combination thereof.

Aspect 24: The method of any of aspects 22 through 23, further comprising: determining to use the pathloss offset for the virtual PHR based at least in part on an indicated TCI state of the UE, wherein the indicated TCI state is associated with the pathloss offset.

Aspect 25: The method of any of aspects 22 through 24, further comprising: determining to use the set of PUSCH reference parameters for the virtual PHR based at least in part on an indicated TCI state of the UE, wherein the pathloss offset is in a non-configuration state for the indicated TCI state.

Aspect 26: The method of any of aspects 22 through 25, further comprising: receiving an RRC message indicating whether to use the pathloss offset for the virtual PHR.

Aspect 27: A method for wireless communications at a UE, comprising: selecting an actual PHR or a virtual PHR for transmission in a first PUSCH transmission on an uplink carrier of the UE, the selecting based at least in part on a previously received grant that schedules a second PUSCH transmission that is associated with an uplink transmission type, wherein previously received grant is received prior to or during a PDCCH monitoring occasion where the UE detects a grant that schedules the first PUSCH transmission on the first uplink carrier; and transmitting the actual PHR or the virtual PHR in the first PUSCH transmission on the uplink carrier of the UE in accordance with the selecting.

Aspect 28: The method of aspect 27, further comprising: selecting the actual PHR for transmission in the first PUSCH transmission based at least in part on the second PUSCH transmission being associated with a specific uplink transmission type, wherein the uplink transmission type comprises the specific uplink transmission type.

Aspect 29: The method of any of aspects 27 through 28, further comprising: selecting the virtual PHR for transmission in the first PUSCH transmission based at least in part on the second PUSCH transmission being associated with a non-specific uplink transmission type, wherein the uplink transmission type comprises the non-specific uplink transmission type.

Aspect 30: A method for wireless communications at a network entity, comprising: transmitting, to a UE, a message indicating a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether to enable transmission of a PHR triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold; and selectively receiving the PHR in accordance with the trigger-based PHR status and the pathloss change on the at least one uplink carrier.

Aspect 31: The method of aspect 30, wherein the message comprises an RRC message.

Aspect 32: The method of any of aspects 30 through 31, further comprising: transmitting an indication of a power control parameter configured for at least one of an SRS transmission, a PUCCH transmission, or an PUSCH transmission, wherein the trigger-based PHR status indicating whether to enable transmission of the PHR is based at least in part on the power control parameter.

Aspect 33: The method of aspect 32, wherein the power control parameter comprises at least one of a pathloss value or a pathloss offset.

Aspect 34: The method of any of aspects 30 through 33, further comprising: transmitting an indication of a power control parameter configured for an uplink TCI state, wherein the trigger-based PHR status indicating whether to enable transmission of the PHR is based at least in part on the power control parameter.

Aspect 35: The method of any of aspects 30 through 34, wherein receiving the message comprises: detecting whether a pathloss reference signal is configured for at least one of: an SRS transmission, a PUCCH transmission, or an PUSCH transmission, wherein the trigger-based PHR status indicating whether to enable transmission of the PHR is based at least in part on the detecting.

Aspect 36: The method of any of aspects 30 through 35, wherein transmitting the message comprises: detecting whether a pathloss reference signal is configured for an uplink TCI state, wherein the trigger-based PHR status indicating whether to enable transmission of the PHR is based at least in part on the detecting.

Aspect 37: The method of any of aspects 30 through 36, wherein selectively receiving the PHR comprises: receiving the PHR based at least in part on the trigger-based PHR status indicating to enable transmission of the PHR and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold.

Aspect 38: The method of any of aspects 30 through 37, wherein selectively receiving the PHR comprises: refraining from receiving the PHR based at least in part on the trigger-based PHR status indicating to disable transmission of the PHR.

Aspect 39: A UE for wireless communications, comprising 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 through 9.

Aspect 40: A UE for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 9.

Aspect 41: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 9.

Aspect 42: A UE for wireless communications, comprising 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 10 through 21.

Aspect 43: A UE for wireless communications, comprising at least one means for performing a method of any of aspects 10 through 21.

Aspect 44: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 10 through 21.

Aspect 45: A UE for wireless communications, comprising 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 22 through 26.

Aspect 46: A UE for wireless communications, comprising at least one means for performing a method of any of aspects 22 through 26.

Aspect 47: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 22 through 26.

Aspect 48: A UE for wireless communications, comprising 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 27 through 29.

Aspect 49: A UE for wireless communications, comprising at least one means for performing a method of any of aspects 27 through 29.

Aspect 50: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 27 through 29.

Aspect 51: A network entity for wireless communications, comprising 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 30 through 38.

Aspect 52: A network entity for wireless communications, comprising at least one means for performing a method of any of aspects 30 through 38.

Aspect 53: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 30 through 38.

It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that 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, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, 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 may also 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 (e.g., 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 (i.e., A and 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, ” “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” 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 (e.g., receiving information) , accessing (e.g., 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 instances, 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:

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:

receive a message indicating a trigger-based power headroom report status of the UE, the trigger-based power headroom report status indicating whether to enable transmission of a power headroom report triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold; and

selectively transmit the power headroom report in accordance with the trigger-based power headroom report status and the pathloss change on the at least one uplink carrier.
The UE of claim 1, wherein the message comprises a radio resource control (RRC) message.
The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

receive an indication of a power control parameter configured for at least one of a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The UE of claim 3, wherein the power control parameter comprises at least one of a pathloss value or a pathloss offset.
The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

receive an indication of a power control parameter configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The UE of claim 1, wherein, to receive the message, the one or more processors are individually or collectively operable to execute the code to cause the UE to:

detect whether a pathloss reference signal is configured for at least one of: a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The UE of claim 1, wherein, to receive the message, the one or more processors are individually or collectively operable to execute the code to cause the UE to:

detect whether a pathloss reference signal is configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The UE of claim 1, wherein, to selectively transmit the power headroom report, the one or more processors are individually or collectively operable to execute the code to cause the UE to:

transmit the power headroom report based at least in part on the trigger-based power headroom report status indicating to enable transmission of the power headroom report and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold.
The UE of claim 1, wherein, to selectively transmit the power headroom report, the one or more processors are individually or collectively operable to execute the code to cause the UE to:

detect that the pathloss change on the at least one uplink carrier has satisfied the pathloss threshold; and

refrain from transmitting the power headroom report based at least in part on the trigger-based power headroom report status indicating to disable transmission of the power headroom report.
A user equipment (UE) , comprising:

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:

transmit a power headroom report in a physical uplink shared channel (PUSCH) transmission on a first uplink carrier of the UE during a slot, wherein a set of PUSCH transmissions in a second uplink carrier overlap in a time domain in the slot with the PUSCH transmission on the first uplink carrier; and

provide a power headroom report value for the second uplink carrier of the UE, the power headroom report value for the second uplink carrier comprising an actual power headroom report or a virtual power headroom report, wherein selection of the actual power headroom report or the virtual power headroom report for the second uplink carrier is based at least in part on an uplink transmission type of each PUSCH transmission in the set of PUSCH transmissions.
The UE of claim 10, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

detect that at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type; and

select the actual power headroom report for the second uplink carrier, wherein the actual power headroom report is based on the at least one PUSCH transmission being a first PUSCH transmission in the set of PUSCH transmissions that is associated with the specific uplink transmission type.
The UE of claim 10, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

detect that each PUSCH transmission in the set of PUSCH transmissions are associated with a non-specific transmission type; and

select the actual power headroom report for the second uplink carrier based at least in part on the detecting, wherein the actual power headroom report is based at least in part on a first PUSCH transmission in the set of PUSCH transmissions.
The UE of claim 10, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

detect that each PUSCH transmission in the set of PUSCH transmissions is associated with a non-specific uplink transmission type; and

select the virtual power headroom report for the second uplink carrier based at least in part on the detecting.
The UE of claim 10, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

detect that a first PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type; and

select the actual power headroom report for the second uplink carrier, wherein the actual power headroom report is based at least in part on the first PUSCH transmission in the set of PUSCH transmissions.
The UE of claim 10, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

detect that a first PUSCH transmission in the set of PUSCH transmissions is associated with a non-specific uplink transmission type; and

select the virtual power headroom report for the second uplink carrier based at least in part on the detecting.
The UE of claim 10, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on a pathloss reference signal being associated with the at least one PUSCH transmission and on a non-configuration status for a pathloss or a pathloss offset associated with the at least one PUSCH transmission.
The UE of claim 10, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on an uplink transmission configuration indicator (TCI) state associated with the at least one PUSCH transmission, wherein the uplink TCI state is associated with a downlink pathloss reference signal, a source downlink reference signal, a timing advance group identifier, any combination thereof.
The UE of claim 10, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on a grant scheduling the at least one PUSCH transmission.
The UE of claim 10, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on a pathloss, a pathloss offset, or both, being associated with the at least one PUSCH transmission.
The UE of claim 10, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on an uplink transmission configuration indicator (TCI) state associated with the at least one PUSCH transmission, wherein the uplink TCI state is associated with a pathloss, a pathloss offset, a sounding reference signal (SRS) resource, a timing advance group identifier, or any combination thereof.
The UE of claim 10, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

receive a radio resource control (RRC) message indicating a specific uplink transmission type.
A user equipment (UE) , comprising:

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:

select a virtual power headroom report for an uplink carrier, wherein a power control parameter is configured for the uplink carrier or a pathloss reference signal non-configuration status exists for at least one of a sounding reference signal (SRS) resource set, a physical uplink control channel (PUCCH) , a physical uplink shared channel (PUSCH) , or a transmission configuration indicator (TCI) state, or any combination thereof, for the uplink carrier; and

computing, base at least in part on the selecting, the virtual power headroom report based at least in part on a set of PUSCH reference parameters, a pathloss offset, or both.
The UE of claim 22, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

identify the pathloss offset based on at least one of a default pathloss reference signal identifier, a default P0 nominal power level, a default uplink transmission configuration indicator (TCI) state, a default pathloss value, an indicated TCI state, or any combination thereof.
The UE of claim 22, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

determine to use the pathloss offset for the virtual power headroom report based at least in part on an indicated TCI state of the UE, wherein the indicated TCI state is associated with the pathloss offset.
The UE of claim 22, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

determine to use the set of PUSCH reference parameters for the virtual power headroom report based at least in part on an indicated TCI state of the UE, wherein the pathloss offset is in a non-configuration state for the indicated TCI state.
The UE of claim 22, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

receive a radio resource control (RRC) message indicating whether to use the pathloss offset for the virtual power headroom report.
A user equipment (UE) , comprising:

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:

select an actual power headroom report or a virtual power headroom report for transmission in a first physical uplink shared channel (PUSCH) transmission on an uplink carrier of the UE, the selecting based at least in part on a previously received grant that schedules a second PUSCH transmission that is associated with an uplink transmission type, wherein previously received grant is received prior to or during a physical downlink control channel (PDCCH) monitoring occasion where the UE detects a grant that schedules the first PUSCH transmission on the uplink carrier; and

transmit the actual power headroom report or the virtual power headroom report in the first PUSCH transmission on the uplink carrier of the UE in accordance with the selecting.
The UE of claim 27, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

select the actual power headroom report for transmission in the first PUSCH transmission based at least in part on the second PUSCH transmission being associated with a specific uplink transmission type, wherein the uplink transmission type comprises the specific uplink transmission type.
The UE of claim 27, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:

select the virtual power headroom report for transmission in the first PUSCH transmission based at least in part on the second PUSCH transmission being associated with a non-specific uplink transmission type, wherein the uplink transmission type comprises the non-specific uplink transmission type.
A network entity, comprising:

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:

transmit, to a user equipment (UE) , a message indicating a trigger-based power headroom report status of the UE, the trigger-based power headroom report status indicating whether to enable transmission of a power headroom report triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold; and

selectively receive the power headroom report in accordance with the trigger-based power headroom report status and the pathloss change on the at least one uplink carrier.
The network entity of claim 30, wherein the message comprises a radio resource control (RRC) message.
The network entity of claim 30, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:

transmit an indication of a power control parameter configured for at least one of a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The network entity of claim 32, wherein the power control parameter comprises at least one of a pathloss value or a pathloss offset.
The network entity of claim 30, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:

transmit an indication of a power control parameter configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The network entity of claim 30, wherein, to receive the message, the one or more processors are individually or collectively operable to execute the code to cause the network entity to:

detect whether a pathloss reference signal is configured for at least one of: a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The network entity of claim 30, wherein, to transmit the message, the one or more processors are individually or collectively operable to execute the code to cause the network entity to:

detect whether a pathloss reference signal is configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The network entity of claim 30, wherein, to selectively receive the power headroom report, the one or more processors are individually or collectively operable to execute the code to cause the network entity to:

receive the power headroom report based at least in part on the trigger-based power headroom report status indicating to enable transmission of the power headroom report and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold.
The network entity of claim 30, wherein, to selectively receive the power headroom report, the one or more processors are individually or collectively operable to execute the code to cause the network entity to:

refrain from receiving the power headroom report based at least in part on the trigger-based power headroom report status indicating to disable transmission of the power headroom report.
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:

transmit a power headroom report in a physical uplink shared channel (PUSCH) transmission on a first uplink carrier of the UE during a slot, wherein a set of PUSCH transmissions in a second uplink carrier overlap in a time domain in the slot with the PUSCH transmission on the first uplink carrier; and

provide a power headroom report value for the second uplink carrier of the UE, the power headroom report value for the second uplink carrier comprising an actual power headroom report or a virtual power headroom report, wherein selection of the actual power headroom report or the virtual power headroom report for the second uplink carrier is based at least in part on an uplink transmission type of each PUSCH transmission in the set of PUSCH transmissions.
The UE of claim 39, wherein the processing system is further configured to cause the UE to:

detect that at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type; and

select the actual power headroom report for the second uplink carrier, wherein the actual power headroom report is based on the at least one PUSCH transmission being a first PUSCH transmission in the set of PUSCH transmissions that is associated with the specific uplink transmission type.
The UE of claim 39, wherein the processing system is further configured to cause the UE to:

detect that each PUSCH transmission in the set of PUSCH transmissions are associated with a non-specific transmission type; and

select the actual power headroom report for the second uplink carrier based at least in part on the detecting, wherein the actual power headroom report is based at least in part on a first PUSCH transmission in the set of PUSCH transmissions.
The UE of claim 39, wherein the processing system is further configured to cause the UE to:

detect that each PUSCH transmission in the set of PUSCH transmissions is associated with a non-specific uplink transmission type; and

select the virtual power headroom report for the second uplink carrier based at least in part on the detecting.
The UE of claim 39, wherein the processing system is further configured to cause the UE to:

detect that a first PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type; and

select the actual power headroom report for the second uplink carrier, wherein the actual power headroom report is based at least in part on the first PUSCH transmission in the set of PUSCH transmissions.
The UE of claim 39, wherein the processing system is further configured to cause the UE to:

detect that a first PUSCH transmission in the set of PUSCH transmissions is associated with a non-specific uplink transmission type; and

select the virtual power headroom report for the second uplink carrier based at least in part on the detecting.
The UE of claim 39, wherein the processing system is further configured to cause the UE to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on a pathloss reference signal being associated with the at least one PUSCH transmission and on a non-configuration status for a pathloss or a pathloss offset associated with the at least one PUSCH transmission.
The UE of claim 39, wherein the processing system is further configured to cause the UE to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on an uplink transmission configuration indicator (TCI) state associated with the at least one PUSCH transmission, wherein the uplink TCI state is associated with a downlink pathloss reference signal, a source downlink reference signal, a timing advance group identifier, any combination thereof.
The UE of claim 39, wherein the processing system is further configured to cause the UE to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on a grant scheduling the at least one PUSCH transmission.
The UE of claim 39, wherein the processing system is further configured to cause the UE to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on a pathloss, a pathloss offset, or both, being associated with the at least one PUSCH transmission.
The UE of claim 39, wherein the processing system is further configured to cause the UE to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on an uplink transmission configuration indicator (TCI) state associated with the at least one PUSCH transmission, wherein the uplink TCI state is associated with a pathloss, a pathloss offset, a sounding reference signal (SRS) resource, a timing advance group identifier, or any combination thereof.
The UE of claim 39, wherein the processing system is further configured to cause the UE to:

receive a radio resource control (RRC) message indicating a specific uplink transmission type.
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:

select a virtual power headroom report for an uplink carrier, wherein a power control parameter is configured for the uplink carrier or a pathloss reference signal non-configuration status exists for at least one of a sounding reference signal (SRS) resource set, a physical uplink control channel (PUCCH) , a physical uplink shared channel (PUSCH) , or a transmission configuration indicator (TCI) state, or any combination thereof, for the uplink carrier; and

computing, base at least in part on the selecting, the virtual power headroom report based at least in part on a set of PUSCH reference parameters, a pathloss offset, or both.
The UE of claim 51, wherein the processing system is further configured to cause the UE to:

identify the pathloss offset based on at least one of a default pathloss reference signal identifier, a default P0 nominal power level, a default uplink transmission configuration indicator (TCI) state, a default pathloss value, an indicated TCI state, or any combination thereof.
The UE of claim 51, wherein the processing system is further configured to cause the UE to:

determine to use the pathloss offset for the virtual power headroom report based at least in part on an indicated TCI state of the UE, wherein the indicated TCI state is associated with the pathloss offset.
The UE of claim 51, wherein the processing system is further configured to cause the UE to:

determine to use the set of PUSCH reference parameters for the virtual power headroom report based at least in part on an indicated TCI state of the UE, wherein the pathloss offset is in a non-configuration state for the indicated TCI state.
The UE of claim 51, wherein the processing system is further configured to cause the UE to:

receive a radio resource control (RRC) message indicating whether to use the pathloss offset for the virtual power headroom report.
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:

select an actual power headroom report or a virtual power headroom report for transmission in a first physical uplink shared channel (PUSCH) transmission on an uplink carrier of the UE, the selecting based at least in part on a previously received grant that schedules a second PUSCH transmission that is associated with an uplink transmission type, wherein previously received grant is received prior to or during a physical downlink control channel (PDCCH) monitoring occasion where the UE detects a grant that schedules the first PUSCH transmission on the uplink carrier; and

transmit the actual power headroom report or the virtual power headroom report in the first PUSCH transmission on the uplink carrier of the UE in accordance with the selecting.
The UE of claim 56, wherein the processing system is further configured to cause the UE to:

select the actual power headroom report for transmission in the first PUSCH transmission based at least in part on the second PUSCH transmission being associated with a specific uplink transmission type, wherein the uplink transmission type comprises the specific uplink transmission type.
The UE of claim 56, wherein the processing system is further configured to cause the UE to:

select the virtual power headroom report for transmission in the first PUSCH transmission based at least in part on the second PUSCH transmission being associated with a non-specific uplink transmission type, wherein the uplink transmission type comprises the non-specific uplink transmission type.
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:

transmit, to a user equipment (UE) , a message indicating a trigger-based power headroom report status of the UE, the trigger-based power headroom report status indicating whether to enable transmission of a power headroom report triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold; and

selectively receive the power headroom report in accordance with the trigger-based power headroom report status and the pathloss change on the at least one uplink carrier.
The network entity of claim 59, wherein the message comprises a radio resource control (RRC) message.
The network entity of claim 59, wherein the processing system is further configured to cause the network entity to:

transmit an indication of a power control parameter configured for at least one of a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The network entity of claim 61, wherein the power control parameter comprises at least one of a pathloss value or a pathloss offset.
The network entity of claim 59, wherein the processing system is further configured to cause the network entity to:

transmit an indication of a power control parameter configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The network entity of claim 59, wherein, to receive the message, the processing system is configured to cause the network entity to:

detect whether a pathloss reference signal is configured for at least one of: a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The network entity of claim 59, wherein, to transmit the message, the processing system is configured to cause the network entity to:

detect whether a pathloss reference signal is configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The network entity of claim 59, wherein, to selectively receive the power headroom report, the processing system is configured to cause the network entity to:

receive the power headroom report based at least in part on the trigger-based power headroom report status indicating to enable transmission of the power headroom report and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold.
The network entity of claim 59, wherein, to selectively receive the power headroom report, the processing system is configured to cause the network entity to:

refrain from receiving the power headroom report based at least in part on the trigger-based power headroom report status indicating to disable transmission of the power headroom report.
A method for wireless communications at a user equipment (UE) , comprising:

receiving a message indicating a trigger-based power headroom report status of the UE, the trigger-based power headroom report status indicating whether to enable transmission of a power headroom report triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold; and

selectively transmitting the power headroom report in accordance with the trigger-based power headroom report status and the pathloss change on the at least one uplink carrier.
The method of claim 68, wherein the message comprises a radio resource control (RRC) message.
The method of claim 68, further comprising:

receiving an indication of a power control parameter configured for at least one of a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The method of claim 70, wherein the power control parameter comprises at least one of a pathloss value or a pathloss offset.
The method of claim 68, further comprising:

receiving an indication of a power control parameter configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The method of claim 68, wherein receiving the message comprises:

detecting whether a pathloss reference signal is configured for at least one of: a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The method of claim 68, wherein receiving the message comprises:

detecting whether a pathloss reference signal is configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The method of claim 68, wherein selectively transmitting the power headroom report comprises:

transmitting the power headroom report based at least in part on the trigger-based power headroom report status indicating to enable transmission of the power headroom report and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold.
The method of claim 68, wherein selectively transmitting the power headroom report comprises:

detecting that the pathloss change on the at least one uplink carrier has satisfied the pathloss threshold; and

refraining from transmitting the power headroom report based at least in part on the trigger-based power headroom report status indicating to disable transmission of the power headroom report.
A method for wireless communications at a user equipment (UE) , comprising:

transmitting a power headroom report in a physical uplink shared channel (PUSCH) transmission on a first uplink carrier of the UE during a slot, wherein a set of PUSCH transmissions in a second uplink carrier overlap in a time domain in the slot with the PUSCH transmission on the first uplink carrier; and

providing a power headroom report value for the second uplink carrier of the UE, the power headroom report value for the second uplink carrier comprising an actual power headroom report or a virtual power headroom report, wherein selection of the actual power headroom report or the virtual power headroom report for the second uplink carrier is based at least in part on an uplink transmission type of each PUSCH transmission in the set of PUSCH transmissions.
The method of claim 77, further comprising:

detecting that at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type; and

selecting the actual power headroom report for the second uplink carrier, wherein the actual power headroom report is based on the at least one PUSCH transmission being a first PUSCH transmission in the set of PUSCH transmissions that is associated with the specific uplink transmission type.
The method of claim 77, further comprising:

detecting that each PUSCH transmission in the set of PUSCH transmissions are associated with a non-specific transmission type; and

selecting the actual power headroom report for the second uplink carrier based at least in part on the detecting, wherein the actual power headroom report is based at least in part on a first PUSCH transmission in the set of PUSCH transmissions.
The method of claim 77, further comprising:

detecting that each PUSCH transmission in the set of PUSCH transmissions is associated with a non-specific uplink transmission type; and

selecting the virtual power headroom report for the second uplink carrier based at least in part on the detecting.
The method of claim 77, further comprising:

detecting that a first PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type; and

selecting the actual power headroom report for the second uplink carrier, wherein the actual power headroom report is based at least in part on the first PUSCH transmission in the set of PUSCH transmissions.
The method of claim 77, further comprising:

detecting that a first PUSCH transmission in the set of PUSCH transmissions is associated with a non-specific uplink transmission type; and

selecting the virtual power headroom report for the second uplink carrier based at least in part on the detecting.
The method of claim 77, further comprising:

detecting whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on a pathloss reference signal being associated with the at least one PUSCH transmission and on a non-configuration status for a pathloss or a pathloss offset associated with the at least one PUSCH transmission.
The method of claim 77, further comprising:

detecting at least one PUSCH transmission in the set of PUSCH transmissions based at least in part on an uplink transmission configuration indicator (TCI) state associated with the at least one PUSCH transmission, wherein the uplink TCI state is associated with a downlink pathloss reference signal, a source downlink reference signal, a timing advance group identifier, any combination thereof.
The method of claim 77, further comprising:

detecting at least one PUSCH transmission in the set of PUSCH transmissions based at least in part on a grant scheduling the at least one PUSCH transmission.
The method of claim 77, further comprising:

detecting at least one PUSCH transmission in the set of PUSCH transmissions based at least in part on a pathloss, a pathloss offset, or both, being associated with the at least one PUSCH transmission.
The method of claim 77, further comprising:

detecting at least one PUSCH transmission in the set of PUSCH transmissions based at least in part on an uplink transmission configuration indicator (TCI) state associated with the at least one PUSCH transmission, wherein the uplink TCI state is associated with a pathloss, a pathloss offset, a sounding reference signal (SRS) resource, a timing advance group identifier, or any combination thereof.
The method of claim 77, further comprising:

receiving a radio resource control (RRC) message indicating a specific uplink transmission type.
A method for wireless communications at a user equipment (UE) , comprising:

selecting a virtual power headroom report for an uplink carrier, wherein a power control parameter is configured for the uplink carrier or a pathloss reference signal non-configuration status exists for at least one of a sounding reference signal (SRS) resource set, a physical uplink control channel (PUCCH) , a physical uplink shared channel (PUSCH) , or a transmission configuration indicator (TCI) state, or any combination thereof, for the uplink carrier; and

computing, based at least in part on the selecting, the virtual power headroom report based at least in part on a set of PUSCH reference parameters, a pathloss offset, or both.
The method of claim 89, further comprising:

identifying the pathloss offset based on at least one of a default pathloss reference signal identifier, a default P0 nominal power level, a default uplink transmission configuration indicator (TCI) state, a default pathloss value, an indicated TCI state, or any combination thereof.
The method of claim 89, further comprising:

determining to use the pathloss offset for the virtual power headroom report based at least in part on an indicated TCI state of the UE, wherein the indicated TCI state is associated with the pathloss offset.
The method of claim 89, further comprising:

determining to use the set of PUSCH reference parameters for the virtual power headroom report based at least in part on an indicated TCI state of the UE, wherein the pathloss offset is in a non-configuration state for the indicated TCI state.
The method of claim 89, further comprising:

receiving a radio resource control (RRC) message indicating whether to use the pathloss offset for the virtual power headroom report.
A method for wireless communications at a user equipment (UE) , comprising:

selecting an actual power headroom report or a virtual power headroom report for transmission in a first physical uplink shared channel (PUSCH) transmission on an uplink carrier of the UE, the selecting based at least in part on a previously received grant that schedules a second PUSCH transmission that is associated with an uplink transmission type, wherein previously received grant is received prior to or during a physical downlink control channel (PDCCH) monitoring occasion where the UE detects a grant that schedules the first PUSCH transmission on the uplink carrier; and

transmitting the actual power headroom report or the virtual power headroom report in the first PUSCH transmission on the uplink carrier of the UE in accordance with the selecting.
The method of claim 94, further comprising:

selecting the actual power headroom report for transmission in the first PUSCH transmission based at least in part on the second PUSCH transmission being associated with a specific uplink transmission type, wherein the uplink transmission type comprises the specific uplink transmission type.
The method of claim 94, further comprising:

selecting the virtual power headroom report for transmission in the first PUSCH transmission based at least in part on the second PUSCH transmission being associated with a non-specific uplink transmission type, wherein the uplink transmission type comprises the non-specific uplink transmission type.
A method for wireless communications at a network entity, comprising:

transmitting, to a user equipment (UE) , a message indicating a trigger-based power headroom report status of the UE, the trigger-based power headroom report status indicating whether to enable transmission of a power headroom report triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold; and

selectively receiving the power headroom report in accordance with the trigger-based power headroom report status and the pathloss change on the at least one uplink carrier.
The method of claim 97, wherein the message comprises a radio resource control (RRC) message.
The method of claim 97, further comprising:

transmitting an indication of a power control parameter configured for at least one of a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The method of claim 99, wherein the power control parameter comprises at least one of a pathloss value or a pathloss offset.
The method of claim 97, further comprising:

transmitting an indication of a power control parameter configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The method of claim 97, wherein receiving the message comprises:

detecting whether a pathloss reference signal is configured for at least one of: a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The method of claim 97, wherein transmitting the message comprises:

detecting whether a pathloss reference signal is configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The method of claim 97, wherein selectively receiving the power headroom report comprises:

receiving the power headroom report based at least in part on the trigger-based power headroom report status indicating to enable transmission of the power headroom report and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold.
The method of claim 97, wherein selectively receiving the power headroom report comprises:

refraining from receiving the power headroom report based at least in part on the trigger-based power headroom report status indicating to disable transmission of the power headroom report.
A user equipment (UE) for wireless communications, comprising:

means for receiving a message indicating a trigger-based power headroom report status of the UE, the trigger-based power headroom report status indicating whether to enable transmission of a power headroom report triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold; and

means for selectively transmitting the power headroom report in accordance with the trigger-based power headroom report status and the pathloss change on the at least one uplink carrier.
The UE of claim 106, wherein the message comprises a radio resource control (RRC) message.
The UE of claim 106, further comprising:

means for receiving an indication of a power control parameter configured for at least one of a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The UE of claim 108, wherein the power control parameter comprises at least one of a pathloss value or a pathloss offset.
The UE of claim 106, further comprising:

means for receiving an indication of a power control parameter configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The UE of claim 106, wherein the means for receiving the message comprise:

means for detecting whether a pathloss reference signal is configured for at least one of: a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The UE of claim 106, wherein the means for receiving the message comprise:

means for detecting whether a pathloss reference signal is configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The UE of claim 106, wherein the means for selectively transmitting the power headroom report comprise:

means for transmitting the power headroom report based at least in part on the trigger-based power headroom report status indicating to enable transmission of the power headroom report and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold.
The UE of claim 106, wherein the means for selectively transmitting the power headroom report comprise:

means for detecting that the pathloss change on the at least one uplink carrier has satisfied the pathloss threshold; and

means for refraining from transmitting the power headroom report based at least in part on the trigger-based power headroom report status indicating to disable transmission of the power headroom report.
A user equipment (UE) for wireless communications, comprising:

means for transmitting a power headroom report in a physical uplink shared channel (PUSCH) transmission on a first uplink carrier of the UE during a slot, wherein a set of PUSCH transmissions in a second uplink carrier overlap in a time domain in the slot with the PUSCH transmission on the first uplink carrier; and

means for providing a power headroom report value for the second uplink carrier of the UE, the power headroom report value for the second uplink carrier comprising an actual power headroom report or a virtual power headroom report, wherein selection of the actual power headroom report or the virtual power headroom report for the second uplink carrier is based at least in part on an uplink transmission type of each PUSCH transmission in the set of PUSCH transmissions.
The UE of claim 115, further comprising:

means for detecting that at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type; and

means for selecting the actual power headroom report for the second uplink carrier, wherein the actual power headroom report is based on the at least one PUSCH transmission being a first PUSCH transmission in the set of PUSCH transmissions that is associated with the specific uplink transmission type.
The UE of claim 115, further comprising:

means for detecting that each PUSCH transmission in the set of PUSCH transmissions are associated with a non-specific transmission type; and

means for selecting the actual power headroom report for the second uplink carrier based at least in part on the detecting, wherein the actual power headroom report is based at least in part on a first PUSCH transmission in the set of PUSCH transmissions.
The UE of claim 115, further comprising:

means for detecting that each PUSCH transmission in the set of PUSCH transmissions is associated with a non-specific uplink transmission type; and

means for selecting the virtual power headroom report for the second uplink carrier based at least in part on the detecting.
The UE of claim 115, further comprising:

means for detecting that a first PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type; and

means for selecting the actual power headroom report for the second uplink carrier, wherein the actual power headroom report is based at least in part on the first PUSCH transmission in the set of PUSCH transmissions.
The UE of claim 115, further comprising:

means for detecting that a first PUSCH transmission in the set of PUSCH transmissions is associated with a non-specific uplink transmission type; and

means for selecting the virtual power headroom report for the second uplink carrier based at least in part on the detecting.
The UE of claim 115, further comprising:

means for detecting whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on a pathloss reference signal being associated with the at least one PUSCH transmission and on a non-configuration status for a pathloss or a pathloss offset associated with the at least one PUSCH transmission.
The UE of claim 115, further comprising:

means for detecting at least one PUSCH transmission in the set of PUSCH transmissions based at least in part on an uplink transmission configuration indicator (TCI) state associated with the at least one PUSCH transmission, wherein the uplink TCI state is associated with a downlink pathloss reference signal, a source downlink reference signal, a timing advance group identifier, any combination thereof.
The UE of claim 115, further comprising:

means for detecting at least one PUSCH transmission in the set of PUSCH transmissions based at least in part on a grant scheduling the at least one PUSCH transmission.
The UE of claim 115, further comprising:

means for detecting at least one PUSCH transmission in the set of PUSCH transmissions based at least in part on a pathloss, a pathloss offset, or both, being associated with the at least one PUSCH transmission.
The UE of claim 115, further comprising:

means for detecting at least one PUSCH transmission in the set of PUSCH transmissions based at least in part on an uplink transmission configuration indicator (TCI) state associated with the at least one PUSCH transmission, wherein the uplink TCI state is associated with a pathloss, a pathloss offset, a sounding reference signal (SRS) resource, a timing advance group identifier, or any combination thereof.
The UE of claim 115, further comprising:

means for receiving a radio resource control (RRC) message indicating a specific uplink transmission type.
A user equipment (UE) for wireless communications, comprising:

means for selecting a virtual power headroom report for an uplink carrier, wherein a power control parameter is configured for the uplink carrier or a pathloss reference signal non-configuration status exists for at least one of a sounding reference signal (SRS) resource set, a physical uplink control channel (PUCCH) , a physical uplink shared channel (PUSCH) , or a transmission configuration indicator (TCI) state, or any combination thereof, for the uplink carrier; and

means for computing, based at least in part on the selecting, the virtual power headroom report based at least in part on a set of PUSCH reference parameters, a pathloss offset, or both.
The UE of claim 127, further comprising:

means for identifying the pathloss offset based on at least one of a default pathloss reference signal identifier, a default P0 nominal power level, a default uplink transmission configuration indicator (TCI) state, a default pathloss value, an indicated TCI state, or any combination thereof.
The UE of claim 127, further comprising:

means for determining to use the pathloss offset for the virtual power headroom report based at least in part on an indicated TCI state of the UE, wherein the indicated TCI state is associated with the pathloss offset.
The UE of claim 127, further comprising:

means for determining to use the set of PUSCH reference parameters for the virtual power headroom report based at least in part on an indicated TCI state of the UE, wherein the pathloss offset is in a non-configuration state for the indicated TCI state.
The UE of claim 127, further comprising:

means for receiving a radio resource control (RRC) message indicating whether to use the pathloss offset for the virtual power headroom report.
A user equipment (UE) for wireless communications, comprising:

means for selecting an actual power headroom report or a virtual power headroom report for transmission in a first physical uplink shared channel (PUSCH) transmission on an uplink carrier of the UE, the selecting based at least in part on a previously received grant that schedules a second PUSCH transmission that is associated with an uplink transmission type, wherein previously received grant is received prior to or during a physical downlink control channel (PDCCH) monitoring occasion where the UE detects a grant that schedules the first PUSCH transmission on the uplink carrier; and

means for transmitting the actual power headroom report or the virtual power headroom report in the first PUSCH transmission on the uplink carrier of the UE in accordance with the selecting.
The UE of claim 132, further comprising:

means for selecting the actual power headroom report for transmission in the first PUSCH transmission based at least in part on the second PUSCH transmission being associated with a specific uplink transmission type, wherein the uplink transmission type comprises the specific uplink transmission type.
The UE of claim 132, further comprising:

means for selecting the virtual power headroom report for transmission in the first PUSCH transmission based at least in part on the second PUSCH transmission being associated with a non-specific uplink transmission type, wherein the uplink transmission type comprises the non-specific uplink transmission type.
A network entity for wireless communications, comprising:

means for transmitting, to a user equipment (UE) , a message indicating a trigger-based power headroom report status of the UE, the trigger-based power headroom report status indicating whether to enable transmission of a power headroom report triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold; and

means for selectively receiving the power headroom report in accordance with the trigger-based power headroom report status and the pathloss change on the at least one uplink carrier.
The network entity of claim 135, wherein the message comprises a radio resource control (RRC) message.
The network entity of claim 135, further comprising:

means for transmitting an indication of a power control parameter configured for at least one of a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The network entity of claim 137, wherein the power control parameter comprises at least one of a pathloss value or a pathloss offset.
The network entity of claim 135, further comprising:

means for transmitting an indication of a power control parameter configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The network entity of claim 135, wherein the means for receiving the message comprise:

means for detecting whether a pathloss reference signal is configured for at least one of: a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The network entity of claim 135, wherein the means for transmitting the message comprise:

means for detecting whether a pathloss reference signal is configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The network entity of claim 135, wherein the means for selectively receiving the power headroom report comprise:

means for receiving the power headroom report based at least in part on the trigger-based power headroom report status indicating to enable transmission of the power headroom report and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold.
The network entity of claim 135, wherein the means for selectively receiving the power headroom report comprise:

means for refraining from receiving the power headroom report based at least in part on the trigger-based power headroom report status indicating to disable transmission of the power headroom report.
A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to:

receive, at a user equipment (UE) , a message indicating a trigger-based power headroom report status of the UE, the trigger-based power headroom report status indicating whether to enable transmission of a power headroom report triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold; and

selectively transmit the power headroom report in accordance with the trigger-based power headroom report status and the pathloss change on the at least one uplink carrier.
The non-transitory computer-readable medium of claim 144, wherein the message comprises a radio resource control (RRC) message.
The non-transitory computer-readable medium of claim 144, wherein the instructions are further executable by the one or more processors to:

receive an indication of a power control parameter configured for at least one of a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The non-transitory computer-readable medium of claim 146, wherein the power control parameter comprises at least one of a pathloss value or a pathloss offset.
The non-transitory computer-readable medium of claim 144, wherein the instructions are further executable by the one or more processors to:

receive an indication of a power control parameter configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The non-transitory computer-readable medium of claim 144, wherein the instructions to receive the message are executable by the one or more processors to:

detect whether a pathloss reference signal is configured for at least one of: a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The non-transitory computer-readable medium of claim 144, wherein the instructions to receive the message are executable by the one or more processors to:

detect whether a pathloss reference signal is configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The non-transitory computer-readable medium of claim 144, wherein the instructions to selectively transmit the power headroom report are executable by the one or more processors to:

transmit the power headroom report based at least in part on the trigger-based power headroom report status indicating to enable transmission of the power headroom report and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold.
The non-transitory computer-readable medium of claim 144, wherein the instructions to selectively transmit the power headroom report are executable by the one or more processors to:

detect that the pathloss change on the at least one uplink carrier has satisfied the pathloss threshold; and

refrain from transmitting the power headroom report based at least in part on the trigger-based power headroom report status indicating to disable transmission of the power headroom report.
A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to:

transmit a power headroom report in a physical uplink shared channel (PUSCH) transmission on a first uplink carrier of a user equipment (UE) during a slot, wherein a set of PUSCH transmissions in a second uplink carrier overlap in a time domain in the slot with the PUSCH transmission on the first uplink carrier; and

provide a power headroom report value for the second uplink carrier of the UE, the power headroom report value for the second uplink carrier comprising an actual power headroom report or a virtual power headroom report, wherein selection of the actual power headroom report or the virtual power headroom report for the second uplink carrier is based at least in part on an uplink transmission type of each PUSCH transmission in the set of PUSCH transmissions.
The non-transitory computer-readable medium of claim 153, wherein the instructions are further executable by the one or more processors to:

detect that at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type; and

select the actual power headroom report for the second uplink carrier, wherein the actual power headroom report is based on the at least one PUSCH transmission being a first PUSCH transmission in the set of PUSCH transmissions that is associated with the specific uplink transmission type.
The non-transitory computer-readable medium of claim 153, wherein the instructions are further executable by the one or more processors to:

detect that each PUSCH transmission in the set of PUSCH transmissions are associated with a non-specific transmission type; and

select the actual power headroom report for the second uplink carrier based at least in part on the detecting, wherein the actual power headroom report is based at least in part on a first PUSCH transmission in the set of PUSCH transmissions.
The non-transitory computer-readable medium of claim 153, wherein the instructions are further executable by the one or more processors to:

detect that each PUSCH transmission in the set of PUSCH transmissions is associated with a non-specific uplink transmission type; and

select the virtual power headroom report for the second uplink carrier based at least in part on the detecting.
The non-transitory computer-readable medium of claim 153, wherein the instructions are further executable by the one or more processors to:

detect that a first PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type; and

select the actual power headroom report for the second uplink carrier, wherein the actual power headroom report is based at least in part on the first PUSCH transmission in the set of PUSCH transmissions.
The non-transitory computer-readable medium of claim 153, wherein the instructions are further executable by the one or more processors to:

detect that a first PUSCH transmission in the set of PUSCH transmissions is associated with a non-specific uplink transmission type; and

select the virtual power headroom report for the second uplink carrier based at least in part on the detecting.
The non-transitory computer-readable medium of claim 153, wherein the instructions are further executable by the one or more processors to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on a pathloss reference signal being associated with the at least one PUSCH transmission and on a non-configuration status for a pathloss or a pathloss offset associated with the at least one PUSCH transmission.
The non-transitory computer-readable medium of claim 153, wherein the instructions are further executable by the one or more processors to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on an uplink transmission configuration indicator (TCI) state associated with the at least one PUSCH transmission, wherein the uplink TCI state is associated with a downlink pathloss reference signal, a source downlink reference signal, a timing advance group identifier, any combination thereof.
The non-transitory computer-readable medium of claim 153, wherein the instructions are further executable by the one or more processors to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on a grant scheduling the at least one PUSCH transmission.
The non-transitory computer-readable medium of claim 153, wherein the instructions are further executable by the one or more processors to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on a pathloss, a pathloss offset, or both, being associated with the at least one PUSCH transmission.
The non-transitory computer-readable medium of claim 153, wherein the instructions are further executable by the one or more processors to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on an uplink transmission configuration indicator (TCI) state associated with the at least one PUSCH transmission, wherein the uplink TCI state is associated with a pathloss, a pathloss offset, a sounding reference signal (SRS) resource, a timing advance group identifier, or any combination thereof.
The non-transitory computer-readable medium of claim 153, wherein the instructions are further executable by the one or more processors to:

receive a radio resource control (RRC) message indicating a specific uplink transmission type.
A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to:

select a virtual power headroom report for an uplink carrier, wherein a power control parameter is configured for the uplink carrier or a pathloss reference signal non-configuration status exists for at least one of a sounding reference signal (SRS) resource set, a physical uplink control channel (PUCCH) , a physical uplink shared channel (PUSCH) , or a transmission configuration indicator (TCI) state, or any combination thereof, for the uplink carrier; and

computing, base at least in part on the selecting, the virtual power headroom report based at least in part on a set of PUSCH reference parameters, a pathloss offset, or both.
The non-transitory computer-readable medium of claim 165, wherein the instructions are further executable by the one or more processors to:

identify the pathloss offset based on at least one of a default pathloss reference signal identifier, a default P0 nominal power level, a default uplink transmission configuration indicator (TCI) state, a default pathloss value, an indicated TCI state, or any combination thereof.
The non-transitory computer-readable medium of claim 165, wherein the instructions are further executable by the one or more processors to:

determine to use the pathloss offset for the virtual power headroom report based at least in part on an indicated TCI state of a user equipment (UE) , wherein the indicated TCI state is associated with the pathloss offset.
The non-transitory computer-readable medium of claim 165, wherein the instructions are further executable by the one or more processors to:

determine to use the set of PUSCH reference parameters for the virtual power headroom report based at least in part on an indicated TCI state of a user equipment (UE) , wherein the pathloss offset is in a non-configuration state for the indicated TCI state.
The non-transitory computer-readable medium of claim 165, wherein the instructions are further executable by the one or more processors to:

receive a radio resource control (RRC) message indicating whether to use the pathloss offset for the virtual power headroom report.
A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to:

select an actual power headroom report or a virtual power headroom report for transmission in a first physical uplink shared channel (PUSCH) transmission on an uplink carrier of a user equipment (UE) , the selecting based at least in part on a previously received grant that schedules a second PUSCH transmission that is associated with an uplink transmission type, wherein previously received grant is received prior to or during a physical downlink control channel (PDCCH) monitoring occasion where the UE detects a grant that schedules the first PUSCH transmission on the first uplink carrier; and

transmit the actual power headroom report or the virtual power headroom report in the first PUSCH transmission on the uplink carrier of the UE in accordance with the selecting.
The non-transitory computer-readable medium of claim 170, wherein the instructions are further executable by the one or more processors to:

select the actual power headroom report for transmission in the first PUSCH transmission based at least in part on the second PUSCH transmission being associated with a specific uplink transmission type, wherein the uplink transmission type comprises the specific uplink transmission type.
The non-transitory computer-readable medium of claim 170, wherein the instructions are further executable by the one or more processors to:

select the virtual power headroom report for transmission in the first PUSCH transmission based at least in part on the second PUSCH transmission being associated with a non-specific uplink transmission type, wherein the uplink transmission type comprises the non-specific uplink transmission type.
A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to:

transmit, to a user equipment (UE) , a message indicating a trigger-based power headroom report status of the UE, the trigger-based power headroom report status indicating whether to enable transmission of a power headroom report triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold; and

selectively receive the power headroom report in accordance with the trigger-based power headroom report status and the pathloss change on the at least one uplink carrier.
The non-transitory computer-readable medium of claim 173, wherein the message comprises a radio resource control (RRC) message.
The non-transitory computer-readable medium of claim 173, wherein the instructions are further executable by the one or more processors to:

transmit an indication of a power control parameter configured for at least one of a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The non-transitory computer-readable medium of claim 175, wherein the power control parameter comprises at least one of a pathloss value or a pathloss offset.
The non-transitory computer-readable medium of claim 173, wherein the instructions are further executable by the one or more processors to:

transmit an indication of a power control parameter configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The non-transitory computer-readable medium of claim 173, wherein the instructions to receive the message are executable by the one or more processors to:

detect whether a pathloss reference signal is configured for at least one of: a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The non-transitory computer-readable medium of claim 173, wherein the instructions to transmit the message are executable by the one or more processors to:

detect whether a pathloss reference signal is configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The non-transitory computer-readable medium of claim 173, wherein the instructions to selectively receive the power headroom report are executable by the one or more processors to:

receive the power headroom report based at least in part on the trigger-based power headroom report status indicating to enable transmission of the power headroom report and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold.
The non-transitory computer-readable medium of claim 173, wherein the instructions to selectively receive the power headroom report are executable by the one or more processors to:

refrain from receiving the power headroom report based at least in part on the trigger-based power headroom report status indicating to disable transmission of the power headroom report.
A method for wireless communications by a user equipment (UE) , comprising:

receiving a message indicating a trigger-based power headroom report status of the UE, the trigger-based power headroom report status indicating whether to enable transmission of a power headroom report triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold; and

selectively transmitting the power headroom report in accordance with the trigger-based power headroom report status and the pathloss change on the at least one uplink carrier.
The method of claim 182, wherein the message comprises a radio resource control (RRC) message.
The method of any of claims 182 through 183, further comprising:

receiving an indication of a power control parameter configured for at least one of a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The method of claim 184, wherein the power control parameter comprises at least one of a pathloss value or a pathloss offset.
The method of any of claims 182 through 185, further comprising:

receiving an indication of a power control parameter configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The method of any of claims 182 through 186, wherein receiving the message comprises detecting whether a pathloss reference signal is configured for at least one of: a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The method of any of claims 182 through 187, wherein receiving the message comprises detecting whether a pathloss reference signal is configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The method of any of claims 182 through 188, wherein selectively transmitting the power headroom report comprises transmitting the power headroom report based at least in part on the trigger-based power headroom report status indicating to enable transmission of the power headroom report and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold.
The method of any of claims 182 through 189, wherein selectively transmitting the power headroom report comprises:

detecting that the pathloss change on the at least one uplink carrier has satisfied the pathloss threshold; and

refraining from transmitting the power headroom report based at least in part on the trigger-based power headroom report status indicating to disable transmission of the power headroom report.
A method for wireless communications by a user equipment (UE) , comprising:

transmitting a power headroom report in a physical uplink shared channel (PUSCH) transmission on a first uplink carrier of the UE during a slot, wherein a set of PUSCH transmissions in a second uplink carrier overlap in a time domain in the slot with the PUSCH transmission on the first uplink carrier; and

providing a power headroom report value for the second uplink carrier of the UE, the power headroom report value for the second uplink carrier comprising an actual power headroom report or a virtual power headroom report, wherein selection of the actual power headroom report or the virtual power headroom report for the second uplink carrier is based at least in part on an uplink transmission type of each PUSCH transmission in the set of PUSCH transmissions.
The method of claim 191, further comprising:

detecting that at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type; and

selecting the actual power headroom report for the second uplink carrier, wherein the actual power headroom report is based on the at least one PUSCH transmission being a first PUSCH transmission in the set of PUSCH transmissions that is associated with the specific uplink transmission type.
The method of any of claims 191 through 192, further comprising:

detecting that each PUSCH transmission in the set of PUSCH transmissions are associated with a non-specific transmission type; and

selecting the actual power headroom report for the second uplink carrier based at least in part on the detecting, wherein the actual power headroom report is based at least in part on a first PUSCH transmission in the set of PUSCH transmissions.
The method of any of claims 191 through 193, further comprising:

detecting that each PUSCH transmission in the set of PUSCH transmissions is associated with a non-specific uplink transmission type; and

selecting the virtual power headroom report for the second uplink carrier based at least in part on the detecting.
The method of any of claims 191 through 194, further comprising:

detecting that a first PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type; and

selecting the actual power headroom report for the second uplink carrier, wherein the actual power headroom report is based at least in part on the first PUSCH transmission in the set of PUSCH transmissions.
The method of any of claims 191 through 195, further comprising:

detecting that a first PUSCH transmission in the set of PUSCH transmissions is associated with a non-specific uplink transmission type; and

selecting the virtual power headroom report for the second uplink carrier based at least in part on the detecting.
The method of any of claims 191 through 196, further comprising:

detecting whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on a pathloss reference signal being associated with the at least one PUSCH transmission and on a non-configuration status for a pathloss or a pathloss offset associated with the at least one PUSCH transmission.
The method of any of claims 191 through 197, further comprising:

detecting at least one PUSCH transmission in the set of PUSCH transmissions based at least in part on an uplink transmission configuration indicator (TCI) state associated with the at least one PUSCH transmission, wherein the uplink TCI state is associated with a downlink pathloss reference signal, a source downlink reference signal, a timing advance group identifier, any combination thereof.
The method of any of claims 191 through 198, further comprising:

detecting at least one PUSCH transmission in the set of PUSCH transmissions based at least in part on a grant scheduling the at least one PUSCH transmission.
The method of any of claims 191 through 199, further comprising:

detecting at least one PUSCH transmission in the set of PUSCH transmissions based at least in part on a pathloss, a pathloss offset, or both, being associated with the at least one PUSCH transmission.
The method of any of claims 191 through 200, further comprising:

detecting at least one PUSCH transmission in the set of PUSCH transmissions based at least in part on an uplink transmission configuration indicator (TCI) state associated with the at least one PUSCH transmission, wherein the uplink TCI state is associated with a pathloss, a pathloss offset, a sounding reference signal (SRS) resource, a timing advance group identifier, or any combination thereof.
The method of any of claims 191 through 201, further comprising:

receiving a radio resource control (RRC) message indicating a specific uplink transmission type.
A method for wireless communications by a user equipment (UE) , comprising:

selecting a virtual power headroom report for an uplink carrier, wherein a power control parameter is configured for the uplink carrier or a pathloss reference signal non-configuration status exists for at least one of a sounding reference signal (SRS) resource set, a physical uplink control channel (PUCCH) , a physical uplink shared channel (PUSCH) , or a transmission configuration indicator (TCI) state, or any combination thereof, for the uplink carrier; and

computing, based at least in part on the selecting, the virtual power headroom report based at least in part on a set of PUSCH reference parameters, a pathloss offset, or both.
The method of claim 203, further comprising:

identifying the pathloss offset based on at least one of a default pathloss reference signal identifier, a default P0 nominal power level, a default uplink transmission configuration indicator (TCI) state, a default pathloss value, an indicated TCI state, or any combination thereof.
The method of any of claims 203 through 204, further comprising:

determining to use the pathloss offset for the virtual power headroom report based at least in part on an indicated TCI state of the UE, wherein the indicated TCI state is associated with the pathloss offset.
The method of any of claims 203 through 205, further comprising:

determining to use the set of PUSCH reference parameters for the virtual power headroom report based at least in part on an indicated TCI state of the UE, wherein the pathloss offset is in a non-configuration state for the indicated TCI state.
The method of any of claims 203 through 206, further comprising:

receiving a radio resource control (RRC) message indicating whether to use the pathloss offset for the virtual power headroom report.
A method for wireless communications by a user equipment (UE) , comprising:

selecting an actual power headroom report or a virtual power headroom report for transmission in a first physical uplink shared channel (PUSCH) transmission on an uplink carrier of the UE, the selecting based at least in part on a previously received grant that schedules a second PUSCH transmission that is associated with an uplink transmission type, wherein previously received grant is received prior to or during a physical downlink control channel (PDCCH) monitoring occasion where the UE detects a grant that schedules the first PUSCH transmission on the uplink carrier; and

transmitting the actual power headroom report or the virtual power headroom report in the first PUSCH transmission on the uplink carrier of the UE in accordance with the selecting.
The method of claim 208, further comprising:

selecting the actual power headroom report for transmission in the first PUSCH transmission based at least in part on the second PUSCH transmission being associated with a specific uplink transmission type, wherein the uplink transmission type comprises the specific uplink transmission type.
The method of any of claims 208 through 209, further comprising:

selecting the virtual power headroom report for transmission in the first PUSCH transmission based at least in part on the second PUSCH transmission being associated with a non-specific uplink transmission type, wherein the uplink transmission type comprises the non-specific uplink transmission type.
A method for wireless communications by a network entity, comprising:

transmitting, to a user equipment (UE) , a message indicating a trigger-based power headroom report status of the UE, the trigger-based power headroom report status indicating whether to enable transmission of a power headroom report triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold; and

selectively receiving the power headroom report in accordance with the trigger-based power headroom report status and the pathloss change on the at least one uplink carrier.
The method of claim 211, wherein the message comprises a radio resource control (RRC) message.
The method of any of claims 211 through 212, further comprising:

transmitting an indication of a power control parameter configured for at least one of a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The method of claim 213, wherein the power control parameter comprises at least one of a pathloss value or a pathloss offset.
The method of any of claims 211 through 214, further comprising:

transmitting an indication of a power control parameter configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The method of any of claims 211 through 215, wherein receiving the message comprises detecting whether a pathloss reference signal is configured for at least one of: a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The method of any of claims 211 through 216, wherein transmitting the message comprises detecting whether a pathloss reference signal is configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The method of any of claims 211 through 217, wherein selectively receiving the power headroom report comprises receiving the power headroom report based at least in part on the trigger-based power headroom report status indicating to enable transmission of the power headroom report and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold.
The method of any of claims 211 through 218, wherein selectively receiving the power headroom report comprises refraining from receiving the power headroom report based at least in part on the trigger-based power headroom report status indicating to disable transmission of the power headroom report.
A user equipment (UE) for wireless communications, comprising:

processing circuitry associated with one or more memory devices and configured to cause the UE to:

receive a message indicating a trigger-based power headroom report status of the UE, the trigger-based power headroom report status indicating whether to enable transmission of a power headroom report triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold; and

selectively transmit the power headroom report in accordance with the trigger-based power headroom report status and the pathloss change on the at least one uplink carrier.
The UE of claim 220, wherein the message comprises a radio resource control (RRC) message.
The UE of claim 220, wherein the processing circuitry is further configured to cause the UE to:

receive an indication of a power control parameter configured for at least one of a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The UE of claim 222, wherein the power control parameter comprises at least one of a pathloss value or a pathloss offset.
The UE of claim 220, wherein the processing circuitry is further configured to cause the UE to:

receive an indication of a power control parameter configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The UE of claim 220, wherein receiving the message comprises the processing circuitry configured to cause the UE to:

detect whether a pathloss reference signal is configured for at least one of: a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The UE of claim 220, wherein receiving the message comprises the processing circuitry configured to cause the UE to:

detect whether a pathloss reference signal is configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The UE of claim 220, wherein selectively transmitting the power headroom report comprises the processing circuitry configured to cause the UE to transmit the power headroom report based at least in part on the trigger-based power headroom report status indicating to enable transmission of the power headroom report and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold.
The UE of claim 220, wherein selectively transmitting the power headroom report comprises the processing circuitry configured to cause the UE to:

detect that the pathloss change on the at least one uplink carrier has satisfied the pathloss threshold; and

refrain from transmitting the power headroom report based at least in part on the trigger-based power headroom report status indicating to disable transmission of the power headroom report.
A user equipment (UE) for wireless communications, comprising:

processing circuitry associated with one or more memory devices and configured to cause the UE to:

transmit a power headroom report in a physical uplink shared channel (PUSCH) transmission on a first uplink carrier of the UE during a slot, wherein a set of PUSCH transmissions in a second uplink carrier overlap in a time domain in the slot with the PUSCH transmission on the first uplink carrier; and

provide a power headroom report value for the second uplink carrier of the UE, the power headroom report value for the second uplink carrier comprising an actual power headroom report or a virtual power headroom report, wherein selection of the actual power headroom report or the virtual power headroom report for the second uplink carrier is based at least in part on an uplink transmission type of each PUSCH transmission in the set of PUSCH transmissions.
The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to:

detect that at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type; and

select the actual power headroom report for the second uplink carrier, wherein the actual power headroom report is based on the at least one PUSCH transmission being a first PUSCH transmission in the set of PUSCH transmissions that is associated with the specific uplink transmission type.
The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to:

detect that each PUSCH transmission in the set of PUSCH transmissions are associated with a non-specific transmission type; and

select the actual power headroom report for the second uplink carrier based at least in part on the detecting, wherein the actual power headroom report is based at least in part on a first PUSCH transmission in the set of PUSCH transmissions.
The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to:

detect that each PUSCH transmission in the set of PUSCH transmissions is associated with a non-specific uplink transmission type; and

select the virtual power headroom report for the second uplink carrier based at least in part on the detecting.
The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to:

detect that a first PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type; and

select the actual power headroom report for the second uplink carrier, wherein the actual power headroom report is based at least in part on the first PUSCH transmission in the set of PUSCH transmissions.
The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to:

detect that a first PUSCH transmission in the set of PUSCH transmissions is associated with a non-specific uplink transmission type; and

select the virtual power headroom report for the second uplink carrier based at least in part on the detecting.
The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on a pathloss reference signal being associated with the at least one PUSCH transmission and on a non-configuration status for a pathloss or a pathloss offset associated with the at least one PUSCH transmission.
The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on an uplink transmission configuration indicator (TCI) state associated with the at least one PUSCH transmission, wherein the uplink TCI state is associated with a downlink pathloss reference signal, a source downlink reference signal, a timing advance group identifier, any combination thereof.
The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on a grant scheduling the at least one PUSCH transmission.
The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on a pathloss, a pathloss offset, or both, being associated with the at least one PUSCH transmission.
The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to:

detect whether at least one PUSCH transmission in the set of PUSCH transmissions is associated with a specific uplink transmission type based at least in part on an uplink transmission configuration indicator (TCI) state associated with the at least one PUSCH transmission, wherein the uplink TCI state is associated with a pathloss, a pathloss offset, a sounding reference signal (SRS) resource, a timing advance group identifier, or any combination thereof.
The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to:

receive a radio resource control (RRC) message indicating a specific uplink transmission type.
A user equipment (UE) for wireless communications, comprising:

processing circuitry associated with one or more memory devices and configured to cause the UE to:

select a virtual power headroom report for an uplink carrier, wherein a power control parameter is configured for the uplink carrier or a pathloss reference signal non-configuration status exists for at least one of a sounding reference signal (SRS) resource set, a physical uplink control channel (PUCCH) , a physical uplink shared channel (PUSCH) , or a transmission configuration indicator (TCI) state, or any combination thereof, for the uplink carrier; and

computing, base at least in part on the selecting, the virtual power headroom report based at least in part on a set of PUSCH reference parameters, a pathloss offset, or both.
The UE of claim 241, wherein the processing circuitry is further configured to cause the UE to:

identify the pathloss offset based on at least one of a default pathloss reference signal identifier, a default P0 nominal power level, a default uplink transmission configuration indicator (TCI) state, a default pathloss value, an indicated TCI state, or any combination thereof.
The UE of claim 241, wherein the processing circuitry is further configured to cause the UE to:

determine to use the pathloss offset for the virtual power headroom report based at least in part on an indicated TCI state of the UE, wherein the indicated TCI state is associated with the pathloss offset.
The UE of claim 241, wherein the processing circuitry is further configured to cause the UE to:

determine to use the set of PUSCH reference parameters for the virtual power headroom report based at least in part on an indicated TCI state of the UE, wherein the pathloss offset is in a non-configuration state for the indicated TCI state.
The UE of claim 241, wherein the processing circuitry is further configured to cause the UE to:

receive a radio resource control (RRC) message indicating whether to use the pathloss offset for the virtual power headroom report.
A user equipment (UE) for wireless communications, comprising:

processing circuitry associated with one or more memory devices and configured to cause the UE to:

select an actual power headroom report or a virtual power headroom report for transmission in a first physical uplink shared channel (PUSCH) transmission on an uplink carrier of the UE, the selecting based at least in part on a previously received grant that schedules a second PUSCH transmission that is associated with an uplink transmission type, wherein previously received grant is received prior to or during a physical downlink control channel (PDCCH) monitoring occasion where the UE detects a grant that schedules the first PUSCH transmission on the uplink carrier; and

transmit the actual power headroom report or the virtual power headroom report in the first PUSCH transmission on the uplink carrier of the UE in accordance with the selecting.
The UE of claim 246, wherein the processing circuitry is further configured to cause the UE to:

select the actual power headroom report for transmission in the first PUSCH transmission based at least in part on the second PUSCH transmission being associated with a specific uplink transmission type, wherein the uplink transmission type comprises the specific uplink transmission type.
The UE of claim 246, wherein the processing circuitry is further configured to cause the UE to:

select the virtual power headroom report for transmission in the first PUSCH transmission based at least in part on the second PUSCH transmission being associated with a non-specific uplink transmission type, wherein the uplink transmission type comprises the non-specific uplink transmission type.
A network entity for wireless communications, comprising:

processing circuitry associated with one or more memory devices and configured to cause the network entity to:

transmit, to a user equipment (UE) , a message indicating a trigger-based power headroom report status of the UE, the trigger-based power headroom report status indicating whether to enable transmission of a power headroom report triggered by a pathloss change on at least one uplink carrier of the UE satisfying a pathloss threshold; and

selectively receive the power headroom report in accordance with the trigger-based power headroom report status and the pathloss change on the at least one uplink carrier.
The network entity of claim 249, wherein the message comprises a radio resource control (RRC) message.
The network entity of claim 249, wherein the processing circuitry is further configured to cause the network entity to:

transmit an indication of a power control parameter configured for at least one of a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The network entity of claim 251, wherein the power control parameter comprises at least one of a pathloss value or a pathloss offset.
The network entity of claim 249, wherein the processing circuitry is further configured to cause the network entity to:

transmit an indication of a power control parameter configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the power control parameter.
The network entity of claim 249, wherein receiving the message comprises the processing circuitry configured to cause the network entity to:

detect whether a pathloss reference signal is configured for at least one of: a sounding reference signal (SRS) transmission, a physical uplink control channel (PUCCH) transmission, or a physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The network entity of claim 249, wherein transmitting the message comprises the processing circuitry configured to cause the network entity to:

detect whether a pathloss reference signal is configured for an uplink transmission configuration indicator (TCI) state, wherein the trigger-based power headroom report status indicating whether to enable transmission of the power headroom report is based at least in part on the detecting.
The network entity of claim 249, wherein selectively receiving the power headroom report comprises the processing circuitry configured to cause the network entity to receive the power headroom report based at least in part on the trigger-based power headroom report status indicating to enable transmission of the power headroom report and on the pathloss change on the at least one uplink carrier satisfying the pathloss threshold.
The network entity of claim 249, wherein selectively receiving the power headroom report comprises the processing circuitry configured to cause the network entity to refrain from receiving the power headroom report based at least in part on the trigger-based power headroom report status indicating to disable transmission of the power headroom report.