Patent Description:
In a telecommunication network, a user equipment (UE) can wirelessly connect to a base station in order to engage in voice calls, video calls, data transfers, or other types of communications. For example, a mobile device, such as a smart phone, can wirelessly connect to a gNB or other base station of a radio access network (RAN) to access the telecommunication network.

UEs can operate according to different power classes that are associated with different output power levels for transmissions. For example, 3GPP defines various power classes, including Power Class <NUM>, Power Class <NUM>, and Power Class <NUM>, that define maximum output power levels for uplink transmissions. Accordingly, a UE may transmit uplink data to a base station of the RAN according to a particular power class. WO2019158461A1 relates to a wireless device indicating multiple power classes to a network node, a network node using the indicated multiple power classes, and related methods of operation for the wireless device and the network node. The wireless device aims at an increase flexibility in setting different power classes in different communication scenarios while minimizing signalling overhead for capability signalling for the wireless device. This is achieved by using at least one set of power classes defining at least two power classes of the wireless device. Each set of power classes applies to a transmission band supported by the wireless device and each power class in each set of power classes applies to a specific operative condition of the wireless device.

Accordingly, there is provided a method, a non-transitory computer-readable medium, and a base station as detailed in the appended set of claims.

A UE can support multiple power classes. A power class can define a maximum output power, such as a maximum output power for uplink transmissions from the UE to a RAN. For example, 3GPP Power Class <NUM> allows uplink transmissions at up to an output power of <NUM> decibels relative to one milliwatt (dBm). 3GPP Power Class <NUM> allows uplink transmissions at up to an output power of <NUM> dBm. 3GPP Power Class <NUM> allows uplink transmissions at up to an output power of <NUM> dBm.

In some situations, transmitting at higher output power levels can have benefits relative to transmitting at lower output power levels. For instance, if a UE uses Power Class <NUM> to transmit uplink signals at up to <NUM> dBm, the uplink signals may propagate farther and/or through more barriers than uplink signals transmitted at up to <NUM> dBm according to Power Class <NUM>. In some examples, using Power Class <NUM> may also result in higher uplink data transmission rates than could be achieved using Power Class <NUM>.

However, in some situations, transmitting at higher output power levels can also have drawbacks relative to transmitting at lower output power levels. For instance, transmitting at higher output power levels can cause a UE to consume more power than transmitting at lower output power levels, and thereby cause the UE to drain its battery more quickly and/or cause the UE to generate more heat. Accordingly, in some situations, a UE that uses Power Class <NUM> may need to be recharged more often, and/or may have a higher risk of overheating, than a UE that uses Power Class <NUM>.

In some systems, if a UE supports multiple power classes, the UE may be configured to select one of those power classes according to a maximum output power allowed by the RAN. For example, if a base station of the RAN indicates that the highest allowed output power for uplink transmissions in a cell is <NUM> dBm, and the UE supports Power Class <NUM>, the UE may use Power Class <NUM> to perform all uplink transmissions at output power levels of up to <NUM> dBm to while the UE is connected to that base station.

However, such systems in which a UE statically selects a single power class, based on a maximum output power allowed by the RAN, can cause the UE to consume more power than may be necessary in situations in which benefits of the increased power consumption may not be apparent to the UE or to a user of the UE. For instance, using a higher uplink output power in situations in which a lower output power would suffice may drain the UE's battery more quickly, cause the UE to generate more heat and potentially risk overheating or damaging the battery, and/or otherwise negatively impact the UE. Accordingly, there may be drawbacks to statically using the highest allowable output power that is permitted by the RAN.

As an example, as noted above, a UE may statically select Power Class <NUM> because a base station indicates that uplink transmissions are permitted in a cell at output power levels of up to <NUM> dBm. However, if the UE is located at a position in the cell that is relatively close to the base station, the UE is unlikely to benefit from a larger signal propagation range that Power Class <NUM> may provide over Power Class <NUM>. Based on the position of the UE, the smaller signal propagation range associated with Power Class <NUM> may be sufficient for uplink signals sent by the UE to reach the base station. Accordingly, in this situation, the UE statically using Power Class <NUM> instead of Power Class <NUM> may not provide appreciable advantages to the UE, or to a user of the UE. However, the UE statically using Power Class <NUM> instead of Power Class <NUM> may lead to appreciable disadvantages caused by higher power consumption rates, such as decreased battery life and/or increased heat generation.

The systems and methods described herein can allow a base station, or other element of the RAN, to dynamically change the power class used by a UE, based on metrics reported by the UE and/or other data. For example, if the base station determines that the UE may benefit from transmitting at higher output power levels, the base station may instruct the UE to use Power Class <NUM>. However, if the base station later determines that the UE would benefit from transmitting at lower output power levels, for instance to save battery life and/or to generate less heat, the base station may instruct the UE to switch to using Power Class <NUM> instead of Power Class <NUM>.

<FIG> shows an example network environment <NUM> in which a UE <NUM> can connect to a telecommunication network to engage in communication sessions for voice calls, video calls, messaging, data transfers, and/or any other type of communication. The telecommunication network can include at least one radio access network (RAN) <NUM>. The UE <NUM> can wirelessly connect to a base station or other access point of the RAN <NUM>. The telecommunication network can also include at least one core network <NUM> linked to the RAN <NUM>, such that the UE <NUM> can access the core network <NUM> via a connection to the RAN <NUM>.

The UE <NUM>, the RAN <NUM>, and/or the core network <NUM> can be compatible with one or more types of radio access technologies, wireless access technologies, protocols, and/or standards. For example, the UE <NUM>, the RAN <NUM>, and/or the core network <NUM> can be compatible with fifth generation (<NUM>) New Radio (NR) technology, Long-Term Evolution (LTE) / LTE Advanced technology, other fourth generation (<NUM>) technology, High-Speed Data Packet Access (HSDPA)/Evolved High-Speed Packet Access (HSPA+) technology, Universal Mobile Telecommunications System (UMTS) technology, Code Division Multiple Access (CDMA) technology, Global System for Mobile Communications (GSM) technology, WiMax® technology, WiFi® technology, and/or any other previous or future generation of radio access technology or wireless access technology.

In some examples, the RAN <NUM> and/or the core network <NUM> may be based on LTE technology. For instance, the RAN <NUM> may be an LTE access network known as an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN), and can include one or more LTE base stations known as evolved Node Bs (eNBs). The core network <NUM> may also be an LTE packet core network, known as an Evolved Packet Core (EPC). In other examples, the RAN <NUM> and/or the core network <NUM> may be based on <NUM> technology. For example, the RAN <NUM> may be a <NUM> access network that includes one or more <NUM> base stations knowns as gNBs, and the core network <NUM> may be a <NUM> core network.

In some examples, the RAN <NUM> and the core network <NUM> may be based on the same radio access technology. However, in other examples, the RAN <NUM> and the core network <NUM> may be based on different radio access technologies. For instance, in some examples a <NUM> access network may be linked to an LTE core network, or an LTE access network may be linked to a <NUM> core network.

The UE <NUM> can be any device that can wirelessly connect to the telecommunication network. In some examples, the UE <NUM> can be a mobile phone, such as a smart phone or other cellular phone. In other examples, the UE <NUM> can be a personal digital assistant (PDA), a media player, a tablet computer, a gaming device, a smart watch, a hotspot, a personal computer (PC) such as a laptop, desktop, or workstation, or any other type of computing or communication device.

As shown in <FIG>, the UE <NUM> can have a battery <NUM>, a temperature sensor <NUM>, and one or more transmission interfaces <NUM>. The UE <NUM> can also support multiple power classes <NUM>, and at any point in time can operate according to a power class selected from the multiple power classes <NUM> supported by the UE <NUM>. As will be discussed further below, a base station such as a gNB or eNB, or another element of the RAN <NUM>, can include a power class switcher <NUM> that is configured to dynamically determine which one of the power classes <NUM> the UE <NUM> should use. Based on a power class determination by the power class switcher <NUM>, the RAN <NUM> can transmit a power class change indicator <NUM> to the UE <NUM>. The power class change indicator <NUM> may identify a specific power class the UE <NUM> should use, or instruct the UE <NUM> to change from using a current power class to using a different power class. The power class change indicator <NUM> provided by the RAN <NUM> can accordingly cause the UE <NUM> to dynamically change a power class associated with the transmission interfaces <NUM>, for instance by changing a maximum output power for uplink transmissions. Other elements of the UE <NUM> are illustrated in greater detail in <FIG>, and are described in detail below with reference to that figure.

