Transmission power capping as a thermal mitigation mechanism

Abstract

A user equipment (UE) device in a cellular network implements one or more thermal mitigation techniques based on reducing transmitted power by a cellular modem of the device. The UE device obtains a set of projected transmission (transmission) powers for the device. A projected duty cycle and radio frequency (RF) power savings are obtained for each projected transmission power of the set of projected transmission powers based on a set of uplink performance metrics estimated for a cellular channel. A projected transmission power is selected from the set of projected transmission powers having a highest projected RF power savings within a first threshold tolerance level and a projected RF power savings exceeding a second threshold tolerance level. A transmission power of the cellular modem is capped at the projected transmission power to reduce RF power consumption.

Description

TRANSMISSION POWER CAPPING AS A THERMAL MITIGATION MECHANISMBACKGROUND

[0001] In modern wireless communication devices, the radio frequency (RF) front end is a component that manages the transmission and reception of signals. The RF front end’s power consumption can become substantial, reaching levels as high as, for example, 3 watts (W) in certain adverse conditions. This is particularly problematic in use cases characterized by frequent uplink transmissions, such as video calls, voice calls, and video gaming applications. During these scenarios, the high average current drain associated with the RF front end leads to elevated device temperatures, which have been widely reported by users as a cause of discomfort and potential device performance issues.SUMMARY OF EMBODIMENTS

[0002] In accordance with one aspect, a method at a user equipment (UE) device of a cellular network includes obtaining a set of projected transmission (Tx) powers for the UE device, obtaining a projected duty cycle and radio frequency (RF) power savings for each projected Tx power of the set of projected Tx powers based on a set of uplink performance metrics estimated for a cellular channel, selecting a projected Tx power from the set that has a highest projected RF power savings within a first threshold tolerance level and a projected RF power savings exceeding a second threshold tolerance level, and capping the Tx power at the selected projected Tx power to reduce RF power consumption.

[0003] In at least some embodiments, capping the Tx power reduces a thermal output of the UE device.

[0004] In at least some embodiments, the uplink performance metrics include a Tx power, a duty cycle, a modulation and coding scheme, physical resource blocks, uplink throughput, and an uplink block error rate associated with the cellular channel.

[0005] In at least some embodiments, the method further includes periodically monitoring, during a configurable time interval, the set of uplink performance metricsand updating the set of projected Tx powers to reflect current device-network dynamics based on the monitored set of uplink performance metrics.

[0006] In at least some embodiments, the periodic monitoring further includes periodically monitoring one or more thermal conditions of the UE device, and updating the set of projected Tx powers based on both the monitored set of uplink performance metrics and the monitored one or more thermal conditions.

[0007] In at least some embodiments, the method further includes, triggering the capping of the Tx power responsive to a determination that at least one thermal initiation threshold is exceeded based on a measured device surface temperature and RF power consumption.

[0008] In at least some embodiments, obtaining the projected duty cycle includes calculating the projected duty cycle for each projected Tx power based on one or more transport block size look-up tables.

[0009] In at least some embodiments, obtaining the projected duty cycle and RF power savings for each projected Tx power includes determining a projected duty cycle and projected RF power savings based on one or more uplink performance metrics, and selecting a projected Tx power that both satisfies an acceptable throughput degradation tolerance and meets a predefined RF power savings tolerance.

[0010] In at least some embodiments, determining the projected duty cycle includes adjusting at least one uplink scheduling parameter selected from at least one of a modulation and coding scheme, a physical resource block allocation, or a block error rate to predict the impact of the capped Tx power.

[0011] In at least some embodiments, determining the projected RF power savings includes mapping, for each projected Tx power of the set of projected Tx powers, a current Tx power and the projected Tx power to respective RF power consumption values using a device-specific look-up table, and calculating a percentage reduction in RF power consumption based on the mapping.

[0012] In at least some embodiments, capping the Tx power includes adjusting a maximum transmit power limit of the UE device for a predetermined operational time window.

[0013] In at least some embodiments, responsive to capping the Tx power, the method further includes monitoring the set of uplink performance metrics for a first portion of a monitoring interval, operating at the selected projected Tx power for a remaining second portion of the monitoring interval, and reassessing the selected projected Tx power responsive to the monitoring interval expiring.

[0014] In at least some embodiments, the method further includes restoring the UE device to a default transmit power level responsive to a device surface temperature and an RF power consumption of the UE device satisfying one or more thresholds.

[0015] In at least some embodiments, a user equipment includes one or more radio frequency (RF) modems configured to wirelessly communicate with at least one network, one or more processors coupled to the one or more RF modems, and at least one memory storing executable instructions configured to manipulate at least one of the one or more processors or the one or more RF modems to perform the methods described herein.

[0016] In at least some embodiments, a computer program product includes a set of executable instructions configured to manipulate a user equipment device to perform the methods described herein.BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The present disclosure may be better understood, and its numerous features and advantages made apparent to those skilled in the art, by referencing the accompanying drawings. The use of the same reference symbols in different drawings indicates similar or identical items.

[0018] FIG. 1 is a diagram illustrating an example wireless system employing a User Equipment (UE) device implementing a transmission (Tx) power capping system in accordance with some embodiments.

[0019] FIG. 2 is a diagram illustrating an example hardware configuration of the UE device of FIG. 1 in accordance with some embodiments.

[0020] FIG. 3 is a diagram illustrating an example configuration of the Tx power capping system implemented by the UE device of FIG. 1 in accordance with some embodiments.

[0021] FIG. 4 illustrates examples of algorithms implemented by the Tx power capping system in accordance with some embodiments.

[0022] FIG. 5 is a flow diagram illustrating an example method for dynamically managing thermal mitigation at a UE device during uplink-intensive scenarios in accordance with some embodiments.DETAILED DESCRIPTION

[0023] One approach to address the thermal challenges posed by the RF front end’s power consumption involves reducing the transmission (Tx) power. Lowering the Tx power can decrease the RF front end’s power consumption, potentially leading to improved thermal performance. However, while this method may be effective in certain situations, it is not without drawbacks. Reducing the Tx power can lead to a decrease in the signal-to-noise ratio (SNR) at the base station receiver. In many cases, this reduction in SNR requires the device to compensate by increasing the uplink duty cycle, resulting in an overall increase in power consumption rather than the intended decrease. Therefore, simply capping the Tx power as a thermal mitigation technique may not consistently yield the desired results. The complexity of managing power consumption, thermal performance, and communication quality necessitates a more sophisticated approach that balances these factors to achieve optimal device operation without compromising user experience.

[0024] The behavior of system power consumption relative to range for different Tx power backoffs reveals insights into power management and thermal mitigation. For a configuration with no backoff (operating at the maximum allowable Tx power), power consumption is initially higher compared to configurations with a 3 decibel(dB) or 6 dB backoff. At the outset, the 6 dB backoff configuration demonstratessignificantly lower power consumption, as the available link budget in this region is sufficient to avoid retransmissions through optimized scheduling. However, as the UE device moves farther from the base station, the link budget deteriorates due to increased path loss, leading to a rise in the block error rate. In this scenario, the power consumption associated with the 6 dB backoff increases sharply, eventually surpassing that of configurations with less backoff or no backoff. This occurs because the savings achieved through reduced peak power during each transmission are negated by the additional power required to handle retransmissions.

