https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092022-05-06T12:34:09ZOpen Source Mobile CommunicationsOsmoBSC - Bug #5552: no overall limit of paging requests at BSC levelhttps://projects.osmocom.org/issues/5552?journal_id=240422022-05-06T12:34:09Zpespin
<ul></ul><p>It may make sense, once reached the threshold of the maximum amount of allowed requests, to try to drop one of the in-retransmission-state requests in the queue, and accept the new one.</p> OsmoBSC - Bug #5552: no overall limit of paging requests at BSC levelhttps://projects.osmocom.org/issues/5552?journal_id=240472022-05-06T12:52:55Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/5553">Bug #5553</a>: dynamic T3113 has no reasonable upper bound</i> added</li></ul> OsmoBSC - Bug #5552: no overall limit of paging requests at BSC levelhttps://projects.osmocom.org/issues/5552?journal_id=241862022-06-15T12:43:17Zpespin
<ul></ul><p>Maximum paging length is already implemented since the last bunch of osmo-bsc paging improvements. See paging.c _paging_request():<br /><pre>
#define MAX_TX_DELAY_TIME_SEC 60
[...]
/* don't try to queue more requests than we can realistically handle within MAX_TX_DELAY_TIME_SEC seconds */
if (paging_pending_requests_nr(bts) > paging_estimate_available_slots(bts, MAX_TX_DELAY_TIME_SEC)) {
rate_ctr_inc(rate_ctr_group_get_ctr(bts->bts_ctrs, BTS_CTR_PAGING_OVERLOAD));
return -ENOSPC;
}
</pre></p>
Some stuff we may want to improve here:
<ul>
<li>Make "MAX_TX_DELAY_TIME_SEC 60" configurable through VTY. This may be useful to configure it so that it matches some paging timeout config at the MSC?</li>
<li>When the queue is full, instead of dropping it, remove the first non-initial (retrans) entry from the list, then add this new paging req.</li>
</ul> OsmoBSC - Bug #5552: no overall limit of paging requests at BSC levelhttps://projects.osmocom.org/issues/5552?journal_id=256422022-11-28T12:43:25Zpespin
<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>50</i></li></ul><p>pespin wrote in <a href="#note-3">#note-3</a>:</p>
<blockquote>
<ul>
<li>Make "MAX_TX_DELAY_TIME_SEC 60" configurable through VTY. This may be useful to configure it so that it matches some paging timeout config at the MSC?</li>
</ul>
</blockquote>
<p><a class="external" href="https://gerrit.osmocom.org/c/osmo-bsc/+/30345">https://gerrit.osmocom.org/c/osmo-bsc/+/30345</a></p> OsmoBSC - Bug #5552: no overall limit of paging requests at BSC levelhttps://projects.osmocom.org/issues/5552?journal_id=256682022-11-29T15:29:35Zpespin
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>50</i> to <i>90</i></li></ul><p>pespin wrote in <a href="#note-3">#note-3</a>:</p>
<blockquote>
<ul>
<li>When the queue is full, instead of dropping it, remove the first non-initial (retrans) entry from the list, then add this new paging req.</li>
</ul>
</blockquote>
<p>Done here: <a class="external" href="https://gerrit.osmocom.org/c/osmo-bsc/+/30347">https://gerrit.osmocom.org/c/osmo-bsc/+/30347</a></p>
<p>Ticket can be closed once merged.</p> OsmoBSC - Bug #5552: no overall limit of paging requests at BSC levelhttps://projects.osmocom.org/issues/5552?journal_id=256932022-12-01T14:22:06Zpespin
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>90</i> to <i>100</i></li></ul><p>Merged, closing.</p>