Huawei WCDMA Radio Parameters Optimization Cases

10/31/15
WCDMA Radio Parameters

Optimization Cases
For internal use

1 © Nokia Siemens Networks Charles / 2009-05-05
Parameters Optimization Flow Chart
Parameters
Optimization
start
Configuration Signaling Drive test data Statistics data

data trace data collection collection Parameters tuning
collection collection
NO Data analysis and

KPI is
OK? optimization
YES
Parameters
optimization
ends.
For internal use

Page 2
Radio Parameters Optimization Cases
1. Coverage parameters optimization cases

2. Intra frequency handover parameters
optimization cases
3. Inter-RAT handover parameters optimization
cases
4. CS call drop rate optimization cases
5. PS call drop rate optimization cases
6. Access control parameters optimization cases
7. BLER parameters optimization cases
8. Soft handover ratio optimization cases
For internal use

Page 3
The coverage parameters being tuned
frequently
Coverage Parameters:
No Parameters
Description Default value
. Name
1 RLMaxDLPwr RL Max DL TX power[0.1dB] 0 for AMR
2 RLMinDLPwr RL Min DL TX power[0.1dB] -150(-15dB) for AMR
3 MaxTxPower Max transmit power of cell[0.1dBm] 430 (43dBm)
4 PCPICHPower PCPICH transmit power[0.1dBm] 330 (33dBm)
5 MaxPCPICHPowe Max transmit power of PCPICH[0.1dBm] 346 (34.6dBm)
r
6 MinPCPICHPower Min transmit power of PCPICH[0.1dBm] 313 (31.3dBm)
Local Cell Radius(m). This is a parameter in
7 RADIUS 30000 (30km)
NodeB.
For internal use

Page 4
Coverage parameters optimization cases
Case 1: Increase the PCPICH Power to improve the coverage
Case 2: Increase DL maximum power of AMR to improve call drop rate
Case 3: Increase FACH power to improve RRC setup success rate
Case 4: Optimize the timer T300 to improve RRC success Rate
Case 5: UE cannot access due to cell radius settings
For internal use

Page 5
Increase the PCPICH Power to improve the
coverage
Problem Description:
• The RSCP is not
good ；
Suggest a
• The EcIo is bad ； new site
• Add a new site is very
difficult 。
For internal use

Page 6
Increase the PCPICH Power to improve the
coverage
RSCP Before increasing RSCP after Increasing EcIo Before increasing EcIo after Increasing
Pcpich Power Pcpich Power 3dB Pcpich Power Pcpich Power 3dB
Increase PCPICH Power 3dB to improve the coverage.
1. How to modify the maximum PCPICH power?

MOD PCPICHPWR: CELLID=30141, MAXPCPICHPOWER=360;
MOD CELL: CELLID=30141, PCPICHPOWER=360;
2. How to modify the minimum PCPICH power?

MOD PCPICHPWR: CELLID=13011, MINPCPICHPOWER=300;
MOD CELL: CELLID=13011, PCPICHPOWER=300;
For internal use

Page 7
Case 2: Increase DL maximum power of AMR to improve call drop
rate
For internal use

Page 8
Increase DL maximum power of AMR to improve call
drop rate
Call drop
increasing
a)In T network, during the WCDMA network swapping from S to Huawei, CS call drop rate
of Cluster 14 rose from 13th July, from 0.45% to more than 0.6%. Before swap the CS drop
rate is only 0.48%. The upper figure is the CDR of Cluster 14 from Jul.4 to Jul. 24.
b) Most call drop reason is SRB reset, most times RNC sent ASU to UE but did not receive
the response. The signal in drop points is very weak, RSCP is about -110dBm and most
drops happened just after connection establishment.
c) This area is near Mediterranean Sea, most coverage is beach and highway. The
increasing traffic is due to tourists.
For internal use

Page 9
drop rate
a) Firstly we check the Huawei power
configuration and found the FACH power (34dBm)
is high than maximum AMR DCH DL power
(33dBm), this explained why in some area in cell
edge, the UE can access to network but cannot keep
the connection.
b) Then we check the S power configuration. The
maximum DL DCH power of S AMR service is
36dBm.
c) So in S network, if UE can setup call, it
will not drop due to DL power. That
explain why S call setup KPI in worse
than Huawei but call drop is better than
Huawei.
The maximum DL DCH power of S AMR service is 36dBm as following table.
For internal use

Page 10
drop rate
DL DCH maximum power of AMR service was changed from 33dBm to 35dBm in cluster 14 on
2th August, and then the CS drop rate decreased as following figure.
How to modify the maximum power of AMR from 33dBm to 35dBm?
MOD CELLRLPWR:CELLID=0, CNDOMAINID=CS_DOMAIN, MAXBITRATE=12200,

RLMAXDLPWR=2, RLMINDLPWR=-130, DLSF=D128;
Mod Power for AMR
CS12.2 CS64 PS32 PS64 PS144 PS256 PS384
Default 0 +3 -4 -2 +0 +2 +4
value
HK 0 +1 -4 0 +2 +2 +3
UAE -3 +3 -4 -2 0 +2 +4
NL -3 +1 -4 0 +1 +2 +3
For internal use

Page 11
For internal use

Page 12
Increase FACH power to improve RRC setup success
rate
From KPI in last few months, there were some RRC setup failures. It was mainly caused during reselection and
registration.
Signaling for RRC Setup
RRC Setup Failure Distribution
UE NodeB RNC
40000 100%
35000 98% 1. CCCH: RRC CONNECTION REQUEST
RRC RRC
30000 96%
25000
94%
20000 2 . Allocate parameters
92% Such as RNTI, L1,L2
15000
10000 90%
3. RADIO LINK SETUP REQUEST
5000 88%
NBAP NBAP
0 86%
Orignating Terminating Reselection Registration 4. RADIO LINK SETUP RESPONSE
NBAP NBAP
RRC Setup Failure RRC Setup Success Rate
5. ALCAP Setup and Synchronization
6.CCCH RRC CONNECTION SETUP

RRC RRC
7.DCCH RRC CONNECTION SETUP COMPLETE

RRC RRC
RRC setup failure for poor coverage

RNC send RRC Connection Setup to UE after receiving
RRC Connection Request from UE. So UL is ok. But RNC
cannot receive RRC Connection Setup Complete from UE.
So the cause is DL poor coverage.
For internal use

Page 13
Increase FACH power to improve RRC setup success
rate
1. Optimize “MAXFACHPOWER”.
RRC Setup statistics
The value is maximum transmit power of FACH,
and it’s -1dB in live network. We suggest Increasing FACH
RRC SETUP
Power 2dB
changing it to 1 dB. It means the FACH power
is 34dBm. 350 96%
94%
300
250 92%
2. In live network, NodeB maximum transmit 200 90%
88%
power is 43dBm, and supposing all the other 150 86%
100 84%
common channels the same as before. We 50 82%
0 80%
calculate the influence for live network,
especially for capacity.
 FACH: changed from 32dBm to 34dBm,
and active factor is 0.25, then it’ll influence RRC SETUP FAILURES RRC SETUP SUCCESS RATE
DCH: 0.25*(10^ ((34-43)/10)-10^ ((32-
43)/10)) =1.16% From the figure above, it was shown that RRC
 This impact is acceptant because live setup failures decreased from 288 to 158 and