[0025] In contrast, the 3 dB backoff configuration maintains a balance between reduced peak power consumption and manageable retransmission costs over a longer range. This observation underscores the importance of dynamically adapting the Tx power backoff based on real-time link conditions. The effectiveness of any specific backoff level as a thermal mitigation technique depends on the current state of the link budget and communication environment, emphasizing the need for a context-aware approach to power management.

[0026] Initial field studies were conducted to understand cellular network uplink (UL) behavior under varying cell conditions. The following is a summary of the results observed in these studies. In one example scenario involving a one-on-one video call on a Third Generation Partnership Project (3GPP) Fourth Generation (4G) Long Term Evolution (LTE) band network, uplink scheduling metrics vary with decreasing Reference Signal Received Power (RSRP). In particular, transmitted power (Tx power), Block Error Rate (BLER), Modulation and Coding Scheme (MCS), number of resource blocks (nRB), and throughput (Tput) all change as RSRP decreases. For each RSRP point, the measured data is the average of a set of instantaneous measurements collected from modem logs during the video call.

[0027] As RSRP decreases, the network first responds through Tx power control by gradually increasing the requested Tx power until it reaches the Maximum Transmit Power Level (MTPL) (23 dBm ± 2 dB) at approximately -102 dBm RSRP (where dBm is decibel-milliwatts). The requested Tx power itself may not be directly observed here. Beyond -102 dBm RSRP, the actual Tx power continues increasing between - 102 dBm and -118 dBm due to Maximum Power Reduction (MPR) relaxation as MCSstarts decreasing. After the -102 dBm RSRP point, the network addresses declining link quality by steadily decreasing MCS allocations during each uplink grant, a process known as rate control. This adjustment keeps the BLER below 10% until about -122 dBm RSRP. Although MCS begins decreasing after RSRP falls below - 102 dBm, an increase in uplink grants and a slight increase in nRB maintain Tput above 450 kbps until approximately -116 dBm. Between -116 dBm and -122 dBm, Tput starts degrading even though BLER remains below 10%. This occurs because additional uplink grants cannot fully compensate for the low MCS in this range. After approximately -122 dBm, a drastic increase in BLER, combined with the low MCS and insufficient allocated frequency and time resources, prevents meeting the throughput / performance requirements of the video call application.

[0028] For this study, the region of interest is between -102 dBm and -116 dBm RSRP. Although Tx power is already close to MTPL in this region, further degradation in cell conditions (reduction in RSRP) is compensated by decreasing MCS while keeping nRB constant or slightly increasing it. To maintain performance or throughput, the decrease in spectral efficiency is balanced by the UE device obtaining more uplink (UL) grants, thus raising the uplink duty cycle. Thermal issues during video calls or other uplink-intensive applications often occur in this region due to the combination of high Tx power and increasing duty cycle. Consequently, capping the Tx power in this region can potentially alleviate such thermal problems by lowering RF power consumption without causing drastic performance or throughput reductions.

[0029] For example, assume a cellular device operating at the -110 dBm RSRP point. Backing off the MTPL by 3 dB, or capping the MTPL at 21 dBm instead of the default 24 dBm, is effectively similar to operating a 24 dBm MTPL device at the -113 dBm RSRP point. In response, the network decreases the MCS and slightly increases nRB and uplink grants to keep the BLER below the 10% target and maintain a constant throughput. Reducing Tx power decreases the RF power consumption per transmission, while the impact on average RF power consumption depends on the degree to which the duty cycle increases to compensate for the reduced frequency resources allocated to the UE. Therefore, a robust thermalmitigation technique that aims to employ Tx power capping or backoff should be able to effectively ascertain when reducing Tx power will lead to an increase in RF power consumption or an unacceptable decrease in throughput.

[0030] It should be understood that the scenario described above is merely an example used to illustrate dynamic uplink scheduling behavior under varying cell conditions. Although these patterns are generally representative of many cellular networks, the specific RSRP values at which Tx power reaches MTPL, MCS starts decreasing, throughput begins to degrade, or BLER increases depend on various factors, including the requested application throughput, cell loading, and Tx power control policies (open-loop or closed-loop).

[0031] As such, the following describes embodiments of systems and methods implementing one or more thermal mitigation techniques based on reducing transmitted power by the cellular modem. This technique incorporates one or more algorithms to identify and implement a balanced trade-off between power consumption and performance. As described in greater detail below, the Tx power capping mechanism of one or more embodiments leverages knowledge of dynamic UL scheduling to mitigate device thermals during uplink-intensive use cases without significantly degrading performance. Tx power capping as a thermal mitigation mechanism integrates seamlessly with the existing thermal mitigation frameworks. In at least some embodiments, the Vskin temperature, which is the temperature of the skin surface of an electronic device, derived from various thermistors located at one or more hotspots of the device and the measured RF power consumption derived from the on-device power monitor are some of the parameters used to trigger the Tx power capping mechanism when certain thresholds are met.

[0032] For ease of illustration, the following techniques are described in an example context in which one or more UE devices and one or more RANs implement at least a 5G New Radio (NR) standard (e.g., Third Generation Partnership Project (3GPP) Release 15, 3GPP Release 16, etc.) (hereinafter, “5G NR” or“5G NR standard”). However, it should be understood that the present disclosure is not limited to networks employing a 5G NR RAT configuration, but rather, the techniques described herein can be applied to any combination of different RATs employed at the UEdevices and the RANs. It should also be understood that the present disclosure is not limited to any specific network configurations or architectures described herein. Also, the present disclosure is not limited to the examples and context described herein, but rather, the techniques described herein can be applied to any network environment where a UE device implements thermal mitigation techniques based on reducing transmitted power by the cellular modem.

[0033] FIG. 1 illustrates a mobile cellular network (system) 100 in accordance with at least some embodiments. As shown, the mobile cellular network 100 includes a User Equipment (UE) device 102 that is configured to communicate with one or more Base Stations (BSs) 104 (illustrated as BS 104-1 and BS 104-2) through one or more wireless communication links 106 (illustrated as wireless links 106-1 and 106-2). The UE device 102, in at least some embodiments, includes any of a variety of wireless communication devices, such as a cellular phone, a cellular-enabled tablet computer or cellular-enabled notebook computer, a cellular-enabled wearable device, an automobile, or other vehicle employing cellular services (e.g., for navigation, provision of entertainment services, in-vehicle mobile hotspots, etc.), and so on. In at least some embodiments, the UE device 102 employs a single RAT 108. In other embodiments, the UE device 102 is a multi-mode UE device that employs multiple RATs 108 (illustrated as RAT 108-1 and RAT 108-2). Examples of multiple RATs include cellular-based RATs, such as a 3GPP LTE RAT and a 3GPP 5G NR RAT, a Wi-Fi RAT, and the like. It should be understood that although FIG. 1 only shows the UE device 102 implementing two different RATs 108, the UE device 102, in at least some embodiments, implements three or more different RATs 108. In at least some embodiments, one or more RAT modules 110 (illustrated as RAT module 110-1 and RAT module 110-2) manage the RATs 108 and enable communication between the UE device 102 and the radio access technology of the network 100. The one or more RAT modules 110, in at least some embodiments, include one or more of a modem chipset(s) of the UE device 102, a protocol stack(s), driver software, or the like.

