Open dark-astra opened 3 weeks ago
HI @dark-astra . Thank you for trying out SD-Core/Aether-onRamp.
"I see you are saving the context in MongoDB, but I wanted to know, is the statelessness procedural, where after the registration procedure, the context is saved or is it saved after each message exchange with RAN all along the the registration procedure, so that the registration, need not be started from the beginning if it fails, somewhere in between ?"
Details are stored after complete registration procedure.
@thakurajayL Deleting the AMF pod, makes all the consequent UE registrations fail. The gnbSim is not able to connect to the newer AMF after the older AMF is deleted. Shouldn't the gnbSim able to process the subsequent UE registrations with the new AMF pod ?
Good question. There are multiple things involved here,
@thakurajayL, Thanks for the detailed response.
Enabling the SCTP load balancer using the configuration has resolved the issue where the new AMF was not handling subsequent requests. However, I'm still encountering a problem: when the old AMF fails, a few UEs (around 3-4) experience timeouts or failures before the new AMF starts registering them again.
Even though I'm running the UE registrations sequentially, I'm puzzled as to why there are multiple timeouts or failures before the new AMF takes over.
Is there native support at the gnbsim itself, for retrying of service request ?
The 5G UE Registration call flow consists of multiple exchange of Uplink and Downlink Transport Messages. So if the AMF pod fails at some stage between these message exchanges, will the UE registration fail and restart a new registration request with the new AMF or can the UE resume the registration at the very step where it failed, with the new AMF ?
I see you are saving the context in MongoDB, but I wanted to know, is the statelessness procedural, where after the registration procedure, the context is saved or is it saved after each message exchange with RAN all along the the registration procedure, so that the registration, need not be started from the beginning if it fails, somewhere in between ?
I did a simple experiment to test this:
I installed the SDCore using Aether OnRamp and configured the gnbsim to run REGISTRATION procedure for 10 UEs. So when the gnbsim starts sending request, I delete the AMF pod, and this cause the registrations to fail.
My gnbsim-default.yaml looks like the following: