TWI533734B - Power headroom reporting for carrier aggregation - Google Patents

Description

Power headroom report for carrier aggregation

SUMMARY OF THE INVENTION The present invention relates to telecommunications systems, and in particular to methods, systems, apparatus, and software for power headroom reporting in a radio communication system.

Radio communication networks were primarily developed primarily to provide voice services over circuit-switched networks. The introduction of packet-switched bearers in, for example, so-called 2.5G and 3G networks enables network operators to provide data services as well as voice services. Finally, the network architecture will likely evolve toward an all-Internet Protocol (IP) network that provides both voice and data services. However, network operators have significant investments in existing infrastructure and will therefore tend to migrate gradually to an all-IP network architecture to allow them to extract sufficient value from investments in existing infrastructure. To provide the capabilities needed to support next-generation radiocommunication applications while using legacy infrastructure designs, network operators can deploy hybrid networks in which a next-generation radio system covers an existing circuit-switched or packet-switched network. As a first step in the transition to an all-IP-based network. Alternatively, a radio communication system can evolve from generation to generation while still providing retrospective compatibility for legacy devices.

An example of such an evolved network is based on the Universal Mobile Telephone System (UMTS), which is an existing third generation (3G) radio communication system that evolved into one of the High Speed Packet Access (HSPA) technologies. Yet another alternative is to introduce a new air interface technology within the UMTS framework, such as the so-called Long Term Evolution (LTE) technology. The target performance objectives of the LTE system include, for example, support for 200 active calls per 5 MHz cell and less than 5 millisecond delay for small IP packets. Each new generation or portion of the mobile communication system adds complexity and capabilities to the mobile communication system, and it is expected that this evolution will continue by enhancing the proposed system or a completely new system in the future.

LTE uses orthogonal frequency division multiplexing (OFDM) in the downlink and discrete Fourier transform (DFT)-spread OFDM in the uplink. The base LTE downlink entity resource can thus be considered as a time-frequency grid as illustrated in Figure 1, where each resource element corresponds to one OFDM subcarrier during one OFDM symbol interval. In the time domain, the LTE downlink transmissions are organized into 10 millisecond radio frames, each of which consists of ten equally sized _{subframes of} length _Tframe = 1 millisecond, as shown in FIG.

In addition, the resource allocation in LTE is usually described in units of resource blocks, where one resource block corresponds to one time slot (0.5 milliseconds) in the time domain and 12 subcarriers in the frequency domain. The resource block number is numbered from 0 at one end of the system bandwidth in the frequency domain. The downlink transmission is dynamically scheduled, that is, in each subframe, the base station (usually referred to as an eNB in LTE) transmits which terminals are transmitted to the terminal during the current downlink subframe and Control information on which resource blocks are transmitted. This control signal is typically transmitted in the first 1, 2, 3 or 4 OFDM symbols in each subframe. A downlink system having 3 OFDM symbols as one of the control regions is illustrated in FIG.

LTE uses a hybrid ARQ in which the terminal attempts to decode the downlink data in a subframe and reports to the base station whether the decoding was successful (ACK) or unsuccessful (NAK). In the case of an unsuccessful decoding attempt, the base station may retransmit the error data. Therefore, the uplink control signaling from the terminal to the base station consists of a hybrid ARQ response for the received downlink data; a terminal report related to the downlink channel condition, which is used as the downlink row Auxiliary (also known as Channel Quality Indication (CQI)); and scheduling request indicating that an active terminal requires uplink resources for uplink data transmission.

An uplink resource specifically allocated for uplink L1/L2 control information on a Physical Uplink Control Channel (PUCCH) if the mobile terminal has not been assigned one of the uplink resources for data transmission The L1/L2 control information (channel status report, hybrid ARQ response, and scheduling request) is transmitted in the (resource block). Different PUCCH formats are used for different information, for example, PUCCH format 1a/1b is used for hybrid ARQ feedback, PUCCH format 2/2a/2b is used for channel status reporting, and PUCCH format 1 is used for scheduling requests. In order to transmit data in the uplink, an active terminal has to be assigned an uplink resource for data transmission on the Physical Uplink Shared Channel (PUSCH). In the uplink, the assignment must always be frequency contiguous in comparison to one of the data assignments in the downlink to preserve the signal carrier nature of the uplink as illustrated in FIG. However, in LTE Rel-10, this constraint can be relaxed to enable discontinuous uplink transmission.

The intermediate single carrier symbol in each time slot is used to transmit a reference symbol. In the event that an uplink resource has been assigned to the mobile terminal for data transmission and the mobile terminal has control information to transmit, the control information will be transmitted with the data on the PUSCH. In Rel-10, simultaneous transmission of PUSCH and PUCCH in the same subframe is also supported.

Uplink power control is used on both the PUSCH and the PUCCH, that is, which power is transmitted to the base station by the mobile terminal. The goal is to ensure that mobile terminals transmit at a high enough but not too high power, because excessive power will increase interference with other users on the network. In both cases, one of the combined open loops is used in combination with a closed loop mechanism. Roughly, an open circuit portion is used to set an operating point around which the closed loop assembly operates. Different parameters (target and "partial compensation factor") are used for the user and the control plane.

Considering the uplink power control in more detail, the mobile terminal sets the output power for the PUSCH according to the following formula:

P _PUSCHc ( i )=min{ P _MAXc ,10log ₁₀ ( M _PUSCHc ( i ))+ P _{O_PUSCHc} ( j )+ α _c ‧ PL _c +Δ _TFc ( i )+ f _c ( i )}[dBm],

Where P _MAXc is the maximum transmission power of the carrier, M _PUSCHc ( i ) is the number of resource blocks assigned, P _{O_PUSCHc} ( j ) and α _c control the target received power, PL _c is the estimated path loss, Δ _TFc ( i ) Transport format compensation and f _c ( i ) is a UE-specific offset or "closed loop correction" (function f _c may represent absolute or cumulative offset). The indicator c is assigned to the component carrier and is only related to carrier aggregation. PUCCH power control has a similar description.

Closed loop power control can operate in two different modes (cumulative or absolute). Both modes are based on TPC, which is one of the commands that are part of the downlink control signaling. When absolute power control is used, the closed loop correction function is reset each time a new power control command is received. When cumulative power control is used, the power control command is corrected for one of the differential corrections of the closed loop that was previously accumulated. The cumulative power control command is defined as f _c ( i )= f _c ( i -1)+ δ _PUSCHc ( i - K _PUSCH ), where δ _PUSCHc is received in the K _PUSCH subframe before the current subframe i The TPC command, and f _c ( i -1) is the cumulative power control value. Absolute power control does not have memory, ie f _c ( i ) = δ _{P USCHc} ( i - K _PUSCH ). The PUCCH power control has in principle the same configurable parameters, but the PUCCH only has full path loss compensation, ie only covers the case of α =1.

In LTE Rel-10, the base station can configure the UE to transmit a power headroom report associated with the PUSCH periodically or when the path loss changes beyond a configurable threshold. The power headroom report indicates how much transmission power the UE leaves for a subframe i, that is, the difference between the nominal UE maximum transmission power and the estimated required power. The reported values are in the range of 40 to -23 dB, with a negative value indicating that the UE does not have sufficient power to direct the transmission. The UE power headroom PH _c (in dB) of subframe i is defined as:

PH _c ( i )= P _CMAXc -{10log ₁₀ ( M _PUSCHc ( i ))+ P _{O_PUSCHc} ( j )+ α _c ( j ) ‧ PL _c +Δ _TFc ( i )+ f _c ( i )} (1)