The battery <NUM> can store energy used to power functions of the UE <NUM>. The battery <NUM> can be a lithium-ion (Li-ion) battery, a lithium-ion polymer (LiPo) battery, a nickel cadmium (NiCd) battery, a nickel-metal hydride (NiMH) battery, or other type of battery. The battery <NUM> may be rechargeable. For instance, the battery <NUM> can charge when the UE <NUM> is connected to a wall outlet, a portable charger, or another external power source. However, operations of the UE <NUM> can also use energy and thus drain the battery <NUM>, for instance when the battery <NUM> is not charging.

In some examples, the UE <NUM> may include the temperature sensor <NUM>. The temperature sensor <NUM> may be a thermocouple, thermistor, resistance temperature detector (RTD), semiconductor-based integrated circuit, thermometer, and/or any other type of temperature sensor. The temperature sensor <NUM> may be configured to measure or derive the internal temperature of the UE <NUM> or temperatures of one or more individual components of the UE <NUM>, such as a temperature of the battery <NUM>, a temperature of a central processing unit (CPU) or other processor, or a temperature of any other component of the UE <NUM>. In some examples, the UE <NUM> may have multiple temperature sensors, such as a CPU temperature sensor and a battery temperature sensor. In other examples, the UE <NUM> may lack a dedicated temperature sensor, but heat generated by the UE <NUM> may be estimated based on how quickly the battery <NUM> drains and/or other UE power consumption metrics.

The transmission interfaces <NUM> of the UE <NUM> can be configured to establish wireless connections with the RAN <NUM>, and to perform uplink and/or downlink data transmissions via the wireless connections. For examples, the transmission interfaces <NUM> can include radio interfaces, transceivers, modems, interfaces, antennas, and/or other components that perform or assist in exchanging radio frequency (RF) communications with one or more base stations of the RAN <NUM>. The transmission interfaces <NUM> may be compatible with one or more radio access technologies, such as <NUM> NR radio access technologies and/or LTE radio access technologies.

In some examples, the transmission interfaces <NUM> can establish a single connection with a base station of the RAN <NUM> for uplink transmissions and/or downlink transmissions. In other examples, the transmission interfaces <NUM> can establish multiple connections with one or more base stations of the RAN <NUM> for uplink transmissions and/or downlink transmissions. For example, the transmission interfaces <NUM> may have multiple antennas, such that the UE <NUM> may use multiple-input multiple-output (MIMO) techniques to exchange different data streams with a base station via different antennas.

The UE <NUM> may be configured to operate according to any of two or more power classes <NUM>. A power class may indicate allowable power levels and/or other power configurations for transmissions via the transmission interfaces <NUM>, such as a maximum output power for uplink transmissions.

As an example, the UE <NUM> may be configured to operate according to two or more of 3GPP Power Class <NUM>, 3GPP Power Class <NUM>, or 3GPP Power Class <NUM>. Power Class <NUM> can permit uplink transmissions at up to <NUM> dBm. Power Class <NUM> can permit uplink transmissions at up to <NUM> dBm. Power Class <NUM> can permit uplink transmissions at up to <NUM> dBm. Because a decibel is a logarithmic value, a <NUM> dBm increase in output power can be equivalent to doubling the output power. Accordingly, using Power Class <NUM> may allow the UE <NUM> to double its uplink output power relative to using Power Class <NUM>. Similarly, using Power Class <NUM> may allow the UE <NUM> to double its uplink output power relative to using Power Class <NUM>. In some examples, the UE <NUM> can be considered a High-Power or High-Performance UE (HPUE) if the UE <NUM> is configured to use Power Class <NUM> and/or Power Class <NUM>.

Power Class <NUM> can allow MIMO dual transmission paths at <NUM> dBm each, for a total uplink transmission power of <NUM> dBm. Alternatively, Power Class <NUM> may allow a single uplink transmission path at up to <NUM> dBm. In some examples, Power Class <NUM> may allow <NUM>% duty cycle for uplink activity when uplink transmission power is at the maximum of <NUM> dBm. This can allow the UE <NUM> to stay below a Specific Absorption Rate (SAR) limit. If the UE <NUM> approaches or exceeds the SAR limit, the UE <NUM> can use additional maximum power reduction (AMPR) techniques to lower output power.

Power Class <NUM> can allow MIMO dual transmission paths at <NUM> dBm each, for a total uplink transmission power of <NUM> dBm. Alternatively, Power Class <NUM> may allow a single uplink transmission path at up to <NUM> dBm. In some examples, Power Class <NUM> may allow <NUM>% duty cycle for uplink activity when uplink transmission power is at the maximum of <NUM> dBm, which may allow the UE <NUM> stay below a SAR limit.

Some power classes <NUM> may be associated with specific duplexing modes and/or specific frequency bands. For instance, Power Class <NUM> may be defined for use with LTE frequency bands that are associated with frequency division duplexing (FDD) or time division duplexing (TDD). However, Power Class <NUM> and Power Class <NUM> may not be defined for use with FDD frequency bands, and may instead be defined for use with TDD frequency bands. For example, Power Class <NUM> may be defined for use with <NUM> TDD frequency bands such as n40, n41, n77, n78, and n79.

The power class used by the UE <NUM> can affect signal quality, connection reliability, signal propagation range, transmission rates, and/or other transmission metrics. For example, transmitting at higher output power levels can allow signals to propagate farther, and/or more easily pass through walls or other barriers, relative to transmitting at lower output power levels. In some situations, transmitting at higher output power levels may also result in higher uplink data transmission rates than could be achieved by transmitting at higher output power levels. Such benefits of transmitting at higher output power levels instead of lower output power levels may be appreciated by a user of the UE <NUM>, and thus offer an improved user experience, as the user may perceive that the UE <NUM> is able to connect to the telecommunication network more reliably and/or with higher data speeds.

However, the power class used by the UE <NUM> may also affect the power consumption of the UE <NUM>. The power consumption of the UE <NUM> may in turn affect how quickly the battery <NUM> drains, and/or affect the temperature of the UE <NUM>. For example, as noted above, Power Class <NUM> may use twice the uplink output power relative to Power Class <NUM>. Accordingly, if the UE <NUM> uses Power Class <NUM>, the battery <NUM> may drain more quickly than if the UE <NUM> had used Power Class <NUM>. Similarly, the temperature sensor <NUM> may indicate that the UE <NUM> generates more heat when the UE <NUM> uses Power Class <NUM> relative to when the UE <NUM> uses Power Class <NUM>. The UE <NUM> may thus operate at higher temperatures when using Power Class <NUM> instead of Power Class <NUM>, which may degrade overall performance of the UE <NUM> and/or put the UE <NUM> at a higher risk of overheating. Such drawbacks of transmitting at higher output power levels may be appreciated by a user of the UE <NUM>, and thus offer a degraded user experience, as the user may perceive that the battery <NUM> of the UE <NUM> does not last as long between charges or that performance of the UE <NUM> suffers overall at higher heat levels.

As such, a power class that allows a higher output power than another power class may have advantages and disadvantages. For instance, Power Class <NUM> may result in advantages relative to Power Class <NUM>, such as a larger signal coverage area and/or higher uplink data transmission speeds. However, Power Class <NUM> may also have disadvantages relative to Power Class <NUM>, such as increased power consumption or increased heat levels at the UE <NUM>.

In some situations, the advantages of a power class that allows a higher output power than another power class may outweigh the corresponding disadvantages. However, in other situations, the disadvantages of that power class may outweigh its advantages. For instance, if the UE <NUM> is located at a position that is relatively close to a gNB of the RAN <NUM>, Power Class <NUM> may provide a sufficient signal propagation range for uplink transmissions to reach the gNB. In this situation, the UE <NUM> may not benefit from an increased signal propagation range that Power Class <NUM> may provide over Power Class <NUM>. The UE <NUM> may also drain the battery <NUM> more quickly, and/or generate more heat, due to the use of Power Class <NUM> instead of Power Class <NUM>, without any appreciable user experience benefit or other benefit to the UE <NUM>.

Accordingly, the power class switcher <NUM> of the RAN <NUM> can be configured to dynamically determine which power class the UE <NUM> should use, and to provide a corresponding power class change indicator <NUM> to the UE <NUM>. The power class change indicator <NUM> may instruct the UE <NUM> to use a specific power class, or instruct the UE <NUM> to switch from a current power class to a different power class.

The power class switcher <NUM> can store data indicating which set of power classes <NUM> the UE <NUM> supports. The power class switcher <NUM> may use UE capability data <NUM> provided by the UE <NUM> during an initial network registration process, and/or at other times, to determine which power classes <NUM> the UE <NUM> supports. The UE capability data <NUM> can be a Radio Resource Control (RRC) message, or other type of message, that indicates capabilities of the UE <NUM>, including an indication of the power classes <NUM> that the UE <NUM> supports. For example, when the UE <NUM> registers with a gNB, the UE <NUM> can provide UE capability data <NUM> to the gNB indicating that the UE <NUM> supports both Power Class <NUM> and Power Class <NUM>.

In some examples, the UE <NUM> may be configured to, by default, initially select a power class based on an output power limit that is broadcast by a base station of the RAN <NUM> to all UEs in range of that base station. For example, a gNB may broadcast a System Information Block #<NUM> (SIB1), which may be received by any UE in range of the gNB. The broadcast SIB1 may indicate a maximum allowable output power for uplink transmissions in the cell. The UE <NUM> can, by default, select one of its supported power levels that corresponds to the maximum allowable output power.

For example, a SIB1 broadcast by a gNB may indicate that the gNB permits uplink transmissions to be sent by UEs at output powers up to <NUM> dBm (corresponding to Power Class <NUM>). In this example, if the UE <NUM> supports both Power Class <NUM> and Power Class <NUM>, the UE <NUM> may initially set itself to use Power Class <NUM> because Power Class <NUM> also allows uplink transmissions at up to <NUM> dBm.

A base station or other element of the RAN <NUM> may infer the power class used by the UE <NUM> upon initial network registration based on the output power limit broadcast by the RAN <NUM> and based on the UE capability data <NUM> provided by the UE <NUM> to the RAN <NUM>. For example, if a base station is configured to broadcast a SIB <NUM> indicating a <NUM> dBm output power limit, and the UE <NUM> provides UE capability data <NUM> during network registration with the base station that indicates that the UE <NUM> supports both Power Class <NUM> and Power Class <NUM>, the base station can determine that the UE <NUM> will initially use Power Class <NUM> according to the SIB1 broadcast by the RAN <NUM>. The base station may store information tracking which power class the UE <NUM> is currently using, and may initialize this tracking information based on the initial power class inferred by the base station based on the output power limit broadcast by the base station and the UE capability data <NUM>.

After the UE <NUM> registers with a base station of the RAN <NUM>, the UE <NUM> can periodically or occasionally send a UE report <NUM> to the base station, or other element of the RAN <NUM>. The UE report <NUM> can be an RRC message, or other type of message, that indicates metrics and/or other information associated with the UE <NUM>, as discussed further below with respect to <FIG>. In some examples, the UE report <NUM> can be an RRC message that includes UE Assistance Information.

The power class switcher <NUM> of the RAN <NUM> can evaluate one or more types of information in the UE report <NUM>, and/or other information associated with other connected UEs or the cell overall, and determine whether the UE <NUM> should change from its current power class to a different power class. If the power class switcher <NUM> does determine that the UE <NUM> should change to a different power class, the power class switcher <NUM> can cause the base station, or other RAN element, to send the power class change indicator <NUM> to the UE <NUM>. The RAN <NUM> may also update information that tracks which power class the UE <NUM> is using, based on the power class change indicator <NUM> sent to the UE <NUM>.

In some examples, the power class change indicator <NUM> can be sent by the RAN <NUM> to the UE <NUM> as an RRC reconfiguration message, or other type of message. For example, a gNB can send the UE <NUM> an RRC reconfiguration message that contains an instruction to use a specific power class, or that contains an instruction to switch from a current power class to a different power class.

As a non-limiting example, the UE <NUM> may have reported to a gNB in UE capability data <NUM> that the UE <NUM> supports both Power Class <NUM> and Power Class <NUM>. The UE <NUM> may have initially started using Power Class <NUM> based on a SIB1 broadcast by a gNB. However, the gNB may determine, based on a UE report <NUM> and/or other data, that the UE should change from using Power Class <NUM> to using Power Class <NUM>. The gNB may accordingly send an RRC reconfiguration message that instructs the UE <NUM> to switch from its current power class to a different power class. Accordingly, the UE <NUM> may follow the instruction in the RRC reconfiguration message, and dynamically switch from using Power Class <NUM> to using Power Class <NUM>. In this example, the RRC reconfiguration message may not directly indicate that the UE <NUM> should use Power Class <NUM>, but instead instruct the UE <NUM> to change between the two power classes it supports. Because the UE <NUM> was using Power Class <NUM>, the RRC reconfiguration message may implicitly instruct the UE <NUM> to dynamically change to using Power Class <NUM>. However, in other examples, the RRC reconfiguration message may directly indicate that the UE <NUM> should use a specific power class, such as Power Class <NUM>.

In other examples, the power class change indicator <NUM> can be sent by the RAN <NUM> to the UE <NUM> as information that can be interpreted by the UE <NUM> at the physical layer. Accordingly, the UE <NUM> may be able to interpret the power class change indicator <NUM> at the physical layer, and/or initiate a corresponding change in the power class of the UE <NUM>, more quickly than if the power class change indicator <NUM> were sent as an RRC reconfiguration message or other message that the UE <NUM> interprets at an RRC layer or other protocol layer above the physical layer.

For example, the power class change indicator <NUM> can be included by a base station, or other RAN element, in a radio frame <NUM>, as shown in <FIG>. Accordingly, in some examples the UE <NUM> may locate, interpret, and/or follow the power class change indicator <NUM> at the physical layer, without passing the power class change indicator <NUM> to an RRC layer or other higher protocol layer for interpretation.

The radio frame <NUM> can include a series of subframes <NUM>. For example, the radio frame <NUM> can include ten subframes <NUM>. An individual subframe may include data in a Physical Downlink Control Channel (PDCCH) <NUM>. An individual subframe may also include other types of data, such as data in a Physical Downlink Shared Channel (PDSCH) <NUM> or a Physical Uplink Shared Channel (PUSCH), depending on the type of subframe.

The PDCCH <NUM> may carry downlink control information (DCI). The DCI can indicate PDSCH transmission resource scheduling, PUSCH transmission resource scheduling, slot format information, and/or other types of information. For instance, if the PDCCH <NUM> includes a UE identifier <NUM> of the UE <NUM>, the UE <NUM> can use DCI to determine how to locate and interpret downlink data for the UE <NUM> that is encoded in the PDSCH <NUM>, how to encode and send uplink data in PUSCH of a subframe, or otherwise how to interpret the structure of the radio frame <NUM>. In some examples, the UE identifier <NUM> may be a cell-radio network temporary identifier (C-RNTI) that is assigned to the UE <NUM> by a base station of the RAN <NUM> when the UE <NUM> initially connects to the base station.

As shown in <FIG>, the base station can also include the power class change indicator <NUM> in the PDCCH <NUM>, in association with the UE identifier <NUM> of the UE <NUM>. The PDCCH <NUM> may include different UE identifiers, and different corresponding power class change indicators, for different UEs that have registered with the base station. Accordingly, if the UE <NUM> receives the radio frame <NUM> and determines at the physical layer that the UE identifier <NUM> of the UE <NUM> is present in the PDCCH <NUM>, the UE <NUM> can identify and follow the corresponding power class change indicator <NUM> associated with the UE identifier <NUM> in the PDCCH <NUM>.

In some examples, the power class change indicator <NUM> in the PDCCH <NUM> may be expressed using a single bit. In these examples, one binary value for the bit may indicate that the UE <NUM> should continue using its current power class, while the other binary value for the bit may indicate that the UE <NUM> should change to another power class.

