Full state machine implementation

[Harald Welte]

Hi Sipos,

On Sun, Jul 10, 2016 at 06:43:51PM +0200, Sipos Csaba wrote:
> Just seen your branch regarding FSM:
> 
> http://cgit.osmocom.org/openbsc/log/?h=laforge/om2000-fsm

I'm happy at least somebody notices this work :)

It's not complete yet (hence the WIP), and it currently only implements
the initialization as set of hierarchical state machines.  The FSMs
terminate once initialization is done.  This could and should probably
be further extended to having the BSC-side per-MO FSMs running
persistently and tracking the state of their counterparts in the BTS.

I also committed the OM2000 MO initialization sequences messace sequence
charts to osmo-gsm-manuals, in case you're curious to see how code
corresponds the protocol messages.

> Do you think this is also doable for the Nokia Site BTS series?

Of course, why not?  I've never looked too deep at the Nokia OML
dialect/flavor though.  I think for most users the more important part
would be the generic one for the TS 12.21 managed objects, which then
helps for nanoBTS, OsmoBTS and BS-11.

> Because if you think its doable, based on your work I a would like to
> try and implement this for Nokia support too, as even between
> different Site versions (InSite, Metro and UltraStie), there are some
> differences in the OML initialization (especially in the timing of it)
> which is now handled by hard coded values, instead of a proper state
> machine.

Sure, I think it would make a lot of sense, technically.  I'm just not
sure how many OpenBSC useres with Nokia BTS are out there.  But that
shouldn't keep you from doing it, if you feel an urge to do so :)

-- 
- 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)