Wherein P _CMAXc , M _PUSCHc ( i ), P _{O_PUSCHc} ( j ), α _c ( j ), PL _c , Δ _TFc ( i ), and f _c ( i ) are as defined above.

In the case where the PUCCH and the PUSCH can be simultaneously transmitted, it is also possible to implement the PUCCH Split Power Headroom Report (PHR). In these cases, either a separate PHR (in dB) is provided for the PUCCH.

Or its combination with PUSCH (in dB)

The parameter definitions associated with these equations are specified above.

The LTE Rel-8 standard is currently standardized to support bandwidths up to 20 MHz. However, to meet the advanced IMT needs of the uplink, 3GPP has initiated work on LTE Release 10. One aspect of LTE REL-10 supports a larger bandwidth than 20 MHz in one way to ensure backward compatibility with LTE Rel-8/9, including spectral compatibility. This means that one LTE Rel-10 carrier that is wider than 20 MHz should appear as a large number of LTE carriers for an LTE Rel-8/9 terminal. Each such carrier can be referred to as a component carrier (CC). A component carrier is also referred to as a cell, and more specifically, a basic component carrier is referred to as a basic cell or a P-cell, and a secondary component carrier is referred to as a secondary cell or an SCell.

For the early LTE Rel-10 deployment, it is expected that there will be a smaller number of operations with LTE Rel-10 capable terminals rather than a large number of operating LTE legacy terminals. Therefore, it is desirable to ensure that a wide carrier is also effectively utilized for legacy terminal devices, i.e., it is possible to implement a carrier in which legacy terminal devices can be scheduled in all portions of the wideband LTE advanced carrier. One way to achieve this goal is by means of carrier aggregation (CA). Carrier aggregation means, for example, that an LTE Rel-10 terminal can receive multiple component carriers, where the component carriers have, or at least possibly have the same structure as a Rel-8 carrier. One example of carrier aggregation is illustrated in Figure 5, where five 20 MHz component carriers 10 are aggregated to form a single wideband carrier.

The number of aggregated CCs and the bandwidth of individual CCs may be different for the uplink and downlink. A symmetric configuration refers to a situation in which the number of CCs in the downlink and the uplink is the same, and an asymmetric configuration refers to a case in which the number of CCs is different. It is worth noting that the number of CCs configured in a cell area can be different from the number of CCs seen or used by a terminal: for example, even if the network configuration has the same number of uplinks and downlinks Road CC, but a terminal can support more downlink CC than the uplink CC.

Applying the LTE Rel-8 framework for power headroom reporting, for example in LTE Rel-10, to carrier aggregation will mean transmitting one of the component carriers PHR on a particular component carrier itself. Furthermore, it is not clear whether a PHR will be transmitted on only one component carrier if the terminal has a PUSCH resource granted on a component carrier. In RAN2, it is proposed to extend this architecture such that the PH of one component carrier can be transmitted on another component carrier. This will enable reporting of fast path loss changes on one component carrier as long as the terminal has PUSCH resources granted on any configured UL component carrier. More specifically, a path loss change of more than one dl-PathlossChange dB on any component carrier triggers transmission of a PHR on the (the same or another) component carrier to which the terminal has the PUSCH resources granted thereto. .

However, such mechanisms for power headroom reporting in systems employing carrier aggregation suffer from some potential drawbacks. For example, the calculation of PHR is closely related to a given PUSCH format. Therefore, one of the component carriers that do not have a PUSCH resource, PHR, cannot be determined due to the lack of a valid PUSCH format. This also applies to a PUCCH PHR. Accordingly, it would be desirable to provide methods, systems, devices, and software for addressing such potential deficiencies.

The power headroom reporting and reporting process is one of the physical uplinks (PUs) in which the previous user equipment (UE) does not have a valid uplink grant and the previous UE does not have one of the physical uplinks. Discussed in the context of Control Channel (PUCCH). In such an environment, it is not possible to directly calculate one or more parameters for calculating the power headroom. Accordingly, the exemplary embodiments provide predetermined, known values to be used by the UE to calculate the power headroom and to understand the meaning of a received power headroom report by the eNodeB.

According to a first exemplary embodiment, a component carrier for a previous user equipment (UE) for a physical uplink shared channel (PUSCH) without a valid uplink grant is carried out in a radio communication system The method of power headroom reporting includes the step of using, by the UE, at least one parameter associated with the PUSCH to calculate at least one parameter of a power headroom of the component carrier on which the UE does not have a valid uplink grant. The known value calculates the power headroom because one of the values for the at least one parameter is not available, wherein the at least one known value is one of the known values of the UE and the UE connected to one of the eNodeBs, wherein The at least one parameter comprises at least one of: (a) M _PUSCHc ( i ) indicating the number of resource blocks assigned to the PUSCH on the component carrier when the UE has a valid uplink grant, (b) Δ _TFc ( i ), which represents one of transport format compensation associated with the PUSCH on the component carrier when the UE has a valid uplink grant, and (c) δ _PUSCHc ( i - K _PUSCH ) table Transmitting a power control command associated with a PUSCH on the component carrier when the UE has a valid uplink grant; and transmitting a power headroom report by the UE based on the calculated power headroom.

According to a second exemplary embodiment, a User Equipment (UE) includes: a processor configured to operate with the following steps for the UE not having a Physical Uplink Shared Channel (PUSCH) for the UE One of the component carriers during a valid mode grant performs a power headroom report: using a power headroom associated with the PUSCH to calculate one of the component carriers on which the UE does not have a valid uplink grant Calculating the power headroom by at least one known value of at least one parameter, because one of the values for the at least one parameter is not available, wherein the at least one known value is that the UE and the UE are connected to one of the eNodeBs One value is known, wherein the at least one parameter comprises at least one of: (a) M _PUSCHc ( i ) indicating a resource region assigned to the PUSCH on the component carrier when the UE has a valid uplink grant The number of blocks, (b) Δ _TFc ( i ), which represents one of the transport format compensation associated with the component carrier when the UE has a valid uplink grant, and (c) δ _PUSCHc ( i - K _PUSCH ) ,its It shows when the UE has a valid uplink transmission power with one of the component carriers associated with the granted link control command; and a transceiver for transmitting a power headroom report has been configured based on the calculated power headroom.

According to a third exemplary embodiment, a method for performing power margin in a radio communication system for a previous user equipment (UE) on a physical uplink control channel (PUCCH) without a component carrier of a current transmission The method of spatial reporting comprises the step of using, by the UE, at least one of at least one parameter associated with the PUCCH to calculate at least one of a power headroom of the component carrier on which the UE does not have transmissions on the PUCCH is known. Calculating the power headroom value because one of the values for the at least one parameter is not available, wherein the at least one known value is one of a value known to the UE and the UE is connected to one of the eNodeBs, wherein the at least one value A parameter includes at least one of: (a) h _c ( n _CQI , n _HARQ ), which represents a certain number of control information bits transmitted on the PUCCH on the component carrier when the UE has a transmission on the PUCCH a quantity of power adapted by the element, (b) Δ _{F_PUCCHc} ( F ), which represents a relative performance difference between the PUCCH format 1a and the PUCCH on the component carrier when the UE has a transmission on the PUCCH, and c) δ _{PU CCHc} ( i - k _m ) indicating a transmission power control command associated with the PUCCH on the component carrier when the UE has a transmission on the PUCCH; and transmitting a power margin by the UE based on the calculated power headroom Spatial report.

