OpenBSCOpenBSCHandover » History » Version 3
ipse, 02/19/2016 10:48 PM
Link to the handover improvement proposal.
1 | 1 | laforge | |
---|---|---|---|
2 | 3 | ipse | h1. Handover code in [[OpenBSC]] |
3 | |||
4 | |||
5 | 1 | laforge | Both the osmo-nitb and osmo-bsc programs implement hand-over between cells in the same BSC (intra-BSC). |
6 | |||
7 | 3 | ipse | We implement the algorithms recommended in the book _Performance Enhancements in a Frequency Hopping GSM Network_ |
8 | 1 | laforge | (by Thomas Toftegaard Nielsen and Jeroen Wigard). |
9 | |||
10 | The actual implementation is in http://cgit.osmocom.org/cgit/openbsc/tree/openbsc/src/libbsc/handover_decision.c |
||
11 | |||
12 | There are some tunable parameters but in the end it's not all that |
||
13 | complicated. The BSC tells the phone the list of neighbor BTS ARFCN, |
||
14 | the phone reports in every SACCH uplink frame the Rx Level measurements |
||
15 | of those neighbors. |
||
16 | |||
17 | There are a number of different reasons: |
||
18 | 3 | ipse | 1. interference HO, if the Rx level > -85dBm but the RxQual is bad over more then 3 out of 4 measurements |
19 | 1. bad quality HO, if the RxQual is bad in 3 out of 4 measurements |
||
20 | 1 | laforge | 1. low level HO, if the Rx level is < - 110dBm |
21 | 1. distance HO, if the TA is above a threshold |
||
22 | 1. power budget HO, i.e. if we have better cells |
||
23 | |||
24 | 3 | ipse | the decision is based on an average RxLev over a sliding window of |
25 | 1 | laforge | measurements, taking into account a configurable hysteresis level. |
26 | |||
27 | We have tested it in a couple of field tests (HAR2009, 27C3 and so on), |
||
28 | but none of our big real-world deployments is currently using hand-over, |
||
29 | as they typically have small single-BTS sites that have no neighboring |
||
30 | cells. |
||
31 | |||
32 | |||
33 | 3 | ipse | h1. Handover improvements |
34 | |||
35 | |||
36 | A proposal for the handover improvement is published [[handover|here]]. |