: Internal only

Auth or Depa rtme nt Upda te Time Appr over Title Pheno menon Descri ption: Alarm Inform ation Cause Analysi s

Gao Bo UMTS RNP 2010-06-01

Staff Number Product Family: Product Vension:

40827 Wireless Performance & RNP & RNO RNC R10B061

Analysis for Call Drop due to SRB Reset

!RB Reset

The problem is that there are many sites have the problem of SRB reset and TRB reset increased.
None

For this problem, we choose the top cells of the RNC analy"e the reason of SRB # TRB reset.

! and RNC !

to

From the analyses of the cell C$T and I%S, &e can 'now that () was doin* +S$,- traffic .It did hard handover from one cell to another cell. B.t after hard handover completed, imminently, () did hard handover bac', this is the pin*/pon* phenomena. It is easy to res.lt in radio lin' lost and the increase of TRB0SRB Reset.For the downlin' 1.ality chan*ed so fast, it is abnormal. -nd this is .s.ally beca.se that the C)223s parameter or cell3s covera*e is .nreasonable. -nd the same phenomena also can find in the cells with I$ 4456 , 478 , 95!5 , 9575, 94!: 9478. From the trace, we can see that the () hand over from cell 4456 to cell 4785 , b.t after ! seconds, it delete the lin' of 4785. It is so fast, and the R2 was o.t of synchroni"ation, then the call drop occ.rred.

2013-1-31

1 , 8

: Internal only

From the meas.re report, we can see that the cell 4785;,SCR-<BC%$)=5>5? has a better )C0N%, then the - event happened s.ccessf.lly.

2013-1-31

2 , 8

: Internal only

B.t after ! seconds, the )C0N% chan*ed so fast and the R2 of the cell 4785 was deleted.

2013-1-31

3 , 8

: Internal only

Then the R2 was o.t of synchroni"ation. -nd the SIR/)rror val.e of the (plin' is so bad. The call drop occ.rred.

-nd there are many pin*/pon* phenomena as below: From the trace
2013-1-31 4 , 8

: Internal only

we 'now that the () hand over from 4455 to 4456, then immediately, hand over bac' to 4455.It cost only or two seconds. This is .nreasonable. It is easy to res.lt in radio lin' lost.

From the C$T and I%S, we can find the other problem ca.sed the call drop, for e@ample, the bad downlin' 1.ality and the nei*hbor cell not confi*.red. If in some position the downlin' 1.ality is bad, and the nei*hbor cell has not been confi*.red, the call drop will occ.rred easily. ? Nei*hbor cell not confi*.red For cell 4456, from the I%S trace, we can see that it has the problem of nei*hbor cell not confi*.red. A.st as the cell 9:> we analy"ed before.
From the I%S, the .plin' has been o.t of synchroni"ation, and from the RRCB<)-SBR,RT, we can see that the downlin' of cell 4456;,SCR-<BC%$)=549? is bad, and the () has reported the event of -, b.t from the RNC confi*.ration file, we can3t find the nei*hbor cell of 4456 whose ,SCR-<BC%$) is ! :. -nd if the cell the () detected ;,SCR-<BC%$)=! :? is confi*.red as the nei*hbor cell of 4456, this call drop will not occ.rred. This is a covera*e problem, and we need to solve it.

2013-1-31

5 , 8

: Internal only

!? $ownlin' bad For the cell 9445, it has many times of TRB reset and (( No reply, we have collected the lo*s to analy"e the reason. There are many call drop proced.res as below: -fter the () *oes to F-C+ then call drop occ.rred.

2013-1-31

, 8

: Internal only

&e can see that the () want to *o to the $C+, b.t From the RRCB<)-SBR,RT we can find the )C0N% is bad now which means the downlin' is bad, and the () wo.ld not receive the messa*e of RRCBRBBR)CFC. Then the Call $rop occ.rred. -nd from the RRCB<)-SBR,RT, we can3t see any other cells that the () can detected.

-nd we can see as below: If the downlin' is *ood, the () will *o to $C+ s.ccessf.lly.
2013-1-31 ! , 8

: Internal only

It can be solved by optimi"in* the parameter and the covera*e of the networ'. Handli ng Process Sugges tions and summa ry Attach ments Relate d docum ent link

The pin*/pon* phenomena is abnormal, and the lo*s shows that the
call drops were d.e to the covera*e of cells and the parameters confi*.red.

2013-1-31

8 , 8