Professional Documents
Culture Documents
(Huawei) WCDMA Radio Parameters Optimization Cases
(Huawei) WCDMA Radio Parameters Optimization Cases
YES
Parameters
optimization ends.
Coverage Parameters:
No. Parameters Name Description Default value
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 MaxPCPICHPower Max transmit power of PCPICH[0.1dBm] 346 (34.6dBm)
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.
Problem Description:
• The RSCP is not good ;
• The EcIo is bad ; Suggest a
• new site
Add a new site is very
difficult 。
20 7月 4日
20 7 5日
20 7 6日
20 7月 7日
20 7 8日
20 7 9日
20 7月 0日
20 7 1日
20 7 2日
7月 日
日
20 7 日
20 7月 日
20 7 日
20 7 日
20 年7 8日
20 7 9日
年 4
年 5
年 6
年 7
年 23
24
年 1
年 1
年 1
年 1
年 1
年 1
年 1
年 1
年 1
年 1
年 2
年 2
年 2
07 月
07 月
07 月
07 月
07 月
07 月
07 月
07 月
07 月
07 月
07 月
07 月
07 月
07 月
07 月
20 7
年
年
07
07
07
07
07
07
20
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.
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.
2日
3日
4日
5日
1日
26
27
28
29
30
31
25
8月
8月
8月
8月
8月
7月
7月
7月
7月
7月
7月
7月
年
年
年
年
年
年
07
07
07
07
07
07
07
07
07
07
07
07
20
20
20
20
20
20
20
20
20
20
20
20
CS_Drop_Times CS_Rel_Times CS_Drop_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
Power 2dB RRC SETUP
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,
1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
especially for capacity. 8-1 8-1 8-1 8-1 8-1 8-1 8-1 8-1 8-1 8-2 8-2 8-2 8-2 8-2 8-2 8-2
- - - - - - - - - - - - - - - -
00 5 005 005 00 5 005 00 5 005 005 005 005 005 005 005 005 005 005
FACH: changed from 32dBm to 34dBm, 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
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 setup
This impact is acceptant because live failures decreased from 288 to 158 and RRC setup
network is limited by coverage. success rate increased from 87% to 94%.
If increase FACH power, then it will decrease the RRC setup failure due to UU no reply.
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
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.
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.
RRC Failure Rate - SUM (%)
1.2%
1.0%
0.8%
0.6%
0.4%
0.2%
0.0%
13:00 14:00 15:00 16:00 17:00 18:00 19:00 20:00
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.
11.3km
cover
the sea.
PSC304 PSC304
Case 4: Parameters optimization for handover not in time when taking the elevator
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.
C 3G S 3G (Huawei)
Case 4: Parameters optimization for handover not in time when taking the elevator
The call
dropped place
The speed distribution
<=100km
/h
0 0k
<=2
m/h
k
3 00
<= h
m/ <=400km/h <=431km/h
The call
dropped The signaling handover between
Poor
coverage
Out of PSC180 and PSC170
coverage
Case 4: Parameters optimization for handover not in time when taking the elevator
Ping-Pong handover
The active set cell change frequently
between the same cells.
Case 4: Parameters optimization for handover not in time when taking the elevator
Cell A
(1F)
Solutions:
① CIO between cell A and cell B change to 10( 5dB);
② Reduce TrigTime1A from 320ms to 0ms;
③ IntraFreqFilterCoef change from D3 to D1.
④ RF tuning, using the indoor coverage system to cover the elevator.
Case 4: Parameters optimization for handover not in time when taking the elevator
UE TxPWR
UE transmit
power is
increased before
call drop.
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;
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
RSCP EcIo
• 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).
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.
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 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
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.
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.
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:
5-31 2:00
5-31 7:00
6-1 13:00
6-1 18:00
6-1 23:00
5-30 6:00
5-30 11:00
5-30 16:00
5-30 21:00
5-31 12:00
5-31 17:00
5-31 22:00
6-2 14:00
6-2 19:00
6-3 0:00
6-3 5:00
6-3 10:00
6-3 15:00
6-3 20:00
6-1 3:00
6-1 8:00
6-2 4:00
6-2 9:00
0 60.00%
0
0
2 0
1 0
1 0
1 00
2 0
0
3 0
5- 16 0
31 00
5- 17 0
5- 0 0
5- 1 7 0
5- 12 0
1 00
2 0
2 00
3 00
5- 11 0
1 00
3 0
3 00
0
3 0
3 0
0
31 :0
6- 3: 0
6- :0
:0
6- 3:0
6- 4:0
2 :0
6- 0 :0
3 :0
30 :0
31 :0
3 1 :0
6- 2:0
30 :0
6- 8 :
5 - 21:
5- 1:
30 6:
5- 2:
6 - 1 3:
6 - 1 8:
6- 1 4:
6 - 1 0:
6- 5:
20
19
6- 5
6- 9
2
1
30
5-
VS.SRELOC.AttPrep.IRHOCS VS.SRELOC.SuccPrep.IRHOCS
VS.SRELOC.SuccPrep.IRHOCS.Rate VS.IRATHO.AttCSOut.RNC VS.IRATHO.SuccCSOut.RNC VS.IRATHO.SuccCSOut.RNC.Rate
the LAC information should be consistent in RNC, CN and BSC, or else, one of them is insistent, the inter-RAT handover
will fail.
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
VS.IRATHO.Fai
GSMCe Time(As VS.IRATHO.AttOu VS.IRATHO.Succ OutPSUTRAN.
Cell ll day) tPSUTRAN.N OutPSUTRAN.N UEFN
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;
MOD GSMCELL: GSMCellIndex=16157, RatCellType=GSM, SuppPSHOFlag=FALSE;
MOD GSMCELL: GSMCellIndex=16159, RatCellType=GSM, SuppPSHOFlag=FALSE;
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
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.
Abnormal Routing area update and attach from 2G side caused the failure of the PS I-RAT.
Check the RAC in SGSN, and find some RAN not configured in the DNS table in SGSN.
The PS inter-RAT handover success rate improved from 86% to 93% after CN changed the DNS
configuration in SGSN
95.00%
90.00%
85.00%
80.00%
75.00%
2008-9-1
2008-9-4
2008-9-7
2008-9-10
2008-9-16
2008-9-19
2008-9-22
2008-9-25
2008-9-28
2008-10-1
2008-10-4
2008-10-7
2008-10-10
2008-10-16
2008-10-19
2008-10-25
2008-11-3
2008-11-6
2008-11-9
2008-11-18
2008-11-24
2008-11-27
2008-9-13
2008-10-13
2008-10-22
2008-10-28
2008-10-31
2008-11-12
2008-11-15
2008-11-21
2008-11-30
Date
T313 changed AMR call drop rate Call re-establishment success analysis
from 3s to 5s
0.40% 10000 6000 5255 5332 80.00%
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 8 8 8 8 8 8
2 00 2 00 2 00 2 00 2 00 2 00
, , , 3, 4, ,
8 08 08 08 08 08 20 21 22 l2 l2 25
200 0 0 0 0 0 ril ril ril ri ri ril
, ,2 ,2 ,2 ,2 ,2 Ap Ap Ap Ap Ap Ap
20 21 22 23 24 25
r il r il r il r il ril r il
Ap Ap Ap Ap Ap Ap
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.
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.
Problem description:
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%.
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%
Case 2: CS RAB Assignment failure due not to configure ATM route in IU interface
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
73 © Nokia Siemens Networks Charles / 2009-05-05
Page 73
The access failure due to the power congestion
1. 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
74 © Nokia Siemens Networks Charles / 2009-05-05
Page 74
Access control parameters optimization cases
Case 2: CS RAB Assignment failure due not to configure ATM route in IU interface
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
06:54:24(92) RAB ASSIGNMENT REQ FAULT 121:19355 AAL2 FAILURE IU LOCAL AL SETUP FAIL
06:54:30(68) RAB ASSIGNMENT REQ FAULT 121:19355 AAL2 FAILURE IU LOCAL AL SETUP FAIL
06:54:39(87) RAB ASSIGNMENT REQ FAULT 121:19355 AAL2 FAILURE IU LOCAL AL SETUP FAIL
06:56:25(50) RAB ASSIGNMENT REQ FAULT 121:19355 AAL2 FAILURE IU LOCAL AL SETUP FAIL
06:58:25(72) RAB ASSIGNMENT REQ FAULT 121:19355 AAL2 FAILURE IU LOCAL AL SETUP FAIL
06:58:37(21) RAB ASSIGNMENT REQ FAULT 121:19355 AAL2 FAILURE IU LOCAL AL SETUP FAIL
06:58:46(46) RAB ASSIGNMENT REQ FAULT 121:19355 AAL2 FAILURE IU LOCAL AL SETUP FAIL
Case 2: CS RAB Assignment failure due not to configure ATM route in IU interface
Here there is an IP Address 192.168.13.6 not configured ,but assigned by SGSN. The IP address is not
configured in 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.
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%.
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.
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%
95.08%
98.33% 97.12% 97.83% 96.20% 96.76%
VPBLER (DL) <= 1%
96.95%
97.56% 97.31% 97.94% 97.52% 97.04%
VP BLER (UL) <= 1%
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.
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 network 1RL probability 2RL 3RL probability Soft handover Soft handover Ratio
probability ratio(statistics) (Drive test )
United Arab Emirates 0.68 0.22 0.10 42.38% 32.24%