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/.
Harald Welte laforge at gnumonks.orgHi Neels and others.
FYI, I added a dot graph of the osmo-nitb data structures and their
relations to openbsc.git in commit bafc1e4. The file is called
openbsc/doc/osmo-nitb-data_structures.dot
In general:
* BTS/TRX/TS/LCHAN are BSC-side data structures
* subscriber is a MSC-side data structures
* subscriber_conn is sort of in between BSC and MSC, but mostly
on the BSC side, too.
Thus:
* subscriber_conn should not point to gsm_bts. This is mostly used
to resolve gsm_network. Replace conn->bts with a new conn->network
* a 'network' will be required in both BSC and MSC
* subscriber_group was an early idea that was never really used and
could/should eventually be removed, and replaced with a direct
subscriber->network reference.
* nothing on the MSC/CSCN side should refer to lchan/ts/trx/bts
subscriber_conn must be split between the BSC and the MSC/CSCN side.
BSC side:
* maintain the references to the lchans required for hand-over,
assignment, etc.
MSC/CSCN side:
* remove the references to the lchans
* instead refer to the Iu/A interface SCCP connection for this subscriber
Regards,
Harald
--
- Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)