You are on page 1of 5

SD

drop

rate

in

Mila

cluster0708 and 09

After swap, the sd drop rate of cluster78 and 9 degrade too mach.
e.g. Cluster8:

Top cell trace analysis


Trace for C43X114_1:

When [SAMULFRM]=20 (9.6s<10s)


SD drop almost is for location updating, and the level is low.
After Establish Indication, DL MR Loss.
At 17:44:56 (300), the first authentication request is send from MSC.
At 17:45:01 (290), the second authentication request is repeated; the time
interval of authentication request is just 5s, which is the same with the
timer in MSC for authentication.
At 17:45:03 (770), connection failure call drop occur, the time interval is about
2.5s, which is smaller than 5s.

When

[SAMULFRM]

=20->24

(9.6s-

>11.5s>10s)
After Establish Indication, DL MR Loss.
At 15:59:17 (560), the first authentication request is send from MSC.
At 15:59:22 (550), the second authentication request is repeated; the time
interval of authentication request is just 5s, which is the same with the
timer in MSC for authentication.
At 15:59:27 (560), the channel release is send from Network, the time interval
is about 5s, for authentication the timer is out.

Difference between HUAWEI and


SIEMENS
The parameter SAMULFRM in HUAWEI is used for non-AMR and
signalingSDCCHnow all cell in Mila is set as 20.
In NSNfor signaling (SDCCH) used the following parameter

And in NSN dump this parameter is null:

So in NSN the parameterRDLNKTBSwill be used for signaling (SDCCH).

And in cluster789, all the cell this parameter set 24 before swap, and after
swap the parameterSAMULFRMin HUAWEI is set as 20, this will affect the
SD drop rate, we should change it.

The KPIs after action


SD drop rate and CSSR improve too much. SD drop from 1.2 to 0.11 (before is
0.25)

Different clusters kpi:

You might also like