HK1255305B - Communication of preferred power consumption configurations - Google Patents

Description

Communication of preferred power consumption configuration

The application is a divisional application of a patent application with the same name and the application number of 201380045208.9, wherein the application date is 2013, 9, 27.

RELATED APPLICATIONS

This application claims priority to U.S. provisional patent application No.61/707,784, filed on day 9, 28, 2012, having a P49082Z title, the entire specification of which is incorporated herein by reference in its entirety for all purposes.

Background

Wireless mobile communication technology uses various standards and protocols to transmit data between a node (e.g., a transmission station) and a wireless device (e.g., a mobile device). Some wireless devices communicate using Orthogonal Frequency Division Multiple Access (OFDMA) in Downlink (DL) transmissions and single carrier frequency division multiple access (SC-FDMA) in Uplink (UL) transmissions. Standards and protocols for signal transmission using Orthogonal Frequency Division Multiplexing (OFDM) include: the third generation partnership project (3GPP) Long Term Evolution (LTE), the Institute of Electrical and Electronics Engineers (IEEE)802.16 standards (e.g., 802.16e, 802.16m) (the industry group commonly referred to as WiMAX (worldwide interoperability for microwave access)), and the IEEE 802.11 standard (the industry group commonly referred to as WiFi).

In a 3GPP Radio Access Network (RAN) LTE system, a node may be a combination of an evolved universal terrestrial radio access network (E-UTRAN) node B (also commonly denoted as evolved node B, enhanced node B, eNodeB, or eNB) and a Radio Network Controller (RNC) in communication with a wireless device, referred to as User Equipment (UE). Downlink (DL) transmissions may be communications from a node (e.g., eNodeB) to a wireless device (e.g., UE), and Uplink (UL) transmissions may be communications from the wireless device to the node.

Drawings

The features and advantages of the present invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, which together illustrate, by way of example, the features of the invention; and wherein:

FIG. 1 is a block diagram illustrating communication between a User Equipment (UE) and an evolved universal terrestrial radio access network (E-UTRAN), according to one example;

FIG. 2A illustrates a scheme for communicating a preferred power consumption configuration using a timer that is not started when a User Equipment (UE) switches to a low power consumption configuration, according to one example;

FIG. 2B illustrates a scheme for communicating a preferred power consumption configuration using a timer that starts when a User Equipment (UE) switches to a low power consumption configuration, according to one example;

FIG. 3 illustrates a scheme for communicating a preferred power consumption configuration using a threshold timer, according to one example;

FIG. 4 is a flow diagram illustrating a scheme for communicating a preferred power consumption configuration using a threshold timer, according to one example;

FIG. 5 illustrates an Abstract Syntax Notation (ASN) code example for communicating a preferred power consumption configuration using a threshold timer, according to an example;

FIGS. 6A and 6B are tables with field descriptions of various parameters and constants, respectively, for communicating a preferred power consumption configuration using a threshold timer, according to one example;

fig. 7 depicts functionality of computer circuitry of a User Equipment (UE) operable to communicate a Power Preference Indication (PPI) message, according to an example;

fig. 8 depicts a flow diagram of a method for communicating a Power Preference Indication (PPI) message, according to an example;

fig. 9 illustrates a block diagram of a User Equipment (UE) operable to communicate a Power Preference Indication (PPI) message, according to an example; and

fig. 10 illustrates a block diagram of a mobile device (e.g., user device) according to an example.

Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended.

Detailed Description

Before the present invention is disclosed and described, it is to be understood that this invention is not limited to the particular structures, process steps, or materials disclosed herein but extends to equivalents thereof as would be recognized by those ordinarily skilled in the pertinent art. It is also to be understood that the terminology used herein is for the purpose of describing particular examples only, and is not intended to be limiting.

Definition of

As used herein, the term "substantially" refers to a complete or nearly complete breadth or extent of an action, characteristic, attribute, state, structure, item, or result. For example, an object that is "substantially" closed would mean that the object is completely closed or nearly completely closed. The exact allowable degree of deviation from absolute completeness may in some cases depend on the particular context. However, in general, the proximity of completeness will be such that there is an overall result as if absolute and overall completeness were obtained. The use of "substantially" when used in a negative sense is equally applicable to refer to the complete or near complete absence of an action, characteristic, attribute, state, structure, item, or result.

Exemplary embodiments

An initial overview of technical embodiments is provided below, and specific technical embodiments are described in further detail later. This initial summary is intended to assist the reader in understanding the present technology more quickly, and is not intended to identify key features or essential features of the technology, nor is it intended to be used to limit the scope of the claimed subject matter. For purposes of summary and clarity of the embodiments described below, the following definitions are provided.

