Power headroom enhancements for dense uplink deployments

Abstract

Methods, systems, and apparatus for conducting wireless communication are described. User equipment (UE) can receive a message indicating a triggered power clearance report status for the UE, the triggered power clearance report status indicating whether to enable the transmission of a power clearance report triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold. The UE can selectively transmit power clearance reports based on the triggered power clearance report status and the path loss change on at least one uplink carrier.

Description

Technical Field

[0001] The following discussion relates to wireless communications, including power headroom enhancements for dense uplink deployments. Background Technology

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A 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 Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0003] The described techniques relate to improved methods, systems, devices, and apparatuses supporting power clearance enhancement for dense uplink deployments. In some aspects, the techniques described herein provide, for example, enabling and / or disabling power clearance reports (PHRs) triggered based on (e.g., by) a threshold path loss change. For example, a user equipment (UE) may receive a message indicating a triggered PHR status for the UE. This status can be used to indicate whether to enable (or disable) transmission of a PHR that has been triggered based on a path loss change on at least one uplink carrier satisfying a path loss threshold. The UE may selectively transmit the PHR based on the triggered PHR status and the path loss change on the uplink carrier. For example, the UE may transmit the PHR when transmission is enabled by the triggered PHR status, or may avoid transmitting the PHR when transmission is disabled by the triggered PHR status (e.g., when a path loss change is detected to satisfy a path loss threshold).

[0004] In some aspects, the techniques described herein provide the ability to transmit actual PHR reports or virtual PHR reports on one or more additional uplink carriers. For example, a UE may transmit a PHR on its first uplink carrier during a time slot, such as during a Physical Uplink Shared Channel (PUSCH) transmission. Additional PUSCH transmissions scheduled on the UE's second uplink carrier may overlap with PUSCH transmissions on the first uplink carrier in the time domain during the time slot. The UE may provide a PHR value for its second uplink carrier during the time slot. The PHR value may include an actual PHR or a virtual PHR. The UE may select between an actual PHR or a virtual PHR on the second uplink carrier based on, for example, the overlap in the time domain between the first uplink carrier PUSCH and a second PUSCH transmission on the second uplink carrier and / or based on, for example, the uplink transmission type used for PUSCH transmissions on the second uplink carrier. The uplink transmission type typically refers to a designated or specific uplink transmission type that may be identified by network specification and other technologies, based on, for example, the association of uplink transmission with a downlink node or only an uplink node.

[0005] In some respects, the techniques described herein provide different methods for estimating channel performance metrics when transmitting a virtual PHR. For example, a UE can select a virtual PHR for an uplink carrier. Power control parameters can be configured for the uplink carrier, or based on a set of Sounding Reference Signals (SRS) resources, Physical Uplink Control Channel (PUCCH), PUSCH, and / or Transmit Configuration Indicator (TCI) states where the UE is not configured with an uplink carrier. The UE can calculate or otherwise determine the virtual PHR value based on a set of PUSCH reference parameters, a path loss offset, or both. The virtual PHR can be based on, for example, a path loss offset included along with an estimation of the channel performance metric. That is, the path loss offset can be configured or otherwise indicated to the UE, which uses it as part of a formula for calculating the virtual PHR.

[0006] A method for wireless communication by a UE is described. The method may include: receiving a message indicating a triggered PHR state of the UE, the triggered PHR state indicating whether to enable the transmission of a PHR triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold; and selectively transmitting the PHR based on the triggered PHR state and the path loss change on the at least one uplink carrier.

[0007] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to cause the UE to: receive a message indicating a triggered PHR state of the UE, the triggered PHR state indicating whether to enable the transmission of a PHR triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold; and selectively transmit the PHR based on the triggered PHR state and the path loss change on the at least one uplink carrier.

[0008] Another UE for wireless communication is described. The UE may include: a component for receiving a message indicating a triggered PHR state of the UE, the triggered PHR state indicating whether to enable the transmission of a PHR triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold; and a component for selectively transmitting the PHR based on the triggered PHR state and the path loss change on the at least one uplink carrier.

[0009] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: receive a message indicating a triggered PHR state for a UE, the triggered PHR state indicating whether to enable transmission of a PHR triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold; and selectively transmit the PHR based on the triggered PHR state and the path loss change on the at least one uplink carrier.

[0010] In the methods described herein, in some examples of user equipment (UE) and non-transitory computer-readable media, messages include RRC messages.

[0011] Some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of a power control parameter configured for at least one of sounding reference signal (SRS) transmission, PUCCH transmission, or PUSCH transmission, wherein a trigger-based PHR condition indicating whether PHR transmission is enabled may be based on the power control parameter.

[0012] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, power control parameters include at least one of path loss value or path loss offset.

[0013] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of a power control parameter configured for uplink TCI state, wherein a trigger-based PHR condition indicating whether PHR transmission is enabled may be based on the power control parameter.

[0014] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, receiving a message may include operations, features, components, or instructions for detecting whether a path loss reference signal can be configured for at least one of: SRS transmission, PUCCH transmission, or PUSCH transmission, wherein a trigger-based PHR condition indicating whether PHR transmission is enabled may be based on the detection.

[0015] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, receiving a message may include operations, features, components, or instructions for detecting whether a path loss reference signal can be configured for uplink TCI status, wherein a trigger-based PHR condition indicating whether PHR transmission is enabled can be based on this detection.

[0016] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, selective transmission of a PHR may include operations, features, components, or instructions for: enabling PHR transmission based on a triggered PHR condition indication and transmitting the PHR based on a path loss change on at least one uplink carrier satisfying a path loss threshold.

[0017] In some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein, selective transmission of a PHR may include operations, features, components, or instructions for: detecting that a path loss change on the at least one uplink carrier may have met a path loss threshold; and disabling PHR transmission based on the triggered PHR condition indication to avoid transmitting a PHR.

[0018] A method for wireless communication by a UE is described. The method may include: transmitting a PHR during a PUSCH transmission on a first uplink carrier of the UE in a time slot, wherein a set of PUSCH transmissions on a second uplink carrier overlaps with the PUSCH transmissions on the first uplink carrier in the time domain within the time slot; and providing a PHR value for the second uplink carrier of the UE, the PHR value of the second uplink carrier including an actual PHR or a virtual PHR, wherein the selection of the actual PHR or virtual PHR for the second uplink carrier is based on the uplink transmission type of each PUSCH transmission in the PUSCH transmission set.

[0019] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to cause the UE to: transmit a PHR in a PUSCH transmission on a first uplink carrier of the UE during a time slot, wherein a set of PUSCH transmissions on a second uplink carrier overlaps with the PUSCH transmissions on the first uplink carrier in the time domain within the time slot; and provide a PHR value for a second uplink carrier of the UE, the PHR value of the second uplink carrier including an actual PHR or a virtual PHR, wherein the selection of the actual PHR or virtual PHR for the second uplink carrier is based on the uplink transmission type of each PUSCH transmission in the PUSCH transmission set.

[0020] Another UE for wireless communication is described. The UE may include: components for transmitting a PHR during a PUSCH transmission on a first uplink carrier of the UE during a time slot, wherein a set of PUSCH transmissions on a second uplink carrier overlaps in the time domain with the PUSCH transmissions on the first uplink carrier in the time slot; and components for providing a PHR value for a second uplink carrier of the UE, the PHR value of the second uplink carrier including an actual PHR or a virtual PHR, wherein the selection of the actual PHR or virtual PHR for the second uplink carrier is based on the uplink transmission type of each PUSCH transmission in the PUSCH transmission set.

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

[0022] Some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: detecting that at least one PUSCH transmission in a PUSCH transmission set can be associated with a specific uplink transmission type; and selecting an actual PHR for a second uplink carrier, wherein the actual PHR can be based on at least one PUSCH transmission being a first PUSCH transmission in the PUSCH transmission set that can be associated with that specific uplink transmission type.

[0023] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: detecting that each PUSCH transmission in the PUSCH transmission set may be associated with a non-specific transmission type; and selecting an actual PHR for a second uplink carrier based on this detection, wherein the actual PHR may be based on a first PUSCH transmission in the PUSCH transmission set.

[0024] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: detecting that each PUSCH transmission in the PUSCH transmission set may be associated with a non-specific uplink transmission type; and selecting a virtual PHR for a second uplink carrier based on this detection.

[0025] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: detecting that a first PUSCH transmission in a PUSCH transmission set may be associated with a specific uplink transmission type; and selecting an actual PHR for a second uplink carrier, wherein the actual PHR may be based on the first PUSCH transmission in the PUSCH transmission set.

[0026] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: detecting that a first PUSCH transmission in a PUSCH transmission set may be associated with a non-specific uplink transmission type; and selecting a virtual PHR for a second uplink carrier based on this detection.

[0027] Some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: associating at least one PUSCH transmission in a set of PUSCH transmissions with a path loss reference signal and for detecting whether the at least one PUSCH transmission can be associated with a specific uplink transmission type based on the unconfigured condition of the path loss or path loss offset associated with the at least one PUSCH transmission.

[0028] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for detecting whether at least one PUSCH transmission can be associated with a specific uplink transmission type based on an uplink TCI state associated with at least one PUSCH transmission in a set of PUSCH transmissions, wherein the uplink TCI state may be associated with a downlink path loss reference signal, a source downlink reference signal, a timing advance group identifier, or any combination thereof.

[0029] The methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for detecting whether at least one PUSCH transmission can be associated with a specific uplink transmission type based on permission granted for at least one PUSCH transmission in a scheduled PUSCH transmission set.

[0030] Some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for detecting whether at least one PUSCH transmission can be associated with a specific uplink transmission type based on path loss, path loss offset, or both associated with at least one PUSCH transmission in a set of PUSCH transmissions.

[0031] Some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for detecting whether at least one PUSCH transmission can be associated with a specific uplink transmission type based on the uplink TCI state associated with at least one PUSCH transmission in a set of PUSCH transmissions, wherein the uplink TCI state may be associated with path loss, path loss offset, SRS resource, timing advance group identifier, or any combination thereof.

[0032] The methods, user equipment (UE), and some examples of non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving RRC messages indicating a specific uplink transmission type.

[0033] A method for wireless communication by a UE is described. The method may include: selecting a virtual PHR for an uplink carrier, wherein power control parameters are configured for the uplink carrier, or a path loss reference signal is not configured for at least one of the SRS resource set, PUCCH, PUSCH, or TCI state, or any combination thereof, of the uplink carrier; and calculating the virtual PHR based on the selection and based on a set of PUSCH reference parameters, a path loss offset, or both.

[0034] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to cause the UE to: select a virtual PHR for an uplink carrier, wherein power control parameters are configured for the uplink carrier, or for at least one of the SRS resource set, PUCCH, PUSCH, or TCI state, or any combination thereof, of the uplink carrier, a path loss reference signal is not configured; and calculate the virtual PHR based at least in part on the selection and on a set of PUSCH reference parameters, a path loss offset, or both.

[0035] Another UE for wireless communication is described. This UE may include: components for selecting a virtual PHR for an uplink carrier, wherein power control parameters are configured for the uplink carrier, or for at least one of the SRS resource set, PUCCH, PUSCH, or TCI state, or any combination thereof, of the uplink carrier, there is a path loss reference signal non-configuration condition; and components for calculating the virtual PHR based on the selection and on a set of PUSCH reference parameters, a path loss offset, or both.

[0036] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: select a virtual PHR for an uplink carrier, wherein power control parameters are configured for the uplink carrier, or for at least one of the SRS resource set, PUCCH, PUSCH, or TCI state, or any combination thereof, of the uplink carrier, a path loss reference signal is not configured; and calculate the virtual PHR based at least in part on the selection and on a set of PUSCH reference parameters, a path loss offset, or both.

[0037] The methods described herein, some examples of user equipment (UE) and nontransitory computer-readable media may also include operations, features, components or instructions for identifying path loss offset based on at least one of a default path loss reference signal identifier, a default P0 nominal power level, a default uplink TCI state, a default path loss value, an indicated TCI state or any combination thereof.

[0038] Some examples of the methods, user equipment (UE), and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining to apply a path loss offset to a virtual PHR based on an indicated TCI state of the UE, wherein the indicated TCI state may be associated with a path loss offset.

[0039] Some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for determining the use of a set of PUSCH reference parameters for a virtual PHR based on the indicated TCI state of the UE, wherein the path loss offset may be in a non-configured state for the indicated TCI state.

[0040] The methods described herein, some examples of user equipment (UE) and non-transitory computer-readable media may also include operations, features, components or instructions for receiving an RRC message indicating whether to use path loss offset for virtual PHR.

[0041] A method for wireless communication by a UE is described. The method may include: selecting an actual PHR or a virtual PHR to be transmitted in a first PUSCH transmission on an uplink carrier of the UE, the selection being based on prior reception permission for a second PUSCH transmission scheduled with an uplink transmission type, wherein the prior reception permission was received before or during a physical downlink control channel (PDCCH) monitoring event in which the UE detects permission for the first PUSCH transmission on the first uplink carrier; and transmitting the actual PHR or virtual PHR in the first PUSCH transmission on the uplink carrier of the UE according to the selection.

[0042] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to cause the UE to: select an actual PHR or a virtual PHR to be transmitted in a first PUSCH transmission on an uplink carrier of the UE, the selection being based on prior reception permission for a second PUSCH transmission associated with an uplink transmission type, wherein prior reception permission was received before or during a PDCCH monitoring event in which the UE detects permission for 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 according to the selection.

[0043] Another UE for wireless communication is described. This UE may include: components for selecting an actual PHR or a virtual PHR to be transmitted in a first PUSCH transmission on the UE's uplink carrier, the selection being based on prior reception permission for scheduling a second PUSCH transmission associated with an uplink transmission type, wherein prior reception permission was received before or during a PDCCH monitoring event in which the UE detects permission for scheduling a first PUSCH transmission on the first uplink carrier; and components for transmitting the actual PHR or virtual PHR in the first PUSCH transmission on the UE's uplink carrier according to the selection.

[0044] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: select an actual PHR or a virtual PHR for transmission in a first PUSCH transmission on an uplink carrier of a UE, the selection being based on prior acceptance of a second PUSCH transmission scheduled with respect to an uplink transmission type, wherein prior acceptance was received before or during a PDCCH monitoring event in which the UE detects acceptance of a first PUSCH transmission on the first uplink carrier; and, according to the selection, transmit the actual PHR or the virtual PHR in the first PUSCH transmission on the uplink carrier of the UE.

[0045] Some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for selecting the actual PHR to be transmitted in the first PUSCH transmission based on the association of a second PUSCH transmission with a specific uplink transmission type, wherein the uplink transmission type includes the specific uplink transmission type.

[0046] Some examples of the methods, user equipment (UE), and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for selecting a virtual PHR to be transmitted in a first PUSCH transmission based on the association of a second PUSCH transmission with a nonspecific uplink transmission type, wherein the uplink transmission type includes a nonspecific uplink transmission type.

[0047] A method for wireless communication by a network entity is described. The method may include: sending a message to a UE indicating a triggered PHR state of the UE, the triggered PHR state indicating whether to enable the transmission of a PHR triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold; and selectively receiving the PHR based on the triggered PHR state and the path loss change on the at least one uplink carrier.

[0048] A network entity for wireless communication is described. The network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to cause the network entity to: send a message to a UE indicative of a triggered PHR state of the UE, the triggered PHR state indicating whether to enable the transmission of a PHR triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold; and selectively receive a PHR based on the triggered PHR state and the path loss change on the at least one uplink carrier.

[0049] Another network entity for wireless communication is described. This network entity may include: components for sending a message to a UE indicative of a triggered PHR state of the UE, the triggered PHR state indicating whether transmission of a PHR triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled; and components for selectively receiving the PHR based on the triggered PHR state and the path loss change on the at least one uplink carrier.

[0050] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: send a message to a UE indicative of a triggered PHR state of the UE, the triggered PHR state indicating whether to enable transmission of a PHR triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold; and selectively receive the PHR based on the triggered PHR state and the path loss change on the at least one uplink carrier.

[0051] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, messages include RRC messages.

[0052] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting an indication of a power control parameter configured for at least one of SRS transmission, PUCCH transmission, or PUSCH transmission, wherein a trigger-based PHR condition indicating whether PHR transmission is enabled may be based on the power control parameter.

[0053] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, power control parameters include at least one of path loss values ​​or path loss offsets.

[0054] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting an indication of a power control parameter configured for uplink TCI state, wherein a trigger-based PHR condition indicating whether PHR transmission is enabled may be based on the power control parameter.

[0055] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving a message may include operations, features, components, or instructions for detecting whether a path loss reference signal can be configured for at least one of: SRS transmission, PUCCH transmission, or PUSCH transmission, wherein a trigger-based PHR condition indicating whether PHR transmission is enabled may be based on the detection.

[0056] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, sending a message may include operations, features, components, or instructions for detecting whether a path loss reference signal can be configured for uplink TCI status, wherein a trigger-based PHR condition indicating whether PHR transmission is enabled can be based on this detection.

[0057] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, selectively receiving a PHR may include operations, features, components, or instructions for: enabling the transmission of a PHR based on a triggered PHR condition indication and receiving a PHR based on a path loss change on at least one uplink carrier satisfying a path loss threshold.

[0058] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, selectively receiving a PHR may include operations, features, components, or instructions for disabling the transmission of a PHR based on the triggered PHR condition to avoid receiving the PHR. Attached Figure Description

[0059] Figure 1 An example of a wireless communication system that supports enhanced power headroom for dense uplink deployments, according to one or more aspects of this disclosure, is shown.

[0060] Figure 2 An example of a wireless communication system that supports enhanced power headroom for dense uplink deployments, according to one or more aspects of this disclosure, is shown.

[0061] Figure 3A and Figure 3B An example of a scheduling configuration supporting power headroom enhancement for dense uplink deployments, according to one or more aspects of this disclosure, is shown.

[0062] Figure 4A and Figure 4B An example of a scheduling configuration supporting power headroom enhancement for dense uplink deployments, according to one or more aspects of this disclosure, is shown.

[0063] Figure 5 and Figure 6 A block diagram of a device supporting power headroom enhancement for dense uplink deployments, according to one or more aspects of this disclosure, is shown.

[0064] Figure 7 A block diagram is shown of a communication manager that supports power headroom enhancement for dense uplink deployments, according to one or more aspects of this disclosure.

[0065] Figure 8 A diagram is shown of a system including devices supporting power headroom enhancement for dense uplink deployments, according to one or more aspects of this disclosure.

[0066] Figure 9 and Figure 10 A block diagram of a device supporting power headroom enhancement for dense uplink deployments, according to one or more aspects of this disclosure, is shown.

[0067] Figure 11 A block diagram is shown of a communication manager that supports power headroom enhancement for dense uplink deployments, according to one or more aspects of this disclosure.

[0068] Figure 12A diagram is shown of a system including devices supporting power headroom enhancement for dense uplink deployments, according to one or more aspects of this disclosure.

[0069] Figures 13 to 17 A flowchart illustrating a method for enhancing power headroom for dense uplink deployments, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0070] Wireless networks can use Power Headroom Reporting (PHR) technology for power-aware packet scheduling performed by User Equipment (UE). Power headroom indicates the amount of available transmit power that a UE has, such as the difference between the UE's maximum transmit power and the transmit power used for uplink transmission. Uplink transmission may include Sounding Reference Signal (SRS) transmission, Physical Uplink Control Channel (PUCCH) transmission, or Physical Uplink Shared Channel (PUSCH) transmission, etc. Power headroom is typically calculated based on downlink reference signals (e.g., dedicated path loss reference signals or other reference signals) measured by the UE on downlink carriers. However, some network deployments may include uplink-only cells or downlink-only cells, where cells are configured with uplink (but no downlink) carriers or downlink (but no uplink) carriers, respectively. However, triggering PHR may be inefficient or ineffective when downlink reference signals are associated with downlink-only cells. In other words, the PHR technique is used to report the available transmit power of uplink transmission on the uplink carrier, and when downlink-only cells and uplink-only cells are associated with different propagation paths, it may be inappropriate to trigger a change in path loss on the downlink carrier from the UE's PHR.

[0071] Therefore, the techniques described herein provide for enabling and / or disabling PHR triggered by a threshold path loss change. For example, a UE may receive a message indicating a triggered PHR status for the UE. This status can be used to indicate whether to enable (or disable) transmission of a PHR triggered by a path loss change on at least one uplink carrier that satisfies a path loss threshold. The UE may selectively transmit PHR based on this triggered PHR status and the path loss change on the uplink carrier. For example, the UE may transmit PHR when transmission is enabled by the triggered PHR status, or may avoid transmitting PHR when transmission is disabled by the triggered PHR status (e.g., when a path loss change is detected to satisfy a path loss threshold).

