https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092018-09-09T16:33:18ZOpen Source Mobile CommunicationsOsmoBSC - Feature #3536: BSC: support for repeated scheduling of SMSCB messageshttps://projects.osmocom.org/issues/3536?journal_id=112102018-09-09T16:33:18Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-3 priority-3 priority-high3 closed behind-schedule" href="/issues/3537">Feature #3537</a>: BSC support for CBSP (cell broadcast service protocol)</i> added</li></ul> OsmoBSC - Feature #3536: BSC: support for repeated scheduling of SMSCB messageshttps://projects.osmocom.org/issues/3536?journal_id=112132018-09-09T16:33:46Zlaforge
<ul><li><strong>Tags</strong> set to <i>SMSCB</i></li></ul> OsmoBSC - Feature #3536: BSC: support for repeated scheduling of SMSCB messageshttps://projects.osmocom.org/issues/3536?journal_id=142082019-05-03T19:12:48Zlaforge
<ul><li><strong>Assignee</strong> set to <i>laforge</i></li></ul> OsmoBSC - Feature #3536: BSC: support for repeated scheduling of SMSCB messageshttps://projects.osmocom.org/issues/3536?journal_id=148322019-06-15T16:33:09Zlaforge
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>60</i></li></ul>the bulk of the work on the scheduler has been implemented together with the CBSP protocol handing in the <code>laforge/cbsp</code> branch of osmo-bsc.git. It is currently untested, but should do the following things:
<ul>
<li>handling of WRITE_REPLACE, KILL and RESET procedures via CBSP from the CBC</li>
<li>building a scheduler data structure from the pages of the active SMSCB, taking into account their individual broadcast periods/intervals</li>
<li>removing SMSCB from the scheduler once the requested number of broadcasts has completed</li>
<li>providing a function to pull one SMSCB page from the scheduler</li>
<li>VTY configuration for the CBSP link</li>
<li>CBSP TCP client and server role</li>
</ul>
<p>The scheduler runs separate for each BTS, and each BTS has separate scheduler instances for BASIC and EXTENDED CBCH</p>
These parts are missing:
<ul>
<li>actually sending the 'pulled' SMSCB pages to the BTS for actual transmission</li>
<li>CBSP LOAD QUERY</li>
<li>CBSP MSG STATUS QUERY</li>
<li>tests, tests, tests</li>
</ul> OsmoBSC - Feature #3536: BSC: support for repeated scheduling of SMSCB messageshttps://projects.osmocom.org/issues/3536?journal_id=152932019-07-18T06:00:29Zlaforge
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Urgent</i></li></ul> OsmoBSC - Feature #3536: BSC: support for repeated scheduling of SMSCB messageshttps://projects.osmocom.org/issues/3536?journal_id=157762019-09-02T09:19:34Zlaforge
<ul><li><strong>% Done</strong> changed from <i>60</i> to <i>80</i></li></ul><p>lots of work has been done on this, see <a class="external" href="https://gerrit.osmocom.org/#/c/osmo-bsc/+/15373/">https://gerrit.osmocom.org/#/c/osmo-bsc/+/15373/</a> for the actual code, and <a class="external" href="https://gerrit.osmocom.org/15374">https://gerrit.osmocom.org/15374</a>, <a class="external" href="https://gerrit.osmocom.org/15375">https://gerrit.osmocom.org/15375</a> and <a class="external" href="https://gerrit.osmocom.org/15376">https://gerrit.osmocom.org/15376</a> for related tests.</p> OsmoBSC - Feature #3536: BSC: support for repeated scheduling of SMSCB messageshttps://projects.osmocom.org/issues/3536?journal_id=158792019-09-05T17:49:59Zlaforge
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>80</i> to <i>100</i></li></ul><p>all patches merged</p>