name: PHR
full_form: Power Headroom Report
context: in TS 38.101-1 [14], TS 38.101-2 [15], and TS 38.101-3 [16]) for this cell has changed more than phr-Tx-PowerFactorChange dB since the last transmission of a PHR when the MAC entity had UL resources allocated for transmission or PUCCH transmission on this cell. NOTE 2: The MAC entity should avoid triggering a PHR when the required power backoff due to power management decreases only temporarily (e.g. for up to a few tens of milliseconds) and it should avoid reflecting such temporary decrease in the values of PCMAX,f,c/PH when a PHR is triggered by other triggering conditions. If the MAC entity has UL resources allocated for a new transmission the MAC entity shall: 1> if it is the first UL resource allocated for a new transmission since the last MAC reset: 2> start phr-PeriodicTimer; 1> if the Power Headroom reporting procedure determines that at least one PHR has been triggered and not cancelled; and 1> if the allocated UL resources can accommodate the MAC CE for PHR which the MAC
description: The Power Headroom Report (PHR) is a procedure used in LTE and 5G networks to report the power headroom of a user equipment (UE) to the base station. The procedure involves the UE measuring its transmit power and reporting it to the base station, which then uses this information to adjust the UE's transmit power and maintain optimal network performance.
explanation: The context describes the Power Headroom Report as a procedure that is triggered under certain conditions, such as when the UE's transmit power changes by more than a certain threshold. The procedure involves the UE sending a report to the base station, which then takes action based on the reported information. This matches the definition of a Procedure in the 3GPP specification.
section_title: 7.1.1.3.7UE power headroom reporting / Periodic reporting / DL pathloss change reporting
biotag_Context: O,B-Specification,O,O,B-Specification,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,B-Protocol,O,O,B-Connection,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Connection,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Parameter,I-Parameter,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,B-Protocol,B-Message,O,B-Procedure,O,O,B-Protocol
biotag_Description: O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,B-Technology,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O