diff options
author | Vadim Yanitskiy <vyanitskiy@sysmocom.de> | 2021-04-06 04:01:50 +0200 |
---|---|---|
committer | fixeria <vyanitskiy@sysmocom.de> | 2021-04-12 12:17:40 +0000 |
commit | 6a8536d4da7a2be83ba8647ed12bdc200740dc36 (patch) | |
tree | 4ec87e8e2900945ec39bcf075db3df4d25bdb499 /src/osmo-bsc/pcu_sock.c | |
parent | 711ac95c26a9c7f280a3fa82ddae5e2442038c45 (diff) |
[hopping] Rework generation of Cell/Mobile Allocation
Calculating the Cell Allocation (basically a bit-vector of all the
frequencies allocated to a cell) on the OML link establishment has
several downsides and potential problems:
* Theoretically, more than 64 ARFCNs can be allocated for a cell
via the VTY interface. The problem here is that the Mobile
Allocation IE cannot contain more than 64 channels.
* The BSC's operator will neither be warned by the interactive
VTY shell during configuration, nor during the startup.
* The BSC will accept such a configuration, but then will be
unable to encode the Mobile Allocation IEs at run-time.
This change aims to improve the situation by separating part of
the logic from generate_cell_chan_list(), and invoking this
part directly from the VTY commands. This way it will become
impossible to configure more than 64 ARFCNs, neither via the
config file, nor interactively from the VTY.
Change-Id: I98211fb0684a973239f5760e1de52a24a1f4c33c
Diffstat (limited to 'src/osmo-bsc/pcu_sock.c')
0 files changed, 0 insertions, 0 deletions