Power headroom reporting for uplink carrier aggregation communications

Abstract

Methods, systems, and devices for wireless communication are described. In some systems, a user equipment (UE) may report power headroom for uplink carrier aggregation communications. The UE may receive a first message indicating that a plurality of component carriers are configured for communication at the UE. The UE may determine a first transmit power available for uplink carrier aggregation transmission by the UE across the plurality of component carriers during a transmission occasion. The UE may transmit one or more uplink messages associated with a second transmit power via one or more of the component carriers. The UE may transmit a power headroom report including carrier aggregation power headroom parameters. The value of the carrier aggregation power headroom parameter may be based on the first transmit power and the second transmit power associated with an uplink carrier aggregation transmission via at least one component carrier of the plurality of component carriers during the transmission occasion.

Description

[0001] Cross-references

[0002] This patent application claims the benefit of U.S. patent application No. 17 / 895,805, entitled “POWER HEADROOM REPORTING FOR UPLINK CARRIER AGGREGATION COMMUNICATIONS,” filed by the inventor et al. on August 25, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including power headroom reporting for uplink carrier aggregation communications. Background Art

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

[0005] In some systems, the UE may be configured to report power headroom information. The UE may send one or more power headroom reports to a network entity. The power headroom reports may each indicate an amount of power available for uplink transmission by the UE via a corresponding component carrier. Summary of the invention

[0006] The described techniques relate to improved methods, systems, devices, and apparatuses that support power headroom reporting for uplink carrier aggregation communications. For example, the described techniques allow a user equipment (UE) to report an amount of transmit power available for uplink communications by the UE across multiple component carriers. The UE may be configured to support uplink carrier aggregation, and the UE may receive a message indicating the multiple component carriers configured for carrier aggregation communications at the UE. The UE may determine an amount of transmit power available for uplink carrier aggregation transmission by the UE across the multiple component carriers during a transmission opportunity based on one or more parameters. In some aspects described herein, a transmit power (e.g., a maximum transmit power level) may be referred to as a carrier aggregation transmit power. The UE may transmit at least one power headroom report including a carrier aggregation power headroom parameter. The UE may transmit the power headroom report via one or more of the component carriers configured for communication at the UE. The value of the carrier aggregation power headroom parameter may be based on the carrier aggregation transmit power available for uplink transmission across the multiple component carriers and a second transmit power associated with uplink carrier aggregation transmission via at least one of the component carriers during the transmission opportunity. The UE may thereby report headroom relative to the total amount of power available for uplink component carrier aggregation communications, which may improve coordination between devices, throughput and reliability of uplink communications.

[0007] A method for wireless communication at a UE is described. The method may include: receiving a first message indicating that a set of multiple component carriers is configured for communication at the UE; determining a first transmit power available for uplink carrier aggregation transmission by the UE across the set of multiple component carriers during a transmission opportunity; and transmitting a power headroom report including a carrier aggregation power headroom parameter via at least a first component carrier in the set of multiple component carriers, wherein a value of the carrier aggregation power headroom parameter is based on the first transmit power available across the set of multiple component carriers during the transmission opportunity and a second transmit power associated with the uplink carrier aggregation transmission via at least one component carrier in the set of multiple component carriers during the transmission opportunity.

[0008] An apparatus for wireless communication at a UE is described. The apparatus may include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: receive a first message indicating that a set of multiple component carriers is configured for communication at the UE; determine a first transmit power available for uplink carrier aggregation transmission by the UE across the set of multiple component carriers during a transmission opportunity; and transmit a power headroom report including a carrier aggregation power headroom parameter via at least a first component carrier in the set of multiple component carriers, wherein the value of the carrier aggregation power headroom parameter is based on the first transmit power available across the set of multiple component carriers during the transmission opportunity and a second transmit power associated with the uplink carrier aggregation transmission via at least one component carrier in the set of multiple component carriers during the transmission opportunity.

[0009] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving a first message indicating that a set of multiple component carriers is configured for communication at the UE; means for determining a first transmit power available for uplink carrier aggregation transmission by the UE across the set of multiple component carriers during a transmission opportunity; and means for transmitting a power headroom report including a carrier aggregation power headroom parameter via at least a first component carrier in the set of multiple component carriers, wherein a value of the carrier aggregation power headroom parameter is based on the first transmit power available across the set of multiple component carriers during the transmission opportunity and a second transmit power associated with the uplink carrier aggregation transmission via at least one component carrier in the set of multiple component carriers during the transmission opportunity.

[0010] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to perform the following operations: receiving a first message indicating that a set of multiple component carriers is configured for communication at the UE; determining a first transmit power available for uplink carrier aggregation transmission by the UE across the set of multiple component carriers during a transmission opportunity; and transmitting a power headroom report including a carrier aggregation power headroom parameter via at least a first component carrier in the set of multiple component carriers, wherein a value of the carrier aggregation power headroom parameter is based on the first transmit power available across the set of multiple component carriers during the transmission opportunity and a second transmit power associated with the uplink carrier aggregation transmission via at least one component carrier in the set of multiple component carriers during the transmission opportunity.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending an uplink message via at least the first component carrier in the set of multiple component carriers, the uplink message being associated with the second transmit power; and calculating a difference between the first transmit power and the second transmit power available across the set of multiple component carriers, wherein the value of the carrier aggregation power headroom parameter indicates the difference.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the power headroom report may include operations, features, components, or instructions for performing the following actions: sending the carrier aggregation power headroom parameter and a second power headroom parameter via the power headroom report, wherein the value of the second power headroom parameter may be based on a difference between a third transmit power available for uplink transmission on the first component carrier and the second transmit power.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending a second uplink message via a second component carrier in the set of multiple component carriers; calculating a second difference between the first transmit power available across the set of multiple component carriers and a third transmit power associated with the second component carrier; and sending a second carrier aggregation power headroom parameter via the second uplink message, wherein the value of the second carrier aggregation power headroom parameter indicates the second difference.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: determining the second transmit power, the second transmit power corresponding to the amount of transmit power available for uplink transmission on the first component carrier, wherein the value of the carrier aggregation power headroom parameter indicates a difference between the first transmit power and the second transmit power available across the set of multiple component carriers.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the value of the carrier aggregation power headroom parameter indicates the first transmit power available for the uplink carrier aggregation transmission by the UE across the set of multiple component carriers during the transmission opportunity.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending one or more uplink messages corresponding to the uplink carrier aggregation transmission, sending each of the one or more uplink messages via a corresponding component carrier in the set of multiple component carriers and using a corresponding second transmission power; and calculating a difference between the first transmission power available across the set of multiple component carriers and the sum of the corresponding second transmission powers used to send each of the one or more uplink messages, wherein the value of the carrier aggregation power headroom parameter indicates the difference.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: calculating the sum of the corresponding second transmit powers and one or more reference power levels, the one or more reference power levels being associated with a subset of component carriers in the set of multiple component carriers that may be different from the corresponding component carrier via which the one or more uplink messages may be sent, wherein the one or more reference power levels may be based on a reference power reduction parameter.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving a control message allocating an uplink channel resource set for a carrier aggregation power headroom report, wherein the power headroom report may be sent via the uplink channel resource set based on the control message.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the power headroom report may include operations, features, components, or instructions for performing the following actions: sending the power headroom report via the first component carrier and the first cell, wherein the first component carrier and the first cell may be configured for carrier aggregation power headroom reporting by the UE.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the power headroom report may include operations, features, components, or instructions for performing the following actions: sending the power headroom report based on the expiration of a power headroom reporting timer, wherein the power headroom reporting timer includes a periodic timer, a prohibit timer, or both configured for power headroom reporting by the UE.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: determining to send the power headroom report via the resource set allocated for power headroom reporting on the first component carrier after the expiration of the power headroom reporting timer and before other resource sets allocated for power headroom reporting on other component carriers in the set of multiple component carriers.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the power headroom reporting timer includes the periodic timer, and the periodicity of the periodic timer is configured for carrier aggregation power headroom reporting, per-carrier power headroom reporting, or both.

[0023] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: determining a difference between a first path loss associated with at least one component carrier in the set of multiple component carriers at a first time and a second path loss associated with the at least one component carrier at a second time; and comparing the difference to a path loss threshold, wherein sending the power headroom report may be based on the difference exceeding the path loss threshold.

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining a difference between a first value of a first maximum power reduction (MPR) parameter associated with at least one component carrier in the set of multiple component carriers at a first time and a second value of the first MPR parameter associated with the at least one component carrier at a second time; and comparing the difference to a power reduction threshold, wherein sending the power headroom report may be based on the difference exceeding the power reduction threshold.

[0025] A method of wireless communication at a network entity is described. The method may include: sending a first message indicating that a set of multiple component carriers is configured for communication at a UE; receiving an uplink message associated with a second transmit power during a transmit opportunity via a first component carrier in the set of multiple component carriers; and receiving a power headroom report including a carrier aggregation power headroom parameter via at least the first component carrier in the set of multiple component carriers, wherein a value of the carrier aggregation power headroom parameter is based on a first transmit power available for uplink transmission by the UE across the set of multiple component carriers during the transmit opportunity and the second transmit power associated with uplink carrier aggregation transmissions performed at least via the first component carrier during the transmit opportunity.

[0026] An apparatus for wireless communication at a network entity is described. The apparatus may include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: send a first message indicating that a set of multiple component carriers is configured for communication at a UE; receive an uplink message associated with a second transmit power during a transmit opportunity via a first component carrier in the set of multiple component carriers; and receive a power headroom report including a carrier aggregation power headroom parameter via at least the first component carrier in the set of multiple component carriers, wherein the value of the carrier aggregation power headroom parameter is based on a first transmit power available for uplink transmission by the UE across the set of multiple component carriers during the transmit opportunity and the second transmit power associated with uplink carrier aggregation transmission performed at least via the first component carrier during the transmit opportunity.

[0027] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for sending a first message indicating that a set of multiple component carriers is configured for communication at a UE; means for receiving an uplink message associated with a second transmit power during a transmit opportunity via a first component carrier in the set of multiple component carriers; and means for receiving a power headroom report including a carrier aggregation power headroom parameter via at least the first component carrier in the set of multiple component carriers, wherein a value of the carrier aggregation power headroom parameter is based on a first transmit power available for uplink transmission by the UE across the set of multiple component carriers during the transmit opportunity and the second transmit power associated with uplink carrier aggregation transmissions performed at least via the first component carrier during the transmit opportunity.

[0028] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to perform the following operations: sending a first message indicating that a set of multiple component carriers is configured for communication at a UE; receiving an uplink message associated with a second transmit power during a transmit opportunity via a first component carrier in the set of multiple component carriers; and receiving a power headroom report including a carrier aggregation power headroom parameter via at least the first component carrier in the set of multiple component carriers, wherein the value of the carrier aggregation power headroom parameter is based on a first transmit power available for uplink transmission by the UE across the set of multiple component carriers during the transmit opportunity and the second transmit power associated with uplink carrier aggregation transmission performed at least via the first component carrier during the transmit opportunity.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the value of the carrier aggregation power headroom parameter may be based on a difference between the first transmit power available across the set of multiple component carriers and the second transmit power associated with the uplink message received via the first component carrier.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the power headroom report may include operations, features, components, or instructions for performing the following actions: receiving the carrier aggregation power headroom parameter and a second power headroom parameter via the power headroom report, wherein the value of the second power headroom parameter may be based on a difference between a third transmit power available for uplink transmission on the first component carrier and the second transmit power.

[0031] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving a second uplink message via a second component carrier in the set of multiple component carriers; and receiving a second carrier aggregation power headroom parameter via the second uplink message, wherein a value of the second carrier aggregation power headroom parameter indicates a second difference between the first transmit power available across the set of multiple component carriers and a third transmit power associated with the second component carrier.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the value of the carrier aggregation power headroom parameter indicates a difference between the first transmit power available across the set of multiple component carriers and a second transmit power available for uplink transmission via the first component carrier.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the value of the carrier aggregation power headroom parameter indicates the first transmit power available across the set of multiple component carriers during the transmit opportunity.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: receiving one or more uplink messages including at least the uplink message, each of the one or more uplink messages being received via a corresponding component carrier in the set of multiple component carriers and being associated with a corresponding second transmit power, wherein the value of the carrier aggregation power headroom parameter may be based on a difference between the first transmit power available across the set of multiple component carriers and the sum of the corresponding second transmit powers associated with each of the one or more uplink messages.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following actions: sending a control message allocating a set of uplink channel resources for a carrier aggregation power headroom report, wherein the power headroom report can be received via the uplink channel resource set based on the control message.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the power headroom report may include operations, features, components, or instructions for performing the following actions: receiving the power headroom report via the first component carrier and the first cell, wherein the first component carrier and the first cell may be configured for carrier aggregation power headroom reporting.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the power headroom report may include operations, features, components, or instructions for performing the following actions: receiving the power headroom report based on the expiration of a power headroom reporting timer, wherein the power headroom reporting timer includes a periodic timer, a prohibit timer, or both configured for power headroom reporting. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 An example of a wireless communication system supporting power headroom reporting for uplink carrier aggregation communications in accordance with one or more aspects of the present disclosure is illustrated.

[0039] Figure 2 An example of a network architecture supporting power headroom reporting for uplink carrier aggregation communications in accordance with one or more aspects of the present disclosure is illustrated.

[0040] Figure 3 An example of a wireless communication system supporting power headroom reporting for uplink carrier aggregation communications in accordance with one or more aspects of the present disclosure is illustrated.

[0041] Figure 4 An example of a power headroom reporting configuration that supports power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is illustrated.

[0042] Figure 5 An example of a power headroom reporting configuration that supports power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is illustrated.

[0043] Figure 6 An example of a process flow to support power headroom reporting for uplink carrier aggregation communications in accordance with one or more aspects of the present disclosure is illustrated.

[0044] Figure 7and Figure 8 A block diagram of an apparatus supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is shown.

[0045] Fig. 9 A block diagram of a communications manager supporting power headroom reporting for uplink carrier aggregation communications is shown in accordance with one or more aspects of the present disclosure.

[0046] Fig.10 A diagram of a system including a device supporting power headroom reporting for uplink carrier aggregation communications is shown in accordance with one or more aspects of the present disclosure.

[0047] Fig.11 and Fig.12 A block diagram of an apparatus supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is shown.

[0048] Fig.13 A block diagram of a communications manager supporting power headroom reporting for uplink carrier aggregation communications is shown in accordance with one or more aspects of the present disclosure.

[0049] Fig.14 A diagram of a system including a device supporting power headroom reporting for uplink carrier aggregation communications is shown in accordance with one or more aspects of the present disclosure.

[0050] Figures 15 to 20 A flow chart illustrating a method of supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0051] In some systems, a user equipment (UE) may report a power headroom associated with the amount of power available for uplink transmission by the UE. A network entity may schedule communications with the UE based on the reported power headroom. The power headroom report may indicate the amount of power available for transmission by the UE on a given component carrier, the difference between the amount of power available on the component carrier and the amount of power currently used by the UE for transmission on the carrier, or both. Some UEs may support uplink carrier aggregation communications (e.g., communications via multiple component carriers). Such UEs may determine or calculate the total amount of power available at the respective UE for transmission across all configured component carriers. Signaling for indicating the total amount of transmit power may improve coordination between the UE and the network entity and improve throughput and reliability of uplink communications.

[0052] The techniques, systems, and devices described herein allow a UE to send one or more power headroom reports indicating a carrier aggregation transmit power, which may correspond to a maximum power level at which the UE is able to transmit across multiple component carriers configured for the UE at a given time (e.g., within a given transmit opportunity during uplink carrier aggregation communications). The UE may determine the maximum power level that can be output by the UE across multiple component carriers in a given transmit opportunity based on one or more parameters. In some aspects, the UE may transmit a power headroom report via each component carrier on which the UE sends uplink communications, and the per-carrier power headroom report may include one or more fields configured to indicate the carrier aggregation transmit power. For example, each per-carrier power headroom report may each include a field for indicating a maximum power level available across multiple configured component carriers. Additionally or alternatively, each per-carrier power headroom report may each include a field for indicating the headroom between a current transmit level on the corresponding carrier and a maximum power level available across multiple carriers.

[0053] In some other aspects, the UE may indicate the carrier aggregation transmit power via a single power headroom report sent on a first component carrier of a plurality of component carriers configured for communication at the UE. In some aspects described herein, the single power headroom report may be referred to as a carrier aggregation power headroom report. The carrier aggregation power headroom report may include one or more fields configured to indicate a maximum transmit power level available across the plurality of component carriers. Additionally or alternatively, the carrier aggregation power headroom report may include one or more fields configured to indicate a difference or headroom between the maximum transmit power level and a sum of transmit power levels used by the UE for transmission across the plurality of component carriers.

[0054] The UE may send the carrier aggregation power headroom report via the uplink resources allocated for the carrier aggregation power headroom report, via the granted uplink resources available after the configured time period expires, or both. The time period may be based on a timer (e.g., a periodic timer, a prohibition timer, or both) configured for uplink carrier aggregation power headroom reporting. Additionally or alternatively, the UE may reuse one or more timers configured for per-carrier power headroom reporting to determine the time period. A UE as described herein may thereby indicate the total amount of transmit power available for uplink transmission by the UE across multiple configured component carriers.

[0055] Aspects of the present disclosure are first described in the context of a wireless communication system. Additional aspects are described with reference to network architecture, power headroom reporting configurations, and process flows. Aspects of the present disclosure are further illustrated by apparatus diagrams, system diagrams, and flow diagrams relating to power headroom reporting for uplink carrier aggregation communications, and are described with reference to these diagrams.

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

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

[0058] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices such as Figure 1 Other UEs 115 or network entities 105 are shown communicating.

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

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

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

[0062] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

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

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

[0065] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. An IAB host may facilitate a connection between a core network 130 and an 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. An IAB host may include a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB host and the IAB node 104 may communicate via an F1 interface according to a protocol defining a signaling message (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CU 160 associated with an alternative IAB host) via an Xn-C interface (which may be an example of a portion of a backhaul link).

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

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

[0068] Where the techniques described herein are applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support power headroom reporting for uplink carrier aggregation communications as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

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

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

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

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

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

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

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

[0076] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

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

[0078] 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, the frame may be divided into subframes (e.g., in the time domain), 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 in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of 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., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

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

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

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

[0082] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to a UE 115 that has a service subscription with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) than a macro cell, and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 that has a service subscription with a network provider, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

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

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

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

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

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

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

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

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

[0091] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about 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 may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

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

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

[0094] The 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 technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly such as an antenna tower. In some examples, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0095] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technique may be referred to as spatial multiplexing. The multiple signals may be sent, 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 for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

[0096] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

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

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

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

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

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

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

[0103] In some aspects, the UE 115 may be configured to report power headroom. For example, the network entity 105 may send RRC signaling or some other type of control signaling that indicates a set of parameters for power headroom reporting. In some aspects, the power headroom reporting configuration may be indicated via an IE in the control signaling and configured across a set of one or more cells (e.g., indicated via a MAC-CellGroupConfig IE or some other IE). The parameters for power headroom reporting indicated via the power headroom reporting configuration (e.g., phr-Config) may include one or more timers for power headroom reporting, a threshold change in a power factor of a parameter for triggering PHR report transmission (e.g., phr-Tx-PowerFactorChange), an indication of the format or number of fields in the power headroom report (e.g., multiplePHR), a type of power headroom report (e.g., phr-Type2OtherCell), a mode of power headroom reporting (e.g., phr-ModeOtherCG), a configuration for maximum permitted exposure (MPE) reporting (e.g., mpe-Reporting-FR2-r16), one or more other parameters, or any combination thereof. The timers for power headroom reporting may include a periodic timer (e.g., phr-PeriodicTimer) indicating a periodicity at which the UE 115 may send power headroom reports, a prohibit timer (e.g., phr-ProhibitTimer) indicating a duration after which the UE 115 may refrain from sending power headroom reports, or both. The configuration for MPE reporting may indicate a timer (eg, mpe-ProhibitTimer-r16), a threshold for MPE reporting, or both.

[0104] A UE 115 receiving a power headroom reporting configuration may send one or more power headroom reports to a network entity 105 according to the parameters indicated via the power headroom reporting configuration. Each power headroom report may be sent via a MAC-CE or some other uplink message. In some cases, the power headroom MAC-CE may include multiple fields for indicating power headroom parameters. The headroom field in the power headroom MAC-CE may include a first number of bits (e.g., six bits or some other number of bits) for indicating the power headroom of a given component carrier. In some aspects, Table 1 includes example values ​​of power headroom levels that may be indicated via the headroom field (e.g., a range of 64 power headroom levels), and Table 2 includes an example mapping between values ​​reported via the power headroom MAC-CE and a measurement of power headroom in decibels (dB).

[0105] Power Headroom Power headroom level 0 POWER_HEADROOM_0 1 POWER_HEADROOM_1 2 POWER_HEADROOM_2 3 POWER_HEADROOM_3 ... ... 60 POWER_HEADROOM_60 61 POWER_HEADROOM_61 62 POWER_HEADROOM_62 63 POWER_HEADROOM_63

[0106] Table 1: Power headroom levels for power headroom reporting

[0107]

[0108]

[0109] Table 2: Power Headroom Report Mapping

[0110] A second field in the Power Headroom MAC-CE may include a number of bits (e.g., six bits or some other number of bits) configured to indicate the amount of power available for transmission by UE 115 on a given component carrier and a given serving cell, which may be determined by a parameter P CMAX,f,c , where f may correspond to (eg, point to) a carrier and c may correspond to (eg, point to) a serving cell. CMAX,f,c It can be relatively fine-grained information. For example, in some cases, P CMAX,f,c may be the finest granular information (e.g., 1 dB resolution) that UE 115 may provide to network entity 105 regarding the amount of available transmit power at UE 115. In some aspects, Table 3 includes P in the second field that may be included in the Power Headroom MAC-CE. CMAX,f,c , and Table 4 includes example values ​​of P in the power headroom MAC-CE CMAX,f,c The value reported in the field is the same as the P value in decibels per milliwatt (dBm). CMAX,f,c Example mapping between measurements of .

[0111] <![CDATA[P CMAX,f,c ]]> Nominal UE transmit power level 0 PCMAX_C_00 1 PCMAX_C_01 2 PCMAX_C_02 ... ... 61 PCMAX_C_61 62 PCMAX_C_62 63 PCMAX_C_63

[0112] Table 3: Nominal UE transmit power levels for power headroom reporting

[0113] Reported Value Measured value unit PCMAX_C_00 <![CDATA[P CMAX,f,c <-29]]> dBm PCMAX_C_01 <![CDATA[-29≤P CMAX,f,c <-28]]> dBm PCMAX_C_02 <![CDATA[-28≤P CMAX,f,c <-27]]> dBm ... ... ... PCMAX_C_61 <![CDATA[-31≤P CMAX,f,c <-32]]> dBm PCMAX_C_62 <![CDATA[-32≤P CMAX,f,c <-33]]> dBm PCMAX_C_63 <![CDATA[-33≤P CMAX,f,c ]]> dBm

[0114] Table 4: P CMAX,f,c Mapping

[0115] UE 115 may set P within the following limits: CMAX,f,c The value of (e.g., the maximum output power configured for a given carrier f and serving cell c): P CMAX L,f,c ≤P CMAX.f,c ≤P CMAX H,f,c , where P CMAX L,f,c and P CMAX H,f,c The maximum transmit power (e.g., P) configured by the network entity 105 for the UE 115 may be determined by the UE 115 based on one or more defined parameters. The parameters may include, for example, a maximum transmit power (e.g., P) configured by the network entity 105 for the UE 115. EMAX ), the maximum transmit power configured by the network entity 105 for the UE 115 in a given serving cell c (e.g., P EMAX,c), a maximum power determined based on the power class of UE 115 (e.g., P PowerClass ), a change or increment in maximum power associated with the power class of UE 115 (eg, ΔP PowerClass ), a maximum power reduction (MPR) parameter, one or more other parameters configured for UE 115, or any combination thereof.

[0116] UE 115 can be based on P CMAX,f,c The value of and determines the transmit power to be used for transmitting uplink transmissions (e.g., physical uplink shared channel (PUSCH) transmissions) in the active uplink bandwidth part (BWP) b in component carrier f and serving cell c according to Formula 1 below.

[0117]

[0118] In the example of Formula 1, j may correspond to a parameter set index, l may correspond to a PUSCH power control adjustment state index, and i may correspond to a transmission opportunity index. CMAX,f,c The maximum power level that UE 115 can use to send uplink transmissions in a given transmission opportunity is determined by the value of .

[0119] The power headroom field in the power headroom report sent by UE 115 may indicate the maximum power per carrier, P CMAX,f,c and the transmit power P used by UE 115 on a given carrier PUSCH,b,f,c (i,j,q d ,I). For example, for each component carrier, the power headroom field can be based on Formula 2.

[0120] PH(i,j,q d ,l)=P CMAXf,c -P PUSCH,b,f,c (i,j,q d ,l) Formula (2)

[0121] The P field in the MAC-CE may indicate whether MPE information is being reported by the UE 115. If the P field is set to 1 and MPE reporting is configured via a power headroom reporting configuration for the UE 115, the UE 115 may indicate the applied power backoff (e.g., power management MPR (P-MPR) level) to meet one or more MPE requirements for the UE 115 via the MPE field in the power headroom report. If the P field is not set to 1, if MPE reporting is not configured in the power headroom reporting configuration, if the UE 115 operates in a frequency band that does not support MPE reporting (e.g., frequency range 1 (FR1)), or any combination thereof, the MPE field may be a reserved field, which may be empty or a null value (e.g., the R bit may be present). Table 5 includes example values ​​for the MPE field in the power headroom MAC-CE.

[0122] MPE Nominal UE transmit power level 0 P+MPR_00 1 P+MPR_01 2 P+MPR_02 3 P+MPR_03

[0123] Table 5: Effective power reduction of MPE P-MPR

[0124] The MAC entity at the UE 115 may set the P field based on the P-MPR level applied to meet the MPE requirement. For example, if the applied P-MPR value is less than a threshold value (e.g., P-MPR_00), the UE 115 may set the P field to 0. If the applied P-MPR value is greater than or the same as the threshold value, the UE 115 may set the P field to 1 and report the P-MPR value via the MPE field. If MPE reporting is not configured in the power headroom reporting configuration, or if the UE 115 operates in a frequency band that does not support MPE reporting (e.g., FR1), the P field may indicate whether power backoff is applied for power management. If the power backoff applied for power management affects P CMAX,f,c field, the P field may be set to 1. The P field may otherwise be set to 0.

[0125] The UE 115 may thus receive a power headroom reporting configuration including one or more parameters for a power headroom report, and the UE 115 may send one or more power headroom reports, each of which includes one or more bit fields to convey power headroom measurements or parameters, such as the examples illustrated in Tables 1-5. Each power headroom report may indicate a headroom parameter for a corresponding component carrier. For example, P, power headroom, MPE, and P CMAX,f,c The bit value in each of the fields may be associated with communication on a single component carrier. In such a case, UE 115 may send a power headroom report via each component carrier configured for communication at UE 115.

[0126] Additionally or alternatively, the UE 115 may generate and send a power headroom report that reports the power headrooms of more than two component carriers. For example, a combined power headroom report may include separate fields for reporting per-carrier power headroom information. An example combined power headroom report is shown in Table 6, which includes a bitmap to indicate which component carrier power headroom is being reported (using C1 to C7); an indication of whether power backoff is being applied (using the P field); an indication of whether the corresponding power headroom report is real or virtual (using the V field); a reserved field represented by the R field; and a power headroom report.

[0127]

[0128] Table 6: Multi-entry Power Headroom MAC-CE

[0129] In some aspects described herein, UE 115 may support uplink carrier aggregation communications. For example, UE 115 may be configured to communicate via multiple uplink component carriers. In such cases, UE 115 may determine the total maximum output power P for a given frequency band combination. CMAX and the maximum output power P of a given service cell CMAX,c The total maximum output power may correspond to the total power used to transmit across all component carriers supported by UE 115 in a given band combination. The total output power across component carriers may be set by UE 115 within the following bounds: CMAX_L ≤P CMAX ≤P CMAX_H , where P CMAX_L and P CMAX_H The maximum transmit power (e.g., P) configured by the network entity 105 for carrier aggregation communications by the UE 115 may be based on one or more power parameters, such as a maximum transmit power (e.g., P) configured by the network entity 105 for carrier aggregation communications by the UE 115. EMAX,CA ), a maximum power (e.g., P ) associated with a power class configured for carrier aggregation communications by UE 115; PowerClass,CA ), a change or increment in the maximum power level (e.g., ΔP PowerClass,CA ), MPR parameters, one or more other parameters configured for UE 115, or any combination thereof). The parameters used to determine the maximum output power may differ based on whether UE 115 is configured to support intra-band contiguous carrier aggregation, intra-band non-contiguous carrier aggregation, or inter-band carrier aggregation.

[0130] In some systems, UE 115 may report power headroom on a per-carrier basis, as described with reference to Tables 1 - 5 and Equation 2, and UE 115 may not report maximum output power across multiple component carriers. In such cases, network entity 105 communicating with UE 115 may not be aware of transmit power constraints at UE 115. For example, headroom (e.g., the amount of remaining power available for communication) for maximum output power per carrier may be reported, but UE 115 may not report headroom for total maximum output power across carriers.

[0131] The techniques, systems, and devices described herein allow a UE 115 supporting uplink carrier aggregation to report an indication of a maximum output power across multiple component carriers determined by the UE 115. The UE 115 may determine a transmit power (e.g., a maximum transmit power level) available for uplink carrier aggregation transmission by the UE 115 across multiple component carriers during a transmission opportunity. The UE 115 may transmit a power headroom report via one or more component carriers in a set of component carriers configured for communication at the UE 115. The power headroom report may include a carrier aggregation power headroom parameter. The value of the carrier aggregation power headroom parameter may be based on the carrier aggregation transmit power available for uplink transmission across the multiple component carriers and a second transmit power associated with uplink carrier aggregation transmission via at least one of the component carriers during the transmission opportunity. The UE 115 may thereby report a headroom relative to the total amount of power available for uplink component carrier aggregation communication, which may improve coordination between devices, throughput, and reliability of uplink communication.

[0132] Figure 2An example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is illustrated. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communication system 100. The network architecture 200 may include one or more CUs 160-a, which may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with a core network 130-a through one or more disaggregated network entities 105 (e.g., a near RT RIC 175-b via an E2 link or a non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO framework), or both. The CU 160-a may communicate with one or more DUs 165-a via corresponding midhaul communication links 162-a (e.g., an F1 interface). The DU 165-a may communicate with one or more RUs 170-a via corresponding fronthaul communication links 168-a. The RU 170-a may be associated with a respective coverage area 110-a and may communicate with the UE 115-a via one or more communication links 125-a. In some implementations, the UE 115-a may be served by multiple RUs 170-a simultaneously.

[0133] Each of the network entities 105 of the network architecture 200 (e.g., CU 160-a, DU 165-a, RU 170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, open cloud (O-Cloud) 205, open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or send signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to an interface of the network entity 105 may be configured to communicate with one or more of the other network entities 105 via a transmission medium. For example, these network entities 105 may include a wired interface that is configured to receive signals on a wired transmission medium or to send signals to one or more of the other network entities 105 on a wired transmission medium. Additionally or alternatively, the network entity 105 may include a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals on a wireless transmission medium, or to send signals to one or more of the other network entities 105 on a wireless transmission medium, or both.

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

[0135] DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RUs 170-a. In some examples, DU 165-a may at least partially host one or more of the RLC layer, the MAC layer, and one or more aspects of the PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), which depends at least in part on functional divisions, such as those defined by the Third Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface that is configured to communicate signals with other layers hosted by DU 165-a or with control functions hosted by CU160-a.

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

[0137] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., an O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a may communicate with components configured according to a 4G RAN (e.g., via an O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0138] The non-RT RIC 175-a may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a may be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b may be configured to include logic functions that implement near real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CUs 160-a, one or more DUs 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b (e.g., via an E2 interface).

[0139] In some examples, in order to generate an AI / ML model to be deployed in the near-RT RIC 175-b, the non-RT RIC 175-a may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 175-b and may be received from a non-network data source or from a network function at the SMO 180-a or the non-RT RIC 175-a. In some examples, the non-RT RIC 175-a or the near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the non-RT RIC 175-a may monitor long-term trends and patterns of performance and employ an AI model or ML model to perform corrective actions through the SMO 180-a (e.g., via reconfiguration of O1) or via the generation of a RAN management policy (such as an A1 policy).

[0140] The network architecture 200 may support techniques for carrier aggregation power headroom reporting by one or more communication devices (e.g., UE 115). In some examples, a network entity (e.g., CU 160-a, DU 165-a, RU 170-a, etc.) may send a message (e.g., a control message) indicating a plurality of component carriers configured for carrier aggregation communications at UE 115. In some aspects, the network entity may send a control message (such as an RRC message) that configures UE 115 to support carrier aggregation power headroom reporting, allocate uplink resources, or both. In some aspects, the network entity may allocate uplink resources for carrier aggregation power headroom reporting separate from other allocated uplink resources. Additionally or alternatively, the network entity may allocate multiple sets of uplink resources and may monitor the allocated resources for any uplink transmission from UE 115, including power headroom reports. In some aspects, the network entity may indicate one or more timers or thresholds for triggering per-carrier power headroom reporting, multi-carrier power headroom reporting, or both. For example, the network entity may indicate a periodic timer, a prohibit timer, a path loss threshold, a P-MPR threshold, or any combination thereof for use by the UE 115 in determining when to send a power headroom report.

[0141] The network entity may receive one or more uplink messages from the UE 115 over at least one of the component carriers. Additionally or alternatively, the network entity may receive one or more power headroom reports from the UE 115 over at least one of the component carriers. The power headroom report may include a carrier aggregation power headroom parameter, which may correspond to a field or a set of bits in the power headroom report, the power headroom report being based in part on a transmit power available for uplink carrier aggregation communications by the UE 115 over the plurality of component carriers. The network entity may schedule uplink resources for subsequent communications with the UE 115 based on the power headroom report and the carrier aggregation power headroom parameter. For example, the network entity may determine an amount of uplink resources to allocate or a component carrier in which to allocate resources based on the carrier aggregation power headroom information.

[0142] In some examples, the aforementioned operations of the network entities (e.g., CU 160-a, DU 165-a, RU 170-a) may be performed according to the network architecture 200. For example, higher layer parameters (e.g., RRC parameters) for per-carrier power headroom reporting, carrier aggregation power headroom reporting, or both may be determined (e.g., selected, configured) by CU 160-a and communicated to DU 165-a (e.g., via midhaul communication link 162-a). In some examples, DU 165-a may generate one or more control messages based on the parameters communicated to DU 165-a from CU 160-a (e.g., via higher layer parameters). For example, DU 165-a may generate an RRC message indicating a set of parameters configured for power headroom reporting. In some aspects, DU 165-a may send a message (e.g., OTA) to one or more other communication devices (such as UE 115), or DU 165-a may, for example, communicate a signal to RU 170-a via a fronthaul communication link 168-a. In some examples, and in response to obtaining a message generated by DU 165-a, RU 170-a may send the message (e.g., OTA) to one or more other communication devices (e.g., one or more UE 115) via communication link 125-a. The power headroom report may be received by RU 170-a, DU 165-a, or both. The power headroom report information may be communicated to DU 165-a, CU 160-a, or both for processing. DU 165-a, CU 160-a, or both may perform resource allocation and scheduling procedures based on the power headroom report information. Such techniques may result in improved reliability of uplink wireless communications between one or more UE 115 and the network.

[0143] Figure 3An example of a wireless communication system 300 supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is illustrated. The wireless communication system 300 may implement reference Figure 1 and Figure 2 Aspects of the wireless communication system 100 and network architecture 200 described herein may be implemented by or in accordance with aspects of the wireless communication system and network architecture. For example, the wireless communication system 300 illustrates a network entity 105-a and a UE 115-b, which may represent a wireless communication system 105-a and a UE 115-b, which may represent a wireless communication system 105-b ... Figure 1 and Figure 2 Examples of corresponding devices described. The network entity 105-a and the UE 115-b may support carrier aggregation communications. For example, the network entity 105-a and the UE 115-b may communicate with each other via one or more component carriers 325 and one or more corresponding cells 310.

[0144] In some aspects, the network entity 105-a may send a control message 315 to the UE 115-b to indicate that the plurality of component carriers 325 are configured for communication at the UE 115-b (e.g., uplink carrier aggregation communication). The control message 315 may indicate, configure, or activate Figure 3 Component carriers 325-a through 325-N are shown. Figure 3 A single cell 310 is illustrated in FIG. 1 , but it should be understood that in some aspects, each component carrier 325 may correspond to a corresponding serving cell 310 (e.g., a primary cell (PCell), a secondary cell (SCell), a primary secondary cell (PSCell), or other cell types). For different component carriers 325, the coverage area of ​​the serving cell 310 may be different due to one or more parameters associated with the component carrier 325 (such as path loss).

[0145] As reference Figure 1 As described, some systems may support per-carrier power headroom reporting. For example, UE 115 may report a power headroom value that indicates the amount or level of output power currently used by UE 115 for transmission via a given component carrier 325 and the total amount or level of output power available for transmission by UE 115 via component carrier 325 (e.g., P CMAX,f,c ) headroom or difference between the carrier aggregation power and the carrier aggregation power. However, in such cases, the network entity 105 communicating with the UE 115 may not know how much total transmit power is available at the UE 115 for carrier aggregation communications. Additionally or alternatively, the network entity 105 may not know the amount of power (e.g., P) available for transmission via a given component carrier. CMAX,f,c ) and the total amount of power available across all component carriers (e.g., P CMAX ) between them.

[0146] Techniques, systems, and devices described herein support power headroom reporting for carrier aggregation communications. For example, UE 115-b may send one or more carrier aggregation power headroom reports 320 that indicate an amount of transmit power available for communication by UE 115-b across multiple component carriers 325-a through 325-N that are configured for carrier aggregation communications at UE 115-b. In some aspects, the transmit power amount may be referred to herein as a maximum output power or carrier aggregation transmit power level (e.g., P) for carrier aggregation. CMAX ). UE 115-b may determine the carrier aggregation transmit power level based on an upper limit and a lower limit, where the upper limit and the lower limit may be based on one or more parameters, such as reference Figure 1 Thus, before the network entity 105 - a receives the carrier aggregation power headroom report 320 , the network entity 105 - a may not know the carrier aggregation transmit power level of the UE 115 - b.

[0147] The carrier aggregation power headroom report 320 may include one or more fields or parameters configured to indicate a headroom or gap (e.g., to P) relative to the carrier aggregation transmit power level across all component carriers 325. CMAX 325-N), indicating a carrier aggregation transmit power level across all component carriers 325, or both. In some aspects, the carrier aggregation transmit power level may correspond to a given transmit opportunity (e.g., a time slot, one or more symbols, or some other time period for transmission by UE 115-b). For example, the carrier aggregation transmit power level may be the maximum amount of power that UE 115-b may use to transmit across component carriers 325-a through 325-N during a given transmit opportunity. In some aspects, the carrier aggregation transmit power level may be associated with a frequency band combination, or may be associated with a given cell and multiple component carriers 325 (e.g., P CMAX,c ) is associated with.

[0148] UE 115-b may combine carrier aggregation power headroom reporting with per-carrier power headroom reporting, or UE 115-b may perform carrier aggregation power headroom reporting alone. In some aspects, UE 115-b may send a power headroom report 320 via each component carrier 325 on which UE 115-a transmits. For example, if UE 115-b sends at least one uplink message via component carrier 325-a and component carrier 325-N, UE 115-b may send a power headroom report 320-a to indicate the power headroom of component carrier 325-a, and send a power headroom report 320-b to indicate the power headroom of component carrier 325-N. In some aspects described herein, per-carrier power headroom report 320 may include one or more fields for carrier aggregation power headroom reporting. Thus, UE 115-b may send per-carrier power headroom information and multi-carrier power headroom information via each power headroom report 320.

[0149] The multi-carrier power headroom information may be an indication of the carrier aggregation transmit power level available across multiple component carriers 325 (eg, UE 115-b may report P CMAX (i), where i may correspond to a transmission occasion). Additionally or alternatively, the multi-carrier power headroom information may be a difference between a carrier aggregation transmission power level and a second transmission power associated with transmission by UE 115-b via a corresponding component carrier 325.

[0150] refer to Figure 3 , UE 115-b may send one or more uplink messages to network entity 105-a via component carrier 325-a and component carrier 325-N (e.g., and one or more other component carriers 325). UE 115-b may send, via a power headroom report 320-a on component carrier 325-a, a difference between a carrier aggregation transmit power level (e.g., PCMAX(i)) and a second transmit power level associated with one or more uplink messages sent via component carrier 325-a during the transmit opportunity. In some aspects, power headroom report 320-a may additionally include per-carrier headroom information, such as an amount of transmit power (e.g., PMAX(i)) available for transmission by UE 115-b via component carrier 325-a and cell 310. CMAX,f,c ) and the difference between the second transmit power.

[0151] UE 115-b may similarly transmit, via a power headroom report 320-b on component carrier 325-N, a difference between the carrier aggregation transmit power level and a third transmit power level associated with transmissions on component carrier 325-N during the same transmit opportunity, and a difference between the available transmit power on component carrier 325-N and cell 310 and the third transmit power. Example configurations of power headroom reports 320 that support indicating multi-carrier power headroom information and per-carrier power headroom information are described elsewhere herein (including reference 1 to FIG. 1 ). Figure 4 ) is described in further detail.

[0152] In some other aspects, the UE 115-b may send the carrier aggregation power headroom report 320 separately from (e.g., in addition to or instead of) one or more per-carrier power headroom reports 320. Figure 3 , UE 115-b may send a power headroom report 320-b via component carrier 325-N to indicate per-carrier power headroom information associated with component carrier 325-N (e.g., P relative to CC_N). CMAX,f,c ), and UE 115-b may send a power headroom report 320-c via component carrier 325-a to indicate per-carrier power headroom information associated with component carrier 325-a (e.g., relative to P of CC_1). CMAX,f,c ). The UE 115-b may additionally send a separate carrier aggregation power headroom report 320-a via the component carrier 325-a to indicate multi-carrier power headroom information. For example, the carrier aggregation power headroom report 320-a may include one or more fields to indicate a carrier aggregation transmit power level determined by the UE 115-b, or to indicate a difference between the carrier aggregation transmit power level and a sum of second transmit power levels used by the UE 115-b for uplink transmissions across multiple component carriers 325-a to 325-N, or both. Example configurations of the power headroom report 320 that support indicating multi-carrier power headroom information are described elsewhere herein (including references to ). Figure 5 ) is described in further detail.

[0153] The network entity 105-a may indicate one or more timers for use by the UE 115-b for uplink power headroom reporting, as described with reference to Figure 1described. For example, the network entity 105-a may send a power headroom report configuration that indicates a periodic timer, a prohibit timer, or both for power headroom reporting. In some aspects described herein, a timer may be configured for per-carrier power headroom reporting (e.g., configured by cell group), and the UE 115-b may reuse the configured timer for carrier aggregation power headroom reporting. For example, the UE 115-b may start a prohibit timer after sending a power headroom report 320 (e.g., a per-carrier report or a carrier aggregation report), and the UE 115-b may avoid sending the carrier aggregation power headroom report 320 until the prohibit timer expires. Additionally or alternatively, the UE 115-b may periodically send the carrier aggregation power headroom report 320 according to a periodic timer.

