Patent Description:
Embodiments described herein pertain generally to wireless communications and in particular to methods and apparatus for uplink power control enhancement in Long-Term Evolution Advanced (LTE-A, LTE-Advanced) communications environments.

Mobile devices (e.g. user equipment (UE)) in heterogeneous network environments, such as LTE-Advanced network environments, may simultaneously communicate with multiple access points, which may include a primary access point, or PCell, and one or more secondary access points, or SCells. In some systems, a macro cell may serve as the PCell, the primary access point governing mobility and other control processes, and one or more SCells (small cells or other macro cells) may serve as the one or more secondary access points that are utilized for data offloading. In such example systems, the maximum transmission power for a mobile device in a subframe can be easily reached by transmitting control messages to the PCell, leaving little to no power for data transmission to the SCells. Thus, there is a need for improved power allocation management in heterogeneous network environments.

<CIT>, discloses allocating transmit power among two or more carriers assigned to a wireless communication device. Moreover, <CIT>, discloses techniques for power control and timing advance.

R2-<NUM> is a 3GPP WG2#<NUM> discussion paper on Initial setup procedure for dual connectivity.

R1-<NUM> is another 3GPP WG1#<NUM> discussion paper on UL control enhancements for Macro-RRH deployments.

The present disclosure presents example methods and apparatuses for improved uplink power control in LTE-Advanced wireless environments, wherein a UE may communicate with multiple cells, including a PCell and one or more SCells, over multiple component carriers using carrier aggregation (CA). In such environments, some examples of the improved uplink power control methods and apparatuses described herein may be based on a power allocation tradeoff strategy using a Minimum Proactive Power Limitation (MPLL) per component carrier, PCMIN,c. In an aspect, if the total transmit power of a UE in a subframe i over all cells and all component carriers would exceed a linear value of a configured maximum output power P̂CMAX(i), the UE may assign PCMIN,c, first to each serving cell c in subframe i, and the remaining power would be assigned to uplink channels, whether PCell or SCell channels, or control or data channels, based on priority. In some examples, this priority may be given first to a physical uplink control channel (PUCCH) (e.g. uplink channel to the primary macro cell, or PCell), then to a physical uplink shared channel (PUSCH) with downlink control information (DCI) (e.g. an uplink channel to the primary macro cell), and then to a PUSCH without DCI (e.g. an uplink channel to one or more SCells. This prioritization allows UEs in LTE-Advanced environments to offload data uplink transmissions to SCells (e.g. via PUSCH) while ensuring that necessary control signaling with the PCell remains intact in the uplink (e.g. via PUCCH), even in a restrictive UE power condition.

<FIG> is a system diagram illustrating an LTE-Advanced wireless system in accordance with some embodiments. <FIG> includes an example UE <NUM>, which may communicate wirelessly with a PCell <NUM> over a wireless communication link <NUM>. In an aspect, communication link <NUM> may include one or more communication channels, which may include a PUCCH, a PUSCH with DCI transmitted on the downlink (or DCI not transmitted on the downlink), and any other channel for transmitting control (e.g. scheduling or power) information or data on the uplink or downlink. Because system <NUM> may support carrier aggregation (e.g. may be an LTE-A system) these channels may be comprised of one or more component carriers that may be aggregated.

Furthermore, PCell <NUM> may be a cell associated with a macro network, such as, but not limited to, a radio access network or cellular network. For example, in some examples, PCell <NUM> may comprise a PCell in LTE-Advanced communication environments. In a further aspect, PCell <NUM> of <FIG> may be associated with a PCell network entity <NUM>, which may comprise or include one or more of any type of network module, such as an access point, a macro cell, including a base station (BS), node B, eNodeB (eNB), a relay, a peer-to-peer device, an authentication, authorization and accounting (AAA) server, a mobile switching center (MSC), a radio network controller (RNC). Additionally, the network entity associated with PCell <NUM> may communicate with one or more other network entities of wireless and/or core networks, such as, but not limited to, wide-area networks (WAN), wireless networks (e.g. <NUM> or cellular network), the Public Switched Telephone Network (PSTN) network, ad hoc networks, personal area networks (e.g. Bluetooth®) or other combinations or permutations of network protocols and network types. Such network(s) may include a single local area network (LAN) or wide-area network (WAN), or combinations of LANs or WANs, such as the Internet.

In an aspect, the UE <NUM> may be a mobile device, such as, but not limited to, a smartphone, cellular telephone, mobile phone, laptop computer, tablet computer, or other portable networked device. In addition, UE <NUM> may also be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. In general, UE <NUM> may be small and light enough to be considered portable. Furthermore, UE <NUM> may include an uplink power manager <NUM>, which may be configured to manage the transmission power of uplink transmissions associated with UE <NUM>.

In a further aspect, UE <NUM> may communicate with one or more SCells <NUM> (dotted line indicating that a plurality of SCells is optional) via one or more communication links <NUM>. In some examples, the one or more SCells <NUM> may include SCells in LTE-Advanced communication environments. In an aspect, UE <NUM> may be configured to communicate simultaneously with PCell <NUM> and the one or more SCells <NUM>, for example, via a plurality of antennas of UE <NUM>. In an aspect, communication link <NUM> may include one or more communication channels, which may include a PUCCH, a PUSCH with DCI transmitted on the downlink (or DCI not transmitted on the downlink), and any other channel for transmitting control (e.g. scheduling or power) information or data on the uplink or downlink.

In an aspect, SCells <NUM> may be small cells or low power cells, controlled by or otherwise associated with one or more network entities or modules, such as, but not limited to a low-power access point, such as a picocell, femtocell, microcell, WiFi hotspot, etc. Additionally, SCells <NUM> may communicate with one or more other network entities of wireless and/or core networks, such as, but not limited to, wide-area networks (WAN), wireless networks (e.g. <NUM> or cellular network), the Public Switched Telephone Network (PSTN) network, ad hoc networks, personal area networks (e.g. Bluetooth®) or other combinations or permutations of network protocols and network types. Such network(s) may include a single local area network (LAN) or wide-area network (WAN), or combinations of LANs or WANs, such as the Internet.

Additionally, system <NUM>, which may include PCell <NUM> and one or more SCells <NUM>, may comprise a Wideband Code Division Multiple Access (W-CDMA) system, and PCell <NUM> and one or more SCells <NUM> may communicate with one or more UEs <NUM> according to this standard. By way of example, various aspects may be extended to other Universal Mobile Telecommunications System (UMTS) systems such as Time Division Synchronous Code Division Multiple Access (TD-SCDMA), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+) and Time-Division CDMA (TD-CDMA). Various aspects may also be extended to systems employing Long Term Evolution (LTE) (in FDD, TDD, or both modes), LTE-Advanced (LTE-A) (in FDD, TDD, or both modes), CDMA2000, Evolution-Data Optimized (EV-DO), Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) <NUM> (Wi-Fi), IEEE <NUM> (WiMAX®), IEEE <NUM>, Ultra-Wideband (UWB), Bluetooth, and/or other suitable systems. The various devices coupled to the network(s) (e.g. UE <NUM> and/or network entities serving PCell <NUM> and/or SCells <NUM>) may be coupled to the network(s) via one or more wired or wireless connections.

