2017/6/10

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 trace Drive test data Statistics data
data collection data collection collection collection Parameters tuning

NO Data analysis and
KPI is
OK? optimization

YES

Parameters
optimization ends.

For internal use
2 © Nokia Siemens Networks Charles / 2009-05-05
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
3 © Nokia Siemens Networks Charles / 2009-05-05
Page 3

The coverage parameters being tuned frequently

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.

For internal use
4 © Nokia Siemens Networks Charles / 2009-05-05
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 5 © Nokia Siemens Networks Charles / 2009-05-05 Page 5 .

Increase the PCPICH Power to improve the coverage Problem Description: • The RSCP is not good; • The EcIo is bad; Suggest a • Add a new site is very new site difficult。 For internal use 6 © Nokia Siemens Networks Charles / 2009-05-05 Page 6 .

For internal use 7 © Nokia Siemens Networks Charles / 2009-05-05 Page 7 . MAXPCPICHPOWER=360. PCPICHPOWER=300. How to modify the minimum PCPICH power? MOD PCPICHPWR: CELLID=13011. MINPCPICHPOWER=300. MOD CELL: CELLID=13011. 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. MOD CELL: CELLID=30141. 2. PCPICHPOWER=360.

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 8 © Nokia Siemens Networks Charles / 2009-05-05 Page 8 .

CS call drop rate of Cluster 14 rose from 13th July.RF TI.00% 20 7 0日 20 7月 1日 20 7 2日 20 7 3日 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日 年 23 24 年 4 年 5 年 6 年 7 年 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 VS.40% 10000 0.42% 0.Loss. The signal in drop points is very weak.46% 0.6%.72% 0. Before swap the CS drop rate is only 0.CS.89% 0.20% 0 0.55% 0.4 to Jul.58% 0.CS a) In T network. c) This area is near Mediterranean Sea. The increasing traffic is due to tourists.40% 0.45% to more than 0.20% 40000 1.46%0. The upper figure is the CDR of Cluster 14 from Jul.53%0.60% 0. RSCP is about -110dBm and most drops happened just after connection establishment.63% 0.60% 50000 1. from 0.87% 30000 0.Drop.40% 1. b) Most call drop reason is SRB reset.RAB.36% 1. most coverage is beach and highway.79% 0. Increase DL maximum power of AMR to improve call drop rate CS Drop Rate Call drop increasing 60000 1.Rate.00% 0.93% 0. during the WCDMA network swapping from S to Huawei.Call.80% 0.64% 20000 0.60% 0.CS.Req TI. For internal use 9 © Nokia Siemens Networks Charles / 2009-05-05 Page 9 .98% 0.53% 0. 24.Drop.37% 0.48%.Rate.Call. most times RNC sent ASU to UE but did not receive the response.41% 0.49%0.

the UE can access to network but cannot keep the connection. it will not drop due to DL power. this explained why in some area in cell edge. b) Then we check the S power configuration. Increase DL maximum power of AMR to improve call 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). That explain why S call setup KPI in worse than Huawei but call drop is better than Huawei. For internal use 10 © Nokia Siemens Networks Charles / 2009-05-05 Page 10 . c) So in S network. The maximum DL DCH power of S AMR service is 36dBm. if UE can setup call. The maximum DL DCH power of S AMR service is 36dBm as following table.

55% 0.48%0.80% 90000 0. CS Drop Rate Mod Power for AMR CS12.39% 0.60% 60000 0.10% 0 0. MAXBITRATE=12200. DLSF=D128. CNDOMAINID=CS_DOMAIN.00% NL -3 +1 -4 0 +1 +2 +3 日 日 日 日 日 日 日 1日 2日 3日 4日 5日 25 26 27 28 29 30 31 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 For internal use 11 © Nokia Siemens Networks Charles / 2009-05-05 Page 11 .50% value 0. RLMINDLPWR=-130.62% Default 0 +3 -4 -2 +0 +2 +4 70000 0.67% 0. How to modify the maximum power of AMR from 33dBm to 35dBm? MOD CELLRLPWR:CELLID=0. Increase DL maximum power of AMR to improve call drop rate DL DCH maximum power of AMR service was changed from 33dBm to 35dBm in cluster 14 on 2th August. RLMAXDLPWR=2. and then the CS drop rate decreased as following figure.70% 80000 0.58% 0.43% 50000 0.40% 40000 0.2 CS64 PS32 PS64 PS144 PS256 PS384 100000 0.48% 0.20% 20000 UAE -3 +3 -4 -2 0 +2 +4 10000 0.63% 0.30% HK 0 +1 -4 0 +2 +2 +3 30000 0.43% 0.59% 0.51% 0.

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 12 © Nokia Siemens Networks Charles / 2009-05-05 Page 12 .

Allocate parameters 92% Such as RNTI. It was mainly caused during reselection and registration.CCCH RRC CONNECTION SETUP RRC RRC 7. But RNC cannot receive RRC Connection Setup Complete from UE. RADIO LINK SETUP REQUEST 5000 88% NBAP NBAP 0 86% Orignating Terminating Reselection Registration 4. L1. So the cause is DL poor coverage. Signaling for RRC Setup RRC Setup Failure Distribution UE NodeB RNC 40000 100% 35000 1. RADIO LINK SETUP RESPONSE NBAP NBAP RRC Setup Failure RRC Setup Success Rate 5.L2 15000 10000 90% 3. So UL is ok.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. there were some RRC setup failures. Increase FACH power to improve RRC setup success rate From KPI in last few months. CCCH: RRC CONNECTION REQUEST 98% RRC RRC 30000 96% 25000 94% 20000 2 . For internal use 13 © Nokia Siemens Networks Charles / 2009-05-05 Page 13 . ALCAP Setup and Synchronization 6.

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. 0 80% especially for capacity. Increase FACH power to improve RRC setup success rate 1. For internal use 14 © Nokia Siemens Networks Charles / 2009-05-05 Page 14 . Optimize “MAXFACHPOWER”. In live network.25*(10^ ((34-43)/10)-10^ ((32- 43)/10)) =1. success rate increased from 87% to 94%. then it’ll influence RRC SETUP FAILURES RRC SETUP SUCCESS RATE DCH: 0. We 50 82% calculate the influence for live network.25. 05 11 05 12 05 13 05 14 05 15 05 16 05 17 05 18 05 19 05 20 05 21 05 22 05 23 05 24 05 25 6 -2 20 -8- 20 -8- 20 -8- 20 -8- 20 -8- 20 -8- 20 -8- 20 -8- 20 -8- 20 -8- 20 -8- 20 -8- 20 -8- 20 -8- 20 -8- -8 05  20 FACH: changed from 32dBm to 34dBm. It means the FACH power is 34dBm. RRC Setup statistics The value is maximum transmit power of FACH. and active factor is 0. and supposing all the other 150 86% 100 84% common channels the same as before. 350 96% 300 94% 250 92% 2. If increase FACH power. We suggest Increasing FACH RRC SETUP Power 2dB changing it to 1 dB.16% From the figure above. then it will decrease the RRC setup failure due to UU no reply. NodeB maximum transmit 200 90% 88% power is 43dBm. and it’s -1dB in live network.

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 15 © Nokia Siemens Networks Charles / 2009-05-05 Page 15 .