[0072] In some aspects, the techniques described herein provide the transmission of actual PHR reports or virtual PHR reports on one or more additional uplink carriers. For example, a UE may transmit a PHR on its first uplink carrier during a time slot, such as during a PUSCH transmission. Additional PUSCH transmissions scheduled on the UE's second uplink carrier may overlap with PUSCH transmissions on the first uplink carrier in the time domain during a time slot. The UE may provide a PHR value for its second uplink carrier during a time slot. The PHR value may include an actual PHR or a virtual PHR. The UE may select between an actual PHR or a virtual PHR on the second uplink carrier based on, for example, the overlap in the time domain between a PUSCH transmission on the first uplink carrier and a second PUSCH transmission on the second uplink carrier, and based on, for example, the uplink transmission type used for PUSCH transmissions on the second uplink carrier. The uplink transmission type may generally refer to a designated or specific uplink transmission type that may be identified by network specification and other technologies, based on, for example, the association of uplink transmission with a downlink node or only an uplink node.

[0073] In some respects, the techniques described herein provide different methods for estimating channel performance metrics when transmitting a virtual PHR. For example, a UE can select a virtual PHR for an uplink carrier. Power control parameters can be configured for the uplink carrier, or based on, for example, an SRS resource set, PUCCH, PUSCH, and / or Transmission Configuration Indicator (TCI) state where the UE is not configured with an uplink carrier. The UE can calculate or otherwise determine the virtual PHR value based on, for example, a PUSCH reference parameter set, a path loss offset, or both. The virtual PHR can be based on, for example, a path loss offset included along with the estimation of the channel performance metric. That is, the path loss offset can be configured or otherwise indicated to the UE, which uses it as part of a formula for calculating the virtual PHR.

[0074] The aspects of this disclosure are first described in the context of wireless communication systems. These aspects are further illustrated and described by way of apparatus diagrams, system diagrams, and flowcharts relating to power clearance enhancement for dense uplink deployments.

[0075] Figure 1An example of a wireless communication system 100 supporting power headroom enhancement for dense uplink deployments according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0076] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0077] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0078] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, apparatus, device, 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 UE 115. As another example, a node may be 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 UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

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

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

[0081] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across 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, network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC, a non-real-time RIC), a service management and orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0082] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can 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 each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0083] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

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

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

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

[0087] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support power headroom enhancements for dense uplink deployments as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0088] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0089] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0090] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating 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 coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0091] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

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

[0093] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a particular radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0094] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0095] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, multiple BWPs can be used to configure UE 115. In some examples, a single BWP of a carrier can be active at a given time, and the communication of UE 115 can be constrained to one or more active BWPs.

[0096] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0097] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

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

[0099] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0100] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, or may include buildings, subsets of buildings, or external space between or overlapping coverage areas.

[0101] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells can be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and can operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells can provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 can support one or more cells and can also use one or more component carriers to support communication via one or more cells.

[0102] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0103] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

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

[0105] Some UE 115 devices (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices 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 geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial toll collection.

[0106] Some UE 115s can be configured to operate in reduced-power modes, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at reduced peak rates. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

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

[0108] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in this group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0109] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or a combination of these. Vehicles may signal information related to traffic conditions, signal control, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0110] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be transferred through user plane entities, which provide IP address allocation and other functions. User plane entities can connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0111] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is 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 these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0112] The wireless communication system 100 can also operate using the ultra-high frequency (SHF) region (also known as the centimeter band) in the range of 3 GHz to 30 GHz or the extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmissions, EHF transmissions may experience even greater attenuation and shorter range. The techniques disclosed herein can be adopted across transmissions using one or more different frequency regions, and the frequency band usage specified across these frequency regions may vary by country or regulatory authority.

[0113] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

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

[0115] Network entity 105 or UE 115 may use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique may be referred to as spatial multiplexing. The multiple signals may be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports 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 multi-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

[0116] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

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

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

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

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

[0121] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0122] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0123] UE 115 may receive a message indicating a triggered PHR status for UE 115, the triggered PHR status indicating whether to enable the transmission of a PHR triggered by a path loss change on at least one uplink carrier of UE 115 satisfying a path loss threshold. UE 115 may selectively transmit PHR based on the triggered PHR status and the path loss change on at least one uplink carrier.

[0124] UE 115 may transmit a PHR during PUSCH transmissions on a first uplink carrier of UE 115 during a time slot, wherein the PUSCH transmission set on a second uplink carrier overlaps with the PUSCH transmissions on the first uplink carrier in the time domain within the time slot. UE 115 may provide a PHR value for the second uplink carrier of UE 115, the PHR value of the second uplink carrier including an actual PHR or a virtual PHR, wherein the selection of the actual PHR or virtual PHR for the second uplink carrier is at least partially based on the uplink transmission type of each PUSCH transmission in the PUSCH transmission set.

[0125] UE 115 can select a virtual PHR for an uplink carrier, where power control parameters are configured for the uplink carrier, or where there is a path loss reference signal unconfigured condition for at least one of the SRS resource set, PUCCH, PUSCH, or TCI state, or any combination thereof, of the uplink carrier. UE 115 can calculate the virtual PHR based at least in part on this selection and at least in part on the PUSCH reference parameter set, path loss offset, or both.

[0126] UE 115 can select either an actual PHR or a virtual PHR to be transmitted in a first PUSCH transmission on an uplink carrier of UE 115. This selection is based at least in part on prior reception permission for a second PUSCH transmission scheduled with respect to the uplink transmission type, wherein the prior reception permission was received before or during the PDCCH monitoring event at which UE 115 detects permission for the first PUSCH transmission on the first uplink carrier. UE 115 can then transmit either an actual PHR or a virtual PHR in the first PUSCH transmission on its uplink carrier according to this selection.

[0127] Network entity 105 may send a message to UE 115 indicative of a triggered PHR status for UE 115, the triggered PHR status indicating whether to enable the transmission of a PHR triggered by a path loss change on at least one uplink carrier of UE 115 satisfying a path loss threshold. Network entity 105 may selectively receive PHRs based on the triggered PHR status and the path loss change on at least one uplink carrier.

[0128] Figure 2 An example of a wireless communication system 200 supporting power headroom enhancement for dense uplink deployments, according to one or more aspects of this disclosure, is shown. The wireless communication system 200 may implement aspects of the wireless communication system 100. The wireless communication 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.

[0129] For example, wireless communication system 200 can be a non-limiting example of a dense uplink deployment scenario, where one or more uplink receiving points are configured within the network and associated with a network entity, such as network entity 210. Dense uplink deployment can provide asymmetric downlink / uplink density to improve uplink capacity and coverage. Uplink signals or channels from UE 205 are received at the uplink receiving point. Downlink signals or channels are transmitted from network entity 210, which may also be referred to as a macro node, central node, serving cell, serving base station, or similar terms. The uplink receiving point may be connected to network entity 210 via a backhaul connection. The uplink receiving point can provide uplink communication from UE 205 to network entity 210 via the backhaul network. Dense uplink deployment can reduce uplink path loss (PL), which can be helpful when uplink coverage areas are bottlenecks. This can also improve the deployment cost and complexity of the wireless network, as the uplink receiving point may not transmit any downlink signals. In other words, the uplink receiving point can receive uplink signals from UE 205 and transmit information to network entity 210 via backhaul, with or without some processing. Uplink-only device 215, uplink-only device 220, and uplink-only device 225 can be non-limiting examples of uplink receiving points in dense uplink deployments.

[0130] The PHR (Power Headroom) technology provides UE 205 with a mechanism to transmit or otherwise provide an indication of the available uplink transmit power for UE 205. That is, each UE may have a maximum transmit power it is capable of providing for radio transmission. The maximum transmit power is typically designed for the UE and the wireless network based on permissible exposure limits defined in various regulations or management standards. The maximum transmit power may be based, at least in part, on the operational capabilities or configuration of UE 205. The PHR may typically carry or otherwise transmit an indication of the power headroom for UE 205, which is generally the difference between the UE 205's maximum transmit power and the current transmit power used for uplink transmission over the channel.

[0131] There are typically three types of PHRs that can be reported by UE 205. Type 1 PHRs can be used for PUSCH (e.g., uplink transmission on PUSCH), Type 2 PHRs can be used for PUCCH (e.g., uplink transmission on PUCCH), and Type 3 PHRs can be used for SRS (e.g., for SCells that are only configured with SRS).

[0132] Furthermore, PHR technology can typically define two types of reportable PHRs: actual PHRs or virtual PHRs. Broadly speaking, actual PHRs can be used to calculate the timing of a specific PUSCH transmission. iThe PHR of the reference PUSCH is used to calculate the PHR sent by the reference PUSCH.

[0133] More specifically, the actual PHR reported by UE 205 for PUSCH (e.g., Type 1) can be calculated, operated on, or otherwise determined using the following formula: [dB] in This is the maximum output power configured for the UE after power back-off due to power management (e.g., back-off due to Maximum Allowable Reduction (MPR) limits), and the remaining parameters are used to determine the timing of a specific PUSCH transmission. i The parameters of the PUSCH transmit power.

[0134] The virtual PHR reported by UE 205 can be calculated, operated on, or otherwise determined using the following formula: [dB] in It is calculated under the assumption of no backoff (e.g., assuming an MPR value of 0 dB), and the remaining parameters are based on j , i , l and q d The default or reference parameter.

[0135] UE 205 may send a PHR to network entity 210 based on multiple 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 path loss change greater than a configured threshold (e.g., a path loss threshold) for at least one path loss reference signal (PL-RS) used for power control in any uplink carrier. Other examples of triggers may be based on SCell activation, activation of the configured CC's BWP, a change from sleep to non-sleep, or vice versa.

[0136] Once triggered, a PHR can be reported in the PHRMAC-CE on the first available PUSCH corresponding to the initial transmission of the transport block (TB), which may accommodate the MAC-CE due to Logical Channel Prioritization (LCP). The PUSCH can be a dynamic PUSCH (e.g., scheduled by DCI grant), or the PUSCH can be semi-persistent in nature (e.g., configuration-granted PUSCH). The UE 205 can be configured with multiple CCs (e.g., multiple uplink carriers) for PUSCH transmission. For example, if enabled... multiple PHRParameters, such as enabling with RRC signaling, allow the PHR MAC-CE to include PHR reports for more than one carrier. Otherwise, PHRs can be reported for PCells, and a single-entry MAC-CE format can be used. When the first PUSCH in the first uplink carrier carries a MAC-CE PHR, the MAC-CE for the second uplink carrier can include either an actual PHR or a virtual PHR. This can depend on whether a PUSCH is being transmitted on the second uplink carrier at the time of the PHR report (e.g., in the same time 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 meets the timeline conditions. Otherwise, UE 205 can report a virtual PHR.

[0137] A single-entry PHR MAC-CE may include a set of bits for transmitting the PHR. A multi-entry PHR MAC-CE may use a bitmap, where each bit represents the PHR for a specific uplink carrier (other than PCell). The PHR MAC-CE may also indicate whether power back-off is applied by the MAC entity due to power management (e.g., power back-off related to MPR). P Parameters. The PHR MAC-CE can also indicate whether it is associated with reporting an actual PHR or a virtual PHR. V Parameters, among which corresponding parameters may exist when reporting the actual PHR. Field.

[0138] However, in dense uplink deployment scenarios, there may be no downlink reference signal from the uplink receiving point (e.g., uplink-only device 215, uplink-only device 220, or uplink-only device 225). To determine the uplink transmit power, two approaches can be applied. One approach may include power control due to changes in uplink path loss configured or indicated by network entity 210. For example, transmit power control (TPC) commands in MAC-CE or DCI can be used to update the closed-loop power P0 or path loss value.

[0139] Another approach could be to indicate a path loss offset to UE 205, and UE 205 could derive the uplink path loss based on the downlink path loss measured on the downlink reference signal and the indicated path loss offset. That is, for example, the path loss offset could be measured, calculated, or otherwise determined based on the true or estimated difference between the downlink path loss associated with network entity 210 and the uplink path loss associated with uplink-only device 215. For downlink nodes (such as network entity 210), the downlink reference signal and uplink transmit power could be determined based on the path loss measured on the downlink reference signal (e.g., because the downlink path and uplink path are at least somewhat inverse of each other).

[0140] However, such techniques can become problematic in some scenarios. Specifically, a Power-Aware Response (PHR) is typically provided to network entity 210 to support power-aware scheduling. For PUSCH transmissions to the uplink receiving point (e.g., uplink-only device 215 in this example), either scheme can be used for the PHR. In the first scheme, the uplink transmission power can be entirely controlled by network entity 210, and therefore a PHR to uplink-only device 215 may be unnecessary. In the second scheme, although the path loss offset can be indicated to UE 205, network entity 210 may not be aware of the downlink path loss of the downlink channel. Therefore, when the path loss change exceeds a configured threshold, UE 205 may still need to provide a PHR to network entity 210 to support power-aware scheduling.

[0141] For the downlink receiver, whether a PHR is required can be based on whether PUSCH transmission to the downlink receiver is allowed. If so, a PHR may be required when the path loss changes to meet a configured threshold (e.g., a path loss threshold). If not, a PHR may not be required when the path loss changes to meet a configured threshold.

[0142] Therefore, in some wireless networks, a PHR can be triggered when the path loss change exceeds a path loss threshold configured for at least one path loss reference signal used for power control in the uplink carrier. For the first scenario, triggering a PHR when the path loss change meets the path loss threshold may be inefficient since the uplink transmit power is controlled by network entity 210 when the PUSCH is not sent to the downlink receiving point. PHR triggering may be necessary when the PUSCH is sent to the downlink receiving point. In some respects, a PHR for the PUSCH to the downlink receiving point may be relatively more useful than a PHR for the uplink receiving point.

[0143] Furthermore, in the second scheme, when a PUSCH is sent to either the downlink or uplink receiving point, if there is more than one PUSCH in the PHR MAC-CE time slot, it is unclear which PHR (actual PHR or virtual PHR) should be reported. For both schemes, when reporting the virtual PHR, given that different power control formulas can be used between PUSCHs destined for the uplink and downlink receiving points, such networks may not be able to correctly define how to calculate the PHR.

[0144] Therefore, the aspects of the techniques described herein provide various improvements to such PHR reporting techniques. These aspects of the techniques described herein can be implemented in dense uplink deployment scenarios, such as wireless networks using uplink receivers, downlink receivers, or both. In some aspects, the described techniques can be applied when the UE 205 is configured with multiple uplink carriers (e.g., two or more uplink carriers).

[0145] The described aspects of the technology provide for PHR triggering based on a configured path loss threshold for a path loss change greater than at least one path loss reference signal on any uplink carrier of UE 205. For example, UE 205 may receive or otherwise obtain (and network entity 210 may send or otherwise provide to output) a message indicating a trigger-based PHR status for UE 205. The trigger-based PHR status may indicate whether the transmission of a PHR triggered by a path loss change on at least one uplink carrier of UE 205 that satisfies a path loss threshold (e.g., a configured threshold) is enabled (or disabled). In some examples, the condition for disabling PHR triggering may be (pre)defined or received in an RRC message.

[0146] UE 205 may selectively transmit a PHR based on a triggered PHR condition and a path loss change on at least one uplink carrier. For example, the UE may transmit a PHR when a triggered PHR condition indicates that PHR transmission is enabled based on a path loss change meeting a path loss threshold. The UE may avoid transmitting a PHR when a triggered PHR condition indicates that PHR transmission is disabled based on a path loss change meeting a path loss threshold. For example, UE 205 may identify, detect, or otherwise determine that a path loss change has met a path loss threshold for at least one uplink carrier of UE 205, and may also avoid transmitting a PHR based on a triggered PHR condition.

[0147] In some aspects, the triggered PHR condition can be based on the fact that uplink-only device 215 is configured for at least one or all uplink carriers of UE 205. Different techniques can be used to identify or otherwise determine whether uplink-only device 215 has been configured for one or more uplink carriers of UE 205. One technique could be that UE 205 is explicitly configured with information identifying uplink-only device 215 for UE 205. Explicit configuration can be based on RRC signaling or other signaling mechanisms.

[0148] Another technique can be based on configuring new power control parameters (e.g., path loss or path loss offset) for SRS transmission, PUCCH transmission, or PUSCH transmission. For example, a triggered PHR condition can be based on power control parameters (e.g., path loss or path loss offset) configured for SRS / PUCCH / PUSCH. UE 205 may receive or otherwise obtain an indication of the power control parameters configured for SRS / PUCCH / PUSCH from network entity 210. When power control parameters are configured, this can indicate to UE 205 that only uplink device 215 has been configured for UE 205.

[0149] Another technique can be based on configuring new power control parameters (e.g., path loss or path loss offset) for at least one uplink TCI state (e.g., when a unified TCI state is configured). For example, UE 205 may receive or otherwise obtain an indication of the uplink TCI state from network entity 210. Triggered PHR states can be based on power control parameters. For example, when power control parameters are configured for the uplink TCI state, this can indicate to UE 205 that only uplink device 215 has been configured for UE 205.

[0150] Another technique can be based on the fact that a path loss reference signal is not configured for at least one SRS resource set, PUCCH, or PUSCH (e.g., a path loss reference signal in an unconfigured state or condition). For example, UE 205 can identify, detect, or otherwise determine whether a path loss reference signal is configured for at least one of SRS transmission, PUCCH transmission, or PUSCH transmission. Similarly, a triggered PHR condition can be based on whether network entity 210 has configured a path loss reference signal for UE 205. That is, if the path loss reference signal is not configured for an SRS resource set, PUCCH, or PUSCH, this can indicate to UE 205 that only uplink device 215 has been configured for UE 205.

[0151] The final technique can be based on the fact that a path loss reference signal is not configured for at least one uplink TCI state (again, when a unified TCI state is configured) (e.g., in an unconfigured state or condition). For example, UE 205 can identify, detect, or otherwise determine whether a path loss reference signal is configured for an uplink TCI state. A triggered PHR state can be used to determine whether network entity 210 has already configured a path loss reference signal for UE 205. That is, the fact that a path loss reference signal is not configured for an uplink TCI state can indicate to UE 205 that only uplink device 215 has been configured for UE 205.

[0152] Therefore, UE 205 can use such techniques to receive, detect, or otherwise determine whether only uplink device 215 has been configured for uplink carrier and apply trigger-based PHR conditions accordingly.

[0153] Figure 3A and Figure 3B An example of a scheduling configuration 300 supporting power headroom enhancement for dense uplink deployments, according to one or more aspects of this disclosure, is shown. The scheduling configuration 300 may implement aspects of wireless communication system 100 or wireless communication system 200. The aspects of the scheduling configuration 300 may be implemented or be implemented by a UE, a network entity, or an uplink-only device, which may be examples of the corresponding devices described herein.

[0154] Scheduling configuration 300 illustrates a non-limiting example of techniques for selecting, identifying, or otherwise determining the PHR to be indicated for a second uplink carrier for a UE. As discussed above, when a UE is configured with multiple uplink carriers (e.g., CC1 and CC2 in this non-limiting example) and a first PUSCH on the first uplink carrier carries or otherwise transmits a PHR MAC-CE, the MAC-CE may carry either the actual PHR or a virtual PHR for the second uplink carrier. In some wireless networks, whether an actual or virtual PHR is transmitted may depend on whether a PUSCH transmission exists on the second uplink carrier in the same time slot and whether the DCI scheduling the PUSCH transmission on the second uplink carrier satisfies a timeline condition relative to the DCI scheduling the PUSCH transmission on the first uplink carrier. However, these techniques for determining whether to provide an actual or virtual PHR for the second uplink carrier may be inefficient or otherwise problematic in some scenarios.

[0155] Therefore, the aspects of the techniques described herein provide an improved mechanism for determining whether to provide an actual PHR or a virtual PHR for the second uplink carrier based on the uplink transmission type of the PUSCH transmissions scheduled in the second uplink carrier. Specifically, the 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 to report an actual PHR value or a virtual PHR value.

[0156] For example, the UE can be in a time slot (e.g., during a time slot) n During this period, the PHR is transmitted or otherwise provided to be output (and can be received or otherwise obtained by the network entity) in the PUSCH transmission on the UE's first uplink carrier. In this non-limiting example, this may include a time slot on the UE's first uplink carrier (e.g., CC1). n DCI reception during -2 period is permitted 305. In time slot n DCI received on CC1 during -2 is permitted to be scheduled in time slot 305. n During this period, PUSCH is sent on CC1.

[0157] The PUSCH transmission set in the second uplink carrier (e.g., CC2) can overlap with the PUSCH transmission on CC1 in the time domain within time slot n. For example, the UE can transmit PUSCH in time slot n. n During the -3 period, if a DCI is received or otherwise obtained (and the network entity may send or otherwise provide it for output), 305 is granted, which allows scheduling in the time slot. n During this period, PUSCH is transmitted on CC2. The UE may also receive or otherwise obtain (and the network entity may send or otherwise provide for output) DCI granted 305 during time slot n-2 on CC2, which is scheduled in time slot. n During this period, PUSCH is sent on CC2. Therefore, in this non-limiting example, in the time slot... n The set of PUSCH transmissions on CC2 during this period includes two PUSCH transmissions. The overlap in the time domain may correspond to one or more symbols of a PUSCH transmission scheduled on CC2 that are the same symbols used for a PUSCH transmission scheduled on CC1 carrying a PHR MAC-CE. The UE may select, calculate, or otherwise provide the actual PHR or virtual PHR as the PHR value for CC2 based on the uplink transmission type of each PUSCH transmission scheduled on CC2.

[0158] Specifically, the uplink transmission type can be a specific PUSCH 310 or a non-specific PUSCH 315. Various methods can be applied to identify or otherwise determine whether a PUSCH transmission is a specific PUSCH 310 or a non-specific PUSCH 315. In some respects, this can be based on whether the PUSCH is associated with a downlink receiving point or an uplink receiving point.

[0159] For example, the first method may include identifying or otherwise detecting a specific PUSCH 310 based on whether a PUSCH transmission is associated with a downlink receiving point. A specific PUSCH 310 may be a PUSCH associated with a downlink path loss reference signal but not with a path loss or path loss offset configured for PUSCH transmission. For example, the UE may identify or otherwise detect whether at least one PUSCH transmission on CC2 is a specific PUSCH 310 based on associating a PUSCH transmission with a path loss reference signal and based on the fact that a path loss or path loss offset is not configured (e.g., in an unconfigured state or condition) for PUSCH transmission. In this example, a specific PUSCH 310 may include a PUSCH transmission associated with a path loss reference signal but not with a path loss or path loss offset value.

[0160] Another approach may include identifying or otherwise detecting a specific PUSCH 310 based on whether the PUSCH transmission is associated with an uplink TCI state, wherein the uplink TCI state is associated with a downlink path loss reference signal, a source downlink reference signal, or a specific timing advance group (TAG) (e.g., the first TAG or the lowest TAG). In this example, a specific PUSCH 310 may be a PUSCH transmission associated with an uplink TCI state when the uplink TCI state is associated with a downlink path loss reference signal, a source downlink reference signal, or a specific TAG identifier. Therefore, the UE may identify or otherwise detect at least one PUSCH transmission on CC2 based on the association of the uplink TCI state with the downlink path loss reference signal, the source downlink reference signal, the TAG identifier, or any combination of these associations.

[0161] One approach may include identifying or otherwise detecting a specific PUSCH 310 based on a scheduled 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 DCI permission granted for the scheduled PUSCH transmission.

[0162] Additionally or alternatively, a specific PUSCH 310 can be identified or otherwise detected based on whether the PUSCH transmission is associated with an uplink receiving point. Different methods can be used to identify or otherwise determine whether a PUSCH transmission on CC2 is a specific PUSCH 310 associated with an uplink receiving point. One method may include whether the PUSCH transmission is associated with path loss or path loss offset. For example, the UE may identify or otherwise detect whether at least one PUSCH transmission scheduled on CC2 is associated with path loss or path loss offset. If so, this may indicate that the PUSCH transmission is a specific PUSCH 310.

[0163] Another approach can be based on whether the PUSCH transmission is associated with an uplink TCI state, where the uplink TCI state is associated with path loss or path loss offset, with source SRS resources, or with a specific TAG identifier (e.g., the second or highest TAG identifier). For example, the UE can 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 path loss, path loss offset, SRS resources, or TAG identifier.

[0164] One approach may include identifying or otherwise detecting a specific PUSCH 310 based on a scheduled 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 DCI permission granted for the scheduled PUSCH transmission.

[0165] Additionally or alternatively, another method for identifying, detecting, or otherwise distinguishing a specific PUSCH 310 from a non-specific PUSCH 315 may include RRC signaling to indicate or otherwise identify a specific PUSCH 310 for the UE. That is, an RRC message can be used to configure a specific PUSCH 310 for the UE. For example, an RRC message may indicate whether a specific PUSCH 310 transmission is associated with a downlink receive point or an uplink receive point.

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

[0167] Figure 3A The scheduling configuration 300-a illustrates a non-limiting example of at least one PUSCH transmission (second PUSCH transmission) scheduled on CC2 associated with a specific uplink transmission type (e.g., a specific PUSCH 310). Figure 3B The scheduling configuration 300-b illustrates a non-limiting example of PUSCH transmissions scheduled on CC2 that are not associated with a specific uplink transmission type. This can be based on [the context of] time slots. n During this period, each PUSCH sent on CC2 is associated with an uplink transmission type to apply different options, choosing between the actual PHR value or the virtual PHR value to be reported to CC2.

[0168] One option may include: if at least one PUSCH transmission on CC2 is a specific PUSCH 310, then select the actual PHR for the second uplink carrier (CC2). Figure 3A In the non-limiting example illustrated in scheduling configuration 300-a, the UE may detect, identify, or otherwise determine that at least one PUSCH in CC2 is a specific PUSCH 310. For example, in a time slot n DCI received on CC2 during -2 period is permitted to be scheduled in time slot 305. n During this period, a specific PUSCH 310 is used for the UE. In the time slot... n The DCI grant 305 received on CC2 during period -2 satisfies the timeline requirement relative to the DCI grant 305 received on CC1, and the DCI grant is scheduled in the time slot. n The PHR MAC-CE of the PUSCH scheduled on CC1 during this period. Furthermore, a specific PUSCH 310 scheduled on CC2 can overlap with the PHR MAC-CE scheduled on CC1 in the time domain. Therefore, in this option, the UE can... n During this period, the actual PHR is selected for CC2. The actual PHR can be based on the specific PUSCH 310 transmission in the time slot. nThe first transmission of PHR MAC-CE overlap carried or otherwise transmitted on CC1 during this period.

[0169] exist Figure 3B In the non-limiting example illustrated in scheduling configuration 300-b, the UE may detect, identify, or otherwise determine that each PUSCH in CC2 is a non-specific PUSCH 315. For example, in a time slot n -3 during the period received on CC2, DCI was granted 305 and in time slot n DCI received during -2 is permitted for 305, both of which can be scheduled in time slots. n During this period, non-specific PUSCH 315 transmissions are used for UE. (In the time slot) n -3 during the period received on CC2, DCI was granted 305 and in time slot n The DCI grant 305 received on CC2 during the -2 period can satisfy the timeline requirements relative to the DCI grant 305 received on CC1, and the DCI grant is scheduled in the time slot. n The PHR MAC-CE of the PUSCH scheduled on CC1 during this period. Furthermore, the non-specific PUSCH 315 transmission scheduled on CC2 can overlap with the PHR MAC-CE scheduled on CC1 in the time domain. Therefore, in this option, the UE can... n During this period, the actual PHR is selected for CC2. Furthermore, the actual PHR can be based on the non-specific PUSCH 315 transmission in the time slot. n The first transmission of PHR MAC-CE overlap carried or otherwise transmitted on CC1 during this period.

[0170] Another option may include: the UE selecting the actual PHR or the virtual PHR based on whether a specific PUSCH 310 overlaps with the PHRMAC-CE carried in the PUSCH transmission on CC1 and is scheduled on CC2. Figure 3A In the non-limiting example illustrated in scheduling configuration 300-a, the UE may detect, identify, or otherwise determine that at least one PUSCH in CC2 is a specific PUSCH 310. Therefore, in this option, the UE may... n During this period, the actual PHR is selected for CC2. Furthermore, the actual PHR can be based on the specific PUSCH 310 transmission and the time slot. n The first transmission of PHR MAC-CE overlap carried or otherwise transmitted on CC1 during this period.

[0171] exist Figure 3BIn the non-limiting example illustrated in scheduling configuration 300-b, 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). Therefore, in this option, the UE may... n During this period, a virtual PHR is selected for CC2. Furthermore, the virtual PHR can be based on a reference PUSCH. Aspects of this option can be used in the first scenario discussed above, where uplink transmit power is entirely controlled by the network entity. In this case, there may be no PUSCH transmission toward the downlink receiving point in time slot n, which allows the virtual PHR toward the downlink receiving point to be prioritized over the actual PHR toward the uplink receiving point.

