[RFC] Changes to the lchan and BSC/MSC split

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 Freyther zecke at selfish.org
Thu Oct 1 02:23:02 UTC 2009


On Wednesday 30 September 2009 19:25:13 Harald Welte wrote:
> Hi Zecke,

Ni Hao Laforge,


> >          The lchan is getting released when the transaction is finished,
> > in case of the "RSL chan" is going away too early there will be a "clear"
> > signal/method called from the BSC and the MSC side is asked to let it go.
> 
> well, what we need to somehow ensure is a situation where multiple
>  transactions are pending / ongoing for one MS, i.e. a call is already
>  established (or in the process of being established), while another call
>  is to be signalled, or while SMS are to be delivered, etc.
> 
> How would this fit into your new concept?

I think there is no change to the problem above as it is mostly policy (e.g. 
two phone MS terminated calls at the same time) or to queue SMS submit and 
then phone call.

What is currently in the tree but unused is the "subscr_get" and "subscr_put" 
methods that implement queuing on top of the paging layer. The current
implementation will close the channel on _put and initiate paging again. This 
could/should be tweaked to issue a channel modify and then pass on the
transaction from one subsystem to another. Once everything has been handled
the "CLEAR REQUEST"/transaction end would be signalized and the radio
resource would be freed.

does this make sense to you?
	holger







More information about the OpenBSC mailing list