[0034] In at least some embodiments, the BSs 104 are implemented in a macrocell, microcell, small cell, picocell, and the like, or any combination thereof. Examples ofbase stations 104 include an Evolved Universal Terrestrial Radio Access Network Node B (E-UTRAN Node B), Evolved Node B (eNodeB or eNB), Next Generation (NG or NGEN) Node B (gNode B or gNB), and so on. The BSs 104 communicate with the UE DEVICE 102 via the wireless links 106, which are implemented using any suitable type of wireless link. The wireless links 106, in at least some embodiments, include a downlink of data and control information communicated from the base stations 104 to the UE DEVICE 102, an uplink of data and control information communicated from the UE DEVICE 102 to the BSs 104, or both. In at least some embodiments, the wireless links 106 (or bearers), such as Data Radio Bearers (DRBs) and Signal Radio Bearers (SRBs), are implemented using any suitable communication protocol or standard, or combination of communication protocols or standards, such as 3GPP 4G LTE, 5G NR, and so on. In at least some embodiments, multiple wireless links 106 are aggregated in a carrier aggregation to provide a higher data rate for the UE DEVICE 102. Also, multiple wireless links 106 from multiple BSs 104 are configured, in at least some embodiments, for Coordinated Multipoint (CoMP) communication with the UE DEVICE 102, as well as dual connectivity, such as single-RAT LTE-LTE or NR-NR dual connectivity, or Multi-Radio Access Technology (Multi-RAT) Dual Connectivity (MR-DC) including E-UTRA-NR Dual Connectivity (EN-DC), NGEN Radio Access Network (RAN) E-UTRA-NR Dual Connectivity (NGEN-DC), and NR E-UTRA Dual Connectivity (NE-DC).

[0035] The BSs 104 collectively form a Radio Access Network (RAN) 112, such as an E-UTRAN or 5G NR RAN. The base stations 104 are connected to a Core Network (CN) 114 (illustrated as CN 114-1 and CN 114-2) via control-plane and userplane interfaces through one or more links 116 (illustrated as link 116-1 and link 116- 2). Depending on the configuration of the mobile cellular network 100, the core network 114 is either an Evolved Packet Core (EPC) network 114-1 or a 5G Core Network (5GC) 114-2. For example, in an E-UTRAN configuration or a 5G non- standalone (NSA) EN-DC configuration, the core network 114 is an EPC network 114-1 that includes, for example, a Mobility Management Entity (MME) 118, a Serving Gateway (SGW) 120, and a Packet Data Network Gateway (PGW) 122. The MME 118 provides control-plane functions, such as registration and authentication of multiple UEs 102, authorization, mobility management, and so on. The SGW 120transfers user-plane packets related to audio calls, video calls, Internet traffic, and the like. The PGW 122 provides connectivity from the UE device 102 to external packet data networks 124, such as the Internet 126 and an Internet Protocol Multimedia Subsystem (IMS) network 128, by being the point of exit and entry of traffic for the UE DEVICE 102. In a 5G standalone (SA) configuration or an NSA NE-DC or NGEN-DC configuration, the core network 114 is a 5GC network 114-2. The 5GC 114-2 includes, for example, an Access and Mobility Management function (AMP) 130, a User Plane Function (UPF) 132, and a Session Management Function (SMF) 134. The AMF 130 provides control-plane functions such as registration and authentication of multiple UEs 102, authorization, mobility management, and so on. The UPF 132 transfers user-plane packets related to audio calls, video calls, Internet traffic, and the like. The SMF 134 manages Protocol Data Unit (PDU) sessions.

[0036] In at least some embodiments, the core network 114 communicatively couples the UE DEVICE 102 to an IMS network 128 via the RAN 112. The IMS network 128 provides various IMS services to the UE DEVICE 102, such as IMS short messages, IMS Unstructured Supplementary Service Data (USSD), IMS value- added service data, IMS supplementary service data, IMS voice calls, and IMS video calls. To this end, an entity (e.g., a server or a group of servers) operating in the IMS network 128 supports packet exchange with the UE DEVICE 102. The packets convey signaling (such as Session Initiation Protocol (SIP) messages, IP messages, or other suitable messages) as well as data (or media), such as voice or video. In at least some embodiments, the IMS network includes entities (not shown) such as a Proxy Call Session Control Function (P-CSCF), an Interrogating Call Session Control Function (l-CSCF), a Serving Call Session Control Function (S-CSCF), a Home Subscriber Server (HSS), a Media Gateway Control Function (MGCF), and the like.

[0037] As described above, a UE’s RF front end’s power consumption can become substantial in certain adverse conditions. In scenarios involving frequent uplink transmissions, this elevated power consumption results in a high average current drain, which consequently leads to increased temperatures. This can result in users experiencing high thermals during uplink-intensive use cases such as video calls, voice calls, and video gaming applications. Reducing the Tx power can help savepower consumption in some cases. However, there are also cases in which reducing the SNR at the base station receiver by capping the Tx power produces an adverse effect in power consumption due to an increased duty cycle. For this reason, capping the Tx power without proper analysis or adjustment is not always a reliable thermal mitigation technique.

[0038] Therefore, the UE device 102 of one or more embodiments employs a Tx power capping system 136 that leverages knowledge of dynamic UL scheduling to mitigate device thermals during uplink-intensive use cases without significantly degrading performance. In at least some embodiment, the Tx power capping system 136 only caps / backs off the Tx power when it is predicted that Tx power capping has a very high likelihood of reducing the RF power consumption without deteriorating performance. This reduction in RF power consumption translates to improved thermal performance by reducing device temperatures and user experience by extending call times.

[0039] For example, the Tx power capping system 136 uses one or more triggers, such as Vskin temperature or measured RF power consumption, for capping Tx power when certain thresholds are met. By projecting a new optimal Tx power level based on device- network dynamics (e.g., MCS, RB allocation, Tx power, UL duty cycle, transport block size look-up tables, equations provided in 3GPP cellular standards, and the like), the Tx power capping system 136 guarantees a reduction in RF power consumption without sacrificing UL performance. The Tx power capping system 136 can be triggered during different scenarios, such as video calling on a UE device 102 with high temperatures and increased RF power consumption, to limit the Tx power to a value less than the default MTPL without deteriorating call quality.

[0040] FIG. 2 illustrates an example device diagram 200 of a UE device 102. In at least some embodiments, the device diagram 200 describes a UE device that implements the thermal mitigation techniques described herein. The UE device 102 may include additional functions and interfaces that are omitted from FIG. 2 for the sake of clarity. The UE device 102, in at least some embodiments, includes antennas 202, a radio frequency (RF) front end 204, and a modem subsystem 206. The modem subsystem 206 includes multiple transceivers 208 (e.g., a 3GPP 4G LTEtransceiver 208-1 and a 5G NR transceiver 208-2) for communicating with one or more base stations 104 in a RAN 112, such as a 5G RAN, an E-UTRAN, a combination thereof, and so on. The modem subsystem 206 also includes a communication processor 210 (also referred to as a baseband processor or a modem) that is responsible for managing the operations of the transceivers 208. The communication processor 210 includes a Radio Resource Manager (RRM) 212, which manages radio resource allocation, DRX cycles, paging, and handover operations. In at least some embodiments, the communication processor 210 is implemented as a modem baseband processor, software-defined radio module, configurable modem (e.g., multi-mode, multi-band modem), wireless data interface, wireless modem, or so on. The communication processor 210 supports, for example, one or more of data access, messaging, or data-based services of a wireless network, as well as various audio-based communication (e.g., voice calls).