[0172] Another option may include: the UE selecting the actual PHR or the virtual PHR based on whether the first PUSCH in the PUSCH transmission set scheduled on CC2 is a specific PUSCH 310 or a non-specific PUSCH. Figure 3A Scheduling configuration 300-a and Figure 3B In the non-limiting examples illustrated in both scheduling configurations 300-b, the UE may detect, identify, or otherwise determine that the first PUSCH transmission scheduled on CC2 (e.g., the first PUSCH transmission in the time domain) is a non-specific PUSCH 315. Therefore, in this option, the UE may... n During this period, a virtual PHR is selected for CC2. Furthermore, the virtual PHR can be based on the first PUSCH transmission on CC2 being a non-specific PUSCH 315. Conversely, in the 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 can select an actual PHR for CC2. The actual PHR can be based on the time slot... n The first PUSCH scheduled on CC2 is transmitted during this period. Therefore, in this option, if the first PUSCH in the set of PUSCHs scheduled on CC2 is a specific PUSCH 310, the UE can report the actual PHR based on the first PUSCH. Otherwise, the UE can report a virtual PHR.

[0173] Additionally or alternatively, aspects of the techniques described herein provide the ability to identify, select, or otherwise calculate a virtual PHR based on a path loss offset when reporting a virtual PHR. For example, a UE may identify, select, or otherwise determine a virtual PHR for an uplink carrier based on power control parameters configured for the uplink carrier or based on an SRS resource set, PUCCH, PUSCH, TCI state, or any combination thereof when the path loss reference signal is not configured (e.g., in an unconfigured state) for the uplink carrier. For example, a UE may select a virtual PHR for an uplink carrier and calculate the virtual PHR based on a PUSCH reference parameter or a path loss offset. Specifically, an example of a formula for calculating or otherwise calculating a virtual PHR may be based on: [dB] However, aspects of the described techniques may include calculating the virtual PHR based on a default path loss offset. For example, the formula described above for calculating the virtual PHR may be modified to include or otherwise base it on the path loss offset configured for the UE and the PUSCH reference parameter. A non-limiting example of such modification may include: [dB]

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

[0175] Whether to use path loss offset to calculate the virtual PHR can be based on the TCI state indicated by the UE. For example, if the indicated TCI state is not associated with the path loss offset (e.g., the path loss offset is in an unconfigured state or condition relative to the indicated TCI state), the UE can calculate the virtual PHR without path loss offset modification. If the indicated TCI state is associated with the path loss offset, the UE can use path loss offset modification to calculate the virtual PHR.

[0176] In another option, the UE can be configured (e.g., using RRC signaling) to have an indicator of whether to use path loss offset when calculating the virtual PHR of the uplink carrier.

[0177] Figure 4A and Figure 4B An example of a scheduling configuration 400 supporting power headroom enhancement for dense uplink deployments, according to one or more aspects of this disclosure, is shown. The scheduling configuration 400 may implement aspects of wireless communication system 100 or wireless communication system 200, or aspects of scheduling configuration 300. The aspects of scheduling configuration 400 may be implemented or be implemented by a UE, a network entity, or an uplink-only device, which may be examples of the corresponding devices described herein.

[0178] Scheduling configuration 400 illustrates non-limiting examples of techniques for selecting, identifying, or otherwise determining the PHR (e.g., actual PHR or virtual PHR) to be indicated for an uplink carrier (e.g., CC1 in this non-limiting example) for a UE. Aspects of the techniques described herein provide improved mechanisms for determining whether to provide an actual PHR or a virtual PHR for an uplink carrier based on the uplink transmission type of the PUSCH transmission scheduled on the uplink carrier. Specifically, aspects of the techniques described herein use the uplink transmission type of the PUSCH transmission carrying the PHR MAC-CE scheduled on the first uplink carrier to identify or otherwise determine whether to report an actual PHR value or a virtual PHR value.

[0179] For example, the UE may identify, select, or otherwise determine the actual or virtual PHR to be transmitted in a first PUSCH transmission on the UE's uplink carrier. This selection may be based on a previously received grant that schedules a second PUSCH transmission associated with the uplink transmission type. In this example, the previously received grant may be received before (or during) a PDCCH monitoring event that detects the grant scheduled for the first PUSCH transmission on the uplink carrier. In this non-limiting example, this may include a time slot on the first uplink carrier (e.g., CC1). n DCI reception during -2 period is permitted 405. In time slotn DCI received on CC1 during -2 is permitted to be scheduled in time slot 305. n During this period, PUSCH transmissions are performed on CC1. For example, the UE may monitor the PDCCH during the monitoring period to receive DCI permission 405 for PUSCH transmissions scheduled to carry PHR MAC-CE on CC1.

[0180] exist Figure 4A In the scheduling configuration 400-a, in the time slot n During this period, PUSCH transmissions scheduled on CC1 can be specific to PUSCH 410. Figure 4B In the scheduling configuration 400-b, in the time slot n During this period, PUSCH transmissions scheduled on CC1 can be non-specific PUSCH 415. Techniques for identifying, determining, or otherwise distinguishing specific PUSCH 410 from non-specific PUSCH 415 have been discussed above.

[0181] The PUSCH transmission set in the second uplink carrier (e.g., CC2) can overlap with the PUSCH transmission on CC1 in the time domain within time slot n. For example, the UE can transmit PUSCH in time slot n. n During the -3 period, if a DCI is received or otherwise obtained (and the network entity may send or otherwise provide it for output), 405 is granted, which allows scheduling in the time slot. n During this period, PUSCH is transmitted on CC2. The UE may also receive or otherwise obtain (and the network entity may send or otherwise provide for output) DCI granted 405 during time slot n-2 on CC2, which is scheduled in time slot. n During this period, PUSCH is sent on CC2. Therefore, in this non-limiting example, in the time slot... n The PUSCH transmission set on CC2 during this period includes two PUSCH transmissions. The UE may select, calculate, or otherwise provide the actual PHR or virtual PHR as the PHR value of CC2 based on the uplink transmission type of each PUSCH transmission scheduled on CC2, as discussed above.

[0182] Regarding time slots n During the PUSCH transmission on CC1, the UE can select the actual PHR or the virtual PHR based on whether the PUSCH transmission is a specific PUSCH 410. Figure 4A In the unrestricted example scheduling configuration 400-a, in the time slot n The PUSCH transmission scheduled on CC1 during this period can be a specific PUSCH 410. In this example, the UE can choose to report the actual PHR in the MAC-CE transmitted by a specific PUSCH 410.

[0183] exist Figure 4B In the unrestricted example scheduling configuration 400-b, in the time slot n The PUSCH transmission scheduled on CC1 during this period can be a non-specific PUSCH 415. In this example, the UE can choose a virtual PHR to be reported in the MAC-CE transmitted via a non-specific PUSCH 415.

[0184] Therefore, the scheduling configuration 400 illustrates a non-limiting example where the UE determines the uplink carrier's PHR based at least in part on the DCI of a scheduling-specific PUSCH 410 based on whether it is based on actual transmission (e.g., actual PHR) or a reference format (e.g., virtual PHR), the UE receiving that specific PUSCH up to and including the PDCCH monitoring timing (e.g., before and during the PDCCH monitoring timing), in which the UE detects the first DCI format of the initial transmission of the TB since the PHR was triggered if a PHR is reported on a PUSCH triggered by the first DCI format.

[0185] Figure 5 A block diagram 500 is shown of a device 505 supporting power headroom enhancement for dense uplink deployments according to one or more aspects of this disclosure. Device 505 may be an example of various aspects of UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505, or one or more components of device 505 (e.g., receiver 510, transmitter 515, and communication manager 520), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0186] Receiver 510 may provide components 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 clearance enhancement for dense uplink deployments). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0187] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, 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 clearance enhancement for dense uplink deployments). In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0188] The communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of power headroom enhancement for dense uplink deployments as described herein. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

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

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

[0191] In some examples, the communication manager 520 may be configured to use a receiver 510, a transmitter 515, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 520 may receive information from the receiver 510, transmit information to the transmitter 515, or integrate with the receiver 510, the transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0192] Communication manager 520 may support wireless communication according to examples disclosed herein. For example, communication manager 520 may be capable of, configured to, or operable to support components for receiving a message indicative of a triggered PHR state for a UE, the triggered PHR state indicating whether transmission of a PHR triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled. Communication manager 520 may be capable of, configured to, or operable to support components for selectively transmitting a PHR based on the triggered PHR state and a path loss change on at least one uplink carrier.

[0193] Additionally or alternatively, the communication manager 520 may support wireless communication according to examples disclosed herein. For example, the communication manager 520 may be capable of, configured to, or operable to support components for transmitting a PHR in a PUSCH transmission on a first uplink carrier of the UE during a time slot, wherein the PUSCH transmission set on a second uplink carrier overlaps in the time domain with the PUSCH transmission on the first uplink carrier in that time slot. The communication manager 520 may be capable of, configured to, or operable to support components for providing a PHR value for a second uplink carrier of the UE, the PHR value of the second uplink carrier including an actual PHR or a virtual PHR, wherein the selection of the actual PHR or virtual PHR for the second uplink carrier is based on the uplink transmission type of each PUSCH transmission in the PUSCH transmission set.

[0194] Additionally or alternatively, the communication manager 520 may support wireless communication according to examples disclosed herein. For example, the communication manager 520 may be capable of, configured to, or operable to support components for selecting a virtual PHR for an uplink carrier, wherein power control parameters are configured for the uplink carrier, or a path loss reference signal non-configured condition exists for at least one of the SRS resource set, PUCCH, PUSCH, or TCI state, or any combination thereof, of the uplink carrier. The communication manager 520 may be capable of, configured to, or operable to support components for calculating the virtual PHR based at least in part on the set of PUSCH reference parameters, the path loss offset, or both, based on this selection.

[0195] Additionally or alternatively, the communication manager 520 may support wireless communication according to examples disclosed herein. For example, the communication manager 520 may be capable of, configured to, or operable to support components for selecting an actual PHR or a virtual PHR to be transmitted in a first PUSCH transmission on an uplink carrier of the UE, the selection being based on prior acceptance of a second PUSCH transmission scheduled in association with the uplink transmission type, wherein the prior acceptance was received before or during a PDCCH monitoring event in which the UE detects acceptance of a first PUSCH transmission on the first uplink carrier. The communication manager 520 may be capable of, configured to, or operable to support components for transmitting an actual PHR or a virtual PHR in a first PUSCH transmission on an uplink carrier of the UE according to this selection.

[0196] By including or configuring a communication manager 520 according to examples as described herein, device 505 (e.g., controlling receiver 510, transmitter 515, communication manager 520 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for improving PHR triggering and reporting in dense uplink deployment scenarios, in some examples, where the dense uplink deployment scenario is based on the uplink transmission type of PUSCH transmission.

[0197] Figure 6 A block diagram 600 is shown of a device 605 supporting power headroom enhancement for dense uplink deployments according to one or more aspects of this disclosure. Device 605 may be an example of aspects of device 505 or UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0198] Receiver 610 may provide components 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 clearance enhancement for dense uplink deployments). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0199] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, 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 clearance enhancement for dense uplink deployments). In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0200] Device 605 or its various components may be examples of parts used to perform various aspects of power headroom enhancement for dense uplink deployments as described herein. For example, communication manager 620 may include PHR status manager 625, PHR selection manager 630, permission manager 635, or any combination thereof. Communication manager 620 may be examples of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use receiver 610, transmitter 615, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in combination with receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0201] Communication manager 620 can support wireless communication according to the examples disclosed herein. PHR status manager 625 is capable of, configured to, or operable to support components for receiving a message indicative of a triggered PHR status for the UE, the triggered PHR status indicating whether PHR transmission triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled. PHR status manager 625 is capable of, configured to, or operable to support components for selectively transmitting PHR based on the triggered PHR status and a path loss change on at least one uplink carrier.

[0202] Additionally or alternatively, the communication manager 620 may support wireless communication according to examples disclosed herein. The PHR selection manager 630 is capable of, configured to, or operable to support components for transmitting a PHR during a PUSCH transmission on a first uplink carrier of the UE during a time slot, wherein the PUSCH transmission set on a second uplink carrier overlaps in the time domain with the PUSCH transmission on the first uplink carrier in that time slot. The PHR selection manager 630 is capable of, configured to, or operable to support components for providing a PHR value for a second uplink carrier of the UE, the PHR value of the second uplink carrier including an actual PHR or a virtual PHR, wherein the selection of the actual PHR or virtual PHR for the second uplink carrier is based on the uplink transmission type of each PUSCH transmission in the PUSCH transmission set.

