Download as pdf or txt
Download as pdf or txt
You are on page 1of 30

pZeroNominalPusch /

pZeroNominalPucch
Trial results

PREPARED BY: ZAHER ZEITOUNEH


agenda

 TECHNICAL OVERVIEW
 pZeroNominalPucch/ pZeroNominalPusch TRIAL
 APPENDIX - COUNTERS DESCRIPTION

Ericsson Internal | 2013-04-05 | Page 2


PUSCH/PUCCH Power Control (1/2)
Uplink PSD (power spectrum density)Target =P/BW
PSDRX_Target = P0 = SINR +(N+I)
TPC: Transmit power control commands

Desired Rx target is
specified by parameter:
pZeroNominalPusch/
pZeroNominalPucch
and signaled in SIB2

UE
PUSCH/PUCCH Power
eNodeB

The uplink receiver at the eNB estimates the SINR of the received signal, and compares it with
the desired SINR target value.
When the received SINR is below the SINR target, a TPC command is transmitted to the UE to
request for an increase in the transmitter power. Otherwise, the TPC command will request for a
decrease in transmitter power.
Ericsson Internal | 2013-04-05 | Page 3
PUSCH/PUCCH Power Control (2/2)
 Noise Floor
– Noise Level = Nt + Nf + 10*log(Wrb)
where:
Nt = thermal noise power spectral density (-174 dBm/Hz)
Nf = noise figure of the receiver
Wrb = bandwidth per resource block 180 KHz / RB
– Calculated Noise Level (Ericsson) = -174 dBm/Hz + 2.2dB +
10*log(180000) => -119.2dB

 Target SINR Calculation –  Target SINR Calculation –


Example 1 Example 2
› Noise Level = -119.2dB › Noise Level = -119.2dB
› P0 Nominal = -117 dB › P0 Nominal = -110 dB (3 dB
› Target SINR = -117 - (-119.2) higher)
= 2.2 dB › Target SINR = -110 - (-119.2)
= 9.2 dB
Note: Interference is considered 0 in both examples for simplicity

Ericsson Internal | 2013-04-05 | Page 4


pZeroNominalPucch and
pZeroNominalPusch settings
 The two parameters (pZeroNominalPucch/Pusch) can be tuned to
find a trade off between UL capacity and peak throughput.

When pZeroNominalPUSCH/PUCCH set  When pZeroNominalPUSCH/PUCCH


to Low value. Set to High value
Pros Pros
 Less UE Tx power required Majority of cases there is Higher UL
 Less Inter-cell Interference created throughput.
 In few cases there is potential UL Larger cell Range.
throughput improvement for bad coverage
UE (In building UE) Cons
 Higher UE Tx Power required
Cons consequently more UE Battery
 Majority of cases there is lower UL consumption.
throughput for users closer to the site (with  Higher Interference level
good coverage)  In few cases there is potential UL
Smaller cell range. throughput degradation for UE in bad SINR
and coverage areas.

Ericsson Internal | 2013-04-05 | Page 5


Parameters Description
› EUtranCellFDD pZeroNominalPucch long
------------------------------------------------------------------------------------------------------------------------------------
The nominal component of the UE transmit power for Physical Uplink Control Channel (PUCCH).
Specifies the desired RX target for PUCCH
Unit: dBm
Resolution: 1
Disturbances: Changes may affect traffic.
Takes effect: Immediately.
Range: -127 to -96, Default=-117
************************************************************************************************************************************
EUtranCellFDD pZeroNominalPusch long
------------------------------------------------------------------------------------------------------------------------------------
The nominal component of the UE transmit power for Physical Uplink Shared Channel (PUSCH).
Specifies the desired RX target for PUSCH

Unit: dBm
Resolution: 1
Disturbances: Changes may affect traffic.
Takes effect: Immediately.
Range: -126 to 24, Default=-103

Ericsson Internal | 2013-04-05 | Page 6