According to a fourth exemplary embodiment, a User Equipment (UE) includes: a processor configured to have no current physical uplink control channel for a previous User Equipment (UE) by the following steps (PUCCH) transmission of one component carrier to perform power headroom reporting: using at least one parameter associated with the PUCCH to calculate at least one parameter of a power headroom of the component carrier on which the UE does not have PUCCH transmission is known Calculating the power headroom value because one of the values for the at least one parameter is not available, wherein the at least one known value is one of a value known to the UE and the UE is connected to one of the eNodeBs, wherein the at least one value A parameter includes at least one of: (a) h _c ( n _CQI , n _HARQ ), which represents a power adapted by a certain number of bits transmitted on the component carrier when the UE has a transmission on the PUCCH. One quantity, (b) Δ _{F_PUCCHc} ( F ), which represents between the PUCCH format 1a and at least one known value of at least one parameter of the PUCCH associated with the component carrier when the UE has a transmission on the PUCCH Relative performance a difference, and (c) δ _PUCCHc ( i - k _m ), which represents a transmission power control command associated with the component carrier when the UE has a transmission on the PUCCH; and a transceiver configured to A power headroom report is transmitted based on the calculated power headroom.

According to a fifth exemplary embodiment, a component carrier for a user equipment (UE) for a physical uplink shared channel (PUSCH) that does not have a valid uplink grant is performed in a radio communication system The method of power margin reporting disposition includes the steps of: receiving, by an eNodeB, a power headroom report of a component carrier on which the UE does not have a valid uplink grant, wherein at least one parameter associated with the PUSCH is used Calculating the power headroom report by at least one known value because one of the at least one parameter values cannot be obtained, wherein the at least one known value is one of a value known to the UE and the eNodeB, wherein the at least one A parameter includes at least one of: (a) M _PUSCHc ( i ) indicating the number of resource blocks assigned to the PUSCH on the component carrier when the UE has a valid uplink grant, (b) ) Δ _TFc (i), which indicates when the UE has a valid uplink PUSCH associated with one of the transport format of the component carrier compensation link grant, and _{(c) δ PUDCHc (i -} K PUSCH), It indicates when the UE has a valid uplink grant associated with the PUSCH transmission power of one of the component carrier related to the control command.

According to a sixth exemplary embodiment, an eNodeB includes: a processor configured to receive one of physical uplink shared channels (PUSCH) during a mode in which one UE does not have a valid uplink grant a power headroom report of one of the component carriers, wherein the power headroom report is calculated by using at least one known value of at least one parameter associated with the PUSCH, because one of the values for the at least one parameter cannot be obtained And wherein the at least one known value is one of a value known to the UE and the _eNodeB , wherein the at least one parameter comprises at least one of: (a) M _PUSCHc ( i ), indicating that the UE has The number of one of the resource blocks assigned to the PUSCH on the component carrier when a valid uplink grant, (b) Δ _TFc ( i ), which indicates that the UE has a valid uplink grant associated with the component carrier a transport format compensation, and (c) δ _PUSCHc ( i - K _PUSCH ), which represents a transmission power control command associated with the component carrier when the UE has a valid uplink grant; and a transceiver Group The state transmits an uplink power control power margin command based on the power headroom report.

According to a seventh exemplary embodiment, a power margin is used in a radio communication system for a previous user equipment (UE) that does not have a component carrier of a current transmission on a Physical Uplink Control Channel (PUCCH) A method of spatial report disposition, the method comprising the steps of: receiving, by an eNodeB, a power headroom report of a component carrier on which the UE does not have a transmission on the PUCCH, wherein at least one parameter associated with the PUCCH is used Calculating the power headroom report by at least one known value because one of the values for the at least one parameter is not obtainable; wherein the at least one known value is one of a value known to the UE and the eNodeB, wherein the At least one parameter comprises at least one of: (a) h _c ( n _CQI , n _HARQ ), which represents a certain number of transmissions on the PUCCH on the component carrier when the UE has a transmission on the PUCCH the amount of power control adjustment of one of the information _{bits, (b) Δ F_PUCCHc (F} ), which represents between PUCCH format 1a and on the component carriers when the UE has between a transmission on the PUCCH in Relative potency difference, and _{(c) δ PUCCHc (i -} k m), which indicates when the UE has transmitted a PUCCH on one of the associated PUCCH transmission power associated with the component carrier of the control command.

According to an eighth exemplary embodiment, an eNodeB includes: a processor configured to have no component of a current physical uplink control channel (PUCCH) transmission for a previous user equipment (UE) thereof The carrier receives a power headroom report, wherein the power headroom report is calculated using at least one known value of at least one parameter associated with the PUCCH, because one of the values for the at least one parameter cannot be obtained, wherein the at least one The known value is one of the values known to the UE and the eNodeB, wherein the at least one parameter comprises at least one of: (a) h _c ( n _CQI , n _HARQ ), which indicates when the UE is The PUCCH has an amount of power adapted to a certain number of bits transmitted on the component carrier during transmission, (b) Δ _{F_PUCCHc} ( F ), which indicates that when the UE has a transmission on the PUCCH a relative performance difference between the reference format of the PUCCH 1a and the PUCCH associated with the component carrier, and (c) δ _PUCCHc ( i - k _m ) indicating that when the UE has a transmission on the PUCCH One of the component carriers associated with transmission power control Order; and a transceiver configured to warp based on the power headroom report an uplink transmission power control commands.

Abbreviation/abbreviation

ACK positive response

ARQ automatic repeat request

CA carrier aggregation

CC component carrier

CQI channel quality indicator

DFT discrete Fourier transform

eNB see eNodeB

eNodeB evolved Node B

LTE long-term evolution

NAK/NACK negative response

PH power margin

PHR Power Headroom Report

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

RAN radio access network

TPC transmission power control

The example embodiments set forth below are understood in conjunction with the drawings presented herein.

The following detailed description of the exemplary embodiments is set forth in the accompanying drawings. The same reference numbers in different figures identify the same or similar elements. Moreover, the following detailed description does not limit the invention. Rather, the scope of the invention is defined by the scope of the accompanying claims. For simplicity, the following embodiments are discussed with reference to the terms and structures of the LTE system. However, the embodiments to be discussed next are not limited to the LTE system, but are applicable to other telecommunication systems.

A reference to "one embodiment" or "an embodiment" is intended to mean that a particular feature, structure, or characteristic is described in connection with an embodiment. The phrase "in one embodiment" or "in an embodiment" or "an" Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

To provide some context for the following example embodiments regarding power headroom reporting and associated bursts, consider the example radio communication systems shown in two different perspective views, respectively, as in Figures 6 and 7. To increase the transmission rate of the system and provide additional versatility relative to the degradation on the radio channel, modern wireless communication systems include transceivers that use multiple antennas (commonly referred to as a MIMO system). Multiple antennas may be distributed to the receiver side, distributed to the transmitter side, and/or provided on both sides as shown in FIG. More specifically, FIG. 6 shows a base station 32 having one of four antennas 34 and a user terminal (also referred to herein as "user equipment" or "UE") 36 having two antennas 34. The number of antennas shown in FIG. 6 is merely exemplary and is not intended to limit the actual number of antennas used at base station 32 or at user terminal 36 in the exemplary embodiments discussed below.

In addition, the term "base station" is used herein as a generic term. As will be appreciated by those skilled in the art, in an LTE architecture, an evolved Node B (eNodeB) may correspond to a base station, that is, a base station may be one of the eNodeBs. However, the term "eNodeB" is also broader in some sense than the conventional base station, since eNodeB generally refers to a logical node. The term "base station" is used herein to include a base station, a Node B, an eNodeB, or other nodes dedicated to other architectures. An eNodeB in an LTE system handles transmissions and receptions in one or several cells, as shown, for example, in FIG.

Figure 7 shows, among other things, two eNode Bs 34 and one user terminal 36. The user terminal communicates with the eNodeB 34 using a dedicated channel 40, such as by transmitting or receiving RLC PDU segments, as in accordance with the exemplary embodiments described below. Two eNode Bs 34 are connected to a corresponding Radio Network Controller (RNC) 42. Although not shown in Figure 7, it should be understood that each RNC 42 can control more than one eNodeB 32. The RNC 42 is connected to a core network 44. In some networks (eg, LTE), the RNC is omitted.

An example LTE architecture for processing data transmitted by an eNodeB 34 to a UE 36 (downlink) is shown in FIG. Wherein, the data transmitted by the eNodeB 34 (e.g., IP packet) to a particular user is first processed by a Packet Data Convergence Agreement (PDCP) entity 50, where (optionally) the IP header is compressed and the data is encrypted. . The Radio Link Control (RLC) entity 52 also processes, for example, segments (and/or concatenation connections) of data received from the PDCP entity 50 into the Protocol Data Unit (PDU). In addition, RLC entity 52 provides a Retransmission Protocol (ARQ) that monitors the sequence number status report from its corresponding body RLC entity in UE 36 to selectively retransmit the PDU upon request. Media Access Control (MAC) entity 54 is responsible for uplink and downlink scheduling via scheduler 56, as well as the hybrid ARQ process discussed above. A physical (PHY) layer entity 58 is responsible for, among other things, coding, modulation, and multi-antenna mapping. Each entity shown in Figure 8 provides the output of its neighboring entity and the input from its neighboring entity using the bearer or channel shown. The reversal of such processes is provided for the UE 36 as shown in FIG. 8 for the received data, and the UE 36 also has similar transmission chain elements as the eNB 34 for transmission on the uplink towards the eNB 34.

Having described certain example LTE devices in which several aspects of power headroom reporting in accordance with an example embodiment may be implemented, reference will now be made to the consideration of power headroom reporting in the context of carrier aggregation. As mentioned above, previous system implementations do not yet need to incorporate carrier aggregation to consider power headroom reporting, where carrier aggregation refers to multiple CCs having different frequency and frequency bandwidths per UE. For example, a decision can be made as to when to send a PHR (ie, a power headroom report triggered by the UE). As a background, in LTE Rel-8/9, the following PHR related parameters can be configured per UE: prohibitPHR-Timer, periodPHR-Timer, and dl-PathlossChange. In Rel-8/9, a PHR report is formed when the periodPHR-Timer expires or when the prohibitPHR-Timer expires and the change in the measured DL path loss exceeds the dl-PathlossChange threshold since the transmission of the previous PHR One of the available PUSCH grants is sent in one TTI. A PHR report should also be sent in case of a higher level (re)configuration of the PHR reporting function.

In LTE Rel-10, where there may be multiple CCs with different frequency and frequency bandwidths per UE, the radio quality and path loss will most likely be different between different CCs. However, even if the path loss may be different between different CCs, it may not be beneficial to compare each CC path loss with a different path loss change threshold in the case of determining whether a PHR should be transmitted when the prohibit PHR-Timer expires. . In addition, there may be no benefit to justify prohibitPHR-Timer and periodicPHR-Timer with per-CC configuration. Thus, according to an exemplary embodiment, the trigger variables associated with when a UE makes its power headroom report for an eNB (ie, prohibitPHR-Timer, periodicPHR-Timer, and dl-PathlossChange) may be the same as Triggering variables for all CCs associated with a user device (ie, per UE). Another option is that for a particular UE, some or all of these variables may differ from CC to CC.

The exemplary embodiment considers the content of the PHR in addition to when the PHR is sent from one UE to one eNB. In LTE Rel-8/9, as long as the UE has an available PUSCH grant, there is no uncertainty about the PHR content, because there is only one carrier for when the periodic PHR timer has expired or when the prohibit PHR-Timer The PHR is reported when the DL path loss change over time has exceeded the dl-pathlossChange threshold. For systems that include carrier aggregation, when deciding which UL CC is to provide PHR information to the eNB, the following different options have been identified for determining which UL CC PHR should be reported when each individual PHR timer expires. News.

When prohibitPHR-Timer expires:

‧ Only for UL CC transmission PHR where the corresponding active DL CC has exceeded the dl-pathlossChange threshold and the UE has an available UL PUSCH grant.

‧ Transmit PHR for all UL CCs in which the corresponding active DL CC has exceeded the dl-pathlossChange threshold.

‧ In the case where at least one active DL CC has exceeded the dl-PathlossChange threshold, the PHR is transmitted only for UL CCs with a corresponding active DL CC and an available PUSCH grant.

‧ Transmit PHR for all UL CCs with a corresponding active DL CC if at least one active DL CC has exceeded the dl-PathlossChange threshold.

When periodPHR-Timer expires:

‧ PHR is only transmitted for UL CCs with a corresponding active DL CC and an available PUSCH grant.

‧ Transmit PHR for all UL CCs with a corresponding active DL CC.

In the case of implementing the initiation of a UL SCC, it may be beneficial to allow PHR transmission for any active UL CC even if there is no available PUSCH grant. This may be meaningful because it can be assumed that the eNB has activated the UL CC for the purpose of utilizing the channel, and even if a specific grant has not been given for that particular TTI, the eNB will therefore want to have one of the channels of the PHR Report to fully understand the power situation. In addition, it may also be desirable for the UE to transmit a PHR even for its UL CCs whose corresponding active DL CCs have not exceeded the threshold to provide a full power state to the eNB. Thus, according to an exemplary embodiment, the UE should always report the PHR for all activated UL CCs regardless of how a PHR system is triggered. According to other example embodiments, the UE may report the PHR only for one or more of the situations discussed above.

However, in the absence of available PUSCH grants, the information needed to calculate the PHR is not always available. Thus, in accordance with an exemplary embodiment, to implement a PHR of a component carrier in the absence of a valid PUSCH grant, a predetermined PUSCH format may be used. In the case where both the eNodeB and the terminal are aware of the same PUSCH reference configuration (eg, configured by the network or standardized), the power headroom based on a desired PUSCH format can be weighted in the eNodeB. Calculated and used for future scheduling decisions. Alternatively, other example embodiments reuse the PUSCH format of the component carrier carrying the PHR (instead of a reference PUSCH format) as a reference. In addition to the PUSCH format, the current state of the power control loop also affects the PHR. According to an example embodiment, the respective states of the PUSCH and PUCCH power control loops on the component carriers that are generating the PHR may be used for PUSCH and PUCCH PHR. One of the PHR analysis for component carrier c of equation (1) set forth in the prior art section above shows that the parameters can be classified into the following groups:

1. Dependent on the parameters of the PUSCH format. The parameters M _PUSCHc ( i ) and Δ _TFc ( i ) belong to this category. These parameters are not available on a component carrier that does not have a granted PUSCH resource.

2. Power control loop parameters. The current state of the power control loop is given by the parameter f _c ( i ). For absolute power control loops and cumulative power control loops, these states can be expressed as: f _c ( i )= δ _PUSCHc ( i - K _PUSCH ) and f _c ( i )= f _c ( i -1)+ δ _PUSCHc ( i - K _PUSCH ). δ _PUSCHc ( i - K _PUSCH ) is a TPC command received under UL grant. However, on a component carrier that does not have a UL grant, δ _PUSCHc ( i - K _PUSCH ) is not available.