75% 0.SUM (%) "=< 10%" 0.SUM in the trend 4561743 5478662 6165218 5232258 8830561 5000059 6445880 478572 42221482 RRC Connection Requests .08% 1. 0.85% 1.IRAT in the trend 1386870 1317011 1127359 1013396 1004143 890266 1425679 0 8146314 Cell Reselection RRC Failure Rate .79% before the swap. Optimize the timer T300 to improve RRC success Rate RRC Failure Rate was 0.SUM in the trend 6255259 6380468 5064183 5298305 7093489 4868310 5521603 0 40370612 RRC Connection Requests .RAB in the trend 1867148 2311263 1574192 2193172 2590867 2084147 1937424 55085 14630080 RRC Connection Requests .32% after swap.32% SUM (%) % For internal use 16 © Nokia Siemens Networks Charles / 2009-05-05 Page 16 .63% 1.79% Minimum Clusters After Switch . but it increased to 1.IRAT in the trend 1496278 1256319 950827 883108 1001577 891959 1169277 337931 Cell Reselection 7992077 RRC Failure Rate .78% 0.59% 1. Minimum Clusters Before Switch Name Requirement C1 C2 C3 C4 C5 C6 C7 C8 Whole City RRC Connection Requests .75% 0.Weekly KPI (HUAWEI) Name Requirement C1 C2 C3 C4 C5 C6 C7 C8 City Level RRC Connection Requests . The KPI is worse than before.07% 1.00 "=< 10%" 1.01% 0.36% 1.25% 1.70% 0.90% 0.95% 0.09% 1.RAB in the trend 2048127 2398928 1653128 2357844 2749713 2208816 2354256 0 15707398 RRC Connection Requests .

Modified the N300 from 3 to 4. And most of reason is RRC no reply for register and inter-Rat cell reselect. We increased the FACH power offset from 1dB to 1. 2. But the KPI acceptance is requested for 99. Optimize the timer T300 to improve RRC success Rate  Usually the RRC setup success rate for other services is about 97%~99% in Huawei commercial network. and RRC no reply for inter-Rat cell reselect is 26%. and RRC setup failure rate improved a little. 1.2% in this network. the RRC setup failure rate decreased 0.  RRC setup failure mainly is due to RNC doesn’t receive the RRC_CONNECTION_SETUP_CMP from UE through statistics. 3.13%. RRC no reply for register is about 48%.5dB. For internal use 17 © Nokia Siemens Networks Charles / 2009-05-05 Page 17 .

SUM (%) 1. For internal use 18 © Nokia Siemens Networks Charles / 2009-05-05 Page 18 .2% 1. Optimize the timer T300 to improve RRC success Rate 1. Modified the T300 from 2s to 0.SUM (%) 1.4% 0. 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.73% in the acceptance test.0% 13:00 14:00 15:00 16:00 17:00 18:00 19:00 20:00 RRC Failure Rate .0% 0. This access is measured another access and the denominator is increased in the KPI formula. RRC Failure Rate . 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.3%. 2. b) If the UE fails to access due to poor coverage.2% 0.8% 0. else enter idle mode. RRC CONNECTION REQUEST will be resent upon the expiry of the timer if V300 is lower than or equal to N300.9% to 99. RRC_CONN_SETUP message will repeat to send after T300 expires. 2.6% 0. it will reselect to another cell and access again. It is stopped when UE receives the RRC CONNECTION SETUP message. Huawei RNC does not support this function. And the RRC setup success rate improved from 98. RRC setup failure rate is about 0. Recommended value: D2000. Notes:T300 is started when UE sends the RRC CONNECTION REQUEST message.4s on 20th March.

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 19 © Nokia Siemens Networks Charles / 2009-05-05 Page 19 .

PSC304 PSC304  RNC didn’t receive the RRC Setup Request signaling because the cell radius is set 10KM and UE accessed far from 11. RADIUS=30000 For internal use 20 © Nokia Siemens Networks Charles / 2009-05-05 Page 20 .EcIo is -2dB Why does access fail? 11. UE cannot access due to cell radius settings RSCP is -72dBm.3km.  The command modified the cell radius is as following: MOD LOCELL: LOCELL=12111.3km cover the sea.

Intra frequency handover parameters optimization cases 3. Radio Parameters Optimization Cases 1. Access control parameters optimization cases 7. PS call drop rate optimization cases 6. Soft handover ratio optimization cases For internal use 21 © Nokia Siemens Networks Charles / 2009-05-05 Page 21 . CS call drop rate optimization cases 5. BLER parameters optimization cases 8. Inter-RAT handover parameters optimization cases 4. Coverage parameters optimization cases 2.

1C. Mi : measurement result of a cell not forbidden to affect reporting range in the active set. R1a : the reporting range constant. namely 6dB (step 0. not taking into account any cell individual offset. MBest : the measurement result of the cell not forbidden to affect reporting range in the active set with the highest measurement result.1D TrigTime1C. NA : the number of cells not forbidden to affect reporting range in the current active set. Hystfor1B. CIONew : the individual cell offset for the cell entering the reporting range. H1a : the hysteresis parameter for the event 1a.TrigTime1B. H1b . Soft handover time-to-trigger parameters. CIOOFFSET Neighboring cell oriented Cell Individual Offset (CIO) 0 TrigTime1A. namely 3dB (step 0.namely 3 measurement  1A (Add a cell in Active Set)  NA  10  LogM New  CIONew  W 10  Log   M i   (1  W ) 10  LogM Best  ( R1a  H1a / 2)  i 1  MNew : the measurement result of the cell entering the reporting range. For internal use 22 © Nokia Siemens Networks Charles / 2009-05-05 Page 22 . 640ms for 1B.namely 4dB(step 0. W: a parameter sent from UTRAN to UE. 320ms for 1A.5) Hystfor1A. The soft handover parameters being tuned frequently Parameter Name Description Default Setting IntraRelThdFor1A Relative thresholds of soft handover for Event 1A (R1a) 6 . Hystfor1D 8. Hystfor1C.H1d.TrigTime1D FilterCoef Filter coefficient of L3 intra-frequency D3 .5) for H1c. Soft handover hysteresis (H1x) 0dB for H1a.5) IntraRelThdFor1B Relative thresholds of soft handover for Event 1B (R1b) 12 .

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 23 © Nokia Siemens Networks Charles / 2009-05-05 Page 23 .

For internal use 24 © Nokia Siemens Networks Charles / 2009-05-05 Page 24 . which leads to the call drop. and the UE fails to receive the ASU command. the target cell signals quickly increase in a short time. At the corner. the service cell signals quickly decrease. Parameters optimization for corner effect case Problem Description: Call dropped Call drops often occur at the corner.

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

The coverage comparing of different operator at the corner H 3G SMT 3G C 3G S 3G (Huawei) For internal use 26 © Nokia Siemens Networks Charles / 2009-05-05 Page 26 .

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 27 © Nokia Siemens Networks Charles / 2009-05-05 Page 27 .

2km due to the handover 5.  Sometimes call drop 4. The call dropped place The speed distribution <=100km /h <=400km/h <=431km/h For internal use 28 © Nokia Siemens Networks Charles / 2009-05-05 Page 28 . Parameters optimization for handover area being small The sites distribution for Maglev train  The maglev train test 2.9km network.0km  The maximum speed is 431km/h. 1.7km area is small.

Parameters optimization for handover area being small The RSCP in the maglev train The call dropped The signaling handover between Poor Out of coverage PSC180 and PSC170 coverage For internal use 29 © Nokia Siemens Networks Charles / 2009-05-05 Page 29 .

downtilt is 2 degrees.6dBi. gain is 20. ② Reduce TrigTime1A from 320ms to 100ms. ④ IntraRelThdFor1BCS change from 6dB to 8dB. ⑤ IntraFreqFilterCoef change from D3 to D2. Cell1 Cell2 ③ IntraRelThdFor1ACS change from 3dB to 5. 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). the handover area is 98m according to simulation  The speed and handover: Generally the handover delay is about 200~600ms. According to simulation the handover is only 28m; ② Increase the CIO between Cell1 and Cell2 5dB.  i 1  For internal use 30 © Nokia Siemens Networks Charles / 2009-05-05 Page 30 . UE measurement the neighbor cell need some time. suppose the handover 800ms. A b) At last we use the splitting the sector. N  10  LogM New  CIONew  W  10  Log   M i   (1  W )  10  LogM Best  ( R1a  H1a / 2).  Result after the parameters tuning CIO a) The call dropped times reduce. but we still find call dropped in this area. Parameters optimization for handover area being small  Simulation of handover area: ① Andrew-UMWD-03319-0DM.5dB.

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 31 © Nokia Siemens Networks Charles / 2009-05-05 Page 31 .

For internal use 32 © Nokia Siemens Networks Charles / 2009-05-05 Page 32 . Before call dropped the signal of SC56 is below -18dB. but the two cells became so worse in a short time. 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. so the SC56 was deleted from active set. Ping-Pong handover optimization case  Ping-Pong handover The active set cell change frequently between the same cells. So the call dropped. the active set is left SC64 and SC66.

Ping-Pong handover optimization case The cell SC 56 was deleted from active set. c) IntraFreqFilterCoef change from D3 to D4. 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. ② RF tuning For internal use 33 © Nokia Siemens Networks Charles / 2009-05-05 Page 33 . b) IntraRelThdFor1BCS change from 6dB to 8dB. The UE reported the 1A event of cell SC 56. ① Parameters tuning a) Increase the TrigTime1B from 640ms to 1280ms or 2560ms.

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 34 © Nokia Siemens Networks Charles / 2009-05-05 Page 34 .

Indoor Cell A (13F) Cell A (1F) For internal use 35 © Nokia Siemens Networks Charles / 2009-05-05 Page 35 . B and no coverage for the elevator. 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. So 电 the elevator is covered by outdoor 梯 cell B. ② It often call drop when enter or out elevator in the 1th floor.

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

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 handover radius

For internal use
37 © Nokia Siemens Networks Charles / 2009-05-05
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
38 © Nokia Siemens Networks Charles / 2009-05-05
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
39 © Nokia Siemens Networks Charles / 2009-05-05
Page 39

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
40 © Nokia Siemens Networks Charles / 2009-05-05
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 41 © Nokia Siemens Networks Charles / 2009-05-05 Page 41 .

RSCP EcIo For internal use 42 © Nokia Siemens Networks Charles / 2009-05-05 Page 42 . The parameters optimization for pingpong Inter-RAT cell reselection in idle state Problem description: UE change to camp in 3G or 2G so frequently in idle state in one building.

7= -12dB. 6= -14dB. 1= -6dB. … . 8 = 0dB , 9 = 4 dB. Solutions: Increase the FDD_Qmin from -20dB to -10dB. 4= -16dB. ③Cell reselection 3G RX level threshold: FDD_Qmin = 0 (-20dB)  FDD_Qmin:0= -20dB. 5= -10dB. 15 = 28 dB.1 = -28 dB. • When the EcIo of 3G changes between -14dB to -20dB. UE will reselect to 3G in spite of the 2G coverage. And if the EcIo of 3G is higher than -20dB. 3= -8dB. UE will reselect between 3G and 2G frequently. • UE will always measure the 3G signal in 2G network. For internal use 43 © Nokia Siemens Networks Charles / 2009-05-05 Page 43 . 2= -18dB. UE will start to measure the GSM signal and maybe reselect to 2G. Usually we suggest the value is 7 (-12dB). (always select a cell if acceptable). • When the EcIo of 3G is lower than -14dB. The parameters optimization for pingpong Inter-RAT cell reselection in idle state 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 = . 2 = -24 dB.

is not sent for serving cell. IdleSintersearch Threshold for inter-frequency cell reselection in idle mode. IdleSintrasearch Threshold for intra-frequency cell reselection in idle mode. Ssearch. UE need not perform inter-frequency measurements. Recommended value: 2. perform intra-frequency measurements. perform intra-frequency measurements. 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 intra-frequency cell reselection procedure will be started. UE need not perform intra-frequency measurements.Qqualmin Qqualmin Minimum required quality level corresponding to the CPICH Ec/No. Recommended value: -18(dB). For internal use 44 © Nokia Siemens Networks Charles / 2009-05-05 Page 44 . 3. If Sintrasearch. It's mandatory When the value of parameter SsearchratInd is TRUE. If Sx <= Sintrasearch. If Sx <= Sintersearch. If Sintersearch.RAT Threshold for inter-RAT cell reselection. perform measurements on cells of RAT. If Sx > SsearchRAT. If Sx > Sintersearch. When the quality (CPICH Ec/No measured by UE) of the serving cell is lower than this threshold plus the [Qqualmin] of the cell. 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. perform inter-frequency measurements. If Sx > Sintrasearch. the inter-RAT cell reselection procedure will be started. UE need not perform measurements on cells of RAT. is not sent for serving cell. Qrxlevmin Minimum required RX level corresponding to the CPICH RSCP. perform inter-frequency measurements. If Sx <= SsearchRAT. If SsearchRAT. the inter-frequency cell reselection procedure will be started. UE can camp on the cell only when the CPICH Ec/No measured is larger than the value of this parameter. The parameters optimization for pingpong Inter-RAT cell reselection in idle state 1. UE can camp on the cell only when the measured CPICH RSCP is larger than the value of this parameter. Sx=Squalmeas . perform measurements on cells of RAT. step is 2dB. Recommended value: -58. 2. is not sent for serving cell.

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 45 © Nokia Siemens Networks Charles / 2009-05-05 Page 45 .

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

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 47 © Nokia Siemens Networks Charles / 2009-05-05 Page 47 .

and continued. the CS Inter-RAT Handover Preparation Success Ratio of RNC 321 decreased greatly. which is shown below: According to the 3GPP 25. the failure always happen after the RNC send message RELOCATION_REQUIRED to CN. The detail information of the RELOCATION_PREPARATION_FAILURE is as following. Do the IOS trace. The case for CS Inter-RAT Preparation handover failure From May 25th. the Handover Execution Success Ratio also dropped. the information contained within the message is not valid." so.413. and the CN return the RELOCATION_PREPARATION_FAILURE. This is a Protocol Cause that means that " The received message included a semantic error. For internal use 48 © Nokia Siemens Networks Charles / 2009-05-05 Page 48 . and the failure reason is Semantic error.

00% 1000 65.00% 1 0 1 00 2 0 0 6.0 0 5 . after modified the LAC information.IRHOCS VS.1 7 0 5 .12 0 1 00 1 00 2 0 2 00 3 0 3 00 3 00 0 3 0 0 3 0 31 :0 6 . information.00% 6-1 3:00 6-1 8:00 6-2 4:00 6-2 9:00 6-3 0:00 6-3 5:00 5-30 1:00 5-30 6:00 5-31 2:00 5-31 7:00 6-1 13:00 6-1 18:00 6-1 23:00 6-2 14:00 6-2 19:00 6-3 10:00 6-3 15:00 6-3 20: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 0 60.3 :0 6 .00% 4000 3000 80.SuccPrep.00% 0 0.00% 2000 70.1: 3 0 6: 5 .SRELOC.8: 5 .IRHOCS.1 0: 0 5 .11 0 5. check the 2G LAC success rate is also increase much.17 0 2 0 1 0 5. the CS inter RAT preparation handover success rate is normal.00% 60. The case for CS Inter-RAT Preparation handover failure From the message analysis.00% 80.2: 6 . For internal use 49 © Nokia Siemens Networks Charles / 2009-05-05 Page 49 .16 0 0 31 00 5 .AttCSOut.2 :0 6.1 8: 6 .RNC VS.AttPrep.RNC.1 4: 6 . one of them is insistent.:0 :0 6 .00% 100.00% 1000 20.RNC VS. really many inconsistent LAC information.SuccCSOut.IRATHO.SRELOC.00% 40. CN and BSC.SRELOC. or else.00% 3000 2000 75. if the parameter is wrong At the same time the CS inter RAT handover configured. which is shown below: 7000 120.00% 5000 4000 85. the LAC maybe wrong.00% 5000 90.IRATHO.00% 7000 100.9 2 30 3 5- VS.21 : 5 .SuccCSOut.SuccPrep.00% 6000 6000 95.5 0 6 .Rate VS.1 5: 19 20 6.IRATHO.1 3: 6 .3: 0 6.0 :0 3 :0 3 0 :0 3 0 :0 3 1 :0 3 1 :0 6 .Rate the LAC information should be consistent in RNC. the inter-RAT handover will fail.4 :0 2 :0 6 .IRHOCS VS.

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 50 © Nokia Siemens Networks Charles / 2009-05-05 Page 50 .

FailOutPS Cell Id Date UTRAN.Succ OutPSUTRAN. 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.Cell TRAN RAN.Fai GSMCe Time(As VS.CfgUnsupp RAN.IRATHO.PhyChFail UTRAN.FailOutPSUT IRATHO.IRATHO.FailOutPSUT VS.IRATHO.N OutPSUTRAN. VS.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 51 © Nokia Siemens Networks Charles / 2009-05-05 Page 51 . Cell ll day) utPSUTRAN.AttO VS.FailOutPS VS.IRATHO.IRATHO.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. The following table shows TOP 10 cells for PS I-RAT handover failure and the reason for one whole day.AttOutPSU IRATHO.

For internal use 52 © Nokia Siemens Networks Charles / 2009-05-05 Page 52 . InterRAT PS handover Failed due to 2G Cell Barred PS IRAT failure is due to the GSM cell 16156 was barred.

It had better not delete the CS neighobor cell. RatCellType=GSM. SuppPSHOFlag=FALSE. RatCellType=GSM. we should modify the GSM cells type RatCellType from GPRS to GSM. otherwise it affects the CS handover. 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. For internal use 53 © Nokia Siemens Networks Charles / 2009-05-05 Page 53 . it means these cells not configuration for PS handover to GSM. SuppPSHOFlag=FALSE. MOD GSMCELL: GSMCellIndex=16157. Because the cell was barred only for GPRS. MOD GSMCELL: GSMCellIndex=16159. RatCellType=GSM. The command modified the GSM type is as following: MOD GSMCELL: GSMCellIndex=16156. SuppPSHOFlag=FALSE.

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 54 © Nokia Siemens Networks Charles / 2009-05-05 Page 54 .

