Change the default behaviour on AMFConfigurationUpdate when TNLAssoci… #631
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
HI,
I would like to propose a change in the default behaviour for handling AMFConfigurationUpdate message.
Indeed, for some 5G platforms, AMF sends to the gNB an AMFConfgurationUpdate message providing additional information. And because it can be quite complex to handle it in a full context (I mean to update all IP addresses used in the connection), UERANSIM currently releases the connection in such situation.
The proposed code let UERANSIM continues providing the expected response to the AMF with a warning message in the console. It allows to successfully use UERANSIM with such platform.
No issue has been detected with this patch but I know it is a little bit unusual and with significant risk if the AMFConfigurationUpdate involves further actions.
Do not hesitate to reject that pull request according to your position on this proposition ;o)