Power Headroom Reporting Enhancements

By introducing an enhanced power headroom reporting mechanism in the wireless communication system, the power improvement of low-latency communication is supported, and the detection problem of overlapping MBB transmission and low-latency transmission resources is solved, and the reception quality and system efficiency are improved.

CN114557053BActive Publication Date: 2024-11-12QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080057344.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-08-06
Filing Date
2020-08-07
Publication Date
2024-11-12
Estimated Expiration
2040-08-07

AI Technical Summary

Technical Problem

When existing wireless communication systems support multiple service types, it is difficult to effectively enhance the detection of uplink low-latency transmission, especially when MBB transmission overlaps with low-latency transmission resources, resulting in interference affecting the reception quality.

Method used

By introducing an enhanced power headroom reporting mechanism in the wireless communication system, user equipment (UE) allows to detect and send power boost information according to service type, including maximum transmission power, actual transmission power and power boost values, to support low-latency communication Power increase. This mechanism uses different power control loops and trigger event configurations to optimize power reporting to suit the needs of different service types.

Benefits of technology

Improves detection capability for uplink low-latency transmission, reduces interference impact, enhances reception quality, and improves system efficiency and throughput throughput through dynamic power management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114557053B_ABST
    Figure CN114557053B_ABST
Patent Text Reader

Abstract

Methods, systems, and devices for wireless communications are described. A user equipment (UE) may identify a trigger event configuration for a power headroom report for a first service type, the first service type having a lower latency condition and a higher reliability condition than a second service type. For example, the first service type may be for low latency communications, and the second service type may be for mobile broadband (MBB) communications. The UE may detect a trigger event for a power headroom report for the first service type based on the trigger event configuration. The UE may send a power headroom report for the first service type based on detecting the trigger event. By sending the power headroom report for the first service type, the UE may indicate whether a power boost for the first service type is available.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims the benefit of U.S. Provisional Patent Application No. 62 / 888,264, filed on August 16, 2019, by Yang et al., entitled “Power Headroom Report Enhancement”; and U.S. Patent Application No. 16 / 987,047, filed on August 6, 2020, by Yang et al., entitled “Power Headroom Report Enhancement”; each of which is assigned to its assignee. Technical Field

[0003] The following relates generally to wireless communications, and more particularly to power headroom reporting enhancements. Background Art

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

[0005] A wireless communication system may support wireless communications of different service types. Some different service types may have different reliability, delay, and power configurations. Some conventional techniques for configuring uplink transmissions of different service types may be improved. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices and apparatuses for supporting power headroom reporting enhancement. In general, the described technology provides for generating a power headroom report for a cell based on the service type of communication supported by the cell. A wireless communication system may support a variety of different service types. For example, a wireless communication system may support mobile broadband (MBB) communication and low-latency communication, which may have more stringent delay and reliability conditions. In some cases, a base station of a wireless communication system may schedule a user equipment (UE) to perform uplink low-latency transmission on resources that overlap with other uplink MBB transmissions, such as from other UEs. Uplink MBB transmissions generally have a higher transmit power, which may affect (e.g., interfere with) the reception of uplink low-latency transmissions at the base station. In order to enhance the detection of uplink low-latency transmissions, the wireless communication system may support the UE to perform power boosting on the uplink low-latency transmission. For example, when low-latency resources overlap with MBB resources, the UE may increase the transmit power for uplink low-latency transmissions.

[0007] The techniques described herein support enhanced power headroom reporting to support power boosting for low-latency communications. For example, a power headroom report for an uplink carrier may indicate whether a UE can perform power boosting for low-latency communications based on the maximum transmit power, actual transmit power (e.g., without boosting) and maximum power boost value of the uplink carrier. In some cases, the UE may be configured with parameters for generating a power headroom report and triggering it based on low-latency communications. For example, whenever a power boost function is configured or reconfigured, the UE may be triggered to generate a power headroom report. In some examples, the UE may have an additional threshold for generating a power headroom report for low-latency communications, which may be different from a threshold for generating a conventional power headroom report or a power headroom report for MBB communications. For example, by using a first power control loop for low-latency communications and a second power control loop for MBB communications, additional techniques are used to use a power loop for a specific service type. For example, the UE may include corresponding fields for the first power control loop and the second power control loop in a power headroom report.

[0008] A method for wireless communication by a UE is described. The method may include: detecting a triggering event for a power headroom report for a first service type, the first service type having a lower latency condition and a higher reliability condition than a second service type; and sending a power headroom report for the first service type based on detecting the triggering event. In some examples, the method may include: identifying a triggering event configuration for a power headroom report for the first service type.

[0009] An apparatus for wireless communication by a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: detect a triggering event for a power headroom report for a first service type, the first service type having a lower latency condition and a higher reliability condition than a second service type; and send a power headroom report for the first service type based on detecting the triggering event. In some examples, the instructions may be executed by the processor to cause the apparatus to: identify a triggering event configuration for a power headroom report for the first service type.

[0010] An apparatus for wireless communication by a UE is described. The apparatus may include components for performing the following operations: detecting a triggering event for a power headroom report for a first service type, the first service type having a lower latency condition and a higher reliability condition than a second service type; and sending a power headroom report for the first service type based on detecting the triggering event. In some examples, the apparatus may include components for identifying a triggering event configuration for a power headroom report for the first service type.

[0011] A non-transitory computer-readable medium is described that stores code for wireless communication by a UE. The code may include instructions executable by a processor to: detect a triggering event for a power headroom report for a first service type, the first service type having a lower latency condition and a higher reliability condition than a second service type; and send a power headroom report for the first service type based on detecting the triggering event. In some examples, the code may include instructions executable by a processor to: identify a triggering event configuration for a power headroom report for the first service type.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying a trigger event configuration may include operations, features, components, or instructions for receiving the trigger event configuration from a base station.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying a trigger event configuration may include an operation, feature, means, or instruction for retrieving the trigger event configuration from a storage device of the UE.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying a trigger event configuration may include operations, features, components, or instructions for identifying a trigger event configuration for a first service type, the trigger event configuration indicating that a trigger event is to be detected based on receiving a power boost function configuration or a power boost function reconfiguration for the first service type.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying a trigger event configuration may include operations, features, components, or instructions for identifying a trigger event configuration for a first service type, the trigger event configuration indicating that a trigger event is to be detected based on detecting that the UE lacks sufficient margin for power boosting for the first service type and based on detecting that a prohibit timer at the UE may have expired.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying a trigger event configuration may include operations, features, components, or instructions for identifying a trigger event configuration for a first service type, the trigger event configuration indicating that a trigger event is to be detected based on detecting that the UE has transitioned from lacking sufficient margin for a power boost for the first service type to having sufficient margin for a power boost for the first service type, and based on detecting that a prohibit timer at the UE may have expired.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a power headroom report may include operations, features, components, or instructions for sending a power headroom report associated with a power boost functionality of a first service type.

[0018] In some examples of methods, apparatus, and non-transitory computer-readable media described herein, sending a power headroom report may include operations, features, components, or instructions for sending a power headroom report that may include a power headroom value calculated based on a configured power boost value.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the configured power boost value may be a maximum configured power boost value of a set of configured power boost values.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a power headroom report may include operations, features, components, or instructions for sending a medium access control (MAC) control element (CE) including a power headroom report on a first uplink shared channel for a first service type, a second uplink shared channel for a second service type, or both.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a power headroom report may include operations, features, components, or instructions for sending a power headroom report indicating a power headroom value corresponding to a single carrier.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a power headroom report may include operations, features, components, or instructions for sending a power headroom report indicating a set of power headroom values ​​corresponding to a set of carriers, respectively.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a power headroom report may include operations, features, components, or instructions for sending a power headroom report on a first uplink shared channel for a first service type.

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for detecting a second trigger event for a power headroom report for a second service type, and avoiding sending a second power headroom report for the second service type on an uplink shared channel for the first service type.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a power headroom report may include operations, features, components, or instructions for sending a power headroom report indicating a power headroom value calculated for at least one carrier configured for a first service type.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the power headroom report does not include power headroom values ​​calculated for any carriers configured for the second service type instead of the first service type.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying a trigger event configuration may include operations, features, components, or instructions for identifying a trigger event configuration for a first service type, the trigger event configuration indicating that a trigger event is to be detected based on detecting a path loss change that satisfies a path loss threshold for the first service type.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a path loss threshold for the first service type may be less than a path loss threshold for the second service type.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a duration of a timer associated with a first service type may be shorter than a duration of a timer associated with a second service type.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the timer associated with the first service type may be a periodic timer or an inhibit timer.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying a trigger event configuration may include operations, features, components, or instructions for identifying a trigger event configuration for a first service type, the trigger event configuration indicating that a trigger event is to be detected based on detecting that a timer associated with the first service type may have expired.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a power headroom report may include operations, features, components, or instructions for sending a power headroom report indicating a first power headroom for a first power control loop associated with a first service type and a second power headroom for a second power control loop associated with a second service type.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the power headroom report includes a first power headroom field for the first power control loop and a second power headroom field for the second power control loop.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first power control loop and the second power control loop may be configured for the same uplink carrier.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying a trigger event configuration may include operations, features, components, or instructions for identifying a trigger event configuration for a first service type, the trigger event configuration indicating that a trigger event is to be detected based on detecting a second trigger event for a power headroom report for a second service type.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the power headroom report may include operations, features, components, or instructions for sending the power headroom report on a second uplink shared channel configured for a second service type.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a power headroom report may include operations, features, components, or instructions for sending a power headroom report on the earlier of a first uplink shared channel configured for a first service type or a second uplink shared channel configured for a second service type.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the power headroom report may be an actual power headroom report, a virtual power headroom report, or both.

[0039] A method for wireless communication by a base station is described. The method may include: sending a trigger event configuration for a power headroom report of a first service type to a UE, the first service type having a lower delay condition and a higher reliability condition than a second service type; and receiving a power headroom report of the first service type from the UE based on the trigger event configuration.

[0040] An apparatus for wireless communication by a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to: send a trigger event configuration for a power headroom report of a first service type to a UE, the first service type having a lower delay condition and a higher reliability condition than a second service type; and receive a power headroom report of the first service type from the UE based on the trigger event configuration.

[0041] Another apparatus for wireless communication by a base station is described. The apparatus may include components for performing the following operations: sending a trigger event configuration for a power headroom report of a first service type to a UE, the first service type having a lower delay condition and a higher reliability condition than a second service type; and receiving a power headroom report of the first service type from the UE based on the trigger event configuration.

[0042] A non-transitory computer-readable medium is described that stores code for wireless communication by a base station. The code may include instructions executable by a processor to: send a trigger event configuration for a power headroom report of a first service type to a UE, the first service type having a lower delay condition and a higher reliability condition than a second service type; and receive a power headroom report of the first service type from the UE based on the trigger event configuration.

[0043] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a trigger event configuration may include operations, features, components, or instructions for sending a trigger event configuration, the trigger event configuration indicating that a trigger event for a power headroom report for a first service type is to be detected based on receiving a power boost function configuration or a power boost function reconfiguration for the first service type.

[0044] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a power boost functionality configuration or a power boost functionality reconfiguration may include operations, features, components, or instructions for receiving a configuration or reconfiguration of a radio resource control power control parameter or receiving a configuration indicated by an open-loop power control parameter set in downlink control information.

[0045] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a trigger event configuration may include operations, features, components, or instructions for sending a trigger event configuration, which trigger event configuration indicates that a trigger event for a power headroom report for a first service type is to be detected based on a lack of sufficient headroom for a power boost for the first service type and based on expiration of a prohibit timer at the UE.

[0046] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a trigger event configuration may include operations, features, components, or instructions for sending a trigger event configuration, the trigger event configuration indicating that a trigger event for a power headroom report for the first service type is to be detected based on detecting a transition from a lack of sufficient headroom for a power boost for the first service type to a sufficient headroom for a power boost for the first service type, and based on expiration of a prohibit timer at the UE.

[0047] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a power headroom report may include operations, features, components, or instructions for receiving a power headroom report that may be associated with a power boost functionality of the first service type.

[0048] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a power headroom report may include operations, features, components, or instructions for receiving a power headroom report including a power headroom value that may be calculated based on a configured power boost value.

[0049] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the configured power boost value may be a maximum configured power boost value of a set of configured power boost values.

[0050] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a power headroom report may include operations, features, components, or instructions for receiving a medium access control (MAC) control element (CE) including a power headroom report on a first uplink shared channel for a first service type, a second uplink shared channel for a second service type, or both.

[0051] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a power headroom report may include operations, features, components, or instructions for receiving a power headroom report indicating a power headroom value corresponding to a single carrier.

[0052] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a power headroom report may include operations, features, components, or instructions for receiving a power headroom report indicating a set of power headroom values ​​corresponding to a set of carriers, respectively.

[0053] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a power headroom report may include operations, features, components, or instructions for receiving a power headroom report on an uplink shared channel for a first service type.

[0054] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a triggering event configuration indication may prohibit the UE from sending a second power headroom report for a second service type on an uplink shared channel for a first service type.

[0055] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a power headroom report may include operations, features, components, or instructions for receiving a power headroom report indicating a power headroom value calculated for at least one carrier configured for a first service type.

[0056] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the power headroom report does not include power headroom values ​​calculated for any carriers configured for the second service type instead of the first service type.

[0057] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a trigger event configuration may include operations, features, components, or instructions for sending a trigger event configuration that indicates that a trigger event for a power headroom report for a first service type is to be detected based on detecting a path loss change that satisfies a path loss threshold for the first service type.