[0203] Additionally or alternatively, the communication manager 620 may support wireless communication according to examples disclosed herein. The PHR selection manager 630 is capable of, configured to, or operable to support components for selecting a virtual PHR for an uplink carrier, wherein power control parameters are configured for the uplink carrier, or a path loss reference signal non-configured condition exists for at least one of the SRS resource set, PUCCH, PUSCH, or TCI state, or any combination thereof, of the uplink carrier. The PHR selection manager 630 is capable of, configured to, or operable to support components for calculating a virtual PHR based on the selection and on a set of PUSCH reference parameters, a path loss offset, or both.

[0204] Additionally or alternatively, the communication manager 620 may support wireless communication according to examples disclosed herein. The grant manager 635 is capable of, configured to, or operable to support components for selecting an actual PHR or a virtual PHR to be transmitted in a first PUSCH transmission on the UE's uplink carrier, the selection being based on a previously received grant for scheduling a second PUSCH transmission associated with the uplink transmission type, wherein the previously received grant was received before or during a PDCCH monitoring event in which the UE detects a grant for scheduling a first PUSCH transmission on the first uplink carrier. The grant manager 635 is capable of, configured to, or operable to support components for transmitting an actual PHR or a virtual PHR in a first PUSCH transmission on the UE's uplink carrier according to this selection.

[0205] Figure 7A block diagram 700 is shown of a communication manager 720 supporting power clearance enhancement for dense uplink deployments according to one or more aspects of this disclosure. The communication manager 720 may be an example of a communication manager 520, a communication manager 620, or aspects thereof as described herein. The communication manager 720 or its various components may be examples of parts for performing various aspects of power clearance enhancement for dense uplink deployments as described herein. For example, the communication manager 720 may include a PHR status manager 725, a PHR selection manager 730, an authorization 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 its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0206] Communication manager 720 can support wireless communication according to examples disclosed herein. PHR status manager 725 is capable of, configured to, or operable to support components for receiving a message instructing the UE on a triggered PHR status, indicating whether PHR transmission triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled. In some examples, PHR status manager 725 is capable of, configured to, or operable to support components for selectively transmitting PHR based on the triggered PHR status and a path loss change on at least one uplink carrier. In some examples, the message includes an RRC message.

[0207] In some examples, the power control parameter manager 740 is capable of, configured to, or operable to support components for receiving indications of power control parameters configured for at least one of SRS transmission, PUCCH transmission, or PUSCH transmission, wherein a trigger-based PHR condition indicating whether PHR transmission is enabled is based on the power control parameter. In some examples, the power control parameter includes at least one of a path loss value or a path loss offset.

[0208] In some examples, the power control parameter manager 740 is capable of, configured to, or able to operate to support components for receiving indications of power control parameters configured for uplink TCI states, wherein the indication of whether PHR transmission is enabled is based on the trigger-based PHR status according to the power control parameters.

[0209] In some examples, to support message reception, the PL-RS manager 745 is capable of, configured to, or operable to support components for detecting whether the path loss reference signal is configured for at least one of: SRS transmission, PUCCH transmission, or PUSCH transmission, wherein a trigger-based PHR condition indicating whether PHR transmission is enabled is based on this detection. In some examples, to support message reception, the PL-RS manager 745 is capable of, configured to, or operable to support components for detecting whether the path loss reference signal is configured for uplink TCI status, wherein a trigger-based PHR condition indicating whether PHR transmission is enabled is based on this detection.

[0210] In some examples, to support selective transmission of PHR, the PHR status manager 725 is capable of, can be configured to, or is able to operate to support components for enabling PHR transmission based on the triggered PHR status indication and for transmitting PHR based on path loss changes on at least one uplink carrier satisfying a path loss threshold.

[0211] In some examples, to support selective transmission of PHR, the PHR status manager 725 can, is configured, or is operable to support components for detecting that a path loss change on at least one uplink carrier has met a path loss threshold. In some examples, to support selective transmission of PHR, the PHR status manager 725 can, is configured, or is operable to support components for avoiding PHR transmission by disabling PHR transmission based on a triggered PHR status indication.

[0212] Additionally or alternatively, the communication manager 720 may support wireless communication according to examples disclosed herein. The PHR selection manager 730 is capable of, configured to, or operable to support components for transmitting a PHR during a PUSCH transmission on a first uplink carrier of the UE during a time slot, wherein the PUSCH transmission set on a second uplink carrier overlaps in the time domain with the PUSCH transmission on the first uplink carrier in that time slot. In some examples, the PHR selection manager 730 is capable of, configured to, or operable to support components for providing a PHR value for a second uplink carrier of the UE, the PHR value of the second uplink carrier including an actual PHR or a virtual PHR, wherein the selection of the actual PHR or virtual PHR for the second uplink carrier is based on the uplink transmission type of each PUSCH transmission in the PUSCH transmission set.

[0213] In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support components for detecting that at least one PUSCH transmission in the PUSCH transmission set 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 components for selecting an actual PHR for a second uplink carrier, wherein the actual PHR is based on at least one PUSCH transmission being the first PUSCH transmission in the PUSCH transmission set associated with a specific uplink transmission type.

[0214] In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support components for detecting each PUSCH transmission in the PUSCH transmission set 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 components for selecting an actual PHR for a second uplink carrier based on detection, wherein the actual PHR is based on a first PUSCH transmission in the PUSCH transmission set.

[0215] In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support components for detecting the association of each PUSCH transmission in the PUSCH transmission set 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 components for selecting a virtual PHR for a second uplink carrier based on detection.

[0216] In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support components for detecting the association of a first PUSCH transmission in the PUSCH transmission set with a specific uplink transmission type. In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support components for selecting an actual PHR for a second uplink carrier, wherein the actual PHR is based on the first PUSCH transmission in the PUSCH transmission set.

[0217] In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support components for detecting the association of a first PUSCH transmission in a PUSCH transmission set 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 components for selecting a virtual PHR for a second uplink carrier based on detection.

[0218] In some examples, the uplink transmission type manager 750 is capable of, configured to, or able to operate to support components that associate at least one PUSCH transmission in a PUSCH transmission set with a path loss reference signal and detect whether the at least one PUSCH transmission is associated with a specific uplink transmission type based on the unconfigured condition of the path loss or path loss offset associated with the at least one PUSCH transmission.

[0219] In some examples, the TCI manager 755 is capable of, configured to, or operable to support components for detecting at least one PUSCH transmission based on the uplink TCI state associated with at least one PUSCH transmission in the PUSCH transmission set, wherein the uplink TCI state is associated with a downlink path loss reference signal, a source downlink reference signal, a timing advance group identifier, or any combination thereof.

[0220] In some examples, the permission manager 735 is capable of, configured to, or able to operate to support components for detecting at least one PUSCH transmission based on a permission granted for at least one PUSCH transmission in a set of scheduled PUSCH transmissions.

[0221] In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support components for detecting at least one PUSCH transmission based on path loss, path loss offset, or both associated with at least one PUSCH transmission in the PUSCH transmission set. In some examples, the uplink transmission type manager 750 is capable of, configured to, or operable to support components for detecting at least one PUSCH transmission based on an uplink TCI state associated with at least one PUSCH transmission in the PUSCH transmission set, wherein the uplink TCI state is associated with path loss, path loss offset, SRS resource, timing advance group identifier, or any combination thereof.

[0222] In some examples, the uplink transmission type manager 750 is capable of, configured to, or able to operate to support components for receiving RRC messages indicating a specific uplink transmission type.

[0223] Additionally or alternatively, the communication manager 720 may support wireless communication according to examples disclosed herein. In some examples, the PHR selection manager 730 is capable of, configured to, or operable to support components for selecting a virtual PHR for an uplink carrier, wherein power control parameters are configured for the uplink carrier, or a path loss reference signal non-configured condition exists for at least one of the SRS resource set, PUCCH, PUSCH, or TCI state, or any combination thereof, of the uplink carrier. In some examples, the PHR selection manager 730 is capable of, configured to, or operable to support components for calculating a virtual PHR based on the selection and on a set of PUSCH reference parameters, a path loss offset, or both.

[0224] In some examples, the TCI manager 755 is capable of, can be configured to, or is operable to support components for identifying path loss offsets based on at least one of the following: a default path loss reference signal identifier, a default P0 nominal power level, a default uplink TCI state, a default path loss value, an indicated TCI state, or any combination thereof.

[0225] In some examples, the TCI manager 755 is capable of, configured to, or able to operate to support components for determining the path loss offset for the virtual PHR based on the indicated TCI state of the UE, wherein the indicated TCI state is associated with the path loss offset. In some examples, the TCI manager 755 is capable of, configured to, or able to operate to support components for determining the PUSCH reference parameter set for the virtual PHR based on the indicated TCI state of the UE, wherein the path loss offset is in a non-configured state with respect to the indicated TCI state.

[0226] In some examples, the PHR selection manager 730 is capable of, configured to, or able to operate to support components for receiving RRC messages indicating whether to use path loss offsets for the virtual PHR.

[0227] Additionally or alternatively, the communication manager 720 may support wireless communication according to examples disclosed herein. The grant manager 735 is capable of, configured to, or operable to support components for selecting an actual PHR or a virtual PHR to be transmitted in a first PUSCH transmission on the UE's uplink carrier, the selection being based on a previously received grant for scheduling a second PUSCH transmission associated with the uplink transmission type, wherein the previously received grant was received before or during a PDCCH monitoring event in which the UE detects a grant for scheduling a first PUSCH transmission on the first uplink carrier. In some examples, the grant manager 735 is capable of, configured to, or operable to support components for transmitting an actual PHR or a virtual PHR in a first PUSCH transmission on the UE's uplink carrier according to this selection.

[0228] In some examples, the grant manager 735 is capable of, configured to, or able to operate to support components for selecting the actual PHR to be transmitted in the first PUSCH transmission based on the association of the second PUSCH transmission with a specific uplink transmission type, wherein the uplink transmission type includes the specific uplink transmission type.

[0229] In some examples, the grant manager 735 is capable of, configured to, or able to operate to support components for selecting the virtual PHR to be sent in the first PUSCH transmission based on the association of the second PUSCH transmission with a non-specific uplink transmission type, wherein the uplink transmission type includes a non-specific uplink transmission type.

[0230] Figure 8 A diagram is shown of a system 800 including device 805 supporting power headroom enhancement for dense uplink deployments, according to one or more aspects of this disclosure. Device 805 may be an example of device 505, device 605, or UE 115 as described herein, or may include components thereof. Device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication 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 communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 845).

[0231] I / O controller 810 manages the input and output signals of device 805. I / O controller 810 can also manage peripheral devices not integrated into device 805. In some cases, I / O controller 810 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 810 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 810 may be implemented as part of one or more processors, such as 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.

[0232] In some cases, device 805 may include a single antenna 825. However, in other cases, device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 815 may communicate bidirectionally via one or more antennas 825, a wired link, or a wireless link as described herein. For example, transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 825 for transmission; and demodulating packets received from one or more antennas 825. Transceiver 815, or transceiver 815 and one or more antennas 825, may be an example of transmitter 515, transmitter 615, receiver 510, receiver 610, or any combination thereof or components thereof as described herein.

[0233] At least one memory 830 may include random access memory (RAM) and read-only memory (ROM). At least one memory 830 may store computer-readable, computer-executable code 835, including instructions that, when executed by at least one processor 840, cause device 805 to perform the various functions described herein. Code 835 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 835 may not be directly executable by at least one processor 840, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 830 may contain a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0234] At least one processor 840 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 840. At least one processor 840 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 830) to cause device 805 to perform various functions (e.g., functions or tasks supporting power headroom enhancement for dense uplink deployments). For example, device 805 or components of device 805 may include at least one processor 840 and at least one memory 830 coupled to or coupled to at least one processor 840, wherein at least one processor 840 and at least one memory 830 are configured to perform the various functions described herein. In some examples, at least one processor 840 may include multiple processors, and at least one memory 830 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 840 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 840) and memory circuitry (which may include at least one memory 830)) or components that receive or receive input and process the input 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, at least one processor 840 or a processing system including at least one processor 840 may be configured, capable of being configured to, or operable to cause device 805 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 830 or otherwise.

[0235] The communication manager 820 can support wireless communication according to the examples disclosed herein. For example, the communication manager 820 is capable of, configured to, or operable to support components for receiving a message indicative of a triggered PHR state for the UE, the triggered PHR state indicating whether PHR transmission triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled. The communication manager 820 is capable of, configured to, or operable to support components for selectively transmitting PHR based on the triggered PHR state and a path loss change on at least one uplink carrier.

[0236] Additionally or alternatively, the communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for transmitting a PHR in a PUSCH transmission on a first uplink carrier of the UE during a time slot, wherein the PUSCH transmission set in the second uplink carrier overlaps in the time domain with the PUSCH transmission on the first uplink carrier in that time slot. The communication manager 820 may be capable of, configured to, or operable to support components for providing a PHR value for a second uplink carrier of the UE, the PHR value of the second uplink carrier including an actual PHR or a virtual PHR, wherein the selection of the actual PHR or virtual PHR for the second uplink carrier is based on the uplink transmission type of each PUSCH transmission in the PUSCH transmission set.

[0237] Additionally or alternatively, the communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operated to support components for selecting a virtual PHR for an uplink carrier, wherein power control parameters are configured for the uplink carrier, or where there is a path loss reference signal non-configuration condition for at least one of the SRS resource set, PUCCH, PUSCH, or TCI state, or any combination thereof, of the uplink carrier. The communication manager 820 may be capable of, configured to, or operated to support components for calculating the virtual PHR based at least in part on the PUSCH reference parameter set, path loss offset, or both, based on this selection.

[0238] Additionally or alternatively, the communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for selecting an actual PHR or a virtual PHR to be transmitted in a first PUSCH transmission on an uplink carrier of the UE, the selection being based on prior acceptance of a second PUSCH transmission scheduled in association with the uplink transmission type, wherein the prior acceptance was received before or during a PDCCH monitoring event in which the UE detects acceptance of a first PUSCH transmission on the first uplink carrier. The communication manager 820 may be capable of, configured to, or operable to support components for transmitting an actual PHR or a virtual PHR in a first PUSCH transmission on an uplink carrier of the UE according to this selection.

[0239] By including or configuring a communication manager 820 according to examples as described herein, device 805 can support techniques for improving PHR triggering and reporting in dense uplink deployment scenarios, in some examples, based on the uplink transmission type of PUSCH transmission.

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

[0241] Figure 9 A block diagram 900 illustrates a device 905 supporting power headroom enhancement for dense uplink deployments according to one or more aspects of this disclosure. Device 905 may be an example of aspects of network entity 105 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905, or one or more components of device 905 (e.g., receiver 910, transmitter 915, and communication manager 920), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0242] Receiver 910 may provide components for acquiring (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). The information may be passed to other components of device 905. In some examples, receiver 910 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 910 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0243] Transmitter 915 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 905. For example, transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, 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, transmitter 915 and receiver 910 may be co-located in a transceiver, which may include or be coupled to a modem.

[0244] The communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of power headroom enhancement for dense uplink deployments as described herein. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0245] In some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

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

[0247] In some examples, the communication manager 920 may be configured to use a receiver 910, a transmitter 915, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or integrate with the receiver 910, the transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0248] The communication manager 920 can support wireless communication according to the examples disclosed herein. For example, the communication manager 920 is capable of, configured to, or operable to support components for sending a message to the UE indicative of a triggered PHR state of the UE, the triggered PHR state indicating whether transmission of a PHR triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled. The communication manager 920 is capable of, configured to, or operable to support components for selectively receiving a PHR based on the triggered PHR state and a path loss change on at least one uplink carrier.

[0249] By including or configuring a communication manager 920 according to examples as described herein, device 905 (e.g., controlling receiver 910, transmitter 915, communication manager 920, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for improving PHR triggering and reporting in dense uplink deployment scenarios, in some examples, where the dense uplink deployment scenario is based on the uplink transmission type of PUSCH transmission.

[0250] Figure 10 A block diagram 1000 of a device 1005 supporting power headroom enhancement for dense uplink deployments according to one or more aspects of this disclosure is shown. Device 1005 may be an example of aspects of device 905 or network entity 105 as described herein. Device 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Device 1005 or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, and communication manager 1020) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0251] Receiver 1010 may provide components for acquiring (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). The information may be passed to other components of device 1005. In some examples, receiver 1010 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0252] Transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, 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, transmitter 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.

[0253] Device 1005 or its various components may be examples of parts used to perform various aspects of power headroom enhancement for dense uplink deployments as described herein. For example, communication manager 1020 may include trigger manager 1025, PHR manager 1030, or any combination thereof. Communication manager 1020 may be examples of aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use receiver 1010, transmitter 1015, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in combination with receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0254] Communication manager 1020 can support wireless communication according to the examples disclosed herein. Trigger manager 1025 is capable of, configured to, or operable to support components for sending a message to the UE indicative of a trigger-based PHR state of the UE, the trigger-based PHR state indicating whether PHR transmission triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled. PHR manager 1030 is capable of, configured to, or operable to support components for selectively receiving PHR based on the trigger-based PHR state and a path loss change on at least one uplink carrier.

[0255] Figure 11A block diagram 1100 is shown of a communication manager 1120 supporting power headroom enhancement for dense uplink deployments according to one or more aspects of this disclosure. The communication manager 1120 may be an example of a communication manager 920, a communication manager 1020, or aspects thereof as described herein. The communication manager 1120 or its various components may be examples of parts for performing various aspects of power headroom enhancement for dense uplink deployments as described herein. For example, the communication manager 1120 may include a trigger manager 1125, a PHR manager 1130, a power control parameter manager 1135, a PL-RS manager 1140, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and such communication may include communication within protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0256] Communication manager 1120 can support wireless communication according to examples disclosed herein. Trigger manager 1125 is capable of, configured to, or operable to support components for sending a message to the UE indicative of a trigger-based PHR status of the UE, the trigger-based PHR status indicating whether PHR transmission triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled. PHR manager 1130 is capable of, configured to, or operable to support components for selectively receiving PHR based on the trigger-based PHR status and a path loss change on at least one uplink carrier. In some examples, the message includes an RRC message.

[0257] In some examples, the power control parameter manager 1135 is capable of, configured to, or operable to support components for transmitting indications of power control parameters configured for at least one of SRS transmission, PUCCH transmission, or PUSCH transmission, wherein a trigger-based PHR condition indicating whether PHR transmission is enabled is based on the power control parameter. In some examples, the power control parameter includes at least one of a path loss value or a path loss offset.

[0258] In some examples, the power control parameter manager 1135 is capable of, configured to, or able to operate to support components for sending indications of power control parameters configured for uplink TCI states, wherein the indication of whether PHR transmission is enabled is based on the trigger-based PHR state according to the power control parameters.

[0259] In some examples, to support message reception, the PL-RS manager 1140 is capable of, configured to, or operable to support components for detecting whether the path loss reference signal is configured for at least one of: SRS transmission, PUCCH transmission, or PUSCH transmission, wherein a trigger-based PHR condition indicating whether PHR transmission is enabled is based on this detection. In some examples, to support message transmission, the PL-RS manager 1140 is capable of, configured to, or operable to support components for detecting whether the path loss reference signal is configured for uplink TCI status, wherein a trigger-based PHR condition indicating whether PHR transmission is enabled is based on this detection.

[0260] In some examples, to support selective PHR reception, the trigger manager 1125 is capable of, configured to, or operable to support components for enabling PHR transmission based on the trigger-based PHR status indication and for receiving PHR based on path loss changes on at least one uplink carrier satisfying a path loss threshold. In some examples, to support selective PHR reception, the trigger manager 1125 is capable of, configured to, or operable to support components for disabling PHR transmission based on the trigger-based PHR status indication to avoid receiving PHR.

[0261] Figure 12 A diagram of a system 1200 including device 1205 supporting power clearance enhancement for dense uplink deployments, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of device 905, device 1005, or network entity 105 as described herein, or may include components thereof. Device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1205 may include components supporting output and acquisition of communication, such as a communication manager 1220, a transceiver 1210, an antenna 1215, at least one memory 1225, code 1230, and at least one processor 1235. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1240).

