S6a peer preference based on roaming status #37
Merged
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.
Accidentally confused the branch number with issue 205.
These changes are for issue 206.
When a roaming UE is seen by the MME (via MNC and MCC, same as in open5gs#205) the diameter client will give a much larger preference to peers that support relay.
When a non-roaming UE is seen by the MME (via MNC and MCC, same as in open5gs#205) the diameter client will give a much larger preference to peers that support s6a functionality.
Note that preference functionality has been added to only the AIR, ULR, and PUR diameter messages on the S6A interface.