neighbour cells

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/OpenBSC@lists.osmocom.org/.

Holger Hans Peter Freyther holger at freyther.de
Mon Mar 11 13:56:22 UTC 2013


On Mon, Mar 11, 2013 at 07:50:43AM +0100, jolly wrote:

> yes, i missed that. but IIRC, it must be set on non-PCS cells (i.a. 850
> or 900) to indicate whether neighbor ARFCN of 512... refer to PCS. on a
> PCS BTS it should be ignored by MS.


right, as PCS/DCS is not allowed I take a look during the SI generation
and check if that bts is a DCS/PCS unit and set the indicator.

In terms of VTY we need to add consistency checks at the time of a 'write'
call and after loading. But this is not limited to the DCS/PCS code.

> if (n)
> ...
> si2->bcch_frequency_list[0] |= 0x20;
> si2b->bcch_frequency_list[0] |= 0x20;
> 
> if there are frequencies defined in si2bis, the EXT-IND is set on both
> (si2 and si2bis) lists. if not, the si2bis is removed and not transmitted.

true. I was confused and thought EXT-IND is set for SI2ter as well. But
this is signalled in the SI3 rest octets. SI5ter doesn't appear to be
signalled at all.

greetings from Iceland
	holger




More information about the OpenBSC mailing list