Local Call Local Switch¶

In the classic 3GPP architecture, all calls go from BTS to BSC to MSC, only then to go back all the same way in case the second call leg is also in the same cell. Particularly in case of statellite or other expensive/slow back-haul this is far from ideal.

Using LCLS, a BSC can know which of the two call legs belong to one call, and can then directly bridge the RTP/media locally.

Spec references¶

• http://www.3gpp.org/DynaReport/23284.htm
  • 3GPP TS 23.284 Rel 14
• http://www.3gpp.org/DynaReport/WiCr--440021.htm
• http://www.3gpp.org/DynaReport/WiCr--430001.htm

AoverIP¶

While osmo-bsc already supports A-over-IP as per IPA/SCCPlite stacking for many years, more recently 3GPP has specified an official A-over-IP interface.

Relevant specifications¶

• 43.903: A over IP Study http://www.3gpp.org/DynaReport/43903.htm
• TS 48.006 Section 6a, use of M3UA
• TS 48.008 Detailed extensions of Messages + IES for AoIP

Virtual GSM Load Testing¶

This is about development of Load Testing Setup to demonstrate OsmoBSC functionality and performance at >= 200 TRX, >= 100 BTS and thousands of MS.

• Development of primitive-based asynchronous interface to OsmocomBB âmobileâ program, together with script language (e.g. LUA) bindings for cellselection, location update, SMS and voice calls.
• Development of voice frame support to OsmocomBB virt_phy, OsmocomBB mobile and osmo-bts-virtual to simulate voice/user plane in addition to control/signaling plane.
• Development of software to manage (configure, start, monitor, stop) thousands of OsmocomBB mobile instances as well as hundreds of osmo-bts-virtual instances
• Creation + Documentation of corresponding test suite for automatic execution of load testing