8 Jul
2013
8 Jul
'13
11:21 a.m.
On Mon, Jul 8, 2013 at 6:34 PM, Thomas Tsou <tom(a)tsou.cc> wrote:
On Mon, Jul 8, 2013 at 3:27 PM, Andreas Eversberg
<andreas(a)eversberg.eu> wrote:
There could be two command sets - one for OpenBTS compatibility, one
for more advanced systems.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Thomas Tsou wrote:
We can easily move to separate TSC settings be removing the static
identifier. The only issue then is that OpenBTS will no longer work.
Perhaps the larger limitation is that we can't set TSC dynamically
after POWERON. This is because the midamble correlation sequence is
regenerated and is not thread safe. Should we now assume that each TRX is setup an
independent manner?
i see no problem with that reject. i think it makes sense to reject TSC,
if it does not match the TSC of first TRX. since trx manager interface
seems to be designed to handle each TRX individually (even might be
possible to run on different transceivers for one BTS), i would think it
is a good idea to set TSC for every TRX.