In 3GPP release 11, diverse data application enhancements (eDDA) are related to improving power efficiency of devices and signaling overhead on the air interface while supporting diverse data applications in LTE. In one example, a UE may communicate a Power Preference Indication (PPI) message to an evolved node b (eNB). The PPI message may be a one-bit UE assistance information message that improves power efficiency of the UE in the context of background traffic. In other words, the UE may communicate its preferred power consumption configuration (i.e., PPI information) to the eNB using the UE assistance information message. In response, the eNB may set or establish a power consumption configuration for the UE.

The preferred power consumption configuration for the UE may be a default power consumption configuration or a lower power consumption configuration. The default power consumption configuration may be a preferred power consumption configuration for the UE, particularly when the UE requires guaranteed performance. A lower power consumption configuration is preferred for power saving purposes. When the power preference is not configured or disabled at the UE, the network may assign a default power configuration to the UE. Further, the default power configuration may represent a preferred UE power configuration optimized for active traffic (e.g., delay sensitive applications). The active traffic session may include a time period when the user is actively interacting with the UE.

The lower power consumption configuration may represent a preferred UE power configuration optimized for device power savings and suitable for background traffic. The background traffic session may represent a duration when the user does not directly interact with the UE. During the background business session, the application may run in the background (background) and generate updates, notifications, etc. The low power configuration may configure the UE to have a relatively lower power consumption than the default power configuration. However, the default power consumption configuration may be more suitable for maintaining other performance parameters, such as reducing end-to-end latency for delay sensitive applications, than the low power consumption configuration.

In general, PPIs may allow a UE to efficiently reconfigure its power saving configuration based on the requirements of the applications running on the UE. However, each PPI indication causes over-the-air signaling overhead, and thus a mechanism for avoiding excessive or frequent power saving configuration changes may be needed. In LTE release 11, a timer-based mechanism is used to avoid excessive signaling of power preference indications from the UE. Thus in LTE release 11, the UE may not transmit additional preferred power consumption configurations to the eNB until the expiration of a timer (e.g., a T340 prohibit timer). In other words, the UE may transmit the further preferred power consumption configuration to the eNB only after the timer expires.

As an example, a timer may be started when the UE transmits a UE assistance information message indicating a default power consumption configuration. After the timer starts, the UE may not transmit additional PPI information indicating the low power configuration until the timer expires. Thus, a change of the UE from the default power consumption configuration to the low power consumption configuration may not occur before a latency time corresponding to a timer (e.g., T340).

In one example, the UE may have previously indicated its preference for a power configuration optimized for power conservation (i.e., a low power consumption configuration). If the UE detects the initiation of an active traffic with strict delay requirements (e.g., a delay-sensitive application), the UE may communicate a new preferred power consumption configuration (e.g., a default power consumption configuration for achieving lower latency) to the network as soon as possible for ensuring delay performance. However, if a T340 timer is applied in this case, the UE may need to wait until the timer expires before passing on the new preferred power consumption configuration. Since the low power configuration is optimized for power saving rather than latency, the delay in changing from the low power configuration to the default power configuration may adversely affect the latency performance of the UE.

The power saved by the UE assistance information may be balanced with minimizing delay requirements of applications running on the UE. In one example, the UE may not start a timer when changing to a low power configuration, thereby improving latency performance by allowing the UE to switch to a default power configuration in less time. However, by not starting the timer, the number of times the UE switches its preferred power consumption configuration and UE-assisted signaling may increase. Thus, as described in further detail below, UE-assisted signaling may be limited when a timer is not started after the UE transitions to a low power configuration.

FIG. 1 is a block diagram illustrating exemplary communications between a User Equipment (UE) and an evolved universal terrestrial radio access network (E-UTRAN). In one example, EUTRAN may include a plurality of evolved node bs (enbs). EUTRAN may transmit a Radio Resource Control (RRC) connection reconfiguration message to the UE. In general, the RRC connection reconfiguration message may modify the RRC connection between EUTRAN and the UE. The RRC connection reconfiguration message may be used to establish or modify a radio bearer, perform handover, establish or modify measurements, and so on.

After receiving the RRC connection reconfiguration message, the UE may transmit a UE assistance information message to EUTRAN. The UE assistance information message may indicate a preferred power consumption configuration of the UE, such as a low power consumption configuration or a default power consumption configuration. As previously discussed, the low power consumption configuration may configure the UE to have a relatively lower power consumption than the default power consumption configuration.

As discussed in more detail below, the low power configuration and the default power configuration may affect a Discontinuous Reception (DRX) cycle associated with the UE. In Wireless Wide Area Networks (WWANs), such as the third generation partnership project (3GPP) Long Term Evolution (LTE) network release 8, the concept of Discontinuous Reception (DRX) is introduced in order to save power. DRX may be used to enable a wireless device, e.g., a User Equipment (UE) in a 3GPP LTE network, to monitor control channels (e.g., a Physical Downlink Control Channel (PDCCH) transmitted from a transmission station such as an enhanced node b (enodeb)) discontinuously. Discontinuous monitoring may provide significant power savings at the UE, as the receiver at the UE may be turned off.