3. Component carrier specific parameters. P _CMAXc , P _{O_PUSCHc} ( j ), and α _c ( j ) are given by higher layers. PL _c is the path loss associated with component carrier c . As can be seen from these categories, the parameters M _PUSCHc ( i ), Δ _TFc ( i ), and δ _PUSCHc ( i - K _PUSCH ) are not available on a component carrier that does not have a valid UL grant. To enable PH calculation and subsequent reporting for a component carrier c that does not have a valid UL grant, the example embodiment replaces these unknown parameters with values known to both the eNodeB and the terminal. The resulting PHR value allows the eNodeB to determine the power headroom that will occur if a certain PUSCH format is given.

According to a first exemplary embodiment, one of the known ones of the eNodeB and the terminal is defined to reference the PUSCH format and used by the terminal to calculate the PH of a component carrier c that does not have a UL grant. This reference format may contain _values for M _PUSCHC ( i ), Δ _TFc ( i ), and δ _PUSCHc ( i - K _PUSCH ), for example

M _PUSCHc ( i )=10, or another selection system, equal to 1,

Δ _TFc ( i )=0 dB, and

δ _PUSCHc ( i - K _PUSCH ) = 0 dB.

It will be appreciated that the aforementioned numerical values of such parameters are purely illustrative. The reference format parameter values may be values fixed to or from the network to the UE as defined in the standard. Alternatively, other parameters may be provided in a reference configuration that implements the calculation of M _PUSCHc ( i ), Δ _TFc ( i ), and δ _{P USCHc} ( i - K _PUSCH ).

According to a second exemplary embodiment, the parameters M _PUSCHc ( i ), Δ _TFc ( i ) and δ _PUSCHc ( i - K _PUSCH ) are obtained from a component carrier c ', which is for example transmitted for transmission a component carrier or an uplink base component carrier (ULPCC) reported for the power headroom of the component carrier c, that is,

M _PUSCHc ( i )= M _PUSCHc' ( i ),

Δ _TFc ( i )=Δ _TFc' ( i ), and

δ _PUSCHc ( i - K _PUSCH ) = δ _{PUSCHc '} ( i - K _PUSCH ).

According to a third exemplary embodiment, some of these otherwise unknown parameters are obtained from a reference configuration, and some parameters are derived from component carriers used to transmit power headroom reports for component carrier c decisions. c 'acquired. An example of this technique may be to reuse M _PUSCHc' ( i ) from component carrier c ', and use Δ _TFc ( i ) and δ _PUSCHc ( i - K _PUSCH ) from a reference configuration, for example

M _PUSCHc ( i )= M _PUSCHc' ( i ),

Δ _TFc ( i )=0 dB, and

δ _PUSCHc ( i - K _PUSCH ) = 0 dB.

In a fourth exemplary embodiment, the parameters M _PUSCHc ( i ), Δ _TFc ( i ), and δ _PUSCHc ( i - K _PUSCH ) are obtained from a previous PUSCH transmission/grant, where the previous PUSCH transmission/grant can be tied to the component CarrierSCH or one of the component carriers c ' is transmitted/granted, where the component carrier c ' is, for example, used to transmit a component carrier or uplink base component carrier (UL) for the power headroom report determined for component carrier c PCC). Another option is that c ' has the component of the last PUSCH transmission/grant. Where multiple UL component carriers have grants/transmissions in the same subframe, this may be combined with another rule, such as using the component carrier that will now be used for power headroom reporting.

In a fifth exemplary embodiment, the UE reports a special predefined value as the PUSCH PH of component carrier c, indicating the power headroom from one of the previous PUSCH PH reports on component carrier c but no data. The eNB will adjust the previous received PUSCH PH report by adding the data power distribution from the previous received PUSCH PH.

A power headroom report for a system employing carrier aggregation in accordance with an example embodiment may also be provided for PUCCH as well as PUSCH. For example, by applying the same category as used above for equation (1) to equation (2) for PUCCH PH, the following classifications are obtained:

1. Dependent on the parameters of the PUCCH format. The parameters h _c ( n _CQI , n _HARQ ) and Δ _{F_PUCCHc} ( F ) fall into this category. These parameters are not available on a component carrier that does not have a PUCCH transmission. More specifically, the parameter Δ _{F_PUCCHc} ( F ) defines a relative performance difference between PUCCH 1a and PUCCH format F. This parameter is cell-specific messaging and should account for different receiver implementations of different PUCCH formats. The parameter h _c ( n _CQI , n _HARQ ) adapts the power to the number of control information bits transmitted. This is 0 dB for PUCCH 1a/1b, so the equivalent format only supports one payload size for this format. However, for PUCCH format 2/2a/2b, it scales power by the number of transmitted bits.

2. Power control loop parameters. The current state of the power control loop is given by the parameter g _c ( i ), which is defined as: . δ _PUCCHc ( i - k _m ) should be applied to the TPC command for PUCCH transmission. Without PUCCH transmission, δ _PUCCHc ( i - k _m ) is not available.

3. Component carrier specific parameters. P _CMAXc and P _{O_PUCCHc} are given by higher layers. PL _c is the path loss associated with component carrier c . On a component carrier that does not have a current PUCCH transmission, h _c ( n _CQI , n _HARQ ), Δ _{F_PUCCHc} ( F ), and δ _PUCCHc ( i - k _m ) are not available. In order to implement PH calculation and subsequent reporting for a component carrier c that does not have a current PUCCH transmission, these parameters may be replaced by values known by both the eNodeB and the terminal in the calculation. The resulting PHR value allows the eNodeB to determine the power headroom that will occur if a PUCCH transmission is given.

According to a sixth exemplary embodiment, a reference format of a PH known by both the eNodeB and the terminal and used by the terminal to calculate a component carrier c that does not have a PUCCH transmission is defined. This reference format can obtain values for h _c ( n _CQI , n _HARQ ), Δ _{F_PUCCHc} ( F ), and δ _PUCCHc ( i - k _m ). The reference format parameter values may be fixed values defined in the standard, or values transmitted from the network to the UE. Another option is to provide additional parameters in a reference configuration that implements the calculation of h _c ( n _CQI , n _HARQ ), Δ _{F_PUCCHc} ( F ), and δ _PUCCHc ( i - k _m ).

According to a seventh exemplary embodiment, the parameters h _c ( n _CQI , n _HARQ ), Δ _{F_PUCCHc} ( F ) and δ _PUCCHc ( i - k _m ) are obtained from a previous PUCCH transmission, wherein the previous PUCCH transmission may be In a current PUCCH transmission on one of the component carriers c whose PH is to be determined, or one of the current PUCCH transmissions on the component carrier c ', the component carrier c ' may, for example, be used for component carrier or uplink of PH transmission Basic component carrier (UL PCC).

According to an eighth exemplary embodiment, some of these otherwise unknown parameters are obtained from a reference configuration, and some of these parameters are obtained from the last PUCCH transmission.

The foregoing exemplary embodiments independently consider the PHR of PUSCH and PUCCH. These embodiments can be used alone or together. For example, according to another exemplary embodiment, a PHR may be generated for one of the component carriers c that does not have a current PUCCH transmission and/or a valid UL grant, and is required to supply M _PUSCHc ( i ), Δ _TFc ( i ) δ _PUSCHc ( i - K _PUSCH ), h _c ( n _CQI , n _HARQ ), Δ _{F_PUCCHc} ( F ), and δ _PUCCHc ( i - k _m ). In the case of a valid parameter set for PUSCH or PUCCH, only a subset of the enumerated parameters need to be provided. The provision of PUSCH and PUCCH parameters can be accomplished in accordance with any of the methods provided above.