As a non-limiting example, the UE <NUM> may support both Power Class <NUM> and Power Class <NUM>. If the UE <NUM> is currently using Power Class <NUM>, a value of "<NUM>" for the power class change indicator <NUM> in the PDCCH <NUM> may indicate that the UE should continue using Power Class <NUM>. However, a value of "<NUM>" for the power class change indicator <NUM> in the PDCCH <NUM> may indicate that the UE <NUM> should switch to using Power Class <NUM>. The meanings of these binary values can be reversed in some examples, such that a value of "<NUM>" instead indicates that the UE <NUM> should switch to a different power class, and a value of "<NUM>" indicates that the UE <NUM> should continue using its current power class.

In other examples, the power class change indicator <NUM> in the PDCCH <NUM> may be expressed using multiple bits. Different possible combinations of values for the multiple bits of the power class change indicator <NUM> in the PDCCH <NUM> may map to corresponding instructions regarding the power class of the UE <NUM>, or map to specific corresponding power classes. For example, a value of "<NUM>" may indicate that the UE <NUM> should use Power Class <NUM>, a value of "<NUM>" may indicate that the UE <NUM> should use Power Class <NUM>, and a value of "<NUM>" may indicate that the UE <NUM> should use Power Class <NUM>.

<FIG> show an example <NUM> of metrics and other data that can be included in the UE report <NUM> sent by the UE <NUM> to the RAN <NUM>. The UE report <NUM> can include one or more of power data <NUM>, temperature data <NUM>, radio condition data <NUM>, uplink transmission data <NUM>, or other types of information. As discussed above, the power class switcher <NUM> can determine, based on information in the UE report <NUM> and/or other data, whether the UE <NUM> should change from its current power class to a different power class. If the power class switcher <NUM> does determine that the UE <NUM> should change to a different power class, the power class switcher <NUM> can cause the RAN <NUM> to send the power class change indicator <NUM> to the UE <NUM>.

Power data <NUM> can include information about the power consumption of the UE <NUM>. For example, the power data <NUM> may indicate rates at which the UE <NUM> has consumed power over one or more periods of time. Such power consumption rates may indicate how quickly the UE <NUM> is draining the battery <NUM>. The power data <NUM> may also indicate current power levels of the battery <NUM>, such as an indication of how much power is stored in the battery <NUM> and/or a current battery level relative to an overall battery capacity. For instance, the power data <NUM> may indicate that the battery <NUM> is currently charged to a level that is <NUM>% full. In some examples, the power data <NUM> may also indicate power headroom levels associated with the UE <NUM>, such as a measure of how much power is available for transmissions in addition to power currently being used for transmissions.

The power class switcher <NUM> may, in some situations, determine whether to dynamically change the power class used by the UE <NUM> based in part on the power data <NUM> in the UE report <NUM>. For example, the power class switcher <NUM> may be configured with one or more battery power thresholds that correspond with one or more power classes <NUM>. By way of a non-limiting example, if the power data <NUM> reported by the UE <NUM> indicates that the battery <NUM> of the UE <NUM> is charged to above a particular threshold, such as above <NUM>%, the power class switcher <NUM> may be configured to instruct the UE <NUM> to use Power Class <NUM>. However, if the power data <NUM> reported by the UE <NUM> indicates that the battery <NUM> of the UE <NUM> is charged to a level below the <NUM>% threshold, the power class switcher <NUM> may be configured to instruct the UE <NUM> to use Power Class <NUM> in order to conserve battery life of the UE <NUM>. As another non-limiting example, the power class switcher <NUM> may be configured to instruct the UE <NUM> to use Power Class <NUM> if the charge level of the battery <NUM> is above a first threshold, instruct the UE <NUM> to use Power Class <NUM> if the charge level of the battery <NUM> is below a second threshold, and use one or more other factors to select between Power Class <NUM> and Power Class <NUM> if the charge level of the battery <NUM> is between the first threshold and the second threshold.

Temperature data <NUM> can, in some examples, include temperature data based on measurements taken by the temperature sensor <NUM>, such as temperatures measurements associated with the battery <NUM>, a CPU, and/or other components of the UE <NUM>, and/or rates indicating how measured temperatures or amounts of heat generated by the UE <NUM> have been increasing or decreasing over time. In other examples, the temperature data <NUM> in the UE report <NUM> can be inferred or estimated based on power consumption rates rather than temperature measurements associated with the temperature sensor <NUM>. In still other examples, the UE report <NUM> can omit temperature data <NUM>, but the RAN <NUM> can infer temperatures and/or heat generation metrics associated with the UE <NUM> based on power consumption rates or other power data <NUM> provided in the UE report <NUM>.

The power class switcher <NUM> may, in some situations, determine whether to dynamically change the power class used by the UE <NUM> based in part on the temperature data <NUM> included in the UE report <NUM> or determined by the RAN <NUM> based on power data <NUM> in the UE report <NUM>. For example, if the UE <NUM> is using Power Class <NUM>, and the temperature data <NUM> indicates that the UE <NUM> is operating at a temperature above a temperature threshold, the power class switcher <NUM> may instruct the UE <NUM> to switch to using Power Class <NUM> in order to decrease the power consumption of the UE <NUM> and thereby lower the operating temperature of the UE <NUM>.

Radio condition data <NUM> can include metrics or other key performance indicators (KPIs) associated with radio conditions associated with the UE <NUM>. For example, the UE <NUM> may include, in the UE report <NUM>, signal-to-interference-plus-noise (SINR) metrics, signal-to-noise (SNR) metrics, received signal strength indicator (RSSI) values, reference signal received power (RSRP) values, reference signal received quality (RSRQ) values, and/or other signal quality or signal strength metrics measured by the UE <NUM>. In some examples, one or more elements of the RAN <NUM> may separately measure or determine signal strength or signal quality metrics associated with transmissions between the RAN <NUM> and the UE <NUM>.

In some examples, the radio condition data <NUM> may indicate a location of the UE <NUM> relative to a base station of the RAN <NUM>. For example, the base station may determine that the UE <NUM> is at a near-cell position relatively close to the base station if signal strength metrics are relatively strong, that the UE <NUM> is at a far-cell position relatively far away from the base station if signal strength metrics are relatively weak, or that the UE <NUM> is at a mid-cell position if signal strength metrics are in an intermediate range. In some examples, base station or other RAN element can also, or alternately, determine an estimated location of the UE <NUM> based on Global Positioning System (GPS) coordinates included in the UE report <NUM>, based on triangulation methods, and/or any other location determination method.

In some examples, the radio condition data <NUM> may indicate whether the UE <NUM> is indoors or outdoors. For example, relatively poor signal strength metrics may indicate that the UE <NUM> is inside a building, and walls of the building are interfering with signal propagation.

The power class switcher <NUM> may, in some situations, determine whether to dynamically change the power class used by the UE <NUM> based in part on the radio condition data <NUM> included in the UE report <NUM> and/or determined by the RAN <NUM>. As an example, if the UE <NUM> is currently using Power Class <NUM>, and relatively strong signal strength and/or signal quality metrics in the radio condition data <NUM> indicate that the UE <NUM> is likely outside and/or at a mid-cell or near-cell position, the power class switcher <NUM> may determine that Power Class <NUM> would be sufficient for uplink signals from the UE <NUM> to reach a base station. Accordingly, in order to preserve battery life of the UE <NUM> and/or decrease the amount of heat produced by the UE <NUM>, the power class switcher <NUM> may transmit the power class change indicator <NUM> with a value that instructs the UE <NUM> to dynamically change from using Power Class <NUM> to using Power Class <NUM>.

As another example, if the UE <NUM> is currently using Power Class <NUM>, and relatively poor signal strength and/or signal quality metrics in the radio condition data <NUM> indicate that the UE <NUM> is likely inside and/or at a far-cell position, the power class switcher <NUM> may determine the UE <NUM> should continue using Power Class <NUM> to maintain current chances of uplink signals reaching the base station. In this situation, the power class switcher <NUM> may avoid transmitting the power class change indicator <NUM> to the UE <NUM> such that the UE <NUM> continues to use Power Class <NUM>, or may transmit the power class change indicator <NUM> with a value that instructs the UE <NUM> to continue to use its current power class.

