Questions on OSMOCOM & real nodes integration
Hi We set up a full Osmocom platform, with an Ettus USRP for SDR. All works well. Congratulations to Osmocom developers ! But now we want to use "real" nodes concerning MSC, MGW, HLR, SGSN & GGSN. Do you think it is possible ? Concerning the BSC-MSC association, do we need to use an SG (osmo-stp) ? or could we establish a Point To Point BSC-MSC ? SUA ? Concerning MGW, is there a way to use our MGW ? At this time, with Osmocom corposants, we can see RTP traffic between BTS-TRX and MGW, and some MGCP traffic between (BSC - local MGW) and MGW, and some MGCP traffic between osmo-MGW and osmo-MSC. Is there a way to have a "more standard" architecture: no traffic between BTS and MGW, and MGW controlled by MSC ? Do we have to more study TRAU, AoIP ? Concerning the Gb, do you think that it 'll work if we configure the Gb on a real SGSN connected to the osmo-pcu, hosted on the osmo-bts-trx? Many thanks in advance, Best regards Jean-Marc Orange Restricted
Hi Jean-Marc, On 11/29/23 16:33, jheyrendt.ext@orange.com wrote:
Hi
We set up a full Osmocom platform, with an Ettus USRP for SDR. All works well. Congratulations to Osmocom developers !
But now we want to use "real" nodes concerning MSC, MGW, HLR, SGSN & GGSN.
Not sure what do you mean with "real" here. Have I been living in some imaginary world until now when using osmocom software? Do you perhaps mean you want to interop with nodes from other vendors perhaps? If that's your question, yes it's possible, there are known setups of osmocom software running against Quortus, Ericsson, Huawei, etc. CNs.
Do you think it is possible ?
What exactly?
Concerning the BSC-MSC association, do we need to use an SG (osmo-stp) ? or could we establish a Point To Point BSC-MSC ? SUA ?
We don't yet support IPSP in osmocom, so you need to configure your node and the peer as SG or ASP.
Concerning MGW, is there a way to use our MGW ? At this time, with Osmocom corposants, we can see RTP traffic between BTS-TRX and MGW, and some MGCP traffic between (BSC - local MGW) and MGW, and some MGCP traffic between osmo-MGW and osmo-MSC. Is there a way to have a "more standard" architecture: no traffic between BTS and MGW, and MGW controlled by MSC ? Do we have to more study TRAU, AoIP ?
Not sure what you mean by "more standard architecture here. I believe the architecture we use is a generally standard AoIP setup. Only thing that resembles what you mention seems to be an SCCPlite setup instead of AoIP? We do support SCCPlite in osmo-bsc too, but we still use an osmo-mgw colocated with osmo-bsc there. In any case, the MSC co-located MGW can be whatever MGW the MSC chooses to use. We didn't test any other MGW implementation using MGCP against our osmo-bsc/osmo-msc (does it exist?) The only one I know has been tested is iirc a Quortus MSC in SCCPlite mode sending MGCP to our osmo-bsc, which is then forwarded to its co-located osmo-mgw.
Concerning the Gb, do you think that it 'll work if we configure the Gb on a real SGSN connected to the osmo-pcu, hosted on the osmo-bts-trx?
Again, if by "real" you mean some SGSN from another vendor (eg. Ericsson), then yes, there are known cases of working setups AFAIR. Regards, Pau -- - Pau Espin Pedrol <pespin@sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte
On Wed, Nov 29, 2023 at 03:33:22PM +0000, jheyrendt.ext@orange.com wrote:
Concerning the BSC-MSC association, do we need to use an SG (osmo-stp) ? or could we establish a Point To Point BSC-MSC ? SUA ?
There is the SCCPlite variant of the A-interface, which osmocom supports, but it is not in any active use that I know of. See - 4.2.2.1 BSSAP/SCCPlite - 5.4.1.2 Configure SCCPlite in https://ftp.osmocom.org/docs/osmo-bsc/master/osmobsc-usermanual.pdf I think you want to use osmo-stp when possible.
Concerning MGW, is there a way to use our MGW ? At this time, with Osmocom corposants, we can see RTP traffic between BTS-TRX and MGW, and some MGCP traffic between (BSC - local MGW) and MGW, and some MGCP traffic between osmo-MGW and osmo-MSC. Is there a way to have a "more standard" architecture: no traffic between BTS and MGW, and MGW controlled by MSC ? Do we have to more study TRAU, AoIP ?
Maybe familiarize with this chart: https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_In... There is lateral MGCP between BSC->MGW and MSC->MGW, and RTP from BTS via the two MGW to the other call leg.
Concerning the Gb, do you think that it 'll work if we configure the Gb on a real SGSN connected to the osmo-pcu, hosted on the osmo-bts-trx?
it may work when you do the integration right =) It would help if you were more specific, instead of "our MGW", "real SGSN". ~N
Hi Many many thanks to you, Pau & Neels Sorry for my unclear questions. The fact is we want to test to integrate Osmocom with some Ericsson nodes: MSC, MGW, SGSN If we understand well, concerning the link between BSC and MSC, an OSMO-STP is the best solution (link SCCP M3UA / declaration of AS, ASP, RK, CP, ...) Concerning the Gb, the link with the SGSN may work. Perfect ! Concerning the CP and UP of the MGW Ericsson and MSC Ericsson, sorry for my misunderstanding, what do you advice us ? if we look to the schema, do we need an Osmocom-mgw ? We presume Yes If Yes, Is it possible to just have one Osmocom-mgw hosted on the Osmocom-bsc ? In this case, There will be RTP traffic between Osmocom-bts and Osmocom-mgw (hosted on Osmocom-bsc) And there will be RTP traffic between Osmocom-mgw (hosted on Osmocom-bsc) and mgw Ericsson. And there will be MGCP traffic between Osmocom-mgw (hosted on Osmocom-bsc) and Osmocom-bsc. Best regards Have a nice day Jean-Marc
Hi Jean-Marc, On 11/30/23 10:17, jheyrendt.ext@orange.com wrote:
Hi Many many thanks to you, Pau & Neels
Sorry for my unclear questions.
The fact is we want to test to integrate Osmocom with some Ericsson nodes: MSC, MGW, SGSN
It should be indeed possible to interop with them, it's been done already.
If we understand well, concerning the link between BSC and MSC, an OSMO-STP is the best solution (link SCCP M3UA / declaration of AS, ASP, RK, CP, ...)
That's the usual approach yes. Whatever should be fine as long as the Ericsson peer is configured as ASP or SG.
Concerning the CP and UP of the MGW Ericsson and MSC Ericsson, sorry for my misunderstanding, what do you advice us ? if we look to the schema, do we need an Osmocom-mgw ? We presume Yes If Yes, Is it possible to just have one Osmocom-mgw hosted on the Osmocom-bsc ?
You definetly need an osmo-mgw co-located/used by osmo-bsc.
In this case, There will be RTP traffic between Osmocom-bts and Osmocom-mgw (hosted on Osmocom-bsc) And there will be RTP traffic between Osmocom-mgw (hosted on Osmocom-bsc) and mgw Ericsson. And there will be MGCP traffic between Osmocom-mgw (hosted on Osmocom-bsc) and Osmocom-bsc.
Correct. In case you are interested, let me remind you that "sysmocom - systems for mobile communications GmbH" (https://sysmocom.de) offers commercial support contracts, in case you require further support for your specific needs or help with integrating/interoperating against other vendors or implementing/fixing any features. Regards, Pau -- - Pau Espin Pedrol <pespin@sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte
On Thu, Nov 30, 2023 at 09:17:58AM +0000, jheyrendt.ext@orange.com wrote:
if we look to the schema, do we need an Osmocom-mgw ? We presume Yes
OsmoBSC requires a co-located MGW. So far all of our users that we know of use osmo-mgw for that. The MGCP protocol is standardized, so it would be interesting to interface with a third party MGW and see what happens.
If Yes, Is it possible to just have one Osmocom-mgw hosted on the Osmocom-bsc ?
Yes of course
In this case, There will be RTP traffic between Osmocom-bts and Osmocom-mgw (hosted on Osmocom-bsc) And there will be RTP traffic between Osmocom-mgw (hosted on Osmocom-bsc) and mgw Ericsson. And there will be MGCP traffic between Osmocom-mgw (hosted on Osmocom-bsc) and Osmocom-bsc.
Yes, the reason why Osmocom is divided in so many components is that you may interface with third party components at "any" edge. The scenario you describe above is what some of our users do: OsmoBSC is responsible for the BSS "sphere", including the BSC co-located MGW. OsmoBSC talks 3GPP standardized A-interface towards an Ericsson MSC. OsmoBSC does not interact with or even needs to know anything about the MSC's MGW setup, it only sends the call leg's RTP to the RTP address:port that the MSC indicated in the BSSAP Assignment Command. It does not matter what component/what brand of MGW that RTP address:port belongs to, as far as the BSC is concerned. Of course the hard part is configuring all the details correctly. Sometimes we also need to resolve a customer's CN's specific peculiarities by implementing new features, and occasionally we find and fix bugs in Osmocom that we did not know about yet. So if you have problems with integration that you need assistance with, one option is the dedicated commercial support that is available for Osmocom, for example from info@sysmocom.de (my employer). You may also get assistance here on this mailing list, where individual community members invest their own free time free of charge. ~N -- - Neels Hofmeyr <nhofmeyr@sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschäftsführer / Managing Directors: Harald Welte
Dear all Many thanks again for your help. We try to configure ourselves Osmocom & Ericsson nodes, and we'll ask you some assistance if needed. Best regards Jean-Marc HEYRENDT Orange Labs -----Message d'origine----- De : Neels Hofmeyr <nhofmeyr@sysmocom.de> Envoyé : jeudi 30 novembre 2023 15:46 À : HEYRENDT Jean Marc Ext DSCS/DSEC <jheyrendt.ext@orange.com> Cc : openbsc@lists.osmocom.org Objet : Re: Questions on OSMOCOM & real nodes integration ---------------------------------------------------------------------------- -------------------------------- CAUTION : this email originated from outside of the organisation. Do not click links, open attachments or answer unless you recognize the sender and know the content is safe. ATTENTION : Ce courriel provient de l'extérieur de l'organisation. Ne cliquez pas sur les liens, n'ouvrez pas les pièces jointes, ne répondez pas si vous ne reconnaissez pas l'expéditeur et si vous ne savez pas si le contenu est sûr. ---------------------------------------------------------------------------- -------------------------------- On Thu, Nov 30, 2023 at 09:17:58AM +0000, jheyrendt.ext@orange.com wrote:
if we look to the schema, do we need an Osmocom-mgw ? We presume Yes
OsmoBSC requires a co-located MGW. So far all of our users that we know of use osmo-mgw for that. The MGCP protocol is standardized, so it would be interesting to interface with a third party MGW and see what happens.
If Yes, Is it possible to just have one Osmocom-mgw hosted on the Osmocom-bsc ?
Yes of course
In this case, There will be RTP traffic between Osmocom-bts and Osmocom-mgw (hosted on Osmocom-bsc) And there will be RTP traffic between Osmocom-mgw (hosted on Osmocom-bsc) and mgw Ericsson. And there will be MGCP traffic between Osmocom-mgw (hosted on Osmocom-bsc) and Osmocom-bsc.
Yes, the reason why Osmocom is divided in so many components is that you may interface with third party components at "any" edge. The scenario you describe above is what some of our users do: OsmoBSC is responsible for the BSS "sphere", including the BSC co-located MGW. OsmoBSC talks 3GPP standardized A-interface towards an Ericsson MSC. OsmoBSC does not interact with or even needs to know anything about the MSC's MGW setup, it only sends the call leg's RTP to the RTP address:port that the MSC indicated in the BSSAP Assignment Command. It does not matter what component/what brand of MGW that RTP address:port belongs to, as far as the BSC is concerned. Of course the hard part is configuring all the details correctly. Sometimes we also need to resolve a customer's CN's specific peculiarities by implementing new features, and occasionally we find and fix bugs in Osmocom that we did not know about yet. So if you have problems with integration that you need assistance with, one option is the dedicated commercial support that is available for Osmocom, for example from info@sysmocom.de (my employer). You may also get assistance here on this mailing list, where individual community members invest their own free time free of charge. ~N -- - Neels Hofmeyr <nhofmeyr@sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschäftsführer / Managing Directors: Harald Welte
participants (3)
-
jheyrendt.ext＠orange.com -
Neels Hofmeyr -
Pau Espin Pedrol