Re: What can be the reasons of Handover failure? Answer # 1 1. Neighbours Definition with Co BCCH and BSIC. 2.

Wrong HO Synchronisation. 3. Non Symmetrical (One Way Neighbours). 4. Adjacencies Discrepancies. 5. High TCH Congestion. 6. Missing Potential Neighbours. 7. Missing Frequencies on Active State of BA List. 8. Creation of unwanted far of Neighbours with low signal strength 9. Abis failure (PCM related faults). 10. VSWR-DAC Values Issues. 11. BTS Hardware Issues. Is This Answer Correct ? 5 Puneet Verma 33 Yes 2 No

Re: What can be the reasons of Handover failure? Answer # 2 most you hang around entry level to internediate level answers to HO failues in GSM. Here are some heavy hitters to consider: 1. Speech Codec mismatch 2. Encryption/Ciphering mismatch And, much more. Cheers.

High Handover Failure Rate Posted by goengineer on September 16, 2009 High handover failures rate will probably be due to one or more of the following reason. 1. High Neighbour Interference 2. No Dominant Server 3. Database Parameters Optimization for tips : 1. High Neighbour Interference While handling off to the best neighbour the interference on the target cell fre quency may result in the hand off failure. TIPS: When designing the cell frequencies care should be taken that there is proper fr equency spacing between the cells to avoid neighbour interference. In most of th

e cases Ping Pong Handover starts i.e the mobile hand off to a cell for better l evel and due to interference (Quality issues) hand off again to original cell. A through drive test can determine the interfering frequencies which should be elim inated from the frequencies plan. 2. No Dominant Server If cell sites are designed poorly there might be areas where neighbour being rec eived at the same level and some neighbour randomly look good for hand off for a certain amount of time. Such situation is disastrous because handoff decision w ill be hard and mostly it will end up unsuccessful handovers. TIPS : Antenna tilts provide the good way to reduce the footprint of the sites. Efforts should be made that a single dominant server should serve the specific area. Ti ming advance limitation is applied to cell areas where there is multiple servers . 3. Database Parameters Received level, receive quality and power budget algorithm are set in the system information to define the criteria for handover. Improper values for these crit eria may result in poor handoff. TIPS: Enable the per neighbour feature which dispalys the successful and unsuccessful ha ndovers on a per cell basis. In optimization, monitor the following stats, which comes under cell statistic category . All those cells can be identified which are problematics in terms of hand off so one can focus only specific cell causing the major contribution towards poor HS SR. Ensure that handover margins are optimised. Rule of thumb is a 4 dB for adje cent frequencies and 6 dB per cell without adjecent frequencies. The following p arameters can be played for defining the threshold for imperative and non-impera tive handovers. a. Defines the lower threshold for uplink quality handovers. ex : Range 0 to 1800 Step size = 0.01 a value of 500 defines the lower threshold value of 5 (BER) for a quality handov er to be triggered for uplink. The optimum for this threshold is 500. b. Defines the lower threshold for downlink quality handovers. c. Defines the lower threshold for received level uplink handovers. Ex : A value of 20 defines the threshold value of -90 dBm for a level handover to be triggered for uplink. Range 0 to 63 Where 0 = -110 dBm 1 = -109 dBm

63 = -47 dBm The optimum value for this threshold is 15 ( elow that, a level handover is initiated. 95 dBm). If the signal level goes b

d. Defines the lower threshold for received level downlink handovers. e. Defines the upper threshold for uplink interference handovers f. Defines the upper threshold for downlink interference handovers

Hi jjohnwongtp Thanx.Will u pl let me know what do u mean by wrong response scenario.And what d oes 0 1 0 1 1 1 1 1 Semantically incorrect message signify?? I found this problem in Delhi/Dolphine network. Thanks and Regards jjohnwongtp - 19th August 2003 (09:09 GMT)