network is limited by coverage. RRC setup success rate increased from 87%
to 94%.
If increase FACH power, then it will decrease the RRC setup failure due to UU no reply.
For internal use

Page 14
For internal use

Page 15
Optimize the timer T300 to improve RRC success
RRCRate
Failure Rate was 0.79% before the swap, but it increased to 1.32 ％ after swap. The KPI is worse than
before.
Minimum Clusters Before Switch
Name
Requirement C1 C2 C3 C4 C5 C6 C7 C8 Whole City
RRC Connection
Requests - SUM
in the trend 4561743 5478662 6165218 5232258 8830561 5000059 6445880 478572 42221482
RRC Connection
Requests - RAB
in the trend 1867148 2311263 1574192 2193172 2590867 2084147 1937424 55085 14630080
RRC Connection
Requests - IRAT in the trend 1496278 1256319 950827 883108 1001577 891959 1169277 337931
Cell Reselection 7992077
RRC Failure
Rate "=< 10%" 0.75% 0.63% 1.01% 0.78% 0.70% 0.75% 0.90% 0.95%
- SUM (%) 0.79%
Minimum Clusters After Switch - Weekly KPI （ HUAWEI ）

Name
Requirement C1 C2 C3 C4 C5 C6 C7 C8 City Level
RRC Connection
Requests - SUM
in the trend 6255259 6380468 5064183 5298305 7093489 4868310 5521603 0 40370612
RRC Connection
Requests - RAB
in the trend 2048127 2398928 1653128 2357844 2749713 2208816 2354256 0 15707398
RRC Connection
Requests - IRAT in the trend 1386870 1317011 1127359 1013396 1004143 890266 1425679 0 8146314
Cell Reselection
RRC Failure Rate 0.00

"=< 10%" 1.36% 1.08% 1.85% 1.07% 1.25% 1.09% 1.59% 1.32%
- SUM (%) %
For internal use

Page 16
Rate
 Usually the RRC setup success rate for other services is about 97%~99% in Huawei commercial
network. But the KPI acceptance is requested for 99.2% in this network.
 RRC setup failure mainly is due to RNC doesn’t receive the RRC_CONNECTION_SETUP_CMP from
UE through statistics. And most of reason is RRC no reply for register and inter-Rat cell reselect.
1. RRC no reply for register is about 48%, and RRC no reply for inter-Rat cell reselect is
26%.
2. We increased the FACH power offset from 1dB to 1.5dB, the RRC setup failure rate decreased 0.13%.
3. Modified the N300 from 3 to 4, and RRC setup failure rate improved a little.
For internal use

Page 17
1.
Rate
Modified the T300 from 2s to 0.4s on 20th March. And the RRC setup success rate improved from
98.9% to 99.3%.
2. RRC setup failure rate is about 0.73% in the acceptance test.
Notes:T300 is started when UE sends the RRC CONNECTION REQUEST message. It is stopped when UE receives the
RRC CONNECTION SETUP message. RRC CONNECTION REQUEST will be resent upon the expiry of the timer if V300
is lower than or equal to N300, else enter idle mode. Recommended value: D2000.
1. RNC will repeat to send RRC_CONN_SETUP message to UE 2 times in each TTI in spite of
receiving the RRC_CONN_SETUP_CMP message or not for another vendor. Huawei RNC does not
support this function. RRC_CONN_SETUP message will repeat to send after T300 expires.
2. Why the RRC setup success rate was improved after the T300 was shortened?
a) It is due to the RRC_CONN_SETUP message is repeated to send to UE in a short time before
UE fails to access and reselect to another cell.
b) If the UE fails to access due to poor coverage, it will reselect to another cell and access
again. This access is measured another access and the denominator is increased in the KPI
formula.
For internal use
Page 18
For internal use

Page 19
UE cannot access due to cell radius
settingsis -2dB
RSCP is -72dBm,EcIo
Why
does
access
fail ？
11.3km
cover
the sea.
PSC304 PSC304
 RNC didn’t receive the RRC Setup

Request signaling because the cell
radius is set 10KM and UE accessed
far from 11.3km.
 The command modified the cell radius
is as following:
MOD LOCELL: LOCELL=12111,
RADIUS=30000
For internal use
Page 20

optimization cases
cases
For internal use

Page 21
The soft handover parameters being tuned
frequentlyDescription
Parameter Default Setting
Name
IntraRelThdFor1A Relative thresholds of soft handover for Event 6 , namely 3dB (step 0.5)
1A (R1a)
IntraRelThdFor1B Relative thresholds of soft handover for Event 12 , namely 6dB (step 0.5)
1B (R1b)
Hystfor1A, Hystfor1B, Soft handover hysteresis (H1x) 0dB for H1a, H1b .
Hystfor1C, Hystfor1D 8,namely 4dB(step 0.5) for
H1c,H1d.
CIOOFFSET Neighboring cell oriented Cell Individual Offset 0
(CIO)
TrigTime1A,TrigTime1 Soft handover time-to-trigger parameters. 320ms for 1A, 640ms for 1B, 1C,1D
B, 1A (Add a cell in Active Set)

TrigTime1C,TrigTime1 NA
 
D 10  LogMNew New  CIO  W 10  Log 
i    (1  W ) 10  LogM
M Best  ( R1a  H 1a / 2)
FilterCoef 1 
Filter coefficient of L3i intra-frequency  D3 ,namely 3
measurement
MNew : the measurement result of the cell entering the reporting range.
CIONew : the individual cell offset for the cell entering the reporting range.
Mi : measurement result of a cell not forbidden to affect reporting range in the active set.
NA : the number of cells not forbidden to affect reporting range in the current active set.
MBest : the measurement result of the cell not forbidden to affect reporting range in the
active set with the highest measurement result, not taking into account any cell individual
offset.
W: a parameter sent from UTRAN to UE.
R1a : the reporting range constant.
H1a : the hysteresis parameter for the event 1a.
For internal use

Page 22
Intra frequency handover parameters
optimization cases
Case 1: Parameters optimization for corner effect case
Case 2: Parameters optimization for handover area being small
Case 3: Ping-Pong handover optimization case
Case 4: Parameters optimization for handover not in time when taking the elevator
Case 5: Handover Failure due to the improper cell radius
For internal use

Page 23
Parameters optimization for corner
effect case
Problem Description: Call dropped

Call drops often occur at the
corner.
At the corner, the service cell signals

quickly decrease, the target cell signals
quickly increase in a short time, and the
UE fails to receive the ASU command,
which leads to the call drop.
For internal use

Page 24
Parameters optimization for corner
effect case
The cell PSC265, the distance is 6.5km, using The cell PSC304, the distance is 11km, using the
the Yagi antenna. Yagi antenna.
· PSC265
PSC265
PSC304
 Parameters tuning
① The CIO between PSC265 and PSC304 is modified 10( 5dB);
② The delay of 1A event, modify from 320ms to100ms ；
③ Increase the PCPICH power of PSC265 and PSC304 3dB, to improve the coverage.
 The result
① The call drop reduce after the parameters tuning.
For internal use

Page 25
The coverage comparing of different operator at the
corner H 3G SMT 3G
C 3G S 3G (Huawei)
For internal use

Page 26
optimization cases
For internal use

Page 27
Parameters optimization for handover area being
small
The sites distribution for Maglev train  The maglev train test
2.9km network;
1.0km  The maximum speed is
431km/h;
 Sometimes call drop
