From 91a202d4885d1e3aff6cb090ec688d695c2cd26b Mon Sep 17 00:00:00 2001 From: Neels Hofmeyr Date: Sat, 13 Jul 2019 01:12:53 +0200 Subject: neighbor config: allow re-using ARFCN+BSIC pairs Fix neighbor config to match OsmoBSC manual: implement the plan for neighbor configuration that was so far only described in the manual without actually being in operation. This first allows re-using ARFCN+BSIC pairs in and across BSS. So far the handover_start() code always looked for handover target cells across *all* local cells, even if they were not listed as neighbors to a source cell. Imply all cells as neighbors only as long as there are no explicit neighbors configured. As soon as the first 'neighbor' line appears in a 'bts' config, only the listed neighbors are regarded as handover target cells. (The 'neighbor-list' commands are not related to this, only the relatively new 'neighbor (bts|lac|cgi|...)' commands affect actual handover procedures.) TTCN3 tests TC_ho_neighbor_config_1 thru _7 play through the various aspects of neighbor configuration: both the legacy implicit all-cells-are-neighbors as well as allowing only explicit neighbors by config. Related: OS#4056 Related: osmo-ttcn3-hacks Ia4ba0e75abd3d45a3422b2525e5f938cdc5a04cc Change-Id: I29bca59ab232eddc74e0d4698efb9c9992443983 --- tests/bsc/bsc_test.c | 2 ++ 1 file changed, 2 insertions(+) (limited to 'tests/bsc') diff --git a/tests/bsc/bsc_test.c b/tests/bsc/bsc_test.c index 492f0c5a1..103e0bbb8 100644 --- a/tests/bsc/bsc_test.c +++ b/tests/bsc/bsc_test.c @@ -250,3 +250,5 @@ void gscon_submit_rsl_dtap(struct gsm_subscriber_connection *conn, struct msgb *msg, int link_id, int allow_sacch) {} void ts_fsm_alloc(struct gsm_bts_trx_ts *ts) {} void lchan_activate(struct gsm_lchan *lchan, void *info) {} +bool neighbor_ident_bts_entry_exists(uint8_t from_bts) { return false; } +const char *handover_status(struct gsm_subscriber_connection *conn) { return "x"; } -- cgit v1.2.3