agenda

 TECHNICAL OVERVIEW
 pZeroNominalPucch/ pZeroNominalPusch TRIAL
 APPENDIX - COUNTERS DESCRIPTION

Ericsson Internal | 2013-04-05 | Page 7


Test Cases
A trial was conducted to evaluate the network performance by
changing the P0 parameters values according to different test cases.
The trial was conducted on SHW cluster
Below table shows the test cases

 Parameters changes trials monitoring periods are below, each


monitoring period is highlighted with specific color on the stats graph.
A: From 12/03/2013 to 18/03/2013 - Blue Color
B: From 19/03/2013 to 26/03/2013 – Red Color
C: From 27/03/2013 to 03/04/2013 – Green Color

Ericsson Internal | 2013-04-05 | Page 8


UE Power Limitation

Case A Settings: Case B Settings: Case C Settings:


pZeroNominalPucch = -117 pZeroNominalPucch = -110 pZeroNominalPucch = -117
pZeroNominalPusch = -96 pZeroNominalPusch = -96 pZeroNominalPusch = -103

 Less UE’s are limited by UE TxPower due to lower pZeroNominal settings in test Case C.
 % UE Power limited = 100*(pmRadioTbsPwrRestricted)/(pmRadioTbspwrRestricted
+pmRadioTbsPwrUnrestriced)
 % UE Power Unlimited=100*(pmRadioTbsPwrUnrestriced)/(pmRadioTbspwrRestricted
+pmRadioTbsPwrUnrestriced)
Ericsson Internal | 2013-04-05 | Page 9
SINR PUCCH Distribution

 Higher SINR Values for pZeroNominalPucch set to -110 (Test Case B) due to
higher UeTx Pwr.
 Percentage of Distribution of SINR on PUCCH % = 100*(pmSinrPucchDistrX) /
Sum (pmSinrPucchDistr-0 to pmSinrPucchDistr-7)
Where : X = 0, 1, 2, 3, 4, 5, 6, 7
Ericsson Internal | 2013-04-05 | Page 10
SINR PUSCH Distribution

 Slightly Lower SINR values for parameters test case C.


 Percentage of Distribution of SINR on PUSCH % =100*( pmSinrPuschDistrX)
/ Sum (pmSinrPuschDistr-0 to pmSinrPuschDistr-7)
Where : X = 0, 1, 2, 3, 4, 5, 6, 7
Ericsson Internal | 2013-04-05 | Page 11
Radio Interference Power PUCCH

› Slight increase in interference power PUCCH for parameters settings case B.


› Percentage of Distribution of Interference Power on PUCCH % =
100*(pmRadioRecInterferencePwrPucchX) / Sum (pmRadioRecInterferencePwrPucch-0
to pmRadioRecInterferencePwrPucch-15)
Where X = 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15
Ericsson Internal | 2013-04-05 | Page 12
Radio Interference Power

 Slight increase on received interference power for parameters settings case B.


 Percentage of Distribution of Interference Power on PUSCH % = 100*(
pmRadioRecInterferencePwrX )/ Sum (pmRadioRecInterferencePwr-0 to
pmRadioRecInterferencePwr-15)
Where X = 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15
Ericsson Internal | 2013-04-05 | Page 13
Average Received Interference
Power
Case A Settings: Case B Settings: Case C Settings:
pZeroNominalPucch = -117 pZeroNominalPucch = -110 pZeroNominalPucch = -117
pZeroNominalPusch = -96 pZeroNominalPusch = -96 pZeroNominalPusch = -103

 Slight increase on received interference power for parameters settings


case B.
Ericsson Internal | 2013-04-05 | Page 14
UL_Throughput & Traffic

 Slight increase in average UL traffic and slight increase in average UL


throughput for parameters settings case B.
Ericsson Internal | 2013-04-05 | Page 15
DL_Throughput & Traffic

 No Change in the trend of DL traffic and DL throughput during the trial


