osmo-bsc[master]: prevent ARFCN+BSIC collisions in config

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.

Neels Hofmeyr gerrit-no-reply at lists.osmocom.org
Mon Apr 16 13:31:11 UTC 2018


Patch Set 1: Code-Review-1

so, it's not that simple. Practically, one would want to be able to re-use the same ARFCN+BSIC even within the same BSC. When resolving an ARFCN+BSIC, the source BTS is the third part of information that needs to provide a unique match. i.e. each BTS has neighbors with unique ARFCN+BSIC configs, while the same ARFCN+BSIC might be re-used three neighbor hops further out.

  A - B - C - A

While it might hold for now, we can't be that strict in the long term. Let me see whether it's simple enough to do it properly right from the start.

-- 
To view, visit https://gerrit.osmocom.org/7814
To unsubscribe, visit https://gerrit.osmocom.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: Ia7c38188ccbad5d8b7398e3e5220015e62c08c8b
Gerrit-PatchSet: 1
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Owner: Neels Hofmeyr <nhofmeyr at sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: Neels Hofmeyr <nhofmeyr at sysmocom.de>
Gerrit-HasComments: No



More information about the gerrit-log mailing list