[0058] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a path loss threshold for the first service type may be less than a path loss threshold for the second service type.

[0059] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a trigger event configuration may include operations, features, components, or instructions for sending a trigger event configuration, the trigger event configuration indicating that a trigger event for a power headroom report for a first service type is to be detected based on detecting that a timer associated with the first service type may have expired.

[0060] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a duration of a timer associated with a first service type may be shorter than a duration of a timer associated with a second service type.

[0061] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the timer associated with the first service type may be a periodic timer or an inhibit timer.

[0062] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a power headroom report may include operations, features, components, or instructions for receiving a power headroom report indicating a first power headroom for a first power control loop associated with a first service type and a second power headroom for a second power control loop associated with a second service type.

[0063] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the power headroom report includes a first power headroom field for the first power control loop and a second power headroom field for the second power control loop.

[0064] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first power control loop and the second power control loop may be configured for the same uplink carrier.

[0065] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a trigger event configuration may include operations, features, components, or instructions for sending a trigger event configuration, wherein the trigger event configuration indicates that a trigger event for a power headroom report for a first service type is to be detected based on detecting a second trigger event for a power headroom report for a second service type.

[0066] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a power headroom report may include operations, features, components, or instructions for receiving a power headroom report on a second uplink shared channel configured for a second service type.

[0067] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a power headroom report may include operations, features, components, or instructions for receiving a power headroom report on the earlier of a first uplink shared channel configured for a first service type or a second uplink shared channel configured for a second service type.

[0068] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the power headroom report may be an actual power headroom report, a virtual power headroom report, or both. BRIEF DESCRIPTION OF THE DRAWINGS

[0069] Figure 1 An example of a system supporting wireless communications with power headroom reporting enhancements according to aspects of the present disclosure is shown.

[0070] Figure 2 An example of a wireless communication system supporting power headroom reporting enhancement according to aspects of the present disclosure is shown.

[0071] Figure 3 An example of a process flow supporting power headroom reporting enhancement according to aspects of the present disclosure is shown.

[0072] Figure 4 and Figure 5 A block diagram of a device supporting power headroom reporting enhancement according to aspects of the present disclosure is shown.

[0073] Figure 6 A block diagram of a communications manager supporting power headroom reporting enhancements according to aspects of the present disclosure is shown.

[0074] Figure 7 A schematic diagram of a system including a device supporting power headroom reporting enhancement according to aspects of the present disclosure is shown.

[0075] Figure 8 and Fig. 9 A block diagram of a device supporting power headroom reporting enhancement according to aspects of the present disclosure is shown.

[0076] Fig.10 A block diagram of a communications manager supporting power headroom reporting enhancements according to aspects of the present disclosure is shown.

[0077] Fig.11 A schematic diagram of a system including a device supporting power headroom reporting enhancement according to aspects of the present disclosure is shown.

[0078] Figures 12 to 18 A flow chart illustrating a method of supporting power headroom reporting enhancement according to aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0079] A wireless communication system may support a variety of different service types. For example, a wireless communication system may support mobile broadband (MBB) communications and low-latency communications, which may have more stringent delay and reliability conditions. In some cases, a base station of a wireless communication system may schedule a user equipment (UE) to perform uplink low-latency transmissions on resources that overlap with other uplink MBB transmissions, for example, from other UEs. Uplink MBB transmissions generally have higher transmit power, which may affect (e.g., interfere with) the reception of uplink low-latency transmissions at the base station. In order to enhance the detection of uplink low-latency transmissions, the wireless communication system may support the UE to perform power boosting on the uplink low-latency transmission. For example, when low-latency resources overlap with MBB resources, the UE may increase the transmit power for uplink low-latency transmissions. However, the UE may have a maximum transmit power that the UE can use for uplink transmissions to the base station. In some conventional systems, the UE may send a power headroom report to the base station, which indicates the difference between the maximum transmit power and the currently used transmit power. However, conventional power headroom reporting techniques do not take into account the transmit power boost or the service type of the cell associated with the power headroom report.

[0080] The techniques described herein support enhanced power headroom reporting. For example, the power headroom reporting techniques described herein may be based on the type of service used by the UE generating the power headroom report. Some of the information included in the power headroom report may be based on power boost low-latency transmission. For example, a power headroom report for an uplink carrier may indicate whether the UE can perform power boost for low-latency communication based on the maximum transmit power of the uplink carrier, the actual transmit power (e.g., without boost), and the maximum power boost value. In some cases, the UE may be configured with parameters and triggers to generate a power headroom report based on low-latency communication. For example, whenever the power boost function is configured or reconfigured, the UE may be triggered to generate a power headroom report. In some examples, the UE may have an additional threshold for generating a power headroom report for low-latency communication, which may be different from the threshold for generating a conventional power headroom report or a power headroom report for MBB communication. For example, by using a first power control loop for low-latency communication and a second power control loop for MBB communication, additional techniques are used to use a power loop for a specific service type. The UE may include corresponding fields of the first power control loop and the second power control loop in the power headroom report.

[0081] Aspects of the present disclosure are initially described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow diagrams related to power headroom reporting enhancements.

[0082] Figure 1 An example of a wireless communication system 100 supporting power headroom reporting enhancements according to aspects of the present disclosure is shown. The wireless communication system 100 includes a base station 105, a UE 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, or a new radio (NR) network. In some cases, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission-critical) communications, low-latency communications, or communications with low-cost and low-complexity devices.

[0083] The base station 105 may communicate wirelessly with the UE 115 via one or more base station antennas. The base station 105 described herein may include or may be referred to by those skilled in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next generation NodeB or a giga NodeB (any of which may be referred to as a gNB), a home NodeB, a home eNodeB, or some other suitable terminology. The wireless communication system 100 may include different types of base stations 105 (e.g., macro cell base stations or small cell base stations). The UE 115 described herein may be able to communicate with various types of base stations 105 and network devices, including macro eNBs, small cell eNBs, gNBs, relay base stations, etc.

[0084] Each base station 105 may be associated with a particular geographic coverage area 110 in which it supports communications with various UEs 115. Each base station 105 may provide communications coverage for a corresponding geographic coverage area 110 via a communication link 125, and the communication link 125 between the base station 105 and the UE 115 may utilize one or more carriers. The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105, or a downlink transmission from the base station 105 to the UE 115. Downlink transmissions may also be referred to as forward link transmissions, and uplink transmissions may also be referred to as reverse link transmissions.

[0085] The geographic coverage area 110 of the base station 105 can be divided into sectors that constitute a portion of the geographic coverage area 110, and each sector can be associated with a cell. For example, each base station 105 can provide communication coverage for a macro cell, a small cell, a hotspot, or other types of cells, or various combinations thereof. In some examples, the base station 105 can be mobile and thus provide communication coverage for a mobile geographic coverage area 110. In some examples, different geographic coverage areas 110 associated with different technologies can overlap, and overlapping geographic coverage areas 110 associated with different technologies can be supported by the same base station 105 or different base stations 105. The wireless communication system 100 may include, for example, a heterogeneous LTE / LTE-A / LTE-APro or NR network in which different types of base stations 105 provide coverage for various geographic coverage areas 110.

[0086] The term "cell" refers to a logical communication entity used to communicate with a base station 105 (e.g., via a carrier), and it can be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)) used to distinguish adjacent cells operating via the same or different carriers. In some examples, a carrier can support multiple cells, and different cells can be configured according to different protocol types that can provide access to different types of devices (e.g., machine type communication (MTC), narrowband Internet of Things (NB-IoT), enhanced mobile broadband (eMBB), or other). In some cases, the term "cell" can refer to a portion of a geographic coverage area 110 (e.g., a sector) on which the logical entity operates.

[0087] UE 115 can be dispersed throughout the wireless communication system 100, and each UE 115 can be fixed or mobile. UE 115 can also be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where "device" can also be referred to as a unit, a station, a terminal, or a client. UE 115 can also be a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 can also refer to a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or an MTC device, etc., which can be implemented in various items such as electrical appliances, vehicles, meters, etc.

[0088] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automatic communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a base station 105 without human intervention. In some examples, M2M communication or MTC may include communications from devices that are integrated with sensors or meters to measure or capture information and relay the information to a central server or application that may utilize the information or present the information to a person interacting with the program or application. Some UEs 115 may be designed to collect information or enable automated behavior of machines. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

[0089] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but not simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UE 115 include entering an energy-saving "deep sleep" mode when not engaged in active communications, or operating over a limited bandwidth (e.g., in accordance with narrowband communications). In some cases, UE 115 may be designed to support critical functions (e.g., mission-critical functions), and the wireless communication system 100 may be configured to provide ultra-reliable communications for these functions.

[0090] In some cases, UE 115 is also able to communicate directly with other UE 115 (e.g., using peer-to-peer (P2P) or device-to-device (D2D) protocols). One or more UEs in the group of UEs 115 utilizing D2D communication may be within the geographic coverage area 110 of the base station 105. Other UEs 115 in the group may be outside the geographic coverage area 110 of the base station 105, or otherwise unable to receive transmissions from the base station 105. In some cases, the group of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system in which each UE 115 transmits to each other UE 115 in the group. In some cases, the base station 105 facilitates resource scheduling for D2D communication. In other cases, D2D communication is performed between UEs 115 without the involvement of the base station 105.

[0091] The base stations 105 may communicate with the core network 130 and with each other. For example, the base stations 105 may interface with the core network 130 via a backhaul link 132 (e.g., via S1, N2, N3, or other interface). The base stations 105 may communicate with each other directly (e.g., directly between the base stations 105) or indirectly (e.g., via the core network 130) via a backhaul link 134 (e.g., via X2, Xn, or other interface).

[0092] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC), which may include at least one mobility management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME may manage non-access stratum (e.g., control plane) functions such as mobility, authentication, and bearer management for UEs 115 served by base stations 105 associated with the EPC. User IP packets may be transmitted through the S-GW, which itself may be connected to the P-GW. The P-GW may provide IP address allocation and other functions. The P-GW may be connected to the IP services of the network operator. The operator's IP services may include access to the Internet, (one or more) intranets, IP multimedia subsystems (IMS), or packet switched (PS) streaming services.

[0093] At least some network devices, such as base stations 105, may include subcomponents, such as access network entities, which may be examples of access node controllers (ANCs). Each access network entity may communicate with UE 115 through multiple other access network transport entities, which may be referred to as radio heads, smart radio heads, or transmit / receive points (TRPs). In some configurations, the various functions of each access network entity or base station 105 may be distributed across various network devices (e.g., radio heads and access network controllers) or merged into a single network device (e.g., base station 105).

[0094] The wireless communication system 100 can operate using one or more frequency bands typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is about 1 decimeter to 1 meter. UHF waves may be blocked or redirected by buildings and environmental features. However, the waves can penetrate the structure sufficiently to enable the macrocell to provide services to the UE 115 located indoors. Compared with the transmission of smaller frequencies and longer waves using the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz, the transmission of UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0095] The wireless communication system 100 may also operate in a Super High Frequency (SHF) region using frequency bands from 3 GHz to 30 GHz (also referred to as centimeter bands). The SHF region includes frequency bands such as the 5 GHz Industrial, Scientific, and Medical (ISM) bands, which may be used appropriately by devices that can tolerate interference from other users.

[0096] The wireless communication system 100 can also operate in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), which is also referred to as the millimeter band. In some examples, the wireless communication system 100 can support millimeter wave (mmW) communications between UE 115 and base station 105, and the EHF antennas of each device can be even smaller and closer than UHF antennas. In some cases, this can promote the use of antenna arrays in UE 115. However, the propagation of EHF transmissions may even be subject to greater atmospheric attenuation and shorter ranges than SHF or UHF transmissions. The technology disclosed herein can be adopted across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may differ from country to country or regulatory agency.

[0097] In some cases, the wireless communication system 100 can utilize both licensed radio bands and unlicensed radio bands. For example, the wireless communication system 100 can adopt license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5GHz ISM band. When operating in an unlicensed radio band, wireless devices such as base stations 105 and UE115 can adopt a listen-before-talk (LBT) process to ensure that the frequency channel is idle before sending data. In some cases, operations in unlicensed bands can be based on a combination of carrier aggregation configurations and component carriers operating in licensed bands (e.g., LAA). Operations in unlicensed spectrum can include downlink transmissions, uplink transmissions, peer-to-peer transmissions, or a combination of these transmissions. Duplexing in unlicensed spectrum can be based on frequency division duplexing (FDD), time division duplexing (TDD), or a combination of the two.

[0098] In some examples, the base station 105 or the UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. For example, the wireless communication system 100 may use a transmission scheme between a transmitting device (e.g., a base station 105) and a receiving device (e.g., a UE 115), wherein the transmitting device is equipped with multiple antennas and the receiving device is equipped with one or more antennas. MIMO communications may employ multipath signal propagation to improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers, which may be referred to as spatial multiplexing. Multiple signals may be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams. Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

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

[0100] In one example, the base station 105 may use multiple antennas or antenna arrays to perform beamforming operations for directional communication with the UE 115. For example, some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the base station 105 in different directions, which may include signals sent according to different beamforming weight sets associated with different transmission directions. The transmissions in different beam directions may be used to identify the beam direction (e.g., by the base station 105 or a receiving device such as the UE 115) for subsequent transmission and / or reception by the base station 105.