[0041] The RF front end 204, in at least some embodiments, includes a transmitting (Tx) front end 204-1 and a receiving (Rx) front end 204-2. The Tx front end 204-1 includes components such as one or more power amplifiers (PA), drivers, mixers, filters, and so on. The Rx front end 204-2 includes components such as low-noise amplifiers (LNAs), mixers, filters, and so on. The RF front end 204, in at least some embodiments, couples or connects the modem subsystem 206, including the LTE transceiver 208-1 and the 5G NR transceiver 208-2, to the antennas 202 to facilitate various types of wireless communication.

[0042] In at least some embodiments, the antennas 202 of the UE device 102 include an array of multiple antennas configured similarly to or different from each other. The antennas 202 and the RF front end 204, in at least some embodiments, are tuned to or are tunable to one or more frequency bands, such as those defined by the 3GPP LTE, 3GPP 5G NR, IEEE Wireless Local Area Network (WLAN), IEEE Wireless Metropolitan Area Network (WMAN), or other communication standards. In at least some embodiments, the antennas 202, the RF front end 204, and the transceivers 208 are configured to support beamforming (e.g., analog, digital, or hybrid) or In-Phase and Quadrature (l / Q) operations (e.g., I / Q modulation or demodulation operations) for the transmission and reception of communications withone or more base stations 104. By way of example, the antennas 202 and the RF front end 204 operate in sub-gigahertz bands, sub-6 GHz bands, above 6 GHz bands, or a combination of these bands defined by the 3GPP LTE, 3GPP 5G NR, or other communication standards.

[0043] In at least some embodiments, the antennas 202 include one or more receiving antennas positioned in a one-dimensional shape (e.g., a line) or a two- dimensional shape (e.g., a triangle, a rectangle, or an L-shape) for implementations that include three or more receiving antenna elements. While the one-dimensional shape enables the measurement of one angular dimension (e.g., an azimuth or an elevation), the two-dimensional shape enables two angular dimensions to be measured (e.g., both azimuth and elevation). Using at least a portion of the antennas 202, the UE device 102 can form beams that are steered or un-steered, wide or narrow, or shaped (e.g., as a hemisphere, cube, fan, cone, or cylinder). The one or more transmitting antennas may have an un-steered omnidirectional radiation pattern or may produce a wide steerable beam. Either of these techniques enables the UE device 102 to transmit a radio signal to illuminate a large volume of space. In some embodiments, the receiving antennas generate thousands of narrow steered beams (e.g., 2000 beams, 4000 beams, or 5000 beams) with digital beamforming to achieve desired levels of angular accuracy and angular resolution.

[0044] The UE device 102, in at least some embodiments, includes one or more sensors 214 implemented to detect various properties such as one or more of temperature, supplied power, power usage, battery state, or the like. Examples of sensors include a thermal sensor, a battery sensor, a power usage sensor, and so on.

[0045] The UE device 102 also includes at least one processor 216. The processor 216, in at least some embodiments, is a single-core processor or a multiple-core processor composed of a variety of materials, such as silicon, polysilicon, high-K dielectric, copper, and so on. In at least some embodiments, the processor 216 is implemented at least partially in hardware, including, for example, components of an integrated circuit or a System-on-a-Chip (SoC), a Digital-Signal-Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array(FPGA), a Complex Programmable Logic Device (CPLD), other implementations in silicon or other hardware, or a combination thereof. Examples of the processor(s) 216 include a communication processor if not implemented within the modem subsystem 206), an application processor, microprocessors, DSPs, controllers, and so on. An application processor, in at least some embodiments, provides computing resources to applications executing on the UE device 102. For example, an application provides a self-contained operating environment that delivers system capabilities (e.g., graphics processing, memory management, and multimedia processing) to support applications executing on the UE device 102.

[0046] The UE device 102, in at least some embodiments, further includes a Wi-Fi controller 218, which is responsible for managing the device’s connection to Wi-Fi networks. The Wi-Fi controller 218 handles tasks such as scanning for available networks, establishing and maintaining Wi-Fi connections, and managing data transmission over Wi-Fi. The UE device 102 interacts with the modem subsystem 206 and other components to coordinate network access and ensure seamless switching between Wi-Fi and cellular networks. The Wi-Fi controller 218, in at least some embodiments, is implemented as an IC, part of an SoC, or as a discrete component within the UE device 102.

[0047] The UE device 102 further includes a power management unit (PMU) 220, which is responsible for managing power distribution across the various components of the UE device 102, including the RF front end 204, the modem subsystem 206, and the communication processor 210. The PMU 220 optimizes power usage by adjusting the power levels supplied to different components based on their operational state, ensuring that power consumption is minimized during periods of low activity or when certain components are disabled, such as when specific RATs are deprioritized or disabled based on the RAT selection techniques described herein. The PMU 220 also manages battery charging and ensures efficient power delivery to components when needed. In at least some embodiments, the PMU 220 is implemented as an IC that is either part of an SoC or as a discrete component within the UE device 102.

[0048] The UE device 102 further includes a non-transitory computer-readable storage media 222 (CRM 222). The computer-readable storage media described herein excludes propagating signals. The CRM 222, in at least some embodiments, includes any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory useable to store device data 224 of the UE device 102. In at least some embodiments, the device data 224 includes user data, multimedia data, beamforming codebooks, applications 226, an operating system 228 of the UE device 102, a user interface(s) 230, and so on, which are executable by the processor(s) 216 to enable user-plane communication, controlplane signaling, and user interaction with the UE device 102. The user interface 230, in at least some embodiments, is configured to receive inputs from a user of the UE device 102, such as to receive input from a user that defines and or facilitates one or more aspects of adverse radio link condition detection. In at least some embodiments, the user interface 230 includes a graphical user interface (GUI) that receives the input information via a touch input. In other instances, the user interface 230 includes an intelligent assistant that receives the input information via an audible input or speech. Alternatively, or additionally, the operating system 228 of the UE device 102 is maintained as firmware or an application on the CRM 222 and executed by the processor(s) 216.

[0049] The CRM 222, in at least some embodiments, further includes a communication manager 232. Alternatively, or additionally, the communication manager 232, in at least some embodiments, is implemented in whole or part as hardware logic or circuitry integrated with or separate from other components of the UE device 102. In at least some embodiments, the communication manager 232 configures the RF front end 204, the LTE transceiver 208-1 , the 5G NR transceiver 208-2, or a combination thereof to perform one or more wireless communication operations.

[0050] The UE device 102 also includes the Tx power capping system 136. The Tx power capping system 136, in at least some embodiments, is implemented in whole or part as hardware logic or circuitry integrated with or separate from othercomponents of the UE device 102. In other embodiments, one or more portions of the Tx power capping system 136 are implemented in the CRM 222. As shown in FIG. 3, the Tx power capping system 136, in at least some embodiments, includes one or more components, such as an application processor (AP) thermal management system 302 and a modem thermal management system 304.

