https://osmocom.org/https://osmocom.org/favicon.ico?16647414092017-10-06T12:27:13ZOpen Source Mobile CommunicationsOsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=55732017-10-06T12:27:13Zlaforge
<ul><li><strong>Subject</strong> changed from <i>OsmoBSCNAT misses AoIP</i> to <i>OsmoBSCNAT misses 3GPP AoIP</i></li></ul> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=60062017-10-29T19:08:31Zlaforge
<ul><li><strong>Target version</strong> set to <i>OSMUX Generalization</i></li></ul> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=96162018-05-30T14:14:20Zlaforge
<ul><li><strong>Tracker</strong> changed from <i>Bug</i> to <i>Feature</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=186332020-06-08T19:07:40Zlaforge
<ul></ul> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=225552021-09-15T10:11:23Zlaforge
<ul><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' disabled> <i>port osmo-bscnat over to libosmo-sigtran, including AoIP support</i> added</li><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' disabled> <i>introduce osmo-mgw into the user plane, rewriting IP/PORT in AoIP related BSSMAP IEs</i> added</li><li><strong>Priority</strong> changed from <i>Low</i> to <i>High</i></li></ul><p>this is becoming more relevant again after 4 years of being on hold...</p>
<p>laforge wrote:</p>
<blockquote>
In order to be able to use it also with 3GPP AoIP, we will probably need to
<ul>
<li>make sure SCCPlite/IPA support in libosmo-sigtran is complete + validated</li>
</ul>
</blockquote>
<p>this part is done, as we support sccplite/ipa from osmo-bsc via that path</p>
<blockquote>
<ul>
<li>port osmo-bscnat over to use libosmo-sigtran as transport interface on both BSC and MSC facing interfaces</li>
<li>run an instance of osmo-mgw next to osmo-bsc_nat for handling RTP and OSMUX media streams to/from BSC and RTP to the (3rd party) MSC</li>
</ul>
</blockquote>
<p>those two parts are missing. This will inevitably end up being a relatively major re-architecture of osmo-bscnat. To reduce the complexity: If there are "odd" use casese in the existing code base, we can certainly review those and drop them in case no known user for them exists anymore.</p>
<p>Inserting osmo-mgw into the user plane (and modifying the control plane IP/Port as per the mgw-allocated connections) will be similar to how osmo-mgw is already used co-located to the BSC, and will be used co-located to BSCNAT (<a class="issue tracker-2 status-3 priority-2 priority-default closed" title="Feature: support hnbgw co-located osmo-mgw for RTP proxying (Resolved)" href="https://osmocom.org/issues/5152">#5152</a>).</p>
<a name="flow-of-events"></a>
<h2 >flow of events<a href="#flow-of-events" class="wiki-anchor">¶</a></h2>
<a name="individual-procedures-related-to-MGW-insertion"></a>
<h2 >individual procedures related to MGW insertion<a href="#individual-procedures-related-to-MGW-insertion" class="wiki-anchor">¶</a></h2>
<a name="BSSMAP-Assignment"></a>
<h3 >BSSMAP Assignment<a href="#BSSMAP-Assignment" class="wiki-anchor">¶</a></h3>
<table>
<tr>
<td>BSCNAT <- MSC</td>
<td>BSSMAP Assignment Req (Containign AoIP TL Addr of CN side)</td>
</tr>
<tr>
<td>BSCNAT <-> MGW</td>
<td>CRCX to wildcard EP (allocate EP); connect towards CN side "remote"</td>
</tr>
<tr>
<td>BSCNAT <-> MGW</td>
<td>CRCX to dedicated EP; obtain BSCNAT-side IP/Port</td>
</tr>
<tr>
<td>BSC <- BSCNAT</td>
<td>BSSMAP Assignment Req (from above, with patched AoIP TL Addr to point to mgw)</td>
</tr>
<tr>
<td>BSC -> BSCNAT</td>
<td>BSSMAP Assignment Compl (contains AoIP TL Addr of RAN side)</td>
</tr>
<tr>
<td>BSCNAT <-> MGW</td>
<td>MDCX to tell mgw of IP/Port of RAN side</td>
</tr>
</table>
<p>The failure case[s] of course will need to release the endpoint on the MGW</p>
<a name="handover-request-from-MSC-to-BSC"></a>
<h3 >handover request from MSC to BSC<a href="#handover-request-from-MSC-to-BSC" class="wiki-anchor">¶</a></h3>
<p>This is an inbound handover into the RAN, processing should be similar to Assignment Req above.</p>
<a name="INTERNAL-HANDOVER-REQUIRED"></a>
<h3 >INTERNAL HANDOVER REQUIRED<a href="#INTERNAL-HANDOVER-REQUIRED" class="wiki-anchor">¶</a></h3>
<p>This is sent by the BSC to the MSC in case the codec/codec-config is changed as part of a BSS-internal handover. We need to handle related signaling with MGW and MSC.</p>
<a name="hiding-intra-BSCNAT-handover-from-MSC"></a>
<h2 >hiding intra-BSCNAT handover from MSC<a href="#hiding-intra-BSCNAT-handover-from-MSC" class="wiki-anchor">¶</a></h2>
<p>If there are inter-BSC hand-overs behind one BSC-NAT, it would probably confuse the MSC quite a bit if they were brought up to the MSC as inter-BSC HO, while the BSCs view is that they are infact intra-BSC (as the BSCNAT appears as one BSC to it).</p>
<p>Hence, we will need to handle inter-BSC handovers within one BSC-NAT internally, and only bring those to the MSCs attention which actually are beyond the service area of the BSC-NAT.</p> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=225562021-09-15T10:11:43Zlaforge
<ul><li><strong>Assignee</strong> set to <i>4368</i></li></ul> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=225572021-09-15T10:11:57Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-3 priority-2 priority-default closed" href="/issues/5152">Feature #5152</a>: support hnbgw co-located osmo-mgw for RTP proxying</i> added</li></ul> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=228332021-10-26T17:15:23Zlaforge
<ul><li><b>Checklist item</b> changed from <i>port osmo-bscnat over to libosmo-sigtran, including AoIP support</i> to <i>rewrite osmo-bscnat using libosmo-sigtran, including AoIP support</i></li><li><strong>Assignee</strong> changed from <i>4368</i> to <i>osmith</i></li></ul><p>as discussed today, <a class="user active" href="https://osmocom.org/users/301771">osmith</a> and <a class="user active" href="https://osmocom.org/users/52">Hoernchen</a> will be working at this</p> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=230692021-11-22T08:45:17Zlaforge
<ul></ul><p>See <a class="wiki-page" href="https://osmocom.org/projects/osmo-bscnat/wiki/AoIP_OsmoBSCNAT">AoIP_OsmoBSCNAT</a> where we gather a related functional specification.</p> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=230702021-11-22T08:51:14Zlaforge
<ul><li><b>Checklist item</b> changed from <i>rewrite osmo-bscnat using libosmo-sigtran, including AoIP support</i> to <i>rewrite osmo-bscnat using libosmo-sigtran (for AoIP support)</i></li><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' disabled> <i>create specification here in the wiki</i> added</li><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' disabled> <i>create ladder diagrams for handling of key prcedures</i> added</li><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' disabled> <i>create TTCN3 test suite covering key procedures</i> added</li></ul> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=232472021-12-16T13:31:01Zlaforge
<ul></ul><p>what is the status here? This should have been worked on for almost two months, but status is still 'new' and completion at 0%?</p> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=232482021-12-16T16:46:34Zosmith
<ul><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' checked disabled> <i>create specification here in the wiki</i> set to Done</li><li><b>Checklist item</b> <input type='checkbox' class='checklist-checkbox' checked disabled> <i>create ladder diagrams for handling of key prcedures</i> set to Done</li><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>10</i></li></ul><p>Sorry, I've only briefly updated a related SYS issue and not this one.</p>
<blockquote>
<p>create specification here in the wiki</p>
</blockquote>
<p>Looks like that's done with what <a class="user active" href="https://osmocom.org/users/7">laforge</a> added here, so marking as complete (or should there be more? in that case, please correct me):<br /><a class="external" href="https://osmocom.org/projects/osmo-bscnat/wiki/AoIP_OsmoBSCNAT">https://osmocom.org/projects/osmo-bscnat/wiki/AoIP_OsmoBSCNAT</a></p>
<blockquote>
<p>create ladder diagrams for handling of key prcedures</p>
</blockquote>
<p>Done for calls, which is the most important one:<br /><a class="external" href="https://osmocom.org/projects/osmo-bscnat/wiki/Ladder_diagrams_for_key_procedures">https://osmocom.org/projects/osmo-bscnat/wiki/Ladder_diagrams_for_key_procedures</a></p>
<p>(Again, if there should be more to complete this checkbox, please correct me.)</p>
<blockquote>
<p>create TTCN3 test suite covering key procedures</p>
</blockquote>
<p><a class="user active" href="https://osmocom.org/users/52">Hoernchen</a> is on this, since I had started with the implementation part he suggested that he takes over the testsuite.</p>
<blockquote>
<p>rewrite osmo-bscnat using libosmo-sigtran (for AoIP support)</p>
</blockquote>
<p>I've started this, WIP branch is in osmith/wip of osmo-bsc-nat.git. This needs some more work, but I've planned to to submit first patches to gerrit tomorrow.</p>
<p>EDIT: urgent tasks came up, but I should be able to submit first patches by the start of next week.</p> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=232502021-12-16T16:49:47Zosmith
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-2 priority-default closed" href="/issues/5359">Bug #5359</a>: add osmo-bsc-nat.git to git.osmocom.org</i> added</li></ul> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=232912021-12-21T19:50:44Zosmith
<ul></ul><p>First patches: <a class="external" href="https://gerrit.osmocom.org/q/topic:bscnat">https://gerrit.osmocom.org/q/topic:bscnat</a></p> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=235542022-01-31T17:02:45Zosmith
<ul><li><strong>% Done</strong> changed from <i>10</i> to <i>20</i></li></ul><p>Submitted new patches. Very basic forwarding of messages between osmo-bsc and osmo-msc is now implemented (with point codes for MSC and BSC in the config, not saving/using a mapping yet, and without modifying the messages). Sending RESET and RESET ACK works, OsmoBSC reports that the connection to MSC is established.</p> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=236692022-02-18T13:38:21Zosmith
<ul></ul><p>I've implemented basic forwarding of Connection Request, Connection Confirm, Data Form and Released SCCP messages. This is still assuming that there is just one BSC, one MSC, so the same connection ID is used in RAN and CN for now. With the latest patches it's possible to perform a call between two MS in this structure:</p>
<pre>
MS1 --.
BTS --- BSC --- BSCNAT --- MSC
MS2 --'
</pre>
<p>Patches:<br /><a class="external" href="https://gerrit.osmocom.org/q/topic:bscnat">https://gerrit.osmocom.org/q/topic:bscnat</a></p>
<p>Next I will configure a manual test environment that includes two BSC and two BTS, and extend the BSCNAT accordingly to make message forwarding work.</p>
<pre>
MS1 --- BTS 1 --- BSC 1 --.
BSCNAT --- MSC
MS2 --- BTS 2 --- BSC 2 --'
</pre> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=237682022-03-10T13:57:40Zosmith
<ul><li><strong>% Done</strong> changed from <i>20</i> to <i>30</i></li></ul><p>I've submitted patches to map connections between MSC and the BSCs. With them it's possible to do a successful Location Updating procedure between MS2 and MSC in the above network structure.</p>
<p>Patches are again here:<br /><a class="external" href="https://gerrit.osmocom.org/q/topic:bscnat">https://gerrit.osmocom.org/q/topic:bscnat</a></p>
<p>Next up is making more of the message forwarding work, until calls between MS1 and MS2 work.</p> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=238862022-04-08T16:57:57Zosmith
<ul><li><strong>% Done</strong> changed from <i>30</i> to <i>40</i></li></ul><p>With latest patches: calls work between MS1 and MS2 in the following network structure, with RTP traffic going through MGW-BSCNAT:</p>
<pre>
MS1 --- BTS1 --- BSC1 --.
| | BSCNAT ----------- MSC
| | | | |
'-- MGW-BSC1 --|-- MGW-BSCNAT --- MGW-MSC
| |
MS2 --- BTS2 --- BSC2 --' |
| | |
'-- MGW-BSC2 ------'
</pre> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=239112022-04-11T22:52:01Zneelsnhofmeyr@sysmocom.de
<ul></ul><p>(btw, our redmines support inline dot graphs, see for example <br /><a class="external" href="https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_In_The_Box/edit?section=4">https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_In_The_Box/edit?section=4</a><br />for me it turns out to be faster than ascii art)</p> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=241612022-06-01T10:39:32Zosmith
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-1 priority-4 priority-high2" href="/issues/5574">Bug #5574</a>: OsmoBSCNAT testsuite running in jenkins</i> added</li></ul> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=250882022-10-12T13:15:18Zosmith
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Stalled</i></li></ul> OsmoBSCNAT - Feature #2545: OsmoBSCNAT misses 3GPP AoIPhttps://osmocom.org/issues/2545?journal_id=250892022-10-12T13:15:56Zosmith
<ul><li><strong>Priority</strong> changed from <i>High</i> to <i>Low</i></li></ul>