Power headroom reporting for uplink component carriers

Abstract

Various aspects of the disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can detect an occurrence of a triggering event associated with a power headroom report. The UE can transmit, from the UE to a base station, a power headroom report (PHR) medium access control (MAC) control element (CE) based at least in part on the occurrence of the triggering event, where the PHR MAC-CE is for one or more uplink component carriers of the UE that are associated with one or more control resource set pool index values. Numerous other aspects are provided.

Description

[0001] Cross-references to related applications

[0002] This patent application claims priority to the following applications: U.S. Provisional Patent Application No. 62 / 706,327, filed August 10, 2020, entitled “POWER HEADROOM REPORTING FOR UPLINK COMPONENT CARRIERS”; and U.S. Non-Provisional Patent Application No. 17 / 304,093, filed June 14, 2021, entitled “POWER HEADROOM REPORTING FOR UPLINK COMPONENT CARRIERS”, which are hereby expressly incorporated herein by reference. Technical Field

[0003] In summary, various aspects of this disclosure relate to wireless communication, and specifically to techniques and apparatus for reporting power margins for uplink component carriers. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / Improved LTE is an enhanced set of the Universal Mobile Telecommunications System (UMTS) mobile standard released by the 3rd Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more base stations that support communication for one or more user equipment (UE) devices. The UE may communicate with the base station via downlink and uplink communication. "Downlink" (or "DL") refers to the communication link from the base station to the UE, and "uplink" (or "UL") refers to the communication link from the UE to the base station.

[0006] The above multiple access technologies have been adopted in various telecommunication standards to provide common protocols to communicate between UEs and base stations (e.g., eNodeBs) on a municipal, national, regional, and / or global level. New Radio (NR), which can be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, CP-OFDM and / or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and may additional support beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. SUMMARY

[0007] In some aspects, a method of wireless communication performed by a user equipment (UE) includes detecting an occurrence of a triggering event associated with a power headroom report; and transmitting, from the UE to a base station, a power headroom report (PHR) medium access control (MAC) control element (CE) based at least in part on the occurrence of the triggering event, wherein the PHR MAC-CE is for one or more uplink component carriers of the UE that are associated with one or more control resource set (CORESET) pool index values.

[0008] In some aspects, a UE for wireless communication includes a memory and one or more processors coupled to the memory, the one or more processors configured to: detect an occurrence of a triggering event associated with a power headroom report; and transmit, from the UE to a base station, a PHR MAC-CE based at least in part on the occurrence of the triggering event, wherein the PHR MAC-CE is for one or more uplink component carriers of the UE that are associated with one or more CORESET pool index values.

[0009] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: detect an occurrence of a triggering event associated with a power headroom report; and transmit, from the UE to a base station, a PHR MAC-CE based at least in part on the occurrence of the triggering event, wherein the PHR MAC-CE is for one or more uplink component carriers of the UE that are associated with one or more CORESET pool index values.

[0010] In some aspects, an apparatus for wireless communication includes means for detecting an occurrence of a triggering event associated with a power headroom report; and means for transmitting, from the apparatus to a base station, a PHR MAC-CE based at least in part on the occurrence of the triggering event, wherein the PHR MAC-CE is for one or more uplink component carriers of the apparatus that are associated with one or more CORESET pool index values.

[0011] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and / or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.

[0012] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows can be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples can be readily utilized as bases for modifying or designing other for carrying the same purposes thereof. Such equivalent constructions are not to depart from the scope of the appended claims. The present description will be better understood from the following description of specific embodiments, taken with reference to the following drawings, from an examination of which can be learned the nature of the subject matter of the application and the related advantages. Each figure depicts only one illustrative embodiment. Each figure is provided to aid in the understanding of the concepts disclosed herein. The figures are not intended to be limiting of the concepts disclosed herein. The figures are provided to aid in the understanding of the concepts disclosed herein.

[0013] While aspects are described in this application by illustration to some examples, those skilled in the art will understand that such aspects can be practiced in many and various ways. Different platform type, devices, systems, shapes, sizes, and / or packaging arrangements can be used to implement the innovations described herein. For example, some aspects can be implemented via integrated chip embodiments and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchasing devices, medical devices, and / or artificial intelligence devices). Chip-scale components, modular components, non-modular components, non-chip-scale components, device-level components, and / or system-level components can be used to implement aspects. Devices incorporating the described aspects and features can include additional components and features for implementation and practice of the claimed and described aspects. For example, transmission and reception of wireless signals can include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or adders). The innovations described herein are intended to be implemented in a variety of devices, chip-scale components, systems, distributed arrangements, and / or end-user devices having different sizes, shapes, and configurations. BRIEF DESCRIPTION OF DRAWINGS

[0014] So that the above-recited features of the present disclosure can be understood in detail, a more particular description will be rendered by reference to certain aspects, some of which are illustrated in the appended drawings. It is appreciated that these drawings depict only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope. The same reference symbols are used in different drawings to identify the same or similar elements.

[0015] Figure 1 FIG. 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0016] Figure 2 FIG. 2 is a diagram illustrating an example of a base station in communication with a UE in a wireless network according to the present disclosure.

[0017] Figure 3 FIG. 3 is a diagram illustrating an example of a multi-transmission reception point configuration according to the present disclosure.

[0018] Figure 4 FIG. 4 is a diagram illustrating an example of a CORESET pool index value configuration according to the present disclosure.

[0019] Figures 5-7 FIG. 5 is a diagram illustrating an example associated with a power headroom report for an uplink component carrier according to the present disclosure.

[0020] Figure 8 FIG. 7 is a diagram illustrating an example process associated with power headroom reporting for uplink component carriers, in accordance with the present disclosure.

[0021] Figure 9 FIG. 8 is a block diagram of an example apparatus for wireless communication, in accordance with the present disclosure. DETAILED DESCRIPTION

[0022] Various aspects of the disclosure are more fully described below with reference to the figures. The disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art will understand that the scope of the disclosure is intended to encompass any aspect of the disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the disclosure. For example, an apparatus can be implemented or a method can be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to encompass any other structure, functionality, or structure and functionality, in addition to or different from the various aspects of the disclosure set forth herein. It will be understood that any aspect of the disclosure disclosed herein can be implemented by one or more elements of a claim.

[0023] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, and / or the like (collectively referred to as “elements”). These elements can be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0024] While aspects can be described herein using terminology commonly associated with a 5G or New Radio (NR) radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and / or a post-5G RAT (e.g., 6G).

[0025] Figure 1is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 can be or include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network and other examples. The wireless network 100 can include one or more base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 1 lOd), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. A base station 110 is an entity that communicates with UEs 120. Base stations 110 (sometimes referred to as BSs) can include, for example, NR base stations, LTE base stations, NodeBs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, and / or transmission and reception points (TRPs). Each base station 110 can provide communication coverage for a particular geographic area. In Third Generation Partnership Project (3GPP), the term “cell” can refer to a coverage area of a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0026] The base stations 110 can provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell can cover a relatively large geographic area (e.g., several kilometers in radius) and can allow unrestricted access by UEs 120 with service subscriptions. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UEs 120 with service subscriptions. A femto cell can cover a relatively small geographic area (e.g., a home) and can allow restricted access by UEs 120 with associations to the femto cell (e.g., UEs 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell can be referred to as a macro base station. A base station 110 for a pico cell can be referred to as a pico base station. A base station 110 for a femto cell can be referred to as a femto base station or a home base station. In the example shown in FIG. 1, the BS 110a can be a macro base station for the macro cell 102a, the BS 110b can be a pico base station for the pico cell 102b, and the BS 110c can be a femto base station for the femto cell 102c. A base station can support one or multiple (e.g., three) cells. Figure 1 In the example shown in FIG. 1, the BS 110a can be a macro base station for the macro cell 102a, the BS 110b can be a pico base station for the pico cell 102b, and the BS 110c can be a femto base station for the femto cell 102c. A base station can support one or multiple (e.g., three) cells.

[0027] In some examples, a cell can not necessarily be stationary, and the geographic area of the cell can move according to the location of a mobile base station 110 (e.g., a mobile base station). In some examples, base stations 110 can be interconnected to one another and / or to one or more other base stations or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces such as a direct physical connection or a virtual network, using any appropriate transport network.

[0028] Wireless network 100 can include one or more relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a base station 110 or a UE 120) and send a transmission of the data to a downstream station (e.g., a UE 120 or a base station 110). A relay station can be a UE 120 that can relay transmissions for other UEs 120. In the example shown, a relay station 110r can communicate with base station 110a and a UE 120r in order to facilitate communication to and from UE 120r. Figure 1 In the example shown, BS 110d (e.g., a relay base station) can communicate with BS 110a (e.g., a macro base station) and UE 120d in order to facilitate communication between BS 110a and UE 120d. A base station 110 that relays

[0029] Wireless network 100 can be a heterogeneous network that includes base stations 110 of different types, such as macro base stations, pico base stations, femto base stations, relay base stations, and / or the like. These different types of base stations 110 can have different transmit power levels, different coverage areas, and / or different impacts on interference. For example, macro base stations can have a high transmit power level (e.g., 5 to 40 Watts), whereas pico base stations, femto base stations, and relay base stations can have relatively lower transmit power levels (e.g., 0.1 to 2 Watts).

[0030] A network controller 130 can couple to or communicate with a set of base stations 110 and can provide coordination and control for these base stations 110. The network controller 130 can communicate with the base stations 110 via a backhaul communication link. The base stations 110 can also communicate with one another directly or indirectly via wireless or wireline backhaul communication links.

[0031] The UEs 120 can be dispersed throughout the wireless network 100, and each UE 120 can be stationary or mobile. A UE 120 can include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. A UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicular component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, and / or any other suitable device that is configured to communicate via a wireless or wired medium.

[0032] Some UEs 120 can be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC and / or eMTC UEs can include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, that can communicate with a base station, another device (e.g., remote device), or some other entity. A

[0033] In general, any number of wireless networks 100 can be deployed within a given geographic area. Each wireless network 100 can support a particular RAT and can operate on one or more frequencies. A RAT can be referred to as a radio technology, an air interface, and / or the like. A frequency can be referred to as a carrier, a frequency channel, and / or the like. Each frequency can support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0034] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using a base station 110 as an intermediary to transmit information from one UE 120 to another UE 120). For example, UEs 120 can communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which can include a vehicle-to- vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol, among other examples), and / or a mesh network. In such examples, a UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the base station 110.

[0035] Devices of wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided by frequency or wavelength into various classes, bands, channels, and so on. For example, devices of wireless network 100 can communicate using one or more of the operating bands. In 5G NR, two initial operating bands have been identified as frequency range designation FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

[0036] The frequencies between FR1 and FR2 are often referred to as mid-bands. Recent 5G NR studies have identified operating bands in these mid-bands as frequency range designation FR3 (7.125 GHz - 24.25 GHz). Bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend FR1 and / or FR2 characteristics into the mid-bands. Moreover, even higher bands are currently under exploration to extend 5G NR operations beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designation FR4a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher bands fall within the EHF band.

[0037] With the above examples in mind, unless specifically stated otherwise, it should be understood that where a term is used with the meaning of “below 6 GHz” or the like herein, it can be broadly interpreted to mean frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. Also, unless specifically stated otherwise, where a term is used with the meaning of “millimeter wave” or the like herein, it can be broadly interpreted to mean frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a, or FR4-1, and / or FR5, or can be within the EHF frequency band. It is contemplated that the frequencies included in these operational frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0038] As indicated above, Figure 1 are provided as examples. Other examples can differ from what is described with respect to at least one of the following. Figure 1

[0039] Figure 2 is a diagram illustrating an example of a base station 110 in communication with a UE 120 in a wireless network 100, in accordance with the present disclosure. The base station 110 can be equipped with a set of antennas 234a through 234t, such as T antennas (T > 1). The UE 120 can be equipped with a set of antennas 252a through 252r, such as R antennas (R > 1).

[0040] ​At base station 110, a transmit processor 220 can receive data from a data source 212 intended for the UE 120 (or a set of UEs 120). Transmit processor 220 can select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. UE 120 can process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS(s) selected for UE 120 and provide data symbols. Transmit processor 220 can process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and control symbols. Transmit processor 220 can generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and can provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), shown as modems 232a through 232t. Each output symbol stream can be provided to a modulator component (shown as MOD) of modems 232, for example. Each modem 232 can use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can also use a respective modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a downlink signal. Modems 232a through 232t can transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas), shown as antennas 234a through 234t.

[0041] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) can receive the downlink signals from base stations 110 and / or other base stations 110 and can provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems), shown as modems 254a through 254r. For example, each received signal can be provided to a demodulator component (shown as a demodulator) of a modem 254. Each modem 254 can use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) a received signal to obtain input samples. Each modem 254 can use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 can obtain received symbols from modems 254, perform MIMO detection on the received symbols if applicable, and can provide detected symbols. A receive processor 258 can process (e.g., demodulate and decode) the detected symbols, can provide decoded data for UE 120 to a data sink 260, and can provide decoded control information and system information to a controller / processor 280. The term “controller / processor” can refer to one or more controllers, one or more processors, or a combination thereof. A channel processor can determine reference signal received power (RSRP) parameters, received signal strength indicator (RSSI) parameters, reference signal received quality (RSRQ) parameters, and / or CQI parameters, among other examples. In some examples, one or more components of UE 120 can be included in a housing.

[0042] A network controller 130 can include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 can include, for example, one or more devices in a core network. The network controller 130 can communicate with the base stations 110 via the communication unit 294.

[0043] One or more antennas (e.g., antennas 234a through 234t and / or antennas 252a through 252r) can include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, among other examples. An antenna panel, antenna group, set of antenna elements, and / or antenna array can include one or more antenna elements (within a single housing or multiple housings), a set of co-planar antenna elements, a set of non-co-planar antenna elements, and / or one or more antenna elements coupled to one or more transmit and / or receive components (such as one or more components of Figure 2

[0044] ​On the uplink, at UE 120, a transmit processor 264 can receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from controller / processor 280. Transmit processor 264 can also generate reference symbols for one or more reference signals. The symbols from transmit processor 264 can be precoded by a TX MIMO processor 266 if applicable, further processed by a modulator 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some examples, modulator 254 of UE 120 can include a modulator and a demodulator. In some examples, UE 120 includes a transceiver. The transceiver can include any combination of antenna 252, modulators 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver can be used by a processor (e.g., controller / processor 280) and memory 282 to perform any of the methods described herein (for example, with reference to Figures 5-8 ).

[0045] At base station 110, the uplink signals from UE 120 and other UEs can be received by antennas 234, processed by modulators 232 (e.g., demodulator components of modulators 232, such as DEMOD), detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by UE 120. Receive processor 238 can provide the decoded data to a data sink 239 and to controller / processor 240 for control information. Base station 110 can include communication unit 244 and can communicate with network controller 130 via communication unit 244. Base station 110 can include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, modulators of base station 110 can include a modulator and a demodulator. In some examples, base station 110 includes a transceiver. The transceiver can include any combination of antenna 234, modulators 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver can be used by a processor (e.g., controller / processor 240) and memory 242 to perform any of the methods described herein (for example, with reference to Figures 5-8 ).

[0046] Controller / processor 240 of base station 110, controller / processor 280 of UE 120, and / or Figure 2Any other components may perform one or more techniques associated with power headroom reporting for uplink component carriers, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component can perform or direct, for example Figure 8 The operation of process 800 and / or other processes as described herein. Memory 242 and 282 may store data and program code for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly, or after compilation, translation, and / or interpretation), may cause one or more processors, UE 120, and / or base station 110 to perform or instruct, for example... Figure 8 The operation of process 800 and / or other processes as described herein. In some aspects, execution instructions may include run instructions, transformation instructions, compilation instructions, and / or interpretation instructions, as well as other examples.

[0047] In some aspects, the UE (e.g., UE 120) includes: a unit for detecting the occurrence of a triggering event associated with a power margin report; and / or a unit for transmitting a PHR MAC-CE from the UE to the base station based at least in part on the occurrence of the triggering event, wherein the PHR MAC-CE is for one or more uplink component carriers of the UE associated with one or more CORESET pool index values. In some aspects, such a unit may include a combination of Figure 2 One or more components of the described UE 120, such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256 and / or receive processor 258.

[0048] Although Figure 2 The boxes in the diagram are shown as different components, but the functions described above with respect to these boxes can be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be performed by or under the control of controller / processor 280.

[0049] As pointed out above, Figure 2 This is provided as an example. Other examples may differ from the one provided. Figure 2 The example described.

[0050] Uplink power control determines the power used for transmission on the Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Sound Reference Signal (SRS), and / or Physical Random Access Channel (PRACH).

[0051] The UE can use a parameter set configuration with index j and a PUSCH power control adjustment state with index l to transmit PUSCH on the active uplink bandwidth portion (BWP) b of carrier f in serving cell c. The UE can adjust the PUSCH transmission power P in PUSCH transmission timing i. PUSCH,b,f,c (i,j,q d ,l) is determined as:

[0052]