[0101] Some signals, such as data signals associated with a particular receiving device, may be sent by base station 105 in a single beam direction (e.g., a direction associated with a receiving device, such as UE 115). In some examples, a beam direction associated with transmissions along a single beam direction may be determined based at least in part on signals sent in different beam directions. For example, UE 115 may receive one or more of the signals sent by base station 105 in different directions, and UE 115 may report to base station 105 an indication of the signal it received having the highest signal quality or other acceptable signal quality. Although these techniques are described with reference to signals sent by base station 105 in one or more directions, UE 115 may employ similar techniques to send signals multiple times in different directions (e.g., to identify a beam direction for UE 115 to perform subsequent transmissions or receptions), or to send signals in a single direction (e.g., to send data to a receiving device).

[0102] When receiving various signals such as synchronization signals, reference signals, beam selection signals, or other control signals from the base station 105, a receiving device (e.g., UE 115, which may be an example of a millimeter wave receiving device) may try multiple receive beams. For example, the receiving device may try multiple receive directions by receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receive beams or receive directions. In some examples, the receiving device may receive along a single beam direction using a single receive beam (e.g., when receiving a data signal). The single receive beam may be aligned on a beam direction determined at least in part based on listening according to different receive beam directions (e.g., a beam direction with the highest signal strength, highest signal-to-noise ratio, or other acceptable signal quality determined at least in part based on listening according to multiple beam directions).

[0103] In some cases, the antennas of the base station 105 or UE 115 may be located within one or more antenna arrays that may support MIMO operations, or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be collocated at an antenna assembly such as an antenna tower. In some cases, the antennas or antenna arrays associated with the base station 105 may be located at different geographic locations. The base station 105 may have an antenna array with multiple rows and columns of antenna ports that the base station 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations.

[0104] In some cases, the wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer or packet data convergence protocol (PDCP) layer can be based on IP. The radio link control (RLC) layer can perform packet segmentation and reorganization to communicate on a logical channel. The medium access control (MAC) layer can perform priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use a hybrid automatic repeat request (HARQ) to provide retransmission at the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer can provide the establishment, configuration and maintenance of the RRC connection (which supports the radio bearer of user plane data) between the UE 115 and the base station 105 or the core network 130. At the physical layer, the transport channel can be mapped to the physical channel.

[0105] In some cases, UE 115 and base station 105 can support retransmission of data to increase the possibility of data being successfully received. HARQ feedback is a technique that increases the possibility of correctly receiving data through communication link 125. HARQ can include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC) and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput at the MAC layer under poor radio conditions (e.g., signal-to-noise ratio conditions). In some cases, a wireless device can support simultaneous slot HARQ feedback, where the device can provide HARQ feedback for data received in the previous symbol in the slot in a specific time slot. In other cases, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0106] The time interval in LTE or NR can be expressed as a multiple of the basic time unit. For example, the time interval can be referred to as T s =1 / 30,720,000 second sampling period. The time intervals of the communication resources can be organized according to radio frames (each radio frame has a duration of 10 milliseconds (ms)), where the frame period can be represented as T f =307,200T s . A radio frame may be identified by a system frame number (SFN) ranging from 0 to 1023. Each frame may include 10 subframes numbered from 0 to 9, and each subframe may have a duration of 1 ms. A subframe may be further divided into 2 slots, each slot having a duration of 0.5 ms, and each slot may contain 6 or 7 modulation symbol periods (e.g., depending on the length of the cyclic prefix preceding each symbol period). In addition to the cyclic prefix, each symbol period may contain 2048 sampling periods. In some cases, a subframe may be the minimum scheduling unit of the wireless communication system 100 and may be referred to as a transmit time interval (TTI). In other cases, the minimum scheduling unit of the wireless communication system 100 may be shorter than a subframe or may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI) or in a selected component carrier using sTTI).

[0107] In some wireless communication systems, a time slot may also be divided into a plurality of micro-slots containing one or more symbols. In some instances, a micro-slot or a symbol of a micro-slot may be the minimum unit of scheduling. The duration of each symbol may vary depending on, for example, the subcarrier spacing or the operating frequency band. In addition, some wireless communication systems may implement time slot aggregation, in which a plurality of time slots or micro-slots are aggregated together and used for communication between UE 115 and base station 105.

[0108] The term "carrier" refers to a collection of radio spectrum resources that have a defined physical layer structure for supporting communications on the communication link 125. For example, a carrier of the communication link 125 may include a portion of a radio frequency spectrum band that operates according to a physical layer channel for a given radio access technology. Each physical layer channel may carry user data, control information, or other signaling. A carrier may be associated with a predefined frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be located according to a channel raster for discovery by a UE 115. A carrier may be a downlink or uplink (e.g., in FDD mode), or may be configured to carry downlink and uplink communications (e.g., in TDD mode). In some examples, a signal waveform transmitted on a carrier may be composed of multiple subcarriers (e.g., using a multi-carrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)).

[0109] The organization structure of the carrier can be different for different radio access technologies (e.g., LTE, LTE-A, LTE-A Pro, NR). For example, communications on a carrier can be organized based on TTIs or time slots, where each TTI or time slot can include user data and control information or signaling to support decoding of the user data. The carrier can also include dedicated acquisition signaling (e.g., synchronization signals or system information) and control signaling to coordinate carrier operations. In some examples (e.g., in a carrier aggregation configuration), the carrier can also have acquisition signaling or control signaling to coordinate the operation of other carriers.

[0110] Physical channels may be multiplexed on a carrier according to various techniques. For example, a physical control channel and a physical data channel may be multiplexed on a downlink carrier using a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. In some examples, the control information sent in the physical control channel may be distributed in a cascaded manner between different control regions (e.g., between a common control region or common search space and one or more UE-specific control regions or UE-specific search spaces).

[0111] A carrier may be associated with a particular bandwidth of radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a plurality of predetermined bandwidths of a carrier for a particular radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). In some examples, each served UE 115 may be configured to operate on part or all of the carrier bandwidth. In other examples, some UEs 115 may be configured to operate using a narrowband protocol type associated with a predefined portion or range (e.g., a set of subcarriers or RBs) within a carrier (e.g., an "in-band" deployment of a narrowband protocol type).

[0112] In a system using MCM technology, a resource element may consist of a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and the subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme). Therefore, the more resource elements received by UE 115 and the higher the order of the modulation scheme, the higher the data rate of UE 115 may be. In a MIMO system, wireless communication resources may refer to a combination of radio spectrum resources, time resources, and space resources (e.g., space layers), and the use of multiple space layers may also increase the data rate for communicating with UE 115.

[0113] A device (e.g., base station 105 or UE 115) of wireless communication system 100 may have a hardware configuration that supports communication on a specific carrier bandwidth, or may be configured to support communication on one carrier bandwidth in a set of carrier bandwidths. In some examples, wireless communication system 100 may include base station 105 and / or UE 115 that supports simultaneous communication via carriers associated with more than one different carrier bandwidths.

[0114] The wireless communication system 100 may support communication with the UE 115 on multiple cells or carriers, a feature that may be referred to as carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used with both FDD and TDD component carriers.

[0115] In some cases, the wireless communication system 100 can utilize an enhanced component carrier (eCC). An eCC can be characterized by one or more characteristics including a wider carrier or frequency channel bandwidth, a shorter symbol duration, a shorter TTI duration, or a modified control channel configuration. In some cases, an eCC can be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g., when multiple serving cells have suboptimal or non-ideal backhaul links). An eCC can also be configured for use in an unlicensed spectrum or a shared spectrum (e.g., where more than one operator is allowed to use the spectrum). An eCC characterized by a wide carrier bandwidth can include one or more segments that can be used by a UE 115 that is unable to monitor the entire carrier bandwidth or is otherwise configured to use a limited carrier bandwidth (e.g., to save power).

[0116] In some cases, an eCC may utilize a different symbol duration than other component carriers, which may include using a reduced symbol duration compared to the symbol duration of other component carriers. A shorter symbol duration may be associated with an increased spacing between adjacent subcarriers. A device such as a UE 115 or a base station 105 utilizing an eCC may transmit a wideband signal (e.g., according to a frequency channel or carrier bandwidth of 20 Mhz, 40 Mhz, 60 Mhz, 80 MHz, etc.) with a reduced symbol duration (e.g., 16.67 microseconds). A TTI in an eCC may consist of one or more symbol periods. In some cases, the TTI duration (i.e., the number of symbol periods in a TTI) may be variable.

[0117] The wireless communication system 100 may be an NR system that may utilize any combination of licensed, shared, and unlicensed spectrum bands, etc. The flexibility of eCC symbol duration and subcarrier spacing may allow the use of eCC across multiple spectrums. In some examples, NR shared spectrum may increase spectrum utilization and spectrum efficiency, specifically through dynamic vertical (e.g., across frequency domain) and horizontal (e.g., across time domain) resource sharing.

[0118] The wireless communication system 100 may support a variety of different service types. For example, the wireless communication system 100 may support MBB communications and low-latency communications, which may have more stringent latency and reliability conditions. In some cases, the base station 105 may schedule the UE 115 to perform uplink low-latency transmissions on resources that overlap with other uplink MBB transmissions, for example, from other UEs 115. Uplink MBB transmissions may generally have higher transmit power, which may affect (e.g., interfere with) the reception of the uplink low-latency transmissions at the base station 105.

[0119] To enhance detection of uplink low-latency transmissions, the wireless communication system 100 may support the UE 115 to perform power boosting for the uplink low-latency transmissions. For example, when low-latency resources overlap with MBB resources, the UE 115 may increase the transmit power for uplink low-latency transmissions. However, the UE 115 may have a maximum transmit power that the UE 115 may use for uplink transmissions to the base station 105. In some cases, the maximum transmit power may be configured per cell or per base station 105.

[0120] In some cases, UE 115 can send a power headroom report to the base station, and the power headroom report indicates the difference between the maximum transmit power and the currently used transmit power. The technology described herein supports enhanced power headroom reports to support power boosting for low-delay communication. In some cases, UE 115 can generate a power headroom report based on a service. Some information included in the power headroom report can be used by the base station 105 to determine whether power boosting for low-delay transmission is available. For example, the power headroom report of an uplink carrier can indicate whether UE 115 can perform power boosting for low-delay communication based on the maximum transmit power of the uplink carrier, the actual transmit power (for example, in the case of no boost) and the maximum power boost value. In some cases, UE 115 can be configured with parameters and triggers for generating a power headroom report, which is based on low-delay communication.

[0121] Figure 2 An example of a wireless communication system 200 supporting power headroom reporting enhancements according to aspects of the present disclosure is shown. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100. The wireless communication system 200 may include a UE 115-a and a base station 105-a, which may be as described in reference Figure 1 Examples of UE 115 and base station 105 are described.

[0122] The wireless communication system may support wireless communication with different service types. For example, UE 115-a and base station 105-a may support MBB communication, low-latency communication, or both. In some cases, ultra-reliable low-latency communication (URLLC) may be an example of low-latency communication. Enhanced MBB (eMBB) may be an example of MBB communication. In some cases, base station 105-a may serve multiple UEs 115, each of which may support eMBB communication or low-latency communication, or both eMBB communication and low-latency communication.

[0123] UE 115-a may have an uplink transmit power budget. For example, UE 115-a may be configured with a maximum uplink transmit power 215. Maximum uplink transmit power 215 may be based on a maximum transmit power per cell, a total uplink transmit budget for all uplink communications, or a combination thereof. In one example, UE 115-a may use URLLC transmit power 220 to send uplink URLLC messages, and UE 115-a may use MBB transmit power 225 to send uplink eMBB messages.

[0124] In some examples, UE 115-a can report the uplink transmit power headroom to base station 105-a. The power headroom generally refers to how much remaining power is available for UE 115-a to use for uplink transmission. For example, the power headroom can be the difference between the current transmit power value and the maximum uplink transmit power 215, which indicates how much the current transmit power value can be increased before reaching the transmit power limit. For example, the power headroom report can indicate the power difference between a shared channel transmission or a sounding reference signal (SRS) transmission and the maximum transmit power supported for the cell. Therefore, the power headroom can be the difference between the maximum transmit power and the transmit power, or Power Headroom = P max -P transmission .

[0125] During the power headroom reporting process, the UE 115-a may report different types of power headroom to the base station 105-a. In some cases, the power headroom report may include one or more types of power headroom information. For a first type of power headroom, the UE 115-a may report the difference between the nominal UE maximum transmit power (e.g., the maximum uplink transmit power 215) and the estimated power for uplink shared channel transmissions for each activated serving cell. For a second type of power headroom, the UE 115-a may report the difference between the nominal UE maximum transmit power and the estimated power of uplink shared channel and uplink control channel transmissions on the secondary primary cell of another MAC entity in a dual connectivity configuration. For a third type of power headroom, the UE 115-a may report the difference between the nominal UE maximum transmit power and the estimated power of SRS transmissions for each activated serving cell.

[0126] In some cases, UE 115-a may report power headroom for a secondary cell (e.g., in a carrier aggregation configuration) that is not actually transmitting. Therefore, UE 115-a may not have an accurate measurement of the uplink transmit power of the secondary cell. Instead, UE 115-a may estimate the uplink transmit power that will be used for uplink transmissions on an active but currently unused secondary cell. In some cases, this may be referred to as a virtual power headroom report, in which UE 115-a indicates the power difference between a virtual physical uplink shared channel (PUSCH) or SRS in a configured format and the maximum transmit power of the corresponding cell. For example, UE 115-a may send a report on a primary cell, reporting power headroom based on the actual transmit power of the primary cell and based on an estimate of the secondary cell.

[0127] Table 1 below shows an example format of a power headroom report for some systems. In some cases, the power headroom report for a cell may be based on eight bits of information or an eight-bit byte (octet). The value of P may indicate whether power backoff is applied, V may indicate whether the power headroom is for virtual transmission or for actual transmission, and R may be a reserved bit (e.g., it may be used for other signaling). Table 1 may be an example of a power headroom report indicating the power headroom of multiple configured cells. As shown, the power headroom value of a cell may be based on the type of power headroom (e.g., type one, type two, or type three described above). In Table 1, type X may be at least any one of type 1, type 2, or type 3. In Table 1, UE 115 may report the power headroom of the primary cell, SPCell, and n serving cells, and obtain m different power headroom measurements.

[0128]

[0129] Table 1

[0130] UE 115-a may be triggered to send a power headroom report. For example, if a periodic timer expires, UE 115-a may be triggered to send a power headroom report. In some cases, UE 115-a may report power headroom non-periodically, for example, by detecting a change in path loss or a change in configuration. In some cases, UE 115-a may have a timer running (e.g., an inhibit timer) that prevents UE 115-a from sending a power headroom report that is too large. Once UE 115-a sends a power headroom report, UE 115-a may start an inhibit timer, and UE 115-a may not send another power headroom report until the inhibit timer completes.

[0131] There may be multiple different examples of non-periodic power headroom reporting. For example, if UE 115-a detects a change in path loss that exceeds a threshold, UE 115-a may be triggered to report power headroom. For example, if the change in path loss is greater than a threshold amount for at least one activated serving cell of any MAC entity, UE 115-a may be triggered to report power headroom. In some cases, UE 115-a may send a power headroom report only if an inhibit timer expires or has expired and the path loss has changed by more than a threshold. Parameters such as "phr-Tx-PowerFactorChange" may be examples of parameters for a path loss threshold, which may be measured in decibels.

[0132] If UE 115-a detects activation of a secondary cell with any MAC entity of the configured uplink, UE 115-a may be triggered to report a power headroom report. If the power headroom reporting function is configured or reconfigured by upper layers (e.g., without disabling the function), UE 115-a may be triggered to report a power headroom report. If a PSCell (e.g., a PSCell of a dual connectivity configuration) is activated, or a new PSCell is added or changed, UE 115-a may be triggered to report a power headroom report.

[0133] In some cases, if the inhibit timer expires, or has expired, and the MAC entity has uplink resources for a new transmission, the UE 115-a may report the power headroom based on satisfying one or more conditions. One condition may be whether there are uplink resources allocated for the transmission. Another condition may be whether there is a physical uplink control channel (PUCCH) transmission on the cell, and when the MAC entity has uplink resources allocated for transmission on the cell or a PUCCH transmission, the required power backoff based on cell power management has changed by more than a power factor change threshold since the last power headroom report transmission.

[0134] UE 115-a may be configured to report power headroom only for one cell or for multiple cells. When UE 115-a is configured to be in multi-PHR mode, UE 115-a may report power headroom for all configured uplink cells of the MAC entity, even if UE 115-a is triggered to report power headroom for one cell. If UE 115-a is configured for a single entry power headroom format, UE 115-a may report power headroom only for the primary cell. In some cases, UE 115-a may be triggered to report power headroom only for secondary cells while being configured for a single entry power headroom format. In some cases, when configured to be in multi-power headroom reporting mode, UE 115-a may report virtual power headroom measurements for uplink cells that have no scheduled uplink transmissions.

[0135] In some cases, the wireless communication system 200 may support multiplexing for UE 115, which supports different service types. For example, the wireless communication system 200 may support inter-UE eMBB / URLLC multiplexing. In some cases, the base station 105-a may schedule low-latency uplink transmissions on resources previously allocated to MBB uplink transmissions. In order to support multiplexing, power boosting of URLLC devices may be implemented. For example, a URLLC UE 115 scheduled for resources overlapping with an eMBB UE 115 may boost the transmit power on the overlapping resources. This may improve the detection of URLLC transmissions at the receiving base station 105. When supporting power boosting of low-latency devices, some conventional techniques for power headroom reporting may not be sufficient to provide power headroom information. For example, when scheduling UE 115-a to determine whether URLLC power boosting can be applied, the base station 105-a may not have the latest information.

[0136] Thus, the wireless communication system 200 may support techniques for power headroom reporting while taking into account power boosting techniques. In some cases, the UE 115-a may be triggered to send a power headroom report for a cell configured for low-latency communication, such as the low-latency power headroom report 210. In some cases, the power headroom report for low-latency communication may include different information than a regular power headroom report, a power headroom report configured for eMBB communication (e.g., the MBB power headroom report 205), or a power headroom report that is not configured for low-latency communication.

[0137] For example, UE 115-a may have additional triggering events for reporting power headroom based on low-latency communications. The triggering events for sending low-latency power headroom may be based on indicating whether UE 115-a can apply power boosting for uplink low-latency transmissions. In some cases, these additional triggering events may provide power headroom information to base station 105-a so that base station 105-a can determine whether power boosting can be applied at UE 115-a.

[0138] In some cases, UE 115-a may be triggered to send a power headroom report when a power boost functionality is configured or reconfigured at a higher layer. In some cases, power boost may be referred to as enhanced open-loop power control or dynamic open-loop power control. In some examples, a power headroom report may be triggered if the UE is configured or reconfigured with an enhanced open-loop power control functionality on an uplink carrier. For example, if the UE receives a configuration or reconfiguration of a higher layer parameter (e.g., pusch-PowerControl-v16xy), the UE may determine that a URLLC power headroom report is triggered, or if the UE is configured with an open-loop power control parameter setting indication (e.g., olpc-ParameterSetForDCI-Format0-1-r16 or olpc-ParameterSetForDCI-Format0-2-r16) in a DCI (e.g., DCI format 0_1 ​​or DCI format 0_2) via a higher layer parameter (e.g., RRC parameter), the UE may determine that a URLLC power headroom report is triggered. In some cases, the low-delay power headroom report 210 may be reported in a first low-delay shared channel transmission (e.g., a first URLLC PUSCH transmission) scheduled after the power headroom reporting functionality is configured or reconfigured in the upper layers. Additionally or alternatively, the power headroom may be reported in a first low-delay shared channel transmission scheduled with a power boost after the power headroom reporting functionality is configured or reconfigured in the upper layers.

[0139] In some examples, upon detecting that UE 115-a does not have enough headroom for power boosting, UE 115-a may be triggered to send a power headroom report. In this example, UE 115-a may send a power headroom report indicating a negative value, which may show the difference in power headroom for UE 115-a to perform power boosting. In some cases, if UE 115-a changes from not having enough headroom for power boosting to having enough headroom for power boosting, UE 115-a may be triggered to send a power headroom report. Then, UE 115-a may send a power headroom report with a positive value, which may show how much additional headroom UE 115-a has in addition to the headroom for power boosting.

[0140] In some examples of the above triggering, UE 115-a may also check whether a prohibit timer has expired. In some cases, in order to trigger a power headroom report, a prohibit timer (e.g., "phr-ProhibitTimer") may first expire or be expired. For example, UE 115-a may detect that it does not have enough headroom for power boosting and may check that the prohibit timer has expired. If UE 115-a does not have enough headroom and the prohibit timer has expired, UE 115-a may send a power headroom report for low-latency communication to base station 105-a. In another example, UE 115-a may detect that the amount of headroom switches from being unable to perform power boosting to being able to perform power boosting, and then UE 115-a may check for prohibition and send a power headroom report if the prohibit timer has expired.

[0141] In some cases, the low latency power headroom report 210 may have a power headroom report format or type based on power boost for low latency communications. For example, the power headroom calculation may be based on considering the maximum configured power boost value. The power headroom report value may be, for example, PHR=P c,max -P tx -ΔP max , where P c,max represents the maximum transmit power limit of cell c, ΔP max represents the maximum power boost value configured for the uplink carrier, and P tx Indicates the actual transmit power without power boosting. Thus, the power headroom value (PHR) may indicate whether power boosting can be applied (e.g., by indicating a positive value) or whether power boosting cannot be applied (e.g., by indicating a negative value). In some cases, in addition to the information included in the regular power headroom report, the information sent with the power headroom report based on low delay power boosting may also be sent.

[0142] In some cases, the power headroom report for low-latency communication may be sent on a low-latency shared channel or on an MBB shared channel. In some cases, the power headroom report may be sent in a MAC CE. For example, UE 115-b may send a MAC CE carrying a power headroom report for low-latency communication to indicate whether power boost is available. If the power headroom report MAC CE is sent on an actual low-latency shared channel (e.g., an actual URLLC PUSCH), the power headroom report may be an example of an actual power headroom report. If the power headroom report MAC CE is sent on an eMBB uplink shared channel (e.g., eMBB PUSCH), the power headroom report MAC CE may indicate a virtual power headroom report for low-latency communication. In addition, a power headroom report triggered based on power boost may be configured for a single entry power headroom report format or a multi-entry power headroom report format. For example, UE 115-a may send a low-latency based power headroom report for each cell (e.g., including a single value indicating the power headroom for a particular cell), or UE 115-a may send a low-latency based power headroom report for each configured uplink carrier.

[0143] The wireless communication system 200 may implement techniques for prioritizing power headroom reports for low-latency communications. In some cases, UE 115-a may be prohibited from sending power headroom reports for eMBB-only uplink carriers on a low-latency uplink shared channel. The prohibition may be configured or controlled via logical channel prioritization. UE 115-a may be able to send power headroom reports for low-latency carriers on a low-latency uplink shared channel or an eMBB uplink shared channel. Thus, power headroom reports for low-latency communications may be sent using any configured carrier (e.g., an eMBB carrier or a URLLC carrier), but power headroom reports for MBB communications may be sent on an MBB carrier (e.g., instead of a low-latency carrier).

[0144] In some examples, when UE 115-a reports power headroom for low-latency communication, UE 115-a may report power headroom for PUSCH transmission (e.g., virtual or actual). In some examples, when reporting power headroom for low-latency communication, UE 115-a may not report power headroom based on SRS transmission. When a power headroom report for low-latency communication is triggered on a serving cell, a power headroom may be calculated for an uplink shared channel transmission (e.g., a low-latency PUSCH transmission) on that cell. In some cases, UE 115-a may not include a power headroom report for a cell calculated based on SRS transmissions in an uplink PUSCH transmission.

[0145] In some cases, the wireless communication system 200 may support a format for a power headroom report configured to carry information for a carrier configured with low-delay uplink transmission. For example, the low-delay power headroom report 210 may have a format specifically configured to convey at least power headroom information for low-delay communications. In some cases, the format may only contain power headroom reports for carriers configured with low-delay uplink transmissions (such as URLLC PUSCH transmissions or URLLC PUCCH transmissions).

[0146] In some cases, the low-delay power headroom report 210 may be based on parameters associated with low-delay communication. For example, UE 115-a may be configured with a power factor change threshold based on low-delay communication. The power factor change threshold of the URLLC carrier may be less than the power factor change threshold of the eMBB carrier. In contrast, some conventional power headroom reporting techniques may use only one parameter configured for the PUCCH group. UE 115-a may also be configured with a periodic timer for reporting low-delay power headroom. The periodic timer for reporting low-delay power headroom on a low-delay uplink carrier may be less than the periodic timer for reporting power headroom on an eMBB carrier. For example, low-delay power headroom report 210 may be sent more frequently than eMBB power headroom report 205. In addition, the low-delay power headroom report may have a separate prohibition timer. The prohibition timer for the low-delay power headroom report on a low-delay carrier may be configured to be less than the prohibition timer for the eMBB carrier. The parameters used to trigger power headroom reporting may generally be adjusted to be smaller for reporting URLLC headroom than for reporting eMBB headroom, thereby allowing more frequent reporting of URLLC power headroom.

[0147] In some wireless communication systems, UE 115 may be configured with two power control loops, and transmit power may be accumulated for the two loops separately. If UE 115 is configured with both URLLC and eMBB uplink transmissions, UE 115 may use two power control loops for URLLC and eMBB, respectively. In some cases, UE 115 may be configured for uplink URLLC and uplink eMBB communications on a single serving cell. When UE 115 reports the power headroom of the serving cell, UE 115 may only report the power headroom of a single power control loop, which may not be enough for a base station 105 that supports both URLLC and eMBB services.

[0148] Therefore, UE 115-a and base station 105-a can support power headroom reporting for two power control loops. In the power headroom report, UE 115-a may include a field indicating the power headroom of the low-latency communication power control loop. In some cases, the new field may be a bit of an eight-bit byte. For each serving cell configured with both URLLC and eMBB, the power headroom report may include two power headroom fields, one field for each power control loop. Table 2 below shows an example of a field for reporting power headroom for two power control loops, where PC may represent power control. In some cases, the fields of Table 2 may be attached to a power headroom report generated based on the fields of Table 1, or UE 115-a may send a power headroom report with only fields based on Table 2. Values ​​V1 and V2 may indicate whether the power headroom reported for power control loops 1 and 2 is a virtual transmission or an actual transmission, respectively.

[0149] P V1 PH (type X, serving cell n, PC loop 1) V2 R PH (type X, serving cell n, PC loop 2) R R <![CDATA[P CMAX,f,c m]]>

[0150] Table 2

[0151] In one example, UE 115-a may send a power headroom report associated with a first power control loop on a PUSCH. UE 115-a may use an actual power headroom for the first power control loop and a virtual power headroom (e.g., formatted according to Table 2) for a second power control loop. In another example, UE 115-a may send a power headroom report associated with a second power control loop on a PUSCH. UE 115-a may use an actual power headroom for the second power control loop and a virtual power headroom (e.g., formatted according to Table 2) for the first power control loop.