In one example, a WWAN transceiver in a wireless device may communicate with a transmission station, referred to as a network node, to negotiate a time period in which the wireless device will receive communications from the network node. During the negotiated time when no information is received, the wireless device may turn off its receiver and enter a low power state. Discontinuous reception is used in a number of different wireless communication standards including, but not limited to, 3GPP LTE releases 8, 9, 11, and 12 and the Institute of Electrical and Electronics Engineers (IEEE)802.11 standard.

In the 3GPP LTE standard, a set of functions is provided to enable an LTE configured receiver in a UE to perform sleep events. These sleep events may last anywhere from one millisecond to several hundred milliseconds or more. The duration and timing of sleep events may be negotiated between the UE and the network node. The negotiation may be performed using higher layer communications, such as Open Systems Interconnection (OSI) layer 3 communications, or another type of higher layer signaling. One example of OSI layer 3 communications in the 3GPP LTE standard is Radio Resource Control (RRC) signaling. In the LTE standard, RRC signaling is used to control DRX operation at LTE configured transceivers in the UE. RRC signaling may be used to manage the use of DRX by setting various parameters. For example, one of these parameters includes: a DRX cycle that identifies a periodic repetition of an active period (identified as an "On Duration") followed by a possible inactive period. There is a DRX long cycle and a DRX short cycle. Additional example parameters include an on-duration timer, a DRX inactivity timer, a DRX retransmission timer, a DRX short cycle, a short DRX cycle timer, an Uplink (UL) retransmission timer, and a Downlink (DL) retransmission timer.

Fig. 2A and 2B illustrate examples in which a User Equipment (UE) does not start a timer (e.g., a T340 prohibit timer) when switching to a low power configuration and starts the timer (e.g., the T340 prohibit timer) when switching to a low power configuration, respectively. The period of time for which the T340 disables the timer may be 1 millisecond (ms), 2ms, 5ms, 10ms, 20ms, 30ms, or the like. As shown in fig. 2A and 2B, the dashed arrow may indicate that the UE is initiating the default power consumption configuration, while the solid arrow may indicate that the UE is initiating the low power consumption configuration. TL may represent the amount of time the UE spends in the low power mode, where TL > 0. TD may represent the amount of time the UE spends in the default power consumption mode, where TD ≧ T340.

As shown in fig. 2A, the UE may initiate a default power consumption configuration (i.e., PPI) by communicating a PPI message to the eNB. The eNB may be in a default power consumption configuration during the period of T340. In other words, since the T340 timer starts when the UE switches to the default power consumption configuration, the UE may be in the default power consumption configuration at least during the length of the timer (e.g., T340). In one example, the UE may have a shorter Discontinuous Reception (DRX) cycle during the time spent in the default power consumption configuration.

The UE may then initiate a low power configuration. Further, the UE may not start the T340 timer after switching to the low power configuration. Thus, the amount of time the UE spends in the low power configuration may be less than or greater than the T340 timer, but greater than 0. In one example, the UE may have a longer DRX cycle and a greater delay during the time spent in the low power configuration. The UE may be in a low power consumption configuration during a time less than T340 and then subsequently initiate a default power consumption configuration. Since the UE switches to the default power consumption configuration faster (i.e., in a period less than T340), the average delay may be reduced. The UE may then switch from the default power consumption configuration to the low power consumption configuration again. The UE may be in the low power consumption configuration for a time less than T340 before switching back to the default power consumption configuration. The UE may be in a default power consumption configuration during the period of T340.

In the example shown in fig. 2A, excessive signaling may occur because the UE initiates the default power consumption configuration shortly after switching to the low power consumption configuration (i.e., a period of time less than the T340 timer). The initiation of the default power consumption configuration by the UE shortly after switching to the low power consumption configuration may be referred to as a ping-pong effect. However, since the T340 timer is not started after the UE switches to the low power configuration, the UE may avoid unnecessary delay (if the active traffic reaches the UE).

As shown in fig. 2B, the UE may initiate a default power consumption configuration (i.e., PPI) by communicating a PPI message to the eNB. The eNB may be in a default power consumption configuration during the period of T340. In other words, since the T340 timer starts when the UE switches to the default power consumption configuration, the UE may be in the default power consumption configuration at least during the length of the timer (e.g., T340). In one example, the UE may have a shorter Discontinuous Reception (DRX) cycle during the time spent in the default power consumption configuration.

The UE may then initiate a low power configuration. Further, a T340 timer may be started after the UE switches to the low power configuration. Thus, the amount of time the UE spends in the low power configuration may be greater than or equal to the T340 timer. In one example, the UE may have a longer DRX cycle and a greater delay during the time spent in the low power configuration. The UE may be in the low power consumption configuration during the period of T340 and then subsequently initiate the default power consumption configuration again. The UE may be in a default power consumption configuration during a period greater than the T340 timer. The UE may then switch to the low power configuration again and then remain in the low power configuration during the period of the T340 timer.

In the example shown in fig. 2B, the UE may avoid the ping-pong effect (i.e., the UE reverts from the low power consumption configuration to the default power consumption configuration in a time period less than the T340 timer), but at the expense of an undesirable time period with potentially higher average latency. Thus, when the T340 timer is started after the UE switches to the low power configuration, the end-to-end delay may increase in the case when active traffic arrives at the UE shortly after the UE transitions to the low power state, thereby adversely affecting the user experience. In one example, active traffic may arrive at the UE in a time period less than the T340 timer after the UE transitions into the low power consumption state.

Fig. 3 illustrates an exemplary scheme for communicating a preferred power consumption configuration using a threshold timer. Fig. 3 illustrates the use of a threshold timer to reduce the undesirable high latency periods that may be avoided if active traffic arrives at the UE, while at the same time controlling the excessive signaling overhead due to the ping-pong effect illustrated in fig. 2A. In one example, the threshold timer (e.g., T340 prohibit timer) may not be started automatically after the UE transmits the low power consumption configuration, as in LTE release 11. More specifically, after the UE transmits the low power configuration, the threshold timer may be implemented only when certain conditions are met that satisfy the threshold.

The UE may receive a signal including a predetermined threshold (N) from the eNB_{Threshold value}) The predetermined threshold value indicates a maximum number of PPI messages that the UE is capable of communicating to the eNB during the specified time window. In particular, the eNB may limit the number of PPI messages communicated by the UE after the UE communicates the low power configuration. In one example, the PPI configuration information may be dynamically reconfigured by the eNB according to network conditions. The PPI configuration information may include a predetermined threshold and a time window size associated with a prescribed time window. The size of the prescribed time window may be selected as the predetermined threshold multiplied by the length of the timer (i.e., N)_{Threshold value}x T340, 340). Further, the value of the predetermined threshold may be defined as an integer value such that N_{Threshold value}The time window size/T340 is not more than. In other words, the length of the prescribed time window may be some multiple of the length of the timer. For example, a time window size of 3 may indicate that the length of the time window is three times the length of the T340 timer. As another example, the length of the time window may be five times the length of the T340 timer or half the length of the T340 timer.

The UE may communicate a low power configuration to the eNB and then subsequently communicate a series of additional PPI messages to the eNB indicating the default power configuration or the low power configuration. The UE may monitor a number of additional PPI messages communicated to the eNB based on the PPI configuration information received from the eNB. The UE may start a threshold timer if the UE detects that the number of additional PPI messages exceeds a predetermined threshold during a specified time window (e.g., ten PPI message exchanges during the specified time window). The start of the threshold timer (e.g., T340 timer) may limit the UE from transmitting additional PPI messages during the length of the threshold timer. In particular, the threshold timer may be started after the last low power configuration message is transmitted to the eNB. The length of the threshold timer may be 1ms, 2ms, 5ms, 10ms, 20ms, 30ms, etc. Accordingly, the threshold timer is started depending on whether the number of further PPI messages exceeds a predetermined threshold. When starting the threshold timer, the UE may not transmit the preferred power consumption configuration to the eNB during the length of the threshold timer.

When the threshold timer expires (e.g., after 10 ms), the UE may not restart the timer unless certain conditions are met. In other words, the threshold timer may be deactivated (inactive), and the UE may freely communicate PPI messages (including low power configuration messages) to the eNB. The UE may not start the threshold timer after transmitting the low power configuration. However, if the number of PPI messages transmitted to the eNB exceeds a predetermined threshold as specified in the PPI configuration message received from the eNB, the UE may restart the threshold timer and prevent the UE from transmitting PPI messages until the threshold timer expires.

As shown in fig. 3, the UE may transmit a plurality of preferred power consumption configurations to the eNB. The dashed arrow may indicate that the UE is initiating a default power consumption configuration, while the solid arrow may indicate that the UE is initiating a low power consumption configuration. TL may represent the amount of time the UE spends in the low power mode, where TL > 0. TD may represent the amount of time the UE spends in the default power consumption mode, where TD ≧ T340.

As shown in fig. 3, the UE may initiate a default power consumption configuration. Since the T340 timer is activated when the UE transmits the default power consumption configuration to the eNB, the UE may spend a period of T340 in the default power consumption configuration. The UE may then initiate a low power configuration. After the UE transmits the low power consumption configuration, the threshold timer is not started as long as the UE does not subsequently change its preferred power consumption configuration within the predetermined threshold per time window. If the number of times the UE changes its power configuration is greater than a predetermined threshold, a threshold timer is activated and the UE may not send PPI messages to the eNB during the length of the threshold timer (e.g., T340 timer).