In example embodiments, the UE <NUM> may comprise processing circuitry arranged to determine whether a total desired transmission power over a plurality of channels exceeds a total configured maximum output power for a subframe when the UE is scheduled for concurrent physical uplink control channel (PUCCH) and physical uplink shared channel (PUSCH) transmission by an enhanced node B (eNB) in the subframe. The processing circuitry may also be arranged to initially allocate a minimum proactive power to the channels. The processing circuitry may also be arranged to initially allocate any remaining power of a power budget to the channels based on priority. The UE <NUM> may also include a transceiver configured by the processing circuitry to transmit the channels in accordance the minimum proactive power and the remaining power allocations. In these embodiments, the PUCCH of a primary cell (PCell) is allocated power as a first priority, a physical uplink shared channel (PUSCH) with downlink control information (DCI) of the PCell is allocated power as a second priority, and the PUSCH without DCI of a secondary cell (SCell) is allocated power as a lowest priority.

In some embodiments, the processing circuitry may also compute the total power assignment from the minimum proactive power and the remaining power allocations. In Some embodiments, the processing circuitry may also initially allocate the minimum proactive power to the channels based on the priorities.

<FIG> is a block diagram illustrating an example UE including uplink power manager in accordance with some embodiments, which may be configured to manage uplink power allocation associated with a UE (e.g. UE <NUM> of <FIG>). In an aspect, uplink power manager <NUM> may include a power comparison module <NUM>, which may be configured to compare power values to determine whether a total desired transmission power <NUM> of the UE for a particular subframe i exceeds a total configured maximum output power <NUM> (represented herein as P̂CMAX(i) ), for the subframe. In some examples, the total desired transmission power <NUM> of the UE may include the sum of multiple module transmission powers, which may include, but are not limited to: the sum of uplink PUSCH channel transmission powers to each serving cell in subframe i (represented herein as <MAT>) and the transmission power value of any uplink transmission to the PCell on the PUCCH during subframe i (represented herein as P̂PUCCH(i) ). In other words, power comparison module <NUM> may be configured to evaluate one or both of the following inequalities: <MAT> <MAT>.