[0154] In some other aspects, the network entity 105-a may indicate a first prohibit timer, a first periodic timer, or both for per-carrier power headroom reporting, and the network entity 105-a may indicate a second prohibit timer, a second periodic timer, or both for carrier aggregation power headroom reporting (e.g., the network entity 105-a may set a dedicated periodicity for uplink carrier aggregation power headroom reporting). If the network entity 105-a configures a carrier aggregation prohibit timer, the UE 115-b may refrain from sending the second carrier aggregation power headroom report 320 until the prohibit timer expires, which may be started after sending the first carrier aggregation power headroom report 320. Additionally or alternatively, if the network entity 105-a configures a carrier aggregation periodicity or a periodic timer, the UE 115-b may periodically send the carrier aggregation power headroom report 320 according to the configured carrier aggregation periodicity. The UE 115-b may send the per-carrier power headroom report 320 according to the configured per-carrier periodic timer, the per-carrier prohibit timer, or both.

[0155] The UE 115-b may send the power headroom report 320 via the granted uplink resources in each respective component carrier 325. In some aspects, the UE 115-b may receive an uplink grant (e.g., a PUSCH grant) for the power headroom report from the network entity 105-a. The UE 115-b may send the power headroom report 320 via the resources indicated by the uplink grant. In some other aspects, the network entity 105-a may send an uplink grant that grants the resources for the UE 115-b to use for uplink transmissions. The UE 115-b may send the power headroom report 320 via the resources granted for uplink transmissions. For example, the UE 115-b may append bits of the power headroom report 320 to data bits of the uplink transmission.

[0156] In some aspects, the network entity 105-a may assign or allocate a set of uplink resources (e.g., PUSCH resources) for sending an uplink carrier aggregation power headroom report by the UE 115-b. The allocated resources may be different from (e.g., non-overlapping or partially overlapping) the resources allocated for per-carrier power headroom reporting by the UE 115-b. Additionally or alternatively, the UE 115-b may determine that at least one of the component carriers 325 or the corresponding cell 310 is configured for uplink carrier aggregation reporting, and the UE 115-b may send an uplink carrier aggregation power headroom report 320 via at least one component carrier 325 and the corresponding cell 310 (e.g., in addition to or as a substitute for a per-carrier power headroom report 320 on at least one component carrier 325). The UE 115 - b may receive control signaling or some other indication from the network entity 105 - a indicating the component carrier 325 , the cell 310 , or both (eg, the PCell or some other cell 310 ) configured for carrier aggregation power headroom reporting.

[0157] In some other aspects, the UE 115-b may send the carrier aggregation power headroom report 320 via a first uplink resource set allocated for power headroom reporting, the first uplink resource set being available at the earliest time after expiration of a periodic timer, a prohibit timer, or both. For example, the network entity 105-a may grant multiple uplink resource sets to the UE 115-b. The UE 115-b may identify one of the multiple granted uplink resource sets that occurs earliest in time, and the UE 115-b may send the carrier aggregation power headroom report 320 via the identified resource set, which may be within a component carrier 325. In some aspects, the UE 115-b may append the uplink carrier aggregation power headroom report 320 to the uplink transmission in the identified resource set, or the UE 115-b may send the carrier aggregation power headroom report 320 and the per-carrier power headroom report 320, or both, via the same uplink resource set.

[0158] The UE 115-b may thereby send an uplink carrier aggregation power headroom report 320 via the granted uplink resources after expiration of a prohibit timer, a periodic timer, or both. In some other aspects, the UE 115-b may send the uplink carrier aggregation power headroom report 320 based on a change in path loss of one or more carriers 325, a change in P-MPR, or both. For example, the UE 115-b may measure the path loss associated with one or more of the component carriers 325. If the UE 115-b detects that the change in path loss of at least one of the component carriers 325 (e.g., or a subset of the component carriers 325, or all of the component carriers 325) exceeds a threshold, the UE 115-b may be triggered to send the carrier aggregation power headroom report 320. Additionally or alternatively, the UE 115-b may monitor the P-MPR associated with one or more of the component carriers 325. If UE 115-b detects that a change in the P-MPR of at least one of component carriers 325 (e.g., or a subset of component carriers 325, or all component carriers 325) exceeds a threshold, UE 115-b may be triggered to send a carrier aggregation power headroom report 320.

[0159] The network entity 105-a may send control signaling (e.g., an RRC message or some other signaling) indicating thresholds for triggering carrier aggregation power headroom reporting. In some aspects, these thresholds may be indicated via a power headroom reporting configuration sent to the UE 115-b. In some aspects, these thresholds may be configured for per-carrier power headroom reporting and carrier aggregation power headroom reporting. Additionally or alternatively, the network entity 105-a may indicate separate thresholds for carrier aggregation power headroom reporting.

[0160] The UE 115-b described herein can thus report power headroom on a per-carrier basis and on a multi-carrier basis for uplink carrier aggregation communications. By indicating the headroom or gap relative to the maximum transmit power available across all component carriers 325 configured for the UE 115-b, the UE 115-b can improve coordination between the UE 115-b and the network entity 105-a, which can improve the throughput and reliability of communications.

[0161] Figure 4 An example of a power headroom reporting configuration 400 for supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is illustrated. The power headroom reporting configuration 400 may be implemented with reference to Figures 1 to 3Aspects of the wireless communication systems 100 and 300 or the network architecture 200 described herein may be implemented by or in accordance with aspects of the wireless communication systems or the network architecture. For example, the power headroom report configuration 400 illustrates an example format or configuration of a power headroom report 420, which may represent a reference Figure 3 An example of a power headroom report 320 is described. A power headroom report 420 may be sent by a UE 115 to a network entity 105, and the UE and the network entity may represent the example of a power headroom report 320 as described in reference to FIG. Figures 1 to 3 Examples of corresponding devices described. In this example, the power headroom report 420 can be configured to convey per-carrier power headroom information and multi-carrier power headroom information.

[0162] As reference Figures 1 to 3 As described, the UE 115 may send a power headroom report 420 via one or more component carriers on which the UE 115 communicates. The power headroom report 420 may be sent via a MAC-CE (e.g., configuration of a PUSCH bit within a control element) or some other signaling. The power headroom report 420 may include a first set of fields 405 for indicating per-carrier power headroom information, such as a P field, an R field, an MPE field, a power headroom field, and a P field. CMAX,f,c Fields. Such fields are described elsewhere in this document (including references to Figure 1 and Tables 1 to 5) are further described in detail.

[0163] As described herein, the per-carrier power headroom report 420 may be extended to include a second set of fields 410 for carrier aggregation power headroom reporting. For example, the second set of fields 410 may include a P field, an R (e.g., reserved) field, an MPE or R field, a power headroom field, a P ... CMAX field or any combination thereof. Therefore, in addition to indicating the transmit power level P based on each carrier CMAX,f,c In addition to the headroom per carrier, the power headroom report 420 may also indicate a carrier aggregation power headroom parameter, which may be based on the carrier aggregation transmit power level P CMAX .

[0164] In some aspects, a carrier aggregation power headroom field (e.g., PH (type, CA)) in the power headroom report 420 may indicate a carrier aggregation power headroom parameter. The value in the power headroom field may be based on a carrier aggregation transmit power level, based on a second transmit power level associated with uplink transmissions via at least one component carrier, or both.

[0165] For example, the carrier aggregation power headroom field may indicate a difference between the carrier aggregation transmit power level and a second transmit power level associated with an uplink transmission by the UE 115 on the corresponding component carrier via which the power headroom report 420 is being transmitted. The UE 115 may determine a transmit power level for transmitting an uplink transmission on a given component carrier based on Formula 1, as described with reference to Figure 1 Thus, according to Formula 3, the power headroom field may indicate the difference between the carrier aggregation transmit power level determined by UE 115 and the transmit power level of a given component carrier.

[0166] PH type,X,b,f,c (i,j,q d ,l)=P CMAX (i)-P PUSCH,b,f,c (i,j,q d ,l) Formula (3)

[0167] In the example of Formula 3, j may correspond to a parameter set index, l may correspond to a PUSCH power control adjustment state index, and i may correspond to a transmission opportunity index. Figure 1 The formula 1 described here determines P PUSCH,b,f,c (i,j,q d In some aspects, the type of power headroom report (e.g., PH typeX ), and UE 115 may indicate this type via the power headroom field.

[0168] Additionally or alternatively, according to Formula 4, the power headroom field may indicate a difference between the carrier aggregation transmit power level and a maximum transmit power available for transmission via the component carrier associated with the power headroom report 420 .

[0169] PH type,X,b,f,c (i,j,q d ,l)=P CMAX (i)-P CMAX,f,c (i) Formula (4)

[0170] In some other aspects, the power headroom field may indicate the carrier aggregation transmit power level (eg, P CMAX (i)). Additionally or alternatively, the P in the power headroom report 420 CMAX The field may indicate the carrier aggregation transmit power level for a given transmit opportunity.

[0171] In some aspects, the power headroom report 420 may include a first MPE field for per-carrier MPE reporting and a second MPE field for indicating a carrier aggregation MPE. The UE 115 may indicate, via the carrier aggregation MPE field, the maximum transmit power level (e.g., P) that may be applied by the UE 115 to meet (e.g., remain below) the maximum transmit power level (e.g., P) across component carriers. CMAX In such cases, the per-carrier MPE field may indicate the amount of backoff applied per carrier, and the carrier aggregate MPE field may indicate the sum of the per-carrier power backoff levels.

[0172] Despite Figure 4 The second field set 410 shown includes five fields, but it should be understood that the number of fields and the format of the fields used for carrier aggregation power headroom reporting in the second field set 410 may vary. For example, the second field set 410 may not include one or more of the illustrated fields, or may include Figure 4 Additionally or alternatively, the field may include any number of bits. In some aspects, the second field set 410 may include a carrier aggregation MPE field and a P CMAX The second field set 410 may include a P, R, or power headroom field. Additionally or alternatively, the second field set 410 may include a P CMAX and power headroom fields, or may include one of these fields or any other combination of these fields.

[0173] The UE 115 may send a per-carrier power headroom report 420 via a set of uplink resources on a corresponding component carrier. The set of uplink resources may be indicated via an uplink grant sent by the network entity 105. The UE 115 may send a respective per-carrier power headroom report 420 via each component carrier that the UE 115 uses for uplink transmission. Thus, each per-carrier power headroom report 420 may indicate carrier aggregate power headroom information. The UE 115 may be configured with a periodic timer, a prohibit timer, or both for reporting power headroom, as described with reference to FIG. Figure 2 Additionally or alternatively, UE 115 may send per-carrier power headroom report 420 based on a measured path loss associated with one or more component carriers exceeding a threshold, a measured P-MPR associated with one or more component carriers exceeding a threshold, or both.

[0174] As described herein, the UE 115 may thus send a per-carrier power headroom report 420 via a single uplink message (e.g., a set of bits) to indicate a first power amount that the UE 115 can use to send uplink messages across multiple component carriers within a transmission opportunity and a second power amount that the UE 115 can use to send uplink messages via a single component carrier within a transmission opportunity. The per-carrier power headroom report 420 may indicate the first power amount via a carrier aggregation power headroom parameter. The UE 115 may directly indicate the first power amount and the second power amount, or the UE 115 may report a corresponding gap or headroom relative to the first power amount and the second power amount according to the power amount currently used per carrier, or both.

[0175] Figure 5 An example of a power headroom reporting configuration 500 for supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is illustrated. The power headroom reporting configuration 500 may be implemented with reference to Figures 1 to 3 Aspects of the wireless communication systems 100 and 300 or network architecture 200 described herein may be implemented by aspects of the wireless communication systems or network architectures. For example, the power headroom report configuration 500 illustrates an example format or configuration of a power headroom report 520, which may represent a reference Figure 3 An example of a power headroom report 320 is described. A power headroom report 520 may be sent by a UE 115 to a network entity 105, and the UE and the network entity may represent the example of a power headroom report 320 as described in reference to FIG. Figures 1 to 4 Examples of corresponding apparatus as described. In this example, the power headroom report 520 may be a carrier aggregation power headroom report 520 configured to convey multi-carrier power headroom information.

[0176] As reference Figures 1 to 4 As described, the UE 115 may send a per-carrier power headroom report via one or more component carriers over which the UE 115 communicates. The power headroom report may be sent via a MAC-CE (eg, configuration of a PUSCH bit within a control element) or some other signaling.

[0177] As described herein, a carrier aggregation power headroom report 520 may be defined or configured for UE 115 for reporting multi-carrier power headroom information. The structure or format of the carrier aggregation power headroom report 520 may be similar to that of reference 1. Figures 1 to 4 For example, the carrier aggregation power headroom report 520 may include multiple fields, such as a P field, a reserved (e.g., R) field, an MPE field, a carrier aggregation power headroom field, and a P field. CMAX Field. The carrier aggregation power headroom report 520 may be configured to indicate a carrier aggregation power headroom parameter.

[0178] In addition to one or more per-carrier power headroom reports, UE 115 may also send a carrier aggregation power headroom report 520 to separately report power headroom relative to the carrier aggregation transmit power level (e.g., P CMAX The carrier aggregation power headroom report 520 may not be associated with a specific carrier. Instead, the carrier aggregation power headroom report 520 may be associated with multiple carriers (e.g., all component carriers supported by the UE 115, or a subset of component carriers).

[0179] UE 115 can use P CMAX The carrier aggregation power headroom parameter may be indicated by the UE 115 via the P field, the power headroom field, or both. CMAX The field indicates the carrier aggregation transmit power level P CMAX . The UE 115 may indicate the headroom relative to the carrier aggregation transmit power level via the power headroom field. In some aspects, the headroom relative to the carrier aggregation transmit power level may be based on the sum of the transmit powers used by the UE 115 to transmit across multiple component carriers. The UE 115 may determine the transmit power used to transmit a given uplink message via the corresponding component carrier during a transmit opportunity according to Formula 5, which may represent the reference Figure 1 An example of Formula 1 is described.

[0180]

[0181] UE 115 may calculate the sum of all transmit powers that UE 115 has used to transmit uplink messages via multiple component carriers in a given time period or transmit opportunity i. UE 115 may calculate the difference between the carrier aggregation transmit power level and the sum of the transmit powers according to Equation 6.

[0182] PH type,X,b,f,c (i,j,q d ,l)=P CMAX (i)-∑P tx,b,f,c (i,j,q d ,l) Formula (6)

[0183] UE 115 may indicate the determined value PH via the power headroom field in carrier aggregation power headroom report 520. type,X,b,f,c (i,j,q d, 1). In some aspects, the UE 115 may not send an uplink message via each component carrier at the same time or within the same transmission opportunity. In such cases, the UE 115 may represent the transmit power levels of those carriers during the transmission opportunity as null values ​​(e.g., 0) in the summation shown in Formula 6. Additionally or alternatively, the UE 115 may utilize one or more reference power levels for a subset of component carriers via which the UE 115 does not send uplink messages.

[0184] In addition to the uplink component carrier carrying the carrier aggregation power headroom report 520, the reference power level (e.g., reference PUSCH) may be used for all uplink component carriers that do not include uplink transmissions in a given transmission opportunity. UE 115 may determine the power level based on P CMAX,f,c The transmit power level of each component carrier is calculated based on the value of, which can be based on the MPR level and the P-MPR level, as shown in reference Figure 1 Thus, if the UE 115 is not transmitting via a component carrier, the UE 115 may calculate a reference power level for the component carrier by setting one or more parameters (such as a P-MPR parameter and an MPR parameter) to zero (e.g., 0 decibels) and calculating the reference power level accordingly. When determining the carrier aggregation power headroom, the UE 115 may utilize the reference power level in the summation of the transmit power levels across the carriers. For example, in some aspects, P in Equation 6 tx,b,f,c (i,j,q d , some values ​​of l) can be reference power levels.

[0185] In some aspects, the carrier aggregation power headroom report 520 may include a P field and an MPE field. The P field and the MPE field may be similar to those described in reference Figure 1 15 and may be configured for carrier aggregation MPE reporting. For example, the P field may indicate whether carrier aggregation MPE information is being reported by the UE 115. If the P field is set to 1 and carrier aggregation MPE reporting is configured via a power headroom reporting configuration for the UE 115, the UE 115 may indicate via the MPE field in the carrier aggregation power headroom report 520 the power backoff (e.g., P-MPR level) applied to meet (e.g., remain below) the carrier aggregation transmit power level (e.g., P-MPR level) across multiple component carriers. CMAX (i)). In some aspects, the power backoff applied may correspond to the sum of the power backoffs applied per carrier.

[0186] The MPE field may be a reserved field, which may be empty or a null value (e.g., the R bit may be present) if the P field is not set to 1, if carrier aggregation MPE reporting is not configured in the power headroom reporting configuration, if UE 115 operates in a frequency band that does not support MPE reporting (e.g., frequency range 1 (FR1)), or any combination thereof.

[0187] The UE 115 may send the carrier aggregation power headroom report 520 via a first component carrier. The UE 115 may determine which component carrier to use to send the carrier aggregation power headroom report 520 based on a defined rule or a configuration indicated via control signaling. Additionally or alternatively, the UE 115 may select a component carrier that includes a set of resources granted for the carrier aggregation power headroom report. In some other aspects, the UE 115 may select a set of granted uplink resources that is available in time before other sets of granted uplink resources, and the UE 115 may send the carrier aggregation power headroom report 520 via the component carrier that includes the selected set of resources, as described in reference to Figure 2 as described.

[0188] although Figure 5 Although five fields are illustrated in FIG. 5 , it should be understood that the number of fields and the format of the fields in the carrier aggregation power headroom report 520 may vary. For example, the carrier aggregation power headroom report 520 may not include one or more of the illustrated fields, or may include Figure 5 Additional fields not illustrated in the examples of FIG. Each of these fields may include any number of bits for conveying corresponding information.

[0189] As described herein, the UE 115 may thus send a carrier aggregation power headroom report 520 via an uplink message (e.g., a set of bits) to indicate the amount of power that the UE 115 can use to send an uplink message across multiple component carriers within a transmission opportunity. The UE 115 may send other uplink messages (e.g., per-carrier power headroom reports) to indicate the available power per component carrier. By sending an indication of the carrier aggregation power headroom, the UE 115 may improve the throughput and reliability of communications with the network entity 105.

[0190] Figure 6 An example of a process flow 600 for supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is illustrated. The process flow 600 may be implemented with reference to Figures 1 to 5Aspects of the described wireless communication systems 100 and 300, network architecture 200, or power headroom reporting configurations 400 and 500 may be implemented by or in accordance with aspects of the wireless communication systems, network architectures, or power headroom reporting configurations. For example, process flow 600 illustrates communication between a UE 115-c and a network entity 105-b, which may be represented as described with reference to Figures 1 to 5 Examples of corresponding devices described. In some aspects, the UE 115-c may report the power headroom for uplink carrier aggregation communications.

[0191] In the following description of process flow 600, operations between UE 115-c and network entity 105-b may be performed in a different order or at a different time. Some operations may also be excluded from process flow 600, or other operations may be added. Although UE 115-c and network entity 105-b are shown as performing operations of process flow 600, some aspects of some operations may also be performed by one or more other wireless devices.

[0192] At 605, the network entity 105-b may send a first message to the UE 115-c. The first message may indicate that a plurality of component carriers are configured for communication at the UE 115-c (e.g., uplink carrier aggregation communication). In some aspects, the first message may be a control message. In some aspects, the network entity 105-b may send a control message (e.g., an RRC configuration) to the UE 115-c indicating a power headroom reporting configuration. The power headroom reporting configuration may include one or more parameters for power headroom reporting on a per-carrier and multi-carrier basis, such as reference Figures 1 to 5 as described.

[0193] At 610, the UE 115-c may determine a first transmit power that may be used for uplink carrier aggregation transmissions across multiple component carriers during a transmission opportunity by the UE 115-c. The UE 115-c may determine the first transmit power, which in some aspects herein may be referred to as a maximum output power (e.g., P ) for carrier aggregation communications, based on one or more configured parameters or boundaries. CMAX ), as referenced Figure 1 as well as Figures 3 to 5 as described.