period.

Ericsson Internal | 2013-04-05 | Page 16


RRC Success Rate

 No impact on RRC success rate during the trial period.

Ericsson Internal | 2013-04-05 | Page 17


Handover Success Rate

 No impact on Handover success rate during the trial period.

Ericsson Internal | 2013-04-05 | Page 18


Retainability

 No impact on Drop rate during the trial period.

Ericsson Internal | 2013-04-05 | Page 19


DRIVE test Results
 The following Drive tests for SHW cluster were used to study the
impact of each set of parameters on performance.
 The drive tests were conducted using the same drive test routes and
the following dates:
a. 01/25/2013 @ 3:00 AM – For parameters settings case A.
b. 22/03/2013 @ 10:30 PM – For parameters settings case B.
c. 02/04/2013 @ 10:30 PM – For parameters settings case C.

 The drive test for case A is depicted on the graphs for reference only
and shall not be used to draw conclusions from it as it was measured
at off peak period and at different time from the other cases.

Ericsson Internal | 2013-04-05 | Page 20


DRIVE Test Results
 Drive test with the
parameters
settings for case
C are showing the
least throughput
and UE TX Power
which is in
accordance to
expectations.
 Drive test with the
parameters
settings for case
A is irrelevant to
the comparison
with cases B and
C as it was done
at Off Peak
Period.
Ericsson Internal | 2013-04-05 | Page 21
Conclusion
 Parameters settings case B (pZeronNominalPUCCH= -110 &
pZeroNominalPUSCH = -96) shall be deployed network wide due to the
following observations:
› Improvements in Reported SINR Values.
› Improvements in UL traffic and improvement in UL throughput (Stats and
Drive test).
› Increase in UE Tx Power for case B parameters settings but it is not
affecting the performance.
› Very slight increase in UL RSSI as a consequence of increasing
pZeroNominalPUCCH but it is not performance affecting.
› No impact on drop rate, RRC success rate, Handover success rate with
parameters settings case B.

 The parameters settings (pZeroNominalPucch = -117 &


pZeroNominalPusch = -103) shall be used on the special events highly
loaded based on a previous recommendation by Ericsson.
Ericsson Internal | 2013-04-05 | Page 22
agenda

 TECHNICAL OVERVIEW
 pZeroNominalPucch/ pZeroNominalPusch TRIAL
 APPENDIX - COUNTERS DESCRIPTION

Ericsson Internal | 2013-04-05 | Page 23


Appendix – Counters Description

Ericsson Internal | 2013-04-05 | Page 24


pmRadioTbsPwrRestricted/
pmRadioTbsPwrUnrestricted
EUtranCellFDD pmRadioTbsPwrRestricted long PEG
------------------------------------------------------------------------------------------------------------------------------------
The number of Transport Blocks on MAC level scheduled in uplink where the UE was considered to be power limited.
Unit: -
Condition: A Transport Block is considered to be power limited when the estimated required transmit power is higher than
the UE maximum transmit power.
Counter type: PEG
Scanner: Not included in any predefined scanner
Counter is reset after measurement period: Yes
************************************************************************************************************************************
EUtranCellFDD pmRadioTbsPwrUnrestricted long PEG
------------------------------------------------------------------------------------------------------------------------------------
The number of Transport Blocks on MAC level scheduled in uplink where the UE was NOT considered to be power
limited.
Unit: -
Condition: A Transport Block is considered to be power limited when the estimated required transmit power is higher than
the UE maximum transmit power.
Counter type: PEG
Scanner: Not included in any predefined scanner
Counter is reset after measurement period: Yes

Ericsson Internal | 2013-04-05 | Page 25


pmSinrPucchDistr
EUtranCellFDD pmSinrPucchDistr sequence:long [8] PDF
------------------------------------------------------------------------------------------------------------------------------------
Distribution of the SINR values calculated for PUCCH .
PDF ranges:
[0]: SINR <= -15
[1]: -15 < SINR <= -12
[2]: -12 < SINR <= -9
[3]: -9 < SINR <= -6
[4]: -6 < SINR <= -3
[5]: -3 < SINR <= 0
[6]: 0 < SINR <= 3
[7]: 3 < SINR
Unit: dB
Condition: Each SINR value for PUCCH per UE calculated on a TTI basis yields one sample in the distribution.
Counter type: PDF
Scanner: Not included in any predefined scanner
Counter is reset after measurement period: Yes
MaxLength=8

Ericsson Internal | 2013-04-05 | Page 26


pmSinrPuschDistr
EUtranCellFDD pmSinrPuschDistr sequence:long [8] PDF
------------------------------------------------------------------------------------------------------------------------------------
Distribution of the SINR values calculated for PUSCH .
PDF ranges:
[0]: SINR <= -5
[1]: -5 < SINR <= -2
[2]: -2 < SINR <= 2
[3]: 2 < SINR <= 6
[4]: 6 < SINR <= 10
[5]: 10 < SINR <= 14
[6]: 14 < SINR <= 17
[7]: 17 < SINR
Unit: dB
Condition: Each SINR value for PUSCH per UE calculated on a TTI basis yields one sample in the distribution.
Counter type: PDF
Scanner: Not included in any predefined scanner
Counter is reset after measurement period: Yes
MaxLength=8

Ericsson Internal | 2013-04-05 | Page 27


pmRadioRecInterferencePwr
EUtranCellFDD pmRadioRecInterferencePwr sequence:long [16] PDF
------------------------------------------------------------------------------------------------------------------------------------
The measured Noise and Interference Power on PUSCH, according to 36.214
PDF ranges:
[0]: N+I <= -121
[1]: -121 < N+I <= -120
[2]: -120 < N+I <= -119
[3]: -119 < N+I <= -118
[4]: -118 < N+I <= -117
[5]: -117 < N+I <= -116
[6]: -116 < N+I <= -115
[7]: -115 < N+I <= -114
[8]: -114< N+I <= -113
[9]: -113 < N+I <= -112
[10]: -112 < N+I <= -108
[11]: -108 < N+I <= -104
[12]: -104 < N+I <= -100
[13]: -100 < N+I <= -96
[14]: -96 < N+I <= -92
[15]: -92 < N+I
Unit: dBm/PRB
Condition: A wideband value for the frequency domain is measured on a TTI basis
Counter type: PDF
Scanner: Not included in any predefined scanner
Counter is reset after measurement period: Yes
MaxLength=16

Ericsson Internal | 2013-04-05 | Page 28


pmRadioRecInterferencePwrPucch
EUtranCellFDD pmRadioRecInterferencePwrPucch sequence:long [16] PDF
------------------------------------------------------------------------------------------------------------------------------------
The measured Noise and Interference Power on PUCCH, according to 36.214.
PDF ranges:
[0]: N+I <= -121
[1]: -121 < N+I <= -120
[2]: -120 < N+I <= -119
[3]: -119 < N+I <= -118
[4]: -118 < N+I <= -117
[5]: -117 < N+I <= -116
[6]: -116 < N+I <= -115
[7]: -115 < N+I <= -114
[8]: -114< N+I <= -113
[9]: -113 < N+I <= -112
[10]: -112 < N+I <= -108
[11]: -108 < N+I <= -104
[12]: -104 < N+I <= -100
[13]: -100 < N+I <= -96
[14]: -96 < N+I <= -92
[15]: -92 < N+I
Unit: dBm/PRB
Condition: A wideband value for the frequency domain is measured on a TTI basis
Counter type: PDF
Sampling rate: -
Scanner: Not included in any predefined scanner
Counter is reset after measurement period: Yes
MaxLength=16

Ericsson Internal | 2013-04-05 | Page 29


Ericsson Internal | 2013-04-05 | Page 30

You might also like