In addition, uplink power manager <NUM> may include a minimum proactive power allocating module <NUM>, which may be configured to allocate a minimum proactive power, PCMIN,c. to one or more uplink channels where power comparison module <NUM> determines that the total desired transmission power exceeds the total configured maximum output power. In an aspect, minimum proactive power module <NUM> may include a minimum proactive power computing module <NUM>, which may be configured to compute one or more minimum proactive power values corresponding to each serving channel c, PCMIN,c. which may be allocated to one or more uplink channels associated with a UE. In a non-limiting aspect, PCMIN,c may be allocated to one or more uplink channels to ensure a non-zero uplink power allocation to each such channel. Furthermore, in an aspect, the minimum proactive power PCMIN,c can be computed such that, when allocated and applied, it may have a minor impact to total power limitation. In one such non-limiting example, where the total power limitation is 23dBm, the PCMIN,c can be set to affect a maximum <NUM> dB degradation to the 23dBm total power limitation (e.g. (<NUM>^(<NUM>/<NUM>)) - (<NUM>^(<NUM>/<NUM>)) = <NUM> mw = <NUM> dBm). In another non-limiting aspect, the minimum proactive power PCMIN,c can be set as the uplink power to meet the coverage of a small cell, and may comprise one value among a set of potential configurable values (e.g. 0dBm, 10dBm). In an additional aspect, this value can be configurable for network optimization adjustment purposes.

In an additional aspect, minimum proactive power allocating module <NUM> may allocate the minimum proactive power individually to two or more channels based on priority. This priority may conform to the power priority definition of existing standards, including, but not limited to standards promulgated by the Third Generation Partnership Project (3GPP), for example, in <NPL> and <NPL>".

For example, in an aspect, the uplink transmission power priority exercised by minimum proactive power allocating module <NUM> may allocate PCMIN,c to uplink channels according to the following priority: <MAT>.

As such, minimum proactive power allocating module may include a PUCCH power allocating module <NUM>, which may be configured to allocate a portion of the limited uplink power budget of the UE as a first part of a PUCCH power as first priority. In a non-limiting example aspect, this first part of the PUCCH power may be allocated as a function of PCMIN,c in subframe i according to the following equation: <MAT> where P̂CMIN,c(i) represents the linear value of the minimum proactive power limitation defined for the serving cell c of the PUCCH (e.g. the PCell, such as PCell <NUM> of <FIG>) for subframe i; and P̂CMAX,c(i) represents the linear value of PCMAX,c(i), which may be defined by the requirements of a standard (e.g. 3GPP TS <NUM> "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) Radio Transmission and Reception").

Additionally, uplink power manager <NUM> may include a remaining power calculating module <NUM>, which may be configured to calculate a linear value of a remaining power, represented herein as P̂REMAINING(i), of a limited uplink power budget for the uplink subframe i after a module of the minimum proactive power allocating module <NUM> allocates uplink power to one or more channels. For example, in an aspect, after PUCCH power allocating module <NUM> allocates P̂PUCCH_Part<NUM> according to Equation (<NUM>), remaining power calculating module <NUM> may calculate P̂REMAINING(i) according to the following algorithm: <MAT>.

Based on this P̂REMAINING(i), the minimum proactive power allocating module may then allocate remaining uplink power to other channels. For example, minimum proactive power allocating module <NUM> may include a PUSCH with DCI power allocating module <NUM>, which may be configured to allocate uplink power to a PUSCH channel with DCI in the downlink (e.g. a channel for data communication with the PCell, which may be a macro cell) as a second priority. In an aspect, PUSCH with DCI power allocating module <NUM> may allocate a first part of such a PUSCH with DCI channel uplink power based on the following equation: <MAT> where P̂PUSCHw/DCI,c(i) represents the total allowed uplink power for the channel. In addition, once the P̂PUSCHw/DCI _Part<NUM> value has been calculated by PUSCH with DCI power allocating module <NUM>, remaining power calculating module <NUM> may update the remaining power <NUM> value, as more available power for the subframe has been allocated to the PUSCH with DCI channel(s). In an aspect, remaining power calculating module <NUM> may do so according to the following equation: <MAT> where P̂REMAINING represents the stored value of remaining power <NUM> (e.g. stored in memory) and P̂REMAINING(i) represents the updated value of remaining power <NUM> after the updating.