[0194] At 615, in some aspects, the UE 115-c may transmit at least one uplink message associated with the second transmit power during the transmit opportunity. For example, the UE 115-c may transmit the at least one uplink message using the second transmit power. The UE 115-c may transmit the uplink message to the network entity 105-b via a first component carrier of the plurality of component carriers. In some aspects, the UE 115-c may transmit a plurality of uplink messages, each via a respective component carrier of the plurality of component carriers and each associated with a respective second transmit power.

[0195] At 620, the UE 115-c may send a power headroom report to the network entity 105-b. The UE 115-c may send the power headroom report via at least a first component carrier of a plurality of component carriers configured for communication at the UE 115-c. The power headroom report may include a carrier aggregation power headroom parameter. The value of the carrier aggregation power headroom parameter may be based on a first transmit power available across the plurality of component carriers (e.g., PCMAX) and a second transmit power associated with an uplink carrier aggregation transmission performed via at least one component carrier of the plurality of component carriers during a transmit opportunity (e.g., an uplink message).

[0196] In some aspects, the carrier aggregation power headroom parameter may indicate a difference between the first transmit power and the second transmit power. In some aspects, the second transmit power may correspond to an amount of power available for uplink transmission via the first component carrier (e.g., P CMAX,f,c ). Additionally or alternatively, the carrier aggregation power headroom parameter may indicate a difference between the first transmit power and a sum of a plurality of second transmit powers associated with uplink transmissions via more than one of the plurality of component carriers. In some other aspects, the carrier aggregation power headroom parameter may indicate the first transmit power. The carrier aggregation power headroom parameter may correspond to a field or a quantity of one or more bits in a power headroom report indicating carrier aggregation power headroom information.

[0197] In some aspects, the power headroom report may include per-carrier power headroom information, such as reference Figure 4 For example, the second power headroom parameter in the power headroom report may indicate a difference between a transmit power available for transmission on the first component carrier and a second transmit power. Additionally or alternatively, the UE 115-c may send one or more other per-carrier power headroom reports on one or more component carriers to indicate per-carrier power headroom information, such as reference Figure 5 as described.

[0198] UE 115-c may thereby report power headrooms across multiple component carriers to network entity 105-b. Network entity 105-b may utilize the reported carrier aggregation power headrooms to schedule or perform wireless communications with UE 115-c, which may improve coordination and communication reliability between devices, among other advantages.

[0199] Figure 7 A block diagram 700 of a device 705 supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of a UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0200] The receiver 710 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to power headroom reporting for uplink carrier aggregation communications), user data, control information, or any combination thereof. The information may be communicated to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0201] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to power headroom reporting for uplink carrier aggregation communications), user data, control information, or any combination thereof. In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0202] The communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of power headroom reporting for uplink carrier aggregation communications as described herein. For example, the communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

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

[0205] In some examples, the communication manager 720 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 can receive information from the receiver 710, transmit information to the transmitter 715, or integrate with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0206] According to examples as disclosed herein, the communication manager 720 may support wireless communications at a UE. For example, the communication manager 720 may be configured to or otherwise support components for receiving a first message indicating that a set of multiple component carriers is configured for communication at the UE. The communication manager 720 may be configured to or otherwise support components for determining a first transmit power available for uplink carrier aggregation transmission by the UE across a set of multiple component carriers during a transmission opportunity. The communication manager 720 may be configured to or otherwise support components for transmitting a power headroom report including a carrier aggregation power headroom parameter via at least a first component carrier in the set of multiple component carriers, wherein the value of the carrier aggregation power headroom parameter may be based on the first transmit power available across the set of multiple component carriers during the transmission opportunity and a second transmit power associated with uplink carrier aggregation transmission via at least one component carrier in the set of multiple component carriers during the transmission opportunity.

[0207] By including or configuring a communication manager 720 according to the examples described herein, the device 705 (e.g., a processor controlling the receiver 710, the transmitter 715, the communication manager 720, or a combination thereof or otherwise coupled thereto) may support techniques for reduced processing, reduced power consumption, and more efficient use of communication resources, among other advantages.

[0208] Figure 8 A block diagram 800 of a device 805 supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of the device 705 or UE 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0209] The receiver 810 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to power headroom reporting for uplink carrier aggregation communications), user data, control information, or any combination thereof. The information may be communicated to other components of the device 805. The receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0210] The transmitter 815 may provide means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to power headroom reporting for uplink carrier aggregation communications), user data, control information, or any combination thereof. In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0211] The device 805 or its various components may be examples of components for performing various aspects of power headroom reporting for uplink carrier aggregation communications as described herein. For example, the communication manager 820 may include a carrier aggregation component 825, a carrier aggregation power component 830, a power headroom reporting component 835, or any combination thereof. The communication manager 820 may be an example of various aspects of the communication manager 720 as described herein. In some examples, the communication manager 820 or its various components may be configured to use or otherwise cooperate with the receiver 810, the transmitter 815, or both to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0212] According to examples as disclosed herein, the communication manager 820 may support wireless communications at a UE. The carrier aggregation component 825 may be configured to or otherwise support means for receiving a first message indicating that a set of multiple component carriers is configured for communication at the UE. The carrier aggregation power component 830 may be configured to or otherwise support means for determining a first transmit power available for uplink carrier aggregation transmission by the UE across a set of multiple component carriers during a transmission opportunity. The power headroom reporting component 835 may be configured to or otherwise support means for transmitting a power headroom report including a carrier aggregation power headroom parameter via at least a first component carrier in the set of multiple component carriers, wherein the value of the carrier aggregation power headroom parameter may be based on a first transmit power available across a set of multiple component carriers during a transmission opportunity and a second transmit power associated with uplink carrier aggregation transmission via at least one component carrier in the set of multiple component carriers during the transmission opportunity.

[0213] Fig. 9A block diagram 900 of a communication manager 920 supporting power headroom reporting for uplink carrier aggregation communications is shown in accordance with one or more aspects of the present disclosure. The communication manager 920 may be an example of aspects of the communication manager 720, the communication manager 820, or both as described herein. The communication manager 920 or its various components may be examples of means for performing various aspects of power headroom reporting for uplink carrier aggregation communications as described herein. For example, the communication manager 920 may include a carrier aggregation component 925, a carrier aggregation power component 930, a power headroom reporting component 935, an uplink message component 940, a multi-carrier headroom component 945, a reporting resource component 950, a reporting timing component 955, a per-carrier headroom component 960, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0214] According to examples as disclosed herein, the communication manager 920 may support wireless communications at a UE. The carrier aggregation component 925 may be configured to or otherwise support a component for receiving a first message indicating that a set of multiple component carriers is configured for communication at the UE. The carrier aggregation power component 930 may be configured to or otherwise support a component for determining a first transmit power available for uplink carrier aggregation transmission by the UE across a set of multiple component carriers during a transmission opportunity. The power headroom reporting component 935 may be configured to or otherwise support a component for transmitting a power headroom report including a carrier aggregation power headroom parameter via at least a first component carrier in the set of multiple component carriers, wherein the value of the carrier aggregation power headroom parameter may be based on a first transmit power available across a set of multiple component carriers during a transmission opportunity and a second transmit power associated with uplink carrier aggregation transmission via at least one component carrier in the set of multiple component carriers during the transmission opportunity.

[0215] In some examples, uplink message component 940 can be configured or otherwise support means for sending an uplink message via at least a first component carrier in a set of multiple component carriers, the uplink message being associated with a second transmit power. In some examples, multi-carrier headroom component 945 can be configured or otherwise support means for calculating a difference between a first transmit power and a second transmit power available across a set of multiple component carriers, wherein the value of the carrier aggregation power headroom parameter indicates the difference.

[0216] In some examples, to support transmit power headroom reporting, the per-carrier headroom component 960 may be configured as or otherwise support components for transmitting a carrier aggregation power headroom parameter and a second power headroom parameter via a power headroom report, wherein the value of the second power headroom parameter is based on a difference between a third transmit power available for uplink transmission on the first component carrier and the second transmit power.

[0217] In some examples, uplink message component 940 may be configured or otherwise support components for sending a second uplink message via a second component carrier in the set of multiple component carriers. In some examples, multi-carrier headroom component 945 may be configured or otherwise support components for calculating a second difference between a first transmit power available across the set of multiple component carriers and a third transmit power associated with the second component carrier. In some examples, multi-carrier headroom component 945 may be configured or otherwise support components for sending a second carrier aggregation power headroom parameter via a second uplink message, wherein a value of the second carrier aggregation power headroom parameter indicates the second difference.

[0218] In some examples, the multi-carrier headroom component 945 may be configured to or otherwise support components for determining a second transmit power corresponding to an amount of transmit power available for uplink transmissions on a first component carrier, wherein the value of the carrier aggregation power headroom parameter indicates a difference between the first transmit power and the second transmit power available across a set of multiple component carriers.