However, if the UE <NUM> is instead currently using Power Class <NUM>, and the radio condition data <NUM> indicates that the UE <NUM> is likely inside and/or at a far-cell position, the power class switcher <NUM> may determine that the UE <NUM> should instead use Power Class <NUM> to increase the output power for of uplink transmissions and increase the likelihood of uplink transmissions reaching the base station. Accordingly, in this situation, the power class switcher <NUM> may transmit the power class change indicator <NUM> to the UE <NUM> with a value that instructs the UE <NUM> to dynamically change from using Power Class <NUM> to using Power Class <NUM>.

Uplink transmission data <NUM> can include metrics, KPIs, or other data associated with uplink transmissions that have been performed and/or are to be performed, by the UE <NUM>. For example, uplink transmission data <NUM> may indicate buffer fullness levels associated with pending uplink transmissions. The uplink transmission data <NUM> may also indicate amounts and/or types of pending uplink data the UE <NUM> will be transmitting. For example, the uplink transmission data <NUM> may indicate that the UE <NUM> will be transmitting a large upload file, and/or relatively small heartbeat messages. In some examples, the uplink transmission data <NUM> can also indicate throughput levels measured by the UE <NUM>. A base station or other RAN element may also, or alternately, measure or derive throughput levels associated with the UE <NUM>.

The power class switcher <NUM> may, in some situations, determine whether to dynamically change the power class used by the UE <NUM> based in part on the uplink transmission data <NUM> included in the UE report <NUM> and/or determined by the RAN <NUM>. As an example, the UE <NUM> may currently be using Power Class <NUM>, and uplink buffer fullness levels reported by the UE <NUM> in UE reports may indicate that the UE's uplink buffer is continuously full despite significantly uplink resources allocated by the RAN <NUM> to the UE <NUM>. In this situation, the power class switcher <NUM> may determine that Power Class <NUM> could allow the UE <NUM> to use more output power for uplink transmissions and transmit data from its uplink buffer more quickly, thereby lowering the fullness level of the UE's uplink buffer and increasing uplink throughput from the UE <NUM> overall. Accordingly, the power class switcher <NUM> may transmit the power class change indicator <NUM> to the UE <NUM> to instruct the UE <NUM> to dynamically change from using Power Class <NUM> to using Power Class <NUM>. However, if the UE's buffer fullness level is below a buffer fullness threshold, the current uplink throughput associated with the UE may be sufficient and the power class switcher <NUM> may determine that the UE <NUM> should continue using Power Class <NUM>.

In some examples, the power class switcher <NUM> can use UE reports provided by multiple UEs connected to a base station of the RAN <NUM>, and/or other types of data, to determine overall metrics associated with a cell. For example, the power class switcher <NUM> may use SINR metrics or other interference metrics associated with a set of UEs in a cell to determine an overall interference level within the cell. The power class switcher <NUM> may be configured to determine power classes for different UEs based on UE reports provided by the different UEs, and/or based on overall cell metrics. For example, although a set of UEs may all be located at near-cell positions, and the power class switcher <NUM> may determine that Power Class <NUM> would provide sufficient signal propagation ranges for all of the near-cell UEs, the power class switcher <NUM> may determine that instructing all of the near-cell UEs to use Power Class <NUM> would increase overall interference levels in the cell. Accordingly, the power class switcher <NUM> may instruct some of the near-cell UEs to use Power Class <NUM> and other near-cell UEs to use Power Class <NUM>, as the use of different power classes by different subsets of UEs may reduce overall interference levels in the cell.

The power class switcher <NUM> may be configured to evaluate any or all of the factors described herein to dynamically determine which power class the UE <NUM> should use, and/or whether to instruct the UE <NUM> to change its power class. For example, if a SINR value reported in radio condition data <NUM> indicates that the UE <NUM> may be indoors, and a power headroom value reported in power data <NUM> indicates that the UE <NUM> has sufficient power headroom to use Power Class <NUM>, the power class switcher <NUM> may instruct the UE <NUM> to change from using Power Class <NUM> to using Power Class <NUM>.

In some examples, the power class switcher <NUM> may evaluate different types of factors against different thresholds to determine which power class the UE <NUM> should use, for instance as discussed below with respect to <FIG>. In other examples, the power class switcher <NUM> may assign different weights to different types of factors, and use a weighted combination of the factors to determine which power class the UE <NUM> should use. For instance, the power class switcher <NUM> may be configured to weight factors associated power data <NUM> and/or temperature data <NUM> more heavily than factors associated with radio condition data <NUM> and/or uplink transmission data <NUM>. Accordingly, even if the power class switcher <NUM> determines from uplink transmission data <NUM> that the UE <NUM> may benefit from increased uplink throughput if the UE <NUM> changed from using Power Class <NUM> to Power Class <NUM>, the power class switcher <NUM> may weight power data <NUM> more heavily and may determine that the UE <NUM> should continue to use Power Class <NUM> because Power Class <NUM> would increase the power consumption of the UE <NUM> and drain the battery <NUM> too quickly. In some examples, factors evaluated the power class switcher <NUM>, thresholds associated with the factors, the order in which the factors are evaluated, and/or weights assigned to the factors can be determined by a machine learning model based on historical data, as discussed below with respect to <FIG>.

Overall, the power class switcher <NUM> can evaluate data in the UE report <NUM> to dynamically determine whether the UE <NUM> should change power classes. The power class switcher <NUM> can use the power class change indicator <NUM> to dynamically instruct the UE <NUM> to use a particular power class selected by the power class switcher <NUM> from a set of power classes <NUM> noted by the UE <NUM> in the UE capability data <NUM>.

In some examples, the power class switcher <NUM> can receive new UE reports from the UE <NUM> periodically or occasionally, and can also determine whether to change the UE's power class on a periodic or occasional basis. For example, if the power class switcher <NUM> is configured to provide power class change indicators in radio frames, such that a power class change indicator is interpretably the UE <NUM> at a physical layer as discussed above with respect to <FIG>, the power class switcher <NUM> may evaluate whether to include a power class change indicator that instructs the UE <NUM> to change its power class with respect to every radio frame transmitted by a base station, every ten radio frames transmitted by the base station, every hundred radio frames transmitted by the base station, or at any other interval.

In other examples in which the power class switcher <NUM> is configured to provide power class change indicators in RRC reconfiguration messages or other higher-layer messages that the UE <NUM> may not be configured to process as quickly as physical layer information, the power class switcher <NUM> may evaluate whether to send a power class change indicator that instructs the UE <NUM> to change its power class at the same or longer intervals, such as with respect to every hundred radio frames transmitted by the base station, every two hundred radio frames transmitted by the base station, every five hundred radio frames transmitted by the base station, or at any other interval.

In some examples, the power class switcher <NUM> may evaluate whether to send a power class change indicator that instructs the UE <NUM> to change its power class at intervals selected based on data provided by the UE <NUM> in UE reports. For example, if power data <NUM> reported by the UE <NUM> indicates that the battery <NUM> is charged to above a threshold level, the power class switcher <NUM> may send power class change indicators that cause the UE <NUM> to change its power class relatively frequency. However, if the power data <NUM> indicates that the battery <NUM> has a charge level below the threshold level, the power class switcher <NUM> may send power class change indicators that cause the UE <NUM> to change its power class less frequently to assist with preserving the battery life of the UE <NUM>.

Although the power class switcher <NUM> can dynamically determine whether the UE <NUM> should change power classes as discussed above, in some examples the UE <NUM> can be configured to limit which the set of power classes the power class switcher <NUM> can select from. For example, the UE <NUM> may support Power Class <NUM> and Power Class <NUM>. However, if the battery <NUM> of the UE <NUM> has a charge level under a defined threshold when the UE <NUM> first registers with a base station, the UE <NUM> may provide UE capability data <NUM> during network registration indicating that the UE <NUM> only supports Power Class <NUM>. By suppressing information in the UE capability data <NUM> indicating that the UE <NUM> also supports Power Class <NUM>, the UE <NUM> can prevent the power class switcher <NUM> from considering Power Class <NUM> as an option for the UE <NUM>. Accordingly, in this situation the UE <NUM> may operate based on Power Class <NUM> while connected to the base station due to the low charge level of the battery <NUM>, without the power class switcher <NUM> potentially instructing the UE <NUM> to change to using Power Class <NUM> and thus potentially causing the UE to consumer power at higher power consumption levels. Similarly, if the UE <NUM> is in an idle state and is not actively sending or receiving data, the UE <NUM> may also suppress information in the UE capability data <NUM> indicating that the UE <NUM> also supports Power Class <NUM> in addition to Power Class <NUM>, such that the UE <NUM> can use Power Class <NUM> while idle. However, if the UE <NUM> moves from the idle state to an active state, the UE <NUM> may provide new UE capability data <NUM> indicating that the UE <NUM> does support both Power Class <NUM> and Power Class <NUM>, such that the power class switcher <NUM> can dynamically instruct the UE <NUM> which of those power classes to use while the UE <NUM> is in the active state.

