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

SM contexts collection Response not compliant to standard #71

Open
bnlrnz opened this issue Mar 8, 2023 · 1 comment
Open

SM contexts collection Response not compliant to standard #71

bnlrnz opened this issue Mar 8, 2023 · 1 comment

Comments

@bnlrnz
Copy link

bnlrnz commented Mar 8, 2023

The response header to an SM contexts collection request
{apiRoot}/nsmf-pdusession/{apiVersion}/sm-contexts
should include a location field with the URI of the newly created resource, according to the structure:
{apiRoot}/nsmf-pdusession/{apiVersion}/sm-contexts/{smContextRef}
Currently the location field is filled with something like:
urn:uuid:7a51fda4-2d05-45d0-9988-1eacfa378310 (this is only the smContextRef)
The other free5GC components are aware of that and build the correct URI themselfs, but one can not use the free5GC SMF with other standard compliant components as they can not handle the format free5GCs SMF is providing in the location field.

See 3GPP TS 29.502 -> Resource: SM contexts collection -> Headers supported by the 201 Response Code on this resource

@pf-lin
Copy link
Contributor

pf-lin commented Mar 13, 2024

Thanks for your information.

Currently, the free5GC implements Release 15.3. There are no clear definitions for smContextRef.
It will be fixed in the following Release 17 upgrade.

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

No branches or pull requests

2 participants