Skip to content
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

feat: request UPF to allocate F-TEID #334

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

gruyaume
Copy link
Contributor

@gruyaume gruyaume commented Oct 16, 2024

Description

As of 3GPP release 16, the F-TEID should be allocated by the UPF (and not by the SMF). Here we make the necessary changes for the SMF to request the UPF to allocate the F-TEID through PFCP and we remove the F-TEID allocation from the SMF.

⚠️ Warning: This is a breaking change. This PR goes hand in hand with the change in the UPF.

Context

From the 3GPP specification referenced below:

For EPC and 5GC, F-TEID shall be only allocated by the UP function, see clause 5.8.2.3 of 3GPP TS 23.501[28].
The UP function shall set the FTUP feature flag in the UP Function Features IE (see clause 8.2.25) and the CP function
shall request the UP function to allocate the F-TEID. The UP function shall reject a request to establish a new PDR with
an F-TEID allocation in the CP function option, with the cause "Invalid F-TEID allocation option". As an exception, the
UP Function shall accept the PFCP Session Establishment Request message with a PDR including an existing F-TEID
to re-establish a PFCP session during a restoration procedure as specified in clause 4.3.2 of 3GPP TS 23.527 [40] and
clauses 16.1A.4 and 17.1A.4 of 3GPP TS 23.007 [24].

Reference

Signed-off-by: Guillaume Belanger <guillaume.belanger27@gmail.com>
@gruyaume gruyaume changed the title feat: request upf to allocate f-teid feat: request UPF to allocate F-TEID Oct 16, 2024
Signed-off-by: Guillaume Belanger <guillaume.belanger27@gmail.com>
Signed-off-by: Guillaume Belanger <guillaume.belanger27@gmail.com>
Signed-off-by: Guillaume Belanger <guillaume.belanger27@gmail.com>
@thakurajayL
Copy link
Contributor

Not reviewing since its in draft state !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants