osmo-bsc - OsmoBSC: Osmocom's Base Station Controller for 2G circuit-switched mobile networks

Age	Commit message (Collapse)	Author	Files	Lines
2023-10-23	ASCI: Add System Information 10 support	Andreas Eversberg	1	-0/+5
	For each BTS, an SI 10 is generated with the informations about all neighbor BTS that have the same group/broadcast call. The SI 10 will only define neighbor cells within the same BSC, because it does not know about neighbor cells within other BSCs. When multiple channels are used for a group/broadcast call, the SI 10 is generated after all channels have been activated. Subsequent channel activations result in an update of SI 10 on all channels. Change-Id: Icd3101e6dd935a57f003253aaef400c2cf95a0c3
2023-09-24	si2quater: Invalidate thresh_lo, prio and qrxlm when needed	Matan Perelman	1	-0/+1
	Change-Id: I5910ce8db2d085295b327b12096ba129369eb532
2022-10-27	gsm48_parse_meas_rep: fix parsing multi-band list	Oliver Smith	1	-0/+1
	When looking up "BCCH-FREQ-NCELL i" from the measurement report, don't treat the BCCH channel list as one list sorted by ascending ARFCN. Instead, treat it as two sub lists, one for the same band, and one for channels in different bands, as described in 3GPP TS 04.08 § 10.5.2.20. This fixes getting the wrong ARFCN from measurement reports in multi-band BSS, which leads to failing handovers. Fixes: OS#5717 Related: osmo-ttcn3-hacks I4fe6bb9e4b5a69ea6204585ebdf1f157a68a8286 Change-Id: Ic5e4f0531e08685460948b102367825588d839ba
2021-06-01	Drop duplicated arfcn_range_encode.c available in libosmocore	Neels Hofmeyr	1	-2/+2
	This code is available in libosmocore since ~3 years ago (fdf8b7b1beeb0cda262c5fb060a933aa7edb5e9a). Let's use it instead of maintaining duplicated code which diverges over time. Depends: osmo-bsc.git Iae058c35506bc25c9f4790889b89ac46aea664b6 (contains cherry-pick of bug fixed in osmo-bsc.git). Change-Id: I53ad3067623077b6a8737c2a0aecc8b46bf71a15
2021-04-12	[hopping] Rework generation of Cell/Mobile Allocation	Vadim Yanitskiy	1	-0/+1
	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
2020-07-03	system_information: publicly declare generate_cell_chan_list()	Vadim Yanitskiy	1	-0/+1
	Change-Id: Idc7a9ed558ed6897e15a0f6d3c23418db7cee0d0
2017-09-06	move include/openbsc to include/osmocom/bsc	Neels Hofmeyr	1	-0/+22
	Change-Id: I39e7b882caa98334636d19ccd104fd83d07d5055