OpenAPI calls with Open5Gs

[zaloafernandez]

Hi!

We are interested in using the OpenAPI Descriptions of 3GPP 5G APIs with Open5Gs. We have seen that it is possible to obtain the registered nf instances (curl --http2-prior-knowledge http://ip:port/nnrf-nfm/v1/nf-instances) and information related to them (curl --http2-prior-knowledge http://ip:port/nnrf-nfm/v1/nf-instances/nfInstanceId).

Apart from making calls to the NRF element, is it possible to make calls to other elements?

Best regards

[ramrattle]

yes, you cab do any CRUD operation on any REST enabled open5gs NF's.

[zaloafernandez]

Thanks for the information. However, how can we know if the deployed NFs are REST enabled? Should this be done in the configuration files of each NF? And how do we know which calls can be made in each of the NFs?

Best regards

[ramrattle]

yes, all the nodes that support SBA will work for this, you can refer https://github.com/jdegre/5GC_APIs to understand which calls to make, make sure to use the swagger UI for better understanding.

[Abebu-23]

I have tried to make a call to namf-evts api with requesting body given below:

curl --http2-prior-knowledge -X 'POST'
'http://localhost:8888/namf-evts/v1/subscriptions'
-H 'accept: application/json'
-H 'Content-Type: application/json'
-d '{
"subscription": {
"eventList": {
"type": "",
"immediateFlag": True,
"refId": 0
},
"eventNotifyUri": "http://localhost:8000/notifications",
"notifyCorrelationId": "string",
"nfId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"subsChangeNotifyUri": "string",
"subsChangeNotifyCorrelationId": "string",
"anyUE": True,
"supi": "string",
"options": {
"trigger": "CONTINUOUS",
"maxReports": 30,
"expiry": "2022-07-20T11:30:31.124Z",
"repPeriod": 1
}
},
"suppo^CedFeatures": "FFFF"
}'
And the response is
{
"title": "cannot parse HTTP sbi_message",
"status": 400
}
did i make something wrong , or should modify something?
or is it even possible to make call to this amf -evts api?

[molnar-gabi]

Hello!

I am not completely familiar with the implementation, but after a basic search in the source code it looks like it is just not implemented yet:

$ grep -r OGS_SBI_SERVICE_NAME_NAMF_EVTS *
lib/sbi/types.h:#define OGS_SBI_SERVICE_NAME_NAMF_EVTS "namf-evts"
lib/sbi/types.c:    { OpenAPI_nf_type_AMF, OGS_SBI_SERVICE_NAME_NAMF_EVTS },

Try testing with some already implemented OAPI calls, like the "namf-comm" in AMF.