Method and apparatus for power headroom reporting procedure for new radio carrier aggregation

Abstract

The present application relates to methods and apparatuses for power headroom reporting procedures for new radio carrier aggregation. The methods and apparatuses provide power headroom reporting procedures for new radio carrier aggregation, such as 5G. Communication can be conducted on a first component carrier (CC) having a first transmission time interval (TTI) and a second CC having a second TTI. It can be ascertained that a power headroom report (PHR) has been triggered for at least one selected from the first CC and the second CC. An uplink grant corresponding to an uplink transmission on the first CC can be received. A first PHR reference TTI corresponding to the uplink transmission on the first CC can be determined. A first PHR for the first CC can be generated based on the first PHR reference TTI. A second PHR reference TTI on the second CC can be determined. A second PHR for the second CC can be generated based on the second PHR reference TTI. The first PHR and the second PHR can be transmitted in the uplink transmission.

Description

[0001] This application is a divisional of application No. 201880019338.8, filed in China on February 28, 2018, which claims the benefit of PCT Application No. PCT / US2018 / 020280, an international filing date of February 28, 2018, and priority to U.S. Nonprovisional Application No. 15 / 882, 1 10, filed on January 31, 2018, the contents of which are incorporated herein by reference in their entirety. TECHNICAL FIELD

[0002] The present disclosure relates to a method and apparatus for power headroom reporting procedure for new radio carrier aggregation, such as 5G. BACKGROUND

[0003] Currently, user equipment (UE), such as user wireless communication devices, communicate with other communication devices using wireless signals. To support various requirements of different services including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine type communication (mMTC), it is envisioned that 5G / New Radio (NR) supports different orthogonal frequency division multiplexing (OFDM) numerologies, such as subcarrier spacing (SCS) and cyclic prefix (CP) length, in a single framework.

[0004] As described in the Third Generation Partnership Project (3GPP) Technical Report (TR) 38.913, various use cases / deployment scenarios of NR have different requirements in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates of 20 Gbps for downlink and 10 Gbps for uplink, and user experienced data rates that are three times the data rates provided by International Mobile Telecommunications (IMT) Advanced. On the other hand, in the case of URLLC, more stringent requirements are for ultra-low latency, such as 0.5 ms user plane latency for each of UL and DL, and high reliability, such as 1 -10 -5 ) probability of packet not passing within 1 ms. Finally, mMTC requires high connection density, large coverage in poor environments, and very long battery life for low cost devices. Thus, OFDM numerologies, such as subcarrier spacing, OFDM symbol duration, CP duration, and number of symbols per scheduling interval, that are suitable for one use case can not be suitable for another.

[0005] For example, low latency services can require shorter symbol duration and thus larger subcarrier spacing and / or fewer symbols per scheduling interval (such as a transmission time interval (TTI)) compared to mMTC services. Furthermore, deployment scenarios with large channel delay spread require longer CP duration compared to scenarios with short delay spread. The subcarrier spacing should thus be optimized to keep similar CP overhead. It is agreed to study different numerologies across different carriers for a given UE and different numerologies within the same carrier for a given UE. For example, multiplexing different OFDM numerologies in the frequency and / or time domain within the same carrier or across different carriers. This facilitates simultaneous support of services with very different requirements, such as ultra-low latency communications with short symbols and thus wide subcarrier spacing and multimedia broadcast / multicast service (MBMS) services with long symbols enabling long cyclic prefix and thus narrow subcarrier spacing.

[0006] In Long Term Evolution (LTE), the UE reports extended power headroom reports (PHRs) for carrier aggregation. For example, the power headroom (PH) information for each activated serving cell is included with Pc max. Because the subframe / TTI length is the same for all carriers in LTE, the PHR reporting subframes (such as the subframes to which the power headroom information refers) are aligned. However, for NR, because different numerologies are supported, one slot / TTI of a carrier can overlap with multiple slots / TTIs of another carrier. For example, eMBB on one carrier can overlap with URLLC on another carrier. In this case, a 5G Node B (gNB) such as a 5G base station will not know which slot the power headroom information refers to when receiving an extended PHR. For example, in a scenario where an extended PHR report is triggered and then transmitted in a slot / TTI that overlaps with multiple slots / TTIs on a different carrier, the gNB will not know which overlapping slot / TTI is the reference for PH computation. It can thus base its future scheduling decisions on the wrong assumptions, such as how close the UE is operating under power limitations, which can result in power scaling or underutilization of resources. BRIEF DESCRIPTION OF DRAWINGS

[0007] In order to describe the manner in which the advantages and features of the disclosure can be obtained, a description of the disclosure will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. These drawings depict only example embodiments of the disclosure and are therefore not to be considered limiting of its scope. For the purposes of clarity, the drawings have not been drawn to scale and some elements can have been exaggerated or simplified.

[0008] Figure 1 is an example block diagram of a system in accordance with possible embodiments.

[0009] Figure 2is an example illustration showing scenarios for power headroom reporting subframes and uplink grants for different component carriers according to possible embodiments;

[0010] Figure 3 and 4 is an example scenario when the slot / transmission time interval boundaries of component carriers are not aligned according to possible embodiments;

[0011] Figure 5 is an example flow chart for illustrating the operation of an apparatus according to possible embodiments; and

[0012] Figure 6 is an example block diagram of an apparatus according to possible embodiments. DETAILED DESCRIPTION

[0013] Embodiments provide methods and apparatuses for power headroom reporting procedures for new radio (NR) carrier aggregation, such as 5G. According to possible embodiments, communication can be conducted on a first component carrier (CC) having a first transmission time interval (TTI) and a second CC having a second TTI. It can be ascertained that a power headroom report (PHR) has been triggered for at least one selected from the first CC and the second CC. An uplink grant corresponding to an uplink transmission can be received on the first CC. A first PHR reference TTI corresponding to the uplink transmission on the first CC can be determined. A first PHR for the first CC can be generated based on the first PHR reference TTI. A second PHR reference TTI on the second CC can be determined. A second PHR for the second CC can be generated based on the second PHR reference TTI. The first PHR and the second PHR can be transmitted in the uplink transmission.

[0014] Figure 1 is an example block diagram of a system 100 according to possible embodiments. The system 100 can include a user equipment (UE) 110, base stations 120 and 130, and a network 130. The UE 110 can be a wireless wide area network communication device, a wireless terminal, a portable wireless communication device, a smart phone, a cellular telephone, a flip phone, a personal digital assistant, a personal computer, a selective call receiver, a tablet computer, a laptop computer, an Internet of Things (IoT) device, or any other user equipment capable of transmitting and receiving communication signals over a wireless network. At least one of the base stations 120 and 130 can be a wireless wide area network base station, a Node B, an enhanced Node B (eNB), a 5G Node B (gNB) such as for NR, an unlicensed network base station, an access point, or any other base station that can provide wireless access between UEs and a network.

[0015] The network 140 can include any type of network capable of transmitting and receiving wireless communication signals. For example, the network 140 can include a wireless communication network, a cellular telephone network, a time division multiple access (TDMA)-based network, a code division multiple access (CDMA)-based network, an orthogonal frequency division multiple access (OFDMA)-based network, a long term evolution (LTE) network, a third generation partnership project (3GPP)-based network, a 4G network, a 5G NR network, a satellite communication network, a high altitude platform network, the Internet, and / or other communication networks. In operation, the UE 110 can communicate with other devices through the network 140 by transmitting signals to and receiving signals from the base stations 120 and 130 over the component carriers 122, 124, 132.

[0016] Uplink transmit power control in a mobile communication system such as the system 100 serves the purpose of balancing the need for sufficient transmitter energy per bit to achieve a desired quality of service (QoS) with the need to minimize interference to other users of the system and to maximize the battery life of the UE 110. To achieve these goals, uplink power control can adapt to radio propagation channel conditions including path loss, shadowing, and fast fading fluctuations, while limiting other user interference impact from within the cell and from neighboring cells. The 3GPP has adopted a power control scheme for LTE that allows full or partial compensation for path loss and shadowing. This functionality enables users with higher path loss to operate at lower SINR requirements so that they are more likely to cause less interference to neighboring cells. The power control scheme used in LTE employs a combination of open loop and closed loop control. The open loop part compensates for slow channel variations according to signal strength measurements (e.g., path loss measurements) performed by the terminal. The closed loop part, on the other hand, directly controls the power of the UE using, for example, explicit transmit power control (TPC) commands in the downlink to optimize system performance. This can control interference and fine-tune the power settings to adapt to channel conditions including fast fading.

[0017] Detailed power control formulas are specified in Section 5.1 of the Third Generation Partnership Project (3GPP) Technical Specification (TS) 36.213 for the physical uplink shared channel (PUSCH), the physical uplink control channel (PUCCH), and the sounding reference signal (SRS). For example, the setting of the transmit power of a physical uplink shared channel (PUSCH) transmission by the UE 110 in subframe i on the serving cell c is defined as follows:

[0018]

[0019] where P CMAX,cmay be the configured UE transmit power defined by the serving cell c in subframe i. For LTE 8 / 9, there can be only one serving cell. Thus, in the above equation, P CMAX,c may be replaced by P CMAX For other variables this can also be done. For example, M PUSCH,c may be replaced by M PUSCH and so on. In Rel-10, support for multiple serving cells, also referred to as carrier aggregation, was introduced. M PUSCH,c may be the number of physical resource blocks (PRBs) allocated to the UE 110. The more PRBs allocated to the UE 110, the greater the required UE transmit power. P O_PUSCH,c may be the target received power, a c may be a path loss compensation factor, and PL c may be the path loss between the UE 110 and its serving base station, such as the base station 120. Delta TF,c and f c (i) can be closed loop power control parameters representing modulation and coding scheme (MCS) related parameters and transmission power control (TPC) commands, respectively.

[0020] The equations for each of these uplink signals, PUSCH, PUCCH, SRS, can follow the same basic principle, where in all cases they can be seen as the sum of two main terms: a basic open loop operating point, which is sourced from static or semi-static parameters signaled by the base station 120, and a dynamic offset, which is updated from subframe to subframe. The base station 120 can also be referred to here as eNB 120 and / or gNB 120, depending on the context of the reference.

[0021] To help the eNB 120 schedule uplink transmission resources to different UEs in an appropriate manner, the UE 110 can report its available power headroom to the eNB 120. The eNB 120 can determine from the received power headroom report how much of the uplink bandwidth per subframe the UE 110 is able to use, such as how close the UE 110 operates to its transmission power limit. The power headroom indicates the difference between the UE maximum uplink transmit power for uplink shared channel (UL-SCH) transmission and the estimated power. For Rel-8 / 9, the UE power headroom (in dB) valid for subframe i can be defined by:

[0022] PH(i) = P CMAX - {10 · log10(M PUSCH (i)) + P 0_PUSCH (j) + a(j) · PL + Delta TF (i) + f(i)}

[0023] where PCMAX Pcmax can be the total maximum UE transmit power and can be the value of Pcmax selected by the UE 110 within a given range of Pcmax according to the following constraints: CMAX_L Pcmax < Pmax CMAX_H and P

[0024] Pcmax < Pmax CMAX_L Pcmax < Pmax CMAX Pcmax < Pmax CMAX_H

[0025] Pcmax < Pmax CMAX_L Pcmax < Pmax EMAX Pcmax < Pmax PowerClass Pcmax < Pmax TC Pcmax < Pmax

[0026] Pcmax < Pmax CMAX_H Pcmax < Pmax EMAX Pcmax < Pmax PowerClass Pcmax < Pmax

[0027] Pcmax < Pmax EMAX Pcmax can be a value signaled by the network 140, and ATC, MPR, and AMPR can be specified in 3GPP TS 36.101. MPR can be a power reduction value used to control the adjacent channel leakage power ratio (ACLR) associated with various modulation schemes and transmission bandwidths. AMPR, such as A-MPR, can be an additional maximum power reduction. It can be a band-specific value and can be applied by the UE 110 when configured by the network.

[0028] The range of the power headroom report can be +40 to -23 dB. The negative part of the range can enable the UE 110 to signal to the eNB 120 the extent to which it would need more transmission power than available to the UE 110 to receive the UL grant. This can enable the eNB 120 to reduce the amount of uplink resources in the subsequent grant, thereby freeing transmission resources that can be allocated to other UEs thereafter.

[0029] The power headroom report (PHR), such as a PHR medium access control (MAC) control element (CE), can be transmitted only in subframes in which the UE 110 has valid uplink resources, such as PUSCH resources. The report can be related to the subframe in which it is transmitted. Thus, the PHR can be an estimate rather than a direct measurement. For example, for a subframe in which the report is to be transmitted, the UE 110 can not directly measure its actual transmission power headroom.

[0030] A number of criteria can be defined to trigger PHR. Such criteria can include a significant change in estimated path loss since the last PHR was sent (such as exceeding a configured threshold), can be periodic power headroom reporting, and can be other criteria. The eNB 120 can configure parameters to control each of these triggers according to system load and needs of its scheduling algorithm. The PHR can be sent as a MAC control element (CE). For Rel-8 / 9, it can include a single octet, where the two highest bits can be reserved and the six lowest bits can represent the 64 dB values in 1 dB steps. For details of the PHR MAC CE, refer to TS 36.321, section 6.1.3.6.

[0031] For the case of carrier aggregation as a Rel-10 feature, there is one independent power control loop for each UL component carrier / serving cell configured for the UE 110. As mentioned above, the setting of the UE transmit power for PUSCH transmission in subframe i on serving cell c is defined as follows:

[0032]

[0033] Further details related to the power control formula for PUSCH, PUCCH, and SRS can be found in TS 36.213.

[0034] Since UL power control is operated per component carrier / serving cell, power headroom can also be reported per component carrier / serving cell, i.e., PH = PHc CMAX,c - estimated PUSCH power. For the case of carrier aggregation, there are basically two defined power limits, the total maximum UE transmit power P Cmax and the component carrier specific maximum transmit power P CMAX,c . Further information related to the definition of the component carrier specific maximum transmit power and the UE total maximum transmit power can be found in TS 36.101. For carrier aggregation, simultaneous PUSCH-PUCCH transmission is supported. An additional power headroom type can indicate the difference between P CMAX,c and the estimated PUSCH + PUCCH TX power. Therefore, two different types of PH are reported for CA:

[0035] PH Type 1 : P CMAX,c - estimated PUSCH power

[0036] PH Type 2 : P CMAX,c - estimated PUSCH + PUCCH power

[0037] PH Type 2 can only apply to the primary cell PCell, while PH Type 1 can be reported to both the PCell and the secondary cell SCell. The PHR can take into account the maximum power reduction (MPR). In other words, the power reduction applied by the UE 110 can be considered in the component carrier specific maximum transmission power P CMAX,c . It should be noted that the eNB 120 can not be aware of the power reduction applied by the UE 110, since the actual power reduction depends on the allocation type, the standardized MPR values, and also on the UE implementation. Thus, the eNB 120 can not be aware of the component carrier specific maximum transmission power with respect to which the UE 110 calculates the power headroom. In particular, the eNB 120 can not accurately know the extent to which the UE 110 operates close to its total maximum transmission power P CMAX . Thus, there can be cases where the UE 110 exceeds the total user equipment maximum transmission power P CMAX that would require power scaling. Therefore, in Rel-10, a new power headroom MAC control element, also referred to as extended PHR MAC CE, can be used. Since it can be beneficial for the eNB 120 to always be aware of the power situation of all activated uplink carriers / serving carriers for future uplink scheduling, the new extended power headroom MAC CE can include the power headroom information (Type 1 / Type 2) for each activated uplink component carrier. Whenever the PHR is triggered on any configured serving cell / component carrier, the UE 110 can send the extended PHR MAC CE, which can contain information for all serving cells.

[0038] Furthermore, the UE 110 can not only report the power headroom value of a component carrier, but also the corresponding P CMAX,c value. When the power headroom report is triggered, the UE can send the extended power headroom MAC control element on one of the serving cells, such as the PCell and Scell, with valid uplink resources for PUSCH. Type 1 and Type 2 PH can be calculated based on some predefined reference format without sending PUSCH and PUCCH. The corresponding PH report can also be referred to as virtual PHR. For example, PH can be calculated using some virtual PUSCH and / or PUCCH transmission, respectively. Further details of the extended power headroom MAC control element can be found in section 6.1.3.6a of the standard TS 36.321.

[0039] Dual connectivity (DC) introduced in Rel-12 can allow a UE to simultaneously receive data from different eNBs in order to improve performance in a heterogeneous network with dedicated carrier deployment. In more detail, a UE in RRC_CONNECTED state can be configured to utilize radio resources provided by two different schedulers located in two eNBs connected through an interface, also referred to as X2 interface.

[0040] There can be a master eNB (MeNB) and one or more secondary eNBs (SeNBs). In LTE Release 12 specifications, only the case of one MeNB and one SeNB is considered. The set of serving cells associated with the MeNB can be referred to as the master cell group (MCG), while the set of serving cells associated with the SeNB can be referred to as the secondary cell group (SCG). The scheduling of uplink transmissions in dual connectivity can be more challenging compared to carrier aggregation, since scheduling decisions made in the MeNB and SeNB cannot be immediately coordinated due to the non-ideal interface between the two schedulers. As a result, it is easy to have cases where scheduling grants from the MeNB and SeNB can cause the maximum transmission power of the UE to be exceeded, which leads to power scaling. To avoid these cases, minimum guaranteed powers for the cell groups have been introduced, such as P_MCG for the MCG and P_SCG for the SCG, respectively. In more detail, the guaranteed minimum power level for a cell group can be configured as a percentage of the maximum UE transmission power P CMAX . The sum of the minimum guaranteed power levels for the two cell groups can be equal to or less than P CMAX . For the case of P_MCG + P_SCG < P CMAX , the remaining power not dedicated to a particular cell group can be dynamically allocated to the MCG or SCG according to the scheduling decisions. In the case where transmission in one of the cell groups requires less than the minimum guaranteed power, power can be allocated to the other cell group.

[0041] Dual connectivity can be used in both synchronous and asynchronous networks. To account for both network deployments, Rel-12 introduced two power control modes. In particular, power control mode 1 (PCM1) can be used in synchronous networks, while PCM2 can be used in asynchronous networks. All Rel-12 should support PCM 1. For UEs that also support PCM2 for asynchronous networks, the eNB can configure which power control mode to use. For PCM1, the remaining power P CMAX- (P_MCG + P_SCG) is allocated to MCG and / or SCG. Basically, the highest priority can be given to Hybrid Automatic Repeat Request (HARQ) feedback and Scheduling Request (SR) transmission. The second highest priority can be given to Channel State Information (CSI), followed by PUSCH transmission without Uplink Control Information (UCI), and finally Sounding Reference Signal (SRS) transmission. In case of same UCI type transmission for MCG and SCG, MCG transmission can be prioritized. Further details related to PCM1 for dual connectivity can be found in TS 36.213 section 5.1.4.

[0042] In case of asynchronous network, the subframe boundary can not be aligned between MCG and SCG transmission. Because the UE 110 cannot process the received uplink grant for other CGs fast enough when determining its own cell group's transmission power, the UE 110 can not take into account the transmission power required for PUSCH / PUCCH transmission on other cell groups for overlapping symbols. Therefore, for PCM2, the remaining power can be simply allocated to the transmission which starts earlier. Further details related to PCM2 can be found in TS 36.213 section 5.1.4.

[0043] In dual connectivity when PHR has been triggered, the UE 110 can send the power headroom information of all activated cells (including serving cells of both cell groups) to the eNB 120. When the UE 110 reports PH information for SCG cells to MeNB or for MCG cells to SeNB, Type 2 PH information for PUCCH cells, sPUCCH of SCG can always be included. The power headroom information of serving cells in other CGs can be configured by eNB or calculated based on some reference format (such as virtual PHR) or based on actual PUSCH / PUCCH transmission.

[0044] According to possible embodiments, the power headroom reference time slot / Transmission Time Interval (TTI) can be defined for the case of aggregated carriers with different numerologies. Any overlapping time slot / TTI can be defined as the reference time slot / TTI for power headroom calculation. The gNB 120 can know which time slot / TTI the power headroom calculation is based on so that it can correctly interpret the received PHR.

[0045] Figure 2This is an example illustration of scenario 200, showing PHR report TTI and uplink clearance for different component carriers CC1, CC2, and CC3 according to a possible embodiment, where TTI is referred to as a subframe. In this scenario 200, UE 110 can be configured with three component carriers / serving cells, each with a different parameter set / TTI length. Based on some defined standards, the TTI... N-3 Previously triggered PHR, and TTI on the first carrier (CC1) N Send PHR in the middle.

[0046] Because of the TTI on CC1 N TTI across CC2 i To TTI i+3 And the TTI on CC3 s To TTI s+1 Therefore, a PHR reference TTI should be defined to ensure that the gNB 120 correctly interprets the received PHR. More specifically, for example, this could be based on whether a TTI has been defined. i ,、TTI i+1 TTI i+2 Or TTI i+3 The PH information of CC2, as reported in the extended PHR MAC CE on CC1, was calculated to define the reference TTI.

[0047] From a technical perspective, there are some reasons for defining the reference TTI in a particular way, as outlined below, even though, as mentioned above, it is usually sufficient to define rules on how to determine the reference TTI for PHR calculations.

[0048] Because power margins (such as the UL power estimated based on the license) can be calculated based on the received UL license when there are different TTI lengths and potentially different (HARQ) timing relationships (such as from UL license to corresponding UL transmission), it is possible that UE 110 may not know whether there will be some uplink transmissions in the reference slots / TTIs / subframes on other carriers when generating extended PHR MAC CE. When calculating power margin information, UE 110 may not be able to process UL licenses for overlapping slots / TTIs on other carriers quickly enough. As an example related to scenario 200, when in TTI... N When generating the extended PHR MAC CE for transmission on CC1, the UE may not be aware of the TTI on CC2. i+3 The PHR reference in the text corresponds to the TTI. i+1 TTI holds a UL license. i+3may not be a good choice as PHR reference TTI. According to this example, if the PHR reference TTI is defined as the TTI i+3 with the last overlapping TTI, the corresponding uplink grant can be received in the TTI i+1 . In this implementation, the scenario 200 can be an example where the UL grant in the TTI i may correspond to the uplink transmission in the TTI i+2 .

[0049] In view of the above considerations, according to this embodiment, the reference TTI for PH computation can be defined as the first overlapping TTI as shown in the scenario 200. The detailed UE 110 behavior according to this embodiment can include the following: when the power headroom procedure has determined that at least one PHR has been triggered in the TTI N-2 on CC1 (where the uplink grant has been received) and the corresponding uplink transmission occurs in the TTI N on CC1, the UE 110 can start generating the extended PHR MAC CE. To do so, the UE 110 can first determine the PHR reference time slots / TTIs for the other activated component carriers / serving cells, i.e. the TTI i on CC2 and the TTI S on CC3 according to this embodiment. In addition, the UE 110 can determine the time slots / TTIs where the UL grant associated with each PHR reference TTI occurs, i.e. the TTI i-2 on CC2 and the TTI s-2 on CC3. The UE 110 can monitor the PDCCH (UL grant) in those time slots / TTIs in order to know whether a transmission will occur in the PHR reference TTI and thus be able to compute the power headroom for the reference TTI. Thereafter the UE 110 can compute the power headroom for the TTI N on CC1, the power headroom for the TTI i on CC2, and the power headroom for the TTI s on CC3, and generate the PHR MAC CE transmitted in the TTI N on CC1.

[0050] The definition of the PHR reference TTI according to this embodiment can ensure that the UE can take into account the corresponding UL grants of the other carriers / serving cells for computing the extended PHR MAC CE. However, this can still be the case where the timing can be too tight to handle and the UE 110 can report a virtual PHR for the other cells / component carriers. For example, the uplink grants on the other cells can not be taken into account for PH computation.

[0051] Referring again to the scenario 200, it is preferable from the UE 110's perspective to transmit the extended power headroom report MAC CE on CC3 in the TTI S instead of on CC1 in the TTI i The reason is that the UE 110 can already know the uplink grant received on CC1 in the TTI N-2 when calculating the power headroom report MAC CE for transmission on CC3, and can also take into account the potential UL grant received on CC2 in the TTI i-2 Typically, the UE 110 can transmit the extended PHR MAC CE on the carrier that allows the UE 110 to take into account the uplink grants on other carriers / serving cells, such as the shortest time duration between the uplink grant and the corresponding uplink transmission.