Additionally, minimum proactive power allocating module <NUM> may include a PUSCH without DCI power allocating module <NUM>, which may be configured to allocate uplink power to one or more PUSCH channels that do not transport DCI information on the downlink. In an aspect, such channels may facilitate communication between a UE and a SCell, which may be a small cell, though the present disclosure is not limited to such a scenario. Further, PUSCH without DCI power allocating module <NUM> may be configured to allocate remaining uplink power to such a channel as a lowest priority, or third priority, of the PUCCH, PUSCH with DCI, and PUSCH without DCI channels. For example, PUSCH without DCI power allocating module <NUM> may be configured to allocate a first part of a PUSCH without DCI power, P̂PUSCHw/oDCI _Part<NUM>, according to the following algorithm: <MAT>.

In addition, once the P̂PUSCHw/oDCI _Part<NUM> value has been calculated by PUSCH without DCI power allocating module <NUM>, remaining power calculating module <NUM> may update the remaining power <NUM> value, as more available power for the subframe has been allocated to a first part of the PUSCH without DCI channel(s). In an aspect, remaining power calculating module <NUM> may do so according to the following equation: <MAT> where P̂REMAINING represents the stored value of remaining power <NUM> (e.g. stored in memory) and P̂REMAINING(i) represents the updated value of remaining power <NUM> after the updating.

In addition, uplink power manager <NUM> may include a remaining power assigning module <NUM>, which may be configured to assign remaining uplink power to one or more channels after an initial power allocation, which may be performed by minimum proactive power allocating module <NUM>. In an aspect, remaining power assigning module <NUM> may include a remaining PUCCH power assigning module <NUM>, which may be configured to assign a second part of a PUCCH power, P̂PUCCH_Part<NUM>, to the PUCCH, for example, where the first part of the PUCCH uplink transmission power, P̂PUCCHPart<NUM>, is less than the standard-allocated maximum PUCCH power, P̂PUCCH(i), for subframe i. In other words, remaining PUCCH power assigning module <NUM> may be configured to evaluate the inequality: P̂PUCCH_Part<NUM> < P̂PUCCH(i). Where this inequality is true, remaining PUCCH power assigning module <NUM> may be configured to set P̂PUCCH_Part<NUM> according to the following equation: <MAT>.

Additionally, once the P̂PUCCH_Part<NUM> value has been calculated by remaining PUCCH power assigning module <NUM>, remaining power calculating module <NUM> may update the remaining power <NUM> value, as more available power for the subframe has been allocated to the second part of the PUCCH channel(s). In an aspect, remaining power calculating module <NUM> may do so according to the following equation: <MAT>.

In a further aspect, remaining power assigning module <NUM> may include a remaining PUSCH with DCI power assigning module <NUM>, which may be configured to assign a second part of a PUSCH with DCI uplink transmission power, P̂PUSCHw/DCI _Part<NUM>, to the PUSCH with DCI channel(s) as a second priority. Remaining PUSCH with DCI power assigning module <NUM> may be configured to do so, for example, where the first part of the PUSCH with DCI uplink transmission power, P̂PUSCHw/DCI _Part<NUM>, is less than the standard-allocated maximum PUSCH with DCI per-channel power, P̂PUSCHw/DCI,c(i), for subframe i and cell c. In other words, remaining PUSCH with DCI power assigning module <NUM> may be configured to evaluate the inequality: P̂PUSCHw/DCI _Part<NUM> < P̂PUSCHw/DCI,c(i). Where this inequality is true, remaining PUSCH with DCI power assigning module <NUM> may be configured to set P̂PUSCHw/DCI _Part<NUM> according to the following equation: <MAT>.

Additionally, once the P̂PUSCHw/DCI _Part2 value has been calculated by remaining PUSCH with DCI power assigning module <NUM>, remaining power calculating module <NUM> may update the remaining power <NUM> value, as more available power for the subframe has been allocated to the second part of the PUSCH with DCI channel(s). In an aspect, remaining power calculating module <NUM> may do so according to the following equation: <MAT>.

