<div dir="ltr"><div dir="ltr"><span class="gmail-im" style="color:rgb(80,0,80)"><div dir="ltr">On Tue, Dec 5, 2023 at 11:23 AM Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>> wrote:<br></div></span><div class="gmail_quote"><span class="gmail-im" style="color:rgb(80,0,80)"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u><div><font face="monospace">I did some reading about this NSA vs SA and as I understand, this will not impact the actual functionalities we need, but more the logic and interfacing with other components (HSS or PC(R)F).<br><br></font></div></blockquote><div><br></div></span><div>Maybe I gave the impression it is a problem of formal requirements (and that's not), actually in my view it is a problem of (open source) implementations.</div><div><br>One of the problems is that in 5G (let's call it NR, NewRadio), Open5GS implemented a different interface in PCF vs the one implemented in PCRF.</div><div><br></div><div>So, while in LTE (4G) Open5GS uses Diameter for interfacing, in NR (5G) it has only implemented HTTP2.</div><div>Then, we need HTTP2 and NR specific logic for implementing VoNR (Voice over New Radio) using Open5GS as NR core.</div><span class="gmail-im" style="color:rgb(80,0,80)"><div><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><font face="monospace">More or less, from OpenSIPS perspective, we need the same set of features, but the scripting will differ (as logic and DIAMETER messages).<br><br></font></div></blockquote><div><br></div></span><div>Yep, definitely: if all specs would have been implemented, VoNR would have *both* diameter and http2, so, it would be a superset of VoLTE with added http2 and some more things, and you can decide to interface it from IMS (that's us) via diameter (like in VoLTE) or via HTTP2 (VoNR specific). But Open5GS does not implement diameter in NR.</div><div><br></div><div>Yes, as Carlsten said, we may implement a network function of a translator between diameter and http2, no idea if that is easier than implementing http2 into (x)CSCF.</div><div>Maybe (just maybe) with kubernetes and all these deployment environments mainly tailored to web, they will heavily push with http2 for additional services.</div><div> </div><div>Or maybe in near future Open5GS will implement diameter in NR.</div><div><br></div><div>Without Open5GS interfacing us (IMS) we'll not be able to actually test real implementation with actual 5G phones (and devil is always in details, simulations are nice, but...)</div><font color="#888888"><div><br></div><div>-giovanni</div><div><span style="color:rgb(34,34,34)">--</span><br></div></font></div></div><div dir="ltr" class="gmail_signature">Sincerely,<br><br>Giovanni Maruzzelli<br>OpenTelecom.IT<br>cell: +39 347 266 56 18<br><br></div></div>