As illustrated in fig. 3, the UE may transmit a plurality of additional preferred power consumption configuration messages after the initial low power consumption configuration message. The plurality of further preferred power consumption configuration messages may exceed a predetermined threshold. Accordingly, a threshold timer (e.g., T340 timer) may be activated when the UE switches to a low power configuration after exceeding a predetermined threshold (shown by the second low power configuration in fig. 3). Therefore, the UE must wait until the T340 timer expires before transmitting another default power consumption configuration. Further, the UE may remain in the default power configuration during the time period of T340. By using a threshold timer to limit the number of preferred power consumption configurations transmitted to the eNB after the UE switches to a low power consumption configuration, excessive user-assisted signaling may be reduced at the UE.

FIG. 4 is a flow diagram illustrating a scheme for communicating a preferred power consumption configuration using a threshold timer. A User Equipment (UE) may receive a time window size and a predetermined threshold (N)_{Threshold value}). As previously discussed, the time window size may be a predetermined threshold (N)_{Threshold value}) Multiplied by the length of the timer (i.e., N)_{Threshold value}x T340) in which N is_{Threshold value}Is an integer. In one example, the UE may receive a time window size and a predetermined threshold from an evolved node b (enb) in a Radio Resource Control (RRC) configuration setup message. The UE may start a threshold timer (e.g., a T340 prohibit timer) using the time window size and a predetermined threshold. Further, the UE may identify an initial user state (e.g., a default power consumption configuration or a low power consumption configuration of the UE).

The UE may initialize a specified time window (e.g., a current time window) such that the current time window is 0. The UE may set a Power Preference Indication (PPI) count to 0. The UE may track the current time window. If the current time window is greater than the time window size, the UE may reinitialize the current time window to 0 and the PPI count to 0. Further, the UE may count the number of PPI messages exchanged between the UE and the eNB. As previously discussed, the UE may communicate PPI messages to change from the low-power state to the default state, or vice versa.

The UE may start a T340 timer after transmitting a PPI message indicating a default power consumption configuration to the eNB. Alternatively, the UE may not start the T340 timer after communicating the PPI message indicating the low power configuration to the eNB. The UE may monitor whether the PPI count (i.e., the number of PPI messages exchanged between the UE and the eNB) is greater than or equal to N_{Threshold value}. If the number of PPI messages is not greater than or equal to N_{Threshold value}The UE may continue to count the number of PPI messages exchanged between the UE and the eNB. Alternatively, if PPThe number of I messages is greater than or equal to N_{Threshold value}The UE may track the current time window. Further, the UE may start the T340 timer after transmitting an additional PPI message indicating a default power consumption configuration to the eNB. Alternatively, the UE may start the T340 timer after transmitting a further PPI message indicating the low power configuration to the eNB. If the current time window is greater than the time window size, the UE may reinitialize the current time window to 0 and the PPI count to 0, and continue to count the number of PPI messages exchanged between the UE and the eNB. The subsequent steps performed by the UE are as described previously.

Fig. 5 illustrates an Abstract Syntax Notation (ASN) code example for communicating a preferred power consumption configuration using a threshold timer. The eNB may transmit a Radio Resource Control (RRC) configuration setup message to the UE. The RRC configuration setup message may include other configuration (otherConfig) Information Elements (IEs). Fig. 5 illustrates exemplary asn.1 code associated with other configuration IEs. Specifically, the asn.1 code may configure a power preference indication-time window (powerpreformation-TimeWindow) with minimum and maximum integer values (e.g., N2 and N340, respectively). Further, the asn.1 code may configure a power preference indication predetermined threshold (powerprefndication-nth) having minimum and maximum integer values (e.g., N2 and N341, respectively).

Fig. 6A and 6B are tables with field descriptions for various parameters and constants, respectively, for communicating a preferred power consumption configuration using a threshold timer. In particular, the parameters and constants may be included in the ASN.1 code example associated with the other configuration IEs shown in FIG. 5. The parameters may include a power preference indication-time window and a power preference indication-N threshold. Parameter power preference indication-the time window may indicate the time window size from the timer T340 side. For example, if the power preference indicates-time window 2, the time window size will be twice the time period of T340. The parameter power preference indication-N threshold is an upper limit on the number of PPI messages that can be exchanged during each time window. If the power preference indication-N threshold is exceeded, a T340 timer may be started when the UE sends each PPI for a low power configuration. The constant N340 is the maximum value of the power preference indication-time window. The constant N341 is the maximum value of the power preference indication-N threshold.