4.2km
due to the handover
5.7km area is small.
The call
dropped place
The speed distribution
<=100km
/h
0 0k
<=2
m/h
k
3 00
<= h
m/ <=400km/h <=431km/h
For internal use

Page 28
small
The RSCP in the maglev train
The call
dropped The signaling handover between
Poor
coverage
Out of PSC180 and PSC170
coverage
For internal use

Page 29

small
Simulation of handover area ：
① Andrew-UMWD-03319-0DM, gain is 20.6dBi, downtilt is 2 degrees. According to simulation the
handover is only 28m ；
② Increase the CIO between Cell1 and Cell2 5dB, the handover area is 98m according to simulation
 The speed and handover ：
Generally the handover delay is about 200 ～ 600ms, UE measurement the neighbor
cell need some time, suppose the handover 800ms, so the speed and handover
relation is as follows:
UE Speed (km/h) 100 200 300 400
Handover area (m) 22 44 66 88
How to modify the parameters of handover
① CIO between PSC180 and PSC170 change to
10( 5dB);
② Reduce TrigTime1A from 320ms to 100ms; Cell1 Cell2
③ IntraRelThdFor1ACS change from 3dB to 5.5dB;
④ IntraRelThdFor1BCS change from 6dB to 8dB;
⑤ IntraFreqFilterCoef change from D3 to D2.
 Result after the parameters tuning
CIO
a) The call dropped times reduce, but we still find call
dropped in this area.  N A
10  LogM New  CIONew  W  10  Log   M i 


 (1  W )  10  LogM Best  ( R1a  H1a / 2),
b) At last we use the splitting the sector.  i 1 
For internal use

Page 30
optimization cases
For internal use

Page 31
Ping-Pong handover optimization case
 Ping-Pong handover
The active set cell change
frequently between the same cells.
Before call dropped the signal of SC56 is below

-18dB, so the SC56 was deleted from active set, the
active set is left SC64 and SC66, but the two cells
became so worse in a short time. So the call dropped.
SC64/66 signal become

so worse in a short time
 How to decrease Ping-Pong handover ?

This can enlarge intra-frequency
measurement coefficient and time to
trigger.
For internal use

Page 32
Ping-Pong handover optimization case
The cell SC 56 was deleted from active The UE reported the 1A event of cell SC
set. 56.
The cell of SC64/66
became so worse in
a short time
Delete the Report 1A

cell SC56
event of SC56
The method of Ping-Pong handover.

① Parameters tuning
a) Increase the TrigTime1B from 640ms to 1280ms or 2560ms.
b) IntraRelThdFor1BCS change from 6dB to 8dB;
c) IntraFreqFilterCoef change from D3 to D4.
② RF tuning
For internal use

Page 33
optimization cases
Case 4: Parameters optimization for handover not in time when taking the
elevator
For internal use

Page 34
Handover not in time when taking the
elevator
Elevator and indoor coverage Outdoor Cell B
Problem description:
sketch map
① There is a DAS in 13th floor and
Elevator
1th floor in one building by cell A, B
and no coverage for the elevator. So
电
the elevator is covered by outdoor 梯
cell B.
② It often call drop when enter or

out elevator in the 1th floor. Indoor Cell A (13F)
Cell A
(1F)
For internal use

Page 35
Handover not in time when taking the
elevator
The EcIo change so fast when the door of elevator is closed or opened.
The red EcIo is covered by indoor cell A,
Cell A
Cell B and green EcIo is covered by outdoor cell
B.
 When the door is opened, the signal
of cell A is very strong, so the EcIo of
cell B become -20dB immediately in
the active set. If the cell A is not
added into active in time, it will call
drop.
Open
the  The signal of cell A become so worse
door Close when the door is closed, and the
the signal of cell B become very strong
door immediately. If the cell B is not added
into active in time, it will also call
drop.
 From the signaling, you can find that
Solutions: UE has already reported 1A event,
① CIO between cell A and cell B change tobut
10(UE5dB);
call drop before receiving the
② Reduce TrigTime1A from 320ms to 0ms;ASU message.
③ IntraFreqFilterCoef change from D3 to D1.
④ RF tuning, using the indoor coverage system to cover the
elevator.
For internal use

Page 36
optimization cases
Case 5: Handover Failure due to the improper cell handover radius
For internal use

Page 37
Handover Failure due to the improper cell handover
radius
Analysis of call drop point
 At the call drop spot, the radio environment is good.
By the drive test, before and after the call drop, both Call
Ec/Io and RSCP are good. The call drop always drop Call
occurs during each drive test and the call drop spot area drop
area
is similar.
SC176 Ec/Io SC192 Ec/Io
UE TxPWR
UE transmit
power is
increased before
call drop.
For internal use

Page 38
Handover Failure due to the improper cell handover
radius Problem troubleshooting
 The newly added radio link is not synchronized, and ASU is delivered to delete the scrambles of
cell 176 from the active set. The quality of scrambles in cell 192 is bad, so the call drop occurs.
The uplink asynchronization may be caused by the following:
 Uplink interference --- check the RTWP of cell 176
 Parameter setting problem - LST LOCELL
Through the RTWP tracing, the RTWP

of the cell is about -105 dBm.
Check the cell handover radius and
find that the inner diameter of handover
radius is 5000m. The configuration is
abnormal. It indicates that UE cannot
perform the handover within 5000 m.
The parameter is set to 0m by default.
 Fixing
 Change the handover radius to 0. And the call drop
disappears.
 Local Cell Inner Handover Radius (m): The inner
handover radius of the local cell must not be
greater than cell radius.
MOD LOCELL: LOCELL=11111, HORAD=0;
For internal use

Page 39

optimization cases
cases
For internal use

Page 40
Inter-RAT handover parameters optimization
cases
Case 1: The parameters optimization for pingpong Inter-RAT cell reselection in
idle state
Case 2: Parameters optimization case of Inter-RAT handover not in time into tunnel
Case 3: The case for CS Inter-RAT Preparation handover failure
Case 4: Inter-RAT PS handover Failed due to 2G Cell Barred
Case 5: Inter-RAT PS handover Failed due to DNS settings in SGSN
For internal use

Page 41
The parameters optimization for pingpong Inter-
RAT cell reselection in idle state
UE change to camp in 3G or 2G so frequently in idle state in one building.
RSCP EcIo
For internal use

Page 42
The cell reselection parameters of 3G to 2G is as following:
① Min quality level :Qqualmin = -18 (-18dB)
② Min Rx level: Qrxlevmin = -58 (-115dBm)
③ Inter-RAT cell reselection threshold: SsearchRAT = 2
(Qqualmin+2*SsearchRAT=-14dB)
The cell reselection parameters of 2G to 3G is as following:
① Inter-RAT measurement start threshold: Qsearch_I = 7 (Always search for 3G cells)
② Cell reselection offset: FDD_Qoffset = 0 (-∞, always select to a cell if acceptable)
 FDD_Qoffset ： 0 = -  (always select a cell if acceptable),1 = -28 dB, 2 = -24 dB, … , 8 =
0dB ， 9 = 4 dB, … , 15 = 28 dB.
③
Cell reselection 3G RX level threshold: FDD_Qmin = 0 (-20dB)
 FDD_Qmin ： 0= -20dB, 1= -6dB, 2= -18dB, 3= -8dB, 4= -16dB, 5= -10dB, 6= -14dB, 7= -12dB.
• When the EcIo of 3G is lower than -14dB, UE will start to measure the GSM signal
and maybe reselect to 2G.
• UE will always measure the 3G signal in 2G network. And if the EcIo of 3G is higher
than -20dB, UE will reselect to 3G in spite of the 2G coverage.
• When the EcIo of 3G changes between -14dB to -20dB, UE will reselect between 3G
and 2G frequently.
Solutions:
Increase the FDD_Qmin from -20dB to -10dB. Usually we suggest the value is 7 (-
12dB).
For internal use
Page 43
1. If Sx > Sintrasearch, UE need not perform intra-frequency measurements.
If Sx <= Sintrasearch, perform intra-frequency measurements.
If Sintrasearch, is not sent for serving cell, perform intra-frequency measurements.
2. If Sx > Sintersearch, UE need not perform inter-frequency measurements.

If Sx <= Sintersearch, perform inter-frequency measurements.
If Sintersearch, is not sent for serving cell, perform inter-frequency measurements.
3. If Sx > SsearchRAT, UE need not perform measurements on cells of RAT.

If Sx <= SsearchRAT, perform measurements on cells of RAT.
If SsearchRAT, is not sent for serving cell, perform measurements on cells of RAT.
Sx=Squalmeas - Qqualmin
Qqualmin Minimum required quality level corresponding to the CPICH Ec/No. UE can camp on the cell only when the CPICH Ec/No
measured is larger than the value of this parameter. Recommended value: -18(dB).
Qrxlevmin Minimum required RX level corresponding to the CPICH RSCP. UE can camp on the cell only when the measured CPICH
RSCP is larger than the value of this parameter. Recommended value: -58.
IdleSintrasearch Threshold for intra-frequency cell reselection in idle mode. When the quality (CPICH Ec/No measured by the UE) of the
serving cell is lower than this threshold plus the [Qqualmin] of the cell, the intra-frequency cell reselection procedure will be
started.
IdleSintersearch Threshold for inter-frequency cell reselection in idle mode. When the quality (CPICH Ec/No measured by UE) of the serving
cell is lower than this threshold plus the [Qqualmin] of the cell, the inter-frequency cell reselection procedure will be started.
Ssearch.RAT Threshold for inter-RAT cell reselection. When the quality (CPICH Ec/No measured by UE) of the serving cell is lower than
the threshold plus the minimum required quality ( Qqualmin) of the cell, the inter-RAT cell reselection procedure will be
started. It's mandatory When the value of parameter SsearchratInd is TRUE. Recommended value: 2, step is 2dB.
For internal use

Page 44
cases
Case 1: The parameters optimization for pingpong Inter-RAT cell reselection in idle state
Case 2: Parameters optimization case of Inter-RAT handover not in time into
tunnel
For internal use

Page 45
Optimization case of Inter-RAT handover not in time into
 tunnel
The cell 54493 cover outer
tunnel and no UMTS coverage in
the tunnel. Inter-RAT handover
 There are 2G coverage in the not in time
tunnel.
 The inter-RAT handover success
rate is not high from the cell
54493 to 2G. Inter-RAT
 The inter-RAT handover data is handover area
as following table in one week. Tunnel
 And the success
Modified the rate is about
80%.
InterRATCSThd2DRSCP from
-95dBm to -85dBm, and UE
will report 2D event in
advance in order to the inter-
RAT handover is in time.
 It is suggested that the RAT
InterRATFilterCoef is reduced VS.IRA IRATH VS.CS.
Time(As object HHO
from the D3 to D2. THO.Fa O.Succ Call.Dr
CellId distinct) SUCC
ilOutCS OutCS op.Cell
The inter-RAT handover parameters RATE
optimization include: 2D & 2F Event
threshold, GSM RSSI threshold, Inter- 54493 2006-2-6 to 2-12 62 315 251 80%
RAT handover trigger time, inter-RAT
measurement filter coefficient, CIO
and hysteresis.
For internal use

Page 46
cases
For internal use

Page 47
The case for CS Inter-RAT Preparation handover
failure
From May 25th, the CS Inter-RAT Handover Preparation Success Ratio of RNC 321
decreased greatly, and continued, the Handover Execution Success Ratio also dropped.
The detail information of the

RELOCATION_PREPARATION_FAILURE is as following.
Do the IOS trace, the failure always happen after the RNC send
message RELOCATION_REQUIRED to CN, and the CN return
the RELOCATION_PREPARATION_FAILURE, and the failure
reason is Semantic error, which is shown below:
According to the 3GPP 25.413, This is a Protocol Cause that means that " The received message
included a semantic error." so, the information contained within the message is not valid.
For internal use

Page 48
The case for CS Inter-RAT Preparation handover
failure
From the message analysis, if the parameter is wrong At the same time the CS inter RAT handover
configured, the LAC maybe wrong, check the 2G LAC success rate is also increase much.
information, really many inconsistent LAC information,
after modified the LAC information, the CS inter RAT
preparation handover success rate is normal, which is
shown below:
the LAC information should be consistent in RNC, CN and BSC, or else, one of them is insistent,
the inter-RAT handover will fail.
For internal use

Page 49
cases
For internal use

Page 50
Inter-RAT PS handover Failed due to 2G Cell
Barred
The PS inter-RAT handover success rate decreased from 88% to 78% at one day.
The following table shows TOP 10 cells for PS I-RAT handover failure and the reason for one whole day.
VS.IRATHO.Fai
GSMCe Time(As VS.IRATHO.AttOu VS.IRATHO.Succ OutPSUTRAN.
Cell ll day) tPSUTRAN.N OutPSUTRAN.N UEFN
37141 16156 2008-10-28 123 0 123

37141 16159 2008-10-28 55 0 55
37141 16157 2008-10-28 52 0 52
VS.IRATHO.FailOutPS VS.IRATHO.AttOutPSU IRATHO.FailOutPSUT IRATHO.FailOutPSUT VS.IRATHO.FailOutPS

Cell Id Date
UTRAN.Cell TRAN RAN.CfgUnsupp RAN.PhyChFail UTRAN.Other
37141 2008-10-28 230 232 0 230 0
36746 2008-10-28 29 38 0 7 22
36135 2008-10-28 24 54 0 20 4
37006 2008-10-28 20 28 0 20 0
37212 2008-10-28 15 47 0 10 5
36889 2008-10-28 10 33 0 1 9
36767 2008-10-28 7 21 0 1 6
37007 2008-10-28 7 15 0 5 2
36559 2008-10-28 6 22 0 6 0
37079 2008-10-28 6 38 0 2 4
For internal use

Page 51
InterRAT PS handover Failed due to 2G Cell
Barred
PS IRAT failure is due to the GSM cell 16156 was

barred.
For internal use
Page 52
InterRAT PS handover Failed due to 2G Cell
Barred
The PS inter-RAT handover success rate increased from 78% to 88% after the 2G neighbor cells were deleted.
Because the cell was barred only for GPRS, we should modify the GSM cells type RatCellType from
GPRS to GSM, it means these cells not configuration for PS handover to GSM. It had better not delete
the CS neighobor cell, otherwise it affects the CS handover.
The command modified the GSM type is as following:
MOD GSMCELL: GSMCellIndex=16156, RatCellType=GSM, SuppPSHOFlag=FALSE;
For internal use