[0262] Transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1210 may include a wired transceiver and be able to communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1210 may include a wireless transceiver and be able to communicate bidirectionally with another wireless transceiver. In some examples, device 1205 may include one or more antennas 1215 that may be able to transmit or receive wireless transmissions (e.g., concurrently). Transceiver 1210 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1215, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1215, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1215 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1210 may include one or more processors or one or more memory components, or be configured to couple to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1210, or transceiver 1210 and one or more antennas 1215, or transceiver 1210 and one or more antennas 1215 and one or more processors or one or more memory components (e.g., at least one processor 1235, at least one memory 1225, or both), may be included in a chip or chip assembly mounted in device 1205. In some examples, transceiver 1210 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0263] At least one memory 1225 may include RAM, ROM, or any combination thereof. At least one memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by one or more processors of at least one processor 1235, cause device 1205 to perform the various functions described herein. Code 1230 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1230 may not be directly executable by a processor of at least one processor 1235, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1225 may contain a BIOS, etc., that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1235 may include multiple processors, and at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0264] At least one processor 1235 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1235. At least one processor 1235 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1225) to cause device 1205 to perform various functions (e.g., functions or tasks supporting power headroom enhancement for dense uplink deployments). For example, device 1205 or components of device 1205 may include at least one processor 1235 and at least one memory 1225 coupled to one or more processors in at least one processor 1235, wherein at least one processor 1235 and at least one memory 1225 are configured to perform the various functions described herein. 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 an operating system, virtual machine, or container instance) that can host functions (e.g., by executing code 1230) to perform the functions of device 1205. 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 device 1205 (such as within one or more memories of at least one memory 1225). In some examples, at least one processor 1235 may include multiple processors, and at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1235 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1235) and memory circuitry (which may include at least one memory 1225)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1235 or a processing system including at least one processor 1235 may be configured, configured to, or operable to cause the device 1205 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1225 or otherwise.

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

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

[0267] Communication manager 1220 may support wireless communications according to examples disclosed herein. For example, communication manager 1220 may be capable of, configured to, or operable to support components for sending a message to a UE indicative of a triggered PHR state of the UE, the triggered PHR state indicating whether transmission of a PHR triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled. Communication manager 1220 may be capable of, configured to, or operable to support components for selectively receiving a PHR based on the triggered PHR state and a path loss change on at least one uplink carrier.

[0268] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 can support techniques for improving PHR triggering and reporting in dense uplink deployment scenarios, in some examples, based on the uplink transmission type of PUSCH transmission.

[0269] In some examples, the communication manager 1220 may be configured to use or otherwise cooperate with transceiver 1210, one or more antennas 1215 (e.g., where applicable) or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by transceiver 1210, one or more processors in at least one processor 1235, one or more memories in at least one memory 1225, code 1230, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1235, at least one memory 1225, code 1230, or any combination thereof). For example, code 1230 may include instructions that can be executed by one or more of at least one processor 1235 to cause device 1205 to perform various aspects of power headroom enhancement for dense uplink deployments as described herein, or at least one processor 1235 and at least one memory 1225 may be otherwise configured to perform or support such operations individually or jointly.

[0270] Figure 13 A flowchart illustrating a method 1300 for power clearance enhancement for dense uplink deployments, according to various aspects of this disclosure, is shown. Operation of method 1300 can be implemented by a UE or its components as described herein. For example, operation of method 1300 can be achieved by, as referenced... Figures 1 to 8 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0271] At 1305, the method may include: receiving a message indicating a triggered PHR state of the UE, the triggered PHR state indicating whether transmission of a PHR triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled. The operation of block 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1305 may be provided by reference to [reference]. Figure 7 The described PHR status manager 725 is used to perform this.

[0272] At 1310, the method may include selectively transmitting a PHR based on a triggered PHR condition and a change in path loss on at least one uplink carrier. The operation of block 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1310 may be provided by reference to [reference needed]. Figure 7The described PHR status manager 725 is used to perform this.

[0273] Figure 14 A flowchart illustrating a method 1400 for power clearance enhancement for dense uplink deployments, according to various aspects of this disclosure, is shown. Operation of method 1400 can be implemented by a UE or its components as described herein. For example, operation of method 1400 can be achieved by, as referenced... Figures 1 to 8 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0274] At 1405, the method may include: transmitting a PHR during a PUSCH transmission on a first uplink carrier of the UE during a time slot, wherein the set of PUSCH transmissions on a second uplink carrier overlaps in the time domain with the PUSCH transmissions on the first uplink carrier in that time slot. The operation of block 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1405 may be derived from references... Figure 7 The described PHR selection manager 730 is used to perform this.

[0275] At 1410, the method may include: providing a PHR value for a second uplink carrier of the UE, the PHR value of the second uplink carrier including an actual PHR or a virtual PHR, wherein the selection of the actual PHR or virtual PHR for the second uplink carrier is based on the uplink transmission type of each PUSCH transmission in the PUSCH transmission set. The operation of block 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be provided by reference to [reference]. Figure 7 The described PHR selection manager 730 is used to perform this.

[0276] Figure 15 A flowchart illustrating a method 1500 for power clearance enhancement for dense uplink deployments, according to various aspects of this disclosure, is shown. Operation of method 1500 can be implemented by a UE or its components as described herein. For example, operation of method 1500 can be achieved by, as referenced... Figures 1 to 8 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0277] At 1505, the method may include: selecting a virtual PHR for an uplink carrier, wherein power control parameters are configured for the uplink carrier, or a path loss reference signal is unconfigured for at least one of the SRS resource set, PUCCH, PUSCH, or Transmit Configuration Indicator (TCI) state, or any combination thereof, of the uplink carrier. The operation of block 1505 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to [reference missing]. Figure 7 The described PHR selection manager 730 is used to perform this.

[0278] At 1510, the method may include: calculating the virtual PHR based on the selection and on a set of PUSCH reference parameters, a path loss offset, or both. The operation of box 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be determined by reference to... Figure 7 The described PHR selection manager 730 is used to perform this.

[0279] Figure 16 A flowchart illustrating a method 1600 for power clearance enhancement for dense uplink deployments, according to various aspects of this disclosure, is shown. Operation of method 1600 can be implemented by a UE or its components as described herein. For example, operation of method 1600 can be achieved by, as referenced... Figures 1 to 8 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0280] 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 selection being based on prior reception permission for a second PUSCH transmission scheduled in association with the uplink transmission type, wherein prior reception permission was received before or during a PDCCH monitoring event in which the UE detects permission for a first PUSCH transmission scheduled on the first uplink carrier. Operation of block 1605 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1605 may be provided by reference to [reference needed]. Figure 7 The described permission manager 735 is used to execute this.

[0281] At 1610, the method may include: transmitting an actual PHR or a virtual PHR in a first PUSCH transmission on the uplink carrier of the UE, depending on the selection. Operation of block 1610 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1610 may be provided by reference to [reference]. Figure 7 The described permission manager 735 is used to execute this.

[0282] Figure 17 A flowchart illustrating a method 1700 for power headroom enhancement for dense uplink deployments, according to various aspects of this disclosure, is shown. Operation of method 1700 may be implemented by a network entity or its components as described herein. For example, operation of method 1700 may be implemented by, as referenced... Figure 1 up to Figure 4 and Figures 9 to 12 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0283] At 1705, the method may include: sending a message to the UE indicative of a triggered PHR state of the UE, the triggered PHR state indicating whether transmission of a PHR triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled. Operation of block 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1705 may be provided by reference to [reference needed]. Figure 11 The described trigger manager 1125 is used to execute.

[0284] At 1710, the method may include selectively receiving a PHR based on a triggered PHR condition and a change in path loss on at least one uplink carrier. Operation of block 1710 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1710 may be derived from references... Figure 11 The described PHR manager 1130 is used to execute this.

[0285] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a message indicating a triggered PHR state of the UE, the triggered PHR state indicating whether transmission of a PHR triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled; and selectively transmitting the PHR based on the triggered PHR state and the path loss change on the at least one uplink carrier.

[0286] Aspect 2: The method according to aspect 1, wherein the message includes an RRC message.

[0287] Aspect 3: The method according to any one of Aspects 1 to 2, the method further comprising: receiving an indication of a power control parameter configured for at least one of SRS transmission, PUCCH transmission, or PUSCH transmission, wherein the trigger-based PHR condition indicating whether to enable transmission of the PHR is at least partially based on the power control parameter.

[0288] Aspect 4: According to the method of aspect 3, the power control parameter includes at least one of path loss value or path loss offset.

[0289] Aspect 5: The method according to any one of Aspects 1 to 4, the method further comprising: receiving an indication of power control parameters configured for uplink TCI state, wherein the trigger-based PHR state indicating whether to enable transmission of the PHR is at least partially based on the power control parameters.

[0290] Aspect 6: The method according to any one of Aspects 1 to 5, wherein receiving the message comprises: detecting whether a path loss reference signal is configured for at least one of: SRS transmission, PUCCH transmission, or PUSCH transmission, wherein the trigger-based PHR condition indicating whether the transmission of the PHR is enabled is at least partially based on the detection.

[0291] Aspect 7: The method according to any one of Aspects 1 to 6, wherein receiving the message includes: detecting whether a path loss reference signal is configured for uplink TCI status, wherein the trigger-based PHR status indicating whether the transmission of the PHR is enabled is at least partially based on the detection.

[0292] Aspect 8: The method according to any one of Aspects 1 to 7, wherein selectively transmitting the PHR comprises: enabling the transmission of the PHR at least in part based on the triggered PHR status indication and transmitting the PHR based on the path loss change on the at least one uplink carrier satisfying the path loss threshold.

[0293] Aspect 9: The method according to any one of Aspects 1 to 8, wherein selectively transmitting the PHR comprises: detecting that the path loss change on the at least one uplink carrier has satisfied the path loss threshold; and avoiding transmission of the PHR by disabling transmission of the PHR at least in part based on the trigger-based PHR condition indication.

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

[0295] Aspect 11: The method according to aspect 10, the method further comprising: detecting that at least one PUSCH transmission in the PUSCH transmission set 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 PUSCH transmission set associated with the specific uplink transmission type.

[0296] Aspect 12: The method according to any one of Aspects 10 to 11, the method further comprising: detecting that each PUSCH transmission in the PUSCH transmission set is associated with a non-specific transmission type; and selecting the actual PHR for the second uplink carrier based at least in part on the detection, wherein the actual PHR is based at least in part on a first PUSCH transmission in the PUSCH transmission set.

[0297] Aspect 13: The method according to any one of Aspects 10 to 12, the method further comprising: detecting that each PUSCH transmission in the PUSCH transmission set 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 detection.

[0298] Aspect 14: The method according to any one of Aspects 10 to 13, the method further comprising: detecting that a first PUSCH transmission in the PUSCH transmission set is associated with a specific uplink transmission type; and selecting the actual PHR for the second uplink carrier, wherein the actual PHR is at least partially based on the first PUSCH transmission in the PUSCH transmission set.

[0299] Aspect 15: The method according to any one of Aspects 10 to 14, the method further comprising: detecting that a first PUSCH transmission in the PUSCH transmission set 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 detection.

[0300] Aspect 16: The method according to any one of Aspects 10 to 15, the method further comprising: detecting whether the at least one PUSCH transmission is associated with a specific uplink transmission type based at least in part on the association of a path loss reference signal with at least one PUSCH transmission in the PUSCH transmission set and on the unconfigured condition of path loss or path loss offset associated with the at least one PUSCH transmission.

[0301] Aspect 17: The method according to any one of Aspects 10 to 16, the method further comprising: detecting whether the at least one PUSCH transmission is associated with a specific uplink transmission type based at least in part on an uplink TCI state associated with at least one PUSCH transmission in the PUSCH transmission set, wherein the uplink TCI state is associated with a downlink path loss reference signal, a source downlink reference signal, a timing advance group identifier, or any combination thereof.

[0302] Aspect 18: The method according to any one of Aspects 10 to 17, the method further comprising: detecting whether the at least one PUSCH transmission is associated with a specific uplink transmission type based at least in part on permission to schedule at least one PUSCH transmission in the PUSCH transmission set.

[0303] Aspect 19: The method according to any one of Aspects 10 to 18, the method further comprising: detecting whether the at least one PUSCH transmission is associated with a specific uplink transmission type based at least in part on path loss, path loss offset, or both associated with at least one PUSCH transmission in the PUSCH transmission set.

[0304] Aspect 20: The method according to any one of Aspects 10 to 19, the method further comprising: detecting whether the at least one PUSCH transmission is associated with a specific uplink transmission type based at least in part on an uplink TCI state associated with at least one PUSCH transmission in the PUSCH transmission set, wherein the uplink TCI state is associated with path loss, path loss offset, SRS resource, timing advance group identifier or any combination thereof.

[0305] Aspect 21: The method according to any one of aspects 10 to 20, the method further comprising: receiving an RRC message indicating a specific uplink transmission type.

[0306] Aspect 22: A method for wireless communication at a UE, the method comprising: selecting a virtual PHR for an uplink carrier, wherein power control parameters are configured for the uplink carrier, or a path loss reference signal non-configuration condition exists for at least one of an SRS resource set, PUCCH, PUSCH, or TCI state, or any combination thereof, of the uplink carrier; and calculating the virtual PHR based at least in part on the selection and at least in part on a set of PUSCH reference parameters, a path loss offset, or both.

[0307] Aspect 23: The method according to aspect 22 further includes identifying the path loss offset based on at least one of a default path loss reference signal identifier, a default P0 nominal power level, a default uplink TCI state, a default path loss value, an indicated TCI state, or any combination thereof.

[0308] Aspect 24: The method according to any one of Aspects 22 to 23, the method further comprising: determining, at least in part, to use the path loss offset for the virtual PHR based on an indicated TCI state of the UE, wherein the indicated TCI state is associated with the path loss offset.

[0309] Aspect 25: The method according to any one of Aspects 22 to 24, the method further comprising: determining, at least in part, to use the PUSCH reference parameter set for the virtual PHR based on the indicated TCI state of the UE, wherein the path loss offset is in a non-configured state with respect to the indicated TCI state.

[0310] Aspect 26: The method according to any one of Aspects 22 to 25, the method further comprising: receiving an RRC message indicating whether the path loss offset is used for the virtual PHR.

[0311] Aspect 27: A method for wireless communication at a UE, the method comprising: selecting an actual PHR or a virtual PHR to be transmitted in a first PUSCH transmission on an uplink carrier of the UE, the selection being based at least in part on prior reception permission for scheduling a second PUSCH transmission associated with an uplink transmission type, wherein prior reception permission was received before or during a PDCCH monitoring timing when the UE detects permission for scheduling 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 according to the selection.

[0312] Aspect 28: The method according to aspect 27 further includes: selecting the actual PHR to be transmitted in the first PUSCH transmission based at least in part on the association of the second PUSCH transmission with a specific uplink transmission type, wherein the uplink transmission type includes the specific uplink transmission type.

[0313] Aspect 29: The method according to any one of Aspects 27 to 28, the method further comprising: selecting the virtual PHR for transmission in the first PUSCH transmission based at least in part on the association of the second PUSCH transmission with a nonspecific uplink transmission type, wherein the uplink transmission type includes the nonspecific uplink transmission type.

[0314] Aspect 30: A method for wireless communication at a network entity, the method comprising: sending to a UE a message indicating a triggered PHR state of the UE, the triggered PHR state indicating whether transmission of a PHR triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled; and selectively receiving the PHR based on the triggered PHR state and the path loss change on the at least one uplink carrier.

[0315] Aspect 31: The method according to aspect 30, wherein the message includes an RRC message.

[0316] Aspect 32: The method according to any one of Aspects 30 to 31, the method further comprising: sending an indication of power control parameters configured for at least one of SRS transmission, PUCCH transmission, or PUSCH transmission, wherein the trigger-based PHR condition indicating whether to enable transmission of the PHR is at least partially based on the power control parameters.

[0317] Aspect 33: According to the method of aspect 32, the power control parameter includes at least one of path loss value or path loss offset.

[0318] Aspect 34: The method according to any one of aspects 30 to 33, the method further comprising: sending an indication of power control parameters configured for uplink TCI state, wherein the trigger-based PHR state indicating whether to enable the transmission of the PHR is at least partially based on the power control parameters.

[0319] Aspect 35: The method according to any one of Aspects 30 to 34, wherein receiving the message comprises: detecting whether a path loss reference signal is configured for at least one of: SRS transmission, PUCCH transmission, or PUSCH transmission, wherein the trigger-based PHR condition indicating whether transmission of the PHR is enabled is at least partially based on the detection.

[0320] Aspect 36: The method according to any one of Aspects 30 to 35, wherein sending the message includes: detecting whether a path loss reference signal is configured for uplink TCI status, wherein the trigger-based PHR status indicating whether the transmission of the PHR is enabled is at least partially based on the detection.

[0321] Aspect 37: The method according to any one of Aspects 30 to 36, wherein selectively receiving the PHR comprises: enabling the transmission of the PHR at least in part based on the triggered PHR status indication and receiving the PHR based on the path loss change on the at least one uplink carrier satisfying the path loss threshold.

[0322] Aspect 38: The method according to any one of Aspects 30 to 37, wherein selectively receiving the PHR comprises: at least in part disabling the transmission of the PHR based on the triggered PHR status indication to avoid receiving the PHR.

[0323] Aspect 39: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of aspects 1 to 9.

[0324] Aspect 40: A UE for wireless communication, the UE comprising at least one component for performing the method according to any one of aspects 1 to 9.

[0325] Aspect 41: A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by one or more processors to perform the method according to any one of aspects 1 to 9.

[0326] Aspect 42: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of aspects 10 to 21.

[0327] Aspect 43: A UE for wireless communication, the UE comprising at least one component for performing a method according to any one of aspects 10 to 21.

[0328] Aspect 44: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 10 to 21.

[0329] Aspect 45: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of aspects 22 to 26.

[0330] Aspect 46: A UE for wireless communication, the UE including at least one component for performing a method according to any one of aspects 22 to 26.

[0331] Aspect 47: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 22 to 26.

[0332] Aspect 48: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of Aspects 27 to 29.

[0333] Aspect 49: A UE for wireless communication, the UE including at least one component for performing a method according to any one of aspects 27 to 29.

[0334] Aspect 50: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform a method according to any one of aspects 27 to 29.

[0335] Aspect 51: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of aspects 30 to 38.

[0336] Aspect 52: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 30 to 38.

[0337] Aspect 53: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 30 to 38.

[0338] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0339] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0340] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0341] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a 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 combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0342] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including portions distributed such that the functions are implemented in different physical locations.

[0343] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible 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, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0344] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, 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). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0345] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing 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 “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0346] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, acquiring, selecting, choosing, creating, and other similar actions.

[0347] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate between similar components. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second reference numeral or other subsequent reference numerals.

[0348] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

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

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Receive a message indicating the triggered power clearance report status of the UE, the triggered power clearance report status indicating whether to enable the transmission of a power clearance report triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold. as well as The power clearance report is selectively sent based on the triggered power clearance report status and the path loss change on the at least one uplink carrier.

2. The UE according to claim 1, wherein the message includes a Radio Resource Control (RRC) message.

3. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receive an indication of power control parameters configured for at least one of Sound Reference Signal (SRS) transmission, Physical Uplink Control Channel (PUCCH) transmission, or Physical Uplink Shared Channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status indicating whether to enable the transmission of the power clearance report is at least partially based on the power control parameters.

4. The UE according to claim 3, wherein the power control parameter includes at least one of path loss value or path loss offset.

5. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receive an indication of power control parameters configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance report status indicating whether to enable the transmission of the power clearance report is at least partially based on the power control parameters.

6. The UE according to claim 1, wherein, In order to receive the message, the one or more processors can operate individually or jointly to execute the code to enable the UE to: The detection path loss reference signal is configured for at least one of the following: probe reference signal (SRS) transmission, physical uplink control channel (PUCCH) transmission, or physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status, which indicates whether the transmission of the power clearance report is enabled, is at least partially based on the detection.

7. The UE according to claim 1, wherein, In order to receive the message, the one or more processors can operate individually or jointly to execute the code to enable the UE to: The detection determines whether a path loss reference signal is configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance reporting status, which indicates whether the transmission of the power clearance report is enabled, is at least partially based on the detection.

8. The UE according to claim 1, wherein, In order to selectively send the power clearance report, the one or more processors can operate individually or jointly to execute the code to enable the UE to: The transmission of the power clearance report is enabled at least in part based on the triggered power clearance report status indication and based on the path loss change on the at least one uplink carrier satisfying the path loss threshold.

9. The UE according to claim 1, wherein, In order to selectively send the power clearance report, the one or more processors can operate individually or jointly to execute the code to enable the UE to: The path loss change on the at least one uplink carrier is detected to have met the path loss threshold. as well as The power clearance report is avoided from being sent, at least in part, based on the trigger-based power clearance report status indication that the sending of the power clearance report is disabled.

10. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: During the time slot, a power clearance report is transmitted in the Physical Uplink Shared Channel (PUSCH) transmission on the first uplink carrier of the UE, wherein the PUSCH transmission set in the second uplink carrier overlaps with the PUSCH transmission on the first uplink carrier in the time domain during the time slot; as well as A power clearance report value is provided for the second uplink carrier of the UE, the power clearance report value of the second uplink carrier including an actual power clearance report or a virtual power clearance report, wherein the selection of the actual power clearance report or the virtual power clearance report for the second uplink carrier is based at least in part on the uplink transmission type of each PUSCH transmission in the PUSCH transmission set.

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

12. The UE of claim 10, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Detecting that each PUSCH transmission in the PUSCH transmission set is associated with a non-specific transmission type; and The actual power clearance report is selected for the second uplink carrier based at least in part on the detection, wherein the actual power clearance report is based at least in part on the first PUSCH transmission in the PUSCH transmission set.

13. The UE of claim 10, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Detecting that each PUSCH transmission in the PUSCH transmission set is associated with a non-specific uplink transmission type; and The virtual power clearance report is selected for the second uplink carrier based at least in part on the detection.

14. The UE of claim 10, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The first PUSCH transmission in the PUSCH transmission set is associated with a specific uplink transmission type; and The actual power clearance report is selected for the second uplink carrier, wherein the actual power clearance report is at least partially based on the first PUSCH transmission in the PUSCH transmission set.

15. The UE of claim 10, wherein the one or more processors are individually or jointly further operable to execute the code to cause the UE to: The first PUSCH transmission in the PUSCH transmission set is associated with a non-specific uplink transmission type; and The virtual power clearance report is selected for the second uplink carrier based at least in part on the detection.

16. The UE of claim 10, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Whether the at least one PUSCH transmission is associated with a specific uplink transmission type is detected, at least in part, based on the path loss reference signal associated with at least one PUSCH transmission in the PUSCH transmission set and based on the unconfigured condition of the path loss or path loss offset associated with the at least one PUSCH transmission.

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

18. The UE of claim 10, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Whether the at least one PUSCH transmission is associated with a specific uplink transmission type is detected, at least in part, based on permission to schedule at least one PUSCH transmission in the set of PUSCH transmissions.

19. The UE of claim 10, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Whether the at least one PUSCH transmission is associated with a specific uplink transmission type is detected, at least in part, based on path loss, path loss offset, or both associated with at least one PUSCH transmission in the PUSCH transmission set.

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

21. The UE of claim 10, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receive Radio Resource Control (RRC) messages indicating a specific uplink transmission type.

22. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: A virtual power clearance report is selected for the uplink carrier, wherein power control parameters are configured for the uplink carrier, or a path loss reference signal is not configured for at least one of the following: the sounding reference signal (SRS) resource set, the physical uplink control channel (PUCCH), the physical uplink shared channel (PUSCH), or the transmit configuration indicator (TCI) state, or any combination thereof for the uplink carrier; and The virtual power headroom report is calculated based at least in part on the selection and at least in part on the PUSCH reference parameter set, path loss offset, or both.

23. The UE of claim 22, wherein the one or more processors are individually or jointly further operable to execute the code to cause the UE to: The path loss offset is identified based on at least one of the following: the default path loss reference signal identifier, the default P0 nominal power level, the default uplink transmit configuration indicator (TCI) state, the default path loss value, the indicated TCI state, or any combination thereof.

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

25. The UE of claim 22, wherein the one or more processors are individually or jointly further operable to execute the code to cause the UE to: The PUSCH reference parameter set is used for the virtual power headroom report based at least in part on the indicated TCI state of the UE, wherein the path loss offset is in a non-configured state for the indicated TCI state.

26. The UE of claim 22, wherein the one or more processors are individually or jointly further operable to execute the code to cause the UE to: Receive a Radio Resource Control (RRC) message indicating whether to use the path loss offset for the virtual power headroom report.

27. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Selecting an actual power clearance report or a virtual power clearance report for transmission in a first Physical Uplink Shared Channel (PUSCH) transmission on the UE's uplink carrier, the selection being at least in part based on prior acceptance of a second PUSCH transmission scheduled in association with the uplink transmission type, wherein the prior acceptance was received before or during the Physical Downlink Control Channel (PDCCH) monitoring timing when the UE detects acceptance of the first PUSCH transmission scheduled on the uplink carrier; and The actual power clearance report or the virtual power clearance report is transmitted in the first PUSCH transmission on the uplink carrier of the UE, depending on the selection.

28. The UE of claim 27, wherein the one or more processors are individually or jointly further operable to execute the code to cause the UE to: The actual power headroom report to be sent in the first PUSCH transmission is selected at least in part based on the association of the second PUSCH transmission with a specific uplink transmission type, wherein the uplink transmission type includes the specific uplink transmission type.

29. The UE of claim 27, wherein the one or more processors are individually or jointly further operable to execute the code to cause the UE to: The virtual power clearance report to be sent in the first PUSCH transmission is selected at least in part based on the association of the second PUSCH transmission with a non-specific uplink transmission type, wherein the uplink transmission type includes the non-specific uplink transmission type.

30. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: Send a message to the user equipment (UE) indicating the triggered power clearance report status of the UE, the triggered power clearance report status indicating whether the transmission of a power clearance report triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled. as well as The power clearance report is selectively received based on the triggered power clearance report status and the path loss change on the at least one uplink carrier.

31. The network entity of claim 30, wherein the message includes a Radio Resource Control (RRC) message.

32. The network entity of claim 30, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: Sending an indication of power control parameters configured for at least one of Sound Reference Signal (SRS) transmission, Physical Uplink Control Channel (PUCCH) transmission, or Physical Uplink Shared Channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status indicating whether the power clearance reporting is enabled is at least partially based on the power control parameters.

33. The network entity of claim 32, wherein the power control parameter includes at least one of path loss value or path loss offset.

34. The network entity of claim 30, wherein the one or more processors are individually or jointly further operable to execute the code to cause the network entity to: Send an indication of power control parameters configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance reporting status indicating whether the transmission of the power clearance report is enabled is at least in part based on the power control parameters.

35. The network entity according to claim 30, wherein, In order to receive the message, the one or more processors can operate individually or jointly to execute the code to enable the network entity to: The detection path loss reference signal is configured for at least one of the following: probe reference signal (SRS) transmission, physical uplink control channel (PUCCH) transmission, or physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status, which indicates whether the transmission of the power clearance report is enabled, is at least partially based on the detection.

36. The network entity according to claim 30, wherein, In order to send the message, the one or more processors can operate individually or jointly to execute the code to enable the network entity to: The detection determines whether a path loss reference signal is configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance reporting status, which indicates whether the transmission of the power clearance report is enabled, is at least partially based on the detection.

37. The network entity according to claim 30, wherein, In order to selectively receive the power clearance report, the one or more processors can operate individually or jointly to execute the code to enable the network entity to: The transmission of the power clearance report is enabled at least in part based on the triggered power clearance report status indication and the power clearance report is received based on the path loss change on the at least one uplink carrier satisfying the path loss threshold.

38. The network entity according to claim 30, wherein, In order to selectively receive the power clearance report, the one or more processors can operate individually or jointly to execute the code to enable the network entity to: At least in part, the transmission of the power clearance report is disabled based on the triggered power clearance report status indication to avoid receiving the power clearance report.

39. A user equipment (UE), the user equipment (UE) comprising: A processing system, comprising processor circuitry and memory circuitry for storing code, is configured to cause the UE to: During the time slot, a power clearance report is transmitted in the Physical Uplink Shared Channel (PUSCH) transmission on the first uplink carrier of the UE, wherein the PUSCH transmission set in the second uplink carrier overlaps with the PUSCH transmission on the first uplink carrier in the time domain during the time slot; as well as A power clearance report value is provided for the second uplink carrier of the UE, the power clearance report value of the second uplink carrier including an actual power clearance report or a virtual power clearance report, wherein the selection of the actual power clearance report or the virtual power clearance report for the second uplink carrier is based at least in part on the uplink transmission type of each PUSCH transmission in the PUSCH transmission set.

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

41. The UE of claim 39, wherein the processing system is further configured to cause the UE to: Detecting that each PUSCH transmission in the PUSCH transmission set is associated with a non-specific transmission type; and The actual power clearance report is selected for the second uplink carrier based at least in part on the detection, wherein the actual power clearance report is based at least in part on the first PUSCH transmission in the PUSCH transmission set.

42. The UE of claim 39, wherein the processing system is further configured to cause the UE to: Detecting that each PUSCH transmission in the PUSCH transmission set is associated with a non-specific uplink transmission type; and The virtual power clearance report is selected for the second uplink carrier based at least in part on the detection.

43. The UE of claim 39, wherein the processing system is further configured to cause the UE to: The first PUSCH transmission in the PUSCH transmission set is associated with a specific uplink transmission type; and The actual power clearance report is selected for the second uplink carrier, wherein the actual power clearance report is at least partially based on the first PUSCH transmission in the PUSCH transmission set.

44. The UE of claim 39, wherein the processing system is further configured to cause the UE to: The first PUSCH transmission in the PUSCH transmission set is associated with a non-specific uplink transmission type; and The virtual power clearance report is selected for the second uplink carrier based at least in part on the detection.

45. The UE of claim 39, wherein the processing system is further configured to cause the UE to: Whether the at least one PUSCH transmission is associated with a specific uplink transmission type is detected, at least in part, based on the path loss reference signal associated with at least one PUSCH transmission in the PUSCH transmission set and based on the unconfigured condition of the path loss or path loss offset associated with the at least one PUSCH transmission.

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

47. The UE of claim 39, wherein the processing system is further configured to cause the UE to: Whether the at least one PUSCH transmission is associated with a specific uplink transmission type is detected, at least in part, based on permission to schedule at least one PUSCH transmission in the set of PUSCH transmissions.

48. The UE of claim 39, wherein the processing system is further configured to cause the UE to: Whether the at least one PUSCH transmission is associated with a specific uplink transmission type is detected, at least in part, based on path loss, path loss offset, or both associated with at least one PUSCH transmission in the PUSCH transmission set.

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

50. The UE of claim 39, wherein the processing system is further configured to cause the UE to: Receive Radio Resource Control (RRC) messages indicating a specific uplink transmission type.

51. A user equipment (UE), the user equipment (UE) comprising: A processing system, comprising processor circuitry and memory circuitry for storing code, is configured to cause the UE to: A virtual power clearance report is selected for the uplink carrier, wherein power control parameters are configured for the uplink carrier, or a path loss reference signal is not configured for at least one of the following: the sounding reference signal (SRS) resource set, the physical uplink control channel (PUCCH), the physical uplink shared channel (PUSCH), or the transmit configuration indicator (TCI) state, or any combination thereof for the uplink carrier; and The virtual power headroom report is calculated based at least in part on the selection and at least in part on the PUSCH reference parameter set, path loss offset, or both.

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

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

54. The UE of claim 51, wherein the processing system is further configured to cause the UE to: The PUSCH reference parameter set is used for the virtual power headroom report based at least in part on the indicated TCI state of the UE, wherein the path loss offset is in a non-configured state for the indicated TCI state.

55. 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 path loss offset for the virtual power headroom report.

56. A user equipment (UE), the user equipment (UE) comprising: A processing system, comprising processor circuitry and memory circuitry for storing code, is configured to cause the UE to: Selecting an actual power clearance report or a virtual power clearance report for transmission in a first Physical Uplink Shared Channel (PUSCH) transmission on the UE's uplink carrier, the selection being at least in part based on prior acceptance of a second PUSCH transmission scheduled in association with the uplink transmission type, wherein the prior acceptance was received before or during the Physical Downlink Control Channel (PDCCH) monitoring timing when the UE detects acceptance of the first PUSCH transmission scheduled on the uplink carrier; and The actual power clearance report or the virtual power clearance report is transmitted in the first PUSCH transmission on the uplink carrier of the UE, depending on the selection.

57. The UE of claim 56, wherein the processing system is further configured to cause the UE to: The actual power headroom report to be sent in the first PUSCH transmission is selected at least in part based on the association of the second PUSCH transmission with a specific uplink transmission type, wherein the uplink transmission type includes the specific uplink transmission type.

58. The UE of claim 56, wherein the processing system is further configured to cause the UE to: The virtual power clearance report to be sent in the first PUSCH transmission is selected at least in part based on the association of the second PUSCH transmission with a non-specific uplink transmission type, wherein the uplink transmission type includes the non-specific uplink transmission type.

59. A network entity, the network entity comprising: A processing system, comprising processor circuitry and memory circuitry for storing code, is configured to cause the network entity to: Send a message to the user equipment (UE) indicating the triggered power clearance report status of the UE, the triggered power clearance report status indicating whether the transmission of a power clearance report triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled. as well as The power clearance report is selectively received based on the triggered power clearance report status and the path loss change on the at least one uplink carrier.

60. The network entity of claim 59, wherein the message includes a Radio Resource Control (RRC) message.

61. The network entity of claim 59, wherein the processing system is further configured to cause the network entity to: Sending an indication of power control parameters configured for at least one of Sound Reference Signal (SRS) transmission, Physical Uplink Control Channel (PUCCH) transmission, or Physical Uplink Shared Channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status indicating whether the power clearance reporting is enabled is at least partially based on the power control parameters.

62. The network entity of claim 61, wherein the power control parameter includes at least one of path loss value or path loss offset.

63. The network entity of claim 59, wherein the processing system is further configured to cause the network entity to: Send an indication of power control parameters configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance reporting status indicating whether the transmission of the power clearance report is enabled is at least in part based on the power control parameters.

64. The network entity according to claim 59, wherein, In order to receive the message, the processing system is configured to cause the network entity to: The detection path loss reference signal is configured for at least one of the following: probe reference signal (SRS) transmission, physical uplink control channel (PUCCH) transmission, or physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status, which indicates whether the transmission of the power clearance report is enabled, is at least partially based on the detection.

65. The network entity according to claim 59, wherein, In order to send the message, the processing system is configured to cause the network entity to: The detection determines whether a path loss reference signal is configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance reporting status, which indicates whether the transmission of the power clearance report is enabled, is at least partially based on the detection.

66. The network entity according to claim 59, wherein, In order to selectively receive the power clearance report, the processing system is configured to cause the network entity to: The transmission of the power clearance report is enabled at least in part based on the triggered power clearance report status indication and the power clearance report is received based on the path loss change on the at least one uplink carrier satisfying the path loss threshold.

67. The network entity according to claim 59, wherein, In order to selectively receive the power clearance report, the processing system is configured to cause the network entity to: At least in part, the transmission of the power clearance report is disabled based on the triggered power clearance report status indication to avoid receiving the power clearance report.

68. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive a message indicating the triggered power clearance report status of the UE, the triggered power clearance report status indicating whether to enable the transmission of a power clearance report triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold. as well as The power clearance report is selectively sent based on the triggered power clearance report status and the path loss change on the at least one uplink carrier.

69. The method of claim 68, wherein the message comprises a Radio Resource Control (RRC) message.

70. The method of claim 68, further comprising: Receive an indication of power control parameters configured for at least one of Sound Reference Signal (SRS) transmission, Physical Uplink Control Channel (PUCCH) transmission, or Physical Uplink Shared Channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status indicating whether to enable the transmission of the power clearance report is at least partially based on the power control parameters.

71. The method of claim 70, wherein the power control parameter includes at least one of path loss value or path loss offset.

72. The method according to claim 68, further comprising: Receive an indication of power control parameters configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance report status indicating whether to enable the transmission of the power clearance report is at least partially based on the power control parameters.

73. The method of claim 68, wherein receiving the message comprises: The detection path loss reference signal is configured for at least one of the following: probe reference signal (SRS) transmission, physical uplink control channel (PUCCH) transmission, or physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status, which indicates whether the transmission of the power clearance report is enabled, is at least partially based on the detection.

74. The method of claim 68, wherein receiving the message comprises: The detection determines whether a path loss reference signal is configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance reporting status, which indicates whether the transmission of the power clearance report is enabled, is at least partially based on the detection.

75. The method of claim 68, wherein selectively sending the power clearance report comprises: The transmission of the power clearance report is enabled at least in part based on the triggered power clearance report status indication and based on the path loss change on the at least one uplink carrier satisfying the path loss threshold.

76. The method of claim 68, wherein selectively sending the power clearance report comprises: The path loss change on the at least one uplink carrier is detected to have met the path loss threshold. as well as The power clearance report is avoided from being sent, at least in part, based on the trigger-based power clearance report status indication that the sending of the power clearance report is disabled.

77. A method for conducting wireless communication at a user equipment (UE), the method comprising: During the time slot, a power clearance report is transmitted in the Physical Uplink Shared Channel (PUSCH) transmission on the first uplink carrier of the UE, wherein the PUSCH transmission set in the second uplink carrier overlaps with the PUSCH transmission on the first uplink carrier in the time domain during the time slot; as well as A power clearance report value is provided for the second uplink carrier of the UE, the power clearance report value of the second uplink carrier including an actual power clearance report or a virtual power clearance report, wherein the selection of the actual power clearance report or the virtual power clearance report for the second uplink carrier is based at least in part on the uplink transmission type of each PUSCH transmission in the PUSCH transmission set.

78. The method according to claim 77, further comprising: Detect that at least one PUSCH transmission in the PUSCH transmission set is associated with a specific uplink transmission type; as well as The actual power clearance report is selected for the second uplink carrier, wherein the actual power clearance report is based on the at least one PUSCH transmission being the first PUSCH transmission in the PUSCH transmission set associated with the specific uplink transmission type.

79. The method according to claim 77, further comprising: The detection associates each PUSCH transmission in the PUSCH transmission set with a non-specific transmission type; as well as The actual power clearance report is selected for the second uplink carrier based at least in part on the detection, wherein the actual power clearance report is based at least in part on the first PUSCH transmission in the PUSCH transmission set.

80. The method of claim 77, further comprising: The detection associates each PUSCH transmission in the PUSCH transmission set with a non-specific uplink transmission type; as well as The virtual power clearance report is selected for the second uplink carrier based at least in part on the detection.

81. The method according to claim 77, further comprising: The first PUSCH transmission in the PUSCH transmission set is associated with a specific uplink transmission type; as well as The actual power clearance report is selected for the second uplink carrier, wherein the actual power clearance report is at least partially based on the first PUSCH transmission in the PUSCH transmission set.

82. The method according to claim 77, further comprising: The first PUSCH transmission in the PUSCH transmission set is associated with a non-specific uplink transmission type; as well as The virtual power clearance report is selected for the second uplink carrier based at least in part on the detection.

83. The method according to claim 77, further comprising: Whether the at least one PUSCH transmission is associated with a specific uplink transmission type is detected, at least in part, based on the path loss reference signal associated with at least one PUSCH transmission in the PUSCH transmission set and based on the unconfigured condition of the path loss or path loss offset associated with the at least one PUSCH transmission.

84. The method according to claim 77, further comprising: The at least one PUSCH transmission is detected at least in part based on the uplink transmission configuration indicator (TCI) state associated with at least one PUSCH transmission in the PUSCH transmission set, wherein the uplink TCI state is associated with a downlink path loss reference signal, a source downlink reference signal, a timing advance group identifier, or any combination thereof.

85. The method according to claim 77, further comprising: The at least one PUSCH transmission is detected at least in part based on permission to schedule at least one PUSCH transmission in the set of PUSCH transmissions.

86. The method according to claim 77, further comprising: The at least one PUSCH transmission is detected at least in part based on path loss, path loss offset, or both associated with at least one PUSCH transmission in the PUSCH transmission set.

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

88. The method according to claim 77, further comprising: Receive Radio Resource Control (RRC) messages indicating a specific uplink transmission type.

89. A method for conducting wireless communication at a user equipment (UE), the method comprising: A virtual power clearance report is selected for the uplink carrier, wherein power control parameters are configured for the uplink carrier, or a path loss reference signal is not configured for at least one of the following: the sounding reference signal (SRS) resource set, the physical uplink control channel (PUCCH), the physical uplink shared channel (PUSCH), or the transmit configuration indicator (TCI) state, or any combination thereof for the uplink carrier; and The virtual power headroom report is calculated based at least in part on the selection and at least in part on the PUSCH reference parameter set, path loss offset, or both.

90. The method according to claim 89, further comprising: The path loss offset is identified based on at least one of the following: the default path loss reference signal identifier, the default P0 nominal power level, the default uplink transmit configuration indicator (TCI) state, the default path loss value, the indicated TCI state, or any combination thereof.

91. The method according to claim 89, further comprising: The path loss offset for the virtual power headroom report is determined at least in part based on the indicated TCI state of the UE, wherein the indicated TCI state is associated with the path loss offset.

