Patent Publication Number: US-10764842-B2

Title: Method for power headroom reporting and device therefor

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application is a continuation of U.S. patent application Ser. No. 15/976,101, filed on May 10, 2018, now U.S. Pat. No. 10,334,537, which is a continuation of U.S. patent application Ser. No. 14/900,980, filed on Dec. 22, 2015, now U.S. Pat. No. 9,992,755, which is the National Stage filing under 35 U.S.C. 371 of International Application No. PCT/KR2014/011487, filed on Nov. 27, 2014, which claims the benefit of U.S. Provisional Application No. 61/918,679, filed on Dec. 20, 2013, the contents of which are all hereby incorporated by reference herein in their entirety. 
    
    
     TECHNICAL FIELD 
     The present invention relates to a wireless communication system and, more particularly, to a method for power headroom reporting and a device therefor. 
     BACKGROUND ART 
     As an example of a mobile communication system to which the present invention is applicable, a 3rd Generation Partnership Project Long Term Evolution (hereinafter, referred to as LTE) communication system is described in brief. 
       FIG. 1  is a view schematically illustrating a network structure of an E-UMTS as an exemplary radio communication system. An Evolved Universal Mobile Telecommunications System (E-UMTS) is an advanced version of a conventional Universal Mobile Telecommunications System (UMTS) and basic standardization thereof is currently underway in the 3GPP. E-UMTS may be generally referred to as a Long Term Evolution (LTE) system. For details of the technical specifications of the UMTS and E-UMTS, reference can be made to Release 7 and Release 8 of “3rd Generation Partnership Project; Technical Specification Group Radio Access Network”. 
     Referring to  FIG. 1 , the E-UMTS includes a User Equipment (UE), eNodeBs (eNBs), and an Access Gateway (AG) which is located at an end of the network (E-UTRAN) and connected to an external network. The eNBs may simultaneously transmit multiple data streams for a broadcast service, a multicast service, and/or a unicast service. 
     One or more cells may exist per eNB. The cell is set to operate in one of bandwidths such as 1.25, 2.5, 5, 10, 15, and 20 MHz and provides a downlink (DL) or uplink (UL) transmission service to a plurality of UEs in the bandwidth. Different cells may be set to provide different bandwidths. The eNB controls data transmission or reception to and from a plurality of UEs. The eNB transmits DL scheduling information of DL data to a corresponding UE so as to inform the UE of a time/frequency domain in which the DL data is supposed to be transmitted, coding, a data size, and hybrid automatic repeat and request (HARQ)-related information. In addition, the eNB transmits UL scheduling information of UL data to a corresponding UE so as to inform the UE of a time/frequency domain which may be used by the UE, coding, a data size, and HARQ-related information. An interface for transmitting user traffic or control traffic may be used between eNBs. A core network (CN) may include the AG and a network node or the like for user registration of UEs. The AG manages the mobility of a UE on a tracking area (TA) basis. One TA includes a plurality of cells. 
     Although wireless communication technology has been developed to LTE based on wideband code division multiple access (WCDMA), the demands and expectations of users and service providers are on the rise. In addition, considering other radio access technologies under development, new technological evolution is required to secure high competitiveness in the future. Decrease in cost per bit, increase in service availability, flexible use of frequency bands, a simplified structure, an open interface, appropriate power consumption of UEs, and the like are required. 
     DISCLOSURE 
     Technical Problem 
     An object of the present invention devised to solve the problem lies in a method and device for a method for power headroom reporting. The technical problems solved by the present invention are not limited to the above technical problems and those skilled in the art may understand other technical problems from the following description. 
     Technical Solution 
     The object of the present invention can be achieved by providing a method for operating by an apparatus in wireless communication system, the method comprising; generating a PHR MAC CE (Power Headroom Reporting MAC Control Element) for activated cells comprising a first cell and a second cell; and transmitting a power headroom reporting through the generated PHR MAC CE to a network in a subframe, wherein the generated PHR MAC CE includes a value of Type 2 PH (Power Headroom) information for the first cell followed by a value of a Type 2 PH information for the second cell, and the Type 2 PH information for the second cell followed by a value of Type 1 PH information for the first cell. 
     In another aspect of the present invention provided herein is an apparatus in the wireless communication system, the apparatus comprising: an RF (radio frequency) module; and a processor configured to control the RF module, wherein the processor is configured to generate a PHR MAC CE (Power Headroom Reporting MAC Control Element) for activated cells, and to transmit a power headroom reporting through the generated PHR MAC CE to a network in a subframe, wherein the generated PHR MAC CE includes a value of Type 2 PH (Power Headroom) information for the first cell followed by a value of a Type 2 PH information for the second cell, and the Type 2 PH information for the second cell followed by a value of Type 1 PH information for the first cell. 
     Preferably, the second cell supports simultaneous PUCCH (Physical Uplink Control Channel)-PUSCH (Physical Uplink Shared Channel) transmission. 
     Preferably, the first cell supports simultaneous PUCCH (Physical Uplink Control Channel)-PUSCH (Physical Uplink Shared Channel) transmission. 
     Preferably, a first octet containing the value of the Type 2 PH information for the first cell is directly followed by a second octet containing the value of the Type 2 PH information for the second cell in the PHR MAC CE, if a PUCCH (Physical Uplink Control Channel) is not transmitted in the subframe on the first cell. 
     Preferably, a first octet containing the value of the Type 2 PH information for the second cell is directly followed by a second octet containing the value of the Type 1 PH information for the first cell in the PHR MAC CE, if a PUCCH (Physical Uplink Control Channel) is not transmitted in the subframe on the second cell. 
     Preferably, a first octet containing the value of the Type 2 PH information for the first cell is directly followed by a second octet containing a value of a maximum power of the first cell, and the second octet containing a value of a maximum power of the first cell is directly followed by a third octet containing the value of the Type 2 PH information for the second cell in the PHR MAC CE, if a PUCCH (Physical Uplink Control Channel) is transmitted in the subframe on the first cell. 
     Preferably, a first octet containing the value of the Type 2 PH information for the second cell is directly followed by a second octet containing a value of a maximum power of the second cell, and the second octet containing the value of the maximum power of the second cell is directly followed by a third octet containing the value of the Type 1 PH information for the first cell in the PHR MAC CE, if a PUCCH (Physical Uplink Control Channel) is transmitted in the subframe on the second cell. 
     Preferably, the Type 1 PH information indicates a power headroom level of a cell of the activated cells calculated based on a transmission power of a PUSCH (Physical Uplink Shared Channel), and the Type 2 PH information indicates a power headroom level of a cell of the of the activated cells calculated based on a transmission power of a PUSCH and a PUCCH (Physical Uplink Control Channel). 
     Preferably, the first cell is a primary cell (PCell) served by a Master eNodeB (MeNB) and the second cell is a Secondary Cell (SCell) served by a Secondary eNodeB (SeNB). 
     It is to be understood that both the foregoing general description and the following detailed description of the present invention are exemplary and explanatory and are intended to provide further explanation of the invention as claimed. 
     Advantageous Effects 
     According to the present invention, power headroom reporting can be efficiently performed in a wireless communication system. Specifically, the UE can report power headroom to each base station efficiently in dual connectivity system. 
     It will be appreciated by persons skilled in the art that that the effects achieved by the present invention are not limited to what has been particularly described hereinabove and other advantages of the present invention will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings. 
    
    
     
       DESCRIPTION OF DRAWINGS 
       The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the principle of the invention. 
         FIG. 1  is a diagram showing a network structure of an Evolved Universal Mobile Telecommunications System (E-UMTS) as an example of a wireless communication system; 
         FIG. 2A  is a block diagram illustrating network structure of an evolved universal mobile telecommunication system (E-UMTS), and  FIG. 2B  is a block diagram depicting architecture of a typical E-UTRAN and a typical EPC; 
         FIG. 3  is a diagram showing a control plane and a user plane of a radio interface protocol between a UE and an E-UTRAN based on a 3rd generation partnership project (3GPP) radio access network standard; 
         FIG. 4  is a diagram of an example physical channel structure used in an E-UMTS system; 
         FIG. 5  is a diagram for carrier aggregation; 
         FIG. 6  is a conceptual diagram for dual connectivity between a MasterCell Group (MCG) and a Secondary Cell Group (SCG); 
         FIG. 7A  is a conceptual diagram for C-Plane connectivity of base stations involved in dual connectivity, and  FIG. 7B  is a conceptual diagram for U-Plane connectivity of base stations involved in dual connectivity; 
         FIG. 8  is a conceptual diagram for radio protocol architecture for dual connectivity; 
         FIG. 9  is a diagram for a detailed split bearer in dual connectivity; 
         FIG. 10  is a diagram for signaling of buffer status and power-headroom reports; 
         FIG. 11  is a conceptual diagram for PHR MAC CE (Power Headroom Reporting MAC Control CE); 
         FIG. 12  is a conceptual diagram for Extended PHR MAC CE (Power Headroom Reporting MAC Control CE); 
         FIG. 13  is a conceptual diagram for transmitting Power Headroom Reporting according to embodiments of the present invention; 
         FIGS. 14 to 16  are conceptual diagrams for Extended PHR MAC CE (Power Headroom Reporting MAC Control CE) generated according to embodiments of the present invention; and 
         FIG. 17  is a block diagram of a communication apparatus according to an embodiment of the present invention. 
     
    
    
     BEST MODE 
     Universal mobile telecommunications system (UMTS) is a 3rd Generation (3G) asynchronous mobile communication system operating in wideband code division multiple access (WCDMA) based on European systems, global system for mobile communications (GSM) and general packet radio services (GPRS). The long-term evolution (LTE) of UMTS is under discussion by the 3rd generation partnership project (3GPP) that standardized UMTS. 
     The 3GPP LTE is a technology for enabling high-speed packet communications. Many schemes have been proposed for the LTE objective including those that aim to reduce user and provider costs, improve service quality, and expand and improve coverage and system capacity. The 3G LTE requires reduced cost per bit, increased service availability, flexible use of a frequency band, a simple structure, an open interface, and adequate power consumption of a terminal as an upper-level requirement. 
     Hereinafter, structures, operations, and other features of the present invention will be readily understood from the embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Embodiments described later are examples in which technical features of the present invention are applied to a 3GPP system. 
     Although the embodiments of the present invention are described using a long term evolution (LTE) system and a LTE-advanced (LTE-A) system in the present specification, they are purely exemplary. Therefore, the embodiments of the present invention are applicable to any other communication system corresponding to the above definition. In addition, although the embodiments of the present invention are described based on a frequency division duplex (FDD) scheme in the present specification, the embodiments of the present invention may be easily modified and applied to a half-duplex FDD (H-FDD) scheme or a time division duplex (TDD) scheme. 
       FIG. 2A  is a block diagram illustrating network structure of an evolved universal mobile telecommunication system (E-UMTS). The E-UMTS may be also referred to as an LTE system. The communication network is widely deployed to provide a variety of communication services such as voice (VoIP) through IMS and packet data. 
     As illustrated in  FIG. 2A , the E-UMTS network includes an evolved UMTS terrestrial radio access network (E-UTRAN), an Evolved Packet Core (EPC) and one or more user equipment. The E-UTRAN may include one or more evolved NodeB (eNodeB)  20 , and a plurality of user equipment (UE)  10  may be located in one cell. One or more E-UTRAN mobility management entity (MME)/system architecture evolution (SAE) gateways  30  may be positioned at the end of the network and connected to an external network. 
     As used herein, “downlink” refers to communication from eNodeB  20  to UE  10 , and “uplink” refers to communication from the UE to an eNodeB. UE  10  refers to communication equipment carried by a user and may be also referred to as a mobile station (MS), a user terminal (UT), a subscriber station (SS) or a wireless device. 
       FIG. 2B  is a block diagram depicting architecture of a typical E-UTRAN and a typical EPC. 
     As illustrated in  FIG. 2B , an eNodeB  20  provides end points of a user plane and a control plane to the UE  10 . MME/SAE gateway  30  provides an end point of a session and mobility management function for UE  10 . The eNodeB and MME/SAE gateway may be connected via an S1 interface. 
     The eNodeB  20  is generally a fixed station that communicates with a UE  10 , and may also be referred to as a base station (BS) or an access point. One eNodeB  20  may be deployed per cell. An interface for transmitting user traffic or control traffic may be used between eNodeBs  20 . 
     The MME provides various functions including NAS signaling to eNodeBs  20 , NAS signaling security, AS Security control, Inter CN node signaling for mobility between 3GPP access networks, Idle mode UE Reachability (including control and execution of paging retransmission), Tracking Area list management (for UE in idle and active mode), PDN GW and Serving GW selection, MME selection for handovers with MME change, SGSN selection for handovers to 2G or 3G 3GPP access networks, Roaming, Authentication, Bearer management functions including dedicated bearer establishment, Support for PWS (which includes ETWS and CMAS) message transmission. The SAE gateway host provides assorted functions including Per-user based packet filtering (by e.g. deep packet inspection), Lawful Interception, UE IP address allocation, Transport level packet marking in the downlink, UL and DL service level charging, gating and rate enforcement, DL rate enforcement based on APN-AMBR. For clarity MME/SAE gateway  30  will be referred to herein simply as a “gateway,” but it is understood that this entity includes both an MME and an SAE gateway. 
     A plurality of nodes may be connected between eNodeB  20  and gateway  30  via the S1 interface. The eNodeBs  20  may be connected to each other via an X2 interface and neighboring eNodeBs may have a meshed network structure that has the X2 interface. 
     As illustrated, eNodeB  20  may perform functions of selection for gateway  30 , routing toward the gateway during a Radio Resource Control (RRC) activation, scheduling and transmitting of paging messages, scheduling and transmitting of Broadcast Channel (BCCH) information, dynamic allocation of resources to UEs  10  in both uplink and downlink, configuration and provisioning of eNodeB measurements, radio bearer control, radio admission control (RAC), and connection mobility control in LTE_ACTIVE state. In the EPC, and as noted above, gateway  30  may perform functions of paging origination, LTE-IDLE state management, ciphering of the user plane, System Architecture Evolution (SAE) bearer control, and ciphering and integrity protection of Non-Access Stratum (NAS) signaling. 
     The EPC includes a mobility management entity (MME), a serving-gateway (S-GW), and a packet data network-gateway (PDN-GW). The MME has information about connections and capabilities of UEs, mainly for use in managing the mobility of the UEs. The S-GW is a gateway having the E-UTRAN as an end point, and the PDN-GW is a gateway having a packet data network (PDN) as an end point. 
       FIG. 3  is a diagram showing a control plane (a) and a user plane (b) of a radio interface protocol between a UE and an E-UTRAN based on a 3GPP radio access network standard. The control plane refers to a path used for transmitting control messages used for managing a call between the UE and the E-UTRAN. The user plane refers to a path used for transmitting data generated in an application layer, e.g., voice data or Internet packet data. 
     A physical (PHY) layer of a first layer provides an information transfer service to a higher layer using a physical channel. The PHY layer is connected to a medium access control (MAC) layer located on the higher layer via a transport channel Data is transported between the MAC layer and the PHY layer via the transport channel. Data is transported between a physical layer of a transmitting side and a physical layer of a receiving side via physical channels. The physical channels use time and frequency as radio resources. In detail, the physical channel is modulated using an orthogonal frequency division multiple access (OFDMA) scheme in downlink and is modulated using a single carrier frequency division multiple access (SC-FDMA) scheme in uplink. 
     The MAC layer of a second layer provides a service to a radio link control (RLC) layer of a higher layer via a logical channel. The RLC layer of the second layer supports reliable data transmission. A function of the RLC layer may be implemented by a functional block of the MAC layer. A packet data convergence protocol (PDCP) layer of the second layer performs a header compression function to reduce unnecessary control information for efficient transmission of an Internet protocol (IP) packet such as an IP version 4 (IPv4) packet or an IP version 6 (IPv6) packet in a radio interface having a relatively small bandwidth. 
     A radio resource control (RRC) layer located at the bottom of a third layer is defined only in the control plane. The RRC layer controls logical channels, transport channels, and physical channels in relation to configuration, re-configuration, and release of radio bearers (RBs). An RB refers to a service that the second layer provides for data transmission between the UE and the E-UTRAN. To this end, the RRC layer of the UE and the RRC layer of the E-UTRAN exchange RRC messages with each other. 
     One cell of the eNB is set to operate in one of bandwidths such as 1.25, 2.5, 5, 10, 15, and 20 MHz and provides a downlink or uplink transmission service to a plurality of UEs in the bandwidth. Different cells may be set to provide different bandwidths. 
     Downlink transport channels for transmission of data from the E-UTRAN to the UE include a broadcast channel (BCH) for transmission of system information, a paging channel (PCH) for transmission of paging messages, and a downlink shared channel (SCH) for transmission of user traffic or control messages. Traffic or control messages of a downlink multicast or broadcast service may be transmitted through the downlink SCH and may also be transmitted through a separate downlink multicast channel (MCH). 
     Uplink transport channels for transmission of data from the UE to the E-UTRAN include a random access channel (RACH) for transmission of initial control messages and an uplink SCH for transmission of user traffic or control messages. Logical channels that are defined above the transport channels and mapped to the transport channels include a broadcast control channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH), and a multicast traffic channel (MTCH). 
       FIG. 4  is a view showing an example of a physical channel structure used in an E-UMTS system. A physical channel includes several subframes on a time axis and several subcarriers on a frequency axis. Here, one subframe includes a plurality of symbols on the time axis. One subframe includes a plurality of resource blocks and one resource block includes a plurality of symbols and a plurality of subcarriers. In addition, each subframe may use certain subcarriers of certain symbols (e.g., a first symbol) of a subframe for a physical downlink control channel (PDCCH), that is, an L1/L2 control channel. In  FIG. 4 , an L1/L2 control information transmission area (PDCCH) and a data area (PDSCH) are shown. In one embodiment, a radio frame of 10 ms is used and one radio frame includes 10 subframes. In addition, one subframe includes two consecutive slots. The length of one slot may be 0.5 ms. In addition, one subframe includes a plurality of OFDM symbols and a portion (e.g., a first symbol) of the plurality of OFDM symbols may be used for transmitting the L1/L2 control information. A transmission time interval (TTI) which is a unit time for transmitting data is 1 ms. 
     A base station and a UE mostly transmit/receive data via a PDSCH, which is a physical channel, using a DL-SCH which is a transmission channel, except a certain control signal or certain service data. Information indicating to which UE (one or a plurality of UEs) PDSCH data is transmitted and how the UE receive and decode PDSCH data is transmitted in a state of being included in the PDCCH. 
     For example, in one embodiment, a certain PDCCH is CRC-masked with a radio network temporary identity (RNTI) “A” and information about data is transmitted using a radio resource “B” (e.g., a frequency location) and transmission format information “C” (e.g., a transmission block size, modulation, coding information or the like) via a certain subframe. Then, one or more UEs located in a cell monitor the PDCCH using its RNTI information. And, a specific UE with RNTI “A” reads the PDCCH and then receive the PDSCH indicated by B and C in the PDCCH information. 
       FIG. 5  is a diagram for carrier aggregation. 
     Carrier aggregation technology for supporting multiple carriers is described with reference to  FIG. 5  as follows. As mentioned in the foregoing description, it may be able to support system bandwidth up to maximum 100 MHz in a manner of bundling maximum 5 carriers (component carriers: CCs) of bandwidth unit (e.g., 20 MHz) defined in a legacy wireless communication system (e.g., LTE system) by carrier aggregation. Component carriers used for carrier aggregation may be equal to or different from each other in bandwidth size. And, each of the component carriers may have a different frequency band (or center frequency). The component carriers may exist on contiguous frequency bands. Yet, component carriers existing on non-contiguous frequency bands may be used for carrier aggregation as well. In the carrier aggregation technology, bandwidth sizes of uplink and downlink may be allocated symmetrically or asymmetrically. 
     Multiple carriers (component carriers) used for carrier aggregation may be categorized into primary component carrier (PCC) and secondary component carrier (SCC). The PCC may be called P-cell (primary cell) and the SCC may be called S-cell (secondary cell). The primary component carrier is the carrier used by a base station to exchange traffic and control signaling with a user equipment. In this case, the control signaling may include addition of component carrier, setting for primary component carrier, uplink (UL) grant, downlink (DL) assignment and the like. Although a base station may be able to use a plurality of component carriers, a user equipment belonging to the corresponding base station may be set to have one primary component carrier only. If a user equipment operates in a single carrier mode, the primary component carrier is used. Hence, in order to be independently used, the primary component carrier should be set to meet all requirements for the data and control signaling exchange between a base station and a user equipment. 
     Meanwhile, the secondary component carrier may include an additional component carrier that can be activated or deactivated in accordance with a required size of transceived data. The secondary component carrier may be set to be used only in accordance with a specific command and rule received from a base station. In order to support an additional bandwidth, the secondary component carrier may be set to be used together with the primary component carrier. Through an activated component carrier, such a control signal as a UL grant, a DL assignment and the like can be received by a user equipment from a base station. Through an activated component carrier, such a control signal in UL as a channel quality indicator (CQI), a precoding matrix index (PMI), a rank indicator (RI), a sounding reference signal (SRS) and the like can be transmitted to a base station from a user equipment. 
     Resource allocation to a user equipment can have a range of a primary component carrier and a plurality of secondary component carriers. In a multi-carrier aggregation mode, based on a system load (i.e., static/dynamic load balancing), a peak data rate or a service quality requirement, a system may be able to allocate secondary component carriers to DL and/or UL asymmetrically. In using the carrier aggregation technology, the setting of the component carriers may be provided to a user equipment by a base station after RRC connection procedure. In this case, the RRC connection may mean that a radio resource is allocated to a user equipment based on RRC signaling exchanged between an RRC layer of the user equipment and a network via SRB. After completion of the RRC connection procedure between the user equipment and the base station, the user equipment may be provided by the base station with the setting information on the primary component carrier and the secondary component carrier. The setting information on the secondary component carrier may include addition/deletion (or activation/deactivation) of the secondary component carrier. Therefore, in order to activate a secondary component carrier between a base station and a user equipment or deactivate a previous secondary component carrier, it may be necessary to perform an exchange of RRC signaling and MAC control element. 
     The activation or deactivation of the secondary component carrier may be determined by a base station based on a quality of service (QoS), a load condition of carrier and other factors. And, the base station may be able to instruct a user equipment of secondary component carrier setting using a control message including such information as an indication Type (activation/deactivation) for DL/UL, a secondary component carrier list and the like. 
       FIG. 6  is a conceptual diagram for Dual Connectivity (DC) between a MasterCell Group (MCG) and a Secondary Cell Group (SCG). 
     The dual connectivity means that the UE can be connected to both a Master eNode-B (MeNB) and a Secondary eNode-B (SeNB) at the same time. The MCG is a group of serving cells associated with the MeNB, comprising of a PCell and optionally one or more SCells. And the SCG is a group of serving cells associated with the SeNB, comprising of the special SCell and optionally one or more SCells. The MeNB is an eNB which terminates at least S1-MME (S1 for the control plane) and the SeNB is an eNB that is providing additional radio resources for the UE but is not the MeNB. 
     With dual connectivity, some of the data radio bearers (DRBs) can be offloaded to the SCG to provide high throughput while keeping scheduling radio bearers (SRBs) or other DRBs in the MCG to reduce the handover possibility. The MCG is operated by the MeNB via the frequency of f1, and the SCG is operated by the SeNB via the frequency of f2. The frequency f1 and f2 may be equal. The backhaul interface (BH) between the MeNB and the SeNB is non-ideal (e.g. X2 interface), which means that there is considerable delay in the backhaul and therefore the centralized scheduling in one node is not possible. 
     Above all, the SCG may have a special SCell so called “PSCell” (Primary SCell). Behavior of the PSCell is similar with that of PCell. Thus, the PSCell is the carrier used by a base station to exchange traffic and control signal with a user equipment. In this case, the control signaling may include addition of component carrier, setting for primary component carrier, uplink (UL) grant, downlink (DL) assignment and the like. And random access procedure performs on the PSCell and the PSCell cannot be de-activated. However, because the PSCell is not a PCell, the PSCell cannot be the carrier used by a base station connected with RRC connection. 
       FIG. 7A  is a conceptual diagram for C-Plane connectivity of base stations involved in dual connectivity, and  FIG. 7B  is a conceptual diagram for U-Plane connectivity of base stations involved in dual connectivity. 
       FIG. 7A  shows C-plane (Control Plane) connectivity of eNBs involved in dual connectivity for a certain UE. The MeNB is C-plane connected to the MME via S1-MME, the MeNB and the SeNB are interconnected via X2-C (X2-Control plane). As  FIG. 7A , Inter-eNB control plane signaling for dual connectivity is performed by means of X2 interface signaling. Control plane signaling towards the MME is performed by means of S1 interface signaling. There is only one S1-MME connection per UE between the MeNB and the MME. Each eNB should be able to handle UEs independently, i.e. provide the PCell to some UEs while providing SCell(s) for SCG to others. Each eNB involved in dual connectivity for a certain UE owns its radio resources and is primarily responsible for allocating radio resources of its cells, respective coordination between MeNB and SeNB is performed by means of X2 interface signaling. 
       FIG. 7B  shows U-plane connectivity of eNBs involved in dual connectivity for a certain UE. U-plane connectivity depends on the bearer option configured: i) For MCG bearers, the MeNB is U-plane connected to the S-GW via S1-U, the SeNB is not involved in the transport of user plane data, ii) For split bearers, the MeNB is U-plane connected to the S-GW via S1-U and in addition, the MeNB and the SeNB are interconnected via X2-U, and iii) For SCG bearers, the SeNB is directly connected with the S-GW via S1-U. If only MCG and split bearers are configured, there is no S1-U termination in the SeNB. In the dual connectivity, enhancement of the small cell is required in order to data offloading from the group of macro cells to the group of small cells. Since the small cells can be deployed apart from the macro cells, multiple schedulers can be separately located in different nodes and operate independently from the UE point of view. This means that different scheduling node would encounter different radio resource environment, and hence, each scheduling node may have different scheduling results. 
       FIG. 8  is a conceptual diagram for radio protocol architecture for dual connectivity. 
     E-UTRAN of the present example can support dual connectivity operation whereby a multiple receptions/transmissions (RX/TX) UE in RRC_CONNECTED is configured to utilize radio resources provided by two distinct schedulers, located in two eNBs (or base stations) connected via a non-ideal backhaul over the X2 interface. The eNBs involved in dual connectivity for a certain UE may assume two different roles: an eNB may either act as the MeNB or as the SeNB. In dual connectivity, a UE can be connected to one MeNB and one SeNB. 
     In the dual connectivity operation, the radio protocol architecture that a particular bearer uses depends on how the bearer is setup. Three alternatives exist, MCG bearer ( 801 ), split bearer ( 803 ) and SCG bearer ( 805 ). Those three alternatives are depicted on  FIG. 8 . The SRBs (Signaling Radio Bearers) are always of the MCG bearer and therefore only use the radio resources provided by the MeNB. The MCG bearer ( 801 ) is a radio protocol only located in the MeNB to use MeNB resources only in the dual connectivity. And the SCG bearer ( 805 ) is a radio protocol only located in the SeNB to use SeNB resources in the dual connectivity. 
     Specially, the split bearer ( 803 ) is a radio protocol located in both the MeNB and the SeNB to use both MeNB and SeNB resources in the dual connectivity and the split bearer ( 803 ) may be a radio bearer comprising one Packet Data Convergence Protocol (PDCP) entity, two Radio Link Control (RLC) entities and two Medium Access Control (MAC) entities for one direction. Specially, the dual connectivity operation can also be described as having at least one bearer configured to use radio resources provided by the SeNB. 
       FIG. 9  is a diagram for a detailed split bearer in dual connectivity. 
     A structure of  FIG. 9  is the combination of S1-U that terminates in the MeNB, bearer split in the MeNB and independent RLCs for split bearers. 
     The expected benefits of this structure are: 
     i) the SeNB mobility hidden to CN, ii) no security impacts with ciphering being required in the MeNB only, iii) no data forwarding between SeNBs required at SeNB change, iv) offloads an RLC processing of SeNB traffic from the MeNB to the SeNB, v) little or no impacts to an RLC entity, vi) utilization of radio resources across the MeNB and the SeNB for the same bearer possible, and vii) relaxed requirements for the SeNB mobility (The MeNB can be used in the meantime). 
     The expected drawbacks of this structure are: 
     i) need to route, process and buffer all dual connectivity traffic in the MeNB, ii) a PDCP entity to become responsible for routing PDCP PDUs towards eNBs for transmission and reordering them for reception, iii) flow control required between the MeNB and the SeNB, iv) in the uplink, logical channel prioritization impacts for handling RLC retransmissions and RLC Status PDUs (restricted to the eNB where the corresponding RLC entity resides) and v) no support of local break-out and content caching at SeNB for dual connectivity UEs. 
       FIG. 10  is a diagram for signaling of buffer status and power-headroom reports. 
     The scheduler needs knowledge about the amount of data awaiting transmission from the terminals to assign the proper amount of uplink resources. Obviously, there is no need to provide uplink resources to a terminal with no data to transmit as this would only result in the terminal performing padding to fill up the granted resources. Hence, as a minimum, the scheduler needs to know whether the terminal has data to transmit and should be given a grant. This is known as a scheduling request. 
     The use of a single bit for the scheduling request is motivated by the desire to keep the uplink overhead small, as a multi-bit scheduling request would come at a higher cost. A consequence of the single bit scheduling request is the limited knowledge at the eNodeB about the buffer situation at the terminal when receiving such a request. Different scheduler implementations handle this differently. One possibility is to assign a small amount of resources to ensure that the terminal can exploit them efficiently without becoming power limited. Once the terminal has started to transmit on the UL-SCH, more detailed information about the buffer status and power headroom can be provided through the inband MAC control message, as discussed below. 
     Terminals that already have a valid grant obviously do not need to request uplink resources. However, to allow the scheduler to determine the amount of resources to grant to each terminal in future subframes, information about the buffer situation and the power availability is useful, as discussed above. This information is provided to the scheduler as part of the uplink transmission through MAC control element. The LCID field in one of the MAC subheaders is set to a reserved value indicating the presence of a buffer status report, as illustrated in  FIG. 10 . 
     Especially, to assist the scheduler in the selection of a combination of modulation-and-coding scheme and resource size M that does not lead to the terminal being power limited, the terminal can be configured to provide regular power headroom reports on its power usage. There is a separate transmit-power limitation for each component carrier. Thus, power headroom should be measured and reported separately for each component carrier. 
     There are two different Types of power-headroom reports defined for LTE release 10, Type 1 and Type 2. Type 1 reporting reflects the power headroom assuming PUSCH-only transmission on the carrier, while the Type2 report assumes combined PUSCH and PUCCH transmission. 
     The Type1 power headroom valid for a certain subframe, assuming that the terminal was really scheduled for PUSCH transmission in that subframe, is given by the following expression:
 
Power Headroom= P   CMAX,c −( P   0,PUSCH   +α·PL   UL +10·log 10 ( M )+Δ MCS +δ).  [Equation 1]
 
     Where the values for M and Δ MCS  correspond to the resource assignment and modulation-and-coding scheme used in the subframe to which the power-headroom report corresponds. It can be noted that the power headroom is not a measure of the difference between the maximum per-carrier transmit power and the actual carrier transmit power. It can be seen that the power headroom is a measure of the difference between P CMAX,c  and the transmit power that would have been used assuming that there would have been no upper limit on the transmit power. Thus, the power headroom can very well be negative. More exactly, a negative power headroom indicates that the per-carrier transmit power was limited by P CMAX,c  at the time of the power headroom reporting. As the network knows what modulation-and-coding scheme and resource size the terminal used for transmission in the subframe to which the power-headroom report corresponds, it can determine what are the valid combinations of modulation-and-coding scheme and resource size M, assuming that the downlink path loss PL DL  and the term δ have not changed substantially. 
     Type-1 power headroom can also be reported for subframes where there is no actual PUSCH transmission. In such cases, 10·log 10 (M) and Δ MCS  in the expression above are set to zero:
 
Power Headroom= P   CMAX,c −( P   0,PUSCH   +α·PL   DL +δ).
 
     This can be seen as the power headroom assuming a default transmission configuration corresponding to the minimum possible resource assignment (M=1) and the modulation-and-coding scheme associated with Δ MCS =0 dB. 
     Similarly, Type2 power headroom reporting is defined as the difference between the maximum per-carrier transmit power and the sum of the PUSCH and PUCCH transmit power respectively, once again not taking into account any maximum per-carrier power when calculating the PUSCH and PUCCH transmit power. 
     Similar to Type1 power headroom reporting, the Type2 power headroom can also be reported for subframes in which no PUSCH and/or PUCCH is transmitted. In that case a virtual PUSCH and or PUCCH transmit power is calculated, assuming the smallest possible resource assignment (M=1) and Δ MCS =0 dB for PUSCH and Δ Format =0 for PUCCH. 
     For the uplink, the power availability, or power headroom is defined as the difference between the nominal maximum output power and the estimated output power for UL-SCH transmission. This quantity can be positive as well as negative (on a dB scale), where a negative value would indicate that the network has scheduled a higher data rate than the terminal can support given its current power availability. The power headroom depends on the power-control mechanism and thereby indirectly on factors such as the interference in the system and the distance to the base stations. 
     Information about the power headroom is fed back from the terminals to the eNodeB in a similar way as the buffer-status reports—that is, only when the terminal is scheduled to transmit on the UL-SCH. Type1 reports are provided for all component carriers simultaneously, while Type2 reports are provided for the primary component carrier only. 
     A power headroom report can be triggered for the following reasons: 
     Periodically as controlled by a timer. 
     Change in path loss, since the last power headroom report is larger than a (configurable) threshold. 
     Instead of padding (for the same reason as buffer-status reports). 
     It is also possible to configure a prohibit timer to control the minimum time between two power-headroom reports and thereby the signaling load on the uplink. 
       FIG. 11  is a conceptual diagram for PHR MAC CE (Power Headroom Reporting MAC Control CE). 
     The Power Headroom MAC control element is identified by a MAC PDU subheader with LCID as specified in Table 1. It has a fixed size and consists of a single octet defined as follows by Table 2. 
     
       
         
           
               
               
               
             
               
                   
                 TABLE 1 
               
               
                   
                   
               
               
                   
                 Index 
                 LCID values 
               
               
                   
                   
               
             
            
               
                   
                 00000 
                 CCCH 
               
               
                   
                 00001- 
                 Identity of the logical 
               
               
                   
                 01010 
                 channel 
               
               
                   
                 01011- 
                 Reserved 
               
               
                   
                 11000 
                   
               
               
                   
                 11001 
                 Extended Power Headroom 
               
               
                   
                   
                 Report 
               
               
                   
                 11010 
                 Power Headroom Report 
               
               
                   
                 11011 
                 C-RNTI 
               
               
                   
                 11100 
                 Truncated BSR 
               
               
                   
                 11101 
                 Short BSR 
               
               
                   
                 11110 
                 Long BSR 
               
               
                   
                 11111 
                 Padding 
               
               
                   
                   
               
            
           
         
       
     
     
       
         
           
               
               
             
               
                 TABLE 2 
               
               
                   
               
               
                 PH 
                 Power Headroom Level 
               
               
                   
               
             
            
               
                   
               
            
           
           
               
               
            
               
                 0 
                 POWER_HEADROOM_0 
               
               
                 1 
                 POWER_HEADROOM_1 
               
               
                 2 
                 POWER_HEADROOM_2 
               
               
                 3 
                 POWER_HEADROOM_3 
               
               
                 . . . 
                 . . . 
               
               
                 60 
                 POWER_HEADROOM_60 
               
               
                 61 
                 POWER_HEADROOM_61 
               
               
                 62 
                 POWER_HEADROOM_62 
               
               
                 63 
                 POWER_HEADROOM_63 
               
               
                   
               
            
           
         
       
     
     A field of R ( 1101 ) is a reserved bit and is set to “0”. And a field of PH ( 1103 ) indicates the power headroom level. A length of the field of PH ( 1103 ) is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 2 above. 
       FIG. 12  is a conceptual diagram for Extended PHR MAC CE (Power Headroom Reporting MAC Control CE). 
     The Extended Power Headroom MAC control element is identified by a MAC PDU subheader with LCID as specified in the Table 1 above. It has a variable size and is defined in  FIG. 12 . When Type 2 PH is reported, the octet containing the Type 2 PH field is included first after the octet indicating the presence of PH per SCell and followed by an octet containing the associated P CMAX,c  field (if reported). Then follows in ascending order based on the Serving Cell Index an octet with the Type 1 PH field and an octet with the associated PCMAX,c field (if reported), for the PCell and for each SCell indicated in the bitmap. 
     The Extended Power Headroom MAC Control Element is defined as follows: 
     A field of ‘Ci’ ( 1201 ) indicates the presence of a PH field for the SCell with SCell index i. The Ci field set to “1” indicates that a PH field for the SCell with SCell index i is reported. The Ci field set to “0” indicates that a PH field for the SCell with SCell index i is not reported; 
     A field of ‘R’ ( 1203 ) is a reserved bit and is set to “0”; 
     A field of ‘V’ ( 1205 ) indicates if the PH value is based on a real transmission or a reference format. For Type 1 PH, V=0 indicates real transmission on PUSCH and V=1 indicates that a PUSCH reference format is used. For Type 2 PH, V=0 indicates real transmission on PUCCH and V=1 indicates that a PUCCH reference format is used. Furthermore, for both Type 1 and Type 2 PH, V=0 indicates the presence of the octet containing the associated P CMAX,c  field, and V=1 indicates that the octet containing the associated P CMAX,c  field is omitted; 
     A field of ‘PH’ ( 1207 ) indicates the power headroom level. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 2 
     A field of ‘P’ ( 1209 ) indicates whether the UE applies power backoff due to power management as allowed by P-MPRc. The UE shall set P=1 if the corresponding P CMAX,c  field would have had a different value if no power backoff due to power management had been applied; 
     A field of ‘P CMAX,c ’ ( 1211 ) if present, this field indicates the P CMAX,c  or {tilde over (P)} CMAX,c  used for calculation of the preceding PH field. The reported P CMAX,c  and the corresponding nominal UE transmit power levels are shown in Table 3. 
     If the UE has UL resources allocated for new transmission for a TTI and if the UE is configured to simultaneous PUCCH-PUSCH transmission, the Extended Power Headroom MAC Control Element includes a value of a Type 2 power headroom for the cell in the field of PH in a TTI. In this case, if the UE has a PUCCH transmission in the TTI, the Extended Power Headroom MAC Control Element includes a value of the corresponding P CMAX,c  field from a physical layer; 
     
       
         
           
               
               
             
               
                 TABLE 3 
               
               
                   
               
               
                 PH 
                 Power Headroom Level 
               
               
                   
               
             
            
               
                   
               
            
           
           
               
               
            
               
                 0 
                 POWER_HEADROOM_0 
               
               
                 1 
                 POWER_HEADROOM_1 
               
               
                 2 
                 POWER_HEADROOM_2 
               
               
                 3 
                 POWER_HEADROOM_3 
               
               
                 . . . 
                 . . . 
               
               
                 60 
                 POWER_HEADROOM_60 
               
               
                 61 
                 POWER_HEADROOM_61 
               
               
                 62 
                 POWER_HEADROOM_62 
               
               
                 63 
                 POWER_HEADROOM_63 
               
               
                   
               
            
           
         
       
     
     For the prior art, the PUCCH is configured only in one cell (i.e. PCell) for the UE even if multiple cells are configured with uplink. Therefore, in the Extended PHR MAC CE, Type 1 PH is reported for all serving cells, but Type 2 PH is reported only for PCell. The Type 1 PH is the power headroom calculated by considering only PUSCH transmission, and the Type 2 PH is the power headroom calculated by considering both PUCCH and PUSCH transmissions. 
     In Dual Connectivity mentioned above, the PUCCH is decided to be used for at least one serving cell controlled by the SeNB. The reason is that since the MeNB and the SeNB is linked with non-ideal backhaul, the SeNB cannot schedule for the UE based on the PUCCH transmitted to the MeNB. If simultaneous PUCCH-PUSCH transmission is supported for serving cells other than PCell, the PHR should be changed to reflect this aspect. 
       FIG. 13  is a conceptual diagram for transmitting Power Headroom Reporting according to embodiments of the present invention. 
     The UE can be connected to both the MeNB and the SeNB at the same time in a dual connectivity. The MCG is a group of serving cells associated with the MeNB, comprising of a PCell and optionally one or more SCells. And the SCG is a group of serving cells associated with the SeNB, comprising of the special SCell and optionally one or more SCells. The special SCell may be a PSCell. 
     In DC, PUCCH is transmitted on PCell and PSCell. Depending on UE capability, the UE is likely to support simultaneous PUCCH-PUSCH transmission on PCell and PSCell in the same subframe. However, MeNB and SeNB may have different preference on configuration of simultaneous PUCCH-PUSCH transmission on PCell and PSCell. Accordingly, for network configurability, it seems natural that each eNB independently configures simultaneous PUCCH-PUSCH transmission on PCell and PSCell. I.e., MeNB configures simultaneous PUCCH-PUSCH transmission on PCell and SeNB configures simultaneous PUCCH-PUSCH transmission on PSCell. 
     To report the accurate UE power situation to eNBs when the UE is configured with multiple PUCCHs, it is invented that, the UE reports Type 2 PH for each activated serving cell configured with simultaneous PUCCH-PUSCH transmission to the eNB, in addition to Type 1 PH. 
     The following steps are used to realize the invention; 
     For each serving cell, the UE receives serving cell configuration information including PUCCH and PUSCH configurations and support of simultaneous PUCCH-PUSCH transmission from the eNB (S 1301 ). 
     When a PHR is triggered, for each serving cell, the UE checks whether a serving cell is configured with PUSCH and is activated (S 1303 ). Preferably, the PHR may be triggered in MAC entities for both the MCG and the SCG. 
     If the serving cell is configured with PUSCH and is activated, i) the UE obtains the value of the Type 1 power headroom and the UE obtains the value for the corresponding P CMAX,c  field from the physical layer if the UE has UL resources allocated for transmission on this serving cell for this TTI (S 1305 ). 
     The UE checks whether the serving cell supports simultaneous PUCCH-PUSCH transmission (S 1307 ). 
     If the serving cell supports simultaneous PUCCH-PUSCH transmission, the UE obtains the value of the Type 2 power headroom and the UE obtains the value for the corresponding P CMAX,c  field from the physical layer if the UE has a PUCCH transmission in this TTI (S 1309 ). 
     The UE generates an Extended PHR MAC control element based on the obtained values (S 1311 ). 
       FIGS. 14 to 16  are conceptual diagrams for Extended PHR MAC CE (Power Headroom Reporting MAC Control CE) generated according to embodiments of the present invention. 
       FIG. 14  represents a case that a SCell served by the SeNB is configured to the UE. In this format, the UE constructs PHR MAC CE by including Type 2 PH first and then including Type 1 PH. 
     When Type 2 PH is reported for a PCell, an octet containing the Type 2 PH field for the PCell is included first after the octet indicating the presence of PH per SCell and followed by an octet containing the associated P CMAX,c  field (if reported). If DC is configured, regarding  FIG. 14 , when Type 2 PH is reported for the PSCell, then follows an octet containing the Type 2 PH field for the PSCell and an octet containing the associated P CMAX,c  field (if reported). Then follows in ascending order based on a serving cell index an octet with the Type 1 PH field and an octet with the associated P CMAX,c  field (if reported), for the PCell and for each PSCell and SCell indicated in the bitmap. 
     In DC, the PHR includes PH information of all activated cells. Accordingly, if simultaneous PUCCH-PUSCH transmission is configured for PCell or PSCell, the MeNB or the SeNB will receive the extended PHR MAC CE including Type 2 PH of PCell or PSCell. 
     In detail, when the UE transmits power headroom reporting through the PHR MAC CE in a subframe, the PHR MAC CE includes a value of Type 2 PH information for the PCell ( 1401 ) followed by a value of a Type 2 PH information for the SCell ( 1403 ), and the Type 2 PH information for the SCell ( 1403 ) followed by a value of Type 1 PH information for the PCell ( 1405 ). 
     Preferably, if the PCell supports simultaneous PUCCH-PUSCH transmission, a value of Type 2 PH information for the PCell is in the PHR MAC CE. And similarly, if the SCell supports simultaneous PUCCH-PUSCH transmission, a value of Type 2 PH information for the SCell is in the PHR MAC CE. 
     Assume that the MeNB configures simultaneous PUCCH-PUSCH transmission on PCell and the SeNB also configures simultaneous PUCCH-PUSCH transmission on PSCell. In this case, a first octet containing the value of the Type 2 PH information for the PCell ( 1401 ) is directly followed by a second octet containing the value of the Type 2 PH information for the SCell ( 1403 ) in the PHR MAC CE, if a PUCCH is not transmitted in the subframe on the PCell. Meanwhile, a first octet containing the value of the Type 2 PH information for the PCell ( 1401 ) is directly followed by a second octet containing a value of a maximum power of the PCell ( 1407 ), and the second octet containing a value of a maximum power of the PCell ( 1407 ), is directly followed by a third octet containing the value of the Type 2 PH information for the SCell ( 1403 ) in the PHR MAC CE, if a PUCCH is transmitted in the subframe on the PCell. 
     Preferably, a first octet containing the value of the Type 2 PH information for the SCell ( 1403 ) is directly followed by a second octet containing the value of the Type 1 PH information for the PCell ( 1405 ) in the PHR MAC CE, if a PUCCH is not transmitted in the subframe on the SCell. And a first octet containing the value of the Type 2 PH information for the SCell ( 1403 ) is directly followed by a second octet containing a value of a maximum power of the SCell ( 1409 ) and the second octet containing the value of the maximum power of the SCell ( 1409 ) is directly followed by a third octet containing the value of the Type 1 PH information for the PCell ( 1405 ) in the PHR MAC CE, if a PUCCH is transmitted in the subframe on the second cell. 
     Meanwhile, if the eNB is not aware of whether the other eNB configures simultaneous PUCCH-PUSCH transmission on the corresponding PCell or PSCell, the eNB cannot interpret the received extended PHR MAC CE. For example, assume that the MeNB configures simultaneous PUCCH-PUSCH transmission on PCell while the SeNB does not configure simultaneous PUCCH-PUSCH transmission on PSCell. 
     The UE will transmit the extended PHR MAC CE including Type 2 PH of PCell to the MeNB/SeNB (depending on trigger condition). Then, if the SeNB does not know whether the MeNB configures simultaneous PUCCH-PUSCH transmission on PCell, the SeNB cannot interpret the received extended PHR MAC CE. Therefore, it is needed that each eNB should inform the other eNB of configuration of simultaneous PUCCH-PUSCH for PCell/PSCell. There are many methods for informing the other eNB of configuration of simultaneous PUCCH-PUSCH for PCell/PSCell of the each eNB. It can be informed explicitly or it can be included information of other Type 2 PH mandatorily. For example, in the above assumption, when the UE will transmit the extended PHR MAC CE including Type 2 PH of PCell to the MeNB, the extended PHR MAC CE includes mandatorily Type 2 PH of PSCell without any condition (i.e. condition for whether or not simultaneous PUCCH-PUSCH transmission is allowed on PSCell), but it is not limited thereto. 
       FIG. 15  represents a case that multiple SCells served by the SeNB are configured to the UE. In this format, the UE constructs PHR MAC CE by including Type 2 PH first and then including Type 1 PH. 
     When the UE transmits power headroom reporting through the PHR MAC CE in a subframe, the PHR MAC CE includes a first group of Type 2 PH (Power Headroom) information (A) including a plurality of values of Type 2 PH information followed by a second group of Type 1 PH information (B) including a plurality of values of Type 1 PH information. 
     In detail, the PHR MAC CE includes a value of Type 2 PH information for the PCell ( 1501 ) followed by a plurality of values of Type2 PH information for respective SCells according to an increasing order of cell indices ( 1503 ), and the plurality of values of Type2 PH information ( 1503 ) followed by second group of Type 1 PH information (B). 
     Preferably, the plurality of values of Type2 PH information for respective multiple SCells ( 1503 ) are arranged in an increasing order of cell indices in the first group of Type 2 PH information (A). 
     For example, if a SCell 1 has index 1 and a SCell 2 has index 2, because index of SCell 1 is earlier than that of SCell 2, an octet containing a value of a Type 2 PH information for SCell 1 is followed by an octet containing a value of a Type 2 PH information of SCell 2. 
     Preferably, if the PCell supports simultaneous PUCCH-PUSCH transmission, a value of Type 2 PH information for the PCell is in the PHR MAC CE. And similarly, if the SCell supports simultaneous PUCCH-PUSCH transmission, a value of Type 2 PH information for the SCell is in the PHR MAC CE. 
     Assume that the MeNB configures simultaneous PUCCH-PUSCH transmission on PCell and the SeNB also configures simultaneous PUCCH-PUSCH transmission on multiple SCells. 
     The first group of Type 2 PH information (A) includes a first octet containing the value of the Type 2 PH information for the PCell ( 1501 ) is directly followed by the plurality of values of Type 2 PH information for the multiple SCells ( 1503 ) in the PHR MAC CE, if a PUCCH (Physical Uplink Control Channel) for the first cell is not transmitted in the subframe, and a first octet containing the value of the Type 2 PH information for the PCell ( 1501 ) is directly followed by a second octet containing a value of a maximum power of the PCell ( 1505 ), and the second octet containing a value of a maximum power of the PCell ( 1505 ) is directly followed by the plurality of values of Type 2 PH information for the multiple SCells ( 1503 ) in the PHR MAC CE, if a PUCCH (Physical Uplink Control Channel) for the first cell is transmitted in the subframe. 
     Preferably, the SCell for which the second octet contains the value of the Type 2 PH information has the earliest index among the multiple SCell, because the plurality of values of Type 2 PH information for respective multiple SCells are arranged in an increasing order of cell indices in the first group of Type 2 PH information (A). 
     The plurality of values of Type 2 PH information for the multiple SCells ( 1503 ) includes a first octet containing a value of the Type 2 PH information for SCell 1 ( 1507 ) is directly followed by a second octet containing a value of a maximum power of the SCell 1 ( 1509 ) in the PHR MAC CE, if a PUCCH (Physical Uplink Control Channel) is transmitted in the subframe on the SCell 1, and a first octet containing the value of the Type 2 PH information for the SCell 1 ( 1507 ) is directly followed by a second octet containing a value of the Type 2 PH information for SCell 2 ( 1511 ) in the PHR MAC CE, if a PUCCH (Physical Uplink Control Channel) for the first cell is not transmitted in the subframe. 
     And similarly, the plurality of values of Type2 PH information for respective multiple SCells are arranged in an increasing order of cell indices in the second group of Type 2 PH information (B). 
     Preferably, the second group of Type 1 PH information (B) includes a value of Type 1 PH information for the PCell ( 1513 ) followed by the plurality of values of Type 1 PH information for respective multiple SCells according to an increasing order of cell indices ( 1515 ). 
     Meanwhile, the PHR MAC CE further includes an octet ( 1517 ) containing cell indices information followed by the first group of Type 2 PH information. The octet ( 1517 ) is indicates a presence of Type 2PH per SCell. 
       FIG. 16  represents a case that multiple SCells served by the SeNB are configured to the UE. Type 2 PH of PSCell is included before the octet containing Type 1 PH of PSCell 
     The PHR MAC CE format is generated by including PH related information per serving cell. For each activated serving cell with configured uplink (i.e. PUSCH), the UE includes Type 1 PH in the PHR MAC CE. The UE includes further the Type 1 PH related P CMAX,c , Type 2 PH, and Type 2 related P CMAX,c , depending on the PUSCH transmission, support of simultaneous PUCCH-PUSCH transmission, and the PUCCH transmission, respectively. Other fields, i.e. P, V, and R fields are set according to prior art. 
     For example, if SCell 1 is configured with PUSCH and is activated when PHR is triggered, the UE sets 
     C1=1 
     Include PH (Type 1, SCell 1) 
     Include P CMAX,c  for Type 1 PH if the UE has UL resources allocated for PUSCH transmission on the SCell 1 for this TTI 
     Include PH (Type 2, SCell 1) if the SCell 1 is configured with simultaneous PUCCH-PUSCH. 
     Include P CMAX,c  for Type 2 PH if the UE has a PUCCH transmission in this TTI. 
     The same rule applies to all other serving cells. 
     Regarding  FIG. 16 , octets containing PH information including Type 1 PH information and Type 2 PH information for the PCell is followed by octets containing PH information Type 1 PH information and Type 2 PH information for SCells. 
     If a SCell 1 has index 1 and a SCell 2 has index 2, because index of SCell 1 is earlier than that of SCell 2, an octet containing a value of a Type 2 PH information for SCell 1 is followed by an octet containing a value of a Type 2 PH information of SCell 2. 
     Between  FIG. 15  an  FIG. 16 , there is no difference in terms of future extendibility or simplicity. However, in the current specification, it is specified that Type 2 PH field is located in the first place after the Ci field octet. In this sense, a structure of  FIG. 15  seems to be aligned with the current specification, and the structure of  FIG. 15  is easier to decode than a structure of  FIG. 16 . 
       FIG. 17  is a block diagram of a communication apparatus according to an embodiment of the present invention. 
     The apparatus shown in  FIG. 17  can be a user equipment (UE) and/or eNB adapted to perform the above mechanism, but it can be any apparatus for performing the same operation. 
     As shown in  FIG. 17 , the apparatus may comprises a DSP/microprocessor ( 110 ) and RF module (transmiceiver;  135 ). The DSP/microprocessor ( 110 ) is electrically connected with the transceiver ( 135 ) and controls it. The apparatus may further include power management module ( 105 ), battery ( 155 ), display ( 115 ), keypad ( 120 ), SIM card ( 125 ), memory device ( 130 ), speaker ( 145 ) and input device ( 150 ), based on its implementation and designer&#39;s choice. 
     Specifically,  FIG. 17  may represent a UE comprising a receiver ( 135 ) configured to receive a request message from a network, and a transmitter ( 135 ) configured to transmit the transmission or reception timing information to the network. These receiver and the transmitter can constitute the transceiver ( 135 ). The UE further comprises a processor ( 110 ) connected to the transceiver ( 135 : receiver and transmitter). 
     Also,  FIG. 17  may represent a network apparatus comprising a transmitter ( 135 ) configured to transmit a request message to a UE and a receiver ( 135 ) configured to receive the transmission or reception timing information from the UE. These transmitter and receiver may constitute the transceiver ( 135 ). The network further comprises a processor ( 110 ) connected to the transmitter and the receiver. This processor ( 110 ) may be configured to calculate latency based on the transmission or reception timing information. 
     It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents. 
     The embodiments of the present invention described herein below are combinations of elements and features of the present invention. The elements or features may be considered selective unless otherwise mentioned. Each element or feature may be practiced without being combined with other elements or features. Further, an embodiment of the present invention may be constructed by combining parts of the elements and/or features. Operation orders described in embodiments of the present invention may be rearranged. Some constructions of any one embodiment may be included in another embodiment and may be replaced with corresponding constructions of another embodiment. It is obvious to those skilled in the art that claims that are not explicitly cited in each other in the appended claims may be presented in combination as an embodiment of the present invention or included as a new claim by subsequent amendment after the application is filed. 
     In the embodiments of the present invention, a specific operation described as performed by the BS may be performed by an upper node of the BS. Namely, it is apparent that, in a network comprised of a plurality of network nodes including a BS, various operations performed for communication with an MS may be performed by the BS, or network nodes other than the BS. The term ‘eNB’ may be replaced with the term ‘fixed station’, ‘Node B’, ‘Base Station (BS)’, ‘access point’, etc. 
     The above-described embodiments may be implemented by various means, for example, by hardware, firmware, software, or a combination thereof. 
     In a hardware configuration, the method according to the embodiments of the present invention may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), processors, controllers, microcontrollers, or microprocessors. 
     In a firmware or software configuration, the method according to the embodiments of the present invention may be implemented in the form of modules, procedures, functions, etc. performing the above-described functions or operations. Software code may be stored in a memory unit and executed by a processor. The memory unit may be located at the interior or exterior of the processor and may transmit and receive data to and from the processor via various known means. 
     Those skilled in the art will appreciate that the present invention may be carried out in other specific ways than those set forth herein without departing from the spirit and essential characteristics of the present invention. The above embodiments are therefore to be construed in all aspects as illustrative and not restrictive. The scope of the invention should be determined by the appended claims and their legal equivalents, not by the above description, and all changes coming within the meaning and equivalency range of the appended claims are intended to be embraced therein. 
     INDUSTRIAL APPLICABILITY 
     While the above-described method has been described centering on an example applied to the 3GPP LTE system, the present invention is applicable to a variety of wireless communication systems in addition to the 3GPP LTE system.