[0053] Regarding PUSCH transmission power P PUSCH,b,f,c (i,j,q d (in dB), P O_PUSCH,b,f,c (j) can represent the P0 value used to control the received power level, α b,f,c (j) can represent the alpha value of partial path loss (PL) compensation, PL b,f,c (q d ) can represent having an index q d The path loss value, Δ, is at least partially based on the measured downlink reference signal. TF,b,f,c (i) can depend on the resource allocation and modulation and coding scheme (MCS) of the PUSCH, and f b,f,c (i,l) can represent closed-loop power control with a closed-loop index l that is at least partially based on transmit power control (TPC) commands.

[0054] For PUSCH transmission, a set of uplink power control parameters can be configured. The uplink power control parameters can include a twoPUSCH-PC-AdjustmentStates parameter, which can be configured when there are two separate loops for closed loop power, and TPC commands can be applied to the two separate loops separately. The uplink power control parameters can include a set of P0 and alpha values for open loop power control (p0-AlphaSets), where each member of the set can have an ID (p0-PUSCH-AlphaSetld: 0, 1, …, 29). The uplink power control parameters can include a list of path loss reference signals, where each member of the list can have an ID (pusch-PathlossReferenceRS-Id: 0, 1, …, 3). The uplink power control parameters can include a list of SRI-PUSCH mappings, where “SRI” refers to SRS reference indicator, and each member of the list can have an ID (sri-PUSCH-PowerControlld: 0, …, 15). In addition, each member of the list can be configured based at least in part on a sri-PUSCH-PowerControlld parameter, which can be used as a codepoint for an SRI field in downlink control information (DCI). When the value of the SRI field in the uplink DCI scheduling the PUSCH is x, then the uplink power control (ULPC) parameters (e.g., PL RS, P0 and alpha, closed loop index) corresponding to the sri-PUSCH-PowerControlld equal to x can be used for the PUSCH transmission. Depending on the configuration of the SRI field, the SRI field can be up to four bits, and can indicate up to 16 x values.

[0055] A power headroom can indicate an amount of remaining transmission power available to the UE in addition to the power used for a current transmission. The power headroom can be based at least in part on a difference between a UE maximum transmission power and a PUSCH transmission power. A power headroom report (PHR) can be a type 1 report for PUSCH, a type 3 report for SRS, and / or a type 2 report for PUCCH. For example, the type of a UE PHR can include a type 1 UE power headroom valid for a PUSCH transmission occasion i on an active UL BWP b of a carrier f of a serving cell c, or a type 3 UE power headroom valid for a SRS transmission occasion i on an active UL BWP b of a carrier f of a serving cell c. Thus, a PHR can be determined for a component carrier and / or a serving cell.

[0056] The UE can determine whether the PHR for an activated serving cell is based at least in part on actual transmissions. The actual transmissions can be determined based at least in part on higher layer signaling of configured grants and periodic / semi-persistent sounding reference signal transmissions and / or DCI received by the UE. The UE can determine whether the PHR for an activated serving cell is based at least in part on a reference format. The reference format can be determined based at least in part on higher layer signaling of configured grants and periodic / semi-persistent sounding reference signal transmissions and / or DCI received by the UE. The UE can determine whether the PHR for an activated serving cell is based at least in part on a reference format.

[0057] When the UE determines that the Type 1 PHR for an activated serving cell is based at least in part on actual PUSCH transmissions, for a PUSCH transmission occasion i on an active uplink BWP b of a carrier f of a serving cell c, the UE can calculate the Type 1 PHR as:

[0058]

[0059] For a Type 1 PHR based at least in part on actual PUSCH transmissions (in dB), P CMAX,f,c (i) can represent the UE configured maximum output power after back-off (e.g., due to maximum power reduction) and P O_PUSCH,b,f,c (j), α b,f,c (j), PL b,f,c (q d ), and f TF,b,f,c (i) and f b,f,c (i, l) can be parameters used to determine the PUSCH transmit power.

[0060] When the UE determines that the Type 1 PHR for an activated serving cell is based at least in part on reference PUSCH transmissions, for a PUSCH transmission occasion i on an active UL BWP b of a carrier f of a serving cell c, the UE can calculate the Type 1 PHR as:

[0061]

[0062] For a Type 1 PHR based at least in part on reference PUSCH transmissions (e.g., a virtual power headroom report), P and P O_PUSCH,b,f,c (j), α b,f,c (j), PL b,f,c (q d ), and fb,f,c (i, l) can be based at least in part on default or reference parameters j, i, l, and q d where for P0 and alpha, p0-PUSCH-AlphaSetId equals 0, and for path loss, PathlossReferenceRS-Id equals 0, and for closed loop index, l equals 0.

[0063] PHR can be triggered by the MAC layer and can be triggered by the occurrence of one or more triggering events. For example, PHR can be triggered by a set of timers, such as phr-PeriodicTimer or phr-ProhibitTimer. PHR can be triggered by a power change that satisfies a configurable threshold for a path loss reference signal for power control in an uplink component carrier. PHR can be triggered by the activation of a secondary cell (SCell). PHR can be triggered when an active BWP of a configured component carrier changes from dormant state to non-dormant state.

[0064] The triggered PHR can be sent in a PHR MAC-CE on a first available PUSCH corresponding to an initial transmission of a transport block, which can accommodate the PHR MAC-CE due to logical channel prioritization. The PUSCH can be dynamic (e.g., scheduled by DCI), or the PUSCH can be a configured grant PUSCH.

[0065] A UE can be configured with multiple component carriers for PUSCH transmission. When the multiple PHR parameter is enabled via radio resource control (RRC) signaling, a PHR MAC-CE can include PHR for more than one component carrier. Otherwise, PHR can be a report for a primary cell (PCell) and can use a single entry PHR MAC-CE format. When a first PUSCH in a first component carrier carries a PHR MAC-CE, for a second component carrier, the PHR MAC-CE can include an actual PHR or a virtual PHR (based on a reference format). When a PUSCH transmission is performed on the second component carrier at the time of a power headroom report (e.g., in a slot of the first PUSCH) and the PUSCH transmission on the second component carrier is scheduled by DCI that satisfies a timeline condition, the PHR MAC-CE can include an actual PHR. Otherwise, the MAC-CE can include a virtual PHR.

[0066] The PHR MAC-CE can be a single entry PHR MAC-CE or a multiple entry PHR MAC-CE. The single entry PHR MAC-CE can include a power headroom (PH) field and a P CMAX,f,cThe PH field can indicate a PH level of the PCell, the P CMAX,f,c The PH field can indicate a PH level of the PCell, the P CMAX,f,c A multi-entry PHR MAC-CE can include entries for the PCell and multiple SCells. For example, for the PCell or a given SCell, the multi-entry PHR MAC-CE can include a corresponding PH field, a P CMAX,f,c The PH field, a “V” value, and a “P” value. The “V” value can indicate whether a PH value in the PH field corresponds to an actual transmission or a reference format. The “P” value can indicate whether a power backoff is applied due to power management.

[0067] Figure 3 is a diagram illustrating an example 300 of a multi-transmission reception point (mTRP) configuration, in accordance with the present disclosure.

[0068] As Figure 3 indicated, the mTRP transmission configuration can follow a multi-DCI based design. For example, a UE (e.g., UE 120a) can communicate with a first TRP (TRP-1) and a second TRP (TRP-2). The first TRP can transmit a first DCI to the UE via a first PDCCH (PDCCH 1). The first DCI can schedule a first PUSCH (PUSCH 1) for the UE. The second TRP can transmit a second DCI to the UE via a second PDCCH (PDCCH 2). The second DCI can schedule a second PUSCH (PUSCH 2) for the UE.

[0069] As indicated above, Figure 3 is provided as an example. Other examples can differ from what is described with respect to at least one example described Figure 3 with respect to at least one example described.

[0070] Figure 4 is a diagram illustrating an example 400 of a CORESET pool index value configuration, in accordance with the present disclosure.

[0071] A UE can distinguish between different TRPs based at least in part on a CORESET pool index value. A CORESET can be configured with a CORESET pool index value. A “CORESET” can refer to a set of physical resources within a particular region of a downlink resource grid. A CORESET can be used to carry a PDCCH (e.g., DCI). A “CORESET” can refer to a set of resource blocks and a set of OFDM symbols, which can be configurable with a corresponding PDCCH search space. CORESETs can provide configuration flexibility (including time, frequency, numerology, and operating point) for control regions to address a wide range of use cases. A CORESET pool index value can be 0 or 1, which can group CORESETs into two separate groups. The concept of different TRPs can also be transparent to the UE, in addition to separate CORESET pool index values that can be associated with different TRPs.

[0072] As shown in Figure 4 , a UE can be configured by a higher parameter PDCCH-Config, which can include two different CORESET pool index values in CORESETs for an active BWP of a serving cell. For example, a UE can be configured with a first CORESET pool index value (CORESETPoolIndex = 0). The first CORESET pool index value can be associated with two separate CORESET IDs (e.g., CORESET ID = 1 and CORESET ID = 2). The UE can be configured with a second CORESET pool index value (CORESETPoolIndex = 1). The second CORESET pool index value can be associated with two separate CORESET IDs (e.g., CORESET ID = 3 and CORESET ID = 4). The first CORESET pool index value can be associated with a first TRP, and the second CORESET pool index value can be associated with a second TRP.

[0073] A CORESET pool index value can be configured for each component carrier. For example, two component carriers can each be configured with two CORESET pool index values (mTRP). One component carrier can be configured with two CORESET pool index values (mTRP), while another component carrier can be configured with one CORESET pool index value (e.g., 0 or 1, corresponding to a first TRP or a second TRP, respectively), or can not be configured with a CORESET pool index value (e.g., a value of 0 can be assumed, which can indicate a first TRP).

[0074] As noted above, Figure 4 is provided as an example. Other examples can differ from what is described with respect to at least the following Figure 4The described examples.

[0075] A UE can not be configured to perform power headroom reporting for the case of uplink carrier aggregation, where the UE can be configured with multiple uplink component carriers, and a particular uplink component carrier can be configured with a particular CORESET pool index value. The multiple uplink component carriers can be configured for mTRP and / or single TRP (sTRP) transmissions. The UE can not be able to perform power headroom reporting on a per uplink component carrier basis and / or on a per CORESET pool index value basis. Thus, a base station receiving power headroom reports from the UE can not be aware of certain PHR information for the UE.

[0076] In various aspects of the technology and apparatus described herein, a UE can be configured to perform power headroom reporting for multiple uplink component carriers in an uplink carrier aggregation scenario (e.g., when the UE is configured with multiple uplink component carriers for uplink carrier aggregation). In some aspects, the UE can be configured to perform power headroom reporting with respect to one or more CORESET pool index values associated with the uplink component carriers. For example, the UE can be configured to perform power headroom reporting for certain CORESET pool index values (irrespective of the uplink component carrier associated with the CORESET pool index value). In some aspects, the UE can be configured to perform power headroom reporting on a per uplink component carrier basis, where PHR can be transmitted for a particular CORESET pool index value associated with a defined uplink component carrier. In some aspects, the UE can be configured to perform power headroom reporting on a per uplink component carrier basis for each CORESET pool index value. Thus, when the UE is configured to use multiple uplink component carriers in an uplink carrier aggregation scenario, the UE is able to transmit PHR to a base station.

[0077] Figure 5 FIG. 5 is a diagram illustrating an example 500 associated with power headroom reporting for uplink component carriers, in accordance with the present disclosure. As shown, the example 500 includes communication between a UE (e.g., the UE 120) and a base station (e.g., the base station 110). In some aspects, the UE and the base station can be included in a wireless network, such as the wireless network 100. The UE and the base station can communicate on a wireless access link, which can include uplink and downlink. Figure 5

[0078] ​As shown by reference number 502, the UE can detect an occurrence of a triggering event associated with a power headroom report. The power headroom report can be triggered separately for individual TRPs. The UE can detect the occurrence of the triggering event based at least in part on detecting an expiration of a periodic timer (phr-PeriodicTimer) or a prohibit timer (phr-ProhibitTimer). The prohibit timer can be maintained for each TRP and / or CORESET pool index value. The prohibit timer can not affect the triggering event for a power headroom report on another TRP and / or CORESET pool index value while running. The UE can detect the occurrence of the triggering event based at least in part on detecting a power change that satisfies a defined threshold for a path loss reference signal for power control of one or more uplink component carriers. The UE can detect the occurrence of the triggering event based at least in part on detecting an activation of one or more uplink component carriers. The UE can detect the occurrence of the triggering event based at least in part on detecting a change of an active BWP of a configured uplink component carrier from a dormant state to a non-dormant state.

[0079] As shown by reference number 504, the UE can transmit a PHR MAC-CE to the base station based at least in part on the occurrence of the triggering event. The PHR MAC-CE can be for one or more uplink component carriers of the UE associated with one or more CORESET pool index values.

[0080] In some aspects, the UE can transmit a PHR MAC-CE for uplink component carriers configured with a same CORESET pool index value. For example, the UE can be configured with multiple uplink component carriers, and a CORESET pool index value can be common for the multiple uplink component carriers. The PHR MAC-CE can be for an actual PHR corresponding to an actual PUSCH transmission, or the PHR MAC-C can be for a virtual PHR corresponding to a reference PUSCH transmission.

[0081] In some aspects, a size of a PHR MAC-CE corresponding to a CORESET pool index value (e.g., 0 or 1) can depend on a number of uplink component carriers configured with the CORESET pool index value.

[0082] For example, a UE can be configured with five uplink component carriers. The first and second uplink component carriers can be configured with both CORESET pool index values, the third and fourth uplink component carriers can be configured with CORESET pool index value 0, and the fifth uplink component carrier can be configured with CORESET pool index value 1. A PHR MAC-CE corresponding to CORESET pool index value 0 can include a bitmap of four bits with up to four fields for the corresponding uplink component carriers. A PHR MAC-CE corresponding to CORESET pool index value 1 can include a bitmap of three bits with up to three fields for the corresponding uplink component carriers.

[0083] In some aspects, a PHR MAC-CE can include a field indicating a CORESET pool index value associated with the PHR. In other words, the entire PHR MAC-CE can be associated with a first CORESET pool index value or a second CORESET pool index value. The PHR MAC-CE can be reported on PUSCHs associated with different CORESET pool index values (e.g., cross-TRP reporting). Alternatively, the PHR MAC-CE can be reported on PUSCHs associated with the CORESET pool index value to which the PHR MAC-CE corresponds (e.g., no cross-TRP reporting).

[0084] In some aspects, in a PHR MAC-CE, PHRs for some uplink component carriers can correspond to CORESET pool index value 0, while PHRs for other uplink component carriers can correspond to CORESET pool index value 1.

[0085] In some aspects, a PHR MAC-CE can be determined for each CORESET pool index value of one or more CORESET pool index values. For example, a PHR MAC-CE can be associated with a first CORESET pool index value or a second CORESET pool index value. Additionally, triggering of the PHR MAC-CE and reporting of the PHR MAC-CE can be determined separately at the UE. For example, a PHR MAC-CE can be triggered separately for separate CORESET pool index values.

[0086] As indicated above, Figure 5 are provided by way of example. Other examples can differ from those described Figure 5 without departing from the spirit of the disclosure.

[0087] Figure 6 is a diagram illustrating an example 600 associated with power headroom reporting for uplink component carriers, in accordance with the present disclosure. As Figure 6As shown, example 600 includes communications between a UE (e.g., UE 120) and a base station (e.g., base station 110). In some aspects, the UE and base station can be included in a wireless network, such as the wireless network 100. The UE and base station can communicate on a wireless access link, which can include uplink and downlink.

[0088] As shown by reference number 602, the UE can detect an occurrence of a triggering event associated with a power headroom report. The power headroom report can be triggered jointly for individual TRPs. The UE can detect the occurrence of the triggering event based at least in part on a timer, a change in power of a path loss reference signal, activation of an uplink component carrier, and / or a change from a dormant state to a non-dormant state of an active BWP.

[0089] As shown by reference number 604, the UE can transmit a PHR MAC-CE to the base station based at least in part on the occurrence of the triggering event. The PHR MAC-CE can be for one or more uplink component carriers of the UE associated with one or more CORESET pool index values. More specifically, the transmitted PHR MAC-CE can include one PHR per uplink component carrier.

[0090] In some aspects, a PHR MAC-CE can be transmitted on a first uplink shared channel (e.g., a first PUSCH) in a first uplink component carrier. A first PHR field corresponding to the first uplink carrier can be an actual PHR field. The presence of a second uplink shared channel (e.g., a second PUSCH) in a second uplink component carrier in the same slot as the first uplink shared channel that satisfies a timeline condition (when scheduled by DCI) can indicate that a second PHR field of the PHR MAC-CE corresponding to the second uplink component carrier is an actual PHR field. Alternatively, the absence of a second uplink shared channel in the second uplink component carrier in the same slot as the first uplink shared channel can indicate that the second PHR field of the PHR MAC-CE corresponding to the second uplink component carrier is a virtual PHR field. Additionally, if the second uplink shared channel in the second uplink component carrier is scheduled by DCI that does not satisfy the timeline condition, the second PHR field of the PHR MAC-CE corresponding to the second uplink component carrier can be a virtual PHR field even when the second uplink shared channel in the second uplink component carrier is in the same slot as the first uplink shared channel. The virtual PHR field can be associated with a first CORESET pool index value that is based on a set of reference parameters associated with the first CORESET pool index value. Alternatively, the virtual PHR field can be associated with a same CORESET pool index value that is associated with the first uplink shared channel using a corresponding set of reference parameters.

[0091] In some aspects, a PHR MAC-CE can be transmitted on a first uplink shared channel in a first uplink component carrier, and a first PHR field associated with the first uplink carrier can be an actual PHR field. A CORESET pool index value of a second PHR field of the PHR MAC-CE can correspond to a CORESET pool index value of the first uplink shared channel. The second PHR field can be an actual PHR field based at least in part on a presence of a second uplink shared channel in a second uplink component carrier in a same slot as the first uplink shared channel associated with the CORESET pool index value, and when a timeline condition is satisfied by DCI scheduling. Alternatively, the second PHR field can be a virtual PHR field based at least in part on an absence of the second uplink shared channel in the second uplink component carrier in the same slot as the first uplink shared channel associated with the CORESET pool index value. Additionally, if the second uplink shared channel in the second uplink component carrier is scheduled by DCI that does not satisfy the timeline condition, the second PHR field of the PHR MAC-CE corresponding to the second uplink component carrier can be a virtual PHR field even when the second uplink shared channel in the second uplink component carrier is in the same slot as the first uplink shared channel.

[0092] In some aspects, a PHR MAC-CE can indicate a first CORESET pool index value for a first uplink component carrier or a second CORESET set index value in a second uplink component carrier. In other words, the PHR MAC-CE can indicate a CORESET pool index value (e.g., 0 or 1) associated with a PHR for a given uplink component carrier in a field of the PHR MAC-CE corresponding to the given uplink component carrier.

[0093] In some aspects, the CORESET pool index value for each PHR field of a PHR MAC-CE can be different. For example, for a PHR field corresponding to a first uplink component carrier, the PHR can be for CORESET pool index value 0. For another PHR field corresponding to a second uplink component carrier, the PHR can be for CORESET pool index 1.

[0094] In some aspects, the PHR MAC-CE can be determined for a CORESET pool index value, and the CORESET pool index value associated with a PHR field in the MAC-CE can be determined for each uplink component carrier. A different CORESET pool index value can be associated with each PHR field in the MAC-CE. A first PHR field corresponding to a first uplink component carrier can be for a first CORESET pool index value. A second PHR field corresponding to a second uplink component carrier can be for a second CORESET pool index value. Additionally, a trigger of the PHR MAC-CE and a reporting of the PHR MAC-CE can be jointly determined at the UE. For example, the PHR MAC-CE can be jointly triggered across multiple CORESET pool index values.

[0095] In some aspects, the UE can not perform simultaneous PUSCH transmissions in the same uplink component carrier. In other words, the UE can perform time division multiplexing of PUSCHs in the same uplink component carrier.

[0096] As indicated above, Figure 6 are provided as examples. Other examples can differ from what is described with respect to at least one of the Figure 6 described examples.

[0097] Figure 7 is a diagram illustrating an example 700 associated with power headroom reporting for uplink component carriers, in accordance with the present disclosure. As shown in Figure 7 the example 700 includes communications between a UE (e.g., the UE 120) and a base station (e.g., the base station 110). In some aspects, the UE and the base station can be included in a wireless network, such as the wireless network 100. The UE and the base station can communicate on a wireless access link, which can include uplinks and downlinks.

[0098] As shown by reference number 702, the UE can detect an occurrence of a triggering event associated with a power headroom report. The power headroom report can be jointly triggered for separate TRPs. The UE can detect the occurrence of the triggering event based at least in part on a timer, a change in power of a pathloss reference signal, an activation of an uplink component carrier, and / or an active BWP changing from a dormant state to a non-dormant state.

[0099] As shown by reference number 704, the UE can transmit a PHR MAC-CE to the base station based at least in part on the occurrence of the triggering event. The PHR MAC-CE can be for one or more uplink component carriers of the UE that are associated with one or more CORESET pool index values. More specifically, the UE can transmit the PHR MAC-CE to include a separate PHR for each CORESET pool index value and each uplink component carrier. The PHR can be determined separately for each CORESET pool index value of each uplink component carrier, whether actual or virtual.

[0100] In some aspects, a maximum size of the PHR MAC-CE can be based at least in part on a number of uplink component carriers that are configured with two CORESET pool index values (e.g., 0 and 1).

[0101] In some aspects, the UE can transmit a bitmap in the PHR MAC-CE that indicates that the PHR is associated with one or more uplink component carriers or one or more CORESET pool index values. For example, the bitmap can include one bit to indicate whether a PHR is transmitted for a single uplink component carrier. In this case, for one bit, two PHR values can be reported for two CORESET pool index values. Alternatively, the bitmap can include two bits to indicate whether a PHR is transmitted separately for each CORESET pool index value.

[0102] In some aspects, the PHR MAC-CE can be determined for two CORESET pool index values and the PHR MAC-CE can include two PHR fields for uplink component carriers associated with the two CORESET pool index values. Additionally, a triggering of the PHR MAC-CE and a reporting of the PHR MAC-CE can be determined jointly at the UE. For example, the PHR MAC-CE can be triggered jointly across multiple CORESET pool index values.

[0103] In some aspects, the UE can perform simultaneous PUSCH transmissions in the same uplink component carrier. In other words, the UE can perform frequency-division multiplexing or spatial-division multiplexing of PUSCHs in the same uplink component carrier.

[0104] As indicated above, Figure 7 are provided by way of example. Other examples can differ from Figure 7 the examples described.

[0105] Figure 8This is a diagram illustrating an example procedure 800 performed by a UE, for example, according to this disclosure. Example procedure 800 is an example in which a UE (e.g., UE 120) performs operations associated with a power margin report for an uplink component carrier.

[0106] like Figure 8 As shown, in some aspects, process 800 may include detecting the occurrence of a triggering event associated with a power headroom report (block 810). For example, the UE (e.g., using antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, modulator 254, controller / processor 280 and / or memory 282) may detect the occurrence of a triggering event associated with a power headroom report, as described above in conjunction with... Figures 5-7 Described.

[0107] like Figure 8 Further, in some aspects, process 800 may include: transmitting a PHR MAC-CE from the UE to the base station at least in part based on the occurrence of a triggering event, wherein the PHR MAC-CE is for one or more uplink component carriers of the UE associated with one or more CORESET pool index values ​​(block 820). For example, the UE (e.g., using antenna 252, transmit processor 264, TX MIMO processor 266, modulator 254, controller / processor 280 and / or memory 282) may transmit a PHR MAC-CE from the UE to the base station at least in part based on the occurrence of a triggering event, wherein the PHR MAC-CE is for one or more uplink component carriers of the UE associated with one or more CORESET pool index values, as described above in conjunction with... Figures 5-7 Described.

[0108] Process 800 may include additional aspects, such as any single aspect or any combination thereof described below and / or in conjunction with one or more other process descriptions elsewhere described herein.

[0109] In the first aspect, a single CORESET pool index value is common to multiple uplink component carriers of the UE.

[0110] In the second aspect, either alone or in combination with the first aspect, the size of the PHRMAC-CE corresponding to the CORESET pool index value is at least partially based on the number of uplink component carriers configured with the CORESET pool index value.

[0111] In the third aspect, either alone or in combination with one or more of the first and second aspects, PHRMAC-CE indicates the associated CORESET pool index value.

[0112] In a fourth aspect, alone or in combination with one or more of the first through third aspects, transmitting the PHR MAC-CE includes transmitting the PHR MAC-CE on an uplink shared channel associated with a CORESET pool index value of the PHR MAC-CE.

[0113] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, transmitting the PHR MAC-CE includes transmitting the PHR MAC-CE on an uplink shared channel not associated with a CORESET pool index value of the PHR MAC-CE.

[0114] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the process 800 includes performing the uplink transmission based at least in part on time division multiplexing of the uplink shared channels in the one or more uplink component carriers.

[0115] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the PHR MAC-CE is transmitted on a first uplink shared channel in a first uplink component carrier, and a first PHR field associated with the first uplink carrier is an actual PHR field. An absence of a second uplink shared channel in a second uplink component carrier in a same time slot as the first uplink shared channel indicates a second PHR field of a PHR MAC-CE corresponding to the second uplink component carrier is a virtual PHR field. A presence of the second uplink shared channel in the second uplink component carrier in the same time slot as the first uplink shared channel indicates the second PHR field of the PHR MAC-CE corresponding to the second uplink component carrier is an actual PHR field. The virtual PHR field is associated with a first CORESET pool index value based on a set of reference parameters associated with the first CORESET pool index value, or the virtual PHR field is associated with a same CORESET pool index value as associated with the first uplink shared channel.

[0116] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the process 800 includes determining whether a PHR field in a PHR MAC-CE is associated with an actual PHR or a virtual PHR, and determining one or more CORESET pool index values to be associated with the PHR field in the PHR MAC-CE based at least in part on whether the PHR field in the PHR MAC-CE is associated with the actual PHR or the virtual PHR.

[0117] In a ninth aspect, alone or in combination with one or more of the first through seventh aspects, the process 800 includes determining one or more CORESET pool index values to be associated with the PHR field in the PHR MAC-CE and determining, based at least in part on the one or more CORESET pool index values to be associated with the PHR field in the PHR MAC-CE, whether the PHR field in the PHR MAC-CE is associated with an actual PHR or a virtual PHR.

[0118] In a tenth aspect, alone or in combination with one or more of the first through seventh aspects, the PHR MAC-CE is transmitted on a first uplink shared channel in a first uplink component carrier and a first PHR field associated with the first uplink carrier is an actual PHR field. A CORESET pool index value of a second PHR field of the PHR MAC-CE corresponds to a CORESET pool index value of the first uplink shared channel and the second PHR field is an actual PHR field based at least in part on a presence of a second uplink shared channel in a second uplink component carrier in a same slot as the first uplink shared channel associated with the CORESET pool index value. The second PHR field is a virtual PHR field based at least in part on an absence of the second uplink shared channel in the second uplink component carrier in the same slot as the first uplink shared channel associated with the CORESET pool index value.

[0119] In an eleventh aspect, alone or in combination with one or more of the first through eighth aspects, the PHR MAC-CE indicates a first CORESET pool index value of the first uplink component carrier or a second CORESET pool index value of the second uplink component carrier.

[0120] In a twelfth aspect, alone or in combination with one or more of the first through ninth aspects, the process 800 includes performing uplink transmissions based at least in part on frequency division multiplexing or spatial division multiplexing of uplink shared channels in the one or more uplink component carriers.

[0121] In a thirteenth aspect, alone or in combination with one or more of the first through tenth aspects, a maximum size of the PHR MAC-CE is based at least in part on a number of uplink component carriers configured with two CORESET pool index values.

[0122] In a fourteenth aspect, alone or in combination with one or more of the first through eleventh aspects, transmitting the PHR MAC-CE includes transmitting a bitmap that indicates that the PHR is associated with one or more uplink component carriers or one or more CORESET pool index values, and the bitmap includes one bit to indicate whether the PHR is transmitted for a single uplink component carrier or the bitmap includes two bits to indicate whether the PHR is transmitted individually for each of the one or more CORESET pool index values.

[0123] In a fifteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the PHR MAC-CE is triggered individually for separate CORESET pool index values or the PHR MAC-CE is triggered jointly across multiple CORESET pool index values.

[0124] In a sixteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the PHR MAC-CE is determined for each of the one or more CORESET pool index values, and the PHR MAC-CE is associated with a first CORESET pool index value or a second CORESET pool index value, and triggering of the PHR MAC-CE and reporting of the PHR MAC-CE are determined individually at the UE.

[0125] In a seventeenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the PHR MAC-CE is determined for the one or more CORESET pool index values, and a CORESET pool index value associated with a PHR field in the MAC-CE is determined for each of the one or more uplink component carriers. Different CORESET pool index values are associated with each PHR field in the MAC-CE, and a first PHR field corresponding to a first uplink component carrier is for a first CORESET pool index value. A second PHR field corresponding to a second uplink component carrier is for a second CORESET pool index value. Triggering of the PHR MAC-CE and reporting of the PHR MAC-CE are determined jointly at the UE.

[0126] In an eighteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the PHR MAC-CE is determined for one or more CORESET pool index values, the PHR MAC-CE includes two PHR fields for uplink component carriers associated with two CORESET pool index values, and the triggering of the PHR MAC-CE and the reporting of the PHR MAC-CE are determined jointly at the UE.

[0127] In a nineteenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the one or more CORESET pool index values include one or more of a first value or a second value, and the first value corresponds to a first transmission reception point and the second value corresponds to a second transmission reception point.

[0128] In a twentieth aspect, alone or in combination with one or more of the first through seventeenth aspects, detecting the occurrence of the triggering event includes detecting an expiration of a periodic timer or a prohibit timer, detecting a power change that satisfies a defined threshold for a path loss reference signal for power control for the one or more uplink component carriers, detecting an activation of the one or more uplink component carriers, or detecting a change of an active bandwidth part of a configured uplink component carrier from a dormant state to a non-dormant state.

[0129] Although Figure 8 Example blocks of the process 800 are illustrated, but in some aspects, the process 800 can include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Figure 8 In addition or as an alternative, two or more of the blocks of the process 800 can be performed in parallel.

[0130] Figure 9 is a block diagram of an example apparatus 900 for wireless communication. The apparatus 900 can be a UE, or a UE can include the apparatus 900. In some aspects, the apparatus 900 includes a reception component 902 and a transmission component 904, which can be in communication with one another (for example, via one or more buses and / or one or more other components). As shown, the apparatus 900 can communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using the reception component 902 and the transmission component 904. As further shown, the apparatus 900 can include a detection component 908, among other examples.

[0131] In some aspects, the apparatus 900 can be configured to perform one or more operations described herein with reference to Figures 5-7 one or more processes described herein. Additionally or alternatively, the apparatus 900 can be configured to perform one or more processes described herein, such as process 800. Figure 8FIG. 8, in accordance with some aspects of the present disclosure. In some aspects, Figure 9 The apparatus 900 and / or one or more components thereof illustrated in FIG. 9 can include means for performing one or more of the functions described herein. For example, the means for receiving can include the antenna, demodulator, MIMO detector, receive processor, controller / processor, memory, or Figure 2 one or more components of the UE described above. Additionally or alternatively, one or more components of the set of components can be implemented at least in part as software stored in memory. Figure 9 one or more components of the UE described above. Additionally or alternatively, one or more components of the set of components can be implemented at least in part as software stored in memory. Figure 2 one or more components of the UE described above. Additionally or alternatively, one or more components of the set of components can be implemented at least in part as software stored in memory.

[0132] The reception component 902 can receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 906. The reception component 902 can provide received communications to one or more other components of the apparatus 900. In some aspects, the reception component 902 can perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and can provide the processed signals to the one or more other components of the apparatus 906. In some aspects, the reception component 902 can include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the UE described above in connection with Figure 2 the reception component 902 can include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the UE described above in connection with

[0133] The transmission component 904 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 906. In some aspects, one or more other components of the apparatus 906 can generate communications and can provide the generated communications to the transmission component 904 for transmission to the apparatus 906. In some aspects, the transmission component 904 can perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and can transmit the processed signals to the apparatus 906. In some aspects, the transmission component 904 can include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the UE described above in connection with Figure 2 the transmission component 904 can include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of the UE described above in connection with

[0134] The detection component 908 can detect an occurrence of a triggering event associated with a power headroom report. In some aspects, the detection component 908 can include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof, of the UE described above in connection with Figure 2The one or more antennas, demodulators, MIMO detector, receive processor, modulators, transmit MIMO processor, transmit processor, controller / processor, memory, or combination thereof of the described UE. The transmission component 904 can transmit, from the UE to the base station, a PHR MAC-CE based at least in part on the occurrence of the triggering event, where the PHR MAC-CE is for one or more uplink component carriers of the UE that are associated with one or more CORESET pool index values.

[0135] Figure 9 The number and arrangement of components shown is provided as an example. In practice, there can be additional components, fewer components, different components, or differently arranged components than those shown. Figure 9 than those shown. Additionally or alternatively, Figure 9 Two or more of the components shown can be implemented within a single component, or Figure 9 A single component shown can be implemented as multiple, distributed components. Additionally or alternatively, Figure 9 A set of one or more components shown can be configured to perform one or more functions described as being performed by another set of one or more components shown. Figure 9 one or more functions described as being performed by another set of components.

[0136] The following provides a summary of some aspects of the present disclosure:

[0137] Aspect 1 : A method of wireless communication performed by a user equipment (UE), comprising: detecting an occurrence of a triggering event associated with a power headroom report; and transmitting, from the UE to a base station, a power headroom report (PHR) medium access control (MAC) control element (CE) based at least in part on the occurrence of the triggering event, where the PHR MAC-CE is for one or more uplink component carriers of the UE that are associated with one or more control resource set (CORESET) pool index values.

[0138] Aspect 2: The method of aspect 1, wherein a single CORESET pool index value is common for multiple uplink component carriers of the UE.

[0139] Aspect 3: The method of any of aspects 1-2, wherein a size of the PHR MAC-CE corresponding to a CORESET pool index value is based at least in part on a number of uplink component carriers configured with the CORESET pool index value.

[0140] Aspect 4: The method of any of aspects 1-3, wherein the PHR MAC-CE indicates an associated CORESET pool index value.

[0141] Aspect 5: The method of any of aspects 1 through 4, wherein transmitting the PHR MAC-CE comprises: transmitting the PHR MAC-CE on an uplink shared channel associated with a CORESET pool index value of the PHR MAC-CE.

[0142] Aspect 6: The method of any of aspects 1 through 5, wherein transmitting the PHR MAC-CE comprises: transmitting the PHR MAC-CE on an uplink shared channel not associated with a CORESET pool index value of the PHR MAC-CE.

[0143] Aspect 7: The method of any of aspects 1 through 6, further comprising: performing uplink transmissions based at least in part on time division multiplexing of uplink shared channels in the one or more uplink component carriers.

[0144] Aspect 8: The method of any of aspects 1 through 7, further comprising: determining whether a PHR field in the PHR MAC-CE is associated with an actual PHR or a virtual PHR; and determining the one or more CORESET pool index values to be associated with the PHR field in the PHR MAC-CE based at least in part on whether the PHR field in the PHR MAC-CE is associated with the actual PHR or the virtual PHR.

[0145] Aspect 9: The method of any of aspects 1 through 8, further comprising: determining the one or more CORESET pool index values to be associated with a PHR field in the PHR MAC-CE; and determining whether the PHR field in the PHR MAC-CE is associated with an actual PHR or a virtual PHR based at least in part on the one or more CORESET pool index values to be associated with the PHR field in the PHR MAC-CE.

[0146] Aspect 10: The method of any of aspects 1 through 9, wherein the PHR MAC-CE is transmitted on a first uplink shared channel in a first uplink component carrier, and a first PHR field associated with the first uplink carrier is an actual PHR field, and wherein a presence of a second uplink shared channel in a second uplink component carrier in a same slot as the first uplink shared channel indicates a second PHR field of the PHR MAC-CE corresponding to the second uplink component carrier is an actual PHR field, and wherein an absence of the second uplink shared channel in the second uplink component carrier in the same slot as the first uplink shared channel indicates the second PHR field of the PHR MAC-CE corresponding to the second uplink component carrier is a virtual PHR field, wherein the virtual PHR field is associated with a first CORESET pool index value based on a set of reference parameters associated with the first CORESET pool index value or the virtual PHR field is associated with a same CORESET pool index value associated with the first uplink shared channel.

[0147] Aspect 11: The method of any of aspects 1 through 10, wherein the PHR MAC-CE is transmitted on a first uplink shared channel in a first uplink component carrier, and a first PHR field associated with the first uplink carrier is an actual PHR field, and wherein a CORESET pool index value of a second PHR field of the PHR MAC-CE corresponds to a CORESET pool index value of the first uplink shared channel, wherein the second PHR field is an actual PHR field based at least in part on a presence of a second uplink shared channel in a second uplink component carrier in a same slot as the first uplink shared channel associated with the CORESET pool index value, or wherein the second PHR field is a virtual PHR field based at least in part on an absence of the second uplink shared channel in the second uplink component carrier in the same slot as the first uplink shared channel associated with the CORESET pool index value.

[0148] Aspect 12: The method of any of aspects 1 through 11, wherein the PHR MAC-CE indicates a first CORESET pool index value for a first uplink component carrier or a second CORESET pool index value for a second uplink component carrier.

[0149] Aspect 13: The method of any of aspects 1 through 12, further comprising: performing uplink transmissions based at least in part on a frequency division multiplexing or a spatial division multiplexing of an uplink shared channel in the one or more uplink component carriers.

[0150] Aspect 14: The method of any of aspects 1 through 13, wherein a maximum size of the PHR MAC-CE is based at least in part on a number of uplink component carriers configured with two CORESET pool index values.

[0151] Aspect 15: The method of any of aspects 1 through 14, wherein transmitting the PHR MAC-CE comprises: transmitting a bitmap indicating a PHR is associated with the one or more uplink component carriers or the one or more CORESET pool index values, wherein the bitmap includes one bit to indicate whether the PHR is transmitted for a single uplink component carrier or wherein the bitmap includes two bits to indicate whether the PHR is transmitted individually for each of the one or more CORESET pool index values.

[0152] Aspect 16: The method of any of aspects 1 through 15, wherein transmitting the PHR MAC-CE is triggered individually for individual CORESET pool index values; or transmitting the PHR MAC-CE is triggered jointly across multiple CORESET pool index values.

[0153] Aspect 17: The method of any of aspects 1 through 16, wherein the PHR MAC-CE is determined for each of the one or more CORESET pool index values, wherein the PHR MAC-CE is associated with a first CORESET pool index value or a second CORESET pool index value, and wherein a triggering of the PHR MAC-CE and a reporting of the PHR MAC-CE are determined individually at the UE.

[0154] Aspect 18: The method of any of aspects 1-17, wherein the PHR MAC-CE is determined for the one or more CORESET pool index values, and a CORESET pool index value associated with a PHR field in the PHR MAC-CE is determined for each of the one or more uplink component carriers, wherein a different CORESET pool index value is associated with each PHR field in the PHR MAC-CE, wherein a first PHR field corresponding to a first uplink component carrier is for a first CORESET pool index value, and a second PHR field corresponding to a second uplink component carrier is for a second CORESET pool index value, and wherein a triggering of the PHR MAC-CE and a reporting of the PHR MAC-CE are determined jointly at the UE.

[0155] Aspect 19: The method of any of aspects 1-18, wherein the PHR MAC-CE is determined for the one or more CORESET pool index values, wherein the PHR MAC-CE includes two PHR fields for uplink component carriers associated with two CORESET pool index values, and wherein a triggering of the PHR MAC-CE and a reporting of the PHR MAC-CE are determined jointly at the UE.

[0156] Aspect 20: The method of any of aspects 1-19, wherein the one or more CORESET pool index values include one or more of a first value or a second value, and wherein the first value corresponds to a first transmission reception point and the second value corresponds to a second transmission reception point.

[0157] Aspect 21: The method of any of aspects 1-20, wherein detecting the occurrence of the triggering event comprises: detecting an expiration of a periodic timer or a prohibit timer; detecting a power change that satisfies a defined threshold for a path loss reference signal for power control for the one or more uplink component carriers; detecting an activation of the one or more uplink component carriers; or detecting a change of an active bandwidth part of a configured uplink component carrier from a dormant state to a non-dormant state.

[0158] Aspect 22: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of aspects 1-21.

[0159] Aspect 23: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-21.

[0160] Aspect 24: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-21.

[0161] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-21.

[0162] Aspect 26: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of an apparatus, cause the apparatus to perform the method of one or more of Aspects 1-21.

[0163] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations can be possible in light of the above disclosure or from practice of the aspects.

[0164] As used herein, the term “component” is intended to be broadly interpreted to encompass hardware and / or a combination of hardware and software. “Software” shall be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a processor is implemented in hardware and / or a combination of hardware and software. It will be apparent that systems and / or methods described herein can be implemented in different forms of hardware and / or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and / or methods were described herein without reference to specific software code — because software and hardware can be designed to implement the systems and / or methods based, at least in part, on the description herein.

[0165] As used herein, depending on the context, “satisfies a threshold” can refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, and / or the like.

[0166] Even if a particular feature is expressly identified as an aspect in a claim, among other places, such disclosure simply ensures that that feature is dismissed and does not mean that no other aspects can include the particular feature. It is possible that any aspect can include one or more of the disclosed features, alone or in combination with other features. The disclosure of a reference in an aspect does not constitute an admission that the, reference is prior art to the aspect. To the extent that there is any conflict between the instant disclosure and that of any reference, the instant disclosure will control. In cases of conflict, a document's disclosure will be considered to end just after any header, subheader, embodiment, example, or other section or paragraph that can have been used to introduce material.

[0167] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and can be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items, and can be used interchangeably with “the one or more.” Also, as used herein, the terms “set” and “group” are intended to include one or more items, and can be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms that do not limit any element to the presence of only a single instance of the element. Rather, the terms “has,” “have,” “having” or the like are intended to mean one or more instances of the element, which is open-ended and does not exclude there being only one of the elements or a singular instance of the element. Furthermore, as used herein, the term “or” is intended to be inclusive when used in a list of items, and can be used interchangeably with “and / or,” unless otherwise indicated or required by context.

Claims

1. A user equipment (UE), comprising: one or more transceivers; one or more memories including instructions; and one or more processors configured to execute the instructions and cause the UE to: detect an occurrence of a triggering event associated with a power headroom report, the triggering event corresponding to one or more uplink component carriers of the UE, the one or more uplink component carriers being associated with one or more control resource set (CORESET) pool index values, wherein each of the one or more CORESET pool index values is associated with a different transmission reception point (TRP); and based at least in part on the occurrence of the triggering event, transmit, via the one or more transceivers, a power headroom report (PHR) medium access control (MAC) control element (CE), wherein the PHR MAC-CE includes a power headroom of each of the one or more uplink component carriers of the UE, and wherein a size of the PHR MAC-CE is based at least in part on a number of one or more uplink component carriers configured with two CORESET pool index values.

2. The UE of claim 1, wherein, a single CORESET pool index value of the one or more CORESET pool index values is common to a plurality of uplink component carriers of the UE.

3. The UE of claim 1, wherein, the PHR MAC-CE indicates an associated CORESET pool index value.

4. The UE of claim 1, wherein, the PHR MAC-CE is transmitted on an uplink shared channel associated with a CORESET pool index value of the PHR MAC-CE.

5. The UE of claim 1, wherein, the PHR MAC-CE is transmitted on an uplink shared channel not associated with a CORESET pool index value of the PHR MAC-CE.

6. The UE of claim 1, wherein, the one or more processors are further configured to cause the UE to: perform uplink transmissions based at least in part on time division multiplexing of uplink shared channels in the one or more uplink component carriers.

7. The UE of claim 1, wherein, a PHR field in the PHR MAC-CE is associated with an actual PHR or with a virtual PHR; and the one or more CORESET pool index values to be associated with the PHR field in the PHR MAC-CE is based at least in part on whether the PHR field in the PHR MAC-CE is associated with the actual PHR or the virtual PHR.

8. The UE of claim 1, wherein, the PHR MAC-CE is based at least in part on: the one or more CORESET pool index values to be associated with a PHR field in the PHR MAC-CE; and the PHR field in the PHR MAC-CE. The PHR field in the PHR MAC-CE is associated with one of an actual PHR or a virtual PHR, where whether the PHR field in the PHR MAC-CE is associated with the actual PHR or the one of the virtual PHR is based at least in part on the one or more CORESET pool index values to be associated with the PHR field in the PHR MAC-CE.

9. The UE of claim 1, wherein, At least one of: The PHR MAC-CE is transmitted on a first uplink shared channel in a first uplink component carrier of the one or more uplink component carriers, and a first PHR field associated with the first uplink component carrier is an actual PHR field, or A second uplink shared channel in a second uplink component carrier of the one or more uplink component carriers in a same slot as the first uplink shared channel indicates a second PHR field of the PHR MAC-CE corresponding to the second uplink component carrier is an actual PHR field, or An absence of the second uplink shared channel in the second uplink component carrier in the same slot as the first uplink shared channel indicates the second PHR field of the PHR MAC-CE corresponding to the second uplink component carrier is a virtual PHR field; and where the virtual PHR field is associated with a first CORESET pool index value, where the first CORESET pool index value is based at least in part on a set of reference parameters, or The virtual PHR field is associated with a same CORESET pool index value associated with the first uplink shared channel.

10. The UE of claim 1, wherein, At least one of: The PHR MAC-CE is transmitted on a first uplink shared channel in a first uplink component carrier of the one or more uplink component carriers, and a first PHR field associated with the first uplink component carrier is an actual PHR field, or A CORESET pool index value of a second PHR field of the PHR MAC-CE corresponds to a CORESET pool index value of the first uplink shared channel, and at least one of: The second PHR field is an actual PHR field based at least in part on a presence of a second uplink shared channel in a second uplink component carrier of the one or more uplink component carriers in a same slot as the first uplink shared channel associated with the CORESET pool index value, or The second PHR field is a virtual PHR field based at least in part on an absence of the second uplink shared channel in the second uplink component carrier in the same slot as the first uplink shared channel associated with the CORESET pool index value.

11. The UE of claim 1, wherein, The PHR MAC-CE indicates a first CORESET pool index value of the one or more CORESET pool index values for a first uplink component carrier or a second CORESET pool index value of the one or more CORESET pool index values for a second uplink component carrier.

12. The UE of claim 1, wherein, The one or more processors are further configured to cause the UE to: perform uplink transmissions based at least in part on frequency-division multiplexing or spatial-division multiplexing of uplink shared channels in the one or more uplink component carriers.

13. The UE of claim 1, wherein, The PHR MAC-CE further includes a bitmap indicating that a PHR is associated with the one or more uplink component carriers or the one or more CORESET pool index values, and at least one of: the bitmap includes one bit to indicate that the PHR corresponds to a single uplink component carrier, or the bitmap includes two bits to indicate that the PHR corresponds to separate CORESET pool index values of the one or more CORESET pool index values.

14. The UE of claim 1, wherein: the PHR MAC-CE is triggered individually for separate CORESET pool index values of the one or more CORESET pool index values; or the PHR MAC-CE is triggered jointly across multiple CORESET pool index values.

15. The UE of claim 1, wherein, at least one of: the PHR MAC-CE is based at least in part on each CORESET pool index value of the one or more CORESET pool index values, the PHR MAC-CE is associated with a first CORESET pool index value or a second CORESET pool index value of the one or more CORESET pool index values, or the triggering of the PHR MAC-CE and the reporting of the PHR MAC-CE are triggered individually at the UE.

16. The UE of claim 1, wherein: the PHR MAC-CE is based at least in part on the one or more CORESET pool index values, and the CORESET pool index values associated with PHR fields in the PHR MAC-CE are based at least in part on a per uplink component carrier basis of the one or more uplink component carriers, and different CORESET pool index values are associated with each PHR field in the PHR MAC-CE, and a first PHR field corresponding to a first uplink component carrier is for a first CORESET pool index value, and a second PHR field corresponding to a second uplink component carrier is for a second CORESET pool index value, and the triggering of the PHR MAC-CE and the reporting of the PHR MAC-CE are triggered jointly at the UE.

17. The UE of claim 1, wherein: the PHR MAC-CE is based at least in part on the one or more CORESET pool index values, wherein: the PHR MAC-CE is associated with a first CORESET pool index value or a second CORESET pool index value of the one or more CORESET pool index values, or the triggering of the PHR MAC-CE and the reporting of the PHR MAC-CE are triggered individually at the UE. the PHR MAC-CE includes two PHR fields for uplink component carriers associated with two CORESET pool index values, and the triggering of the PHR MAC-CE and the reporting of the PHR MAC-CE are jointly triggered at the UE.

18. The UE of claim 1, wherein, the one or more CORESET pool index values include one or more of a first value and a second value, and the first value corresponds to a first transmission reception point and the second value corresponds to a second transmission reception point.

19. The UE of claim 1, wherein, when detecting the occurrence of the triggering event, the one or more processors are configured to cause the UE to: detect an expiration of a periodic timer or a prohibit timer; detect a power change that satisfies a defined threshold for a path loss reference signal for power control for the one or more uplink component carriers; detect an activation of the one or more uplink component carriers; or detect a change in an active bandwidth part of a configured uplink component carrier from a dormant state to a non-dormant state.

20. A method of wireless communication performed at a user equipment (UE), comprising: detecting an occurrence of a triggering event associated with a power headroom report, the triggering event corresponding to one or more uplink component carriers of the UE, the one or more uplink component carriers being associated with one or more control resource set (CORESET) pool index values, wherein the one or more CORESET pool index values are each associated with a different transmission reception point (TRP); and transmitting, based at least in part on the occurrence of the triggering event, a power headroom report (PHR) medium access control (MAC) control element (CE), wherein the PHR MAC-CE includes a power headroom for each of the one or more uplink component carriers of the UE, and wherein a size of the PHR MAC-CE is based at least in part on a number of uplink component carriers configured with two CORESET pool index values.

21. The method of claim 20, wherein: a single CORESET pool index value of the one or more CORESET pool index values is common to multiple uplink component carriers of the UE; the PHR MAC-CE indicates an associated CORESET pool index value.

22. The method of claim 20, wherein, transmitting the PHR MAC-CE includes: transmitting the PHR MAC-CE on an uplink shared channel that is not associated with a CORESET pool index value of the PHR MAC-CE.

23. The method of claim 20, wherein, the PHR MAC-CE indicates a first CORESET pool index value of the one or more CORESET pool index values for a first uplink component carrier or a second CORESET pool index value of the one or more CORESET pool index values for a second uplink component carrier.

24. The method of claim 20, wherein, detecting the occurrence of the triggering event further includes: detecting an expiration of a periodic timer or a prohibit timer; detecting a power change that satisfies a defined threshold of a pathloss reference signal for power control of the one or more uplink component carriers; detecting activation of the one or more uplink component carriers; or detecting a change of an active bandwidth part of a configured uplink component carrier from a dormant state to a non-dormant state.

25. A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising: one or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to: detect an occurrence of a triggering event associated with a power headroom report, the triggering event corresponding to one or more uplink component carriers of the UE, the one or more uplink component carriers being associated with one or more control resource set (CORESET) pool index values, wherein the one or more CORESET pool index values are each associated with a different transmission reception point (TRP); and transmit, based at least in part on the occurrence of the triggering event, a power headroom report (PHR) medium access control (MAC) control element (CE), wherein the PHR MAC-CE includes a power headroom of each of the one or more uplink component carriers of the UE, and wherein a size of the PHR MAC-CE is based at least in part on a number of uplink component carriers configured with two CORESET pool index values.

26. The non-transitory computer-readable medium of claim 25, wherein: a single CORESET pool index value of the one or more CORESET pool index values is common to multiple uplink component carriers of the UE; or the PHR MAC-CE indicates an associated CORESET pool index value.

27. The non-transitory computer-readable medium of claim 25, wherein, the one or more instructions that cause the UE to transmit the PHR MAC-CE cause the UE to: transmit the PHR MAC-CE on an uplink shared channel associated with a CORESET pool index value of the PHR MAC-CE.

28. A user equipment (UE), comprising: means for detecting an occurrence of a triggering event associated with a power headroom report, the triggering event corresponding to one or more uplink component carriers of the UE, the one or more uplink component carriers being associated with one or more control resource set (CORESET) pool index values, wherein the one or more CORESET pool index values are each associated with a different transmission reception point (TRP); and means for transmitting, based at least in part on the occurrence of the triggering event, a power headroom report (PHR) medium access control (MAC) control element (CE), wherein the PHR MAC-CE includes a power headroom of each of the one or more uplink component carriers of the UE, and wherein a size of the PHR MAC-CE is based at least in part on a number of uplink component carriers configured with two CORESET pool index values. a means for transmitting a power headroom report (PHR) medium access control (MAC) control element (CE) based at least in part on an occurrence of the trigger event, wherein the PHR MAC-CE includes a power headroom for each of the one or more uplink component carriers of the UE, and wherein a size of the PHR MAC-CE is based at least in part on a number of uplink component carriers configured with two CORESET pool index values.

29. The UE of claim 28, wherein: a single CORESET pool index value of the one or more CORESET pool index values is common to multiple uplink component carriers of the UE; or the PHR MAC-CE indicates an associated CORESET pool index value.

30. The UE of claim 28, wherein, the means for transmitting the PHR MAC-CE comprises: a means for transmitting the PHR MAC-CE on an uplink shared channel that is not associated with a CORESET pool index value of the PHR MAC-CE.

Images