Page 53
cases
For internal use

Page 54
Inter-RAT PS handover Failed due to DNS settings in
SGSN
The following table shows the one day PS inter-RAT attempts and PS service inter-RAT handover success
rate in one week, the PS inter-RAT handover success rate is only 85%, it is lower than acceptance target
90%.
From the signaling, you can find that after RNC decides to
handover from 3G to 2G and send
Cell_Change_Order_From_UTRAN to UE, others procedures
are not related to RNC anymore.
And RNC just waits for the IU_Release_Command from
SGSN.
For internal use
Page 55
SGSN
Abnormal Routing area update and attach from 2G side caused the failure of the
PS I-RAT.
For internal use
Page 56
SGSN
1. The direct cause of the PS Inter-RAT failure is no reply from SGSN before the timer expire.
2. When UE handover to 2G the routing area update request is rejected by CN. The failure of the
routing area update from 2G side will delay the SGSN sending the “IU release message” to RNC to
confirm the handover is completed. So if RNC does not received this message from SGSN before the
timer expire, RNC will count the PS IRAT fail due to no reply from SGSN.
3. From the test, we found many cases that SGSN sends the “IU release Message” to RNC when the
routing area update rejected, but the release reason is normal release. In this case RNC will count
the handover as a success one. This is the SGSN problem.
VS.IRATHO.SuccO Physical channel Other reasons (mainly
LAC RAC utPSUNTRAN.Cell. failure Rate in PS HO due to IU release timer Routing Area Update after PS IRAT HO
Rate Failure reason expiry ) Rate
5636 199 95.02% 62.50% 37.50% RAU Accept.
5536 198 92.02% 83.53% 16.47% RAU Accept.
6036 111 79.38% 28.57% 71.43% RAU Reject due to implicitly detached.
Check the RAC in SGSN, and find some RAN not configured in the DNS table in SGSN.
For internal use

Page 57
SGSN
The PS inter-RAT handover success rate improved from 86% to 93% after CN
changed the DNS configuration in SGSN
Change the DNS

configuration in SGSN
For internal use

Page 58

optimization cases
cases
For internal use

Page 59
CS call drop rate optimization cases
Case 1: AMR Call Drop Rate Increase Due to T313 tuning
Case 2: SRB parameters optimization to improve CS call drop rate
For internal use

Page 60
AMR Call Drop Rate Increase Due to T313
 tuning
T313 was changed from 3s to 5s to expect to reduce the call drop rate in one commercial network. UEs
were expected to report RL failure later to reduce the call drop rate. However, the AMR call drop rate
was increased by 0.07%.
 It seemed that it was normal fluctuation (modified on April 21 and restored on April 24).
T313 AMR call drop rate Call re-establishment success analysis
changed
0.40% 10000 6000 5255 5332 80.00%
from 3s to 5s
0.35% 0.35% 0.35% 9000
0.33% 0.31% 8000 5000 3764 75.00%
0.30% 0.29% 7000 4000
0.25% 0.27% 2478 2291 2287 70.00%
6000 3000
0.20% 5000 2000 65.00%
0.15% 4000 60.00%
3000 1000
0.10% 2000 0 55.00%
0.05% 1000
0.00% 0
RRC.AttConnReEstab.RFLoss RRC.SuccConnReEstab
VS.RAB.Loss.CS.AMR.12.2 VS.CS.AMR.Call.Drop.Cell.Rate ReEst Succ Rate
1. When RL failure were reported later, the call re-establishment procedure was affected since the re-establishment function
was enabled (T314=20s). The call re-establishment times and call success ratio of the cells of RNC62 is as upper figure.
2. The call re-establishment times ware reduced to half, which lead to increase of the call drop rate. The
success ratio of call re-establishment was decreased after the parameter T313 was modified. It was due to
the re-establishment link quality was reduced due to the delay. And the call re-establishment times was
greatly reduced.
Notes:
T313 is started after the UE detects consecutive N313 "out of sync" indications from L1. T313 is
stopped after the UE detects consecutive N315 "in sync" indications from L1.It indicates Radio Link (RL)
failure upon expiry.
For internal use
Page 61
AMR Call Drop Rate Increase Due to T313
1. We analyzed the settings of timers and call drop distribution information. The causes of new call drops were
UU no Replay and lost synchronization of uplink. The procedures before UU No Reply were soft handover
procedures.
2. The timer for soft handover was 5s (HOASUTMR=5000). The timer for lost synchronization of uplink was 5s
(TRLFAILURE=50). Both of the two timers expired, so the system did not re-establish the call when RL
failure messages were received. The call drop was incurred.
AMR Call Drop

600
0
500
400
0
300
0
200
0
100
0
0
0
VS.RAB.Loss.CS.RF.ULSync VS.RAB.Loss.CS.SRBReset VS.RAB.Loss.CS.RF.UuNoReply
a) After T313 was changed from 3s to 5s, because the timer for soft handover was 5s and the timer for lost
synchronization of uplink was 5s, the call drop was incurred when one of these timers was triggered (50% of
the probability). The call re-establishment was not performed instead.
b) At last, we restored the timer T313 from 5s to 3s.
For internal use

Page 62
CS call drop rate optimization cases
Case 1: AMR Call Drop Rate Increase Due to T313 tuning
Case 2: SRB parameters optimization to improve CS call drop rate
For internal use

Page 63
SRB parameters optimization to improve CS call
drop rate
 In one commercial network, the CS call drop is about 1.5%. Usually the
CS call drop is lower than 1%.
 And most of call drop is due to ASU expire. And in all call drop, this
reason is about 70%.
Date RNC ID CS call drop rate

2006-2-6 1 1.61%
2006-2-7 1 1.65%
2006-2-8 1 1.68%
2006-2-9 1 1.60%
2006-2-10 1 1.50%
2006-2-11 1 1.40%
2006-2-12 1 1.40%
2006-2-13 1 1.53%
2006-2-14 1 1.54%
2006-2-15 1 1.54%
2006-2-16 1 1.52%
For internal use

Page 64
drop rate
Name Description Default Optimization value
Value
T313 T313 is started after the UE detects consecutive N313 "out of sync" 3s 5s
indications from L1. T313 is stopped after the UE detects consecutive N315
"in sync" indications from L1.It indicates Radio Link (RL) failure upon expiry.
N313 Physical value range: 1, 2, 4, 10, 20, 50, 100, 200. 50 100
Maximum number of successive "out of sync" indications received from L1.
 The AMR call drop decrease from 1.50% to 1.2% after the parameters.
Before Optimization After Optimization
Date RNC ID CS call drop rate Date RNC ID CS call drop rate
2006-2-6 1 1.61% 2006-2-17 1 1.23%
2006-2-7 1 1.65% 2006-2-18 1 1.13%
2006-2-8 1 1.68% 2006-2-19 1 1.13%
2006-2-9 1 1.60% 2006-2-20 1 1.29%
2006-2-10 1 1.50% 2006-2-21 1 1.33%
2006-2-11 1 1.40% 2006-2-22 1 1.38%
2006-2-12 1 1.40% 2006-2-23 1 1.37%
2006-2-13 1 1.53% 2006-2-24 1 1.23%
2006-2-14 1 1.54% 2006-2-25 1 1.21%
2006-2-15 1 1.54% 2006-2-26 1 1.16%
2006-2-16 1 1.52% 2006-2-27 1 1.36%
2006-2-28 1 1.35%
2006-3-1 1 1.35%
2006-3-2 1 1.21%
For internal use