[0052] As outlined above, due to the support of multiple numerologies across serving cells and within a serving cell, there can be different timing relationships between the UL grant and the corresponding uplink transmission for different component carriers / serving cells. Thus, when calculating the PH information for transmission of the PHR MAC CE, it can happen that the UE 110 can not process and take into account all potential uplink grants associated with the PHR reference TTI of all serving cells. As another example related to the scenario 200, the UE 110 can not be able to take into account the potential uplink transmission in the TTI i on CC2 because the potential UL grant is received in the TTI i-2 when calculating the PH information of all three component carriers / serving cells for generating the extended PHR MAC CE transmitted on CC1 in the TTI N Although the scenario 200 shows one exemplary grant on CC2 to illustrate the timing relationship between the UL grant and the corresponding uplink transmission, in this example, because the reference PHR TTI of CC2 is TTI i according to one embodiment, the corresponding uplink grant can be received in the TTI i-2 According to this embodiment, for the case where the UE 110 is not able to determine whether there is an uplink transmission in the PHR reference TTI of any activated serving cell when generating the PHR MAC CE, the power headroom can be calculated without the assumption of an uplink transmission. For example, a virtual PH can be reported for the corresponding serving cell.

[0053] For NR, an unlicensed uplink transmission mode is supported, where uplink resources are pre-allocated to UE110, similar to semi-persistent scheduling (SPS) operations in LTE, thus avoiding the need to send a scheduling request and wait for uplink permission before being able to send uplink transmissions. The unlicensed transmission mode can be used for very latency-critical services like URLLC. Because UE110 can have a valid uplink permission for each TTI (e.g., in the case where the SPS period is set to one TTI), UE110 can use only the allocated resources and perform uplink transmissions when uplink data is available for transmission. If no data is available for transmission, UE110 can skip uplink transmission opportunities, such as ignoring the uplink permission. Similar to the embodiment just described above, when generating the content of the extended PHRMAC CE, UE110 may not be able to determine whether an uplink transmission for the unlicensed transmission mode exists in the PHR reference TTI (e.g., depending on data availability), and UE110 can ignore or comply with the UL permission. In this scenario, according to this embodiment, UE 110 can assume that no uplink transmission is taking place. For example, a virtual PH can be reported for the corresponding serving cell.

[0054] Figure 3 and 4 These are example scenarios 300 and 400 illustrating possible embodiments where the slot / TTI / boundaries of CC1 and CC3 are not aligned. For example, for NR CA, even if symbol timings can be aligned across different carriers / serving cells, slot / TTI boundaries may still be misaligned. For the situation depicted in scenarios 300 and 400, a reference PHR TTI can be defined. As shown in scenario 400, according to this embodiment, the PHR reference TTI can be defined as the first fully overlapping TTI (such as the TTI on CC3). s+1 TTI on CC2 i For example, selecting the TTIs of CC3 as the reference TTI can mean that the reference TTI is greater than the TTI of the PHR transmission (such as the TTI on the avoidable CC1 according to this embodiment). N (In the middle) it starts earlier. For the same reason, in scenario 300, the PHR reference TTI of CC1 can be defined as TTI. N For example, the PHR reference TTI may not start earlier than the TTI for sending the PHR MAC CE.

[0055] According to another embodiment, the UE 110 can always calculate the power headroom for the component carriers / serving cells for which the PHR MAC CE is not sent based on some reference format, such as used as a pre-defined resource allocation. Taking the scenario 200 as an example, according to this embodiment, the UE 110 can calculate the PH for CC1 based on the actual uplink transmission, e.g. the PHR MAC CE can be sent on CC1, and the UE 110 can calculate the PH for CC2 and CC3 based on a reference format, such as using a virtual PHR. This embodiment can allow to simply calculate the power headroom information for all active carriers / serving cells from a processing power perspective. For example, it can not be dependent on different timing relations / TTI lengths due to different numerologies used on the carriers. According to a possible implementation, the network 140 can configure whether the PH for the component carriers / serving cells for which the PHR MAC CE is not sent is calculated based on the actual uplink transmission or based on some reference format / allocation.

[0056] Parameter set specific power control parameters can also be supported. For example, in order to meet the stringent reliability requirements of URLLC traffic, the parameters P0_PUSCH and / or a can be configured differently for the numerology used for URLLC compared to the numerology used for eMBB. For a power headroom report calculated based on a reference transmission / format, such as a virtual PHR, the gNB 120 can know which uplink power control parameters the UE 110 is using for the calculation in order to correctly interpret the PH information. Thus, according to this embodiment, a pre-defined numerology can be used for calculating the virtual PHR. According to one implementation, the UE 110 can use a reference numerology for the component carriers / serving cells to calculate the power headroom based on the reference transmission / format. The UE can have one reference numerology in a given NR carrier, which can define the subframe duration of the given NR carrier.

[0057] According to another embodiment, the serving cells / carriers for NR CA can be grouped into several power headroom reporting groups. For example, according to one implementation, the serving cells with the same numerology or TTI length can be grouped together. Because the timing granularity can be the same between the serving cells / carriers within a PHR group, the PHR report of a PHR group can be similar to the LTE CA case. The network 140 can configure the UE 110 with different PHR grouping information. The UE 110 can send the power headroom information for all activated serving cells of a PHR group, such as an extended PHR MAC CE per PHR group. The PH report, such as the PHR MAC CE, can be sent on any serving cell of the PHR group using the available uplink resources.

[0058] There can be PHR triggering conditions defined per PHR group. For example, a PHR can be triggered for a PHR group in case the triggering condition is met for at least one serving cell included in the PHR group. Alternatively, the triggering condition is common for all serving cells / carriers regardless of the PHR group. Because for NR a UE can aggregate serving cells / carriers from different frequency bands such as high frequency carriers above 6 Ghz and low frequency carriers below 6 Ghz, where the radio channel conditions are very different, there is one dl-PathlossChange value defined per PHR reporting group under the assumption that the HF carriers and LF carriers are grouped in different PHR groups.

[0059] According to another additional embodiment, when a PHR of one PHR group is triggered, the PHR trigger can be propagated to other PHR groups. This propagation of PHR trigger can ensure that PHRs of all PHR groups are sent when any PHR in a PHR group is triggered.

[0060] Because there can be different parameter settings for different beam links, the path loss can also be very different when the beam link is changed. According to another additional embodiment, when a beam link / pair is changed and this is informed to the gNB, the UE can also trigger a PHR (because the channel condition can also change significantly when the beam link is changed). According to one embodiment, the PHR is reported with information related to the beam link / pair.

[0061] Figure 5 is an example flowchart 500 for illustrating the operation of an apparatus, such as UE 110, in accordance with possible embodiments. At 510, communication can be conducted on a first component carrier having a first TTI and a second component carrier having a second TTI. The second TTI can be different or the same as the first TTI. At 520, it can be ascertained that a PHR has been triggered for at least one of the first component carrier and / or the second component carrier.

[0062] At 530, a first uplink grant corresponding to a first uplink transmission on the first component carrier can be received. At 540, a first PHR reference TTI corresponding to the first uplink transmission on the first component carrier can be determined. The first PHR reference TTI can be a TTI for which the first uplink grant grants the first uplink transmission on the first component carrier. At 550, a first PHR for the first component carrier can be generated based on the first PHR reference TTI.

[0063] At 560, a second PHR reference TTI on the second component carrier can be determined. According to a possible implementation, the first PHR reference TTI can start at a first time, the uplink transmission can be a first uplink transmission, and the second PHR reference TTI can be a first overlapping TTI on the second component carrier, where the first PHR reference TTI overlaps the second PHR reference TTI. For example, the second PHR reference TTI can be the first overlapping TTI on the second component carrier, where the first uplink transmission overlaps the second PHR reference TTI. According to another possible implementation, the second PHR reference TTI can start at a second time, where the first time of the first PHR reference TTI can be before the second time. According to another possible implementation, the second PHR reference TTI can be an overlapping TTI, where one of the first uplink transmission and the second uplink transmission fully overlaps the other of the first uplink transmission and the second uplink transmission. According to another possible implementation, the second PHR reference TTI can be the first overlapping TTI on the second component carrier, where one of the first PHR reference TTI and the second PHR reference TTI fully overlaps the other of the first PHR reference TTI and the second PHR reference TTI.

[0064] At 570, an uplink grant TTI in which a second uplink grant can be received can be determined. The second uplink grant can correspond to the second uplink transmission in the second PHR reference TTI on the second component carrier. At 580, the second uplink grant can be monitored in the uplink grant TTI. The second uplink grant can grant the second uplink transmission in the second PHR reference TTI that starts simultaneously with the first PHR reference TTI.

[0065] At 590, a second PHR can be generated for the second component carrier based on the second PHR reference TTI. There can be additional component carriers such as a third component carrier, and a PHR reference TTI can be determined and a respective PHR can be generated for each additional component carrier. The second PHR for the second component carrier for the second PHR reference TTI can be generated based on monitoring of the second uplink grant. The second PHR for the second PHR reference TTI can also be generated when the second uplink grant is received in the uplink grant TTI. The second PHR for the second PHR reference TTI can further be generated using a predefined uplink transmission for the second component carrier when the UE 110 is unable to determine whether there is an uplink transmission on the second component carrier. The predefined uplink transmission can be a dummy uplink transmission. For example, the UE can generate a power headroom report by assuming no uplink transmission on the second component carrier. The UE can also generate a PHR in this manner when the second uplink grant is not transmitted, such as when an unlicensed transmission mode is being used. The UE can further generate a PHR in this manner as a default manner for generating a PHR and can not rely on different timing relationships / TTI lengths due to the use of different numerologies on different carriers. According to a possible implementation, when the second power headroom report is calculated using a predefined uplink transmission, the second PHR can be generated based on a predefined numerology. For example, the UE 110 can use a reference numerology of a component carrier / serving cell for calculating a power headroom based on a reference transmission / format. Component carriers with the same TTI can have the same numerology. According to another possible implementation, the second PHR can only be generated when the second TTI is the same as the first TTI. In this implementation, power headroom information can only be transmitted for a group of component carriers with the same TTI as opposed to reporting power headroom for each component carrier.

[0066] At 595, the first PHR and the second PHR can be transmitted in an uplink transmission such as in the first uplink transmission. According to a possible implementation, the first uplink grant can be a first time period away from the first PHR reference TTI, the second uplink grant can be a second time period away from the second PHR reference TTI, and the PHR can be transmitted on the component carrier with the shortest time period between the respective uplink grant and the respective PHR reference TTI. For example, the UE 110 can transmit an extended PHR MAC CE on a carrier that allows the UE 110 to take into account uplink grants on other carriers / serving cells. According to a possible implementation, the first PHR and the second PHR can be transmitted in a PHR MAC CE in the uplink transmission.

[0067] It should be understood that while particular steps are illustrated, various additional or different steps can be performed according to embodiments, and one or more particular steps can be rearranged, repeated, or completely deleted according to embodiments. Also, some steps performed can be repeated on a continuous or ongoing basis while other steps are performed. Further, not all steps can be performed by different elements or in a single element of the disclosed embodiments.

[0068] Figure 6 is an exemplary block diagram of an apparatus 600 such as a UE 110, base station 120, access point, or any other device disclosed herein according to possible embodiments. The apparatus 600 can include a housing 610, a controller 620 within the housing 610, audio input and output circuitry 630 coupled to the controller 620, a display 640 coupled to the controller 620, at least one transceiver 650 coupled to the controller 620, an antenna 655 coupled to the transceiver 650, a user interface 660 coupled to the controller 620, a memory 670 coupled to the controller 620, and a network interface 680 coupled to the controller 620. The apparatus 600 can perform the methods described in all embodiments.

[0069] The display 640 can be a viewfinder, a liquid crystal display (LCD), a light emitting diode (LED) display, a plasma display, a projection display, a touchscreen, or any other device that displays information. The at least one transceiver 650 can include a transmitter, a receiver, multiple transceivers, and / or different transceivers for different frequencies and / or different wireless communication interfaces. The audio input and output circuitry 630 can include a microphone, a speaker, a transducer, or any other audio input and output circuitry. The user interface 660 can include a keypad, a keyboard, buttons, a touchpad, a joystick, a touchscreen display, another additional display, or any other device for providing an interface between a user and an electronic device. The network interface 680 can be a universal serial bus (USB) port, an Ethernet port, an infrared transmitter / receiver, an IEEE 1394 port, a wireless local area network (WLAN) transceiver, or any other interface that can connect the apparatus to a network, device, or computer and can send and receive data communication signals. The memory 670 can include random access memory, read only memory, optical storage, solid state storage, flash memory, removable memory, a hard drive, a cache, or any other memory that can be coupled to the apparatus.