[0051] The AP thermal management system 302 is responsible for gathering and analyzing thermal data from various device components. In at least some embodiments, the AP thermal management system 302 includes one or more modules. A first module 306, monitors temperatures at various hotspots across the UE device 102 using, for example, thermistors 308 (T1 , T2, ... Tn) to gather real-time thermal data. In at least some embodiments, the first module 306 is implemented as, for example, dedicated sensor interface circuitry, a microcontroller performing analog- to-digital conversions, a software routine executed by a general-purpose processor, and the like.

[0052] A second module 310, evaluates the UE device’s surface temperature, referred to as Vskin 312, and computes a corresponding thermal level indicator (Level) 314 that reflects the overall thermal condition of the UE device 102. In at least some embodiments, the second module 310 is implemented as, for example, a hardware logic block integrated into an ASIC, a firmware routine running on an application processor, a specialized processor core applying calibrated algorithms to sensor data, and the like.

[0053] A third module 316 tracks the device’s RF power consumption, labeled as meas_RF power 318, using for example, an on-device power monitor. In at least some embodiments, the third module 316 is implemented as, for example, a dedicated integrated circuit that measures RF power directly, a programmable logic device (such as an FPGA) that processes raw power signals, a software component executing on the modem’s communication processor to compute averaged RF power metrics in real time, and the like.

[0054] The modem thermal management system 304 integrates thermal data from the AP thermal management system 302 and uses this thermal data to triggerappropriate mitigation mechanisms. For example, the modem thermal management system 304 compares the Level parameter 314 against a predefined set_level_threshold and the meas_RF power parameter 318 against a set_rf_power_threshold. If both thresholds are exceeded, the modem thermal management system 304 triggers a Tx power capping process. This process reduces the Tx power of the UE device 102, thereby mitigating thermal issues while ensuring that UL performance is not significantly degraded.

[0055] The two systems 302, 304, working in tandem, enable a balanced approach to thermal management. By leveraging dynamic device-network parameters, such as measured RF power consumption and device temperature, the Tx power capping system 136 ensures that thermal mitigation actions are only taken when necessary, minimizing performance impacts while effectively managing device thermals.

[0056] In at least some embodiments, the Tx power capping system 136 overcomes the problems of increased temperatures and adverse effects in power consumption by leveraging device-network dynamics (e.g., MCS, RB allocation, Tx power, UL duty cycle, transport block size look-up tables or equations provided in the 3GPP cellular standards, and the like) to project a new optimal Tx power level that can guarantee a reduction in RF power consumption without sacrificing UL performance.

[0057] During cellular use-case scenarios, such as video calling where the high temperatures at the UE device 102 occur from increased RF power consumption, the Tx power capping system 136 caps or backs off the Tx power level using the techniques described herein. For example, assume a video call on the UE device 102 with device temperatures above 40 degrees Celsius (°C), a Tx power level of approximately 24 dBm, and an RF power consumption greater than 300 mW. In this example, the Tx power capping system 136 is triggered to limit the Tx power to a value less than 24 dBm without deteriorating the call quality.

[0058] After determining that the device temperature, Tx power level, and RF power consumption thresholds have been met, the portion of the Tx power capping system 136 implemented in the modem subsystem 206 (or another component) is triggered. For example, in at least some embodiments, the Tx power capping system 136periodically monitors the cellular channel every Ay seconds, where the value of Ay is configurable. The value of Ay can be different for stationary-mode and mobility-mode operating conditions. For the first Ax seconds of each Ay period, the Tx power capping system 136 collects an estimate of the current Tx power (T), duty cycle (5), MCS, nRB (Physical Resource Block (PRB)), UL throughput (Tput), and UL BLER (BLER). Afterwards, the Tx power capping system 136 implements a first algorithm 402 and a second algorithm 404, as shown in FIG. 4, to execute one or more operations for determining a new projected maximum transmit power level (MTPL) value that optimally results in RF power savings without any significant throughput degradation. For the remaining (Ay - Ax) seconds, the modem subsystem 206 operates at the new projected MTPL value.

[0059] The first algorithm 402 and second algorithm 404 shown in FIG. 4 are implemented by the Tx power capping system 136 to leverage knowledge of dynamic UL scheduling gained through, for example, analysis, practical experience and comprehensive evaluations. Using the first algorithm 402, the Tx power capping system 136 selects the optimum projected MTPL from a set of projected Tx power required to throttle RF power consumption and, thus, reduce device temperature during thermal events without significantly sacrificing application performance. The first algorithm 402 evaluates each Tx power in the set of projected Tx power levels (Tproj) to determine the corresponding projected duty cycle (5proi) and RF power savings (RFs ™:1). Inputs to the first algorithm 402 include the set of projected Tx power values, throughput degradation tolerance (ATputtol), and RF power savings tolerance (A / ?F °^nflS). The set of projected Tx power can be defined as any finite set of Tx power levels less than the default MTPL for the operating band. For example, if operating in a power class 3 band with an MTPL of 24 dBm, the set of projected Tx power levels might include {19 dBm, 20 dBm, 21 dBm}. Another example of a set of projected Tx power is {18.5 dBm, 19 dBm, 19.5 dBm, 20 dBm}.

[0060] In at least some embodiments, the projected Tx power values (Tproj) are predetermined and configured into the Tx power capping system 136 based on, for example, device performance evaluations, power class specifications, operational conditions for each band, and the like. These values are selected to represent arange of potential transmit power levels that can effectively balance thermal mitigation and uplink performance. The throughput degradation tolerance (ATputto1) is a configurable parameter obtained from system settings, indicating the maximum acceptable reduction in uplink throughput due to power capping. This parameter is typically defined during the device calibration phase or adjusted dynamically based on user experience requirements and application demands. Similarly, the RF power savings tolerance (AFFsf°^nflS) is defined as the minimum percentage of RF power reduction necessary to justify the thermal trade-off. This tolerance is derived from, for example, empirical data, device thermal profiles, and expected uplink duty cycle patterns, ensuring that power savings translate into meaningful thermal benefits. These inputs can be periodically updated or recalibrated based on real-world performance data, environmental conditions, or user behavior patterns.

[0061] The Tx power capping system 136 performs Step 1 of the first algorithm 402 by iterating through each projected Tx power (Tproj) in the set to evaluate its potential effect on duty cycle and RF power consumption. For Step 2, the Tx power capping system 136 calls the second algorithm 404 for each Tpr0Jto compute the associated 5pr°janc| in Step 3, the Tx power capping system 136 collects the resultsfrom the second algorithm 404 for all candidate Tx power values. Finally, in Step 4, the Tx power capping system selects the optimal Tprojthat maximizes RF power savings (FF / ^ ) while ensuring that the projected duty cycle (5proj) remains within the allowable tolerance ((e.g., 100 + ATputtol)%) and that the RF power savings exceed the required tolerance (^RFsavings)- The selected Tproibecomes the new MTPL for the next (Ay - Ax) seconds.

[0062] The second algorithm 404 implemented by the Tx power capping system 136 calculates the projected duty cycle (0proi) and RF power savings (FFj™nflS) for a given Tproj. Inputs to the second algorithm 404 include the current Tx power (Tcurr), duty cycle (0curr), modulation and coding scheme (MCScurr), physical resource blocks (PRBcurr), uplink throughput (Tputcurr), and block error rate (BLERcurr). These inputs are measured during the first Ax seconds of each Ay period.

[0063] In at least some embodiments, the current Tx power (Tcurr) is directly monitored by the modem’s power management unit 220, which tracks the power levels used during uplink transmission. The duty cycle (6curr), representing the percentage of time the uplink transmission is active, is dynamically measured by the modem based on real-time uplink activity. The modulation and coding scheme (MCScurr), which reflects the link quality and spectral efficiency of the uplink, is determined from the network’s dynamic uplink scheduling and feedback mechanisms. The physical resource blocks (PRBcurr), indicating the number of resource blocks allocated for uplink transmission, are also monitored in real time as part of the modem’s uplink scheduling process. The uplink throughput (Tputcurr) is derived from the data rate currently being achieved on the uplink, while the block error rate (BLERcurr) is measured from network feedback to assess the reliability of the uplink transmission. In at least some embodiments, these inputs are gathered in real time during the first Ax seconds of each monitoring period (Ay), ensuring that the calculations performed by the second algorithm 404 reflect the current state of the device and network conditions. This real-time monitoring enables the Tx power capping system 136 to adapt dynamically to changes in device performance and environmental factors.

[0064] The Tx power capping system 136 performs Step 1 of the second algorithm 404 by computing the difference between the current and projected Tx power (AT = -curr . Tproj) porstep 2, the Tx power capping system 136 adjusts the current MCS to derive the projected MCS (MCSproi), assuming a reduction in Tx power reduces the effective modulation and coding scheme. In Step 3, the Tx power capping system 136 calculates the projected PRB allocation (PRBproj) as a subset of the current PRB allocation. Then, in Step 4, the Tx power capping system 136 estimates the projected duty cycle (6proj) using the projected transport block size (TBS) obtained from 3GPP-defined look-up tables (LUTs) defined in the 3GPP Technical Specifications TS 36. 213 and TS 38.214. The formula for calculating <5pr°i is:Here, lTBSrefers to the transport block size (TBS) index derived from 3GPP-defined look-up tables (LUTs), which map the modulation and coding scheme (MCS) and the number of physical resource blocks (PRB) to the corresponding TBS value. This TBS index is used to determine the projected duty cycle (5proj(Tproj)), which accounts for the throughput (Tputcurr) and block error rate (BLERcurr).

[0065] Finally, in Step 5, the Tx power capping system 136 calculates the RF power savings (RFproisa ings) using a mapping function f(T), which is derived from a LUT specific to the UE device 102. This LUT translates the transmit power (Tcurrand Tproj) into RF power consumption values in milliwatts or milliamperes. The formula for RF power savings is:

[0066] This formula estimates the percentage reduction in RF power consumption achieved by reducing the transmit power to the projected level (Tproj), while accounting for the current duty cycle (6curr) and the projected duty cycle (6proj). The use of the minimum function ensures that the projected duty cycle does not exceed 100%.

[0067] After determining the projected duty cycle and RF power savings for each projected Tx power, the Tx power capping system 136 performs Step 4 of the first algorithm 402 to select the projected Tx power (Tproj) that maximizes RF power savingswhile ensuring that the projected duty cycle (dproj) remains within the allowable tolerance level (e.g., (100 + ATputtol)%) and the projected RF power savings exceed the required tolerance level ( RFs°vlings). The selected Tprojis then set as the new maximum transmit power level (MTPL) for the device to operate within during the next (Ay - Ax) seconds.

[0068] It should be understood that the described Tx power capping and thermal mitigation techniques are not limited to the embodiments described above. The algorithms described herein provide a flexible framework that can be applied to any Tx power capping implementation capable of dynamically projecting RF power consumption and throughput based on transport block size, MCS, and resourceallocation parameters. These techniques may also be extended or adapted to accommodate evolving network standards, environmental conditions, or additional system-specific constraints, ensuring that the device maintains an optimal balance between thermal management and uplink performance.

[0069] In an additional embodiment, RF power consumption curves (power saving requirement of the techniques described herein) are used to determine a lower- bound of the operating UL duty cycle, while the TBS or throughput requirement is used to determine the upper-bound of the operating UL duty cycle. Combining power consumption and throughput constraint:0.95 (EQ. 3).If only capping Tx power greater than 23 dBm to 21 dBm is assumed, and allowing throughput to degrade by as much as 20%, then:

[0070] In at least some embodiments, the thermal mitigation techniques described herein are implemented in other devices, such as smart watches, tablets, vehicles, and the like to cap Tx power for either thermal mitigation or power optimization purposes without sacrificing performance such as UL latency or throughput. Also, the techniques described herein are applicable to different cellular deployments, such as LTE, 5G SA or 5G NSA. Also, in at least some embodiments, the techniques described herein are used to optimize power for power class 1 .5 devices. These devices operate at an MTPL of 29 dBm. The techniques described herein can also be applied to reduce RF power consumption in power class 1.5 devices, regardless of thermal conditions or use case scenarios.

[0071] Evaluation of the Tx power capping techniques described herein was carried out through a series of field and simulation studies using example configurations. The field study involved multiple interleaved tests between two devices. In these tests, one device operated at the default MTPL of 24 dBm, representative of a power class 3 device, while the second device had its MTPL capped at 21 dBm, reflecting a3 dB backoff. Each test involved both devices sending and receiving UDP traffic in a manner that simulates a video call. Each session lasted for 30 seconds and was repeated 16 times. After each test, performance metrics, including MCS, PRB, duty cycle, RSRP, Tx power, throughput, and RF power consumption, were collected and analyzed. The tests were repeated across various locations and carrier networks to assess the behavior under different conditions.

[0072] Results from these interleaved tests revealed the impact of capping the Tx power at 21 dBm compared to operating at the default MTPL of 24 dBm. Specifically, the analysis demonstrated that capping the Tx power can reduce RF power consumption in certain scenarios without major degradation to throughput. However, the results also showed variability depending on uplink scheduling behavior. In some cases, capping the Tx power caused slight performance degradations, while in others, it resulted in substantial RF power savings. These observations highlighted the need for a more refined approach to Tx power capping, which is addressed by the techniques described herein.

[0073] One insight from the evaluation is that capping Tx power without a proper assessment of conditions does not guarantee RF power savings or acceptable performance. Uplink scheduling intricacies, such as MCS adaptation and RB allocation, play a role in determining whether power savings can be achieved without noticeable throughput degradation. Therefore, the techniques described herein optimize the selection of an MTPL that maximizes the likelihood of RF power savings while ensuring minimal impact on uplink throughput and overall user experience.

[0074] Another observation is that the likelihood of achieving power savings increases when the uplink duty cycle exceeds. For example, 70%. This is due to the upper limit of the achievable duty cycle (100%), which amplifies the effects of Tx power reduction. However, as the duty cycle increases, the risk of throughput degradation also rises. This trade-off is addressed by the alternative Tx power backoff mechanism described herein, which dynamically balances the need for power savings and throughput preservation.