[0219] In some examples, the value of the carrier aggregation power headroom parameter indicates a first transmit power available for uplink carrier aggregation transmissions by the UE across a set of multiple component carriers during a transmit opportunity.

[0220] In some examples, uplink message component 940 may be configured to or otherwise support means for sending one or more uplink messages corresponding to uplink carrier aggregation transmissions, each of the one or more uplink messages being sent via a corresponding component carrier in a set of multiple component carriers and using a corresponding second transmit power. In some examples, multi-carrier headroom component 945 may be configured to or otherwise support means for calculating a difference between a first transmit power available across a set of multiple component carriers and a sum of corresponding second transmit powers used to send each of the one or more uplink messages, wherein the value of the carrier aggregation power headroom parameter indicates the difference.

[0221] In some examples, the multi-carrier headroom component 945 may be configured to or otherwise support components for calculating a sum of respective second transmit powers and one or more reference power levels associated with a subset of component carriers in a set of multiple component carriers that are different from respective component carriers via which one or more uplink messages are transmitted, wherein the one or more reference power levels are based on a reference power reduction parameter.

[0222] In some examples, the reporting resource component 950 may be configured as or otherwise support a component for receiving a control message allocating an uplink channel resource set for carrier aggregation power headroom reporting, wherein the power headroom report is sent via the uplink channel resource set based on the control message.

[0223] In some examples, to support sending power headroom reports, the reporting resource component 950 may be configured as or otherwise support components for sending power headroom reports via a first component carrier and a first cell, where the first component carrier and the first cell are configured for carrier aggregation power headroom reporting by the UE.

[0224] In some examples, to support sending a power headroom report, the report timing component 955 may be configured as or otherwise support components for sending a power headroom report based on expiration of a power headroom reporting timer, wherein the power headroom reporting timer includes a periodic timer, a prohibit timer, or both configured for power headroom reporting by the UE.

[0225] In some examples, the reporting timing component 955 can be configured to or otherwise support means for determining to send a power headroom report via a set of resources allocated for power headroom reporting on a first component carrier after expiration of a power headroom reporting timer and before other sets of resources allocated for power headroom reporting on other component carriers in a set of multiple component carriers. In some examples, the power headroom reporting timer includes a periodic timer whose periodicity is configured for carrier aggregation power headroom reporting, per-carrier power headroom reporting, or both.

[0226] In some examples, the reporting timing component 955 can be configured or otherwise support means for determining a difference between a first path loss associated with at least one component carrier in a set of a plurality of component carriers at a first time and a second path loss associated with the at least one component carrier at a second time. In some examples, the reporting timing component 955 can be configured or otherwise support means for comparing the difference to a path loss threshold, wherein the transmit power headroom report is based on the difference exceeding the path loss threshold.

[0227] In some examples, the reporting timing component 955 can be configured or otherwise support means for determining a difference between a first value of a first MPR parameter associated with at least one component carrier in a set of multiple component carriers at a first time and a second value of the first MPR parameter associated with the at least one component carrier at a second time. In some examples, the reporting timing component 955 can be configured or otherwise support means for comparing the difference to a power reduction threshold, wherein sending a power headroom report is based on the difference exceeding the power reduction threshold.

[0228] Fig.10 A diagram of a system 1000 including a device 1005 supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of a device 705, a device 805, or a UE 115 as described herein, or include a component of the device or the UE. The device 1005 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1005 may include components for two-way voice and data communications, including components for sending communications and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, a code 1035, and a processor 1040. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1045).

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

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

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

[0232] Processor 1040 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1040. Processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1030) so that device 1005 performs various functions (e.g., functions or tasks supporting power headroom reporting for uplink carrier aggregation communications). For example, device 1005 or a component of device 1005 may include processor 1040 and memory 1030 coupled to or coupled to processor 1040, and processor 1040 and memory 1030 are configured to perform the various functions described herein.

[0233] According to examples as disclosed herein, the communication manager 1020 may support wireless communications at a UE. For example, the communication manager 1020 may be configured to or otherwise support a component for receiving a first message indicating that a set of multiple component carriers is configured for communication at the UE. The communication manager 1020 may be configured to or otherwise support a component for determining a first transmit power available for uplink carrier aggregation transmission by the UE across a set of multiple component carriers during a transmission opportunity. The communication manager 1020 may be configured to or otherwise support a component for transmitting a power headroom report including a carrier aggregation power headroom parameter via at least a first component carrier in the set of multiple component carriers, wherein the value of the carrier aggregation power headroom parameter may be based on a first transmit power available across a set of multiple component carriers during the transmission opportunity and a second transmit power associated with uplink carrier aggregation transmission via at least one component carrier in the set of multiple component carriers during the transmission opportunity.

[0234] By including or configuring a communications manager 1020 according to the examples described herein, the device 1005 may support techniques for improved communications reliability, reduced latency, an improved user experience associated with reduced processing, reduced power consumption, more efficient use of communications resources, improved inter-device coordination, and longer battery life, among other advantages.

[0235] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1015, one or more antennas 1025, or any combination thereof. Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or performed by the processor 1040, the memory 1030, the code 1035, or any combination thereof. For example, the code 1035 may include instructions executable by the processor 1040 to cause the device 1005 to perform various aspects of power headroom reporting for uplink carrier aggregation communications as described herein, or the processor 1040 and the memory 1030 may be otherwise configured to perform or support such operations.

[0236] Fig.11 A block diagram 1100 of a device 1105 supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0237] The receiver 1110 may provide means for obtaining (e.g., receiving, determining, identifying) 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). The information may be communicated to other components of the device 1105. In some examples, the receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0238] The transmitter 1115 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 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, the transmitter 1115 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0239] The communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof or various components thereof may be examples of means for performing various aspects of power headroom reporting for uplink carrier aggregation communications as described herein. For example, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0240] In some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that is configured as or otherwise supports components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

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

[0242] In some examples, communication manager 1120 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated in conjunction with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0243] According to examples as disclosed herein, the communication manager 1120 may support wireless communications at a network entity. For example, the communication manager 1120 may be configured to or otherwise support components for sending a first message indicating that a set of multiple component carriers is configured for communication at a UE. The communication manager 1120 may be configured to or otherwise support components for receiving an uplink message associated with a second transmit power during a transmit opportunity via a first component carrier in the set of multiple component carriers. The communication manager 1120 may be configured to or otherwise support components for receiving a power headroom report including a carrier aggregation power headroom parameter via at least a first component carrier in the set of multiple component carriers, wherein the value of the carrier aggregation power headroom parameter may be based on a first transmit power available for uplink transmission by the UE across the set of multiple component carriers during the transmit opportunity and a second transmit power associated with uplink carrier aggregation transmission performed at least via the first component carrier during the transmit opportunity.

[0244] By including or configuring a communications manager 1120 according to the examples described herein, a device 1105 (e.g., a processor controlling a receiver 1110, a transmitter 1115, a communications manager 1120, or a combination thereof or otherwise coupled thereto) may support techniques for reduced processing, reduced power consumption, and more efficient use of communications resources, among other advantages.

[0245] Fig.12 A block diagram 1200 of a device 1205 supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of aspects of the device 1105 or network entity 105 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0246] The receiver 1210 may provide means for obtaining (e.g., receiving, determining, identifying) 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). The information may be passed to other components of the device 1205. In some examples, the receiver 1210 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1210 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0247] The transmitter 1215 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1205. For example, the transmitter 1215 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, the transmitter 1215 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1215 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1215 and the receiver 1210 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0248] The device 1205 or its various components may be examples of components for performing various aspects of power headroom reporting for uplink carrier aggregation communications as described herein. For example, the communication manager 1220 may include a carrier aggregation component 1225, an uplink message component 1230, a power headroom reporting component 1235, or any combination thereof. The communication manager 1220 may be an example of various aspects of the communication manager 1120 as described herein. In some examples, the communication manager 1220 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 1210, the transmitter 1215, or both. For example, the communication manager 1220 may receive information from the receiver 1210, transmit information to the transmitter 1215, or be integrated in combination with the receiver 1210, the transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0249] According to examples as disclosed herein, the communication manager 1220 may support wireless communications at a network entity. The carrier aggregation component 1225 may be configured to or otherwise support means for sending a first message indicating that a set of multiple component carriers is configured for communication at the UE. The uplink message component 1230 may be configured to or otherwise support means for receiving an uplink message associated with a second transmit power during a transmit opportunity via a first component carrier in the set of multiple component carriers. The power headroom reporting component 1235 may be configured to or otherwise support means for receiving a power headroom report including a carrier aggregation power headroom parameter via at least a first component carrier in the set of multiple component carriers, wherein the value of the carrier aggregation power headroom parameter may be based on a first transmit power available for uplink transmission by the UE across the set of multiple component carriers during the transmit opportunity and a second transmit power associated with uplink carrier aggregation transmissions performed at least via the first component carrier during the transmit opportunity.

[0250] Fig.13 A block diagram 1300 of a communication manager 1320 supporting power headroom reporting for uplink carrier aggregation communications in accordance with one or more aspects of the present disclosure is shown. The communication manager 1320 may be an example of aspects of the communication manager 1120, the communication manager 1220, or both as described herein. The communication manager 1320 or its various components may be examples of means for performing various aspects of power headroom reporting for uplink carrier aggregation communications as described herein. For example, the communication manager 1320 may include a carrier aggregation component 1325, an uplink message component 1330, a power headroom reporting component 1335, a multi-carrier headroom component 1340, a control message component 1345, a reporting resource component 1350, a reporting timing component 1355, a per-carrier headroom component 1360, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0251] According to examples as disclosed herein, the communication manager 1320 may support wireless communications at a network entity. The carrier aggregation component 1325 may be configured to or otherwise support components for sending a first message indicating that a set of multiple component carriers is configured for communication at the UE. The uplink message component 1330 may be configured to or otherwise support components for receiving an uplink message associated with a second transmit power during a transmit opportunity via a first component carrier in the set of multiple component carriers. The power headroom reporting component 1335 may be configured to or otherwise support components for receiving a power headroom report including a carrier aggregation power headroom parameter via at least a first component carrier in the set of multiple component carriers, wherein the value of the carrier aggregation power headroom parameter may be based on a first transmit power available for uplink transmission by the UE across the set of multiple component carriers during the transmit opportunity and a second transmit power associated with uplink carrier aggregation transmission performed at least via the first component carrier during the transmit opportunity.

[0252] In some examples, the value of the carrier aggregation power headroom parameter is based on a difference between a first transmit power available across a set of multiple component carriers and a second transmit power associated with an uplink message received via the first component carrier. In some examples, to support receiving power headroom reports, the per-carrier headroom component 1360 may be configured to or otherwise support means for receiving the carrier aggregation power headroom parameter and the second power headroom parameter via a power headroom report, wherein the value of the second power headroom parameter is based on a difference between a third transmit power available for uplink transmission on the first component carrier and the second transmit power.

[0253] In some examples, uplink message component 1330 may be configured or otherwise support means for receiving a second uplink message via a second component carrier in the set of multiple component carriers. In some examples, power headroom reporting component 1335 may be configured or otherwise support means for receiving a second carrier aggregation power headroom parameter via the second uplink message, wherein a value of the second carrier aggregation power headroom parameter indicates a second difference between a first transmit power available across the set of multiple component carriers and a third transmit power associated with the second component carrier.

[0254] In some examples, the value of the carrier aggregation power headroom parameter indicates a difference between a first transmit power available across a set of multiple component carriers and a second transmit power available for uplink transmission via the first component carrier. In some examples, the value of the carrier aggregation power headroom parameter indicates a first transmit power available across a set of multiple component carriers during a transmit opportunity.

[0255] In some examples, the multi-carrier headroom component 1340 may be configured as or otherwise support components for receiving one or more uplink messages including at least the uplink message, each of the one or more uplink messages being received via a corresponding component carrier in a set of multiple component carriers and being associated with a corresponding second transmit power, wherein the value of the carrier aggregation power headroom parameter is based on a difference between a first transmit power available across the set of multiple component carriers and a sum of the corresponding second transmit powers associated with each of the one or more uplink messages.

[0256] In some examples, the control message component 1345 may be configured as or otherwise support components for sending a control message allocating a set of uplink channel resources for carrier aggregation power headroom reporting, wherein a power headroom report is received via the set of uplink channel resources based on the control message.

[0257] In some examples, to support receiving power headroom reports, the reporting resource component 1350 may be configured as or otherwise support components for receiving power headroom reports via a first component carrier and a first cell, where the first component carrier and the first cell are configured for carrier aggregation power headroom reporting.

[0258] In some examples, to support receiving power headroom reports, the report timing component 1355 may be configured as or otherwise support components for receiving power headroom reports based on expiration of a power headroom reporting timer, wherein the power headroom reporting timer includes a periodic timer, a prohibit timer, or both configured for power headroom reporting.

[0259] Fig.14 A diagram of a system 1400 including a device 1405 supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is shown. The device 1405 may be an example of a device 1105, a device 1205, or a network entity 105 as described herein, or include components thereof. The device 1405 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which communication may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1405 may include components that support output and acquisition of communications, such as a communication manager 1420, a transceiver 1410, an antenna 1415, a memory 1425, a code 1430, and a processor 1435. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1440).

[0260] As described herein, the transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both. In some examples, the transceiver 1410 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1410 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1405 may include one or more antennas 1415, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1410 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1415, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1415, from a wired receiver); and demodulating the signal. In some implementations, the transceiver 1410 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1415 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1415 configured to support various transmitting operations or output operations, or a combination thereof. In some implementations, the transceiver 1410 may include or be configured to be coupled to one or more processors or memory components that are operable to: perform or support operations based on received or obtained information or signals; or generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1410, or the transceiver 1410 and one or more antennas 1415, or the transceiver 1410 and one or more antennas 1415 and one or more processors or memory components (e.g., processor 1435, or memory 1425, or both) may be included in a chip or chip assembly installed in the device 1405. The transceiver 1410 or transceiver 1410 and one or more antennas 1415 or wired interfaces (where applicable) may be examples of transmitter 1115, transmitter 1215, receiver 1110, receiver 1210, or any combination thereof or components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

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