[0152] In some cases, when the eMBB power headroom report is triggered, UE 115-a may be triggered to report the power headroom for both eMBB and URLLC. In some cases, when the URLLC power headroom is triggered, UE 115-a may only report the URLLC power headroom (e.g., instead of the eMBB power headroom). Therefore, whenever the eMBB power headroom is reported, the URLLC power headroom may be reported, but when the URLLC power headroom is reported, the eMBB power headroom may not always be reported. The power headroom report conveying the URLLC power headroom may be sent on an eMBB uplink shared channel or a URLLC uplink shared channel. For example, which uplink shared channel is scheduled first to report the URLLC power headroom may be used.

[0153] URLLC power headroom reporting can similarly support virtual power headroom reporting. For example, UE 115-a can detect a trigger to report URLLC power headroom, but UE 115-a may not have a URLLC PUSCH allocation. Therefore, the power headroom of the transmit power control accumulation or associated power control loop (e.g., associated with URLLC) can be reported.

[0154] In one example, UE 115-a may be configured for both URLLC and eMBB communications with base station 105-a on an uplink carrier. When low-latency communication resources are multiplexed with eMBB resources, UE 115-a may support power boosting of the transmit power of low-latency communication. UE 115-a may detect a trigger for a transmit power headroom report. In some cases, the trigger may be a trigger for reporting an eMBB power headroom report 205. Alternatively, in some cases, the trigger may be a trigger for reporting a URLLC power headroom report 210. Some examples of triggers for reporting a URLLC power headroom report 210 may include a first event (e.g., configuration or reconfiguration of a power boost function), a second event (e.g., if UE 115-a detects that there is not enough headroom for power boosting), or a third event (e.g., if UE 115-a detects a change in the amount of power headroom such that there becomes enough power headroom for power boosting).

[0155] Additionally or alternatively, UE 115-a may be configured with power headroom reporting parameters for URLLC. For example, UE 115-a may be configured with a power factor variation parameter for reporting URLLC power headroom, a periodic timer parameter for reporting URLLC power headroom, and a prohibition timer for reporting URLLC power headroom. UE 115-a may be configured with these parameters in addition to the corresponding parameters for sending eMBB power headroom reports.

[0156] Then, UE 115-a can generate a power headroom report to indicate the power headroom of the URLLC on the uplink carrier. The power headroom report that conveys the URLLC power headroom can have a new format or be a new type of power headroom report. For example, the power headroom value indicated in the report can be based on the maximum configured power boost transmit power.

[0157] UE 115-a may send the power headroom for URLLC in both URLLC power headroom report 210 and eMBB power headroom report 205. In some cases, the eMBB power headroom may be sent only in eMBB power headroom report 205. In some examples, UE 115-a may be configured with two transmit power control loops. UE 115-a may use one transmit power control loop for URLLC and another transmit power control loop for eMBB. UE 115-a may include a field in the power headroom report to indicate the power headrooms of the two transmit power control loops.

[0158] The base station 105-a may receive a power headroom report including power headroom measurements for URLLC carriers. In some cases, the base station 105-a may modify the transmit power at the UE 115-a based on the power headroom report. For example, the base station 105-a may send control signaling (such as transmit power control) to adjust the uplink transmit power at the UE 115-a. In some cases, the transmit power control may indicate that the uplink transmit power of the first control loop (e.g., for eMBB communication), the second control loop (e.g., for URLLC), or both is to be adjusted. In some cases, the base station 105-a may schedule the UE 115-a based on the power headroom report. For example, if the UE 115-a indicates that a power boost is not available, the base station 105-a may prevent the UE 115-a from being scheduled for the URLLC uplink on resources that overlap with the eMBB transmission.

[0159] Figure 3 An example of a process flow 300 for supporting power headroom reporting enhancements according to aspects of the present disclosure is shown. In some examples, the process flow 300 may implement aspects of the wireless communication system 100. The process flow 300 may include a UE 115-b and a base station 105-b, which may be as described in reference Figure 1 An example of a UE 115 and a base station 105 is described. The UE 115-b and the base station 105-b may support techniques for reporting URLLC power overhead to support URLLC power boosting.

[0160] In some cases, at 305, base station 105-b may send a trigger event configuration for a power headroom report for a first service type having a lower latency condition and a higher reliability condition than a second service type. URLLC may be an example of the first service type, and eMBB may be an example of the second service type.

[0161] In some cases, the trigger event configuration indicates that a trigger event for a power headroom report for the first service type is to be detected based on receiving a power boost functionality configuration or a power boost functionality reconfiguration for the first service type. For example, UE 115-b may trigger a power headroom report upon configuration or reconfiguration of power boost in an upper layer such as RRC.

[0162] In some cases, the trigger event configuration indicates a trigger event for detecting a power headroom report for the first service type based on a lack of sufficient headroom for power boosting of the first service type. In some cases, the power headroom report triggered due to a lack of sufficient headroom may include a negative value to indicate how much additional headroom may be available to enable power boosting.

[0163] In some cases, the trigger event configuration indicates that a trigger event for a power headroom report for the first service type is to be detected based on detecting a transition from lack of sufficient headroom for a power boost for the first service type to having sufficient headroom for a power boost for the first service type. In some cases, the power headroom report triggered by the switch to having sufficient headroom may include a positive value to indicate how much additional or excess headroom is available after the power boost.

[0164] In some cases, the trigger event configuration indicates that a trigger event for power headroom reporting for the first service type is to be detected based on detecting a path loss change that satisfies a path loss threshold for the first service type. In some cases, detecting the path loss change can be based on a path loss threshold or a power factor change threshold specific to the first type of service type.

[0165] In some cases, the trigger event configuration indicates that a trigger event for a power headroom report for the first service type is to be detected based on detecting that a timer associated with the first service type has expired. In some cases, the timer associated with the service type may be smaller than a corresponding timer associated with the second service type. For example, the period of the periodic timer configured for the URLLC carrier may be smaller than the period of the periodic timer configured for the eMBB carrier, so that the power headroom report for the first service type occurs more frequently.

[0166] In some cases, the trigger event configuration indicates that a trigger event for a power headroom report for a first service type is to be detected based on detecting a second trigger event for a power headroom report for a second service type. For example, sending a trigger for an eMBB power headroom report may also trigger a URLLC power headroom report.

[0167] In some cases, at 310, UE 115-b may identify a trigger event configuration for power headroom reporting for the first service type. In some cases, the trigger event configuration may be received from base station 105-b. In some cases, the trigger event configuration may be retrieved from a storage device of UE 115-b. For example, UE 115-b may be pre-configured with one or more trigger event configurations.

[0168] At 315, UE 115-b may detect a triggering event for a power headroom report for the first service type. For example, UE 115-b may detect the triggering event based on a triggering event configuration. UE 115-b may measure a power headroom for the first service type based on detecting the triggering event. The power headroom for the first service type may be, for example, a difference between a transmit power of the first service type and a maximum transmit power of the first service type.

[0169] At 320, UE 115-b may send a power headroom report for the first service type based on detecting the triggering event. In some cases, UE 115-b may send a power headroom report including a power headroom value associated with a power boost functionality for the first service type. In some cases, UE 115-b may send a power headroom report including a power headroom value calculated based on a configured power boost value. In some cases, UE 115-b may send a MAC CE including the power headroom report on a first uplink shared channel for the first service type, a second uplink shared channel for the second service type, or both.

[0170] In some cases, UE 115-b may send a power headroom report including a power headroom value calculated based on a configured power boost value. For example, the power headroom calculation may be based on considering the maximum configured power boost value. In some examples, by considering the maximum configured power boost value, the power headroom value may be negative if UE 115-b cannot apply the power boost, or the power headroom value may be positive if UE 115-b can apply the power boost. In some cases, the power headroom value may be calculated for at least one carrier configured for the first service type. In some cases, the power headroom report may indicate a set of power headroom values ​​corresponding to a set of carriers, respectively. For example, UE115-b may support a single entry power headroom report for a single cell (e.g., a primary cell), or multiple power headroom reports for multiple cells (e.g., all configured or selected sets of cells).

[0171] In some cases, UE 115-b may send a power headroom report indicating a first power headroom for a first power control loop associated with a first service type and a second power headroom for a second power control loop associated with a second service type. For example, UE 115-b may have two power control loops, and UE 115-b may use one power control loop for URLLC and one power control loop for eMBB communications. In some cases, the power headroom report may include a first power headroom field for the first power control loop and a second power headroom field for the second power control loop.

[0172] In some cases, the power headroom report may include a virtual power headroom measurement for a cell of the first service type that is not scheduled for an uplink shared channel. For example, UE 115-b may perform an estimation of uplink transmit power for a URLLC cell that is not scheduled for PUSCH. In some cases, UE 115-b may report the power headroom based on a power control loop associated with the first service type of the cell.

[0173] At 325, the base station 105-b may receive a power headroom report including a power headroom value calculated based on the configured power boost value. In some cases, the base station 105-b may schedule the UE 115-b based on the power headroom report. For example, if the power headroom report indicates that the UE 115-b has sufficient power headroom to perform power boosting, the base station 105-b may schedule the UE 115-b on URLLC resources that overlap with uplink eMBB transmissions. Alternatively, if the power headroom report indicates that the UE 115-b does not have sufficient power headroom to perform power boosting, the base station 105-b may avoid scheduling the UE 115-b on URLLC resources that overlap with uplink eMBB transmissions.

[0174] In some cases, the base station 105-b may send control signaling to adjust the transmit power at the UE 115-b. For example, the base station 105-b may send a power control command for one or more power control loops at the UE 115-b. In the case where the UE 115-b uses one power control loop for each of the first service type and the second service type, the base station 105-b may send a transmit power control signal to adjust the transmit power of the transmit power loop associated with the first service type. In some cases, the transmit power command may adjust the transmit power of the uplink URLLC at the UE 115-b so that the UE 115-b may perform a power boost.

[0175] Figure 4A block diagram 400 of a device 405 supporting power headroom reporting enhancements according to aspects of the present disclosure is shown. The device 405 may be an example of aspects of a UE 115 as described herein. The device 405 may include a receiver 410, a communication manager 415, and a transmitter 420. The device 405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0176] The receiver 410 may receive information associated with various information channels (e.g., control channels, data channels, and information related to power headroom reporting enhancement, etc.), such as packets, user data, or control information. The information may be delivered to other components of the device 405. The receiver 410 may be a reference Figure 7 Examples of aspects of the described transceiver 720. The receiver 410 may utilize a single antenna or a collection of antennas.

[0177] The communication manager 415 may detect a triggering event for a power headroom report for a first service type, the first service type having a lower latency condition and a higher reliability condition than a second service type, and send a power headroom report for the first service type based on detecting the triggering event. In some cases, the communication manager 415 may identify a triggering event configuration for a power headroom report for the first service type. The communication manager 415 may be an example of aspects of the communication manager 710 described herein.

[0178] The communication manager 415 or its subcomponents may be implemented in hardware, in code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 415 or its subcomponents may be performed by a general purpose processor, a DSP, an application specific integrated circuit (ASIC), an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.

[0179] The communication manager 415 or its subcomponents can be physically located in a variety of locations, including being distributed so that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the communication manager 415 or its subcomponents can be separate and distinct components. In some examples, according to various aspects of the present disclosure, the communication manager 415 or its subcomponents can be combined with one or more other hardware components, including but not limited to input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof.

[0180] The actions performed by the communication manager 415 described herein may be implemented to achieve one or more potential advantages. One embodiment may allow the UE 115 to perform power boosting for low-latency transmissions more frequently. By sending a power headroom report that takes into account low-latency power boosting to the serving base station 105, the serving base station 105 may be able to make a notified scheduling decision or adjust the transmit power of the UE 115. Then, in some cases, the UE 115 may avoid being scheduled for low-latency transmission on resources that overlap with MBB uplink transmissions. Additionally or alternatively, the base station 105 may manage and sometimes adjust the uplink transmit power of the UE 115 so that the UE 115 can perform power-boosted low-latency transmissions. This may improve the throughput of the UE 115 because the uplink low-latency transmissions from the UE 115 may not be affected by the eMBB transmissions, or may be less affected by the eMBB transmissions.

[0181] Transmitter 420 can transmit signals generated by other components of device 405. In some examples, transmitter 420 can be co-located with receiver 410 in a transceiver module. For example, transmitter 420 can be a reference Figure 7 Examples of aspects of the described transceiver 720. The transmitter 420 may utilize a single antenna or a collection of antennas.

[0182] Figure 5 A block diagram 500 of a device 505 supporting power headroom reporting enhancements according to aspects of the present disclosure is shown. The device 505 may be an example of aspects of the device 405 or UE 115 as described herein. The device 505 may include a receiver 510, a communication manager 515, and a transmitter 535. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0183] The receiver 510 may receive information associated with various information channels (e.g., control channels, data channels, and information related to power headroom reporting enhancement, etc.), such as packets, user data, or control information. The information may be delivered to other components of the device 505. The receiver 510 may be a reference Figure 7 Examples of aspects of the described transceiver 720. The receiver 510 may utilize a single antenna or a collection of antennas.

[0184] The communication manager 515 can be an example of aspects of the communication manager 415 described herein. The communication manager 515 can include a trigger event detection component 525 and a power headroom report sending component 530. In some cases, the communication manager 515 can include a trigger event configuration component 520. The communication manager 515 can be an example of aspects of the communication manager 710 described herein.

[0185] In some cases, trigger event configuration component 520 can identify a trigger event configuration for power headroom reporting for a first service type having a lower latency condition and a higher reliability condition than a second service type.

[0186] The trigger event detecting component 525 can detect a trigger event for a power headroom report for the first service type. In some cases, the trigger event can be detected based on a trigger event configuration.

[0187] The power headroom report sending component 530 can send a power headroom report for the first service type based on detecting the triggering event.

[0188] Transmitter 535 can transmit signals generated by other components of device 505. In some examples, transmitter 535 can be co-located with receiver 510 in a transceiver module. For example, transmitter 535 can be a reference Figure 7 Examples of aspects of the described transceiver 720. The transmitter 535 may utilize a single antenna or a collection of antennas.

[0189] Figure 6 A block diagram 600 of a communication manager 605 supporting power headroom reporting enhancements according to aspects of the present disclosure is shown. The communication manager 605 can be an example of aspects of the communication manager 415, the communication manager 515, or the communication manager 710 described herein. The communication manager 605 can include a trigger event configuration component 610, a trigger event detection component 615, a power headroom report transmission component 620, a path loss change component 625, and a power control loop component 630. Each of these modules can communicate with each other directly or indirectly (e.g., via one or more buses).

[0190] The trigger event configuration component 610 can identify a trigger event configuration for power headroom reporting for a first service type having a lower latency condition and a higher reliability condition than a second service type.

[0191] In some examples, trigger event configuration component 610 can receive a trigger event configuration from a base station. In some examples, trigger event configuration component 610 can retrieve a trigger event configuration from a storage device of the UE.

[0192] In some examples, the trigger event configuration component 610 may identify a trigger event configuration for a first service type, the trigger event configuration indicating that a trigger event is to be detected based on receiving a power boost functionality configuration or a power boost functionality reconfiguration for the first service type. In some examples, the trigger event configuration component 610 may identify a trigger event configuration for a first service type, the trigger event configuration indicating that a trigger event is to be detected based on detecting that the UE lacks sufficient margin for power boosting for the first service type. In some examples, the trigger event configuration component 610 may identify a trigger event configuration for a first service type, the trigger event configuration indicating that a trigger event is to be detected based on detecting that the UE lacks sufficient margin for power boosting for the first service type and at least in part based on detecting that a prohibit timer at the UE has expired. In some cases, receiving a power boost functionality configuration or a power boost functionality reconfiguration includes receiving a configuration or reconfiguration of a radio resource control power control parameter or receiving a configuration indicated by an open-loop power control parameter set in downlink control information.

[0193] In some examples, trigger event configuration component 610 may identify a trigger event configuration for a first service type that indicates that a trigger event is to be detected based on detecting that the UE has transitioned from lacking sufficient margin for a power boost for the first service type to having sufficient margin for a power boost for the first service type. In some examples, trigger event configuration component 610 may identify a trigger event configuration for a first service type that indicates that a trigger event is to be detected based on detecting that the UE has transitioned from lacking sufficient margin for a power boost for the first service type to having sufficient margin for a power boost for the first service type, and based at least in part on detecting that a prohibit timer at the UE has expired. In some examples, trigger event configuration component 610 may identify a trigger event configuration for a first service type that indicates that a trigger event is to be detected based on detecting that a timer associated with the first service type has expired.

[0194] In some examples, trigger event configuration component 610 can identify a trigger event configuration for a first service type that indicates that a trigger event is to be detected based on detecting a second trigger event for a power headroom report for a second service type.

[0195] The trigger event detecting component 615 can detect a trigger event for a power headroom report for the first service type. In some examples, the trigger event detecting component 615 can detect a trigger event based on the trigger event configuration.

[0196] Power headroom report sending component 620 can send a power headroom report for the first service type based on detecting the triggering event. In some examples, power headroom report sending component 620 can send a power headroom report associated with a power boost function of the first service type.

[0197] In some examples, power headroom report sending component 620 can send a power headroom report including a power headroom value calculated based on the configured power boost value. In some cases, the configured power boost value is a maximum configured power boost value in a set of configured power boost values.

[0198] In some examples, the power headroom report sending component 620 can send a MAC CE including a power headroom report on a first uplink shared channel for a first service type, a second uplink shared channel for a second service type, or both. In some examples, the power headroom report sending component 620 can send a power headroom report indicating a power headroom value corresponding to a single carrier.

[0199] In some examples, power headroom report sending component 620 can send a power headroom report indicating a set of power headroom values ​​corresponding to a set of carriers, respectively. In some examples, power headroom report sending component 620 can send the power headroom report on a first uplink shared channel for a first service type.

[0200] In some examples, power headroom report sending component 620 can detect a second triggering event for a power headroom report for a second service type. In some examples, power headroom report sending component 620 can avoid sending a second power headroom report for the second service type on an uplink shared channel for the first service type.

[0201] In some examples, the power headroom report sending component 620 can send a power headroom report indicating a power headroom value calculated for at least one carrier configured for the first service type. In some examples, the power headroom report sending component 620 can send the power headroom report on a second uplink shared channel configured for the second service type.

[0202] In some examples, the power headroom report sending component 620 can send the power headroom report on the earlier of a first uplink shared channel configured for the first service type or a second uplink shared channel configured for the second service type. In some cases, the power headroom report does not include power headroom values ​​calculated for any carrier configured for the second service type instead of the first service type. In some cases, the power headroom report is an actual power headroom report, a virtual power headroom report, or both.

[0203] The path loss change component 625 can identify a trigger event configuration for a first service type, the trigger event configuration indicating that a trigger event is to be detected based on detecting a path loss change that satisfies a path loss threshold for the first service type. In some cases, the path loss threshold for the first service type is less than the path loss threshold for the second service type. In some cases, the duration of a timer associated with the first service type is shorter than the duration of a timer associated with the second service type. In some cases, the timer associated with the first service type is a periodic timer or a prohibit timer.

[0204] The power control loop component 630 can send a power headroom report indicating a first power headroom for a first power control loop associated with a first service type and a second power headroom for a second power control loop associated with a second service type. In some cases, the power headroom report includes a first power headroom field for the first power control loop and a second power headroom field for the second power control loop. In some cases, the first power control loop and the second power control loop are configured for the same uplink carrier.

[0205] Figure 7 A schematic diagram 700 of a system 705 including a device supporting power headroom reporting enhancement according to aspects of the present disclosure is shown. The device 705 may be an example of or include a component of the device 405, device 505, or UE 115 as described herein. The device 705 may include components for two-way voice and data communications, including components for sending and receiving communications, including a communication manager 710, an I / O controller 715, a transceiver 720, an antenna 725, a memory 730, and a processor 740. These components may be in electronic communication via one or more buses (e.g., bus 745).

[0206] The communication manager 710 can identify a trigger event configuration for a power headroom report for a first service type having a lower delay condition and a higher reliability condition than a second service type, detect a trigger event for a power headroom report for the first service type based on the trigger event configuration, and send a power headroom report for the first service type based on the detection of the trigger event.

[0207] I / O controller 715 can manage input and output signals for device 705. I / O controller 715 can also manage peripheral devices that are not integrated into device 705. In some cases, I / O controller 715 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 715 can utilize an operating system, such as Or another well-known operating system. In other cases, I / O controller 715 can represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 715 can be implemented as a part of a processor. In some cases, a user can interact with device 705 via I / O controller 715 or via hardware components controlled by I / O controller 715.

[0208] As described above, the transceiver 720 can communicate bidirectionally via one or more antennas, wired or wireless links. For example, the transceiver 720 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 720 can also include a modem to modulate packets and provide the modulated packets to an antenna for transmission, and demodulate packets received from an antenna.

[0209] In some cases, a wireless device may include a single antenna 725. However, in some cases, a device may have more than one antenna 725, which may be capable of sending or receiving multiple wireless transmissions concurrently.

[0210] The memory 730 may include RAM and ROM. The memory 730 may store computer-readable, computer-executable code 735 including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, the memory 730 may also contain, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0211] The actions performed by the communication manager 710 described herein may be implemented to achieve one or more potential advantages at the components of the device 705. For example, by sending a power headroom report that takes into account power boosting, transmit power efficiency at the device 705 may be improved. For example, the device 705 may receive signaling including a transmit power control indication from the scheduling base station 105. The processor 740 may send signaling to the transceiver 720 to adjust the transmit power to a more efficient value so that the device 705 may effectively perform power boosting for low latency transmissions.

[0212] The processor 740 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 740 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 740. The processor 740 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 730) to cause the device 705 to perform various functions (e.g., functions or tasks that support power headroom reporting enhancements).

[0213] The code 735 may include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communications. The code 735 may be stored in a non-transitory computer-readable medium such as a system memory or other type of memory. In some cases, the code 735 may not be directly executable by the processor 740, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

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

[0215] The receiver 810 may receive information associated with various information channels (e.g., control channels, data channels, and information related to power headroom reporting enhancement, etc.), such as packets, user data, or control information. The information may be delivered to other components of the device 805. The receiver 810 may be a reference Fig.11 Examples of aspects of the described transceiver 1120. The receiver 810 may utilize a single antenna or a collection of antennas.

[0216] The communication manager 815 may send a trigger event configuration for a power headroom report of a first service type to the UE, the first service type having a lower delay condition and a higher reliability condition than a second service type, and receive a power headroom report of the first service type from the UE based on the trigger event configuration. The communication manager 815 may be an example of aspects of the communication manager 1110 described herein.

[0217] The communication manager 815 or its subcomponents may be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 815 or its subcomponents may be performed by a general purpose processor, a DSP, an application specific integrated circuit (ASIC), an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.

[0218] The communication manager 815 or its subcomponents can be physically located in a variety of locations, including being distributed so that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the communication manager 815 or its subcomponents can be separate and distinct components. In some examples, according to various aspects of the present disclosure, the communication manager 815 or its subcomponents can be combined with one or more other hardware components, including but not limited to input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof.

[0219] Transmitter 820 can transmit signals generated by other components of device 805. In some examples, transmitter 820 can be co-located with receiver 810 in a transceiver module. For example, transmitter 820 can be a reference Fig.11 Examples of aspects of the described transceiver 1120. The transmitter 820 may utilize a single antenna or a collection of antennas.

[0220] Fig. 9 A block diagram 900 of a device 905 supporting power headroom reporting enhancements according to aspects of the present disclosure is shown. The device 905 may be an example of aspects of the device 805 or base station 105 as described herein. The device 905 may include a receiver 910, a communication manager 915, and a transmitter 930. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0221] The receiver 910 may receive information associated with various information channels (e.g., control channels, data channels, and information related to power headroom reporting enhancement, etc.), such as packets, user data, or control information. The information may be delivered to other components of the device 905. The receiver 910 may be a reference Fig.11 Examples of aspects of the described transceiver 1120. The receiver 910 may utilize a single antenna or a collection of antennas.

[0222] The communication manager 915 can be an example of aspects of the communication manager 815 described herein. The communication manager 915 can include a triggering event configuring component 920 and a power headroom report receiving component 925. The communication manager 915 can be an example of aspects of the communication manager 1110 described herein.

[0223] The trigger event configuration component 920 can send a trigger event configuration for a power headroom report of a first service type to the UE, the first service type having a lower delay condition and a higher reliability condition than the second service type. The power headroom report receiving component 925 can receive a power headroom report of the first service type from the UE based on the trigger event configuration.

[0224] Transmitter 930 can transmit signals generated by other components of device 905. In some examples, transmitter 930 can be co-located with receiver 910 in a transceiver module. For example, transmitter 930 can be a reference Fig.11 Examples of aspects of the described transceiver 1120. The transmitter 930 may utilize a single antenna or a collection of antennas.

[0225] Fig.10 A block diagram 1000 of a communication manager 1005 supporting power headroom reporting enhancements according to aspects of the present disclosure is shown. The communication manager 1005 can be an example of aspects of the communication manager 815, the communication manager 915, or the communication manager 1110 described herein. The communication manager 1005 can include a trigger event configuration component 1010, a power headroom report receiving component 1015, a path loss variation component 1020, and a power control loop component 1025. Each of these modules can communicate with each other directly or indirectly (e.g., via one or more buses).

[0226] The trigger event configuration component 1010 may send a trigger event configuration for a power headroom report for a first service type to the UE, the first service type having a lower latency condition and a higher reliability condition than a second service type. In some examples, the trigger event configuration component 1010 may send a trigger event configuration indicating that a trigger event for a power headroom report for the first service type is to be detected based on receiving a power boost function configuration or a power boost function reconfiguration for the first service type.

[0227] In some examples, trigger event configuration component 1010 may send a trigger event configuration indicating that a trigger event for power headroom reporting for the first service type is to be detected based on a lack of sufficient headroom for power boosting for the first service type and based on expiration of a prohibit timer at the UE. In some examples, trigger event configuration component 1010 may send a trigger event configuration indicating that a trigger event for power headroom reporting for the first service type is to be detected based on detecting a transition from a lack of sufficient headroom for power boosting for the first service type to having sufficient headroom for power boosting for the first service type and based on expiration of a prohibit timer at the UE.

[0228] In some examples, trigger event configuration component 1010 can send a trigger event configuration indicating that a trigger event for a power headroom report for a first service type is to be detected based on detecting that a timer associated with the first service type has expired. In some examples, trigger event configuration component 1010 can send a trigger event configuration indicating that a trigger event for a power headroom report for a first service type is to be detected based on detecting a second trigger event for a power headroom report for a second service type.

[0229] In some examples, the trigger event configuration component 1010 can receive a power headroom report on a second uplink shared channel configured for the second service type. In some cases, the duration of the timer associated with the first service type is shorter than the duration of the timer associated with the second service type. In some cases, the timer associated with the first service type is a periodic timer or a prohibit timer.

[0230] The power headroom report receiving component 1015 can receive a power headroom report for the first service type from the UE based on the trigger event configuration. In some examples, the power headroom report receiving component 1015 can receive a power headroom report associated with a power boost function for the first service type.

[0231] In some examples, the power headroom report receiving component 1015 can receive a power headroom report including a power headroom value calculated based on the configured power boost value. In some examples, the power headroom report receiving component 1015 can receive a MAC CE including a power headroom report on a first uplink shared channel for a first service type, a second uplink shared channel for a second service type, or both.

[0232] In some examples, power headroom report receiving component 1015 can receive a power headroom report indicating a power headroom value corresponding to a single carrier. In some examples, power headroom report receiving component 1015 can receive a power headroom report indicating a set of power headroom values ​​corresponding to a set of carriers, respectively.

[0233] In some examples, the power headroom report receiving component 1015 can receive a power headroom report on an uplink shared channel for the first service type. In some examples, the power headroom report receiving component 1015 can receive a power headroom report indicating a power headroom value calculated for at least one carrier configured for the first service type.

[0234] In some examples, the power headroom report receiving component 1015 can receive the power headroom report on the earlier of a first uplink shared channel configured for the first service type or a second uplink shared channel configured for the second service type.

[0235] In some cases, the configured power boost value is the maximum configured power boost value in a set of configured power boost values. In some cases, the triggering event configuration indicates that the UE is avoided from sending a second power headroom report for the second service type on an uplink shared channel for the first service type. In some cases, the power headroom report does not include a power headroom value calculated for any carrier configured for the second service type instead of the first service type. In some cases, the power headroom report is an actual power headroom report, a virtual power headroom report, or both.

[0236] The path loss change component 1020 can send a trigger event configuration indicating that a trigger event for a power headroom report for the first service type is to be detected based on detecting a path loss change that satisfies a path loss threshold for the first service type. In some cases, the path loss threshold for the first service type is less than the path loss threshold for the second service type.

[0237] The power control loop component 1025 can receive a power headroom report indicating a first power headroom for a first power control loop associated with a first service type and a second power headroom for a second power control loop associated with a second service type. In some cases, the power headroom report includes a first power headroom field for the first power control loop and a second power headroom field for the second power control loop. In some cases, the first power control loop and the second power control loop are configured for the same uplink carrier.

[0238] Fig.11A schematic diagram 1100 of a system 1105 including a device supporting power headroom reporting enhancement according to aspects of the present disclosure is shown. The device 1105 may be an example of or include components of the device 805, device 905, or base station 105 as described herein. The device 1105 may include components for two-way voice and data communications, including components for sending and receiving communications, including a communication manager 1110, a network communication manager 1115, a transceiver 1120, an antenna 1125, a memory 1130, and a processor 1140 and an inter-station communication manager 1145. These components may be in electronic communication via one or more buses (e.g., bus 1150).

[0239] The communication manager 1110 can send a trigger event configuration for a power headroom report of a first service type to the UE, where the first service type has a lower delay condition and a higher reliability condition than a second service type, and receive a power headroom report of the first service type from the UE based on the trigger event configuration.

[0240] The network communications manager 1115 may manage communications with the core network (eg, via one or more wired backhaul links). For example, the network communications manager 1115 may manage the delivery of data communications for client devices such as one or more UEs 115 .

[0241] As described above, the transceiver 1120 can communicate bidirectionally via one or more antennas, wired or wireless links. For example, the transceiver 1120 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 1120 can also include a modem to modulate packets and provide the modulated packets to an antenna for transmission, and demodulate packets received from an antenna.

[0242] In some cases, a wireless device may include a single antenna 1125. However, in some cases, a device may have more than one antenna 1125, which may be capable of sending or receiving multiple wireless transmissions concurrently.

[0243] The memory 1130 may include RAM, ROM, or a combination thereof. The memory 1130 may store computer readable code 1135 including instructions that, when executed by a processor (e.g., processor 1140), cause the device to perform various functions described herein. In some cases, the memory 1130 may also contain, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral device components or devices.

[0244] Processor 1140 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1140 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into processor 1140. Processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1130) to cause device 1105 to perform various functions (e.g., functions or tasks that support power headroom reporting enhancements).

[0245] The inter-site communication manager 1145 may manage communications with other base stations 105 and may include a controller or scheduler for coordinating with other base stations 105 to control communications with UE 115. For example, the inter-site communication manager 1145 may coordinate scheduling of transmissions to UE 115 for various interference mitigation techniques, such as beamforming or joint transmission. In some examples, the inter-site communication manager 1145 may provide an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between base stations 105.

[0246] The code 1135 may include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communications. The code 1135 may be stored in a non-transitory computer-readable medium such as a system memory or other type of memory. In some cases, the code 1135 may not be directly executable by the processor 1140, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0247] Fig.12 1 is a flowchart illustrating a method 1200 for supporting power headroom reporting enhancement according to aspects of the present disclosure. The operations of the method 1200 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a UE 115 or a component thereof as described herein. Figures 4 to 7 The communication manager described in the embodiment of the present invention performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0248] At 1205, the UE may identify a triggering event configuration for a power headroom report for a first service type, the first service type having a lower latency condition and a higher reliability condition than a second service type. The operation of 1205 may be performed according to the methods described herein. In some examples, aspects of the operation of 1205 may be as described in reference to Figures 4 to 7 Describes the triggering events that configure component execution.

[0249] At 1210, the UE may detect a triggering event for a power headroom report for the first service type based on the triggering event configuration. The operations of 1210 may be performed according to the methods described herein. In some examples, aspects of the operations of 1210 may be as described in reference to Figures 4 to 7 Describes the triggering event detection component execution.

[0250] At 1215, the UE may send a power headroom report for the first service type based on detecting the triggering event. The operations of 1215 may be performed according to the methods described herein. In some examples, aspects of the operations of 1215 may be as described in reference to Figures 4 to 7 Describes the power headroom report sending component performed.

[0251] Fig.13 1 is a flowchart illustrating a method 1300 for supporting power headroom reporting enhancement according to aspects of the present disclosure. The operations of the method 1300 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE 115 or a component thereof as described herein. Figures 4 to 7 The communication manager described in the embodiment of the present invention performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0252] At 1305, the UE may receive a trigger event configuration for a power headroom report for a first service type from a base station, the first service type having a lower delay condition and a higher reliability condition than a second service type. The operation of 1305 may be performed according to the methods described herein. In some examples, aspects of the operation of 1305 may be as described in reference to Figures 4 to 7 Describes the triggering events that configure component execution.

[0253] At 1310, the UE may detect a triggering event for a power headroom report for the first service type based on the triggering event configuration. The operations of 1310 may be performed according to the methods described herein. In some examples, aspects of the operations of 1310 may be as described in reference to Figures 4 to 7 Describes the triggering event detection component execution.

[0254] At 1315, the UE may send a power headroom report for the first service type based on detecting the triggering event. The operations of 1315 may be performed according to the methods described herein. In some examples, aspects of the operations of 1315 may be as described in reference to Figures 4 to 7 Describes the power headroom report sending component performed.

[0255] Fig.141400 is a flowchart illustrating a method 1400 for supporting power headroom reporting enhancement according to aspects of the present disclosure. The operations of the method 1400 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE 115 or a component thereof as described herein. Figures 4 to 7 The communication manager described in the embodiment of the present invention performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0256] At 1405, the UE may retrieve a trigger event configuration for a power headroom report for a first service type from a storage device of the base station, the first service type having a lower latency condition and a higher reliability condition than a second service type. The operation of 1405 may be performed according to the methods described herein. In some examples, aspects of the operation of 1405 may be as described in reference to Figures 4 to 7 Describes the triggering events that configure component execution.

[0257] At 1410, the UE may detect a triggering event for a power headroom report for the first service type based on the triggering event configuration. The operations of 1410 may be performed according to the methods described herein. In some examples, aspects of the operations of 1410 may be as described in reference to Figures 4 to 7 Describes the triggering event detection component execution.

[0258] At 1415, the UE may send a power headroom report for the first service type based on detecting the triggering event. The operations of 1415 may be performed according to the methods described herein. In some examples, aspects of the operations of 1415 may be as described in reference to Figures 4 to 7 Describes the power headroom report sending component performed.

[0259] Fig.15 1 is a flowchart illustrating a method 1500 for supporting power headroom reporting enhancement according to aspects of the present disclosure. The operations of the method 1500 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE 115 or a component thereof as described herein. Figures 4 to 7 The communication manager described in the embodiment of the present invention performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0260] At 1505, the UE may identify a trigger event configuration for a power headroom report for a first service type, the first service type having a lower latency condition and a higher reliability condition than a second service type. The operation of 1505 may be performed according to the methods described herein. In some examples, aspects of the operation of 1505 may be as described in reference to Figures 4 to 7 Describes the triggering events that configure component execution.

[0261] At 1510, the UE may detect a triggering event for a power headroom report for the first service type based on the triggering event configuration. The operations of 1510 may be performed according to the methods described herein. In some examples, aspects of the operations of 1510 may be as described in reference to Figures 4 to 7 Describes the triggering event detection component execution.

[0262] At 1515, the UE may send a power headroom report indicating a first power headroom of a first power control loop associated with the first service type and a second power headroom of a second power control loop associated with the second service type based on detecting the triggering event. The operations of 1515 may be performed according to the methods described herein. In some examples, aspects of the operations of 1515 may be as described in reference to Figures 4 to 7 Some aspects of the operation of 1515 may be performed by the power headroom report sending component described in reference to Figures 4 to 7 The power control loop components described are implemented.

[0263] Fig.16 A flow chart illustrating a method 1600 for supporting power headroom reporting enhancement according to aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of the method 1600 may be implemented by a base station 105 or components thereof as described herein. Figures 8 to 11 The communication manager described in the present invention performs. In some examples, the base station may execute an instruction set to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.

[0264] At 1605, the base station may send a trigger event configuration for a power headroom report for a first service type to the UE, the first service type having a lower delay condition and a higher reliability condition than a second service type. The operation of 1605 may be performed according to the method described herein. In some examples, aspects of the operation of 1605 may be as described in reference to Figures 8 to 11 Describes the triggering events that configure component execution.

[0265] At 1610, the base station may receive a power headroom report of the first service type from the UE based on the trigger event configuration. The operations of 1610 may be performed according to the methods described herein. In some examples, aspects of the operations of 1610 may be as described in reference to Figures 8 to 11 A power headroom report receiving component is described as being performed.

[0266] Fig.171700 is a flowchart illustrating a method 1700 for supporting power headroom reporting enhancement according to aspects of the present disclosure. The operations of the method 1700 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of the method 1700 may be implemented by a base station 105 or components thereof as described herein. Figures 8 to 11 The communication manager described in the present invention performs. In some examples, the base station may execute an instruction set to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.

[0267] At 1705, the base station may send a trigger event configuration for a power headroom report for a first service type to the UE, the first service type having a lower delay condition and a higher reliability condition than a second service type. The operation of 1705 may be performed according to the method described herein. In some examples, aspects of the operation of 1705 may be as described in reference to Figures 8 to 11 Describes the triggering events that configure component execution.

[0268] At 1710, the base station may receive a power headroom report indicating a first power headroom of a first power control loop associated with a first service type and a second power headroom of a second power control loop associated with a second service type from a UE based on a triggering event configuration. The operations of 1710 may be performed according to the methods described herein. In some examples, aspects of the operations of 1710 may be as described in reference to Figures 8 to 11 Some aspects of the operation of 1710 may be performed by the power headroom report receiving component described in reference to Figures 8 to 11 The power control loop components described are implemented.

[0269] Fig.18 1 is a flowchart illustrating a method 1800 for supporting power headroom reporting enhancement according to aspects of the present disclosure. The operations of the method 1800 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a UE 115 or a component thereof as described herein. Figures 4 to 7 The communication manager described in the embodiment of the present invention performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0270] At 1805, the UE may detect a trigger event for a power headroom report for a first service type based on a trigger event configuration, the first service type having a lower latency condition and a higher reliability condition than a second service type. The operation of 1805 may be performed according to the methods described herein. In some examples, aspects of the operation of 1805 may be as described in reference to Figures 4 to 7 Describes the triggering event detection component execution.

[0271] At 1810, the UE may send a power headroom report for the first service type based on detecting the triggering event. The operations of 1810 may be performed according to the methods described herein. In some examples, aspects of the operations of 1810 may be as described in reference to Figures 4 to 7 Describes the power headroom report sending component performed.

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

[0273] The technology described herein can be used in various wireless communication systems, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA) and other systems. CDMA systems can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000, IS-95 and IS-856 standards. IS-2000 release versions are generally referred to as CDMA20001X, 1X, etc. IS-856 (TIA-856) is generally referred to as CDMA2000 1xEV-DO, High Speed ​​Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. TDMA systems can implement radio technologies such as Global System for Mobile Communications (GSM).

[0274] OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS). LTE, LTE-A, and LTE-APro are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-APro, NR, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The technology described herein can be used for the systems and radio technologies mentioned herein as well as other systems and radio technologies. Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may be applicable beyond LTE, LTE-A, LTE-A Pro, or NR applications.