33% 209 40 RNC:3 2008-10-19 3228 81. you can find that after RNC decides to handover from 3G to 2G and send Cell_Change_Order_From_UTRAN to UE. RNCName Time(As day) PS.97% 278 218 RNC:3 2008-10-21 3550 82.IRATHO.RNC Physical Channel Fail PS. 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.66% 268 175 RNC:3 2008-10-20 3649 81.Success rate.35% 249 97 RNC:1 2008-10-21 2741 86. it is lower than acceptance target 90%.IRATHO.IRATHO.72% 214 85 RNC:1 2008-10-22 2438 87. others procedures are not related to RNC anymore. the PS inter-RAT handover success rate is only 85%.RNC PS.54% 278 189 From the signaling. And RNC just waits for the IU_Release_Command from SGSN.61% 272 105 RNC:1 2008-10-20 3210 87. For internal use 55 © Nokia Siemens Networks Charles / 2009-05-05 Page 55 . Fail No reply RNC:1 2008-10-19 3037 85.Attempts.

Inter-RAT PS handover Failed due to DNS settings in SGSN Abnormal Routing area update and attach from 2G side caused the failure of the PS I-RAT. For internal use 56 © Nokia Siemens Networks Charles / 2009-05-05 Page 56 .

57% 21.55% 51.53% 16. From the test.53% 76. 5536 198 92.60% 78.00% RAU Reject due to implicitly detached.43% 35. 1838 116 73.43% RAU Reject due to implicitly detached. 6036 111 79. VS.08% 30.42% 23.57% 71.77% 69. 1738 115 86.00% 50. 2.Cell.50% 37. 1238 203 86. This is the SGSN problem.23% RAU Reject due to implicitly detached. In this case RNC will count the handover as a success one.47% RAU Reject due to implicitly detached.75% RAU Reject due to implicitly detached.14% 64. 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.94% 31.25% 68. 1438 112 81. and find some RAN not configured in the DNS table in SGSN.02% 62. 1138 202 88.74% 39. Check the RAC in SGSN.67% 48.33% RAU Reject due to implicitly detached. 1338 204 89.IRATHO. RNC will count the PS IRAT fail due to no reply from SGSN.69% 60.02% 83. 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. So if RNC does not received this message from SGSN before the timer expire.31% RAU Reject due to implicitly detached.SuccO Physical channel Other reasons (mainly LAC RAC utPSUNTRAN.50% RAU Accept. Inter-RAT PS handover Failed due to DNS settings in SGSN 1. The direct cause of the PS Inter-RAT failure is no reply from SGSN before the timer expire. When UE handover to 2G the routing area update request is rejected by CN. For internal use 57 © Nokia Siemens Networks Charles / 2009-05-05 Page 57 .47% RAU Accept. but the release reason is normal release.86% RAU Reject due to implicitly detached.43% RAU Reject due to implicitly detached. 3. 1038 201 84.19% 50.33% 17. 5836 109 82.50% 82.38% 28. 1538 113 89. we found many cases that SGSN sends the “IU release Message” to RNC when the routing area update rejected.50% RAU Reject due to implicitly detached.

00% Change the DNS configuration in SGSN PS IRAT HO SR 95.00% 80.00% 75.00% 85.All data Services For internal use 58 © Nokia Siemens Networks Charles / 2009-05-05 Page 58 .00% 90. Inter-RAT PS handover Failed due to DNS settings in SGSN The PS inter-RAT handover success rate improved from 86% to 93% after CN changed the DNS configuration in SGSN PS IRAT 3G to 2G Handover Success Rate 100.00% 2008-9-1 2008-9-4 2008-9-7 2008-9-10 2008-9-13 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-11-3 2008-11-6 2008-11-9 2008-10-10 2008-10-13 2008-10-16 2008-10-19 2008-10-22 2008-10-25 2008-10-28 2008-10-31 2008-11-12 2008-11-15 2008-11-18 2008-11-21 2008-11-24 2008-11-27 2008-11-30 Date 3G & 3G+ to 2G Handover Success Rate .

Coverage parameters optimization cases 2. Radio Parameters Optimization Cases 1. Soft handover ratio optimization cases For internal use 59 © Nokia Siemens Networks Charles / 2009-05-05 Page 59 . Access control parameters optimization cases 7. CS call drop rate optimization cases 5. PS call drop rate optimization cases 6. Intra frequency handover parameters optimization cases 3. BLER parameters optimization cases 8. Inter-RAT handover parameters optimization cases 4.

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 60 © Nokia Siemens Networks Charles / 2009-05-05 Page 60 .

00% 0.CS.Drop. the AMR call drop rate was increased by 0.SuccConnReEstab VS. The call re-establishment times and call success ratio of the cells of RNC62 is as upper figure.20% 5000 2000 65.Loss.07%.2 . AMR Call Drop Rate Increase Due to T313 tuning Problem description:  T313 was changed from 3s to 5s to expect to reduce the call drop rate in one commercial network.It indicates Radio Link (RL) failure upon expiry.30% 0.27% 2478 70.00% 3000 1000 0.2 . UEs were expected to report RL failure later to reduce the call drop rate.Cell.AMR.35% 9000 0.00% 0.25% 0.Call.CS.35% 0.AttConnReEstab.2 Ap Ap Ap Ap Ap Ap 20 21 22 23 24 25 ril ril ril ril ril ril Ap Ap Ap Ap Ap Ap RRC.  It seemed that it was normal fluctuation (modified on April 21 and restored on April 24).35% 0.RFLoss RRC.40% 10000 6000 5255 5332 80.2 .05% 1000 8 8 8 8 8 8 0.00% 0. T313 changed AMR call drop rate Call re-establishment success analysis from 3s to 5s 0.RAB.AMR. The success ratio of call re-establishment was decreased after the parameter T313 was modified. The call re-establishment times ware reduced to half.2 VS.2 .2 . When RL failure were reported later. It was due to the re-establishment link quality was reduced due to the delay.2 08 08 08 08 08 08 20 21 22 23 24 25 0 0 0 0 0 0 ril ril ril ril ril ril .12.31% 8000 5000 3764 75.2 .29% 7000 4000 0. which lead to increase of the call drop rate. For internal use 61 © Nokia Siemens Networks Charles / 2009-05-05 Page 61 .15% 4000 60. T313 is stopped after the UE detects consecutive N315 "in sync" indications from L1. However.10% 2000 0 55. And the call re-establishment times was greatly reduced.Rate ReEst Succ Rate 1.33% 0.2 .00% 0 00 00 00 00 00 00 .2 .00% 6000 3000 2291 2287 0. 2.2 . Notes: T313 is started after the UE detects consecutive N313 "out of sync" indications from L1.2 . the call re-establishment procedure was affected since the re-establishment function was enabled (T314=20s).00% 0.

.RAB. . .RF. the call drop was incurred when one of these timers was triggered (50% of the probability). For internal use 62 © Nokia Siemens Networks Charles / 2009-05-05 Page 62 .Loss.Loss. so the system did not re-establish the call when RL failure messages were received. We analyzed the settings of timers and call drop distribution information. we restored the timer T313 from 5s to 3s.CS. AMR Call Drop 600 0 500 400 0 300 0 200 0 100 0 0 0 08 08 08 08 08 08 20 20 20 20 20 20 . The timer for lost synchronization of uplink was 5s (TRLFAILURE=50). 2. AMR Call Drop Rate Increase Due to T313 1. The causes of new call drops were UU no Replay and lost synchronization of uplink. The call re-establishment was not performed instead.RAB.ULSync VS.RF.CS.CS. Both of the two timers expired. The timer for soft handover was 5s (HOASUTMR=5000).SRBReset VS. The procedures before UU No Reply were soft handover procedures. . .RAB. 20 21 22 23 24 25 ril ril ril ril ril ril Ap Ap Ap Ap Ap Ap VS. The call drop was incurred. b) At last. because the timer for soft handover was 5s and the timer for lost synchronization of uplink was 5s.UuNoReply a) After T313 was changed from 3s to 5s.Loss.

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 63 © Nokia Siemens Networks Charles / 2009-05-05 Page 63 .

40% 2006-2-12 1 1.52% For internal use 64 © Nokia Siemens Networks Charles / 2009-05-05 Page 64 .54% 2006-2-16 1 1. Date RNC ID CS call drop rate 2006-2-6 1 1. Usually the CS call drop is lower than 1%.65% 2006-2-8 1 1.50% 2006-2-11 1 1.54% 2006-2-15 1 1. this reason is about 70%. And in all call drop.68% 2006-2-9 1 1.60% 2006-2-10 1 1.61% 2006-2-7 1 1.  And most of call drop is due to ASU expire. the CS call drop is about 1.40% 2006-2-13 1 1.5%. SRB parameters optimization to improve CS call drop rate Problem description:  In one commercial network.53% 2006-2-14 1 1.

52% 2006-2-27 1 1.33% 2006-2-11 1 1.38% 2006-2-12 1 1. 3s 5s T313 is stopped after the UE detects consecutive N315 "in sync" indications from L1.60% 2006-2-20 1 1.16% 2006-2-16 1 1.It indicates Radio Link (RL) failure upon expiry. 50. 100.35% 2006-3-1 1 1. N313 Physical value range: 1.35% 2006-3-2 1 1.23% 2006-2-14 1 1.54% 2006-2-26 1 1. 200.50% 2006-2-21 1 1.50% to 1.53% 2006-2-24 1 1.40% 2006-2-23 1 1.40% 2006-2-22 1 1.68% 2006-2-19 1 1.54% 2006-2-25 1 1. Before Optimization After Optimization Date RNC ID CS call drop rate Date RNC ID CS call drop rate 2006-2-6 1 1.2% after the parameters.  The AMR call drop decrease from 1. SRB parameters optimization to improve CS call drop rate Name Description Default Optimization value Value T313 T313 is started after the UE detects consecutive N313 "out of sync" indications from L1.37% 2006-2-13 1 1. 20.61% 2006-2-17 1 1.21% 2006-2-15 1 1. 10.13% 2006-2-9 1 1. 4. 50 100 Maximum number of successive "out of sync" indications received from L1.21% For internal use 65 © Nokia Siemens Networks Charles / 2009-05-05 Page 65 .29% 2006-2-10 1 1.65% 2006-2-18 1 1.13% 2006-2-8 1 1. 2.23% 2006-2-7 1 1.36% 2006-2-28 1 1.

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

Coverage parameters optimization cases 2. CS call drop rate optimization cases 5. Intra frequency handover parameters optimization cases 3. Soft handover ratio optimization cases For internal use 67 © Nokia Siemens Networks Charles / 2009-05-05 Page 67 . Inter-RAT handover parameters optimization cases 4. PS call drop rate optimization cases 6. Radio Parameters Optimization Cases 1. Access control parameters optimization cases 7. BLER parameters optimization cases 8.

C VS.  RNC2: 0.55% 1 2009-01-05 89 463 19. The Case of High PS Call Drop due to PSInactTimer Improper Setting Two RNCs’ PS call drop rate are very different. is almost same.80% 1 2009-01-04 68 312 21.Call. VS.PS. normal.76 48. RNC1 1 12.12 56.Call.PS.PS. RNC VS.Call.PS. Why the PS service attempted times has so large discrepancy? For internal use 68 © Nokia Siemens Networks Charles / 2009-05-05 Page 68 .4%(462/2381).58% RNC VS. 2 8.78% 2 2008-12-30 67 6505 1.63 has much less PS service times.79% 2 2009-01-04 61 11091 0.PS.R VS. but the PS service attempted times are quite different.Rate Id ease. the PS CDR is very high.61% 1 2009-01-03 62 323 19.64% 1 2009-01-02 76 407 18.PSLoad.RNC  The PS call drop times of the 2 RNCs are Id (GBytes) (GBytes) almost equivalent. Id Time Drop.DLThruput. Drop.69% 2 2008-12-31 69 8519 0.18  Check the PS throughput of the two RNCs The PS throughput of the two RNCs is very close.45% 2 2009-01-01 50 7813 0.20% 2 2009-01-03 67 8375 0.7%(414/58907).RNC.R RNC Rate se.Dr RNC RABRel Time all.ULThruput.PS.81% 1 2009-01-01 52 298 17.RNC.RNC ABRelea op.67% 2 2009-01-02 54 8852 0.PSLoad. The traffic statistics of last week is as following:  RNC1: 19.03% 1 2008-12-31 49 277 17.Drop.22% 2 2009-01-05 46 7931 0.RNC NC 1 2008-12-30 66 303 21. VS. VS.RNC VS.

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