[0262] The processor 1435 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1435 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1435. The processor 1435 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1425) so that the device 1405 performs various functions (e.g., functions or tasks that support power headroom reporting for uplink carrier aggregation communications). For example, the device 1405 or a component of the device 1405 may include a processor 1435 and a memory 1425 coupled to the processor 1435, and the processor 1435 and the memory 1425 are configured to perform the various functions described herein. Processor 1435 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance) that may host functions for performing functions of device 1405 (e.g., by executing code 1430). Processor 1435 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1405 (such as within memory 1425). In some specific implementations, processor 1435 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce a set of outputs (which may be passed to other systems or components (e.g., device 1405)). For example, a processing system of device 1405 may refer to a system including various other components or subcomponents of device 1405, such as processor 1435, or transceiver 1410, or communication manager 1420, or other components or combinations of components of device 1405. The processing system of device 1405 may be docked with other components of device 1405, and may process information (such as input or signal) received from other components or output information to other components. For example, a chip or modem of device 1405 may include a processing system and an interface for outputting information or for obtaining information or both. The interface may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information. In some specific implementations, the first interface may refer to an interface between a processing system of a chip or modem and a transmitter, so that device 1405 can send information output from the chip or modem. In some specific implementations, the second interface may refer to an interface between a processing system of a chip or modem and a receiver, so that device 1405 can obtain information or signal input, and the information can be passed to the processing system.One of ordinary skill in the art will readily recognize that the first interface may also obtain information or signal input, and the second interface may also output information or signal output.

[0263] In some examples, bus 1440 may support communications of protocol layers (e.g., within protocol layers) of a protocol stack. In some examples, bus 1440 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1405, or communications performed between different components of device 1405 that may be co-located or may be located in different locations (e.g., where device 1405 may refer to a system in which one or more of communication manager 1420, transceiver 1410, memory 1425, code 1430, and processor 1435 may be located in one component of different components or divided between different components).

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

[0265] According to examples as disclosed herein, the communication manager 1420 may support wireless communications at a network entity. For example, the communication manager 1420 may be configured to or otherwise support components for sending a first message indicating that a set of multiple component carriers is configured for communication at a UE. The communication manager 1420 may be configured to or otherwise support components for receiving an uplink message associated with a second transmit power during a transmit opportunity via a first component carrier in the set of multiple component carriers. The communication manager 1420 may be configured to or otherwise support components for receiving a power headroom report including a carrier aggregation power headroom parameter via at least a first component carrier in the set of multiple component carriers, wherein a value of the carrier aggregation power headroom parameter may be based on a first transmit power available for uplink transmission by the UE across the set of multiple component carriers during the transmit opportunity and a second transmit power associated with uplink carrier aggregation transmissions performed at least via the first component carrier during the transmit opportunity.

[0266] By including or configuring a communications manager 1420 according to examples as described herein, the device 1405 may support techniques for improved communications reliability, reduced latency, reduced power consumption, more efficient use of communications resources, improved inter-device coordination, and longer battery life, among other advantages.

[0267] In some examples, the communication manager 1420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1410, one or more antennas 1415 (e.g., where applicable), or any combination thereof. Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the processor 1435, the memory 1425, the code 1430, the transceiver 1410, or any combination thereof. For example, the code 1430 may include instructions executable by the processor 1435 to cause the device 1405 to perform various aspects of power headroom reporting for uplink carrier aggregation communications as described herein, or the processor 1435 and the memory 1425 may be otherwise configured to perform or support such operations.

[0268] Fig.15 A flow chart illustrating a method 1500 for supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described herein. Figures 1 to 10 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0269] At 1505, the method may include receiving a first message indicating that a plurality of component carriers are configured for communication at the UE. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Fig. 9 The described carrier aggregation component 925 is performed.

[0270] At 1510, the method may include determining a first transmit power that may be used by the UE to perform uplink carrier aggregation transmission across the plurality of component carriers during a transmission opportunity. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig. 9 The described carrier aggregation power component 930 is performed.

[0271] At 1515, the method may include transmitting a power headroom report including a carrier aggregation power headroom parameter via at least a first component carrier in the plurality of component carriers, wherein a value of the carrier aggregation power headroom parameter is based at least in part on the first transmit power available across the plurality of component carriers during the transmit opportunity and a second transmit power associated with the uplink carrier aggregation transmission via at least one component carrier in the set of the plurality of component carriers during the transmit opportunity. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described with reference to Fig. 9 The described power headroom reporting component 935 is performed.

[0272] Fig.16 A flow chart illustrating a method 1600 for supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described herein. Figures 1 to 10 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0273] At 1605, the method may include receiving a first message indicating that a plurality of component carriers are configured for communication at the UE. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Fig. 9 The described carrier aggregation component 925 is performed.

[0274] At 1610, the method may include determining a first transmit power that may be used by the UE to perform uplink carrier aggregation transmission across the plurality of component carriers during a transmission opportunity. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig. 9 The described carrier aggregation power component 930 is performed.

[0275] At 1615, the method may include transmitting an uplink message via at least a first component carrier of the plurality of component carriers, the uplink message being associated with a second transmit power. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig. 9 The described uplink message component 940 is performed.

[0276] At 1620, the method may include calculating a difference between the first transmit power and the second transmit power available across the plurality of component carriers. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Fig. 9 The described multi-carrier headroom component 945 is performed.

[0277] At 1625, the method may include sending a power headroom report including a carrier aggregation power headroom parameter via at least a first component carrier of the plurality of component carriers, wherein a value of the carrier aggregation power headroom parameter indicates the difference between the first transmit power and the second transmit power available across the plurality of component carriers. The operations of 1625 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1625 may be performed as described in reference to Fig. 9 The described power headroom reporting component 935 is performed.

[0278] Fig.17 A flow chart illustrating a method 1700 for supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE or a component thereof as described herein. Figures 1 to 10 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0279] At 1705, the method may include receiving a first message indicating that a plurality of component carriers are configured for communication at the UE. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig. 9 The described carrier aggregation component 925 is performed.

[0280] At 1710, the method may include determining a first transmit power that may be used by the UE to perform uplink carrier aggregation transmission across the plurality of component carriers during a transmission opportunity. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig. 9 The described carrier aggregation power component 930 is performed.

[0281] At 1715, the method may include sending one or more uplink messages corresponding to the uplink carrier aggregation transmission, each of the one or more uplink messages being sent via a corresponding component carrier of the plurality of component carriers and using a corresponding second transmission power. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig. 9 The described uplink message component 940 is performed.

[0282] At 1720, the method may include calculating a difference between the first transmit power available across the plurality of component carriers and the sum of the corresponding second transmit powers used to transmit each of the one or more uplink messages. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described in reference to Fig. 9 The described multi-carrier headroom component 945 is performed.

[0283] At 1725, the method may include sending a power headroom report including a carrier aggregation power headroom parameter via at least a first component carrier in the set of multiple component carriers, wherein a value of the carrier aggregation power headroom parameter indicates the difference between the first transmit power available across the multiple component carriers and the sum of the corresponding second transmit powers used to send each of the one or more uplink messages. The operations of 1725 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1725 may be performed as described in reference to Fig. 9 The described power headroom reporting component 935 is performed.

[0284] Fig.18 A flow chart illustrating a method 1800 for supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 6 as well as Figures 11 to 14 The network entity described herein may be executed by the network entity described herein. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0285] At 1805, the method may include sending a first message indicating that a plurality of component carriers are configured for communication at the UE. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.13 The described carrier aggregation component 1325 is performed.

[0286] At 1810, the method may include receiving an uplink message associated with a second transmit power during a transmit opportunity via a first component carrier of the plurality of component carriers. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.13 The described uplink message component 1330 is performed.

[0287] At 1815, the method may include receiving a power headroom report including a carrier aggregation power headroom parameter via at least the first component carrier in the set of multiple component carriers, wherein a value of the carrier aggregation power headroom parameter is based at least in part on a first transmit power available for uplink transmission by the UE across the multiple component carriers during the transmission opportunity and a second transmit power associated with uplink carrier aggregation transmissions performed via at least the first component carrier during the transmission opportunity. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described with reference to Fig.13 The described power headroom reporting component 1335 is performed.

[0288] Fig.19 A flow chart illustrating a method 1900 for supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 6 as well as Figures 11 to 14 The network entity described herein may be executed by the network entity described herein. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0289] At 1905, the method may include sending a first message indicating that a plurality of component carriers are configured for communication at the UE. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Fig.13 The described carrier aggregation component 1325 is performed.

[0290] At 1910, the method may include receiving an uplink message associated with a second transmit power during a transmit opportunity via a first component carrier of the plurality of component carriers. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described in reference to Fig.13 The described uplink message component 1330 is performed.

[0291] At 1915, the method may include receiving one or more uplink messages including at least the uplink message, each of the one or more uplink messages being received via a corresponding component carrier of the plurality of component carriers and being associated with a corresponding second transmit power. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described in reference to Fig.13 The described multi-carrier headroom component 1340 is performed.

[0292] At 1920, the method may include receiving, via at least the first component carrier of the set of multiple component carriers, a power headroom report including a carrier aggregation power headroom parameter, wherein a value of the carrier aggregation power headroom parameter is based at least in part on a difference between the first transmit power available across the multiple component carriers and a sum of the corresponding second transmit powers associated with each of the one or more uplink messages. The operations of 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed as described in reference to Fig.13 The described power headroom reporting component 1335 is performed.

[0293] Fig. 20 A flow chart illustrating a method 2000 for supporting power headroom reporting for uplink carrier aggregation communications according to one or more aspects of the present disclosure is shown. The operations of the method 2000 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2000 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 6 as well as Figures 11 to 14 The network entity described herein may be executed by the network entity described herein. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0294] At 2005, the method may include sending a first message indicating that a plurality of component carriers are configured for communication at the UE. The operations of 2005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed as described in reference to Fig.13 The described carrier aggregation component 1325 is performed.

[0295] At 2010, the method may include receiving an uplink message associated with a second transmit power during a transmit opportunity via a first component carrier of the plurality of component carriers. The operations of 2010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed as described in reference to Fig.13 The described uplink message component 1330 is performed.

[0296] At 2015, the method may include sending a control message allocating a set of uplink channel resources for carrier aggregation power headroom reporting. The operations of 2015 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2015 may be performed as described in reference to Fig.13 The described control message component 1345 is executed.

[0297] At 2020, the method may include receiving a power headroom report including a carrier aggregation power headroom parameter via at least the first component carrier of the plurality of component carriers, wherein a value of the carrier aggregation power headroom parameter is based at least in part on a first transmit power available for uplink transmission by the UE across the plurality of component carriers during the transmission opportunity and the second transmit power associated with uplink carrier aggregation transmissions performed at least via the first component carrier during the transmission opportunity, and wherein the power headroom report is received via the uplink channel resource set based at least in part on the control message. The operations of 2020 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2020 may be performed by reference to Fig.13 The described power headroom reporting component 1335 is performed.

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

[0299] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a first message indicating that multiple component carriers are configured for communication at the UE; determining a first transmit power available for uplink carrier aggregation transmission by the UE across the multiple component carriers during a transmission opportunity; and sending a power headroom report including a carrier aggregation power headroom parameter via at least a first component carrier among the multiple component carriers, wherein the value of the carrier aggregation power headroom parameter is at least partially based on the first transmit power available across the multiple component carriers during the transmission opportunity and a second transmit power associated with the uplink carrier aggregation transmission performed via at least one component carrier among the multiple component carriers during the transmission opportunity.

[0300] Aspect 2: According to the method described in Aspect 1, the method also includes: sending an uplink message via at least the first component carrier among the multiple component carriers, the uplink message being associated with the second transmit power; and calculating the difference between the first transmit power and the second transmit power available across the multiple component carriers, wherein the value of the carrier aggregation power headroom parameter indicates the difference.

[0301] Aspect 3: A method according to Aspect 2, wherein sending the power headroom report includes: sending the carrier aggregation power headroom parameter and the second power headroom parameter via the power headroom report, wherein the value of the second power headroom parameter is at least partially based on the difference between a third transmit power available for uplink transmission on the first component carrier and the second transmit power.

[0302] Aspect 4: According to the method described in any one of Aspects 2 to 3, the method further includes: sending a second uplink message via a second component carrier among the multiple component carriers; calculating a second difference between the first transmit power available across the multiple component carriers and a third transmit power associated with the second component carrier; and sending a second carrier aggregation power headroom parameter via the second uplink message, wherein the value of the second carrier aggregation power headroom parameter indicates the second difference.

[0303] Aspect 5: According to the method described in any one of Aspects 1 to 4, the method further includes: determining the second transmit power, the second transmit power corresponding to the amount of transmit power available for uplink transmission on the first component carrier, wherein the value of the carrier aggregation power headroom parameter indicates the difference between the first transmit power and the second transmit power available across the multiple component carriers.

[0304] Aspect 6: The method according to any one of aspects 1 to 4, wherein the value of the carrier aggregation power headroom parameter indicates the first transmission power that can be used by the UE to perform the uplink carrier aggregation transmission across the multiple component carriers during the transmission opportunity.

[0305] Aspect 7: According to the method described in Aspect 1, the method further includes: sending one or more uplink messages corresponding to the uplink carrier aggregation transmission, sending each of the one or more uplink messages via a corresponding component carrier among the multiple component carriers and using a corresponding second transmission power; and calculating the difference between the first transmission power available across the multiple component carriers and the sum of the corresponding second transmission powers used to send each of the one or more uplink messages, wherein the value of the carrier aggregation power headroom parameter indicates the difference.

[0306] Aspect 8: According to the method described in Aspect 7, the method also includes: calculating the sum of the corresponding second transmission powers and one or more reference power levels, the one or more reference power levels being associated with a subset of component carriers among the multiple component carriers that is different from the corresponding component carriers via which the one or more uplink messages are sent, wherein the one or more reference power levels are at least partially based on a reference power reduction parameter.

[0307] Aspect 9: According to the method described in any one of Aspects 1 to 8, the method further includes: receiving a control message allocating an uplink channel resource set for carrier aggregation power headroom reporting, wherein the power headroom report is sent via the uplink channel resource set based at least in part on the control message.

[0308] Aspect 10: A method according to any one of Aspects 1 to 8, wherein sending the power headroom report comprises: sending the power headroom report via the first component carrier and the first cell, wherein the first component carrier and the first cell are configured for carrier aggregation power headroom reporting by the UE.

[0309] Aspect 11: A method according to any one of Aspects 1 to 10, wherein sending the power headroom report includes: sending the power headroom report based at least in part on the expiration of a power headroom reporting timer, wherein the power headroom reporting timer includes a periodic timer, a prohibition timer, or both configured for power headroom reporting by the UE.

[0310] Aspect 12: According to the method described in Aspect 11, the method also includes: determining to send the power headroom report via the resource set based at least in part on the resource set allocated for power headroom reporting on the first component carrier after the expiration of the power headroom reporting timer and before other resource sets allocated for power headroom reporting on other component carriers among the multiple component carriers.