Moreover, remaining power assigning module <NUM> may include a remaining PUSCH without DCI power assigning module <NUM>, which may be configured to assign a second part of a PUSCH without DCI uplink transmission power, P̂PUSCHw/oDCI _Part<NUM>, to the PUSCH without DCI channel(s) as a third (or least) priority. Remaining PUSCH without DCI power assigning module <NUM> may be configured to do so, for example, where the first part of the PUSCH without DCI uplink transmission power, P̂PUSCHw/oDCI _Part<NUM>, is less than the standard-allocated maximum PUSCH without DCI per-channel power, P̂PUSCHw/DCI,c(i), for subframe i and cell c. In other words, remaining PUSCH without DCI power assigning module <NUM> may be configured to evaluate the inequality: P̂PUSCHw/oDCI _Part<NUM> < P̂PUSCHw/oDCI,c(i). Where this inequality is true, remaining PUSCH without DCI power assigning module <NUM> may be configured to set P̂PUSCHw/oDCI _Part<NUM> according to the following equation: <MAT>.

Additionally, once the P̂PUSCHw/oDCI _Part<NUM> value has been calculated by remaining PUSCH without DCI power assigning module <NUM>, remaining power calculating module <NUM> may update the remaining power <NUM> value, as more available power for the subframe has been allocated to the second part of the PUSCH without DCI channel(s). In an aspect, remaining power calculating module <NUM> may do so according to the following equation: <MAT>.

Additionally, uplink power manager <NUM> may include a total power assignment computing module <NUM>, which may be configured to compute a total power assignment for each uplink channel scheduled to transmit uplink data in a subframe. In an aspect, total power assignment computing module <NUM> may be configured to compute these total power assignments by combining and/or summing component (e.g. Part <NUM>, Part <NUM>, and so on) power allocation or assignment values for one or more channels, which may have been assigned, allocated, and/or stored by one or more other modules of uplink power manager <NUM>-such as, but not limited to, minimum proactive power allocating module <NUM> and/or remaining power assigning module <NUM>.

For example, in an aspect, total power assignment computing module <NUM> may be configured to compute a total PUCCH uplink assignment value, P̂PUCCH_TOTAL, for subframe i according to the following equation: <MAT>.

Likewise, total power assignment computing module <NUM> may be configured to compute a total PUSCH with DCI uplink assignment value, P̂PUSCHw/DCI _TOTAL, for subframe i and for each channel c according to the following equation: <MAT>.

Furthermore, total power assignment computing module <NUM> may be configured to compute a total PUSCH without DCI uplink assignment value, P̂PUSCHw/oDCI _TOTAL, for subframe i and for each channel c according to the following equation: <MAT>.

<FIG> is a flowchart illustrating a method <NUM> for improved uplink transmission power management, according to some example embodiments. In some examples, method <NUM> and/or any of the method steps comprising method <NUM> may be configured to be performed by a processing apparatus, which may include UE <NUM> of <FIG>, a network device (e.g. a network entity of primary or SCells of <FIG>) and/or a method therein, for example. In some examples, method <NUM> may be performed during transmission scheduling procedures for each uplink transmission subframe i of a plurality of transmission subframes in a slot, frame, block, or any other transmission window, slot, or other temporal or wavelength transmission-organizing mechanism or procedure.

In an aspect, method <NUM> may include a decision at block <NUM>, wherein the processing apparatus may determine whether a total desired transmission power exceeds a total configured maximum output power. Where the total desired transmission power does not exceed the total configured maximum output power (NO decision line), method <NUM> may proceed to end and the uplink power scheduling may proceed as normal (e.g. according to specification-defined uplink power methods and values). However, where the total desired transmission power exceeds the total configured maximum output power (YES decision line), method <NUM> may proceed to block <NUM>.

In an aspect, at block <NUM>, a processing apparatus may allocate a minimum proactive power limitation to each serving cell. In an aspect, the minimum proactive power limitation may be based on a minimum proactive power value, PCMIN,c. In a non-limiting aspect, PCMIN,c may be allocated to one or more uplink channels to ensure a non-zero uplink power allocation to each such channel. Furthermore, in an aspect, the minimum proactive power PCMIN,c can be computed such that, when allocated and applied, it may have a minor impact to total power limitation. In another non-limiting aspect, the minimum proactive power PCMIN,c can be set as the uplink power to meet the coverage of a small cell, and may comprise one value among a set of potential configurable values (e.g. 0dBm, 10dBm). Furthermore, allocating the minimum proactive power limitation to each serving cell may comprise allocating a first part of total power assignment in the uplink for a particular cell for a subframe i. In an additional aspect, this value can be configurable for network optimization adjustment purposes.

