Escolar Documentos
Profissional Documentos
Cultura Documentos
<
MSC timer values. In this case we should not get anyimprovement. But we got some improvement as T305 is the
timer trigerred first, and if no response isreceived for T305 with in N200 expiry time, T308 is initiated. Therefore, T305
is actually which has given us improvement. For further improvement we needto change SIGDEL values to Long from
Normal. Which would make sure we get improvementby T308 as well. Please correct me if I am wrong. Regards,
With the ongoing exercise of changing system parameters to gain our objective of reducing the TCH drop in the network.
Below are the changes done in the MSC.
Before the changes :
T305 + 2*T308 + T3109 < (N200+1)*T200
30 + 60 + 1 <(3+1) *0.24
91 < 0.96
The parameter settings on the BSC side and MSC side may affect the TCH call drop rate.
You should check the settings of the following parameters for a cell with a high TCH call
drop rate. See Case 5: Reduction of Call Drops by Optimizing Handover Parameters and
Case 12: Increase in Call Drop Rate Due to Change of TR1N on the MSC Side.
1. SACCH Multi-Frames
This parameter determines whether an uplink radio link is faulty. Each time the BTS fails to
decode the measurement report on the SACCH from the MS, the counter decreases by 1.
Each time the BTS successfully decodes the measurement report on the SACCH, the
counter increases by 2. When the value of this counter is 0, the BTS regards the radio link
as faulty. In the traffic measurement, if there are many call drops (M3101A) related to radio
link failure, you can infer that the radio propagation conditions are poor. In this case, you
can set this parameter to a greater value.
2. Radio Link Timeout
This parameter determines whether a downlink radio link is faulty. Each time the BTS fails to
decode the measurement report sent over the SACCH by the MS, the counter decreases by
1. Each time the BTS successfully decodes the measurement report sent over the SACCH,
the counter increases by 2. When the value of this parameter is 0, the BTS regards the radio
link as faulty. In the traffic measurement, if there are many call drops (M3101A) related to
radio link failure, you can infer that the radio propagation conditions are poor. In this case,
you can set this parameter to a greater value.
3. RXLEV_ACCESS_MIN
This parameter specifies the minimum receive level of an MS to access the BSS. If this
parameter is set to a too small value, some MSs with low receive levels may access the
network and call drops are likely to occur. You can set this parameter to a great value to
reduce the TCH call drop rate. The counters such as call setup success rate and the
Cv a
I assume that your coleague changed the MSC side timer T305 and T308, your coleague did a "clever" trick
to let the MSC clear the call early before the BSS side peg the drop call statistics. In long run, your coleague
just plays around these timer parameters and doesn't improve the network quality. I saw similar actions
before.
Here are the explanation what these 2 timers are used for.
T305 timer is started at the MSC/MS when DTAP message DISCONNECT is sent, this will guard the
DISCONNECT procedure run correctly in T305 period.
T308 timer is started at the MSC/MS when DTAP message RELEASE is sent after the DISCONNECT
procedure, this timer guards how long the RELEASE procedure runs.
(GSM 04.08 section 5.4 call clearing)
T305 and T308 at MSC should be set to no less than 11 seconds to guarantee that the layer 2 T200 is timing
out N200 times on the air interface, reducing these timers to less than 11 seconds will pull them below the
related BSS timers[T200*(N200+1) in this case] at the air
interface that are used to ensure a successful transmission of a message (DISCONNECT and RELEASE in this
case) to/from the mobile over the air interface. Normally the higher level MSC timers would be set longer
than the related lower level times in the BSS, using a strategy that lower level timers should expire first.
Setting T305 and T308 to less than 11 seconds here is forced the higher level MSC timers to expire before
the BSS timers[T200*(N200+1) and link_fail(only for MSC issuing DISCONNECT/RELEASE first)] when there
are air interface transmission problems (RF interference) for DISCONNECT and RELEASE signalling, and as a
result the BSS statistics SD/TCH drop doesn't get a chance to peg for T200*(N200+1).
The end user experience is probably not that relevant here as they were trying to clear the call anyway. The
end user would see no difference.
However the network operator could be fooled here though thinking that he has a clean RF interface with a
lower drop call rate, when in fact there could be RF interference issues to be resolved. The low MSC timers
are just masking it.