[0311] Aspect 13: The method according to any one of Aspects 11 to 12, wherein the power headroom reporting timer includes the periodic timer, and the periodicity of the periodic timer is configured for carrier aggregation power headroom reporting, per-carrier power headroom reporting, or both.

[0312] Aspect 14: According to the method described in any one of Aspects 1 to 13, the method further includes: determining a difference between a first path loss associated with at least one of the multiple component carriers at a first time and a second path loss associated with the at least one component carrier at a second time; and comparing the difference with a path loss threshold, wherein sending the power headroom report is at least partially based on the difference exceeding the path loss threshold.

[0313] Aspect 15: According to the method described in any one of Aspects 1 to 13, the method further includes: determining a difference between a first value of a first MPR parameter associated with at least one of the multiple component carriers at a first time and a second value of the first MPR parameter associated with the at least one component carrier at a second time; and comparing the difference with a power reduction threshold, wherein sending the power headroom report is at least partially based on the difference exceeding the power reduction threshold.

[0314] Aspect 16: A method for wireless communication at a network entity, the method comprising: sending a first message indicating that multiple component carriers are configured for communication at a UE; receiving an uplink message associated with a second transmit power during a transmit opportunity via a first component carrier among the multiple component carriers; and receiving a power headroom report including a carrier aggregation power headroom parameter via at least the first component carrier among the multiple component carriers, wherein the value of the carrier aggregation power headroom parameter is at least partially based on a first transmit power that can be used by the UE for uplink transmission across the multiple component carriers during the transmit opportunity and the second transmit power associated with uplink carrier aggregation transmission performed at least via the first component carrier during the transmit opportunity.

[0315] Aspect 17: A method according to Aspect 16, wherein the value of the carrier aggregation power headroom parameter is based at least in part on a difference between the first transmit power available across the multiple component carriers and the second transmit power associated with the uplink message received via the first component carrier.

[0316] Aspect 18: A method according to Aspect 17, wherein receiving the power headroom report includes: receiving the carrier aggregation power headroom parameter and the second power headroom parameter via the power headroom report, wherein the value of the second power headroom parameter is at least partially based on the difference between a third transmit power available for uplink transmission on the first component carrier and the second transmit power.

[0317] Aspect 19: According to the method described in any one of Aspects 17 to 18, the method further includes: receiving a second uplink message via a second component carrier among the multiple component carriers; and receiving a second carrier aggregation power headroom parameter via the second uplink message, wherein the value of the second carrier aggregation power headroom parameter indicates a second difference between the first transmit power available across the multiple component carriers and a third transmit power associated with the second component carrier.

[0318] Aspect 20: A method according to any one of Aspects 16 to 19, wherein the value of the carrier aggregation power headroom parameter indicates a difference between the first transmit power available across the multiple component carriers and a second transmit power available for uplink transmission via the first component carrier.

[0319] Aspect 21: The method according to any one of aspects 16 to 20, wherein the value of the carrier aggregation power headroom parameter indicates the first transmit power available across the multiple component carriers during the transmit opportunity.

[0320] Aspect 22: According to the method according to Aspect 16, the method also includes: receiving one or more uplink messages including at least the uplink message, each of the one or more uplink messages is received via a corresponding component carrier among the multiple component carriers and is associated with a corresponding second transmit power, wherein the value of the carrier aggregation power headroom parameter is at least partially based on the difference between the first transmit power available across the multiple component carriers and the sum of the corresponding second transmit powers associated with each of the one or more uplink messages.

[0321] Aspect 23: According to the method described in any one of Aspects 16 to 22, the method also includes: sending a control message allocating an uplink channel resource set for carrier aggregation power headroom reporting, wherein the power headroom report is received via the uplink channel resource set based at least in part on the control message.

[0322] Aspect 24: The method according to any one of Aspects 16 to 23, wherein receiving the power headroom report comprises: receiving the power headroom report via the first component carrier and the first cell, wherein the first component carrier and the first cell are configured for carrier aggregation power headroom reporting.

[0323] Aspect 25: A method according to any one of Aspects 16 to 24, wherein receiving the power headroom report includes: receiving the power headroom report based at least in part on the expiration of a power headroom reporting timer, wherein the power headroom reporting timer includes a periodic timer, a prohibit timer, or both configured for power headroom reporting.

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

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

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

[0327] Aspect 29: An apparatus for performing wireless communications at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 16 to 25.

[0328] Aspect 30: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing a method according to any one of aspects 16 to 25.

[0329] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 16 to 25.

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

[0331] Although aspects of LTE, LTE-A, LTE-APro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-APro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-APro, or NR networks. For example, the described techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

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

[0333] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

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

[0335] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that promotes computer program to be transmitted from one position to another position.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code parts and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disks and optical disks as used herein include CDs, laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0336] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Moreover, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

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

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

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

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

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: receiving a first message indicating that a plurality of component carriers are configured for communication at the UE; determining a first transmit power available for uplink carrier aggregation transmission by the UE across the plurality of component carriers during a transmit opportunity; as well as A power headroom report including a carrier aggregation power headroom parameter is sent via at least a first component carrier among the multiple component carriers, wherein a value of the carrier aggregation power headroom parameter is based at least in part on the first transmit power available across the multiple component carriers during the transmit opportunity and a second transmit power associated with the uplink carrier aggregation transmission performed via at least one component carrier among the multiple component carriers during the transmit opportunity.

2. The method according to claim 1, further comprising: transmitting an uplink message via at least the first component carrier of the plurality of component carriers, the uplink message being associated with the second transmit power; as well as A difference between the first transmit power and the second transmit power available across the plurality of component carriers is calculated, wherein the value of the carrier aggregation power headroom parameter is indicative of the difference.

3. The method of claim 2, wherein sending the power headroom report comprises: The carrier aggregation power headroom parameter and a second power headroom parameter are transmitted via the power headroom report, wherein a value of the second power headroom parameter is based at least in part on a difference between a third transmit power available for uplink transmission on the first component carrier and the second transmit power.

4. The method according to claim 2, further comprising: sending a second uplink message via a second component carrier among the plurality of component carriers; calculating a second difference between the first transmit power available across the plurality of component carriers and a third transmit power associated with the second component carrier; as well as A second carrier aggregation power headroom parameter is sent via the second uplink message, wherein a value of the second carrier aggregation power headroom parameter indicates the second difference.

5. The method according to claim 1, further comprising: Determine the second transmit power, the second transmit power corresponding to an amount of transmit power available for uplink transmission on the first component carrier, wherein the value of the carrier aggregation power headroom parameter indicates a difference between the first transmit power and the second transmit power available across the multiple component carriers.

6. The method of claim 1, wherein the value of the carrier aggregation power headroom parameter indicates the first transmit power available for the uplink carrier aggregation transmission by the UE across the plurality of component carriers during the transmit opportunity.

7. The method according to claim 1, further comprising: transmitting one or more uplink messages corresponding to the uplink carrier aggregation transmission, each of the one or more uplink messages being transmitted via a corresponding component carrier of the plurality of component carriers and using a corresponding second transmit power; as well as A difference between the first transmit power available across the plurality of component carriers and a sum of the respective second transmit powers used to transmit each of the one or more uplink messages is calculated, wherein the value of the carrier aggregation power headroom parameter indicates the difference.

8. The method according to claim 7, further comprising: A sum of the respective second transmit powers and one or more reference power levels are calculated, the one or more reference power levels being associated with a subset of component carriers of the plurality of component carriers that are different from the respective component carriers via which the one or more uplink messages are sent, wherein the one or more reference power levels are based at least in part on a reference power reduction parameter.

9. The method according to claim 1, further comprising: A control message is received that allocates a set of uplink channel resources for a carrier aggregation power headroom report, wherein the power headroom report is sent via the set of uplink channel resources based at least in part on the control message.

10. The method of claim 1, wherein sending the power headroom report comprises: The power headroom report is sent via the first component carrier and a first cell, wherein the first component carrier and the first cell are configured for carrier aggregation power headroom reporting by the UE.

11. The method of claim 1 , wherein sending the power headroom report comprises: The power headroom report is sent based at least in part on an expiration of a power headroom reporting timer, wherein the power headroom reporting timer comprises a periodic timer, a prohibit timer, or both configured for power headroom reporting by the UE.

12. The method according to claim 11, further comprising: Determining to send the power headroom report via the set of resources allocated for power headroom reporting on the first component carrier based at least in part on the set of resources allocated for power headroom reporting on the first component carrier after the expiration of the power headroom reporting timer and before other sets of resources allocated for power headroom reporting on other component carriers in the plurality of component carriers.

13. The method of claim 11, wherein the power headroom reporting timer comprises the periodic timer, and the periodicity of the periodic timer is configured for carrier aggregation power headroom reporting, per-carrier power headroom reporting, or both.

14. The method according to claim 1, further comprising: determining a difference between a first path loss associated with at least one component carrier of the plurality of component carriers at a first time and a second path loss associated with the at least one component carrier at a second time; as well as The difference is compared to a path loss threshold, wherein sending the power headroom report is based at least in part on the difference exceeding the path loss threshold.

15. The method according to claim 1, further comprising: determining a difference between a first value of a first maximum power reduction parameter associated with at least one component carrier of the plurality of component carriers at a first time and a second value of the first maximum power reduction parameter associated with the at least one component carrier at a second time; as well as The difference is compared to a power reduction threshold, wherein sending the power headroom report is based at least in part on the difference exceeding the power reduction threshold.

16. A method for wireless communication at a network entity, the method comprising: sending a first message indicating that a plurality of component carriers are configured for communication at a user equipment (UE); receiving, via a first component carrier of the plurality of component carriers, an uplink message associated with a second transmit power during a transmit opportunity; as well as A power headroom report including a carrier aggregation power headroom parameter is received via at least the first component carrier of the plurality of component carriers, wherein a value of the carrier aggregation power headroom parameter is based at least in part on a first transmit power available for uplink transmission by the UE across the plurality of component carriers during the transmission opportunity and a second transmit power associated with uplink carrier aggregation transmissions performed via at least the first component carrier during the transmission opportunity.

17. The method of claim 16, wherein the value of the carrier aggregation power headroom parameter is based at least in part on a difference between the first transmit power available across the plurality of component carriers and the second transmit power associated with the uplink message received via the first component carrier.

18. The method of claim 17, wherein receiving the power headroom report comprises: The carrier aggregation power headroom parameter and a second power headroom parameter are received via the power headroom report, wherein a value of the second power headroom parameter is based at least in part on a difference between a third transmit power available for uplink transmission on the first component carrier and the second transmit power.

19. The method according to claim 17, further comprising: receiving a second uplink message via a second component carrier of the plurality of component carriers; as well as A second carrier aggregation power headroom parameter is received via the second uplink message, wherein a value of the second carrier aggregation power headroom parameter indicates a second difference between the first transmit power available across the plurality of component carriers and a third transmit power associated with the second component carrier.

20. The method of claim 16, wherein the value of the carrier aggregation power headroom parameter indicates a difference between the first transmit power available across the plurality of component carriers and a second transmit power available for uplink transmission via the first component carrier.

21. The method of claim 16, wherein the value of the carrier aggregation power headroom parameter indicates the first transmit power available across the plurality of component carriers during the transmit opportunity.

22. The method according to claim 16, further comprising: receiving one or more uplink messages comprising at least the uplink message, each of the one or more uplink messages being received via a corresponding component carrier of the plurality of component carriers and being associated with a corresponding second transmit power, wherein the value of the carrier aggregation power headroom parameter is based at least in part on a difference between the first transmit power available across the plurality of component carriers and a sum of the corresponding second transmit powers associated with each of the one or more uplink messages.

23. The method according to claim 16, further comprising: A control message is sent that allocates a set of uplink channel resources for a carrier aggregation power headroom report, wherein the power headroom report is received via the set of uplink channel resources based at least in part on the control message.

24. The method of claim 16, wherein receiving the power headroom report comprises: The power headroom report is received via the first component carrier and a first cell, wherein the first component carrier and the first cell are configured for carrier aggregation power headroom reporting.

25. The method of claim 16, wherein receiving the power headroom report comprises: The power headroom report is received based at least in part on expiration of a power headroom reporting timer, wherein the power headroom reporting timer comprises a periodic timer, a prohibit timer, or both configured for power headroom reporting.

26. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; and a memory coupled to the processor, wherein the memory includes instructions executable by the processor to cause the apparatus to: receiving a first message indicating that a plurality of component carriers are configured for communication at the UE; determining a first transmit power available for uplink carrier aggregation transmission by the UE across the plurality of component carriers during a transmit opportunity; as well as A power headroom report including a carrier aggregation power headroom parameter is sent via at least a first component carrier among the multiple component carriers, wherein a value of the carrier aggregation power headroom parameter is based at least in part on the first transmit power available across the multiple component carriers during the transmit opportunity and a second transmit power associated with the uplink carrier aggregation transmission performed via at least one component carrier among the multiple component carriers during the transmit opportunity.

27. The apparatus of claim 26, wherein the instructions are further executable by the processor to cause the apparatus to: transmitting an uplink message via at least the first component carrier of the plurality of component carriers, the uplink message being associated with the second transmit power; and A difference between the first transmit power and the second transmit power available across the plurality of component carriers is calculated, wherein the value of the carrier aggregation power headroom parameter is indicative of the difference.

28. The apparatus of claim 27, wherein the instructions for sending the power headroom report are executable by the processor to cause the apparatus to: The carrier aggregation power headroom parameter and a second power headroom parameter are transmitted via the power headroom report, wherein a value of the second power headroom parameter is based at least in part on a difference between a third transmit power available for uplink transmission on the first component carrier and the second transmit power.

29. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; and a memory coupled to the processor, wherein the memory includes instructions executable by the processor to cause the apparatus to: sending a first message indicating that a plurality of component carriers are configured for communication at a user equipment (UE); receiving, via a first component carrier of the plurality of component carriers, an uplink message associated with a second transmit power during a transmit opportunity; as well as A power headroom report including a carrier aggregation power headroom parameter is received via at least the first component carrier of the plurality of component carriers, wherein a value of the carrier aggregation power headroom parameter is based at least in part on a first transmit power available for uplink transmission by the UE across the plurality of component carriers during the transmission opportunity and a second transmit power associated with uplink carrier aggregation transmissions performed via at least the first component carrier during the transmission opportunity.

30. The apparatus of claim 29, wherein the value of the carrier aggregation power headroom parameter is based at least in part on a difference between the first transmit power available across the plurality of component carriers and the second transmit power associated with the uplink message received via the first component carrier.

Images