New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UP initiated association setup #78
Comments
Association Setup Procedure Association Update Procedure Association Release Procedure It turns out that the feature release is meaningless |
The current goal: implement UP initiated Assotiation Setup Request. |
Current status: Faced some problems while setting up associations in open5gs kubernetes environment. Problem №1 Problem №2 2.1. Heartbeats. When we get Heartbeat Request, how can we find specific association to that Heartbeat? 2.2. How can UPF understand when it should stop sending Requests? In config we set a service alias to connect to. But when UPF gets Response from SMF, there will be a Node ID of a SMF itself. For example, service name is "open5gs-smf-pfcp", and Node ID is some "10.244.1.24". So the question is: How can UPF know if it should sending Requests to a service? |
✔ Solution for setting up associations in open5gs kubernetes environment. To set open5gs-smf-pfcp service as Headless
|
Good solution!
UPF receives an additional request from SMF (a later timestamp):
|
Both SMF and UPF services set to
|
According to TS 129 244:
6.2.7.3 PFCP Association Update Procedure Initiated by UP Function (see Graceful Release)6.2.8 PFCP Association Release ProcedureThe text was updated successfully, but these errors were encountered: