Power Control (ERAN3.0 03)
Power Control (ERAN3.0 03)
eRAN3.0
Feature Parameter Description
Issue 03
Date 2013-05-20
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience ........................................................................................................................ 1-1
1.3 Change History.............................................................................................................................. 1-1
7 Engineering Guidelines...........................................................................................................7-1
7.1 When to Use Power Control.......................................................................................................... 7-1
7.1.1 Downlink Power Control ....................................................................................................... 7-1
7.1.2 Uplink Power Control ............................................................................................................ 7-2
7.2 Information to Be Collected ........................................................................................................... 7-2
7.3 Network Planning .......................................................................................................................... 7-2
7.4 Deploying Downlink Power Control ............................................................................................... 7-2
7.4.1 Deployment Requirements ................................................................................................... 7-2
7.4.2 Data Preparation .................................................................................................................. 7-3
7.4.3 Initial Configuration ............................................................................................................. 7-10
7.4.4 Activation Observation .........................................................................................................7-11
7.4.5 Deactivation ........................................................................................................................ 7-25
7.5 Deploying Uplink Power Control ................................................................................................. 7-25
7.5.1 Deployment Requirements ................................................................................................. 7-25
7.5.2 Data Preparation ................................................................................................................ 7-26
7.5.3 Initial Configuration ............................................................................................................. 7-30
7.5.4 Activation Observation ........................................................................................................ 7-31
7.5.5 Deactivation ........................................................................................................................ 7-41
7.6 Performance Optimization ........................................................................................................... 7-41
7.7 Troubleshooting ........................................................................................................................... 7-42
8 Parameters .................................................................................................................................8-1
9 Counters ......................................................................................................................................9-1
10 Glossary ..................................................................................................................................10-1
11 Reference Documents .........................................................................................................11-1
1 Introduction
1.1 Scope
This document describes features related to power control in terms of implementation, parameters
involved, feature relationships, network impact, and engineering guidelines.
Any managed objects (MOs), parameters, alarms, or counters described in this document correspond to
the software release delivered with this document. In the event of updates, the updates will be described
in the product documentation delivered with the latest software release.
Document Issues
The document issues are as follows:
03 (2013-05-20)
02 (2012-12-29)
01 (2012-03-30)
Draft A (2012-01-10)
03 (2013-05-20)
Compared with issue 02 (2012-12-29) of eRAN3.0, issue 03 (2013-05-20) of eRAN3.0 includes the
following changes.
02 (2012-12-29)
Compared with issue 01(2012-03-30) of eRAN3.0, issue 02 (2012-12-29) of eRAN3.0 includes the
following changes.
01 (2012-03-30)
This is the first official release.
Compared with draft A (2012-01-10) of eRAN3.0, issue 01 (2012-03-30) of eRAN3.0 includes the
following changes.
Draft A (2012-01-10)
This is a draft.
Compared with issue 01 (2011-12-24) of eRAN2.2, draft A (2012-01-10) of eRAN3.0 includes the
following changes.
When PdcchPcSwitch under CellAlgoSwitch.DlPcAlgoSwitch is not selected, the PDCCH uses fixed
power assignment. In this case, the offset of the power for the PDCCH against the power for the
cell-specific reference signal is set using the CellDlpcPdcch.DediDciPwrOffset parameter.
Adaptive modulation and coding (AMC) and HARQ also improve system throughput and spectral efficiency. You can use
them in combination with power control.
Power control for the PDSCH determines the EPREs of different OFDM symbols by using ρA and ρB. ρA
is used to determine the PDSCH EPRE for symbol type A, and ρB is used to determine the PDSCH
EPRE for symbol type B.
The transmit power for the two types of OFDM symbols corresponding to the transmit power for the RE
on the PDSCH is defined by PPDSCH_A and PPDSCH_B. The calculation formulas are as follows:
PPDSCH_A = ρA + PDSCHCfg.ReferenceSignalPwr
PPDSCH_B = ρB + PDSCHCfg.ReferenceSignalPwr
When the eNodeB receives a CQI reported by the UE, it compares the reported CQI with the previous
CQI. If the difference between the two CQI values is great, the process for re-calculating the PA for the
UE is started. For details, see Figure 3-1.
Power control for the SRS and PRACH is not conventional. In addition, the power for the SRS is determined by the result
of power control for the PUSCH. Therefore, this section does not describe power control for the SRS and PRACH. For
related descriptions, see section 4.2 "Power Control for the PRACH" and section 4.5 "Power Control for Sounding
Reference Signals."
Power control for the PUSCH and PUCCH how the eNodeB adjusts the transmit power of UEs by means
of TPCs.
Based on the power control parameter settings, interference to neighboring cells, and the results of
uplink data transmission measurement performed by the eNodeB, the uplink power control algorithm
calculates the TPC of a UE and sends the TPC to the UE by means of the PDCCH. Based on the
mapping defined in section 5.1 "Uplink power control" in 3GPP TS 36.213 V9.3.0 (2010-09), the UE
converts the TPC to the power adjustment value. Then, the UE determines its transmit power based on
factors such as the power adjustment value, its own maximum transmit power, the nominal power of the
cell, the path loss, the MCS, and radio resources. By adjusting the TPC, power control enables the
transmission performance of radio link to converge to the target value. In addition, TPC adjustment
suppresses the inter-cell interference.
For details about how to configure parameters, see chapter 7 "Engineering Guidelines."
where
N pre is the number of times the UE sends the preamble. This value cannot exceed the maximum
number of preamble transmissions.
step is the preamble power ramping step. This value is set using the RACHCfg.PwrRampingStep
parameter.
The eNodeB sends Po _ pre and step to a UE by broadcasting system information, and the UE
calculates the transmit power for the random access preamble based on Po _ pre , step , PL , and the
recorded N pre .
PPUSCH (i) min{PCMAX ,10 log( M PUSCH (i)) Po _ PUSCH PL TF (i) f (i)}
where
i is the subframe number (for example, when i = 9, i is the ninth uplink subframe).
PCMAX is the maximum transmit power of the UE.
M PUSCH (i) is the number of RBs used by the ith uplink subframe.
Po _ PUSCH is the receive power expected by the eNodeB.
is the path loss compensation factor. is set using the CellUlpcComm.PassLossCoeff
parameter.
PL is the downlink path loss estimated by the UE. For details, see section 4.2.1 "Basics of PRACH
Power Calculation."
TF (i) is the offset of the power for the current MCS format against the reference MCS format. If the
CellUlpcDedic.DeltaMcsEnabled parameter is set to 0, TF (i) is 0. Otherwise, the impact of
TF (i) is considered.
f (i) is the adjustment of the PUSCH transmit power of the UE. This value is obtained based on the
TPC information on the PDCCH.
Po _ PUSCH is determined by the eNodeB and reflects the receive power density expected by the eNodeB
when the requirements for the PUSCH demodulation performance are met. The calculation formula is as
follows:
where
Po _ NOMINAL _ PUSCH is the transmit power density for the PUSCH expected by the eNodeB when the
correct PUSCH demodulation is ensured. Po _ NOMINAL _ PUSCH is set using the
CellUlpcComm.P0NominalPUSCH parameter.
Po _ UE _ PUSCH is the offset of the power for the UE against Po _ NOMINAL _ PUSCH . This value reflects the
impact of the UE level, service type, and channel quality on the transmit power for the PUSCH.
power density is greater than the target transmit power density, the eNodeB sends a TPC command,
ordering a decrease in transmit power. If the estimated transmit power density is less than the target
transmit power density, the eNodeB sends a TPC command, ordering an increase in transmit power.
The transmit power density in the E-UTRAN system refers to the transmit power of an RB.
In semi-persistent scheduling, power control for the PUSCH is set using the
CellAlgoSwitch.UlPcAlgoSwitch parameter. The principles are as follows:
When CloseLoopSpsSwitch under CellAlgoSwitch.UlPcAlgoSwitch is selected, the transmit power
for the PUSCH is periodically adjusted to adapt to change in the channel environment based on the
difference between the measured IBLER and IBLERTarget:
If the measured IBLER is greater than IBLERTarget, the eNodeB sends a TPC command to the UE,
ordering an increase in transmit power.
If the measured IBLER is less than IBLERTarget, the eNodeB sends a TPC command to the UE,
ordering a decrease in transmit power.
The value of IBLERTarget is determined based on the requirement of the service in semi-persistent
scheduling.
The PUSCH TPCs of multiple UEs in semi-persistent scheduling are sent to the UEs in DCI format 3/3A.
In this way, signaling overheads on the PDCCH are reduced.
PPUSCH (i) min{PCMAX ,10 log( M PUSCH (i)) PO_pre PREAMBLE _ Msg3 PL TF (i) f (i)}
where
i is the subframe number (for example, when i = 9, i is the ninth uplink subframe).
PCMAX is the maximum transmit power of the UE.
M PUSCH (i) is the number of RBs used by the ith uplink subframe.
Po _ pre is the target power expected by the eNodeB when the requirements for the preamble detection
performance are met and the PRACH preamble format is 0.
PREAMBLE _ Msg3 is the preamble delta value of Msg3. This value is set using the
CellUlpcComm.DeltaPreambleMsg3 parameter.
PL is the downlink path loss estimated by the UE. For details, see section 4.2.1 "Basics of PRACH
Power Calculation."
TF (i) is the offset of the power for the current MCS format against the reference MCS format. For
details, see section 4.3.1 "Basics of PUSCH Power Calculation."
f (i) is the adjustment of the PUSCH transmit power of the UE. This value is obtained based on the
TPC information on the PDCCH.
The transmit power for Msg3 is determined based on Po _ pre and the parameters related to power
control for the PUSCH. For details about Po _ pre , see section 4.2 _Ref276369212"Power Control for the
PRACH "
where
i is the subframe number (for example, when i = 9, i is the ninth uplink subframe).
PCMAX is the maximum transmit power of the UE.
P0 _ PUCCH is the receive power expected by the eNodeB.
PL is the downlink path loss estimated by the UE. This value is obtained based on the measured
RSRP and the transmit power for the cell-specific reference signal. The Alpha filtering coefficient for
filtering the RSRP measurement values is set using the CellUlpcDedic.FilterRsrp parameter.
h n CQI , nHARQ is determined by the PUCCH format. nCQI is the number of information bits of the CQI,
and it reflects the impact of the number of CQI bits of the PUCCH on the power. nHARQ is the number of
information bits of HARQ, and it reflects the impact of the number of HARQ signaling bits of the
PUCCH on the power.
F _ PUCCH ( F ) reflects the transmission format of the PUCCH on the transmit power. It is set using the
CellUlpcComm.DeltaFPUCCHFormat1, CellUlpcComm.DeltaFPUCCHFormat1b,
CellUlpcComm.DeltaFPUCCHFormat2, CellUlpcComm.DeltaFPUCCHFormat2a, and
CellUlpcComm.DeltaFPUCCHFormat2b parameters.
g (i) is the adjustment of the transmit power of the UE's PUCCH, and it is obtained based on the TPC
information on the PDCCH.
P0 _ PUCCH is determined by the eNodeB and is the receive power expected by the eNodeB when the
requirements for the PUCCH demodulation performance are met. The calculation formula is as follows:
where
Po _ NOMINAL _ PUCCH is the target signal power expected by the eNodeB for the reference transmission
format. Po _ NOMINAL _ PUCCH is set using the CellUlpcComm.P0NominalPUCCH parameter.
Po _ UE _ PUCCH is the offset of the power for the UE against Po _ NOMINAL _ PUCCH . This value reflects the
impact of the UE level, service type, and channel quality on the transmit power for the PUCCH.
where
i is the subframe number (for example, when i = 9, i is the ninth uplink subframe).
PCMAX is the maximum transmit power of the UE.
M SRS is the transmission bandwidth of the SRS.
PSRS _ OFFSET is the offset of the SRS power against the PUSCH power. This value is set using the
CellUlpcDedic.PsrsOffsetDeltaMcsDisable or CellUlpcDedic.PSrsOffsetDeltaMcsEnable
parameters based on different CellUlpcDedic.DeltaMcsEnabled values.
Po _ PUSCH is the value in dynamic scheduling for the PUSCH.
is the path loss compensation factor, and it is set using the CellUlpcComm.PassLossCoeff
parameter.
PL is the downlink path loss estimated by the UE. This value is calculated based on the measured
RSRP value and the transmit power for the cell-specific reference signal. The Alpha filtering coefficient
for filtering the RSRP measurement values is set using the CellUlpcDedic.FilterRsrp parameter.
f (i) is the adjustment of the transmit power of the UE's PUSCH, and it is obtained based on the TPC
information on the PDCCH.
5 Related Features
Power control involves the basic features LBFD-002016 Dynamic Downlink Power Allocation and
LBFD-002026 Uplink Power Control. This chapter describes their relationships with other features.
The downlink VoIP semi-persistent scheduling algorithm provides the achieved downlink BLER as an
input to the downlink semi-persistent power control algorithm. The BLER is a prerequisite for enabling
PDSCH power adjustment in semi-persistent scheduling.
LBFD-00202201 Downlink Static Inter-Cell Interference Coordination, LOFD-00101401 Downlink
Dynamic Inter-Cell Interference Coordination, and Adaptive Inter-Cell Interference Coordination - LTE
The downlink ICIC algorithm provides the downlink power control algorithm with the ICIC switch status
and UE types (CCU or CEU). The downlink power control affects the transmit power and therefore
ICIC features.
recommended that CloseLoopSpsSwitch be turned on to enable power control for the PUSCH in
semi-persistent scheduling mode.
LBFD-002010 Random Access Procedure
The random access procedure provides the uplink power control algorithm with information such as
the preamble format and the number of times the UE sends the preamble. Based on this information,
the uplink power control algorithm maintains the transmit power of the UE above the required level
during the random access procedure.
7 Engineering Guidelines
This chapter provides engineering guidelines for power control.
The setting of CellDlpcPdschPa.PdschPaAdjSwitch takes effect only when downlink ICIC is disabled.
The setting of PdschSpsPcSwitch takes effect only when downlink ICIC is disabled.
The main source of interference is cell-specific reference signals transmitted in neighboring cells.
This is true when neighboring cells are lightly loaded (cell load is lower than 20%). In this case, an
effective measure is to increase the transmit power for data and decrease that for cell-specific
reference signals in both the local cell and the neighboring cells. Specifically, the following settings are
recommended: PRS = 15.2 dBm, PA = 0, and PB = 0.
The main source of interference is data transmitted in neighboring cells.
This is true when neighboring cells are heavily loaded. In this case, an effective measure is to increase
the transmit power for cell-specific reference signals in the local cell to improve the PDSCH
demodulation performance. Specifically, the following settings are recommended: PRS = 18.2 dBm, PA
= 3, and PB = 1.
If the power control described in this section is enabled, it is recommended that inner-loop power control for the PUSCH in
dynamic scheduling mode also be enabled.
Generic Data
Power Settings for Cell-specific Reference Signals
The following table describes the parameters that must be set in the PDSCHCfg managed object (MO)
to configure the cell-specific reference signal power.
The following table describes the parameters that must be set in the CellAlgoSwitch MO to configure
the PHICH inner-loop power control switch.
The following table describes the parameters that must be set in the CellAlgoSwitch MO to configure
the PDCCH power control switch.
Power Settings for the PDSCH Carrying Information Other Than RACH Response, Paging
Messages, and SIBs
The following table describes the parameters that must be set in the CellDlpcPdschPa MO to configure
the PA adjustment switch.
The following table describes the parameters that must be set in the CellAlgoSwitch MO to configure
the switch for PDSCH power control during semi-persistent scheduling.
The following table describes the parameters that must be set in the PDSCHCfg MO to configure PB.
Power Settings for the PDSCH Carrying RACH Response, Paging Messages, and SIBs
The following table describes the parameters that must be set in the CellChPwrCfg MO to configure
power offsets for the PDSCH that carries RACH response, paging messages, and SIBs.
Scenario-specific Data
Scenario 1: Downlink ICIC Disabled
The following table describes the parameters that must be set in the CellDlpcPdschPa MO to configure
PA for PDSCH power control.
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
Switch Setting for PDCCH Power Control, PHICH Power Control, and PDSCH Power Control in
Semi-Persistent Scheduling Mode
The following table lists the parameter that includes the switches for PDCCH power control, PHICH
power control, and power control for the PDSCH in semi-persistent scheduling mode.
----End
Power Allocation for the PDSCH Carrying RACH Response, Paging Messages,
and SIBs
On the M2000 client, check the setting of the cell-specific reference signal power. Then, run the LST
CELLCHPWRCFG command to check the power setting for the PDSCH that carries the RACH
response, paging messages, and SIBs in each cell.
Figure 7-5 shows an example of the result.
Figure 7-5 Example of the power for the PDSCH carrying RACH response, paging messages, and SIBs
Step 5 Enable a UE to access the cell. Wait until the UE inactivity timer expires and the UE enters
RRC_IDLE mode. Then, perform an 80 Mbit/s uplink UDP data transmission. The UE enters
RRC_CONNECTED mode. Check the values for the mMEC and m-TMSI IEs in the
S1AP_INITIAL_UE_MSG message traced over the S1 interface, as shown in Figure 7-6.
Figure 7-6 S1AP_INITIAL_UE_MSG message
Step 6 In the navigation tree of the Signaling Trace window, choose Trace Type > LTE > User
Performance Monitoring > DL Power Control Monitoring. Double-click DL Power Control
Monitoring.
Step 7 In the displayed DL Power Control Monitoring dialog box, set UEID-MME to the decimal value
for the mMEC IE, and set UEID-TMSI/Trace Reference NO. to the decimal value for the m-TMSI
IE, as shown in Figure 7-7. Then, click Finish to start the UE downlink power control monitoring.
Step 8 Double-click the new task in the task list on the right of the Signaling Trace Management tab
page. The task monitoring tab page is displayed.
Step 9 Check the real-time value for Power Offset of PHICH (0.01dB), as shown in Figure 7-8.
When PhichInnerLoopPcSwitch is disabled, the eNodeB allocates fixed power to the PHICH. In
this situation, the value for Power Offset of PHICH (0.01dB) is the same as that for
CellDlpcPhich.PwrOffset. When PhichInnerLoopPcSwitch is enabled, the eNodeB
dynamically adjusts the PHICH power. In this situation, the values for Power Offset of PHICH
(0.01dB) and CellDlpcPhich.PwrOffset may be different.
----End
Step 6 In the navigation tree of the Signaling Trace window, choose Trace Type > LTE > User
Performance Monitoring > DL Power Control Monitoring. Double-click DL Power Control
Monitoring.
Step 7 In the displayed DL Power Control Monitoring dialog box, set UEID-MME to the decimal value
for the mMEC IE, and set UEID-TMSI/Trace Reference NO. to the decimal value for the m-TMSI
IE, as shown in Figure 7-10. Then, click Finish to start the UE downlink power control
monitoring.
Step 8 Double-click the new task in the task list on the right of the Signaling Trace Management tab
page.
The task monitoring tab page is displayed.
Step 9 Move the UE to the cell center and check the real-time value for Power Offset of
PDCCH(0.01dB), as shown in Figure 7-11.
When the UE is in the cell center, the power of the PDCCH is small, and accordingly the value for
Power Offset of PDCCH(0.01dB) is small.
Step 10 Move the UE to the cell edge and check the real-time value for Power Offset of PDCCH(0.01dB),
as shown in Figure 7-12.
When PdcchPcSwitch is turned on and the UE is in the cell edge, the eNodeB increases the
power of the PDCCH. When the value for Power Offset of PDCCH(0.01dB) in this step is greater
than that in Step 9, power control for the PDCCH carrying dedicated control information takes
effect. When PdcchPcSwitch is turned off, the eNodeB does not adjust the power of the PDCCH,
which means the two values are the same.
----End
Power Settings for the PDSCH Carrying Channels Other Than RACH
Response, Paging Messages, and SIBs
Step 1 On the M2000 client, choose Monitor > Signaling Trace > Signaling Trace Management.
Step 2 In the navigation tree of the displayed Signaling Trace window, choose Trace Type > LTE >
Application Layer > Uu Interface Trace. Double-click Uu Interface Trace.
Step 3 Set task information in the displayed Uu Interface Trace dialog box and click Finish.
The Uu interface signaling tracing task is started.
Step 4 Double-click the new task in the task list on the right of the Signaling Trace Management tab
page. The task monitoring tab page is displayed.
Step 5 Deactivate the cell and then activate it. After the cell is activated, find the p-b IE in the first
RRC_SYS_INFO message traced over the Uu interface, as shown in Figure 7-13. Then, check
whether the value for the p-b IE is consistent with the value for PDSCHCfg.Pb.
If the values are consistent, the settings for PDSCHCfg.Pb take effect.
Step 6 In the navigation tree of the displayed Signaling Trace window, choose Trace Type > LTE >
Application Layer > S1 Interface Trace. Double-click S1 Interface Trace.
Step 7 Set task information in the displayed S1 Interface Trace dialog box and click Finish.
The S1 interface signaling tracing task is started.
Step 8 Double-click the new task in the task list on the right of the Signaling Trace Management tab
page.
The task monitoring tab page is displayed.
Step 9 Enable a UE to access the cell. Wait until the UE inactivity timer expires and the UE enters
RRC_IDLE mode. Then, perform a 150 Mbit/s downlink UDP data transmission. The UE enters
RRC_CONNECTED mode. Check the values for the mMEC and m-TMSI IEs in the
S1AP_INITIAL_UE_MSG message traced over the S1 interface, as shown in Figure 7-14.
Step 10 In the navigation tree of the Signaling Trace window, choose Trace Type > LTE > User
Performance Monitoring > DL Power Control Monitoring. Double-click DL Power Control
Monitoring.
Step 11 In the displayed DL Power Control Monitoring dialog box, set UEID-MME to the decimal value
for the mMEC IE, and set UEID-TMSI/Trace Reference NO. to the decimal value for the m-TMSI
IE, as shown in Figure 7-15. Then, click Finish to start the UE downlink power control
monitoring.
Step 12 Double-click the new task in the task list on the right of the Signaling Trace Management tab
page. The task monitoring tab page is displayed.
Step 13 Check the real-time value for PDSCH PA (0.01dB), as shown in Figure 7-16.
When downlink ICIC is disabled and PdschPaAdjSwitch is turned off, the eNodeB allocates fixed
power to the PDSCH. In this situation, the value for PDSCH PA (0.01dB) is the same as the value
for CellDlpcPdschPa.PaPcOff. When downlink ICIC is enabled, the eNodeB allocates power to
the PDSCH according to UE attributes. In this situation, the value for PDSCH PA (0.01dB) is the
same as the value for CellDlpcPdsch.CcuPa or CellDlpcPdsch.CeuPa. For details about
downlink ICIC-triggered UE attribute decision making, see ICIC Feature Parameter Description.
----End
7.4.5 Deactivation
Dynamic Power Adjustment for the PHICH
Run the MOD CELLALGOSWITCH command with the PhichInnerLoopPcSwitch check box cleared
under the CellAlgoSwitch.DlPcAlgoSwitch parameter.
The following table describes the parameters that must be set in the CellUlpcDedic MO to configure the
dedicated RRC parameters for PUSCH power control.
The following table describes the parameters that must be set in the CellAlgoSwitch MO to configure
the closed-loop power control switch for the PUSCH in semi-persistent scheduling mode and the
inner-loop power control switch for the PUSCH in dynamic scheduling mode.
DeltaF for CellUlpcCom Network plan This parameter specifies the Delta value
PUCCH format 2 m.DeltaFPUCC (negotiation corresponding to PUCCH format 2. The value
HFormat2 not required) DELTAF1(1dB) is recommended.
DeltaF for CellUlpcCom Network plan This parameter specifies the Delta value
PUCCH format m.DeltaFPUCC (negotiation corresponding to PUCCH format 2a. The value
2a HFormat2a not required) DELTAF2(2dB) is recommended.
DeltaF for CellUlpcCom Network plan This parameter specifies the Delta value
PUCCH format m.DeltaFPUCC (negotiation corresponding to PUCCH format 2b. The value
2b HFormat2b not required) DELTAF2(2dB) is recommended.
The following table describes the parameters that must be set in the CellAlgoSwitch MO to configure
the PUCCH inner-loop power control switch.
Scenario-specific Data
None
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
This following table lists the parameter that includes the switches for inner-loop power control for the
PUSCH in dynamic scheduling mode, closed-loop power control for the PUSCH in semi-persistent
scheduling mode, and PUCCH power control.
----End
Step 6 Enable a UE to access the cell, and find the deltaMCS-Enabled and filterCoefficient IEs in the
first RRC_CONN_SETUP message traced over the Uu interface, as shown in Figure 7-19. Then,
check whether the values for the two IEs are consistent with the values for
CellUlpcDedic.DeltaMcsEnabled and CellUlpcDedic.FilterRsrp, respectively.
If the values are consistent, the PUSCH power settings take effect.
Step 11 Enable the UE to access the cell in the cell center. Then, perform an 80 Mbit/s uplink UDP data
transmission.
Step 12 In the navigation tree of the Signaling Trace window, choose Trace Type > LTE > Cell
Performance Monitoring > Usage of RB Monitoring. Double-click Usage of RB Monitoring.
Step 13 Set task information in the displayed Usage of RB Monitoring dialog box and click Finish. The
cell RB usage tracing task is started.
Step 14 Double-click the new task in the task list on the right of the Signaling Trace Management tab
page.
The task monitoring tab page is displayed.
Step 15 Check the real-time value for Uplink Equivalent Used RB Num, as shown in Figure 7-21. When
the UE is in the cell center, the value for Uplink Equivalent Used RB Num approximates 1000
times the uplink cell bandwidth. Move the UE from cell center to cell edge until the value for
Uplink Equivalent Used RB Num becomes about 500 times the uplink cell bandwidth. Then,
record this value.
Figure 7-21 Usage of RB Monitoring dialog box (1)
Equivalent Used RB Num in Step 18 is greater than that obtained in Step 9, the PUSCH dynamic
scheduling inner-loop power control takes effect.
Figure 7-22 Usage of RB Monitoring dialog box (2)
deltaF-PUCCH-Format1b
deltaF-PUCCH-Format2
deltaF-PUCCH-Format2a
deltaF-PUCCH-Format2b
Step 7 Check whether the values for these IEs are consistent with the values for the following
parameters, respectively:
CellUlpcComm.P0NominalPUCCH
CellUlpcComm.DeltaFPUCCHFormat1
CellUlpcComm.DeltaFPUCCHFormat1b
CellUlpcComm.DeltaFPUCCHFormat2
CellUlpcComm.DeltaFPUCCHFormat2a
CellUlpcComm.DeltaFPUCCHFormat2b
If the values are consistent, the PUCCH power settings take effect.
Figure 7-23 RRC_SYS_INFO message
Step 8 In the navigation tree of the displayed Signaling Trace window, choose Trace Type > LTE >
Application Layer > S1 Interface Trace. Double-click S1 Interface Trace.
Step 9 Set task information in the displayed S1 Interface Trace dialog box and click Finish.
The S1 interface signaling tracing task is started.
Step 10 Double-click the new task in the task list on the right of the Signaling Trace Management tab
page.
The task monitoring tab page is displayed.
Step 11 Enable a UE to access the cell in the cell center. Wait until the UE inactivity timer expires and the
UE enters RRC_IDLE mode. Then, perform a 150 Mbit/s downlink UDP data transmission. The
UE enters RRC_CONNECTED mode. Check the values for the mMEC and m-TMSI IEs in the
S1AP_INITIAL_UE_MSG message traced over the S1 interface, as shown in Figure 7-24.
Figure 7-24 S1AP_INITIAL_UE_MSG message
Step 12 In the navigation tree of the Signaling Trace window, choose Trace Type > LTE > User
Performance Monitoring > UL Power Control Monitoring. Double-click UL Power Control
Monitoring.
Step 13 In the displayed UL Power Control Monitoring dialog box, set UEID-MME to the decimal value
for the mMEC IE, and set UEID-TMSI/Trace Reference NO. to the decimal value for the m-TMSI
IE, as shown in Figure 7-25. Then, click Finish to start the UE uplink power control monitoring.
Step 14 Double-click the new task in the task list on the right of the Signaling Trace Management tab
page. The task monitoring tab page is displayed.
Step 15 Check the real-time value for PUCCH SINR (0.01dB) and PUCCH SINR Target (0.01dB), as
shown in Figure 7-26.
When the PUCCH inner-loop power control switch is turned on, the eNodeB periodically adjusts
the transmit power of the PUCCH. When the UE is in the cell center, the value for PUCCH SINR
(0.01dB) fluctuates around the value for PUCCH SINR Target (0.01dB). When the PUCCH
inner-loop power control switch is turned off and the UE is in the cell center, the value for PUCCH
SINR (0.01dB) does not approximate the value for PUCCH SINR Target (0.01dB). Instead, it
fluctuates around a relatively larger value.
----End
----End
7.5.5 Deactivation
Inner-Loop Power Control for the PUCCH
Run the MOD CELLALGOSWITCH command with the InnerLoopPucchSwitch check box cleared
under the CellAlgoSwitch.UlPcAlgoSwitch parameter.
7.7 Troubleshooting
None
8 Parameters
Table 8-1 Parameter description
MO Parameter ID MML Feature ID Feature Description
Command Name
CellDlpcPd DediDciPwrOffs MOD LBFD-0020 Dynami Meaning:Indicates the offset of the DCI
cch et CELLDLPCPD 16 / c power relative to the reference signal
CCH TDLBFD-0 Downlin power when the PDCCH channel
02016 k Power carries dedicated control information.
LST Allocati
CELLDLPCPD on GUI Value Range:-150~150
CCH
Unit:0.1dB
Actual Value Range:-15~15, step:0.1
Default Value:-30
9 Counters
Table 9-1 Counter description
Counter ID Counter Name Counter Feature ID Feature Name
Description
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
11 Reference Documents
This chapter lists the reference documents related to power control:
[1] 3GPP TS 36.300, "Overall description, Stage 2"
[2] 3GPP TS 36.211, "Physical channels and modulation"
[3] 3GPP TS 36.213, "Physical layer procedures"
[4] 3GPP TS 36.331, "Radio Resource Control (RRC); Protocol specification"
[5] eNodeB MO Reference
[6] eNodeB Performance Counter Reference
[7] eNodeB Initial Configuration Guide
[8] ICIC Feature Parameter Description