Page 65
drop rate Name Description Default Value Optimization value
HOASUTMR Physical unit: ms. 5000 9000
A timer to RNC wait for the response to active set update in soft handover
procedure.
RLRSTRTMR Physical unit: ms. 5000 9000
A timer to RNC wait for radio link restoration indication in the radio link
procedure.
T313 T313 is started after the UE detects consecutive N313 "out of sync" 5 7
indications from L1. T313 is stopped after the UE detects consecutive N315
"in sync" indications from L1.It indicates Radio Link (RL) failure upon expiry.
NODISCARD Maximum number of transmissions of a PDU before an AM RLC entity, 30 40
MAXDAT whose [AM RLC discard mode selection] is set to NO_DISCARD, is reset The maximum
When the mode is set to NO_DISCARD, the RLC entity will be directly reset time for SRB reset
if the number of retransmissions of a PDU reaches the value defined by this is
parameter. This parameter can be set large, if the target BLER of the NODISCARDMAXD
 transmission
The AMR call drop channel
decrease is high.
from 1.20% to 1% after the parameters. AT*TIMERPOLL=4
Before Optimization After Optimization 0*200ms=8s.
Date RNC ID CS call drop rate Date RNC ID CS call drop rate
2006-2-20 1 1.29% 2006-3-3 1 1.00%
2006-2-21 1 1.33% 2006-3-4 1 0.92%
2006-2-22 1 1.38% 2006-3-5 1 0.96%
2006-2-23 1 1.37% 2006-3-6 1 1.03%
2006-2-24 1 1.23% 2006-3-7 1 1.03%
2006-2-25 1 1.21% 2006-3-8 1 1.05%
2006-2-26 1 1.16% 2006-3-9 1 1.03%
2006-2-27 1 1.36% 2006-3-10 1 1.00%
2006-2-28 1 1.35% 2006-3-11 1 0.90%
2006-3-1 1 1.35% 2006-3-12 1 0.91%
2006-3-2 1 1.21%
For internal use

Page 66

optimization cases
cases
For internal use

Page 67
The Case of High PS Call Drop due to PSInactTimer Improper
Setting
Two RNCs’ PS call drop rate are very different. The traffic statistics of last week is as following:
 RNC1: 19.4%(462/2381), the PS CDR is very high.
 RNC2: 0.7%(414/58907), normal.
VS.PS. VS.PS.R
VS.PS.C VS.PS.Call. RNC VS.PS.Call. VS.PS.Call.Dr
RNC RABRel Time ABRelea
Time all.Drop. Drop.RNC. Id Drop.RNC op.RNC.Rate
Id ease.R
RNC Rate se.RNC
NC
1 2008-12-30 66 303 21.78% 2 2008-12-30 67 6505 1.03%
1 2008-12-31 49 277 17.69% 2 2008-12-31 69 8519 0.81%
1 2009-01-01 52 298 17.45% 2 2009-01-01 50 7813 0.64%
1 2009-01-02 76 407 18.67% 2 2009-01-02 54 8852 0.61%
1 2009-01-03 62 323 19.20% 2 2009-01-03 67 8375 0.80%
1 2009-01-04 68 312 21.79% 2 2009-01-04 61 11091 0.55%
1 2009-01-05 89 463 19.22% 2 2009-01-05 46 7931 0.58%
RNC VS.PSLoad.ULThruput.RNC VS.PSLoad.DLThruput.RNC

 The PS call drop times of the 2 RNCs are
Id (GBytes) (GBytes)
almost equivalent, but the PS service
attempted times are quite different, RNC1 1 12.76 48.63
has much less PS service times. 2 8.12 56.18
 Check the PS throughput of the two RNCs
The PS throughput of the two RNCs is very close.
is almost same.
Why the PS service attempted times has so large discrepancy?
For internal use

Page 68
High PS Call Drop due to PSInactTimer Improper
The Setting
PSInactTimer is set as following in RNC2:
SET PSINACTTIMER: PsInactTmrForInt=20,
ProtectTmrForInt=20, PsInactTmrForBac=20,
VS.PS.Call. VS.PS.Call.Drop.R
ProtectTmrForBac=20, PSInactTmrForImsSig=20, RNC Id Time(As hour)
Drop.RNC NC.Rate
ProtectTmrForImsSig=20;
1 2009-01-09 13:00 4 0.66%
But the PSInactTimer is set 0 in RNC1 :
LST PSINACTTIMER: PsInactTmrForInt=0, 1 2009-01-09 14:00 6 1.18%
ProtectTmrForInt=0, PsInactTmrForBac=0, 1 2009-01-09 15:00 9 1.44%
ProtectTmrForBac=0, PSInactTmrForImsSig=0, 1 2009-01-09 16:00 1 0.18%
ProtectTmrForImsSig=0;
1 2009-01-09 17:00 4 0.84%
1. If PsInactTimer=0, that means the PS permanent online
1 2009-01-09 18:00 7 1.13%
function is switched off. If one user establishes the PS
service successfully, he will occupy the resources all the 1 2009-01-09 19:00 4 0.61%
time, till normal release or call drop. 1 2009-01-09 20:00 2 0.35%
2. And if PsInactTimer is not equivalent to 0, that means 1 2009-01-09 21:00 4 0.87%
after a PS service established successfully, when no 1 2009-01-09 22:00 6 1.42%
data traffic after a specified period, the Access Stratum
resources will be released, only the PDP Context is
retained. Then when the data traffic requirement is After the modification, the PS call drop is normal.
appeared, the network will establish the connection When PSInactTimer is set 20s, it only affect
again. the PS service attempted times and the
3. Thus the PS service attempted times will increase and denominator increases, but the call drop
the call drop rate will decrease, also the network does not decrease in fact.
resource is saved.
4. After the modification, the PS call drop is normal.
For internal use

Page 69

optimization cases
cases
For internal use

Page 70
Access control parameters optimization cases
Case 1: The access failure due to the power congestion
Case 2: CS RAB Assignment failure due not to configure ATM route in IU interface
Case 3: PS RAB Setup Failures due not to IP Address configured in RNC
For internal use

Page 71
The access failure due to the power
congestion
 There were two UE test for PS384K
service in drive test.
 One of UEs received RRC
Connection Abnormal Release
and access failed at 21:01:12 .
 From the trace in RNC, RNC sent the
RANAP_IU_Release_Request to CN
and the cause is Request maximum
bit rat for DL not available.
For internal use

Page 72
1. congestion
Firstly we checked the code, CE and IUB resource, it is available.
2. Then we checked the power resource.
a) The maximum power of the cell is 10w(40dBm);
b) Checked the switch of DCCC, it was closed.
 SET CORRMALGOSWITCH:CHSWITCH = DCCC_SWITCH-0;
c) Checked the switch of CAC, it was algorithm 1, and the DL threshold of CAC
for PS is 75%.
 ADD CELLCAC:CELLID = 28, CELLENVTYPE = TU, NONORTHOFACTOR = 400,
DLCONVAMRTHD = 80, DLCONVNONAMRTHD = 80, DLOTHERTHD = 75, DLHOTHD
= 85, DLCCHLOADRSRVCOEFF = 0, DLINTERFACTOR = 60, DLTOTALEQUSERNUM =
50;
d) Checked the TCP for downlink in the RNC trace as following.
a) The TCPs for two UE are 38.7dBm(7.4W) and 39.95dBm(9.9W). The offset is 3dB
between TCP and the pilot power.
b) The traffic power for UE1 is 38.7-3=35.7dBm(3.7W). And the traffic power for UE2 is
39.95-3=36.95dBm(4.95W) before access failed.
For internal use
Page 73
1. congestion
Usually the power for common channel is 20% in total power in a cell. So it is 2w.
2. And the total used power was P= 3.7+4.95+2=10.65(w). And the maximum power
for the cell is 10w.
3. So it was power congestion. Usually it is due to the poor coverage and you can
find the RSCP is about -111dBm during the access failure.
RSCP is -111dBm.
Suggestions:
a) To enhance the power for this cell from 10w to 20w or more.
b) To improve the coverage by RF tuning.
c) Set RAB_DOWNSIZING_SWITCH and DCCC_SWITCH to access more users.
For internal use
Page 74
Case 2: CS RAB Assignment failure due not to configure ATM route in IU
interface
For internal use

Page 75
CS RAB Assignment failure due not to configure ATM route in IU
interface
CS RAB assignment success rate decreased in RNC121. Most of reason is due to
VS.RAB.FailEst.CS.TNL in the statistics. And this failure was not found in the before and it is
occupied 20% in all failure.
The RAB assignment failure of TNL is due to AAL2 setup failure in IU interface from CHR as following table.
CURRENT BEST INTERFACE FAULT
FAULT TYPE DETAILED FAULT REASON
TIME CELLID REASON
06:54:15(88) RAB ASSIGNMENT REQ FAULT 121:19355 AAL2 FAILURE IU LOCAL AL SETUP FAIL
For internal use

Page 76
CS RAB Assignment failure due not to configure ATM route in IU
interface
From the trace, RNC sent the RAB_ASSIGNMENT_RESP The transport layer address is
message to CN, and the failure is due to IU transport 0x45000034901706104F0000000000000000000000 in
connection failed to establish. message RAB_ASSIGNMEN_REQ from CN.
AAL2RT  Check the IU interface of AAL2RT configured in RNC, the ATM

NSAP RTX OWNERSHIP ANI
route didn’t find. So if the address is assigned by CN in RAB
assignment, it will all fail.
0x45000034901706103F0000000000000000000000 1 YES 1
0x45000034901706101F0000000000000000000000 2 NO 1
 We asked the customers, they added a new MGM, but
they did not tell us to add a new ATM route. So many
0x45000034901706102F0000000000000000000000 3 NO 1
RAB assignment failed for CS services.
0x45000034901706501F0000000000000000000000 4 NO 1
 And, the problem was solved after the address of
0x45000034901706502F0000000000000000000000 5 NO 1
0x45000034901706104F0000000000000000000000
0x45000034901706503F0000000000000000000000 6 NO 1 is added in RNC.
For internal use
Page 77
Case 2: CS RAB Assignment failure due not to configure ATM route in IU interface
For internal use

Page 78
PS RAB Setup Failures due not to IP Address configured in
RNC
•In recent 3 days, PS RAB Setup Success rate degraded
from about 99.50% to about 95% or less. As most of the PS •The main reason of the Rab CSSR
service are setup on HSDPA service, it cause HSDPA CSSR degradation is due to the TNL(Transmission
and HSUPA CSSR worse than before too. Network Layer) problem which means that the
RAB CSSR degradation is related to the
transmission system of the IUPS between
RNC and SGSN.
There are 13 IPPATHs

between Huawei RNC and
SGSN:
192.168.13.9
192.168.13.2
192.168.13.3
192.168.13.4
192.168.13.5
192.168.13.7
192.168.13.8
192.168.13.1
10.16.9.133
10.16.9.197
10.16.10.5
10.16.8.5
For internal use

Page 79
RNC
Here there is an IP Address 192.168.13.6 not configured ,but assigned by SGSN. The IP
address is not configured in RNC
For internal use

Page 80
RNC
Action taken:
1. Added IP address
192.168.13.6 at 17:10 on
Feb.4th afternoon.
2. PS RAB Setup Success was
normal after IP address being
added.
For internal use

Page 81

optimization cases
cases
For internal use

Page 82
BLER Optimization for CS
The BLER target of the AMR (uplink and downlink) <= 2% in 97% samples in one
commercial network.
And it is very difficult to get the KPI target. What is the meaning of BLER?
Transport channel parameters for AMR 12.2 kbps from 3GPP BLER means Block Error Rate and it
TS 34.108 V8.1.0 are in the following table. defines the ratio of the incorrectly
Higher layer RAB/Signalling RB RAB subflow #1 RAB subflow #2 RAB subflow #3 received transport blocks to the total
RLC Logical channel type DTCH number of received transport blocks.
RLC mode TM TM TM
Payload sizes, bit 0,39,81 103 60
Max data rate, bps 12 200
TrD PDU header, bit 0
MAC MAC header, bit 0
MAC multiplexing N/A
Layer 1 TrCH type DCH DCH DCH
TB sizes, bit 0,39,81 103 60
TFS TF0, bits 1x0 (note 2) 0x103 0x60
(note TF1, bits 1x39 1x103 1x60
1)
TF2, bits 1x81 N/A N/A
TTI, ms 20 20 20
Only 1 block is error
Coding type CC 1/3 CC 1/3 CC 1/2
CRC, bit 12 N/A N/A
Max number of bits/TTI 303 333 136
after channel coding
RM attribute 180 to 220 170 to 210 215 to 256
a) TTI (transmission timing interval) is 20ms for AMR, and the transport format is 81x1. It means 1 block is transported and each
block is 81 bits in 20ms. It is at most 50 blocks in 1s. If only 1 block is error in 1s, the BLER is 2%.
b) For the uplink, we get a BLER sample about each 640ms from the RNC. So it is transmitted about 32 blocks in 640ms. If only 1
block is error in 640ms, the BLER is 3.12%.
For internal use

Page 83
BLER and EcIo distribution in Cluster8 in
Quito
EcIo BLER
Checking the BLER error distribution in the Cluster8, you can find that the BLER error in most of cases is
due to the poor coverage in the edge of cluster. In the central cluster, it is good coverage, so no BLER is
error.
If we improve the coverage, at the same time the BLER will be improved.
For internal use