<FIG> shows an example <NUM> of system architecture for the UE <NUM>, in accordance with various examples. The UE <NUM> can include the battery <NUM>, the temperature sensor <NUM>, and the transmission interfaces <NUM> discussed above. The UE <NUM> can also have at least one memory <NUM>, processor(s) <NUM>, a display <NUM>, output devices <NUM>, input devices <NUM>, and/or a drive unit <NUM> including a machine readable medium <NUM>.

As discussed above, the battery <NUM> can be a Li-ion battery, a LiPo battery, a NiCd battery, a NiMH battery, or other type of battery. The temperature sensor <NUM> can be a thermocouple, thermistor, RTD, semiconductor-based integrated circuit, thermometer, and/or any other type of temperature sensor.

The transmission interfaces <NUM> can include transceivers, modems, interfaces, antennas, and/or other components that perform or assist in exchanging radio frequency (RF) communications with base stations of the RAN <NUM>, a Wi-Fi access point, or otherwise implement connections with one or more networks. The transmission interfaces <NUM> can be compatible with one or more radio access technologies, such as <NUM> NR radio access technologies and/or LTE radio access technologies.

The transmission interfaces <NUM> can also be configured to transmit data according to a selected power class, as described herein. In some examples, the transmission interfaces <NUM> can be configured to interpret a power class change indicator in a radio frame at a physical layer, and use a power class indicated by the power class change indicator, as described above with respect to <FIG>. In other examples, elements of the UE <NUM> above the physical layer can interpret a power class change indicator received in another type of message, such as an RRC reconfiguration message, and can instruct the transmission interfaces <NUM> to use the power class indicated by the power class change indicator.

In various examples, the memory <NUM> can include system memory, which may be volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two. The memory <NUM> can further include non-transitory computer-readable media, such as volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. System memory, removable storage, and non-removable storage are all examples of non-transitory computer-readable media. Examples of non-transitory computer-readable media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium which can be used to store the desired information and which can be accessed by the UE <NUM>. Any such non-transitory computer-readable media may be part of the UE <NUM>.

The memory <NUM> can include one or more software or firmware elements, such as computer-readable instructions that are executable by the one or more processors <NUM>. For example, the memory <NUM> can store computer-executable instructions that cause the UE <NUM> to transmit UE capability data <NUM> to the RAN <NUM>, transmit the UE report <NUM> to the RAN <NUM>, and/or interpret and implement the power class change indicator <NUM>. The memory <NUM> can also store other modules and data <NUM>, which can be utilized by the UE <NUM> to perform or enable performing any action taken by the UE <NUM>. The other modules and data <NUM> can include a UE platform, operating system, and applications, and data utilized by the platform, operating system, and applications.

In various examples, the processor(s) <NUM> can be a CPU, a graphics processing unit (GPU), or both CPU and GPU, or any other type of processing unit. Each of the one or more processor(s) <NUM> may have numerous arithmetic logic units (ALUs) that perform arithmetic and logical operations, as well as one or more control units (CUs) that extract instructions and stored content from processor cache memory, and then executes these instructions by calling on the ALUs, as necessary, during program execution. The processor(s) <NUM> may also be responsible for executing all computer applications stored in the memory <NUM>, which can be associated with common types of volatile (RAM) and/or nonvolatile (ROM) memory.

The display <NUM> can be a liquid crystal display or any other type of display commonly used in UEs. For example, the display <NUM> may be a touch-sensitive display screen, and can thus also act as an input device or keypad, such as for providing a soft-key keyboard, navigation buttons, or any other type of input.

The output devices <NUM> can include any sort of output devices known in the art, such as the display <NUM>, speakers, a vibrating mechanism, and/or a tactile feedback mechanism. Output devices <NUM> can also include ports for one or more peripheral devices, such as headphones, peripheral speakers, and/or a peripheral display.

The input devices <NUM> can include any sort of input devices known in the art. For example, input devices <NUM> can include a microphone, a keyboard/keypad, and/or a touch-sensitive display, such as the touch-sensitive display screen described above. A keyboard/keypad can be a push button numeric dialing pad, a multi-key keyboard, or one or more other types of keys or buttons, and can also include a j oystick-like controller, designated navigation buttons, or any other type of input mechanism.

The machine readable medium <NUM> can store one or more sets of instructions, such as software or firmware, that embodies any one or more of the methodologies or functions described herein. The instructions can also reside, completely or at least partially, within the memory <NUM>, processor(s) <NUM>, and/or transmission interface(s) <NUM> during execution thereof by the UE <NUM>. The memory <NUM> and the processor(s) <NUM> also can constitute machine readable media <NUM>.

<FIG> shows an example system architecture for a base station <NUM>, in accordance with various examples. In some examples, the base station <NUM> may be a gNB, eNB, or other base station or network element in the RAN <NUM>. As shown, the base station <NUM> can include processor(s) <NUM>, memory <NUM>, and transmission interfaces <NUM>.

The processor(s) <NUM> may be a CPU or any other type of processing unit. Each of the one or more processor(s) <NUM> may have numerous ALUs that perform arithmetic and logical operations, as well as one or more CUs that extract instructions and stored content from processor cache memory, and then executes these instructions by calling on the ALUs, as necessary, during program execution. The processor(s) <NUM> may also be responsible for executing all computer-executable instructions and/or computer applications stored in the memory <NUM>.

In various examples, the memory <NUM> can include system memory, which may be volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two. The memory <NUM> can also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Memory <NUM> can further include non-transitory computer-readable media, such as volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. System memory, removable storage, and non-removable storage are all examples of non-transitory computer-readable media. Examples of non-transitory computer-readable media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, DVD, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium which can be used to store the desired information and which can be accessed by the base station <NUM>. Any such non-transitory computer-readable media may be part of the base station <NUM>.

The memory <NUM> can store computer-readable instructions and/or other data associated with operations of the base station <NUM>. For example, the memory <NUM> can store UE power class data <NUM>, UE reports <NUM>, cell data <NUM>, and the power class switcher <NUM>.

The UE power class data <NUM> can indicate a set of power classes that each UE registered with the base station <NUM> supports, based on UE capability data reported by the UEs during network registration or at other times. For example, the UE power class data <NUM> may indicate that a first UE supports Power Class <NUM> and Power Class <NUM>, such that the power class switcher <NUM> can dynamically instruct the first UE to switch between using Power Class <NUM> and Power Class <NUM>. However, the UE power class data <NUM> may indicate that a second UE only supports Power Class <NUM>, such that the power class switcher <NUM> is not configured to dynamically change the power class of the second UE. The UE power class data <NUM> may also indicate that a third UE supports Power Class <NUM> and Power Class <NUM>, such that the power class switcher <NUM> can dynamically instruct the first UE to switch between using Power Class <NUM> and Power Class <NUM>.

The UE power class data <NUM> can also indicate a current power class for each UE. For example, based on the UE capability data <NUM> indicating that the UE <NUM> supports Power Class <NUM> and Power Class <NUM>, and SIB1 information broadcast indicating that the base station <NUM> permits UEs to use Power Class <NUM>, the base station <NUM> can infer that the UE <NUM> will initially use Power Class <NUM> upon registration with the base station <NUM>. The base station <NUM> can indicate, in a database, table, or other type of UE power class data <NUM>, that the UE <NUM> is currently using Power Class <NUM>. Thereafter, if the power class switcher <NUM> instructs the UE <NUM> to use Power Class <NUM>, the base station <NUM> can update the UE power class data <NUM> to indicate that the UE <NUM> is now using Power Class <NUM>. Accordingly, the base station <NUM> can update the UE power class data <NUM> to reflect the UE's current power classes based on initial power classes used by UEs, and/or later power class change indicators sent by the base station <NUM> to the UEs over time.