The foregoing example embodiments discuss in part when to send PHR reports and what content they may contain. According to other example embodiments, the manner in which their reports are sent to the eNB may be considered. There are at least two options on how to report a PHR: including the PHR to the MAC PDU on the UL CC it is reporting, or allowing the PHR to be sent on any UL CC. A less complex solution would probably be to send a PHR only on the CC it is reporting. However, with this solution, in order to be able to send PHR, the UE will need to transmit on all UL CCs, even if there is not enough data to fill all UL CC grants.

Allowing the UE to transmit the PHR on any CC is slightly more complicated, but still beneficial, as it will give a more flexible UE implementation and may save some RLC segmentation when building the MAC PDU. It would be beneficial to MAC multiplex when the amount of data available for transmission is suitable for a subset of available UL grants, since PHR is not required to be transmitted on UL CCs that are otherwise empty. Moreover, in the case where the UE may transmit a PHR report for a UL CC with a current corresponding DL CC but no PUSCH grant, it may not be possible to constrain the PHR to transmit only on the corresponding CC. In order for the eNB to be able to map the received PHR to a particular CC, a seemingly uncomplicated solution would be to extend the MAC CE by indicating which CC the one of the CCs belongs to. Thus, according to an exemplary embodiment, PHR reporting is allowed to be transmitted on any UL CC, although the invention does not exclude the possibility of limiting the transmission of PHR on UL CCs associated with the PHR.

An exemplary base station 32 (e.g., an eNodeB) is illustrated in FIG. 9, which receives a power headroom report from UE 36 and is based in part on a power headroom report as input to a scheduler 56. Transfer data. Among them, the eNodeB 32 includes one or more antennas 71 connected to the processor 74 via the transceiver 73. Processor 74 is configured to analyze and process signals received over an empty interfacing plane via antenna 71 and to receive such signals from a core network node (e.g., an access gateway) via, for example, an S1 interface. Processor 74 can also be coupled to one or more memory devices 76 via a bus 78. As will be appreciated by those skilled in the art, further means or functions (not shown) for performing various operations such as encoding, decoding, modulating, demodulating, encrypting, scrambling, precoding, etc. may be implemented not only as appropriate It is an electronic component and is implemented in software or a combination of the two possible to enable transceiver 72 and processor 74 to process uplink and downlink signals. A similar, general purpose structure (e.g., including a memory device, one or more processors, and a transceiver) can be used to implement a communication node, such as UE 36, among other things.

An example embodiment implements a PH report for component carriers that do not have valid PUSCH resources and/or PUCCH transmissions. In the case of fast path loss changes, it is advantageous to provide this information to the eNodeB as soon as possible rather than waiting for the effective UL resources on the affected UL component carrier. To better understand how these embodiments can be used to influence the calculations performed for Power Headroom Reporting (PHR), consider the following. The so-called Type 1 PHR (in dB) can be calculated using the following equations when PUSCH transmission occurs:

PH _type1,c ( i )= P _{CMAX, c} ( i )-{10log ₁₀ ( M _PUSCH,c ( i ))+ P _{O_PUSCH,c} ( j )+ α _c ( j ) ‧ PL _c +Δ _TF,c ( i )+ f _c ( i )}

However, when the real PUSCH transmission is not available to the UE, the Type 1 PHR may be calculated by the UE using a predetermined known value instead of the like, for example:

‧ M _PUSCHc ( i )=1(10log ₁₀ ( M _PUSCH,c ( i ))=0)

‧ Δ _TFc ( i )=0

‧ δ _PUSCHc ( i - K _PUSCH )=0

This has the effect of reducing the first equation to the following equation:

PH _type1,c ( i )= P _{CMAX, c} ( i )-{ P _{O_PUSCH,c} ( j )+ α _c ( j )‧ PL _c + f _c ( i )}.

Similarly, for the so-called Type 2 PHR (in dB), the power headroom can be calculated by the following equation when real PUSCH and PUCCH transmissions occur:

Another option is that type 2 PHR does not have real PUSCH transmission (ie, using the PUSCH reference format).

‧ M _PUSCHc ( i )=1(10log ₁₀ ( M _PUSCH,c ( i ))=0)

‧ Δ _TFc ( i )=0

‧ δ _PUSCHc ( i - K _PUSCH ) = 0, thus reducing the latter program to:

Similarly, in the absence of a real PUCCH transmission, the following known values can be used, for example, to calculate the Type 2 PHR:

‧ h _c ( n _CQI , n _HARQ )=0

‧ Δ _{F_PUCCHc} ( F )=0

‧ δ _PUCCHc ( i - k _m )=0

‧ Δ _{T xD} ( F )=0, resulting in the reduction of the first PHR 2 equation to:

Similarly, Type 2 PHR can also be computed without using both known PUSCH and PUCCH transmissions (ie, using PUSCH and PUCCH reference formats) using known values such as:

‧ M _PUSCHc ( i )=1(10log ₁₀ ( M _PUSCH,c ( i ))=0)

‧ Δ _TFc ( i )=0

‧ δ _PUSCHc ( i - K _PUSCH )=0

‧ h _c ( n _CQI , n _HARQ )=0

‧ Δ _{F_PUCCHc} ( F )=0

‧ δ _PUCCHc ( i - k _m )=0

‧ Δ _{T xD} ( F ) = 0 to reduce the type 2 PHR equation to:

Accordingly, these example embodiments provide known values for certain PUSCH and/or PUCCH parameters that are not otherwise available. Thus, in such environments, these parameters, which typically represent actual PUSCH and/or PUCCH parameters, represent "virtual" PUSCH and/or PUCCH parameters in this case.

Accordingly, a component carrier for one of a physical uplink shared channel (PUSCH) for which a previous user equipment (UE) does not have a valid uplink grant is performed in a radio communication system in accordance with an exemplary embodiment. The method of power headroom reporting can include the steps illustrated in the flow chart of FIG. Wherein, at step 1000, the UE uses at least one known value associated with the PUSCH to calculate at least one parameter of a power headroom of a component carrier on which the UE does not have a valid uplink grant. The power headroom is calculated because one of the values for the at least one parameter cannot be obtained. The at least one known value is a value known by both the UE and the UE connected to one of the eNodeBs (step 1002), and the at least one parameter includes (step 1004) at least one of:

(a) M _PUSCHc ( i ), which represents the number of resource blocks assigned to the PUSCH on the component carrier when the UE has a valid uplink grant,

(b) Δ _TFc ( i ), which represents one of the transport format compensation associated with the component carrier when the UE has a valid uplink grant, and

(c) δ _PUSCHc ( i - K _PUSCH ), which represents one of the transmission power control commands associated with the component carrier when the UE has a valid uplink grant. With this information, the UE can then transmit a power headroom report at step 1006 based on the calculated power headroom.

According to another exemplary embodiment, a method for performing power headroom reporting in a radio communication system for a component device (UE) on which a previous user equipment (UE) does not have a current physical uplink control channel (PUCCH) transmission The method includes the steps shown in the flow chart of FIG. Wherein, at step 1100, the power margin is calculated by the UE using at least one known value associated with the PUCCH to calculate at least one parameter of a power headroom of a component carrier on which the UE does not have a PUCCH transmission. Space, because one of the values for the at least one parameter cannot be obtained. The at least one known value is a value known by both the UE and the UE connected to one of the eNodeBs (step 1102), and the at least one parameter comprises at least one of:

(a) h _c ( n _CQI , n _HARQ ), which represents an amount of power that is adapted by a certain number of bits transmitted by the UE on the component carrier when the UE has a transmission on the PUCCH,

(b) Δ _{F_PUCCHc} ( F ), which represents a relative performance difference between at least one known value of at least one parameter of the PUCCH 1a and the PUCCH associated with the component carrier when the UE has a transmission on the PUCCH ,and

(c) δ _PUCCHc ( i - k _m ), which represents one of the transmission power control commands associated with the component carrier when the UE has a transmission on the PUCCH (step 1104). With this information, at step 1106 the UE can then transmit a power headroom report based on the calculated power headroom.

Although FIG. 10 and FIG. 11 illustrate several methods from the UE view point, the method according to the exemplary embodiment may be considered from the viewpoint of the base station or the eNodeB, that is, the base station or the eNodeB processes or processes the incoming data. The power headroom is reported to generate power control commands. Thus, in an exemplary embodiment of FIG. 12, a radio communication is illustrated for one of the user devices (UEs) that does not have a valid uplink grant, one of the physical uplink shared channel (PUSCH) component carriers. A method of performing power margin reporting in the system. Wherein, at step 1200, a power headroom report of a component carrier on which the UE does not have a valid uplink grant is received by an eNodeB. The power headroom report is calculated using at least one known value of at least one parameter associated with the PUSCH because one of the values for the at least one parameter is not available (step 1202) and the at least one known value is the UE And one of the eNodeBs is known to have one value (step 1204). The at least one parameter comprises at least one of: (a) M _PUSCHc ( i ) indicating a number of resource blocks assigned to the PUSCH on the component carrier when the UE has a valid uplink grant, ( b) Δ _TFc ( i ), which represents one of the transport format compensation associated with the component carrier when the UE has a valid uplink grant, and (c) δ _PUSCHc ( i - K _PUSCH ), which represents when the UE A transmission power control command associated with the component carrier when there is a valid uplink grant (step 1206). With this information, the eNodeB can determine an uplink power control command based on the power headroom report and then transmit the uplink power control command towards the UE.

Similarly, for PUCCH handling, a radio communication for one of the previous user equipment (UE) without a current physical uplink control channel (PUCCH) transmission is illustrated in the flow chart of FIG. A method of performing power headroom reporting in the system. Wherein, at step 1300, a power headroom report of a component carrier on which the UE does not have PUCCH transmission is received by an eNodeB. The power headroom report is calculated using at least one known value of at least one parameter associated with the PUCCH, because one of the values for the at least one parameter is not available (step 1302) and the at least one known value is UE And one of the eNodeBs is known to have one value (step 1304). Additionally, the at least one parameter comprises at least one of the following:

(a) h _c ( n _CQI , n _HARQ ), which represents an amount of power adapted by a certain number of bits transmitted on a component carrier when the UE has a PUCCH transmission,

(b) Δ _{F_PUCCHc} ( F ), which represents a relative performance difference between at least one known value of at least one parameter of PUCCH 1a and a PUCCH associated with the component carrier when the UE has a PUCCH transmission, and

(c) δ _PUCCHc ( i - k _m ), which represents one of the transmission power control commands associated with the component carrier when the UE has a PUCCH transmission (step 1306). With this information, the eNodeB can report and then transmit an uplink power control command based on the power headroom report.

The above-described exemplary embodiments are intended to be illustrative and not limiting in all aspects of the invention. All such variations and modifications are considered to be within the scope and spirit of the invention as defined by the following claims. Any elements, acts or instructions used in the description of the invention should not be considered as decisive or essential, unless explicitly stated otherwise. Moreover, as used herein, the article "a" is intended to include one or more items.

10. . . Component carrier

32. . . Base station

34. . . antenna

36. . . User terminal

40. . . Dedicated channel

42. . . Radio network controller

44. . . Core network

50. . . Packet data convergence agreement entity

52. . . Radio link control entity

54. . . Media access control entity

56. . . Scheduler

58. . . Physical layer entity

71. . . antenna

73. . . transceiver

74. . . processor

76. . . Memory device

78. . . Busbar

Figure 1 shows one of the LTE OFDM downlink signals in the frequency/time domain;

2 shows one subframe associated with one of the LTE OFDM signals in the time domain;

Figure 3 illustrates a downlink system with three PFDM symbols as one of the control regions;

4 shows a continuous uplink assignment in an LTE system;

Figure 5 illustrates carrier aggregation;

Figure 6 illustrates one of the base stations and a user equipment that can be used to implement the aspects of the exemplary embodiments;

Figure 7 shows a communication system in which an example embodiment may be implemented;

Figure 8 illustrates a processing element within one of the eNodeBs and a mobile terminal or UE in which an exemplary embodiment may be implemented;

Figure 9 illustrates additional components of an eNodeB UE; and

10 through 13 are flow diagrams illustrating methods in accordance with example embodiments.

(no component symbol description)

Claims (36)

