search

free5gc / smf

Apache License 2.0
19 stars 95 forks source link

SM contexts collection Response not compliant to standard #71

Open bnlrnz opened 1 year ago

bnlrnz commented 1 year ago

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 commented 6 months ago

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.