While NSN rely on periodical measurement reports and based on these the RNC decides whether to trigger IRAT or not, on E******* event 3a is configured so the RNC will only triger the IRAT HO once the UE sends one of these measurement reports (only one is needed).
That is wrong "Wolverine" IRAT HO in NSN is triggered by event also. RNC send IRAT HO request to MSS which decides by its role to trigger HO or not depending on target GSM cell availabiliy.
There will be much better results if you include "AdjgRxlevminHO" together with "GsmMaxMeasPeriod".
Set AdjgRxlevminHO step by step making it harder to perform ISHO.
For example:
Step 1: -95 dBm
Step 2: -85 dBm
Step 3: -75 dBm
This is the minimum average Rxlev of 2G before UE can handover to that BCCH.
When UE in ISHO, radio condition is of course bad, but it does not mean that 2G should be bad also, this parameter makes sure that the 2G cell the UE is going to handover is a healthy cell. Thus, reducing the probability of RL disconnection during CM because UE selected a poor 2G cell.
Expect the ISHO attempts to lessen, 3G traffic to increase and ISHO SR to improve dramatically.
There will be much better results if you include "AdjgRxlevminHO" together with "GsmMaxMeasPeriod".
Set AdjgRxlevminHO step by step making it harder to perform ISHO.
For example:
Step 1: -95 dBm
Step 2: -85 dBm
Step 3: -75 dBm
This is the minimum average Rxlev of 2G before UE can handover to that BCCH.
When UE in ISHO, radio condition is of course bad, but it does not mean that 2G should be bad also, this parameter makes sure that the 2G cell the UE is going to handover is a healthy cell. Thus, reducing the probability of RL disconnection during CM because UE selected a poor 2G cell.
Expect the ISHO attempts to lessen, 3G traffic to increase and ISHO SR to improve dramatically.
Bookmarks