92. The method according to claim 89, further comprising: The PUSCH reference parameter set is used for the virtual power headroom report based at least in part on the indicated TCI state of the UE, wherein the path loss offset is in a non-configured state for the indicated TCI state.

93. The method according to claim 89, further comprising: Receive a Radio Resource Control (RRC) message indicating whether to use the path loss offset for the virtual power headroom report.

94. A method for conducting wireless communication at a user equipment (UE), the method comprising: Selecting an actual power clearance report or a virtual power clearance report for transmission in a first Physical Uplink Shared Channel (PUSCH) transmission on the UE's uplink carrier, the selection being at least in part based on prior acceptance of a second PUSCH transmission scheduled in association with the uplink transmission type, wherein the prior acceptance was received before or during the Physical Downlink Control Channel (PDCCH) monitoring timing when the UE detects acceptance of the first PUSCH transmission scheduled on the uplink carrier; and The actual power clearance report or the virtual power clearance report is transmitted in the first PUSCH transmission on the uplink carrier of the UE, depending on the selection.

95. The method according to claim 94, further comprising: The actual power headroom report to be sent in the first PUSCH transmission is selected at least in part based on the association of the second PUSCH transmission with a specific uplink transmission type, wherein the uplink transmission type includes the specific uplink transmission type.

96. The method according to claim 94, further comprising: The virtual power clearance report to be sent in the first PUSCH transmission is selected at least in part based on the association of the second PUSCH transmission with a non-specific uplink transmission type, wherein the uplink transmission type includes the non-specific uplink transmission type.

97. A method for conducting wireless communication at a network entity, the method comprising: Send a message to the user equipment (UE) indicating the triggered power clearance report status of the UE, the triggered power clearance report status indicating whether the transmission of a power clearance report triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled. as well as The power clearance report is selectively received based on the triggered power clearance report status and the path loss change on the at least one uplink carrier.

98. The method of claim 97, wherein the message comprises a Radio Resource Control (RRC) message.

99. The method according to claim 97, further comprising: Sending an indication of power control parameters configured for at least one of Sound Reference Signal (SRS) transmission, Physical Uplink Control Channel (PUCCH) transmission, or Physical Uplink Shared Channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status indicating whether the power clearance reporting is enabled is at least partially based on the power control parameters.

100. The method of claim 99, wherein the power control parameter includes at least one of path loss value or path loss offset.

101. The method according to claim 97, further comprising: Send an indication of power control parameters configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance reporting status indicating whether the transmission of the power clearance report is enabled is at least in part based on the power control parameters.

102. The method of claim 97, wherein receiving the message comprises: The detection path loss reference signal is configured for at least one of the following: probe reference signal (SRS) transmission, physical uplink control channel (PUCCH) transmission, or physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status, which indicates whether the transmission of the power clearance report is enabled, is at least partially based on the detection.

103. The method of claim 97, wherein sending the message comprises: The detection determines whether a path loss reference signal is configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance reporting status, which indicates whether the transmission of the power clearance report is enabled, is at least partially based on the detection.

104. The method of claim 97, wherein selectively receiving the power clearance report comprises: The transmission of the power clearance report is enabled at least in part based on the triggered power clearance report status indication and the power clearance report is received based on the path loss change on the at least one uplink carrier satisfying the path loss threshold.

105. The method of claim 97, wherein selectively receiving the power clearance report comprises: At least in part, the transmission of the power clearance report is disabled based on the triggered power clearance report status indication to avoid receiving the power clearance report.

106. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: A component for receiving a message indicating the triggered power clearance report status of the UE, the triggered power clearance report status indicating whether the transmission of a power clearance report triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled. and A component for selectively sending the power clearance report based on the triggered power clearance report status and the path loss change on the at least one uplink carrier.

107. The UE of claim 106, wherein the message includes a Radio Resource Control (RRC) message.

108. The UE according to claim 106, further comprising: A component for receiving an indication of power control parameters configured for at least one of Sound Reference Signal (SRS) transmission, Physical Uplink Control Channel (PUCCH) transmission, or Physical Uplink Shared Channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status indicating whether the transmission of the power clearance report is enabled is at least partially based on the power control parameters.

109. The UE of claim 108, wherein the power control parameter includes at least one of path loss value or path loss offset.

110. The UE according to claim 106, further comprising: A component for receiving an indication of power control parameters configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance report status indicating whether the transmission of the power clearance report is enabled is at least in part based on the power control parameters.

111. The UE of claim 106, wherein the component for receiving the message comprises: The component for detecting whether the path loss reference signal is configured for at least one of the following: probe reference signal (SRS) transmission, physical uplink control channel (PUCCH) transmission, or physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status indicating whether the power clearance reporting is enabled is at least partially based on the detection.

112. The UE of claim 106, wherein the component for receiving the message comprises: The component used to detect whether the path loss reference signal is configured for the uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance report status indicating whether the transmission of the power clearance report is enabled is at least partially based on the detection.

113. The UE of claim 106, wherein the component for selectively transmitting the power clearance report comprises: Components for enabling the transmission of the power clearance report based at least in part on the trigger-based power clearance report status indication and for transmitting the power clearance report based on the path loss change on the at least one uplink carrier satisfying the path loss threshold.

114. The UE of claim 106, wherein the component for selectively transmitting the power clearance report comprises: A component for detecting that the path loss change on the at least one uplink carrier has met the path loss threshold; and A component for avoiding the transmission of the power clearance report by disabling the transmission of the power clearance report based at least in part on the trigger-based power clearance report status indication.

115. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: A component for transmitting a power clearance report during a physical uplink shared channel (PUSCH) transmission on a first uplink carrier of the UE during a time slot, wherein the PUSCH transmission set on a second uplink carrier overlaps in the time domain with the PUSCH transmission on the first uplink carrier in the time slot; and A component for providing a power clearance report value for the second uplink carrier of the UE, the power clearance report value of the second uplink carrier including an actual power clearance report or a virtual power clearance report, wherein the selection of the actual power clearance report or the virtual power clearance report for the second uplink carrier is based at least in part on the uplink transmission type of each PUSCH transmission in the PUSCH transmission set.

116. The UE according to claim 115, further comprising: A component used to detect that at least one PUSCH transmission in the PUSCH transmission set is associated with a specific uplink transmission type; and The component for selecting the actual power clearance report for the second uplink carrier, wherein the actual power clearance report is based on the at least one PUSCH transmission being the first PUSCH transmission in the PUSCH transmission set associated with the specific uplink transmission type.

117. The UE according to claim 115, further comprising: A component used to detect the association between each PUSCH transmission in the PUSCH transmission set and a non-specific transmission type; and The component is used to select the actual power clearance report for the second uplink carrier based at least in part on the detection, wherein the actual power clearance report is based at least in part on a first PUSCH transmission in the PUSCH transmission set.

118. The UE according to claim 115, further comprising: A component used to detect the association between each PUSCH transmission in the PUSCH transmission set and a non-specific uplink transmission type; and Components for selecting the virtual power headroom report for the second uplink carrier based at least in part on the detection.

119. The UE according to claim 115, further comprising: A component used to detect whether the first PUSCH transmission in the PUSCH transmission set is associated with a specific uplink transmission type; and The component for selecting the actual power clearance report for the second uplink carrier, wherein the actual power clearance report is at least partially based on the first PUSCH transmission in the PUSCH transmission set.

120. The UE according to claim 115, further comprising: A component used to detect whether the first PUSCH transmission in the PUSCH transmission set is associated with a non-specific uplink transmission type; and Components for selecting the virtual power headroom report for the second uplink carrier based at least in part on the detection.

121. The UE according to claim 115, further comprising: The component is used to detect whether the at least one PUSCH transmission is associated with a specific uplink transmission type, based at least in part on the path loss reference signal associated with at least one PUSCH transmission in the PUSCH transmission set and on the unconfigured condition of the path loss or path loss offset associated with the at least one PUSCH transmission.

122. The UE according to claim 115, further comprising: A component for detecting at least one PUSCH transmission based at least in part on the uplink transmission configuration indicator (TCI) state associated with at least one PUSCH transmission in the PUSCH transmission set, wherein the uplink TCI state is associated with a downlink path loss reference signal, a source downlink reference signal, a timing advance group identifier, or any combination thereof.

123. The UE according to claim 115, further comprising: A component for detecting at least one PUSCH transmission based at least in part on permission to schedule at least one PUSCH transmission in the set of PUSCH transmissions.

124. The UE according to claim 115, further comprising: A component for detecting the at least one PUSCH transmission based at least in part on path loss, path loss offset, or both associated with at least one PUSCH transmission in the PUSCH transmission set.

125. The UE according to claim 115, further comprising: A component for detecting at least one PUSCH transmission based at least in part on the uplink transmission configuration indicator (TCI) state associated with at least one PUSCH transmission in the PUSCH transmission set, wherein the uplink TCI state is associated with path loss, path loss offset, probe reference signal (SRS) resource, timing advance group identifier, or any combination thereof.

126. The UE according to claim 115, further comprising: A component used to receive Radio Resource Control (RRC) messages indicating a specific uplink transmission type.

127. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Components for selecting virtual power clearance reports for uplink carriers, wherein power control parameters are configured for the uplink carrier, or a path loss reference signal unconfigured condition exists for at least one of the following: the sounding reference signal (SRS) resource set, the physical uplink control channel (PUCCH), the physical uplink shared channel (PUSCH), or the transmit configuration indicator (TCI) state, or any combination thereof; and A component for calculating the virtual power headroom report based at least in part on the selection and at least in part on the PUSCH reference parameter set, path loss offset, or both.

128. The UE according to claim 127, further comprising: A component for identifying the path loss offset based on at least one of the following: a default path loss reference signal identifier, a default P0 nominal power level, a default uplink transmit configuration indicator (TCI) state, a default path loss value, an indicated TCI state, or any combination thereof.

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

130. The UE according to claim 127, further comprising: The component for determining, at least in part, to use the set of PUSCH reference parameters for the virtual power headroom report based on the indicated TCI state of the UE, wherein the path loss offset is in a non-configured state for the indicated TCI state.

131. The UE according to claim 127, further comprising: A component for receiving a Radio Resource Control (RRC) message indicating whether to use the path loss offset for the virtual power headroom report.

132. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: The component for selecting an actual power clearance report or a virtual power clearance report to be transmitted in a first physical uplink shared channel (PUSCH) transmission on the uplink carrier of the UE, the selection being based at least in part on prior acceptance of a second PUSCH transmission scheduled in association with the uplink transmission type, wherein the prior acceptance was received before or during the physical downlink control channel (PDCCH) monitoring timing when the UE detects acceptance of the first PUSCH transmission on the uplink carrier; and A component for transmitting the actual power clearance report or the virtual power clearance report in the first PUSCH transmission on the uplink carrier of the UE, based on the selection.

133. The UE according to claim 132, further comprising: The component is used to select the actual power headroom report to be transmitted in the first PUSCH transmission based at least in part on the association of the second PUSCH transmission with a specific uplink transmission type, wherein the uplink transmission type includes the specific uplink transmission type.

134. The UE according to claim 132, further comprising: The component is used to select the virtual power clearance report to be transmitted in the first PUSCH transmission based at least in part on the association of the second PUSCH transmission with a non-specific uplink transmission type, wherein the uplink transmission type includes the non-specific uplink transmission type.

135. A network entity for wireless communication, the network entity comprising: A component for sending a message to a user equipment (UE) indicating the triggered power clearance report status of the UE, the triggered power clearance report status indicating whether the transmission of a power clearance report triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled. and A component for selectively receiving the power clearance report based on the triggered power clearance report status and the path loss change on the at least one uplink carrier.

136. The network entity of claim 135, wherein the message includes a Radio Resource Control (RRC) message.

137. The network entity according to claim 135, further comprising: A component for transmitting an indication of power control parameters configured for at least one of Sound Reference Signal (SRS) transmission, Physical Uplink Control Channel (PUCCH) transmission, or Physical Uplink Shared Channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status indicating whether the transmission of the power clearance report is enabled is at least partially based on the power control parameters.

138. The network entity of claim 137, wherein the power control parameter includes at least one of path loss value or path loss offset.

139. The network entity according to claim 135, further comprising: A component for sending an indication of power control parameters configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance reporting status indicating whether the transmission of the power clearance report is enabled is at least in part based on the power control parameters.

140. The network entity of claim 135, wherein the component for receiving the message comprises: The component for detecting whether the path loss reference signal is configured for at least one of the following: probe reference signal (SRS) transmission, physical uplink control channel (PUCCH) transmission, or physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status indicating whether the power clearance reporting is enabled is at least partially based on the detection.

141. The network entity of claim 135, wherein the component for sending the message comprises: The component used to detect whether the path loss reference signal is configured for the uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance report status indicating whether the transmission of the power clearance report is enabled is at least partially based on the detection.

142. The network entity of claim 135, wherein the component for selectively receiving the power clearance report comprises: A component for enabling the transmission of the power clearance report based at least in part on the trigger-based power clearance report status indication and for receiving the power clearance report based on the path loss change on the at least one uplink carrier satisfying the path loss threshold.

143. The network entity of claim 135, wherein the component for selectively receiving the power clearance report comprises: A component for avoiding receiving the power clearance report by disabling the transmission of the power clearance report, at least in part, based on the trigger-based power clearance report status indication.

144. A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by one or more processors to perform the following operations: At the User Equipment (UE), a message indicating the triggered power clearance report status of the UE is received, the triggered power clearance report status indicating whether to enable the transmission of a power clearance report triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold; and The power clearance report is selectively sent based on the triggered power clearance report status and the path loss change on the at least one uplink carrier.

145. The non-transitory computer-readable medium of claim 144, wherein the message comprises a Radio Resource Control (RRC) message.

146. 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 power control parameters configured for at least one of Sound Reference Signal (SRS) transmission, Physical Uplink Control Channel (PUCCH) transmission, or Physical Uplink Shared Channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status indicating whether to enable the transmission of the power clearance report is at least partially based on the power control parameters.

147. The non-transitory computer-readable medium of claim 146, wherein the power control parameter includes at least one of a path loss value or a path loss offset.

148. 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 power control parameters configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance report status indicating whether to enable the transmission of the power clearance report is at least partially based on the power control parameters.

149. The non-transitory computer-readable medium of claim 144, wherein the instructions for receiving the message are executable by the one or more processors to: The detection path loss reference signal is configured for at least one of the following: probe reference signal (SRS) transmission, physical uplink control channel (PUCCH) transmission, or physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status, which indicates whether the transmission of the power clearance report is enabled, is at least partially based on the detection.

150. The non-transitory computer-readable medium of claim 144, wherein the instructions for receiving the message are executable by the one or more processors to: The detection determines whether a path loss reference signal is configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance reporting status, which indicates whether the transmission of the power clearance report is enabled, is at least partially based on the detection.

151. The non-transitory computer-readable medium of claim 144, wherein the instructions for selectively sending the power clearance report are executable by the one or more processors to: The transmission of the power clearance report is enabled at least in part based on the triggered power clearance report status indication and based on the path loss change on the at least one uplink carrier satisfying the path loss threshold.

152. The non-transitory computer-readable medium of claim 144, wherein the instructions for selectively sending the power clearance report are executable by the one or more processors to: The path loss change on at least one uplink carrier has been detected to meet the path loss threshold; and The power clearance report is avoided from being sent, at least in part, based on the trigger-based power clearance report status indication that the sending of the power clearance report is disabled.

153. A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by one or more processors to perform the following operations: During a time slot, a power clearance report is transmitted in the Physical Uplink Shared Channel (PUSCH) transmission on a first uplink carrier of the User Equipment (UE), wherein the PUSCH transmission set on the second uplink carrier overlaps in the time domain with the PUSCH transmission on the first uplink carrier in the time slot; and A power clearance report value is provided for the second uplink carrier of the UE, the power clearance report value of the second uplink carrier including an actual power clearance report or a virtual power clearance report, wherein the selection of the actual power clearance report or the virtual power clearance report for the second uplink carrier is based at least in part on the uplink transmission type of each PUSCH transmission in the PUSCH transmission set.

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

155. The non-transitory computer-readable medium of claim 153, wherein the instructions are further executable by the one or more processors to: Detecting that each PUSCH transmission in the PUSCH transmission set is associated with a non-specific transmission type; and The actual power clearance report is selected for the second uplink carrier based at least in part on the detection, wherein the actual power clearance report is based at least in part on the first PUSCH transmission in the PUSCH transmission set.

156. The non-transitory computer-readable medium of claim 153, wherein the instructions are further executable by the one or more processors to: Detecting that each PUSCH transmission in the PUSCH transmission set is associated with a non-specific uplink transmission type; and The virtual power clearance report is selected for the second uplink carrier based at least in part on the detection.

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

158. The non-transitory computer-readable medium of claim 153, wherein the instructions are further executable by the one or more processors to: The first PUSCH transmission in the PUSCH transmission set is associated with a non-specific uplink transmission type; and The virtual power clearance report is selected for the second uplink carrier based at least in part on the detection.

159. The non-transitory computer-readable medium of claim 153, wherein the instructions are further executable by the one or more processors to: Whether the at least one PUSCH transmission is associated with a specific uplink transmission type is detected, at least in part, based on the path loss reference signal associated with at least one PUSCH transmission in the PUSCH transmission set and based on the unconfigured condition of the path loss or path loss offset associated with the at least one PUSCH transmission.

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

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

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

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

164. The non-transitory computer-readable medium of claim 153, wherein the instructions are further executable by the one or more processors to: Receive Radio Resource Control (RRC) messages indicating a specific uplink transmission type.

165. A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by one or more processors to perform the following operations: A virtual power clearance report is selected for the uplink carrier, wherein power control parameters are configured for the uplink carrier, or a path loss reference signal is not configured for at least one of the following: the sounding reference signal (SRS) resource set, the physical uplink control channel (PUCCH), the physical uplink shared channel (PUSCH), or the transmit configuration indicator (TCI) state, or any combination thereof for the uplink carrier; and The virtual power headroom report is calculated based at least in part on the selection and at least in part on the PUSCH reference parameter set, path loss offset, or both.

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

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

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

169. 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 path loss offset for the virtual power headroom report.

170. A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by one or more processors to perform the following operations: Selecting an actual power clearance report or a virtual power clearance report for transmission in a first Physical Uplink Shared Channel (PUSCH) transmission on an uplink carrier of a User Equipment (UE), the selection being at least in part based on prior acceptance of a second PUSCH transmission scheduled in association with the uplink transmission type, wherein the prior acceptance was received before or during the Physical Downlink Control Channel (PDCCH) monitoring timing at which the UE detects acceptance of the first PUSCH transmission scheduled on the first uplink carrier; and The actual power clearance report or the virtual power clearance report is transmitted in the first PUSCH transmission on the uplink carrier of the UE, depending on the selection.

171. The non-transitory computer-readable medium of claim 170, wherein the instructions are further executable by the one or more processors to: The actual power headroom report to be sent in the first PUSCH transmission is selected at least in part based on the association of the second PUSCH transmission with a specific uplink transmission type, wherein the uplink transmission type includes the specific uplink transmission type.

172. The non-transitory computer-readable medium of claim 170, wherein the instructions are further executable by the one or more processors to: The virtual power clearance report to be sent in the first PUSCH transmission is selected at least in part based on the association of the second PUSCH transmission with a non-specific uplink transmission type, wherein the uplink transmission type includes the non-specific uplink transmission type.

173. A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by one or more processors to perform the following operations: Send a message to the User Equipment (UE) indicating the triggered power clearance report status of the UE, the triggered power clearance report status indicating whether to enable the transmission of a power clearance report triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold; and The power clearance report is selectively received based on the triggered power clearance report status and the path loss change on the at least one uplink carrier.

174. The non-transitory computer-readable medium of claim 173, wherein the message includes a Radio Resource Control (RRC) message.

175. The non-transitory computer-readable medium of claim 173, wherein the instructions are further executable by the one or more processors to: Sending an indication of power control parameters configured for at least one of Sound Reference Signal (SRS) transmission, Physical Uplink Control Channel (PUCCH) transmission, or Physical Uplink Shared Channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status indicating whether the power clearance reporting is enabled is at least partially based on the power control parameters.

176. The non-transitory computer-readable medium of claim 175, wherein the power control parameter includes at least one of a path loss value or a path loss offset.

177. The non-transitory computer-readable medium of claim 173, wherein the instructions are further executable by the one or more processors to: Send an indication of power control parameters configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance reporting status indicating whether the transmission of the power clearance report is enabled is at least in part based on the power control parameters.

178. The non-transitory computer-readable medium of claim 173, wherein the instructions for receiving the message are executable by the one or more processors to: The detection path loss reference signal is configured for at least one of the following: probe reference signal (SRS) transmission, physical uplink control channel (PUCCH) transmission, or physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status, which indicates whether the transmission of the power clearance report is enabled, is at least partially based on the detection.