In addition, at block <NUM>, the minimum proactive power limitation value may be allocated based on priority, such as, but not limited to, a priority scheme that takes the form of PUCCH > PUSCH (with DCI) > PUSCH (without DCI), as described in reference to <FIG> above. Furthermore, the allocation of the minimum proactive power limitation may be performed according to the methods, equations, or techniques performed by minimum proactive power allocating module <NUM>, remaining power calculating module <NUM>, and/or any of the modules therein (see <FIG>).

In addition, at block <NUM>, a processing apparatus may assign remaining power to one or more channels based on priority. In an aspect, the assigning of block <NUM> may comprise a second part of a total transmission power for one or more uplink channels. As with the allocation at block <NUM>, the remaining power may be assigned to one or more channels based on priority, such as, but not limited to, a priority scheme that takes the form of PUCCH > PUSCH (with DCI) > PUSCH (without DCI), as described in reference to <FIG> above. Moreover, the allocation of the minimum proactive power limitation may be performed according to the methods, equations, or techniques performed by remaining power assigning module <NUM>, remaining power calculating module <NUM>, and/or any of the modules therein (see <FIG>).

In addition, at block <NUM>, a processing apparatus may compute a total power assignment based on the allocating and assigning of blocks <NUM> and <NUM>, respectively. In an aspect, at block <NUM>, the processing apparatus may compute total power assignments by combining and/or summing component (e.g. Part <NUM>, Part <NUM>, and so on) power allocation or assignment values for one or more channels, which may have been assigned, allocated, and/or stored at blocks <NUM> and/or <NUM> of method <NUM>. Additionally, once these total power assignments are computed at block <NUM>, the power allocation method <NUM> may end and the processing apparatus may transmit one or more messages via one or more channels according to the channels' unique total power assignments allocated or otherwise computed by method <NUM>.

<FIG> is a block diagram illustrating an example system <NUM> for improved uplink power management in a UE in accordance with some embodiments. For example, system <NUM> may reside at least partially within a UE (e.g. UE <NUM> of <FIG>), such as a UE or network entity (e.g. a network entity of PCell(s) <NUM> and/or SCell(s) <NUM> of <FIG>). It is to be appreciated that system <NUM> is represented as including functional blocks, which may be functional blocks that represent functions implemented by a processor, software, or combination thereof (e.g. firmware). System <NUM> includes a logical grouping <NUM> of electrical modules that may act in conjunction.

For instance, logical grouping <NUM> may include an electrical module <NUM> for determining whether a total desired transmission power exceeds a total configured maximum output power. In an aspect, electrical module <NUM> may comprise power comparison module <NUM> (<FIG>). Additionally, logical grouping <NUM> may include an electrical module <NUM> for allocating a minimum proactive power limitation to each serving cell. In an aspect, electrical module <NUM> may comprise minimum proactive power allocating module <NUM> (<FIG>). In an additional aspect, logical grouping <NUM> may include an electrical module <NUM> for assigning a remaining power to one or more channels based on priority. In an aspect, electrical module <NUM> may comprise remaining power assigning module <NUM> (<FIG>). Furthermore, logical grouping <NUM> may include electrical module <NUM> for computing a total power assignment. In an aspect, electrical module <NUM> may comprise total power assignment computing module <NUM> (<FIG>).

Additionally, system <NUM> may include a memory <NUM> that retains instructions for executing functions associated with electrical modules <NUM>, <NUM>, <NUM>, and <NUM>, stores data used or obtained by electrical modules <NUM>, <NUM>, <NUM>, and <NUM>, etc. While shown as being external to memory <NUM>, it is to be understood that one or more of electrical modules <NUM>, <NUM>, <NUM>, and <NUM> may exist within memory <NUM>. In one example, electrical modules <NUM>, <NUM>, <NUM>, and <NUM> may comprise at least one processor, or each electrical module <NUM>, <NUM>, <NUM>, and <NUM> may be a corresponding module or module of at least one processor. Moreover, in an additional or alternative example, one or more electrical modules <NUM>, <NUM>, <NUM>, and <NUM> may be a computer program product including a computer readable medium, where the respective electrical module <NUM>, <NUM>, <NUM>, and <NUM> may be corresponding code.