[0070] The apparatus 600 or controller 620 can implement any operating system such as Microsoft Windows®, Linux®, Unix®, Google Android®, Apple iOS®, or any other operating system. or Android TMor any other operating system. For example, the device operating software can be written in any programming language, such as C, C++, Java, or Visual Basic. The device software can also run on an application framework, such as, for example, framework, framework, or any other application framework. The software and / or operating system can be stored in the memory 670 or elsewhere on the device 600. The device 600 or controller 620 can also use hardware to implement the disclosed operations. For example, the controller 620 can be any programmable processor. The disclosed embodiments can also be implemented on a general-purpose or a special purpose computer, a programmed microprocessor or microcontroller, peripheral integrated circuit elements, an application-specific integrated circuit or other integrated circuits, a hardware / software

[0071] In operation, the at least one transceiver 650 can communicate on at least a first component carrier having a first TTI and a second component carrier having a second TTI. The controller 620 can ascertain that a PHR has been triggered for at least one of the first component carrier, the second component carrier, and / or other component carriers. The transceiver 650 can receive an uplink grant corresponding to an uplink transmission on the first component carrier. The controller 620 can determine a first PHR reference TTI corresponding to the uplink transmission on the first component carrier. The controller 620 can generate a first PHR for the first component carrier based on the first PHR reference TTI.

[0072] The controller 620 can determine a second PHR reference TTI on the second component carrier. According to one possible implementation, the second PHR reference TTI can be a first overlapping TTI on the second component carrier, where the first PHR reference TTI overlaps the second PHR reference TTI. According to another possible implementation, the second PHR reference TTI can be a first overlapping TTI on the second component carrier, where one of the first PHR reference TTI and the second PHR reference TTI completely overlaps the other of the first PHR reference TTI and the second PHR reference TTI.

[0073] The controller 620 can generate a second PHR for the second component carrier based on the second PHR reference TTI. According to a possible implementation, the second PHR can be generated based on a predefined set of parameters when the second PHR is calculated using a predefined uplink transmission. According to another possible implementation, the second PHR can be generated only when the second TTI is the same as the first TTI. The transceiver 650 can transmit the first PHR and the second PHR in the uplink transmission.

[0074] According to a possible embodiment, the uplink grant can be a first uplink grant and the uplink transmission can be a first uplink transmission. The controller 620 can determine an uplink grant TTI in which a second uplink grant can be received. The second uplink grant can correspond to a second uplink transmission in a second PHR reference TTI on a second component carrier. The second uplink grant can grant the second uplink transmission in the second PHR reference TTI that starts simultaneously with the first PHR reference TTI. The controller 620 can monitor the second uplink grant in the uplink grant TTI. The controller 620 can generate a second PHR for the second component carrier for the second PHR reference TTI based on the monitoring of the second uplink grant. The controller 620 can generate the second PHR for the second PHR reference TTI when the second uplink grant is received in the uplink grant TTI. The first uplink grant can be a first time period away from the first PHR reference TTI, the second uplink grant can be a second time period away from the second PHR reference TTI, and the transceiver 650 can transmit the PHRs on the component carriers with the shortest time period between the respective uplink grant and the respective PHR reference TTI. According to a possible implementation, the controller 620 can generate the second PHR using a predefined uplink transmission for the second component carrier when the apparatus 600 cannot determine whether there is an uplink transmission on the second component carrier. According to another possible implementation, the second PHR reference TTI can be an overlapping TTI in which one of the first uplink transmission and the second uplink transmission fully overlaps the other of the first uplink transmission and the second uplink transmission.

[0075] It should be noted that the term slot / TTI / subframe has been used throughout this disclosure to denote a unit for scheduling data transmission. Data transmission can also be scheduled to span one or more slots.

[0076] The methods of the present disclosure can be implemented on a programmed processor. However, the controller, flow charts, and modules can also be implemented on a general purpose or special purpose computer, a programmed microprocessor or microcontroller, peripheral integrated circuit elements, an integrated circuit, a hardware electronic or logic circuit such as a discrete element circuit, a programmable logic device, or the like. In general, any device that can function according to the methods of the disclosure described herein can be used in implementing the functionality of the present disclosure.

[0077] While the present disclosure has been described with reference to specific implementations thereof, it is evident that many alternatives, modifications and variations can be apparent to those skilled in the art. For instance, in other embodiments, various components of the embodiments can be interchanged, added, or removed. Also, not all of the elements of each figure are essential for operation of the disclosed embodiments. For example, one of ordinary skill in the art of the disclosed embodiments will be able to make and use the teachings of the present disclosure without the elements not specifically described herein. Accordingly, embodiments of the present disclosure as set forth herein are intended to be illustrative, not limiting. Various changes can be made without departing from the spirit and scope of the disclosure.

[0078] In this document, relational terms such as "first," "second," and the like can be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. The phrase "at least one of" followed by a list of two or more items, such as "at least one of A, B, or C," is defined to mean one, some, or all of the items in the list. The use of "at least one of" followed by a list of two or more items, such as "at least one of A, B, or C," is to be taken as a specific recitation of one, some, or all of the items in the list. The term "comprises" or "comprising" or the like is defined to mean the process, methods, articles or apparatuses that include a recited step, element, or the like, and that also include additional steps, elements, or the like not recited. The terms "a" and "an" are defined as "one or more" unless explicitly indicated to the contrary. The term "another" is defined as at least a second or more. The terms "including," "having," and the like are defined as "comprising." Furthermore, the Background section is intended to provide contextual background information for some embodiments and includes information that the inventors themselves regard as being of possible relevance to the application but which need not necessarily be understood by those skilled in the art to be prior art or to be part of the prior art.

Claims

1. A method in a user equipment, the method comprising: Configured with A first serving cell with a first subcarrier spacing and a first time slot length for physical uplink shared channel transmission, and A second serving cell with a second subcarrier spacing and a second time slot length for physical uplink shared channel transmission. The first subcarrier spacing is less than the second subcarrier spacing, and the first time slot length is greater than the second time slot length; It has been confirmed that the power margin report has been triggered; It has uplink allocation corresponding to uplink transmissions in the allocated time slots on the first serving cell. The time slots allocated on the first serving cell overlap with multiple time slots on the second serving cell. Generate a first power margin report for the allocated time slots on the first serving cell; A second power margin report is generated for the second serving cell. Specifically, for the first time slot among multiple overlapping time slots on the second serving cell that completely overlaps with the allocated time slot on the first serving cell, a second power margin report is generated; and In the uplink transmission within the allocated time slot on the first serving cell, the first power headroom report and the second power headroom report are transmitted. The first power margin report and the second power margin report are both type 1 power margin reports.