The UE reports <NUM> can include data from one or more UE reports, such as UE report <NUM>, collected from one or more UEs over time. For example, the UE <NUM> may periodically send new UE reports to the base station <NUM> over time. Different UEs may also send in different UE reports. The base station <NUM> can store some or all of the received UE reports in the memory <NUM> for use by the power class switcher <NUM>.

The cell data <NUM> can include metrics or other KPIs that are measured or derived for a cell associated with the base station <NUM>. For example, the cell data <NUM> can include an aggregated interference level associated with the cell, based on individual SINR measurements included in UE reports <NUM> provided by a set of UEs registered with the base station <NUM>. In some examples, the cell data <NUM> may also include an indication of how many UEs are currently registered with the base station <NUM>. The power class switcher <NUM> may consider the cell data <NUM> in addition to, or instead of, one or more of the UE reports <NUM> and/or the UE power class data <NUM> to determine whether to change the power class used by any of the registered UEs.

The memory <NUM> can further store other modules and data <NUM>, which can be utilized by the base station <NUM> to perform or enable performing any action taken by the base station <NUM>. The modules and data <NUM> can include a platform, operating system, firmware, and/or applications, and data utilized by the platform, operating system, firmware, and/or applications.

The transmission interfaces <NUM> can include one or more modems, receivers, transmitters, antennas, error correction units, symbol coders and decoders, processors, chips, application specific integrated circuits (ASICs), programmable circuit (e.g., field programmable gate arrays), firmware components, and/or other components that can establish connections with one or more UEs, other base stations or elements of the RAN <NUM>, elements of the core network <NUM>, and/or other network elements, and can transmit data over such connections. For example, the transmission interfaces <NUM> can establish one or more connections with the UE <NUM> over air interfaces. The transmission interfaces <NUM> can also support transmissions using one or more radio access technologies, such as <NUM> NR or LTE.

<FIG> shows a flowchart of a method <NUM> in accordance with the present invention by which the power class switcher <NUM> can dynamically determine a power class for the UE <NUM>. As discussed above, the power class switcher <NUM> may be an element of a base station, or other network element of the RAN <NUM>. The power class switcher <NUM> may have information that indicates a set of power classes <NUM> supported by the UE <NUM>, for instance based on UE capability data <NUM> reported by the UE <NUM> during network registration. The set of power classes <NUM> can include a first power class with a higher maximum output power, and a second power class with a lower maximum output power. For example, the first power class can be Power Class <NUM>, while the second power class can be Power Class <NUM>. The power class switcher <NUM> may also have information indicating which one of the supported power classes instance based on an inference of an initial power class selected by the UE <NUM> during a network registration procedure or based on a previous power class change indicator provided by the power class switcher <NUM> to the UE <NUM>.

At block <NUM>, the power class switcher <NUM> can receive the UE report <NUM> from the UE <NUM>. The UE report <NUM> can include power data <NUM>, temperature data <NUM>, radio condition data <NUM>, uplink transmission data <NUM>, and/or other types of information, as discussed above with respect to <FIG>.

At block <NUM>, the power class switcher <NUM> can determine whether a current charge level of the battery <NUM> is less than a predefined battery threshold. The battery threshold may be set at a battery charge level of <NUM>%, <NUM>%, <NUM>%, <NUM>%, or any other level. For example, the power class switcher <NUM> can determine if power data <NUM> provided by the UE <NUM> in the UE report <NUM> indicates that the charge level of the battery <NUM> is less than the predefined battery threshold.

If the power class switcher <NUM> determines that the current charge level of the battery <NUM> is less than the predefined battery threshold (Block <NUM> - Yes), the power class switcher <NUM> can determine that the UE <NUM> should be using the second power class. Because the second power class has a lower maximum output power than the first power class, and the current charge level of the battery <NUM> is less than the predefined battery threshold, use of the second power class may assist with preserving battery life of the battery <NUM>. Accordingly, at block <NUM>, the power class switcher <NUM> can configure the UE <NUM> to use the second power class, by sending the power class change indicator <NUM> to the UE <NUM> with a value indicating that the UE <NUM> should use the second power class. In some examples, if the UE <NUM> is already using the second power class, the value of the power class change indicator <NUM> may indicate that the UE <NUM> should continue to use the second power class. However, if the UE <NUM> is currently using the first power class, the value of the power class change indicator <NUM> may indicate that the UE <NUM> should switch from using the first power class to using the second power class.

If the power class switcher <NUM> determines that the current charge level of the battery <NUM> is at or above the predefined battery threshold (Block <NUM> - No), the power class switcher <NUM> can, at block <NUM>, determine whether a temperature of the UE <NUM> is above a predefined temperature threshold. The temperature threshold may be set at <NUM>, <NUM>, <NUM>, or any other temperature. For example, the power class switcher <NUM> can determine if temperature data <NUM> provided by the UE <NUM> in the UE report <NUM>, or an estimated temperature of the UE <NUM> inferred from power consumption rates and/or other metrics, indicates that a temperature of the UE <NUM> is above the predefined temperature threshold.

If the power class switcher <NUM> determines that the temperature of the UE <NUM> is above the predefined temperature threshold (Block <NUM> - Yes), the power class switcher <NUM> can determine that the UE <NUM> should be using the second power class. Because the second power class has a lower maximum output power than the first power class, use of the second power class may result in the temperature of the UE <NUM> being cooler than if the UE <NUM> uses the higher maximum output power allowed by the first power class. Accordingly, the power class switcher <NUM> can configure the UE <NUM> to use the second power class at block <NUM>, by sending the power class change indicator <NUM> to the UE <NUM> with a value indicating that the UE <NUM> should use the second power class. In some examples, if the UE <NUM> is already using the second power class, the value of the power class change indicator <NUM> may indicate that the UE <NUM> should continue to use the second power class. However, if the UE <NUM> is currently using the first power class, the value of the power class change indicator <NUM> may indicate that the UE <NUM> should switch from using the first power class to using the second power class.

If the power class switcher <NUM> determines that the temperature of the UE <NUM> is at or below the predefined temperature threshold (Block <NUM> - No), the power class switcher <NUM> can, at block <NUM>, determine whether an amount of uplink data to be sent by the UE <NUM> is less than a predefined data threshold. In some examples, the predefined data threshold can be an amount of data, such as <NUM> MB, <NUM> MB, or any other amount of data. In other examples, the predefined data threshold can be an uplink buffer fullness level, such as <NUM>%, <NUM>%, or any other buffer fullness level. For example, the power class switcher <NUM> can determine if a buffer fullness level provided by the UE <NUM> in uplink transmission data <NUM> of the UE report <NUM> indicates that an uplink buffer of the UE is filled to above the predefined data threshold.

If the power class switcher <NUM> determines that the amount of uplink data to be sent by the UE <NUM> is less than the predefined data threshold (Block <NUM> - Yes), the power class switcher <NUM> can determine that the UE <NUM> should be using the second power class. In this situation, the UE <NUM> may be sending relatively small amounts of data, or may have a relatively low uplink buffer fullness level. As such, the UE <NUM> may not appreciably benefit from using the higher maximum output power allowed by the first power class relative to the second power class. Accordingly, the power class switcher <NUM> can configure the UE <NUM> to use the second power class at block <NUM>, by sending the power class change indicator <NUM> to the UE <NUM> with a value indicating that the UE <NUM> should use the second power class. In some examples, if the UE <NUM> is already using the second power class, the value of the power class change indicator <NUM> may indicate that the UE <NUM> should continue to use the second power class. However, if the UE <NUM> is currently using the first power class, the value of the power class change indicator <NUM> may indicate that the UE <NUM> should switch from using the first power class to using the second power class.

If the power class switcher <NUM> determines that the amount of uplink data to be sent by the UE <NUM> at or above the predefined data threshold (Block <NUM> - No), the power class switcher <NUM> can, at block <NUM>, determine whether one or more radio condition metrics associated with the UE <NUM> exceed a predefined radio condition threshold. For example, the power class switcher <NUM> can determine if a SINR value provided by the UE <NUM> in radio condition data <NUM> of the UE report <NUM> is above or below a predefined threshold SINR value.