179. The non-transitory computer-readable medium of claim 173, wherein the instructions for sending the message are executable by the one or more processors to: The detection determines whether a path loss reference signal is configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance reporting status, which indicates whether the transmission of the power clearance report is enabled, is at least partially based on the detection.

180. The non-transitory computer-readable medium of claim 173, wherein the instructions for selectively receiving the power clearance report are executable by the one or more processors to: The transmission of the power clearance report is enabled at least in part based on the triggered power clearance report status indication and the power clearance report is received based on the path loss change on the at least one uplink carrier satisfying the path loss threshold.

181. The non-transitory computer-readable medium of claim 173, wherein the instructions for selectively receiving the power clearance report are executable by the one or more processors to: At least in part, the transmission of the power clearance report is disabled based on the triggered power clearance report status indication to avoid receiving the power clearance report.

182. A method for wireless communication by a user equipment (UE), the method comprising: Receive a message indicating the triggered power clearance report status of the UE, the triggered power clearance report status indicating whether to enable the transmission of a power clearance report triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold. as well as The power clearance report is selectively sent based on the triggered power clearance report status and the path loss change on the at least one uplink carrier.

183. The method of claim 182, wherein the message comprises a Radio Resource Control (RRC) message.

184. The method according to any one of claims 182 to 183, the method further comprising: Receive an indication of power control parameters configured for at least one of Sound Reference Signal (SRS) transmission, Physical Uplink Control Channel (PUCCH) transmission, or Physical Uplink Shared Channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status indicating whether to enable the transmission of the power clearance report is at least partially based on the power control parameters.

185. The method of claim 184, wherein the power control parameter includes at least one of path loss value or path loss offset.

186. The method according to any one of claims 182 to 185, the method further comprising: Receive an indication of power control parameters configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance report status indicating whether to enable the transmission of the power clearance report is at least partially based on the power control parameters.

187. The method of any one of claims 182 to 186, wherein receiving the message includes detecting whether a path loss reference signal is configured for at least one of: probe reference signal (SRS) transmission, physical uplink control channel (PUCCH) transmission, or physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status indicating whether the transmission of the power clearance report is enabled is based at least in part on the detection.

188. The method of any one of claims 182 to 187, wherein receiving the message includes detecting whether a path loss reference signal is configured for an uplink transmit configuration indicator (TCI) state, wherein the trigger-based power clearance reporting status indicating whether the transmission of the power clearance report is enabled is at least partially based on the detection.

189. The method according to any one of claims 182 to 188, wherein selectively sending the power clearance report comprises: The transmission of the power clearance report is enabled at least in part based on the triggered power clearance report status indication and based on the path loss change on the at least one uplink carrier satisfying the path loss threshold.

190. The method according to any one of claims 182 to 189, wherein selectively sending the power clearance report comprises: The path loss change on the at least one uplink carrier is detected to have met the path loss threshold. as well as The power clearance report is avoided from being sent, at least in part, based on the trigger-based power clearance report status indication that the sending of the power clearance report is disabled.

191. A method for wireless communication by a user equipment (UE), the method comprising: During the time slot, a power clearance report is transmitted in the Physical Uplink Shared Channel (PUSCH) transmission on the first uplink carrier of the UE, wherein the PUSCH transmission set in the second uplink carrier overlaps with the PUSCH transmission on the first uplink carrier in the time domain during the time slot; as well as A power clearance report value is provided for the second uplink carrier of the UE, the power clearance report value of the second uplink carrier including an actual power clearance report or a virtual power clearance report, wherein the selection of the actual power clearance report or the virtual power clearance report for the second uplink carrier is based at least in part on the uplink transmission type of each PUSCH transmission in the PUSCH transmission set.

192. The method according to claim 191, further comprising: Detect that at least one PUSCH transmission in the PUSCH transmission set is associated with a specific uplink transmission type; as well as The actual power clearance report is selected for the second uplink carrier, wherein the actual power clearance report is based on the at least one PUSCH transmission being the first PUSCH transmission in the PUSCH transmission set associated with the specific uplink transmission type.

193. The method according to any one of claims 191 to 192, the method further comprising: The detection associates each PUSCH transmission in the PUSCH transmission set with a non-specific transmission type; as well as The actual power clearance report is selected for the second uplink carrier based at least in part on the detection, wherein the actual power clearance report is based at least in part on the first PUSCH transmission in the PUSCH transmission set.

194. The method according to any one of claims 191 to 193, the method further comprising: The detection associates each PUSCH transmission in the PUSCH transmission set with a non-specific uplink transmission type; as well as The virtual power clearance report is selected for the second uplink carrier based at least in part on the detection.

195. The method according to any one of claims 191 to 194, the method further comprising: The first PUSCH transmission in the PUSCH transmission set is associated with a specific uplink transmission type; as well as The actual power clearance report is selected for the second uplink carrier, wherein the actual power clearance report is at least partially based on the first PUSCH transmission in the PUSCH transmission set.

196. The method according to any one of claims 191 to 195, the method further comprising: The first PUSCH transmission in the PUSCH transmission set is associated with a non-specific uplink transmission type; as well as The virtual power clearance report is selected for the second uplink carrier based at least in part on the detection.

197. The method according to any one of claims 191 to 196, the method further comprising: Whether the at least one PUSCH transmission is associated with a specific uplink transmission type is detected, at least in part, based on the path loss reference signal associated with at least one PUSCH transmission in the PUSCH transmission set and based on the unconfigured condition of the path loss or path loss offset associated with the at least one PUSCH transmission.

198. The method according to any one of claims 191 to 197, the method further comprising: The at least one PUSCH transmission is detected at least in part based on the uplink transmission configuration indicator (TCI) state associated with at least one PUSCH transmission in the PUSCH transmission set, wherein the uplink TCI state is associated with a downlink path loss reference signal, a source downlink reference signal, a timing advance group identifier, or any combination thereof.

199. The method according to any one of claims 191 to 198, the method further comprising: The at least one PUSCH transmission is detected at least in part based on permission to schedule at least one PUSCH transmission in the set of PUSCH transmissions.

200. The method according to any one of claims 191 to 199, the method further comprising: The at least one PUSCH transmission is detected at least in part based on path loss, path loss offset, or both associated with at least one PUSCH transmission in the PUSCH transmission set.

201. The method according to any one of claims 191 to 200, the method further comprising: The at least one PUSCH transmission is detected at least in part based on the uplink transmission configuration indicator (TCI) state associated with at least one PUSCH transmission in the PUSCH transmission set, wherein the uplink TCI state is associated with path loss, path loss offset, probe reference signal (SRS) resource, timing advance group identifier, or any combination thereof.

202. The method according to any one of claims 191 to 201, the method further comprising: Receive Radio Resource Control (RRC) messages indicating a specific uplink transmission type.

203. A method for wireless communication by a user equipment (UE), the method comprising: A virtual power clearance report is selected for the uplink carrier, wherein power control parameters are configured for the uplink carrier, or a path loss reference signal is not configured for at least one of the following: the sounding reference signal (SRS) resource set, the physical uplink control channel (PUCCH), the physical uplink shared channel (PUSCH), or the transmit configuration indicator (TCI) state, or any combination thereof for the uplink carrier; and The virtual power headroom report is calculated based at least in part on the selection and at least in part on the PUSCH reference parameter set, path loss offset, or both.

204. The method according to claim 203, further comprising: The path loss offset is identified based on at least one of the following: the default path loss reference signal identifier, the default P0 nominal power level, the default uplink transmit configuration indicator (TCI) state, the default path loss value, the indicated TCI state, or any combination thereof.

205. The method according to any one of claims 203 to 204, the method further comprising: The path loss offset for the virtual power headroom report is determined at least in part based on the indicated TCI state of the UE, wherein the indicated TCI state is associated with the path loss offset.

206. The method according to any one of claims 203 to 205, the method further comprising: The PUSCH reference parameter set is used for the virtual power headroom report based at least in part on the indicated TCI state of the UE, wherein the path loss offset is in a non-configured state for the indicated TCI state.

207. The method according to any one of claims 203 to 206, the method further comprising: Receive a Radio Resource Control (RRC) message indicating whether to use the path loss offset for the virtual power headroom report.

208. A method for wireless communication by a user equipment (UE), the method comprising: Selecting an actual power clearance report or a virtual power clearance report for transmission in a first Physical Uplink Shared Channel (PUSCH) transmission on the UE's uplink carrier, the selection being at least in part based on prior acceptance of a second PUSCH transmission scheduled in association with the uplink transmission type, wherein the prior acceptance was received before or during the Physical Downlink Control Channel (PDCCH) monitoring timing when the UE detects acceptance of the first PUSCH transmission scheduled on the uplink carrier; and The actual power clearance report or the virtual power clearance report is transmitted in the first PUSCH transmission on the uplink carrier of the UE, depending on the selection.

209. The method according to claim 208, further comprising: The actual power headroom report to be sent in the first PUSCH transmission is selected at least in part based on the association of the second PUSCH transmission with a specific uplink transmission type, wherein the uplink transmission type includes the specific uplink transmission type.

210. The method according to any one of claims 208 to 209, the method further comprising: The virtual power clearance report to be sent in the first PUSCH transmission is selected at least in part based on the association of the second PUSCH transmission with a non-specific uplink transmission type, wherein the uplink transmission type includes the non-specific uplink transmission type.

211. A method for wireless communication by a network entity, the method comprising: Send a message to the user equipment (UE) indicating the triggered power clearance report status of the UE, the triggered power clearance report status indicating whether the transmission of a power clearance report triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled. as well as The power clearance report is selectively received based on the triggered power clearance report status and the path loss change on the at least one uplink carrier.

212. The method of claim 211, wherein the message comprises a Radio Resource Control (RRC) message.

213. The method according to any one of claims 211 to 212, the method further comprising: Sending an indication of power control parameters configured for at least one of Sound Reference Signal (SRS) transmission, Physical Uplink Control Channel (PUCCH) transmission, or Physical Uplink Shared Channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status indicating whether the power clearance reporting is enabled is at least partially based on the power control parameters.

214. The method of claim 213, wherein the power control parameter includes at least one of path loss value or path loss offset.

215. The method according to any one of claims 211 to 214, the method further comprising: Send an indication of power control parameters configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance reporting status indicating whether the transmission of the power clearance report is enabled is at least in part based on the power control parameters.

216. The method of any one of claims 211 to 215, wherein receiving the message includes detecting whether a path loss reference signal is configured for at least one of: probe reference signal (SRS) transmission, physical uplink control channel (PUCCH) transmission, or physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status indicating whether the transmission of the power clearance report is enabled is at least partially based on the detection.

217. The method of any one of claims 211 to 216, wherein sending the message includes detecting whether a path loss reference signal is configured for an uplink transmit configuration indicator (TCI) state, wherein the trigger-based power clearance reporting status indicating whether the transmission of the power clearance report is enabled is based at least in part on the detection.

218. The method according to any one of claims 211 to 217, wherein selectively receiving the power clearance report comprises: The transmission of the power clearance report is enabled at least in part based on the triggered power clearance report status indication and the power clearance report is received based on the path loss change on the at least one uplink carrier satisfying the path loss threshold.

219. The method of any one of claims 211 to 218, wherein selectively receiving the power clearance report includes at least in part disabling the transmission of the power clearance report based on the trigger-based power clearance report status indication to avoid receiving the power clearance report.

220. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Processing circuitry, associated with one or more memory devices and configured to cause the UE to: Receive a message indicating the triggered power clearance report status of the UE, the triggered power clearance report status indicating whether to enable the transmission of a power clearance report triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold. as well as The power clearance report is selectively sent based on the triggered power clearance report status and the path loss change on the at least one uplink carrier.

221. The UE of claim 220, wherein the message includes a Radio Resource Control (RRC) message.

222. The UE of claim 220, wherein the processing circuitry is further configured to cause the UE to: Receive an indication of power control parameters configured for at least one of Sound Reference Signal (SRS) transmission, Physical Uplink Control Channel (PUCCH) transmission, or Physical Uplink Shared Channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status indicating whether to enable the transmission of the power clearance report is at least partially based on the power control parameters.

223. The UE of claim 222, wherein the power control parameter includes at least one of path loss value or path loss offset.

224. The UE of claim 220, wherein the processing circuitry is further configured to cause the UE to: Receive an indication of power control parameters configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance report status indicating whether to enable the transmission of the power clearance report is at least partially based on the power control parameters.

225. The UE of claim 220, wherein receiving the message includes the processing circuit being configured to cause the UE to: The detection path loss reference signal is configured for at least one of the following: probe reference signal (SRS) transmission, physical uplink control channel (PUCCH) transmission, or physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status, which indicates whether the transmission of the power clearance report is enabled, is at least partially based on the detection.

226. The UE of claim 220, wherein receiving the message includes the processing circuitry being configured to cause the UE to: The detection determines whether a path loss reference signal is configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance reporting status, which indicates whether the transmission of the power clearance report is enabled, is at least partially based on the detection.

227. The UE of claim 220, wherein selectively transmitting the power clearance report includes the processing circuit being configured to cause the UE to: enable the transmission of the power clearance report at least in part based on the triggered power clearance report status indication and to transmit the power clearance report based on the path loss change on the at least one uplink carrier satisfying the path loss threshold.

228. The UE of claim 220, wherein selectively transmitting the power clearance report includes the processing circuit being configured to cause the UE to: The path loss change on at least one uplink carrier has been detected to meet the path loss threshold; and The power clearance report is avoided from being sent, at least in part, based on the trigger-based power clearance report status indication that the sending of the power clearance report is disabled.

229. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Processing circuitry, associated with one or more memory devices and configured to cause the UE to: During the time slot, a power clearance report is transmitted in the Physical Uplink Shared Channel (PUSCH) transmission on the first uplink carrier of the UE, wherein the PUSCH transmission set in the second uplink carrier overlaps with the PUSCH transmission on the first uplink carrier in the time domain during the time slot; as well as A power clearance report value is provided for the second uplink carrier of the UE, the power clearance report value of the second uplink carrier including an actual power clearance report or a virtual power clearance report, wherein the selection of the actual power clearance report or the virtual power clearance report for the second uplink carrier is based at least in part on the uplink transmission type of each PUSCH transmission in the PUSCH transmission set.

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

231. The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to: Detecting that each PUSCH transmission in the PUSCH transmission set is associated with a non-specific transmission type; and The actual power clearance report is selected for the second uplink carrier based at least in part on the detection, wherein the actual power clearance report is based at least in part on the first PUSCH transmission in the PUSCH transmission set.

232. The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to: Detecting that each PUSCH transmission in the PUSCH transmission set is associated with a non-specific uplink transmission type; and The virtual power clearance report is selected for the second uplink carrier based at least in part on the detection.

233. The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to: The first PUSCH transmission in the PUSCH transmission set is associated with a specific uplink transmission type; and The actual power clearance report is selected for the second uplink carrier, wherein the actual power clearance report is at least partially based on the first PUSCH transmission in the PUSCH transmission set.

234. The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to: The first PUSCH transmission in the PUSCH transmission set is associated with a non-specific uplink transmission type; and The virtual power clearance report is selected for the second uplink carrier based at least in part on the detection.

235. The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to: Whether the at least one PUSCH transmission is associated with a specific uplink transmission type is detected, at least in part, based on the path loss reference signal associated with at least one PUSCH transmission in the PUSCH transmission set and based on the unconfigured condition of the path loss or path loss offset associated with the at least one PUSCH transmission.

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

237. The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to: Whether the at least one PUSCH transmission is associated with a specific uplink transmission type is detected, at least in part, based on permission to schedule at least one PUSCH transmission in the set of PUSCH transmissions.

238. The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to: Whether the at least one PUSCH transmission is associated with a specific uplink transmission type is detected, at least in part, based on path loss, path loss offset, or both associated with at least one PUSCH transmission in the PUSCH transmission set.

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

240. The UE of claim 229, wherein the processing circuitry is further configured to cause the UE to: Receive Radio Resource Control (RRC) messages indicating a specific uplink transmission type.

241. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Processing circuitry, associated with one or more memory devices and configured to cause the UE to: A virtual power clearance report is selected for the uplink carrier, wherein power control parameters are configured for the uplink carrier, or a path loss reference signal is not configured for at least one of the following: the sounding reference signal (SRS) resource set, the physical uplink control channel (PUCCH), the physical uplink shared channel (PUSCH), or the transmit configuration indicator (TCI) state, or any combination thereof for the uplink carrier; and The virtual power headroom report is calculated based at least in part on the selection and at least in part on the PUSCH reference parameter set, path loss offset, or both.

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

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

244. The UE of claim 241, wherein the processing circuitry is further configured to cause the UE to: The PUSCH reference parameter set is used for the virtual power headroom report based at least in part on the indicated TCI state of the UE, wherein the path loss offset is in a non-configured state for the indicated TCI state.

245. 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 path loss offset for the virtual power headroom report.

246. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Processing circuitry, associated with one or more memory devices and configured to cause the UE to: Selecting an actual power clearance report or a virtual power clearance report for transmission in a first Physical Uplink Shared Channel (PUSCH) transmission on the UE's uplink carrier, the selection being at least in part based on prior acceptance of a second PUSCH transmission scheduled in association with the uplink transmission type, wherein the prior acceptance was received before or during the Physical Downlink Control Channel (PDCCH) monitoring timing when the UE detects acceptance of the first PUSCH transmission scheduled on the uplink carrier; and The actual power clearance report or the virtual power clearance report is transmitted in the first PUSCH transmission on the uplink carrier of the UE, depending on the selection.

247. The UE of claim 246, wherein the processing circuitry is further configured to cause the UE to: The actual power headroom report to be sent in the first PUSCH transmission is selected at least in part based on the association of the second PUSCH transmission with a specific uplink transmission type, wherein the uplink transmission type includes the specific uplink transmission type.

248. The UE of claim 246, wherein the processing circuitry is further configured to cause the UE to: The virtual power clearance report to be sent in the first PUSCH transmission is selected at least in part based on the association of the second PUSCH transmission with a non-specific uplink transmission type, wherein the uplink transmission type includes the non-specific uplink transmission type.

249. A network entity for wireless communication, the network entity comprising: Processing circuitry, associated with one or more memory devices and configured to cause the network entity to: Send a message to the user equipment (UE) indicating the triggered power clearance report status of the UE, the triggered power clearance report status indicating whether the transmission of a power clearance report triggered by a path loss change on at least one uplink carrier of the UE satisfying a path loss threshold is enabled. as well as The power clearance report is selectively received based on the triggered power clearance report status and the path loss change on the at least one uplink carrier.

250. The network entity of claim 249, wherein the message includes a Radio Resource Control (RRC) message.

251. The network entity of claim 249, wherein the processing circuitry is further configured to cause the network entity to: Sending an indication of power control parameters configured for at least one of Sound Reference Signal (SRS) transmission, Physical Uplink Control Channel (PUCCH) transmission, or Physical Uplink Shared Channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status indicating whether the power clearance reporting is enabled is at least partially based on the power control parameters.

252. The network entity of claim 251, wherein the power control parameter includes at least one of path loss value or path loss offset.

253. The network entity of claim 249, wherein the processing circuitry is further configured to cause the network entity to: Send an indication of power control parameters configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance reporting status indicating whether the transmission of the power clearance report is enabled is at least in part based on the power control parameters.

254. The network entity of claim 249, wherein receiving the message includes the processing circuitry being configured to cause the network entity to: The detection path loss reference signal is configured for at least one of the following: probe reference signal (SRS) transmission, physical uplink control channel (PUCCH) transmission, or physical uplink shared channel (PUSCH) transmission, wherein the trigger-based power clearance reporting status, which indicates whether the transmission of the power clearance report is enabled, is at least partially based on the detection.

255. The network entity of claim 249, wherein sending the message includes the processing circuitry being configured to cause the network entity to: The detection determines whether a path loss reference signal is configured for uplink transmit configuration indicator (TCI) status, wherein the trigger-based power clearance reporting status, which indicates whether the transmission of the power clearance report is enabled, is at least partially based on the detection.

256. The network entity of claim 249, wherein selectively receiving the power clearance report includes the processing circuitry being configured to cause the network entity to: enable the transmission of the power clearance report at least in part based on the triggered power clearance report status indication and to receive the power clearance report based on the path loss change on the at least one uplink carrier satisfying the path loss threshold.

257. The network entity of claim 249, wherein selectively receiving the power clearance report includes the processing circuitry being configured to cause the network entity to at least partially disable the transmission of the power clearance report based on the trigger-based power clearance report status indication to avoid receiving the power clearance report.

Images