<FIG> is a block diagram illustrating a machine in the example form of a computer system <NUM>, within which a set or sequence of instructions for causing the machine to perform any one of the methodologies discussed herein may be executed, according to an example embodiment. In alternative embodiments, the machine operates as a standalone device or may be connected (e.g. networked) to other machines. In a networked deployment, the machine may operate in the capacity of either a server or a client machine in server-client network environments, or it may act as a peer machine in peer-to-peer (or distributed) network environments. The machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a mobile telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

Example computer system <NUM> includes at least one processor <NUM> (e.g. a central processing unit (CPU), a graphics processing unit (GPU) or both, processor cores, compute nodes, etc.), a main memory <NUM> and a static memory <NUM>, which communicate with each other via a link <NUM> (e.g. bus). The computer system <NUM> may further include a video display unit <NUM>, an alphanumeric input device <NUM> (e.g. a keyboard), and a user interface (UI) navigation device <NUM> (e.g. a mouse). In one embodiment, the video display unit <NUM>, input device <NUM> and UI navigation device <NUM> are incorporated into a touch screen display. The computer system <NUM> may additionally include a storage device <NUM> (e.g. a drive unit), a signal generation device <NUM> (e.g. a speaker), a network interface device <NUM>, and one or more sensors (not shown), such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor.

The storage device <NUM> includes a machine-readable medium <NUM> on which is stored one or more sets of data structures and instructions <NUM> (e.g. software) embodying or utilized by any one or more of the methodologies or functions described herein. The instructions <NUM> may also reside, completely or at least partially, within the main memory <NUM>, static memory <NUM>, and/or within the processor <NUM> during execution thereof by the computer system <NUM>, with the main memory <NUM>, static memory <NUM>, and the processor <NUM> also constituting machine-readable media.

While the machine-readable medium <NUM> is illustrated in an example embodiment to be a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g. a centralized or distributed database, and/or associated caches and servers) that store the one or more instructions <NUM>. The term "machine-readable medium" shall also be taken to include any tangible medium that is capable of storing, encoding or carrying instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present disclosure or that is capable of storing, encoding or carrying data structures utilized by or associated with such instructions. The term "machine-readable medium" shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media. Specific examples of machine-readable media include nonvolatile memory, including, by way of example, semiconductor memory devices (e.g. Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

The instructions <NUM> may further be transmitted or received over a communications network <NUM> using a transmission medium via the network interface device <NUM> utilizing any one of a number of well-known transfer protocols (e.g. HTTP). Examples of communication networks include a local area network (LAN), a wide area network (WAN), the Internet, mobile telephone networks, Plain Old Telephone (POTS) networks, and wireless data networks (e.g. Wi-Fi, <NUM>, and <NUM> LTE/LTE-A or WiMAX networks). The term "transmission medium" shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.

Examples, as described herein, may include, or may operate on, logic or a number of modules, modules, or mechanisms. Modules are tangible entities capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g. internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g. a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g. instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside (<NUM>) on a non-transitory machine-readable medium or (<NUM>) in a transmission signal.

Accordingly, the terms "module" and "module" are understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g. hardwired), or temporarily (e.g. transitorily) configured (e.g. programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, one instantiation of a module may not exist simultaneously with another instantiation of the same or different module. Accordingly, software may configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.

Claim 1:
An apparatus of user equipment (<NUM>), UE, the apparatus comprising: processing circuitry (<NUM>); and transceiver circuitry (<NUM>) controlled by the processing circuitry, the processing and transceiver circuitry being configured to:
configure the UE to concurrently communicate with a primary cell (<NUM>), PCell, and a secondary cell (<NUM>), SCell via associated channels;
when a total desired power exceeds a maximum power for a subframe:
allocate a minimum power for a scheduled uplink transmission to the channels associated with the SCell and the PCell;
allocate at least some remaining power to a scheduled uplink transmission to the PCell based on a priority of the scheduled uplink transmission when the scheduled uplink transmission to the SCell includes control information and when the scheduled uplink transmission to the SCell and the scheduled uplink transmission to the PCell are concurrent; and
transmit the scheduled uplink transmission to the SCell and the scheduled uplink transmission to the PCell in accordance with respective power allocations.