The current implementation of the MBS User Data Ingest Sessions API at reference point Nmb10 does not implement the HTTP GET method for the .../nmbsf-mbs-ud-ingest/v1/sessions path (MBS User Data Ingest Sessions collection path).
This should return a JSON array of MBSUserDataIngSession structures according to TS 29.580 Clause 6.2.3.2.3.1. This was deliberately left out of the implementation as the specified return type is not useful as it does not contain the MBS User Data Ingest Session resource Id. 5G-MAG/Standards#191 raises the issue of the missing resource Ids.
The current implementation of the MBS User Data Ingest Sessions API at reference point Nmb10 does not implement the HTTP GET method for the
.../nmbsf-mbs-ud-ingest/v1/sessionspath (MBS User Data Ingest Sessions collection path).This should return a JSON array of MBSUserDataIngSession structures according to TS 29.580 Clause 6.2.3.2.3.1. This was deliberately left out of the implementation as the specified return type is not useful as it does not contain the MBS User Data Ingest Session resource Id. 5G-MAG/Standards#191 raises the issue of the missing resource Ids.