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

MME: Incorrect formatting in GTP Serving Network #969

Closed
gusbourg opened this issue Apr 30, 2021 · 3 comments
Closed

MME: Incorrect formatting in GTP Serving Network #969

gusbourg opened this issue Apr 30, 2021 · 3 comments
Labels
Housekeeping:ToClose Issues reviewed and closed. Old requests, issues which are not bug, feature or documentation request

Comments

@gusbourg
Copy link

When sending a Create Session Request (and possibly other types of GTPv2 operations), the MME is incorrectly encoding Serving Network. The MME appears using the S1 plmnidentity which is encoded according to 3GPP 36.413 section 9.2.3.8 and encodes it in the GTPv2 CSR as Serving Network without coverting it to the format specified in 3GPP 29.274 section 8.18. As a result the serving network sent in the create session request is incorrect.

References:
36.314 Section 9.2.3.8
https://www.etsi.org/deliver/etsi_ts/136400_136499/136413/12.03.00_60/ts_136413v120300p.pdf

29.274 Section 8.18
https://www.etsi.org/deliver/etsi_ts/129200_129299/129274/10.05.00_60/ts_129274v100500p.pdf

@acetcom
Copy link
Member

acetcom commented May 2, 2021

@gusbourg

You're right. PLMN-ID in ULI(E-CGI, E-TAI, ...) is also incorrect in Open5GS GTPv2 message. I'll fix it soon.

Thank you so much!
Sukchan

@acetcom
Copy link
Member

acetcom commented May 5, 2021

@gusbourg

I've fixed the bug and updated it to the main branch.
Let me know if you have any further questions.

Thank you so much!
Sukchan

@pobk pobk added the Housekeeping:ToClose Issues reviewed and closed. Old requests, issues which are not bug, feature or documentation request label Feb 18, 2023
@github-actions
Copy link

This issue has been closed automatically due to lack of activity. This has been done to try and reduce the amount of noise. Please do not comment any further. The Open5GS Team may choose to re-open this issue if necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Housekeeping:ToClose Issues reviewed and closed. Old requests, issues which are not bug, feature or documentation request
Projects
None yet
Development

No branches or pull requests

3 participants