Another example provides functionality 700 of computer circuitry of a User Equipment (UE) operable to communicate a Power Preference Indication (PPI) message, as shown in the flowchart in fig. 7. The functionality may be implemented as a method or the functionality may be executed as instructions on a machine, where the instructions are included on at least one computer readable medium or one non-transitory machine readable storage medium. The computer circuitry can be configured to: receiving PPI configuration information from an evolved node B (eNB), wherein the PPI configuration information comprises: a predetermined threshold for a number of PPI messages that the UE is capable of communicating to the eNB during a specified time window after indicating the low power configuration, as in block 710. The computer circuitry can be configured to: communicating a plurality of PPI messages during the defined time window after indicating the low power consumption configuration to the eNB, wherein each of the plurality of PPI messages indicates a change in the preferred power consumption configuration, as in block 720. The computer circuitry can be further configured to: detecting that the plurality of PPI messages exceeds a predetermined threshold for a number of PPI messages that the UE is capable of communicating to the eNB during the specified time window as specified in the PPI configuration information, as in block 730. The computer circuitry can be further configured to: in response to the plurality of PPI messages exceeding the predetermined threshold, a threshold timer is started to limit further PPI messages from being transmitted to the eNB until the threshold timer expires, as in block 740.

In one example, the PPI configuration information includes: a predetermined threshold and a time window size associated with the specified time window, wherein the time window size is the predetermined threshold multiplied by the length of a threshold timer. Further, the computer circuitry can be further configured to: at a UE, PPI configuration information is received from an eNB in a PPI configuration Information Element (IE) included in a Radio Resource Control (RRC) configuration setup message.

In one configuration, the computer circuitry can be further configured to: it is determined that when the plurality of PPI messages does not exceed the predetermined threshold during the defined time window, additional messages should not be restricted from being transmitted to the eNB. Further, the threshold timer is a T340 prohibit timer.

In one configuration, the computer circuitry can be further configured to: in response to the UE detecting initialization of the delay-sensitive application, a PPI message indicating a default power consumption configuration is communicated to the eNB. Further, the computer circuitry can be further configured to: restarting the threshold timer after the threshold timer expires when the plurality of PPI messages communicated after the threshold timer expires exceeds a predetermined threshold. In one example, the computer circuitry can be further configured to: the threshold timer is started in response to sending a PPI message to the eNB indicating a default power consumption configuration. Further, the UE may include: an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, internal memory, or a non-volatile memory port.

Another example provides a method 800 for communicating a Power Preference Indication (PPI) message, as shown in the flowchart in fig. 8. The method may be performed on a machine as instructions included on at least one computer-readable medium or one non-transitory machine-readable storage medium. The method comprises the following operations: communicating PPI configuration information from a node to a User Equipment (UE), wherein the PPI configuration information comprises: a predetermined threshold for a number of PPI messages that the UE is capable of communicating to the node during a specified time window when the UE is in the low power configuration, as in block 810. The method can comprise the following steps: receiving a plurality of PPI messages from the UE during the defined time window after receiving the PPI message indicating the low power consumption configuration, wherein each of the plurality of PPI messages indicates a change in the preferred power consumption configuration, as in block 820. The method may further comprise: in response to the UE detecting that the plurality of PPI messages communicated to the node during the prescribed time window exceeds the predetermined threshold, after expiration of a threshold timer started at the UE, receiving additional PPI messages from the UE, as in block 830.

In one example, the method may include: transmitting PPI configuration information including a predetermined threshold and a time window size associated with the specified time window to the UE, wherein the time window size is the predetermined threshold multiplied by the length of the threshold timer. Further, the method may comprise: the PPI configuration information is communicated from the node to the UE in a PPI configuration Information Element (IE) included in a Radio Resource Control (RRC) configuration setup message.

In one configuration, the method may include: after expiration of the T340 prohibit timer, additional PPI messages are received from the UE. Further, the method may comprise: in response to the UE detecting initialization of the delay-sensitive application, a PPI message is received at the node indicating a default power consumption configuration. Further, the method may comprise: receiving, from the UE, a plurality of PPI messages indicating a change in the preferred power consumption configuration, wherein the change in the preferred power consumption configuration indicates one of: a default power consumption configuration or a low power consumption configuration. In one example, the node is selected from the group consisting of a Base Station (BS), a node b (nb), an evolved node b (enb), a baseband unit (BBU), a Remote Radio Head (RRH), a Remote Radio Equipment (RRE), or a Remote Radio Unit (RRU).

Fig. 9 illustrates an example wireless device (e.g., user device) 900 configured to: a Power Preference Indication (PPI) message is transmitted as shown in another embodiment of the present invention. The wireless device includes: a PPI configuration module 902 configured to: receiving PPI configuration information from an evolved node B (eNB), wherein the PPI configuration information comprises: a predetermined threshold for a number of PPI messages that the UE may communicate to the eNB during a specified time window after indicating the low power configuration. The wireless device may include: a communication module 904 configured to: communicating a plurality of PPI messages during the defined time window after sending the low power consumption configuration to the eNB, wherein each of the plurality of PPI messages indicates a change in the preferred power consumption configuration. The wireless device may further include: a detection module 906 configured to: detecting that the plurality of PPI messages exceeds a predetermined threshold for a number of PPI messages that the UE is capable of communicating to the eNB during the specified time window as specified in the PPI configuration information. Further, the wireless device may include: a timer module 908 configured to: in response to the plurality of PPI messages exceeding a predetermined threshold, a threshold timer is started to limit further PPI messages from being transmitted to the eNB until the threshold timer expires.

In one example, the PPI configuration module is further configured to: at a UE, PPI configuration information is received from an eNB in a PPI configuration Information Element (IE) included in a Radio Resource Control (RRC) configuration setup message. Further, the communication module is further configured to: in response to the UE detecting initialization of the delay-sensitive application, a PPI message indicating a default power consumption configuration is communicated to the eNB.

In one configuration, the timer module is further configured to: determining that additional messages should not be restricted from being transmitted to the eNB when the plurality of PPI messages do not exceed the predetermined threshold during the defined time window. In one example, the timer module is further configured to: a T340 prohibit timer is started in response to the plurality of PPI messages exceeding a predetermined threshold. Further, the timer module is further configured to: restarting the threshold timer after expiration of the threshold timer when the plurality of PPI messages communicated after expiration of the threshold timer exceeds a predetermined threshold. Further, the timer module is further configured to: the threshold timer is started in response to the UE indicating a default power consumption configuration.

Fig. 10 provides an exemplary depiction of a mobile device, such as a User Equipment (UE), Mobile Station (MS), mobile wireless device, mobile communication device, tablet, handset, or other type of wireless device. The mobile device may include one or more antennas configured to communicate with a node, a macro node, a Low Power Node (LPN), or a transmission station (e.g., a Base Station (BS), an evolved node b (enb), a baseband unit (BBU), a Remote Radio Head (RRH), a Remote Radio Equipment (RRE), a Relay Station (RS), a Radio Equipment (RE), or other type of Wireless Wide Area Network (WWAN) access point). The mobile device may be configured to communicate using at least one wireless communication standard including 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), bluetooth, and WiFi. The mobile device may communicate using a separate antenna for each wireless communication standard or a shared antenna for multiple wireless communication standards. The mobile device may communicate in a Wireless Local Area Network (WLAN), a Wireless Personal Area Network (WPAN), and/or a WWAN.

Fig. 10 also provides a depiction of a microphone and one or more speakers that may be used for audio input and output from the mobile device. The display screen may be a Liquid Crystal Display (LCD) screen, or may be another type of display screen such as an Organic Light Emitting Diode (OLED) display. The display screen may be configured as a touch screen. The touch screen may use capacitive, resistive, or other types of touch screen technology. The application processor and the graphics processor may be coupled to internal memory to provide processing and display capabilities. The non-volatile memory port may also be used to provide data input/output options to a user. The non-volatile memory port may also be used to extend the memory capabilities of the mobile device. The keyboard may be integrated with the mobile device or wirelessly connected to the mobile device to provide additional user input. A touch screen may also be used to provide a virtual keyboard.

The various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, non-transitory computer-readable storage media, or any other machine-readable storage medium, wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. In the case of program code execution on programmable computers, the computing device may include: a processor, a storage medium readable by the processor (which includes volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. The volatile and nonvolatile memory and/or storage units can be RAM, EPROM, flash drive, optical drive, magnetic hard drive, or other media for storing electronic data. The base station and mobile device may also include a transceiver module, a counter module, a processing module, and/or a clock module or timer module. One or more programs that may implement or use the various techniques described herein may use an Application Programming Interface (API), reusable controls, and/or the like. The programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the programs may be implemented in assembly or machine language, if desired. In any event, the language may be a compiled or interpreted language, and combined with hardware implementations.

It should be appreciated that many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. These modules may be passive or active, including agents operable to perform desired functions.

Reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment.

As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. Furthermore, various embodiments and examples of the invention may be referred to herein along with various component alternatives thereof. It should be understood that these embodiments, examples and alternatives are not to be construed as actual equivalents of each other, but are to be considered as separate and autonomous representations of the invention.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided (e.g., examples of materials, fasteners, sizes, lengths, widths, shapes, etc.) in order to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention can be practiced without one or more of the specific details, or with other methods, components, arrangements, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.

While the foregoing examples illustrate the principles of the invention with one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the invention. Accordingly, it is not intended that the invention be limited, except as by the claims set forth below.

Claims (22)

1. An apparatus of a user equipment, UE, operable to determine a power preference indication, PPI, the apparatus comprising:

a memory; and

one or more processors configured to:

determining, at the UE, the PPI as one of low power consumption or normal power consumption;

starting a PPI timer at the UE when the PPI is set for the normal power consumption;

determining whether to start the PPI timer based on tracking of a predefined time window and an initial power consumption configuration of the UE when the PPI is set to the low power consumption; and

encoding, at the UE, the PPI for transmission to Evolved Universal Terrestrial Radio Access Network (EUTRAN) in a UE assistance information message.

2. The apparatus of claim 1, further comprising: a transceiver configured to communicate the PPI to the EUTRAN in the UE assistance information message.

3. The apparatus of claim 1, wherein the one or more processors are further configured to: decoding a PPI configuration received from the EUTRAN, wherein the PPI configuration configures the UE to transmit the PPI to the EUTRAN in the UE assistance information message.

4. The apparatus of claim 1, wherein the one or more processors are configured to: encoding the PPI for transmission to the EUTRAN in a UE assistance information message when the UE does not transmit the UE assistance information message to the EUTRAN since the reception of the PPI configuration from the EUTRAN.

5. The apparatus of claim 1, wherein the UE assistance information message indicates a different PPI than a last UE assistance information message transmitted to the EUTRAN, and the PPI timer is not running.

6. The apparatus of claim 1, wherein the one or more processors are further configured to: setting the PPI to the low power consumption, wherein the PPI timer is not started when the PPI is set to the low power consumption.

7. The apparatus of claim 1, wherein the one or more processors are further configured to: decoding a radio resource control, RRC, reconfiguration message from the EUTRAN including a PPI configuration.

8. The apparatus of claim 1, wherein the PPI timer is a T340 timer.

9. The apparatus of claim 1, wherein the apparatus comprises: an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, internal memory, or a non-volatile memory port.

10. An apparatus of an evolved universal terrestrial radio access network, EUTRAN, operable to decode a power preference indication, PPI, received from a user equipment, UE, the apparatus comprising:

a memory; and

one or more processors configured to:

encoding a PPI configuration for communication to the UE, wherein the PPI configuration comprises a predetermined threshold indicating a maximum number of PPIs the UE communicates to the apparatus during a predefined time window; and

decoding the PPI received from the UE in a UE assistance information message at the EUTRAN, wherein the PPI is one of low power consumption or normal power consumption.

11. The apparatus of claim 10, wherein the one or more processors are further configured to: the PPI configuration configures the UE to transmit the PPI to the EUTRAN in the UE assistance information message.

12. The apparatus of claim 10, wherein the one or more processors are configured to: decoding the PPI received from the UE in a UE assistance information message when the UE does not transmit the UE assistance information message to the EUTRAN since the PPI configuration was received from the EUTRAN.

13. The apparatus of claim 10, wherein the UE assistance information message indicates a different PPI than a last UE assistance information message received from the UE, and the PPI timer is not running.

14. The apparatus of claim 10, wherein the one or more processors are further configured to: encoding a radio resource control, RRC, reconfiguration message including a PPI configuration for communication to the UE.

15. The apparatus of claim 10, wherein the PPI timer is a T340 timer.

16. A machine-readable storage medium having stored thereon instructions for determining, at a user equipment, UE, a power preference indication, PPI, which when executed by one or more processors, cause the UE to:

determining, at the UE, the PPI as one of low power consumption or normal power consumption;

starting a PPI timer at the UE when the PPI is set for the normal power consumption;

determining whether to start the PPI timer based on tracking of a predefined time window and an initial power consumption configuration of the UE when the PPI is set to the low power consumption; and

encoding, at the UE, the PPI for transmission to Evolved Universal Terrestrial Radio Access Network (EUTRAN) in a UE assistance information message.

17. The machine-readable storage medium of claim 16, further comprising instructions which, when executed by the one or more processors, cause the UE to: decoding a PPI configuration received from the EUTRAN, wherein the PPI configuration configures the UE to transmit the PPI to the EUTRAN in the UE assistance information message.

18. The machine-readable storage medium of claim 16, further comprising instructions which, when executed by the one or more processors, cause the UE to: encoding the PPI for transmission to the EUTRAN in a UE assistance information message when the UE does not transmit the UE assistance information message to the EUTRAN since the reception of the PPI configuration from the EUTRAN.

19. The machine-readable storage medium of claim 16, wherein the UE assistance information message indicates a different PPI than a last UE assistance information message transmitted to the EUTRAN, and the PPI timer is not running.

20. The machine-readable storage medium of claim 16, further comprising instructions which, when executed by the one or more processors, cause the UE to: setting the PPI to the low power consumption, wherein the PPI timer is not started when the PPI is set to the low power consumption.

21. The machine-readable storage medium of claim 16, further comprising instructions which, when executed by the one or more processors, cause the UE to: decoding a radio resource control, RRC, reconfiguration message from the EUTRAN including a PPI configuration.

22. The machine-readable storage medium of claim 16, wherein the PPI timer is a T340 timer.