Radio Parameters Optimization Cases 1. PS call drop rate optimization cases 6. BLER parameters optimization cases 8. CS call drop rate optimization cases 5. Coverage parameters optimization cases 2. Intra frequency handover parameters optimization cases 3. Access control parameters optimization cases 7. Soft handover ratio optimization cases For internal use 70 © Nokia Siemens Networks Charles / 2009-05-05 Page 70 . Inter-RAT handover parameters optimization cases 4.

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 71 © Nokia Siemens Networks Charles / 2009-05-05 Page 71 .

 One of UEs received RRC Connection Abnormal Release and access failed at 21:01:12 . The access failure due to the power congestion Problem description:  There were two UE test for PS384K service in drive test. For internal use 72 © Nokia Siemens Networks Charles / 2009-05-05 Page 72 .  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.

7dBm(7. Then we checked the power resource. 2. DLHOTHD = 85.7-3=35. CE and IUB resource. DLCONVNONAMRTHD = 80.95dBm(4. NONORTHOFACTOR = 400. DLINTERFACTOR = 60.7W). DLTOTALEQUSERNUM = 50. and the DL threshold of CAC for PS is 75%. For internal use 73 © Nokia Siemens Networks Charles / 2009-05-05 Page 73 . a) The maximum power of the cell is 10w(40dBm). DLCONVAMRTHD = 80. DLCCHLOADRSRVCOEFF = 0.95W) before access failed.95dBm(9.  SET CORRMALGOSWITCH:CHSWITCH = DCCC_SWITCH-0.9W).7dBm(3. it was algorithm 1. c) Checked the switch of CAC. Firstly we checked the code. The access failure due to the power congestion 1. CELLENVTYPE = TU. DLOTHERTHD = 75. a) The TCPs for two UE are 38.4W) and 39.95- 3=36. d) Checked the TCP for downlink in the RNC trace as following. b) The traffic power for UE1 is 38. And the traffic power for UE2 is 39.  ADD CELLCAC:CELLID = 28. it was closed. The offset is 3dB between TCP and the pilot power. b) Checked the switch of DCCC. it is available.

Usually the power for common channel is 20% in total power in a cell. Suggestions: a) To enhance the power for this cell from 10w to 20w or more. For internal use 74 © Nokia Siemens Networks Charles / 2009-05-05 Page 74 . c) Set RAB_DOWNSIZING_SWITCH and DCCC_SWITCH to access more users. So it is 2w. The access failure due to the power congestion 1.7+4. RSCP is -111dBm.65(w). So it was power congestion. 2. b) To improve the coverage by RF tuning.95+2=10. And the maximum power for the cell is 10w. Usually it is due to the poor coverage and you can find the RSCP is about -111dBm during the access failure. 3. And the total used power was P= 3.

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 75 © Nokia Siemens Networks Charles / 2009-05-05 Page 75 .

And this failure was not found in the before and it is occupied 20% in all failure.FailEst. The RAB assignment failure of TNL is due to AAL2 setup failure in IU interface from CHR as following table. Most of reason is due to VS. CS RAB Assignment failure due not to configure ATM route in IU interface CS RAB assignment success rate decreased in RNC121.RAB.CS.TNL in the statistics. 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 For internal use 76 © Nokia Siemens Networks Charles / 2009-05-05 Page 76 .

but they did not tell us to add a new ATM route. the problem was solved after the address of 0x45000034901706502F0000000000000000000000 5 NO 1 0x45000034901706104F0000000000000000000000 is added 0x45000034901706503F0000000000000000000000 6 NO 1 in RNC. RNC sent the RAB_ASSIGNMENT_RESP The transport layer address is message to CN. message RAB_ASSIGNMEN_REQ from CN. 0x45000034901706103F0000000000000000000000 1 YES 1 0x45000034901706101F0000000000000000000000 2 NO 1  We asked the customers. 0x45000034901706501F0000000000000000000000 4 NO 1  And. So many RAB 0x45000034901706102F0000000000000000000000 3 NO 1 assignment failed for CS services. CS RAB Assignment failure due not to configure ATM route in IU interface From the trace. and the failure is due to IU transport 0x45000034901706104F0000000000000000000000 in connection failed to establish. it will all fail. For internal use 77 © Nokia Siemens Networks Charles / 2009-05-05 Page 77 . So if the address is assigned by CN in RAB assignment. the ATM NSAP RTX OWNERSHIP ANI route didn’t find. they added a new MGM. AAL2RT  Check the IU interface of AAL2RT configured in RNC.

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 78 © Nokia Siemens Networks Charles / 2009-05-05 Page 78 .

13.16.7 192. Network Layer) problem which means that the RAB CSSR degradation is related to the transmission system of the IUPS between RNC and SGSN.168.5 For internal use 79 © Nokia Siemens Networks Charles / 2009-05-05 Page 79 .10.133 10.4 192.1 10.168.2 192.168.8 192.13. PS RAB Setup Failures due not to IP Address configured in RNC •In recent 3 days.13.13.13.197 10.5 192.9.16. it cause HSDPA CSSR and HSUPA degradation is due to the TNL(Transmission CSSR worse than before too. There are 13 IPPATHs between Huawei RNC and SGSN: 192.168.9 192. As most of the PS service are •The main reason of the Rab CSSR setup on HSDPA service.16.8.9.50% to about 95% or less. PS RAB Setup Success rate degraded from about 99.168.13.3 192.168.5 10.168.16.13.168.13.

168.6 not configured .but assigned by SGSN.13. The IP address is not configured in RNC For internal use 80 © Nokia Siemens Networks Charles / 2009-05-05 Page 80 . PS RAB Setup Failures due not to IP Address configured in RNC Here there is an IP Address 192.

PS RAB Setup Failures due not to IP Address configured in RNC Action taken: 1.6 at 17:10 on Feb. For internal use 81 © Nokia Siemens Networks Charles / 2009-05-05 Page 81 .4th afternoon. Added IP address 192.168. PS RAB Setup Success was normal after IP address being added.13. 2.

Soft handover ratio optimization cases For internal use 82 © Nokia Siemens Networks Charles / 2009-05-05 Page 82 . Intra frequency handover parameters optimization cases 3. Inter-RAT handover parameters optimization cases 4. Radio Parameters Optimization Cases 1. Access control parameters optimization cases 5. BLER parameters optimization cases 8. PS call drop rate optimization cases 7. CS call drop rate optimization cases 6. Coverage parameters optimization cases 2.

39.2 kbps from 3GPP TS BLER means Block Error Rate and it 34.81 103 60 TFS TF0. bits 1x0 (note 2) 0x103 0x60 (note TF1. bits 1x39 1x103 1x60 1) TF2. the BLER is 2%. bit 0. What is the meaning of BLER? Transport channel parameters for AMR 12. It is at most 50 blocks in 1s. And it is very difficult to get the KPI target. So it is transmitted about 32 blocks in 640ms.0 are in the following table.12%. and the transport format is 81x1.39. BLER Optimization for CS The BLER target of the AMR (uplink and downlink) <= 2% in 97% samples in one commercial network. 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. It means 1 block is transported and each block is 81 bits in 20ms. ms 20 20 20 Only 1 block is error Coding type CC 1/3 CC 1/3 CC 1/2 CRC. 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. b) For the uplink. bit 0 MAC multiplexing N/A Layer 1 TrCH type DCH DCH DCH TB sizes. For internal use 83 © Nokia Siemens Networks Charles / 2009-05-05 Page 83 . bps 12 200 TrD PDU header. bits 1x81 N/A N/A TTI. the BLER is 3.1.108 V8. RLC mode TM TM TM Payload sizes. we get a BLER sample about each 640ms from the RNC. bit 0. If only 1 block is error in 1s.81 103 60 Max data rate. If only 1 block is error in 640ms. bit 0 MAC MAC header.

