<div dir="ltr">This was discussed in detail at commcon. Have a look at
<a href="https://www.youtube.com/watch?v=4HdGuCFQYMs&list=PLvNS4EBAxmJKz6E6PLCqBq0eB-KKB6HR0&index=21&t=0s">https://www.youtube.com/watch?v=4HdGuCFQYMs&list=PLvNS4EBAxmJKz6E6PLCqBq0eB-KKB6HR0&index=21&t=0s</a><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Oct 21, 2019 at 12:51 PM Dario Renaud <<a href="mailto:dario.renaud@gmail.com">dario.renaud@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">Hello Javier,</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">Well, if we
take a step back to goals, I would like first to point that going Full MVNO
might not be the best solution for us (roaming alone seems like quite a hassle,
not to mention handsets management). </span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">My focus
here is narrower, as I am mostly trying here to assert what the possibilities
for the core are, and if there are reasonable alternatives to the fully
integrated solutions of the big providers. </span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">That being
said, I am not sure how our specific goals here would impact much the architecture:
aren’t there a lot of constraints due to the 3GPP requirements? It seems to leave little room for creativity.</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">To provide
a bit of context and answer you:</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">We are
historically providing solutions on fixed networks, with a strong bend toward business
end-users. We are also used to have a lot of control over our architecture,
most of our services running over open-source and/or in-house solutions.</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">Being able
to provide our services on mobile accesses is now a necessity. For this we
already are light MVNO, using two different MNOs. Thanks to forced routing, it
mostly does the job regarding voice. Data could be managed also. SMS is proving
trickier.</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">But each
MNO have their own products set: building offers that would work on both is
tedious and necessitate compromises that tend to make our marketing people
unhappy. Not to talk about supporting two provisioning chains, two SIMs supply
chains, etc… These problems would only get worse if we add other MNOs to the
mix. </span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">We are also
stuck with the roadmap of the MNOs (VoLTE and VoWifi are but distant “maybe
later” possibilities).</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">So, in one
word, this is about autonomy. And its cost.</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">Regards,</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">Dario
Renaud</span></p></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le ven. 18 oct. 2019 à 17:44, Javier J <<a href="mailto:javier@advancedmachines.us" target="_blank">javier@advancedmachines.us</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">This is interesting but so many variables to unpack to determin what the right solution is. What are the main goals of your org? What exact pain points are you trying to fix?<div dir="auto"><br></div><div dir="auto"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Oct 16, 2019, 8:28 AM Dario Renaud <<a href="mailto:dario.renaud@gmail.com" target="_blank">dario.renaud@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">Hello,</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">At my day
job, we are considering going Full MVNO. Which means building a mobile core
network.</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">I was
wondering if some of you would have feedback or advices on the solutions currently
available?</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">We would
like to avoid the big providers (Ericsson & such).<br>
Ideally, something opensource, or, if proprietary, a company maybe willing to
license access to the code (one can dream).</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">There seems
to be a lot of bits and pieces available out there, with a mix of full, fullish
or partial solutions. This makes for quite the puzzle.</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">Among the
ones I found most interesting:</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">nextEPC,
covering, well, the EPC… (<a href="https://github.com/nextepc/nextepc" style="color:rgb(5,99,193)" rel="noreferrer" target="_blank">https://github.com/nextepc/nextepc</a>).
It looks like the more active open EPC implementation out there.</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">And it seems
that Yate people have a commercial product covering basically everything needed
(<a href="https://yatebts.com/solutions_and_technology/mobile_virtual_network_operator/" style="color:rgb(5,99,193)" rel="noreferrer" target="_blank">https://yatebts.com/solutions_and_technology/mobile_virtual_network_operator/</a>).
</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">What do you
think?</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">Regards</span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span lang="EN-US">Dario Renaud</span></p></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>