rjb1000
commented
8 months ago Note that although the HTTP POST method is used to submit a QoE metrics report to the 5GMS AF at reference point M5, it isn't correct to refer to this as a Create operation. It's not creating a resource on the 5GMS AF in the RESTful sense. You can't subsequently retrieve the resource using GET, for example.
It's more accurate to think of this operation in terms of the Remote Procedure Call metaphor: you provide the metrics report to the 5GMS AF at the RPC interface and get a return code in response. And that's the end of the matter.
stojkovicv
Description
This merge request expands Application Function with an entrypoint for a collected QoE Metrics at RPC interface with a reference point M5. Only HTTP method defined in TS26.512 (v17.7) for Metrics Reporting API is
POST, used to submit QoE metrics reports.Related discussions: https://github.com/5G-MAG/rt-5gms-application-function/issues/76 , https://github.com/5G-MAG/rt-5gms-application-function/issues/95
Changes
Bash generator now pulls declarations for M5 Metrics API.
Service Access Information module has been expanded to iterate through map of Metrics Reporting objects, and to populate JSON subarray
clientMetricsReportingConfiguration. This array contains, previously, provisioned Metrics Reporting data.M5 state machine now contains code to handle Metrics Reporting
POSTrequest. It expects XML data as a payload, parses relevant information from it, so that metrics data can be written locally with a correct parameters in the file name (https://github.com/5G-MAG/rt-5gms-application-function/issues/90). There is a logical checking that proceeds with M5POSTmethods only if, at least one, Metrics Configuration has been previously provisioned.Finally, Service Access Information cache clearance has been added for M1 Create, Update and Delete operations, because they affect SAI content. This will enable to correctly populate Service Access Information list along with a
clientMetricsReportingConfiguration.