[0275] A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to UEs with service subscriptions to a network provider. Compared to a macro cell, a small cell may be associated with a low-power base station, and the small cell may operate in the same or different (e.g., licensed or unlicensed) frequency band as the macro cell. According to various examples, a small cell may include a pico cell, a femto cell, and a micro cell. For example, a pico cell may cover a small geographic area and may allow unrestricted access to UEs with service subscriptions to a network provider. A femto cell may also cover a small geographic area (e.g., a home) and may provide limited access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). An eNB for a macro cell may be referred to as a macro eNB. An eNB for a small cell may be referred to as a small cell eNB, a pico eNB, a femto eNB, or a home eNB. An eNB may support one or more (e.g., two, three, four, etc.) cells and may also support communications using one or more component carriers.

[0276] The wireless communication systems described herein may support synchronous or asynchronous operation. For synchronous operation, the base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, the base stations may have different frame timing, and transmissions from different base stations may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.

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

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

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

[0280] Computer-readable media include both non-transitory computer storage media and communication media, and communication media include any media that facilitates the transfer of computer programs from one place to another.Non-transitory storage media can be any available media that can be accessed by a general or special computer.As an example and not limitation, non-transitory computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, disk storage or other magnetic storage devices, or can be used to carry or store required program code components in the form of instructions or data structures and can be accessed by a general or special computer or a general or special processor.Any other non-transitory medium.Moreover, any connection is properly referred to as computer-readable media.For example, if software is sent from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwaves, coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwaves are included in the definition of medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

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

[0282] In the drawings, similar components or features may have the same reference number. In addition, various components of the same type may be distinguished by following the reference number with a dash and a second reference that distinguishes between similar components. If only the first reference number is used in the specification, the specification applies to any of the similar components having the same first reference number, regardless of the second or other subsequent reference numbers.

[0283] The description presented herein in conjunction with the accompanying drawings describes exemplary configurations and does not represent all examples that may be implemented or within the scope of the claims. The term "exemplary" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "superior to other examples." In order to provide an understanding of the described technology, the detailed description includes specific details. However, these technologies may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

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

Claims

1. A method for wireless communication by a user equipment UE, comprising: detecting a triggering event for a power headroom report for a first service type based at least in part on a triggering event configuration for a power headroom report for the first service type, the first service type having a lower latency condition and a higher reliability condition than a second service type, the triggering event for the power headroom report for the first service type being different from a second triggering event for the power headroom report for the second service type; sending a power headroom report for the first service type based at least in part on detecting the triggering event; receiving first control signaling indicating a first set of resources for transmitting a first uplink message of the first service type based at least in part on the power headroom report, wherein the first set of resources at least in part overlaps with a second set of resources for transmitting a second uplink message of the second service type; receiving second control signaling instructing to adjust the transmit power of the UE based at least in part on the power headroom report; and The first uplink message of the first service type is transmitted using an adjusted transmit power via the first set of resources.

2. The method according to claim 1, wherein: Sending the power headroom report includes: The power headroom report is sent on a first uplink shared channel for the first service type.

3. The method according to claim 1, further comprising: detecting a second triggering event for power headroom reporting for the second service type; as well as Avoid sending a second power headroom report for the second service type on an uplink shared channel for the first service type.

4. The method according to claim 1, wherein: Sending the power headroom report includes: A power headroom report is sent indicating a power headroom value calculated for at least one carrier configured for the first service type.

5. The method according to claim 4, wherein: The power headroom report does not include power headroom values ​​calculated for any carriers configured for the second service type but not the first service type.

6. The method according to claim 1, further comprising: A triggering event configuration for power headroom reporting for the first service type is identified.

7. The method according to claim 6, wherein: Identifying the trigger event configuration includes: The trigger event configuration is received from a network device.

8. The method according to claim 6, wherein: Identifying the trigger event configuration includes: The trigger event configuration is retrieved from a storage device of the UE.

9. The method according to claim 6, wherein: Identifying the trigger event configuration includes: A trigger event configuration for the first service type is identified, the trigger event configuration indicating that the trigger event is to be detected based at least in part on receiving a power boost functionality configuration or a power boost functionality reconfiguration for the first service type.

10. The method according to claim 9, wherein: Receiving the power boost function configuration or the power boost function reconfiguration includes: A configuration or reconfiguration of a radio resource control power control parameter is received, or a configuration of an open loop power control parameter setting indication is received in downlink control information.

11. The method according to claim 6, wherein: Identifying the trigger event configuration includes: Identifying a trigger event configuration for the first service type, the trigger event configuration indicating that the trigger event is to be detected based at least in part on detecting that the UE lacks sufficient margin for power boosting for the first service type and at least in part on detecting that a prohibit timer at the UE has expired.

12. The method according to claim 6, wherein: Identifying the trigger event configuration includes: Identify a trigger event configuration for the first service type, the trigger event configuration indicating that the trigger event is to be detected based at least in part on detecting that the UE has transitioned from lacking sufficient margin for power boost for the first service type to having sufficient margin for power boost for the first service type, and at least in part on detecting that a prohibit timer at the UE has expired.

13. The method according to claim 6, wherein: Identifying the trigger event configuration includes: A trigger event configuration for the first service type is identified, the trigger event configuration indicating that the trigger event is to be detected based at least in part on detecting a change in path loss that satisfies a path loss threshold for the first service type.

14. The method according to claim 6, wherein: Identifying the trigger event configuration includes: A trigger event configuration for the first service type is identified, the trigger event configuration indicating that the trigger event is to be detected based at least in part on detecting that a timer associated with the first service type has expired.

15. The method according to claim 6, wherein: Identifying the trigger event configuration includes: A trigger event configuration for the first service type is identified, the trigger event configuration indicating that the trigger event is to be detected based at least in part on detecting a second trigger event for power headroom reporting for the second service type.

16. The method according to claim 1, wherein: Sending the power headroom report includes: The power headroom report associated with a power boost functionality of the first service type is sent.

17. The method according to claim 1, wherein: Sending the power headroom report includes: A power headroom report is sent that includes a power headroom value calculated based at least in part on the configured power boost value.

18. The method according to claim 1, wherein: Sending the power headroom report includes: A medium access control MAC control element CE including the power headroom report is sent on a first uplink shared channel for the first service type, a second uplink shared channel for the second service type, or both.

19. The method according to claim 1, wherein: Sending the power headroom report includes: A power headroom report is sent indicating a power headroom value corresponding to a single carrier.

20. The method according to claim 1, wherein: Sending the power headroom report includes: A power headroom report indicating a plurality of power headroom values ​​respectively corresponding to the plurality of carriers is transmitted.

21. The method according to claim 1, wherein: The duration of the timer associated with the first service type is shorter than the duration of the timer associated with the second service type.

22. The method according to claim 1, wherein: Sending the power headroom report includes: A power headroom report is sent indicating a first power headroom for a first power control loop associated with the first service type and a second power headroom for a second power control loop associated with the second service type.

23. A method for wireless communication by a network device, comprising: sending a triggering event configuration for a power headroom report of a first service type to a user equipment UE, the first service type having a lower delay condition and a higher reliability condition than a second service type, the triggering event configuration indicating a triggering event for a power headroom report of the first service type, wherein a second triggering event for a power headroom report of the second service type is different from the triggering event for a power headroom report of the first service type; receiving, based at least in part on the triggering event configuration, a power headroom report for the first service type from the UE; sending first control signaling indicating a first set of resources for transmitting a first uplink message of the first service type based at least in part on the power headroom report, wherein the first set of resources at least in part overlaps with a second set of resources for transmitting a second uplink message of the second service type; Sending second control signaling instructing to adjust the transmit power of the UE based at least in part on the power headroom report; and The first uplink message of the first service type is received according to the adjusted transmit power via the first set of resources.

24. The method according to claim 23, wherein: Receiving the power headroom report includes: A power headroom report is received indicating a power headroom value calculated for at least one carrier configured for the first service type.

25. The method according to claim 24, wherein: The power headroom report does not include power headroom values ​​calculated for any carriers configured for the second service type but not the first service type.

26. An apparatus for wireless communication by a user equipment UE, comprising: means for detecting a triggering event for a power headroom report for a first service type based at least in part on a triggering event configuration for a power headroom report for the first service type, the first service type having a lower latency condition and a higher reliability condition than a second service type, the triggering event for the power headroom report for the first service type being different from a second triggering event for the power headroom report for the second service type; means for sending a power headroom report for the first service type based at least in part on the triggering event; means for receiving first control signaling indicating a first set of resources for transmitting a first uplink message of the first service type based at least in part on the power headroom report, wherein the first set of resources at least in part overlaps with a second set of resources for transmitting a second uplink message of the second service type; means for receiving second control signaling instructing to adjust the transmit power of the UE based at least in part on the power headroom report; and Means for transmitting the first uplink message of the first service type using an adjusted transmit power via the first set of resources.

27. The device according to claim 26, wherein The means for sending the power headroom report comprises: Means for sending a power headroom report indicating a power headroom value calculated for at least one carrier configured for the first service type.

28. The device according to claim 27, wherein The power headroom report does not include power headroom values ​​calculated for any carriers configured for the second service type but not the first service type.

29. An apparatus for wireless communication by a network device, comprising: means for sending a triggering event configuration for a power headroom report of a first service type to a user equipment UE, the first service type having a lower delay condition and a higher reliability condition than a second service type, the triggering event configuration indicating a triggering event for a power headroom report of the first service type, wherein the second triggering event for the power headroom report of the second service type is different from the triggering event for the power headroom report of the first service type; means for receiving a power headroom report for the first service type from the UE based at least in part on the triggering event configuration; means for sending first control signaling indicating a first set of resources for transmitting a first uplink message of the first service type based at least in part on the power headroom report, wherein the first set of resources at least in part overlaps with a second set of resources for transmitting a second uplink message of the second service type; means for sending second control signaling instructing to adjust the transmit power of the UE based at least in part on the power headroom report; and Means for receiving the first uplink message of the first service type according to the adjusted transmit power via the first set of resources.

30. The device according to claim 29, wherein: The means for receiving the power headroom report comprises: Means for receiving a power headroom report indicating a power headroom value calculated for at least one carrier configured for the first service type.

31. An apparatus for wireless communication by a user equipment UE, comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the device to: detecting a triggering event for a power headroom report for a first service type based at least in part on a triggering event configuration for a power headroom report for the first service type, the first service type having a lower latency condition and a higher reliability condition than a second service type, the triggering event for the power headroom report for the first service type being different from a second triggering event for the power headroom report for the second service type; sending a power headroom report for the first service type based at least in part on detecting the triggering event; receiving first control signaling indicating a first set of resources for transmitting a first uplink message of the first service type based at least in part on the power headroom report, wherein the first set of resources at least in part overlaps with a second set of resources for transmitting a second uplink message of the second service type; receiving second control signaling instructing to adjust the transmit power of the UE based at least in part on the power headroom report; and The first uplink message of the first service type is transmitted using an adjusted transmit power via the first set of resources.

32. An apparatus for wireless communication by a network device, comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the device to: sending a triggering event configuration for a power headroom report of a first service type to a user equipment UE, the first service type having a lower delay condition and a higher reliability condition than a second service type, the triggering event configuration indicating a triggering event for a power headroom report of the first service type, wherein a second triggering event for a power headroom report of the second service type is different from the triggering event for a power headroom report of the first service type; receiving, based at least in part on the triggering event configuration, a power headroom report for the first service type from the UE; sending first control signaling indicating a first set of resources for transmitting a first uplink message of the first service type based at least in part on the power headroom report, wherein the first set of resources at least in part overlaps with a second set of resources for transmitting a second uplink message of the second service type; Sending second control signaling instructing to adjust the transmit power of the UE based at least in part on the power headroom report; and The first uplink message of the first service type is received according to the adjusted transmit power via the first set of resources.

33. A non-transitory computer-readable storage medium storing instructions for wireless communication by a user equipment (UE), the instructions causing a processor to: detecting a triggering event for a power headroom report for a first service type based at least in part on a triggering event configuration for a power headroom report for the first service type, the first service type having a lower latency condition and a higher reliability condition than a second service type, the triggering event for the power headroom report for the first service type being different from a second triggering event for the power headroom report for the second service type; sending a power headroom report for the first service type based at least in part on detecting the triggering event; receiving first control signaling indicating a first set of resources for transmitting a first uplink message of the first service type based at least in part on the power headroom report, wherein the first set of resources at least in part overlaps with a second set of resources for transmitting a second uplink message of the second service type; receiving second control signaling instructing to adjust the transmit power of the UE based at least in part on the power headroom report; and The first uplink message of the first service type is transmitted using an adjusted transmit power via the first set of resources.

34. A non-transitory computer-readable storage medium storing instructions for wireless communication by a network device, the instructions causing a processor to: sending a triggering event configuration for a power headroom report of a first service type to a user equipment UE, the first service type having a lower delay condition and a higher reliability condition than a second service type, the triggering event configuration indicating a triggering event for a power headroom report of the first service type, wherein a second triggering event for a power headroom report of the second service type is different from the triggering event for a power headroom report of the first service type; receiving, based at least in part on the triggering event configuration, a power headroom report for the first service type from the UE; sending first control signaling indicating a first set of resources for transmitting a first uplink message of the first service type based at least in part on the power headroom report, wherein the first set of resources at least in part overlaps with a second set of resources for transmitting a second uplink message of the second service type; Sending second control signaling instructing to adjust the transmit power of the UE based at least in part on the power headroom report; and The first uplink message of the first service type is received according to the adjusted transmit power via the first set of resources.