Disclaimer

People like Dieter, Holger, Daniel and I have invested lots of our spare time in the early years. So funding for that came from other paid work, and Osmocom projects were a hobby. It was a lot of fun, but it’s not a sustainable basis for the scope of the projects at this time.

Today, our development is driven by

This means in general that very little will happen, unless somebody commits to putting resources at it!

Major Roadmap Areas

OsmoNITB

RIP NITB; Long Live OsmoMSC

→ typical 2G setup will become OsmoBSC + OsmoMSC + OsmoHLR

OsmoSTP

Signal Transfer Point, part of libosmo-sccp

osmo_fsm + osmo_prim

osmo_fsm

structured approach to state machines

osmo_prim

structured approach towards primitives at SAP between layers

osmo_fsm

Generalized finite state machine (FSM) abstraction

Much more maintainable and deterministic than the many implicit or non-existing state machines in older code

osmo_fsm so far

osmo_fsm candidates

More osmo_fsm Would greatly improve code quality, testability and maintainability

Testing

osmo-gsm-tester

→ GOAL: Daily functional testing on all supported platforms/configs

osmo-gsm-tester

TODO:

External Interfaces

⇒ Roadmap is to put more effort into CTRL completeness

Grand Unified Config Theory

Big Wishlist item:

But who will fund this / put resources at it?

Integration between 2G and 3G

Operation / Maintenance

→ we need to generate more alarms in abnormal situations

→ we need aggregation/interpretation/analysis of that data

Further Wishlist

EOF

End of File