[0075] Additional details from one test illustrate how uplink scheduling mechanisms enable Tx power capping to achieve RF power savings without compromising throughput. For example, reducing the Tx power from 24 dBm to 21 dBm may result in a lower MCS, but this can be offset by an increase in allocated resource blocks (RBs). This scheduling adjustment can stabilize the duty cycle, minimize throughput impact, and significantly reduce RF power consumption. These scheduling dynamics are what the Tx power capping mechanism predicts when implementing the second algorithm 404 and incorporates into its calculations when selecting the appropriate Tx power cap.

[0076] Further evaluation involved simulating the behavior of the second algorithm 404 by assuming a projected Tx power cap of 21 dBm and using real-world data collected from the 24 dBm device during the interleaved tests. The results showed that the second algorithm 404 consistently identified scenarios where power savings exceeded a tolerance (e.g., a 5% tolerance) without throughput degradation exceeding a tolerance (e.g., a 10% tolerance). This evaluation demonstrated the algorithm’s ability to accurately project and recommend Tx power caps based on current network conditions and device metrics.

[0077] Overall, the tests confirmed that capping Tx power under the right conditions yields significant RF power savings while preserving acceptable uplink throughput. The techniques described herein rely on an intelligent, context-aware framework that optimally balances thermal mitigation and performance. For example, scenarios where the algorithm 404 recommended a 3 dB Tx power backoff often resulted in improved thermal performance without noticeable degradation in user experience.

[0078] The thermal impact of the Tx power capping techniques was also evaluated. By translating RF power savings into thermal performance, it was observed that reducing the Tx power from 24 dBm to 21 dBm improved the time it took for the device skin temperature (Vskin) to reach 40°C during a video call scenario.

[0079] In summary, the field and simulation results demonstrate that the Tx power capping techniques described herein effectively enhance thermal performance during uplink-intensive scenarios. The described techniques leverage link adaptationmechanisms, such as MGS and RB allocation, to achieve power savings while maintaining acceptable throughput performance. Evaluation results showed improvement in RF power consumption (e.g., up to at least a 40% improvement) and improvement in thermal performance (e.g., up to at least a 12% improvement), with uplink throughput degradation limited to less than 10%. While these tests simulated traffic patterns similar to video calls, the generality of the techniques ensures their applicability across a wide range of use cases and traffic patterns.

[0080] FIG. 5 illustrates a flow diagram of a method 500 for dynamically managing thermal mitigation at a UE device 102 during uplink-intensive scenarios. The processes described below with respect to method 500 are detailed further with reference to FIGs. 1 through 5 above. For purposes of description, the method 500 is described with respect to an example implementation of the UE device 102 described above with respect to FIG. 1 to FIG. 3, but it will be appreciated that, in other implementations, the method 500 is performed within systems with different configurations of the UE device 102. Furthermore, the method 500 is not limited to the sequence of operations shown in FIG. 5, as at least some operations can occur in parallel or in a different sequence. Additionally, in at least some implementations, the method 500 can include one or more different operations beyond those depicted in FIG. 5.

[0081] At block 502, the Tx power capping system 136 of the UE device 102 monitors thermal and RF power metrics. For example, the Tx power capping system 136 collects real-time data on the device’s thermal state and power consumption. The Tx power capping system 136 uses various sensors, such as thermistors, to measure the surface temperature (Vskin) and internal hotspots. In at least some embodiments, an on-device power monitor measures RF power consumption during uplink transmissions. This data provides a comprehensive view of the device’s current thermal and power conditions, establishing the foundation for subsequent evaluations.

[0082] At block 504, the Tx power capping system 136 evaluates thresholds to determine whether thermal mitigation is needed. For example, the Tx power capping system 136 analyzes the metrics collected from block 502, including the device’ssurface temperature (Vskin) and RF power consumption. These values are compared against pre-defined thresholds that dynamically adapt based on the device’s operational state, environmental conditions, and application demands. For instance, if Vskin exceeds a critical temperature threshold or if RF power consumption surpasses acceptable limits, the Tx power capping system 136 identifies a need for thermal mitigation. When thresholds are exceeded, the Tx power capping system 136 initiates the mitigation process. If the thresholds are not met, the Tx power capping system 136 concludes that no action is necessary, allowing the UE device 102 to continue normal operation without modifying the transmit power, and the method exits at block 520.

[0083] At block 506, the Tx power capping system 136 evaluates real-time devicenetwork dynamics to assess the feasibility of applying a Tx power cap. In at least some embodiments, this evaluation involves analyzing one or more uplink scheduling parameters, such as MCS, RB allocation, uplink duty cycle, BLER, a combination thereof, and the like. The Tx power capping system 136 uses this information to predict how reducing Tx power would impact uplink performance. For example, a low MCS or high duty cycle indicates that capping Tx power could risk throughput degradation or necessitate increased retransmissions, offsetting any thermal benefits. The Tx power capping system 136 ensures that it only proceeds with capping if the analysis confirms a high likelihood of reducing RF power consumption without significantly affecting performance, thereby maintaining user experience.

[0084] At block 508, the Tx power capping system 136 applies its first algorithm 402 to determine the optimal Tx power cap. Using insights from block 506, the Tx power capping system 136 evaluates a predefined range of potential Tx power levels. The Tx power capping system 136 iterates through these levels to calculate the projected impact of each on RF power savings, uplink duty cycle, and throughput. These calculations consider factors such as acceptable throughput degradation tolerances and minimum RF power savings thresholds. For example, the first algorithm 402 may identify that reducing the Tx power by 3 dB achieves significant RF power savings while keeping throughput degradation within acceptable limits. The Tx power capping system 136 selects the Tx power level that offers the best balance betweenthermal mitigation and performance retention, ensuring minimal disruption to the user experience.

[0085] At block 510, the Tx power capping system 136 applies its second algorithm 404 to compute projected duty cycle and RF power savings. For the Tx power level identified in block 508, the Tx power capping system 136 calculates the corresponding duty cycle and RF power consumption using real-time inputs, such as the current Tx power, duty cycle, MCS, and RB allocation. The second algorithm 404 estimates how the new Tx power level will affect uplink performance, including expected changes in throughput and BLER. By referencing 3GPP-defined look-up tables and formulas, the Tx power capping system 136 ensures that the selected Tx power level achieves thermal mitigation objectives while maintaining acceptable network performance and application quality of service.

[0086] At block 512, the Tx power capping system 136 sets the new Tx power limit (MTPL). The Tx power capping system 136 enforces the selected Tx power cap by adjusting the MTPL for the device. This new limit is applied for a specified operational time window, during which the UE device 102 operates at the capped power level. The Tx power capping system 136 continuously monitors uplink performance and device thermals during this period to ensure that the new power level successfully reduces RF power consumption and mitigates thermal buildup without causing significant performance degradation.

[0087] At block 514, the Tx power capping system 136 monitors the impact of the adjusted Tx power level. Throughout the operational period, the Tx power capping system 136 collects performance metrics, such as uplink throughput, duty cycle, thermal state, a combination thereof, and the like. This data allows the Tx power capping system 136 to verify the effectiveness of the applied Tx power cap. If the metrics indicate that the power cap is reducing RF power consumption and device temperature without negatively affecting uplink performance, the Tx power capping system 136 maintains the new Tx power level. Otherwise, the Tx power capping system 136 re-evaluates the situation to identify necessary adjustments.