Hi Sharma This RR cause value 111 could means that MS with some response scenario is incor rect to Network side, so network response with HANDOVER FAILURE with RR Cause va lue 111; Which network does you test for this case ? where are the location you tested ? jjohnwongtp - 19th August 2003 (09:05 GMT)

HI Sharma, I checked with ETSI spec., I think the RR cause value 111 is listed below : RR cause value (octet ) Bits 8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 0 Normal event 0 0 0 0 0 0 0 1 Abnormal release, unspecified 0 0 0 0 0 0 1 0 Abnormal release, channel unacceptable 0 0 0 0 0 0 1 1 Abnormal release, timer expired 0 0 0 0 0 1 0 0 Abnormal release, no activity on the radio path 0 0 0 0 0 1 0 1 Preemptive release 0 0 0 0 1 0 0 0 Handover impossible, timing advance out of range 0 0 0 0 1 0 0 1 Channel mode unacceptable 0 0 0 0 1 0 1 0 Frequency not implemented 0 1 0 0 0 0 0 1 Call already cleared 0 1 0 1 1 1 1 1 Semantically incorrect message 0 1 1 0 0 0 0 0 Invalid mandatory information 0 1 1 0 0 0 0 1 Message type non-existent or not implemented 0 1 1 0 0 0 1 0 Message type not compatible with protocol state 0 1 1 0 0 1 0 0 Conditional IE error 0 1 1 0 0 1 0 1 No cell allocation available 0 1 1 0 1 1 1 1 Protocol error unspecified

This means it is the Protocol error unspecified, this means a HANDOVER FAILURE m essage with RR cause value 111 is a scenario bug in MS, pls. list your MS messag e scenario for this HANDOVER FAILURE case; Sharma - 18th August 2003 (08:24 GMT)

Hi All, There are some cause values in ETSI recommendation which describes the handover failure problem.Can anybody help me to know what does cause value 111 and other mean.I have found RR cause value 111 in layer 3 messages most of the times while doing the drive test. Thanks and Regards jjohnwongtp - 17th August 2003 (04:59 GMT)

Hi, I experienced this kind of situtation in some network coverage area before, we f ind MS can have several situtations need to check : 1. Handover ARFCN receiving power level ? 2. Handover ARFCN SNR ? 3. Handover ARFCN BSIC situtaion If you find more handover failure statistic at some area is caused by (1), then, this means some bad coverage happen on this area, we need to check with AGC lev er we use to make sure that AGC algorithm in Handset is correct, if this is a ne w MS design;

if you find more handover failure statistic at some area is caused by (2), then, you need to check how many different network or ARFCN plan at that area, you al so need to statistic their power level to understand any interference over the s pec. of MS that MS can not handle, it mostly happen with situation there are sev eral networks at some area with several repeater; Nguyen - 1st August 2003 (10:09 GMT)

This parameter does not belong to MS, it belongs to the BTS and can be set in th e BTS database. This timer sets the wait period (time) for handover complete from MS on target c ell. This timer starts when the BTS attempts to assign a channel for a handover. If this timer expires, the handover terminates. I dont know the ETSI name of this timer, and not sure whether it is the ETSI sta ndard timer. In the Motorola BSS, this timer is named ho_complete. If anyone knows the ETSI name of this timer, plz let me know. Brgds. neelam - 1st August 2003 (09:01 GMT)

Thanks Nguyen what is the wait period of the MS and where it is defined Nguyen - 1st August 2003 (08:24 GMT)

I think this is the big question which almost all operators have to face with. I n my knowledge, the possible causes are: + + + + Traffic congestion at the destination cell. Bad planning of BSIC and frequency (included in HPLMN and adjacent PLMN) Bad planning of radio coverage, that cause the ping-pong symptom. The wait period set for the MS to move from the source cell to the destination cell in a handover may have been too short. + Other timers that related to handover (T7, T8, Tqho, T3103, T3105) have not be en set properly. + ... ;-( Of course there are still many causes, that are waiting for other to contribute.