2. The method according to claim 1, in, The configuration includes configuring the user equipment. The first serving cell for physical uplink shared channel transmission with a first subcarrier spacing and a first time slot length, and The second serving cell is used for physical uplink shared channel transmission with a second subcarrier spacing and a second time slot length. The first subcarrier spacing is less than the second subcarrier spacing, and the first time slot length is greater than the second time slot length. The method further includes receiving an uplink allocation corresponding to an uplink transmission in an allocated time slot on the first serving cell, wherein the allocated time slot on the first serving cell overlaps with multiple time slots of the second serving cell.

3. The method according to claim 1, in, The plurality of overlapping time slots on the second serving cell include at least one time slot that completely overlaps with the allocated time slots on the first serving cell, and The at least one time slot that completely overlaps with the allocated time slot begins from the first time slot among the at least one time slots that completely overlap with the allocated time slot.

4. The method according to claim 1, further comprising: Receive a first uplink permission including the uplink allocation, wherein the uplink transmission includes the first uplink transmission; Determine a specific time slot in which a second uplink permission can be received, the second uplink permission corresponding to a second uplink transmission in the first time slot of the plurality of overlapping time slots; and The second uplink permission is monitored within the determined time slot. The generation of the second power margin report includes generating the second power margin report for the second serving cell based on monitoring of the second uplink permission.

5. The method according to claim 4, wherein, The determined license slot in which the second uplink license can be received is determined in response to the determination that a power headroom report has been triggered and in response to the receipt of the first uplink license.

6. The method according to claim 4, wherein, Generating the second power headroom report includes: when the second uplink permission is received in the determined time slot, generating the second power headroom report for the first time slot among the plurality of overlapping time slots.

7. The method according to claim 1, in, The allocation slots on the first serving cell begin at the first moment, and Wherein, the first time slot in the plurality of overlapping time slots begins at the second time, wherein the first time is prior to the second time.

8. The method according to claim 1, wherein, Generating the second power headroom report includes: when calculating the second power headroom report using a predefined uplink transmission, generating the second power headroom report based on a predefined set of parameters.

9. The method according to claim 1, wherein, The transmission includes transmitting the first power headroom report and the second power headroom report in the power headroom report media access control element of the uplink transmission in the allocated time slot on the first serving cell.

10. The method according to claim 1, in, The first power headroom report indicates the difference between the maximum uplink transmission power configured by the user equipment in the first serving cell and the estimated power transmitted on the uplink shared channel in the first serving cell, and The second power margin report indicates the difference between the maximum uplink transmission power configured by the user equipment in the second serving cell and the estimated power transmitted on the uplink shared channel in the second serving cell.

11. An apparatus comprising: The memory includes a configuration of a first serving cell for physical uplink shared channel transmission having a first subcarrier spacing and a first time slot length, and a configuration of a second serving cell for physical uplink shared channel transmission having a second subcarrier spacing and a second time slot length, wherein the first subcarrier spacing is less than the second subcarrier spacing and the first time slot length is greater than the second time slot length. as well as The controller determines that a power margin report has been triggered. The memory includes uplink allocations corresponding to uplink transmissions in the allocated time slots on the first serving cell, wherein the allocated time slots on the first serving cell overlap with multiple time slots on the second serving cell. Wherein, the controller: Generate a first power margin report for the allocated time slots on the first serving cell, and A second power headroom report is generated for the second serving cell, wherein the second power headroom report is generated for the first time slot, which is one of the multiple overlapping time slots on the second serving cell and completely overlaps with the allocated time slot on the first serving cell. The apparatus further includes a transceiver that transmits the first power headroom report and the second power headroom report in uplink transmissions within allocated time slots on the first serving cell. The first power margin report and the second power margin report are both type 1 power margin reports.

12. The apparatus according to claim 11, in, The transceiver receives a configuration, which is then configured to configure the device. The first serving cell for physical uplink shared channel transmission with a first subcarrier spacing and a first time slot length, and The second serving cell is used for physical uplink shared channel transmission with a second subcarrier spacing and a second time slot length. The first subcarrier spacing is less than the second subcarrier spacing, and the first time slot length is greater than the second time slot length. The transceiver receives uplink allocations corresponding to uplink transmissions in the allocated time slots of the first serving cell, where the allocated time slots of the first serving cell overlap with multiple time slots of the second serving cell.

13. The apparatus according to claim 11, in, The multiple overlapping time slots on the second serving cell include at least one time slot that completely overlaps with the allocated time slots on the first serving cell, and The at least one time slot that completely overlaps with the allocated time slot begins from the first time slot among the at least one time slots that completely overlap with the allocated time slot.

14. The apparatus according to claim 11, in, The transceiver receives a first uplink license, including the uplink allocation, wherein the uplink transmission includes the first uplink transmission; and Wherein, the controller Determine a specific time slot in which a second uplink license can be received, the second uplink license corresponding to a second uplink transmission in the first time slot of the plurality of overlapping time slots, and Monitoring is performed in the determined time slots for the second uplink permission, and The second power margin report for the second serving cell is generated based on monitoring of the second uplink permission.

15. The apparatus according to claim 14, wherein, The determined license slot in which the second uplink license can be received is determined in response to the determination that a power headroom report has been triggered and in response to the receipt of the first uplink license.

16. The apparatus according to claim 14, wherein, When the second uplink permission is received in the determined time slot, the controller generates a second power margin report for the first time slot among the plurality of overlapping time slots.

17. The apparatus according to claim 11, in, The allocation slots on the first serving cell begin at the first moment, and Wherein, the first time slot in the plurality of overlapping time slots begins at the second time, wherein the first time is prior to the second time.

18. The apparatus according to claim 11, wherein, When the controller uses a predefined uplink transmission to calculate the second power headroom report, it generates the second power headroom report based on a predefined set of parameters.

19. The apparatus of claim 11, wherein the transceiver transmits the first power headroom report and the second power headroom report in the uplink transmission power headroom report media access control control element in the allocated time slot on the first serving cell.

20. The apparatus according to claim 11, in, The first power headroom report indicates the difference between the maximum uplink transmission power configured by the user equipment in the first serving cell and the estimated power transmitted on the uplink shared channel in the first serving cell, and The second power margin report indicates the difference between the maximum uplink transmission power configured by the user equipment in the second serving cell and the estimated power transmitted on the uplink shared channel in the second serving cell.

Images