[0088] At block 516, the Tx power capping system 136 determines whether to continue or terminate the thermal mitigation process. Using updated performance and thermal metrics, the Tx power capping system 136 assesses whether conditions, such as Vskin temperature and RF power consumption, remain within acceptable thresholds. At block 518, if the metrics indicate that thresholds are no longer exceeded, the Tx power capping system 136 concludes the thermal mitigation process and restores Tx power to its default level. If thresholds are still exceeded, the Tx power capping system 136 loops back to block 502 to repeat the evaluation process with updated inputs, ensuring continuous and adaptive thermal management.

[0089] The method exits when normal operation resumes, or thresholds for further mitigation are no longer met. By leveraging dynamic device-network interactions, the Tx power capping system 136 ensures that the device efficiently manages thermal performance without unnecessary disruptions to network functionality or user experience. This comprehensive and adaptive approach optimizes power consumption while preserving seamless communication and application performance.

[0090] In some embodiments, certain aspects of the techniques described above may be implemented by one or more processors of a processing system executing software. The software comprises one or more sets of executable instructions stored or otherwise tangibly embodied on a non-transitory computer-readable storage medium. The software can include the instructions and certain data that, when executed by the one or more processors, manipulate the one or more processors to perform one or more aspects of the techniques described above. The non-transitory computer-readable storage medium can include, for example, a magnetic or optical disk storage device, solid-state storage devices such as Flash memory, a cache, random access memory (RAM) or other non-volatile memory device or devices, and the like. The executable instructions stored on the non-transitory computer-readable storage medium may be in source code, assembly language code, object code, or other instruction format that is interpreted or otherwise executable by one or more processors.

[0091] A computer-readable storage medium may include any storage medium, or combination of storage media, accessible by a computer system during use to provide instructions and / or data to the computer system. Such storage media can include, but is not limited to, optical media (e.g., compact disc (CD), digital versatile disc (DVD), Blu-Ray disc), magnetic media (e.g., floppy disc, magnetic tape, or magnetic hard drive), volatile memory (e.g., random access memory (RAM) or cache), non-volatile memory (e.g., read-only memory (ROM) or Flash memory), or microelectromechanical systems (MEMS)-based storage media. The computer- readable storage medium may be embedded in the computing system (e.g., system RAM or ROM), fixedly attached to the computing system (e.g., a magnetic hard drive), removably attached to the computing system (e.g., an optical disc or Universal Serial Bus (USB)-based Flash memory), or coupled to the computer system via a wired or wireless network (e.g., network accessible storage (NAS)).

[0092] Note that not all of the activities or elements described above in the general description are required, that a portion of a specific activity or device may not be required, and that one or more further activities may be performed, or elements included, in addition to those described. Still further, the order in which activities are listed are not necessarily the order in which they are performed. Also, the concepts have been described with reference to specific embodiments. However, one of ordinary skills in the art appreciates that various modifications and changes can be made without departing from the scope of the present disclosure as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of the present disclosure.

[0093] Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any feature(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature of any or all the claims. Moreover, the particular embodiments disclosed above are illustrative only, as the disclosed subject matter may be modified and practiced in different but equivalent manners apparent to thoseskilled in the art having the benefit of the teachings herein. No limitations are intended to the details of construction or design herein shown, other than as described in the claims below. It is therefore evident that the particular embodiments disclosed above may be altered or modified and all such variations are considered within the scope of the disclosed subject matter. Accordingly, the protection sought herein is as set forth in the claims below.

Claims

WHAT IS CLAIMED IS:1 . A method at a user equipment (UE) device (102) of a cellular network (100), comprising: obtaining a set of projected transmission powers for the UE device; obtaining a projected duty cycle and radio frequency (RF) power savings for each projected transmission power of the set of projected transmission powers based on a set of uplink performance metrics estimated for a cellular channel; selecting a projected transmission power from the set of projected Transmission powers having a highest projected RF power savings within a first threshold tolerance level and a projected RF power savings exceeding a second threshold tolerance level; and capping a transmission power of the UE device at the projected transmission power to reduce RF power consumption.

2. The method of claim 1 , wherein capping the transmission power of the UE device includes limiting a thermal output of the UE device.

3. The method of any of the preceding claims, wherein the set of uplink performance metrics comprise at least one of: a transmission power, a duty cycle, a modulation and coding scheme, physical resource blocks, uplink throughput, or uplink block error rate associated with the cellular channel.

4. The method of any of the preceding claims, further comprising: periodically monitoring, during a configurable time interval, the set of uplink performance metrics; and updating the set of projected transmission powers to reflect current devicenetwork dynamics based on the monitored set of uplink performance metrics.

5. The method of claim 4, wherein periodically monitoring further comprises: periodically monitoring, one or more thermal conditions of the UE device, and wherein the updating of the set of projected transmission powers comprises updating the set of the set of projected transmission powers based on the monitored set of uplink performance metrics and the monitored one or more thermal conditions.

6. The method of the preceding claims, further comprising: responsive to a determination that at least one thermal initiation threshold is exceeded based on a measured device surface temperature and RF power consumption, triggering the capping of the transmission power.

7. The method of the preceding claims 1 , wherein obtaining the projected duty cycle comprises: calculating the projected duty cycle for each projected transmission power based on one or more transport block size look-up tables.

8. The method of claim 1 , wherein obtaining the projected duty cycle and RF power savings for each projected transmission power comprises: determining a projected duty cycle and projected RF power savings based on one or more uplink performance metrics; and selecting a projected transmission power that both satisfies an acceptable throughput degradation tolerance and meets a predefined RF power savings tolerance.

9. The method of claim 8, wherein determining the projected duty cycle comprises: adjusting at least one uplink scheduling parameter selected from at least one of a modulation and coding scheme, a physical resource block, allocation, or block error rate to predict an impact of the capped transmission power.

10. The method of claim 8, wherein determining the projected RF power savings comprises:mapping, for each projected transmission power of the set of projected transmission powers, a current transmission power and the projected transmission power to respective RF power consumption values using a device-specific look-up table; and calculating a percentage reduction in RF power consumption based on the mapping.11 . The method of any of the preceding claims, wherein capping of the transmission power of the UE device comprises: adjusting a maximum transmit power limit of the UE device for a predetermined operational time window.

12. The method of any of the preceding claims, further comprising: responsive to capping the transmission power of the UE device, monitoring the set of uplink performance metrics for a first portion of a monitoring interval; operating the selected projected transmission power for a remaining second portion of the monitoring interval; and responsive to the monitoring interval expiring, reassessing the selected projected transmission power.

13. The method of any of the preceding claims, further comprising: responsive to a device surface temperature and an RF power consumption of the UE device satisfying one or more thresholds, restoring the UE device to a default transmit power level.

14. A user equipment device (102), comprising: one or more radio frequency (RF) modems (210) configured to wirelessly communicate with at least one network (100); one or more processors (216) coupled to the one or more RF modems; and at least one memory (222) storing executable instructions, the executable instructions configured to manipulate at least one of the one or moreprocessors or the one or more RF modems to perform the method of any of the preceding claims.

15. A computer program product comprising a set of executable instructions, the set of executable instructions to manipulate a user equipment device (104) to perform the method of any of claims 1 to 13.

Images