Hello, all,
I wonder if anyone has thought about introducing a handover log (to a file or a DB) to OsmoBSC/OsmoNITB?
For small deployments <6 BTS you can just add every BTS to neighbor lists of each other and don't worry, but once you get above that, you face a handover optimization issue. I.e. which BTS should be neighbors of which other ones. Initial assigning of the neighbors can be done by simply looking at coverage maps of each BTS. But once the network is actually used there is a lot of useful information about the network performance which can be extracted from the handover history - which cells have issues handing over to each other, etc.
On Thu, Jan 04, 2018 at 02:16:17PM +0900, Alexander Chemeris wrote:
Hello, all,
I wonder if anyone has thought about introducing a handover log (to a file or a DB) to OsmoBSC/OsmoNITB?
Seems like a good idea. The main question is how to implement it in a way that is easy to evaluate.
We have those rate rounters that could easily count handovers per BTS, but to count between each pair of BTSes is an exponential thing.
I'm not closely familiar with them, but we also have external DB storage mechanisms of events; I wonder whether we have documentation for those? I can't find much on it, just know we used it on 34c3.
The simplistic approach would be to just output logging statements. We have the HO (handover) and soon the HODEC (handover decision) logging categories, with minor effort that logging could be made easily parsable by external tooling.
So all for it, as always the questions are how to and who will implement.
~N
-
Alexander Chemeris -
Neels Hofmeyr