Page 84
Parameters optimization of BLER
Type Parameter Name Default value Optimized Comments
value
AMR SIRADJUSTSTEP 5(0.005dB) 3(0.003dB) Step of target SIR adjustment in outer loop power
Video phone SIRADJUSTSTEP 2(0.002dB) 1(0.001dB) control algorithm.
AMR BLERQuality 1% 0.50% It is used by CRNC to decide the target SIR value
Video phone BLERQuality 0.20% 0.10% that influences access and power control. The
formula of BLER is the 10*Lg(BLER).
AMR RlMaxDlPwr(dB) 0 1 The maximum and minimum downlink transmit
AMR RlMinDlPwr(dB) -15 -14 power of radio link.
Video phone RlMaxDlPwr(dB) 3 4 The maximum and minimum downlink transmit
Video phone RlMinDlPwr(dB) -12 -11 power of radio link.
The test result of BLER in Quito:
Type( BLER target 97% BLER(Cluster2) BLER(Cluster3) BLER(Cluster6 BLER(Cluster7 BLER(Cluster8 BLER(Cluster9
) ) ) ) )
AMR BLER (DL) <= 2% 99.44% 98.39% 99.80% 99.32% 99.29% 99.28%
AMR BLER (UL) <= 2% 94.78% 94.76% 92.05% 89.20% 90.25% 93.23%
VPBLER (DL) <= 1% 98.33% 95.08% 97.12% 97.83% 96.20% 96.76%
VP BLER (UL) <= 1% 97.56% 96.95% 97.31% 97.94% 97.52% 97.04%
A. The BLER is worse in dense urban than in suburban because it is less than pilot pollution in suburban than in dense
urban and urban.
B. When the EcIo, Pilot Pollution and coverage are improved the BLER will be improved at the
same time.
For internal use
Page 85

optimization cases
cases
For internal use

Page 86
Soft handover ratio mapping for swap
network
In one swap commercial network in Europe , the soft handover ratio is less than 15% than before.
We find that the formula to calculate the soft handover ratio is same between the two vendors.
The another vendor is SHO _ Ratio   uPALSS[1]  uPALSS[2]  2  uPALSS[3]  3  1  100
 uPALSS[1]  uPALSS[2]  uPALSS[3] 
 
The Huawei  A11  B1 2  C1 3  SHO_Ratio = 100*{[VS.SHO.AS.1 + (VS.SHO.AS.2Softer

SHR    1 100% +VS.SHO.AS.2Soft)*2+ (VS.SHO.AS.3Softer+ VS.SHO.AS.3Soft+
formula is  A1  B1  C1 
VS.SHO.AS.3Soft2Softer)*3)] /( VS.SHO.AS.1 + VS.SHO.AS.2Softer
+ VS.SHO.AS.2Soft + VS.SHO.AS.3Softer + VS.SHO.AS.3Soft
+VS.SHO.AS.3Soft2Softer )-1}
But the counter is different between the two vendors.
The counter for another vendor is based on cell level and radio link is measured in all active set, but for Huawei it
is based on RNC level and it does not measure in soft state.
So the RL is measured repeatedly for cell level, and the custom should be modify the formula for soft handover
ratio as following.   uPALSS[1]  uPALSS[2]   uPALSS[3]



SHO _ Ratio   celle RNC
 1  100
  (uPALSS[1]  uPALSS[ 2] / 2  uPALSS[3] / 3) 
 celle RNC 
•Reference Name •Associated Counters •Specification
•A1: NumberOfUEWith1RL VS.SHO.AS.1 Average Number of UEs with One RL
•B1: NumberOfUEWith2RL VS.SHO.AS.2Softer, VS.SHO.AS.2Soft Average Number of UEs with Two RLs Combined or Uncombined.
VS.SHO.AS.3Soft2Softer Average Number of UEs with Three RLs and Two Combined
•C1: NumberOfUEWith3RL
VS.SHO.AS.3Soft, VS.SHO.AS.3Softer Average Number of UEs with Three RLs Uncombined or Combined.
For internal use

Page 87
Soft handover ratio mapping for swap
network
Many factors impact the soft handover ratio, including the following items:
a) Soft handover parameter settings;
b) Network topology, site distribution, cell radius;
c) The antenna pattern;
d) Path loss;
The soft handover parameter settings and site distribution have more impact on the soft handover rati
We check the soft handover ratio in the commercial network of Huawei. It shows the
probability of one RL (radio link), two RLs and three RLs in the United Arab Emirates,
Brunei, Hong Kong, and Quito.
Commercial 1RL 2RL 3RL Soft handover Soft handover Ratio

network probability probability probability ratio(statistics) (Drive test )
United Arab 0.68 0.22 0.10 42.38% 32.24%
Emirates
Brunei 0.59 0.30 0.11 51.85% 40.81%
Hong Kong RNC1 0.56 0.30 0.14 58.09% 43.76%
Hong Kong RNC2 0.56 0.28 0.15 58.97% 43.61%
Hong Kong RNC3 0.54 0.29 0.16 62.20% 45.76%
Hong Kong RNC4 0.62 0.26 0.12 50.18% 38.17%
Quito 0.68 0.24 0.08 40.61% 32.89% (Average)
For internal use

Page 88

Huawei WCDMA Radio Parameters Optimization Cases

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Huawei WCDMA Radio Parameters Optimization Cases

Uploaded by

Copyright:

Available Formats

10/31/15

WCDMA Radio Parameters

For internal use

Configuration Signaling Drive test data Statistics data

NO Data analysis and

For internal use

1. Coverage parameters optimization cases

For internal use

For internal use

Case 1: Increase the PCPICH Power to improve the coverage

Case 2: Increase DL maximum power of AMR to improve call drop rate

Case 3: Increase FACH power to improve RRC setup success rate

Case 4: Optimize the timer T300 to improve RRC success Rate

Case 5: UE cannot access due to cell radius settings

For internal use

For internal use

Increase PCPICH Power 3dB to improve the coverage.

1. How to modify the maximum PCPICH power?

2. How to modify the minimum PCPICH power?

For internal use

Case 1: Increase the PCPICH Power to improve the coverage

Case 2: Increase DL maximum power of AMR to improve call drop

Case 3: Increase FACH power to improve RRC setup success rate

Case 4: Optimize the timer T300 to improve RRC success Rate

Case 5: UE cannot access due to cell radius settings

For internal use

For internal use

For internal use

How to modify the maximum power of AMR from 33dBm to 35dBm?

MOD CELLRLPWR:CELLID=0, CNDOMAINID=CS_DOMAIN, MAXBITRATE=12200,

Mod Power for AMR

CS12.2 CS64 PS32 PS64 PS144 PS256 PS384

For internal use

Case 1: Increase the PCPICH Power to improve the coverage

Case 2: Increase DL maximum power of AMR to improve call drop rate

Case 3: Increase FACH power to improve RRC setup success rate

Case 4: Optimize the timer T300 to improve RRC success Rate

Case 5: UE cannot access due to cell radius settings

For internal use

5. ALCAP Setup and Synchronization

6.CCCH RRC CONNECTION SETUP

7.DCCH RRC CONNECTION SETUP COMPLETE

RRC setup failure for poor coverage

For internal use

For internal use

Case 1: Increase the PCPICH Power to improve the coverage

Case 2: Increase DL maximum power of AMR to improve call drop rate

Case 3: Increase FACH power to improve RRC setup success rate

Case 4: Optimize the timer T300 to improve RRC success Rate

Case 5: UE cannot access due to cell radius settings

For internal use

Minimum Clusters After Switch - Weekly KPI （ HUAWEI ）

RRC Failure Rate 0.00

For internal use

For internal use

Case 1: Increase the PCPICH Power to improve the coverage

Case 2: Increase DL maximum power of AMR to improve call drop rate

Case 3: Increase FACH power to improve RRC setup success rate

Case 4: Optimize the timer T300 to improve RRC success Rate

Case 5: UE cannot access due to cell radius settings

For internal use

 RNC didn’t receive the RRC Setup

1. Coverage parameters optimization cases