For internal use 84 © Nokia Siemens Networks Charles / 2009-05-05 Page 84 . If we improve the coverage. so no BLER is error. BLER and EcIo distribution in Cluster8 in Quito EcIo BLER Checking the BLER error distribution in the Cluster8. at the same time the BLER will be improved. it is good coverage. In the central cluster. you can find that the BLER error in most of cases is due to the poor coverage in the edge of cluster.

The formula of BLER is the 10*Lg(BLER).80% 99.05% 89.002dB) 1(0.25% 93.20% 0.76% VPBLER (DL) <= 1% 96.83% 96.12% 97. For internal use 85 © Nokia Siemens Networks Charles / 2009-05-05 Page 85 .001dB) control algorithm. 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.23% 95.31% 97.50% It is used by CRNC to decide the target SIR value that Video phone BLERQuality 0.005dB) 3(0. B.95% 97.39% 99.28% AMR BLER (UL) <= 2% 94. When the EcIo.003dB) Step of target SIR adjustment in outer loop power Video phone SIRADJUSTSTEP 2(0. Parameters optimization of BLER Type Parameter Name Default value Optimized value Comments AMR SIRADJUSTSTEP 5(0. Video phone RlMaxDlPwr(dB) 3 4 The maximum and minimum downlink transmit power of Video phone RlMinDlPwr(dB) -12 -11 radio link.20% 96.10% influences access and power control.94% 97.20% 90. Pilot Pollution and coverage are improved the BLER will be improved at the same time.78% 94.44% 98.76% 92.29% 99. AMR BLERQuality 1% 0. 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.32% 99.04% VP BLER (UL) <= 1% A.08% 98.52% 97.33% 97.56% 97. AMR RlMaxDlPwr(dB) 0 1 The maximum and minimum downlink transmit power of AMR RlMinDlPwr(dB) -15 -14 radio link.

Radio Parameters Optimization Cases 1. Soft handover ratio optimization cases For internal use 86 © Nokia Siemens Networks Charles / 2009-05-05 Page 86 . BLER parameters optimization cases 8. Inter-RAT handover parameters optimization cases 4. PS call drop rate optimization cases 7. Access control parameters optimization cases 5. Coverage parameters optimization cases 2. Intra frequency handover parameters optimization cases 3. CS call drop rate optimization cases 6.

3Soft2Softer )-1} But the counter is different between the two vendors. VS.2Soft + VS.SHO.SHO.SHO.3Softer Average Number of UEs with Three RLs Uncombined or Combined.AS.3Softer + VS. VS.1 + (VS.3Soft +VS. The counter for another vendor is based on cell level and radio link is measured in all active set.AS.SHO.SHO. but for Huawei it is based on RNC level and it does not measure in soft state.AS.AS.3Soft+ formula is  A1  B1  C1  VS.SHO.3Softer+ VS.1 + VS.AS.3Soft.SHO.SHO. So the RL is measured repeatedly for cell level.AS.SHO.2Softer + VS.3Soft2Softer Average Number of UEs with Three RLs and Two Combined •C1: NumberOfUEWith3RL VS.SHO. VS.AS. For internal use 87 © Nokia Siemens Networks Charles / 2009-05-05 Page 87 .AS.AS.AS.AS.2Soft Average Number of UEs with Two RLs Combined or Uncombined.AS.1 Average Number of UEs with One RL •B1: NumberOfUEWith2RL VS.AS.AS.SHO.AS.AS. and the custom should be modify the formula for soft handover ratio as following.SHO. We find that the formula to calculate the soft handover ratio is same between the two vendors.AS.AS.   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.2Soft)*2+ (VS. the soft handover ratio is less than 15% than before. 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.2Softer SHR    1 100% +VS. Soft handover ratio mapping for swap network In one swap commercial network in Europe .SHO.SHO.3Soft2Softer)*3)] /( VS.SHO.SHO.SHO.2Softer.

30 0. The soft handover parameter settings and site distribution have more impact on the soft handover ratio.76% Hong Kong RNC4 0.97% 43.15 58.56 0.68 0. and Quito.61% 32.10 42. c) The antenna pattern.62 0.16 62. Soft handover ratio mapping for swap network Many factors impact the soft handover ratio. Hong Kong. cell radius. including the following items: a) Soft handover parameter settings.59 0.68 0.24% Emirates Brunei 0.14 58.24 0.09% 43.12 50.28 0.30 0.54 0. b) Network topology.17% Quito 0. It shows the probability of one RL (radio link). We check the soft handover ratio in the commercial network of Huawei.22 0. Commercial 1RL probability 2RL 3RL probability Soft handover Soft handover Ratio network probability ratio(statistics) (Drive test ) United Arab 0. site distribution.08 40.89% (Average) For internal use 88 © Nokia Siemens Networks Charles / 2009-05-05 Page 88 .56 0.11 51. two RLs and three RLs in the United Arab Emirates.38% 32.76% Hong Kong RNC2 0. Brunei.85% 40. d) Path loss.81% Hong Kong RNC1 0.20% 45.18% 38.61% Hong Kong RNC3 0.26 0.29 0.