https://osmocom.org/https://osmocom.org/favicon.ico?16647414092017-07-29T12:16:39ZOpen Source Mobile CommunicationsOsmoPCU - Bug #2407: N3101 not implemented in OsmoPCUhttps://osmocom.org/issues/2407?journal_id=47492017-07-29T12:16:39Zlaforge
<ul></ul><p>bts->n3101 is actually N3101_MAX, and it is provided via PCU socket from the BTS. So we already have a configurable N3101_MAX, but we have no actual per-USF/TBF counter and related mechanism.</p> OsmoPCU - Bug #2407: N3101 not implemented in OsmoPCUhttps://osmocom.org/issues/2407?journal_id=59812017-10-29T18:45:49Zlaforge
<ul><li><strong>Assignee</strong> deleted (<del><i>laforge</i></del>)</li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul> OsmoPCU - Bug #2407: N3101 not implemented in OsmoPCUhttps://osmocom.org/issues/2407?journal_id=64562017-11-30T10:14:26Zlaforge
<ul><li><strong>Assignee</strong> set to <i>msuraev</i></li><li><strong>Priority</strong> changed from <i>High</i> to <i>Immediate</i></li></ul> OsmoPCU - Bug #2407: N3101 not implemented in OsmoPCUhttps://osmocom.org/issues/2407?journal_id=64612017-11-30T10:50:38Zmsuraev
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul><p>The counter and timer are described in 3GPP TS 44.060 §13.2 and §13.4</p> OsmoPCU - Bug #2407: N3101 not implemented in OsmoPCUhttps://osmocom.org/issues/2407?journal_id=65332017-12-04T11:52:37Zmsuraev
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/2586">Bug #2586</a>: fix timer duration calculations</i> added</li></ul> OsmoPCU - Bug #2407: N3101 not implemented in OsmoPCUhttps://osmocom.org/issues/2407?journal_id=65352017-12-04T12:00:27Zmsuraev
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>10</i></li></ul><p>This change is less trivial than initially anticipated: the problem is with TBF timeout handling in OsmoPCU - there's only single osmo_timer_list which is used for handling of all the timeouts. This in turn means that TBF cannot have 2 concurrent timers running at the same time - the moment we schedule new timer, we lose the information about any pending timer for this TBF. This is both counterintuitive and unnecessary fragile which makes it hard to test and modify.</p>
<p>Related gerrit 5109 has been merged, gerrit 5120 and 5158 are under review. Once it's merged we'll have generic infrastructure in place for handling TBF timers. Follow-up patches will convert remainig timers to use it (including T3169) which would allow use to properly integrate N3101 support.</p> OsmoPCU - Bug #2407: N3101 not implemented in OsmoPCUhttps://osmocom.org/issues/2407?journal_id=65692017-12-05T10:55:22Zmsuraev
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-3 priority-1 priority-lowest closed" href="/issues/2709">Feature #2709</a>: use osmo_fsm for TBF</i> added</li></ul> OsmoPCU - Bug #2407: N3101 not implemented in OsmoPCUhttps://osmocom.org/issues/2407?journal_id=66162017-12-08T13:29:04Zmsuraev
<ul><li><strong>% Done</strong> changed from <i>10</i> to <i>70</i></li></ul><p>Tested successfully with sysmoBTS, under review in gerrit 5158, 5182.</p> OsmoPCU - Bug #2407: N3101 not implemented in OsmoPCUhttps://osmocom.org/issues/2407?journal_id=68632017-12-18T13:06:53Zmsuraev
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Stalled</i></li></ul> OsmoPCU - Bug #2407: N3101 not implemented in OsmoPCUhttps://osmocom.org/issues/2407?journal_id=69172017-12-21T12:26:16Zmsuraev
<ul><li><strong>Status</strong> changed from <i>Stalled</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>70</i> to <i>100</i></li></ul><p>N3101 implementation has been merged, remaining patches to convert timer handling to the same infrastructure which is used for T3169 are under review.</p> OsmoPCU - Bug #2407: N3101 not implemented in OsmoPCUhttps://osmocom.org/issues/2407?journal_id=75092018-02-06T08:27:39Zlaforge
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>