URGENT: range 1024/512/256 encoding of neighbor cell list required

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/.

Dieter Spaar spaar at mirider.augusta.de
Sat Dec 26 09:37:20 UTC 2009


Hello Harald,

On Sat, 26 Dec 2009 00:40:05 +0100, "Harald Welte" <laforge at gnumonks.org> wrote:
> 
> If anyone understands (and/or has time to implement) the specification
> in GSM TS 04.08 10.5.2.13.3 / 10.5.2.13.4 / 10.5.2.13.5, or even the full
> algorithm as specified in "Annex J: Algorithm to encode frequency list
> information elements", I would be extremely grateful.

Sorry, no time to code the algorithm, however here is a handcrafted
list:

   0x83, 0x64, 0x5C, 0x00, 0xFF, 0x3F, 0xC0, 0x00, 
   0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 

It contains ARFCN 536, 540, 868, 870 und 871, I have not yet checked it
with a phone.

I guess its OK to use it for all five BTS units, T-Mobile also includes
the main BCCH ARFCN in the neighbor cell list, at least here in my area,
so this should work for us too.

Best regards,
  Dieter
-- 
Dieter Spaar, Germany                           spaar at mirider.augusta.de




More information about the OpenBSC mailing list