Open Source Mobile Communications: Issueshttps://osmocom.org/https://osmocom.org/favicon.ico?16647414092017-10-06T14:53:38ZOpen Source Mobile Communications
Redmine Cellular Network Infrastructure - Feature #2558 (Stalled): Scripts to manage thousands of "mobile...https://osmocom.org/issues/25582017-10-06T14:53:38Zlaforge
<p>The goal here is to be able to run a network with hundreds of BTSs, several hundreds of TRXs and thousands of MSs from a single command, in order to perform load testing against OsmoBSC.</p>
<p>The scripts should make sure all related processes are started reliably, their termination is recorded, and somehow their result / error / logging is aggregated and reported.</p> OsmoBTS - Feature #2557 (Resolved): extend osmo-bts-virtual + GSMTAP with voice frame (TCH) supporthttps://osmocom.org/issues/25572017-10-06T14:51:09Zlaforge
<p>In order to have actual voice call user plane between osmo-bts-virt and virt_phy, we need to extend GSMTAP with a way to transport voice codec frames, and implement scheduling of rx/tx of such frames in osmo-bts-virtual.</p> OsmocomBB - Feature #2556 (Resolved): Extend virt_phy and "mobile" with support for voice frameshttps://osmocom.org/issues/25562017-10-06T14:49:40Zlaforge
<p>In order to have proper virtual voice calls, we need to extend virt_phy with support for GSMTAP-encapsulated voice frames. They can be communicated via L1CTL up to "mobile" who can then handle them via mic/speaker or via local loopback, playback from file or any other fashion.</p> OsmocomBB - Feature #2555 (Stalled): script interface to OsmocomBB "mobile"https://osmocom.org/issues/25552017-10-06T14:47:31Zlaforge
<p>The idea here is to have some high-level scripting interface in the OsmocomBB "mobile" program, which can be used to automatically execute certain behavior. This is very useful for automatic testing.</p>
The commands should be very high-level operations, such as
<ul>
<li>perform network search</li>
<li>perform cell (re)selection</li>
<li>perform normal/periodic/attach LU</li>
<li>perform USSD</li>
<li>send MO-SMS</li>
<li>receive MT-SMS</li>
<li>make MO voice call</li>
<li>receive MT voice call</li>
</ul>
<p>In order to make the related scripts easy to write, the script language interface functions should expose blocking semantics. This means the "mobile" stack needs to be run in a thread/process with its usual event-driven osmo_fd architecture, and it needs to exchange primitives with another thread/process that runs the script commands.</p>
<p>As scripting language, I would suggest LUA as it's small to embed. Size does matter, as we likely will want to simultaneously run thousands to tens of thousandsof "mobile" instances on one machine.</p>