If the power class switcher <NUM> determines that radio condition metrics associated with the UE <NUM> exceed a predefined radio condition threshold (Block <NUM> - Yes), the power class switcher <NUM> can determine that the UE <NUM> should be using the second power class. For example, a SINR value provided by the UE <NUM> may indicate that the UE is experiencing relatively low interference, and/or that the UE <NUM> may be located outside or at a position that is relatively close to the base station, such that transmitting uplink signals at up to the lower maximum output power permitted by the second power class may sufficiently allow the uplink signals to reach the base station. As such, the UE <NUM> may not appreciably benefit from using the higher maximum output power allowed by the first power class relative to the second power class. Accordingly, the power class switcher <NUM> can configure the UE <NUM> to use the second power class at block <NUM>, by sending the power class change indicator <NUM> to the UE <NUM> with a value indicating that the UE <NUM> should use the second power class. In some examples, if the UE <NUM> is already using the second power class, the value of the power class change indicator <NUM> may indicate that the UE <NUM> should continue to use the second power class. However, if the UE <NUM> is currently using the first power class, the value of the power class change indicator <NUM> may indicate that the UE <NUM> should switch from using the first power class to using the second power class.

If the power class switcher <NUM> determines that radio condition metrics associated with the UE <NUM> are at or below the predefined radio condition threshold (Block <NUM> - No), the power class switcher <NUM> can, at block <NUM>, determine that the UE <NUM> should be using the first power class. For example, a SINR value provided by the UE <NUM> may indicate that the UE is experiencing relatively high interference, and/or that the UE <NUM> may be located inside or at a position that is relatively far away from the base station, such that transmitting uplink signals at up to the higher maximum output power permitted by the first power class may be more likely to allow the uplink signals to reach the base station. Accordingly, the power class switcher <NUM> can configure the UE <NUM> to use the first power class at block <NUM>, by sending the power class change indicator <NUM> to the UE <NUM> with a value indicating that the UE <NUM> should use the first power class. In some examples, if the UE <NUM> is already using the first power class, the value of the power class change indicator <NUM> may indicate that the UE <NUM> should continue to use the first power class. However, if the UE <NUM> is currently using the second power class, the value of the power class change indicator <NUM> may indicate that the UE <NUM> should switch from using the second power class to using the first power class.

The order of operations shown in <FIG> is not intended to be limiting, as in other examples the power class switcher <NUM> may be configured to evaluate the factors shown in <FIG> in an order different from the order shown in <FIG>. For example, the power class switcher <NUM> may consider an amount of uplink data to be sent at block <NUM> and/or radio condition metrics at block <NUM> before considering a battery level of the UE <NUM> at block <NUM> and/or a temperature of the UE <NUM> at block <NUM>.

In still other examples, the power class switcher <NUM> may be configured to evaluate any or all of the factors shown in <FIG>, and/or other factors, and assign weights to each factor. The power class switcher <NUM> may accordingly use a weighted combination of the factors to determine whether to configure the UE <NUM> to use the second power class at block <NUM> or to configure the UE <NUM> to use the first power class at block <NUM>. For instance, if the battery <NUM> is at charge level of <NUM>% and the UE <NUM> is experiencing relatively poor radio conditions, the power class switcher <NUM> may weigh the charge level of the battery <NUM> less than the poor radio conditions, and determine that the UE <NUM> should use the first power class in an attempt to counteract the poor radio conditions. However, if the battery <NUM> is at charge level of <NUM>% and the UE <NUM> is experiencing similar relatively poor radio conditions, the power class switcher <NUM> may weigh the charge level of the battery <NUM> more heavily, and determine that the UE <NUM> should use the second power class in an attempt to extend the battery life of the UE <NUM> despite the relatively poor radio conditions.

As shown in <FIG>, although the UE <NUM> may support both the first power class and the second power class, the power class switcher <NUM> may tend to configure the UE <NUM> to use the second power class in situations in which the charge level of the battery <NUM> is low, the temperature of the UE <NUM> is high, the UE <NUM> is sending relatively little uplink data, and/or the UE <NUM> is experiencing relatively good radio conditions. In these situations, the extra uplink output power that the first power class may provide over the second power class may be unlikely to result in appreciable benefits to the UE <NUM>, or to a user of the UE <NUM>, and may instead result in increased power consumption, faster draining of the battery <NUM>, increased heat generation, and/or other appreciable drawbacks.

However, in other situations in which the charge level of the battery <NUM> is high, the temperature of the UE <NUM> is low, the UE <NUM> is sending a large amount of uplink data, and/or the UE <NUM> is experiencing relatively poor radio conditions, the power class switcher <NUM> may tend to configure the UE <NUM> to use the first power class. In these situations, the extra uplink output power that the first power class may provide over the second power class may be more likely to result in appreciable benefits to the UE <NUM>, or to a user of the UE <NUM>, such as improved signal strengths, improved signal propagation ranges, improved reliability, higher data transfer speeds, and/or other benefits. In these situations, users may be less likely to perceive increased power consumption, faster draining of the battery <NUM>, increased heat generation, and/or other appreciable impacts associated with using the first power class when the charge level of the battery <NUM> is high and/or the temperature of the UE <NUM> is low. Even if such impacts are noticed by users, users may consider such impacts to be an acceptable tradeoff to the improved reliability, higher data transfer speeds, or other benefits of the first power class when the charge level of the battery <NUM> is high and/or the temperature of the UE <NUM> is low.

<FIG> shows an example <NUM> of a computing device <NUM> that is configured to generate and provide a power class switcher configuration <NUM> to the power class switcher <NUM>. The power class switcher configuration <NUM> may be a configuration file that can be used by the power class switcher <NUM>, an update to the power class switcher <NUM>, a new version of the power class switcher <NUM>, or any other type of data that can adjust the operations of the power class switcher <NUM>. For example, the power class switcher configuration <NUM> may adjust which factors are considered by the power class switcher <NUM>, add or delete factors to be considered by the power class switcher <NUM>, adjust a relative order of when the power class switcher <NUM> considers different factors, define weights associated with different factors overall and/or in different situations, adjusts one or more threshold levels used to evaluate different factors, and/or adjusts any other operation or data used by the power class switcher <NUM>.

The computing device <NUM> can be a computer, server, or other computing device that can execute computer-readable instructions to send the power class switcher configuration <NUM> to the power class switcher <NUM> at the base station <NUM> via a network, such as the telecommunication network. For example, the computing device <NUM> can have processors, data interfaces, memory, machine readable media, and/or other computer architecture elements similar to the elements of the UE <NUM> shown in <FIG> or the base station <NUM> shown in <FIG>. In some examples, the computing device <NUM> may be operated by an operator of the telecommunication network, such that the operator can provide the power class switcher configuration <NUM> to adjust how the power class switcher <NUM> dynamically determines which power class the UE <NUM> should use. For example, the computing device <NUM> may be part of the core network <NUM>, the RAN <NUM>, or any other element of the telecommunication network.

In some examples, the computing device <NUM> can include, or be associated with, a machine learning model <NUM> that can be trained to generate the power class switcher configuration <NUM>. The machine learning model <NUM> can be based on support-vector networks, linear regression, logistic regression, nearest-neighbor algorithms, decision trees, recurrent neural networks or other types of neural networks, and/or other machine learning and/or artificial intelligence techniques.

Claim 1:
A method, comprising:
determining, by a base station (<NUM>) of a telecommunication network, that a user equipment, UE (<NUM>), supports a first power class and a second power class, wherein the first power class permits the UE (<NUM>) to perform uplink transmissions at a higher output power level than the second power class;
determining, by the base station (<NUM>), that the UE is configured to use the first power class;
receiving (<NUM>), by the base station (<NUM>) and from the UE (<NUM>), a UE report (<NUM>) indicating one or more UE metrics;
determining, (<NUM>) by the base station (<NUM>), that a UE battery level measurement included in the UE report (<NUM>) is below a battery threshold;
determining, by the base station (<NUM>), to dynamically change the UE (<NUM>) from using the first power class to using the second power class, based at least in part on determining that the UE battery level measurement is below the battery threshold; and
instructing (<NUM>), by the base station (<NUM>), the UE to use the second power class.