A method for power headroom reporting in a radio communication system for a component carrier on which a user equipment (UE) does not have an active uplink for a physical uplink shared channel (PUSCH) An uplink grant, the method comprising: calculating, by the UE, one of the following values for the UE and one of the eNodeBs (eNodeB) connected to the UE to calculate that the UE is not A power headroom of the component carrier with a valid uplink grant: (a) M _PUSCHc ( i ) indicating the PUSCH assigned to the component carrier when the UE has a valid uplink grant a number of resource blocks, (b) Δ _TFc ( i ), which represents one of the transport format compensation associated with the PUSCH on the component carrier when the UE has a valid uplink grant, and (c) δ _PUSCHc ( i - K _PUSCH ), which represents a transmission power control command associated with the PUSCH on the component carrier when the UE has a valid uplink grant; wherein the UE does not have a valid uplink grant Unable to determine _M PUSCHc (i), _TFc (i) and _δ PUSCHc (i - K _PUSCH) in one of the at least one actual value; and based on the calculated power headroom reported by the UE of a transmission power headroom. The method of claim 1, wherein the value known by both the UE and the _eNodeB comprises a first predetermined value for one of M _PUSCHc ( i ), a second predetermined value for one of Δ _TFc ( i ), and a predetermined value for δ One of the third predetermined values of _PUSCHc ( i - K _PUSCH ). The method of claim 2, wherein the first predetermined value is 1. The method of claim 2, wherein the second predetermined value is 0 dB. The method of claim 2, wherein the third predetermined value is 0 dB. The method of claim 1, further comprising: receiving, by the UE, the at least one of signals from one of the _eNodeBs and M _PUSCHc ( i ), _ΔTFc ( i ), and δ _PUSCHc ( i - K _PUSCH ) One of the associated reference formats. The method of claim 1, wherein the power headroom report includes information indicating how much transmission power the UE has left for a subframe. The method of claim 1, wherein the value associated with the at least one of M _PUSCHc ( i ), Δ _TFc ( i ), and δ _PUSCHc ( i - K _PUSCH ) is M _PUSCHc ( i ), Δ _TFc ( The value of i ) and / or δ _PUSCHc ( i - K _PUSCH ). The method of claim 1, wherein the value associated with the at least one of M _PUSCHc ( i ), Δ _TFc ( i ), and δ _PUSCHc ( i - K _PUSCH ) is from which M _PUSCHc ( i ) can be calculated One of the values of Δ _TFc ( i ) and/or δ _PUSCHc ( i - K _PUSCH ). A User Equipment (UE), comprising: a processor configured to use a value known to the UE and one of the eNodeBs connected to the UE by using at least one of Calculating a power headroom of the component carrier on which the UE does not have a valid uplink grant, and in the mode in which the UE does not have a valid uplink grant for a physical uplink shared channel (PUSCH) One component carrier reports power headroom: (a) M _PUSCHc ( i ) indicating the number of resource blocks assigned to the PUSCH on the component carrier when the UE has a valid uplink grant, (b Δ _TFc ( i ), which represents one of the transport format compensation associated with the component carrier when the UE has a valid uplink grant, and (c) δ _PUSCHc ( i - K _PUSCH ), which represents when the UE A transmission power control command associated with the component carrier when there is a valid uplink grant, wherein the UE does not have a valid uplink grant and cannot determine M _PUSCHc ( i ), Δ _TFc ( i ), and δ _PUSCHc ( i - K _PUSCH) in the one of the at least one actual ; And a transceiver, which is configured by a power headroom based on the calculated transmission of a power headroom report. The UE of claim 10, wherein the value comprises a first predetermined value for one of M _PUSCHc ( i ), a second predetermined value for one of Δ _TFc ( i ), and a third for δ _PUSCHc ( i - K _PUSCH ) Predetermined value. The UE of claim 11, wherein the first predetermined value is 1. The UE of claim 11, wherein the second predetermined value is 0 dB. The UE of claim 11, wherein the third predetermined value is 0 dB. The UE of claim 10, wherein the transceiver is further configured to receive the signal from one of the _eNodeBs and the M _PUSCHc ( i ), Δ _TFc ( i ), and δ _PUSCHc ( i - K _PUSCH ) At least one of the associated reference formats. The UE of claim 10, wherein the power headroom report includes information indicating how much transmission power the UE has left for a subframe. The UE of claim 10, wherein the value associated with M _PUSCHc ( i ), Δ _TFc ( i ), and δ _PUSCHc ( i - K _PUSCH ) is M _PUSCHc ( i ), Δ _TFc ( i ), and/or δ _{The value of PUSCHc} ( i - K _PUSCH ). The UE of claim 10, wherein the value associated with the at least one of M _PUSCHc ( i ), Δ _TFc ( i ), and δ _PUSCHc ( i - K _PUSCU ) is from which the M _PUSCHc ( i ) can be calculated One of the values of Δ _TFc ( i ) and/or δ _PUSCHc ( i - K _PUSCH ). A method for power headroom reporting handling in a radio communication system for a component carrier on which a User Equipment (UE) does not have a valid uplink grant for a Physical Uplink Shared Channel (PUSCH) The method includes receiving, by an eNodeB, a power headroom report of the component carrier on which the UE does not have a valid uplink grant, wherein the UE is used and connected to the UE for at least one of One of the _eNodeBs is known to calculate the power headroom report: (a) M _PUSCHc ( i ), which indicates that the UE is assigned to the component carrier when it has a valid uplink grant. a number of resource blocks of the PUSCH, (b) Δ _TFc ( i ), which represents one of the transport format compensation associated with the PUSCH on the component carrier when the UE has a valid uplink grant, and (c δ _PUSCHc ( i - K _PUSCH ), which represents a transmission power control command associated with the PUSCH on the component carrier when the UE has a valid uplink grant, wherein the UE does not have a valid uplink grant and Method determining _{M PUSCHc (i), △ TFc} (i) and _δ PUSCHc (i - K _PUSCH) of the at least one actual value of one. The method of claim 19, wherein the value comprises a first predetermined value for one of M _PUSCHc ( i ), a second predetermined value for one of Δ _TFc ( i ), and a third for δ _PUSCHc ( i - K _PUSCH ) Predetermined value. The method of claim 20, wherein the first predetermined value is one. The method of claim 20, wherein the second predetermined value is 0 dB. The method of claim 20, wherein the third predetermined value is 0 dB. The method of claim 19, further comprising: transmitting, by the _eNodeB , a reference format associated with the at least one of M _PUSCHc ( i ), Δ _TFc ( i ), and δ _PUSCHc ( i - K _PUSCH ) . The method of claim 19, wherein the power headroom report includes information indicating how much transmission power the UE has left for a subframe. The method of claim 19, wherein the at least one known value associated with at least one of M _PUSCHc ( i ), Δ _TFc ( i ), and δ _PUSCHc ( i - K _PUSCH ) is M _PUSCHc ( i ), Δ The _{value of TFc} ( i ) and/or δ _PUSCHc ( i - K _PUSCH ). The method of claim 19, wherein the at least one known value associated with at least one of M _PUSCHc ( i ), Δ _TFc ( i ), and δ _PUSCHc ( i - K _PUSCH ) is from which M _PUSCHc can be calculated One of the values of ( i ), Δ _TFc ( i ), and/or δ _PUSCHc ( i - K _PUSCH ). An eNodeB, comprising: a processor configured to receive one of a component carrier of one of a physical uplink shared channel (PUSCH) in a mode in which one UE does not have a valid uplink grant during reception The margin space report, and based on the power headroom report, interpreting the power headroom report for at least one of the following using the UE and a known value associated with one of the eNodeBs of the UE to calculate: ( a) M _PUSCHc ( i ), which represents the number of resource blocks assigned to the PUSCH on the component carrier when the UE has a valid uplink grant, (b) Δ _TFc ( i ), which indicates when The UE has one transport format compensation associated with the component carrier upon grant of a valid uplink grant, and (c) δ _PUSCHc ( i - K _PUSCH ) indicating when the UE has a valid uplink grant and the One of the component carriers is associated with a transmission power control command, the UE does not have a valid uplink grant and cannot determine at least one of M _PUSCHc ( i ), Δ _TFc ( i ), and δ _PUSCHc ( i - K _PUSCH ) An actual value; and a transceiver configured to An uplink power control power margin command is transmitted based on the power headroom report. The _{eNodeB of} claim 28, wherein the value comprises a first predetermined value for one of M _PUSCHc ( i ), a second predetermined value for one of Δ _TFc ( i ), and one of δ _PUSCHc ( i - K _PUSCH ) The third predetermined value. The eNodeB of claim 29, wherein the first predetermined value is 1. The eNodeB of claim 29, wherein the second predetermined value is 0 dB. The eNodeB of claim 29, wherein the third predetermined value is 0 dB. The _{eNodeB of} claim 28, wherein the transceiver is further configured to transmit with M _PUSCHc ( i ), Δ _TFc ( i ), and δ _PUSCHc ( i - K _PUSCH ) in a signal toward the eNode B One of the at least one of the associated reference formats. The eNodeB of claim 28, wherein the power headroom report includes information indicating how much transmission power the UE has left for a subframe. The _{eNodeB of} claim 28, wherein the value associated with the at least one of M _PUSCHc ( i ), Δ _TFc ( i ), and δ _PUSCHc ( i - K _PUSCH ) is M _PUSCHc ( i ), Δ _{The value of TFc} ( i ) and/or δ _PUSCHc ( i - K _PUSCH ). As the _{eNodeB of} claim 28, wherein the value associated with the at least one of M _PUSCHc ( i ), Δ _TFc ( i ), and δ _PUSCHc ( i - K _PUSCH ) is from which M _PUSCHc can be calculated ( One of the values of i ), Δ _TFc ( i ) and/or δ _PUSCHc ( i - K _PUSCH ).