Directed Retry Paramters

Yes, if the candidate target is congested, the fast traffic ho will fail due to congestion.

But I must disagree with you : the HO inc fail due to congestion is NOT a KPI !!

HO congestion means the BSC detects a HO, and check for available candidate. If it doesn’t find the candidate is congested, what is actually the impact for the subscriber ? Not being able to setup the call ? So it is as if fast traffic HO is disabled… >> call setup fails.
But sometimes, the BSC finds a candidate with a free TCH >> call setup succeeds.

Altogether, you increaase the probability of call setup success, even though you artificially increse the inc HO congestion.

The KPI for HO is actually “outgoing HO execution success rate”, which doesn’t take into account congestion failures.

Cheers,
pix

DR = HO from sdcch to tch, detected with a standard HO algorithm (could be poor quality, low level, long distance, power budget, etc)

FDR = ho from sdcch to tch, detected thanks to a specific “capture-style” algorithm:
if DL_RXLEV(n) > L_RXLEV_NCELL_DR(n) and number of free TCH in n > FREELEVEL_DR(n), then the MS is sent to “n”.

The order of detection… DR is actually a mix of different causes, so if DR is detected on Emergency algo, it has high priority. If it is detected with PBGT algo, then it has the same priority as the cause 12.

FDR and fast traffic HO have less priority than cause 12. But the priority is no really important here : DR doesn’t happen much, while FDR and FTH are more easily triggered.

Cheers,
Pix

Best regards,

MS, MO, HSN, what is the role in a cell. Plz explain .