QoE Metrics Reporting: M1 Provisioning - reportingInterval shall be greater than zero

[dsilhavy]

Description

According to TS 26.512 Table 7.8.3-1 the reportingInterval shall be greater than zero:

The time interval between successive metrics reports. The value shall be greater than zero.
If not specified, a single final report shall be sent after the media streaming session has ended.

This requirement is not reflected in TS26512_M1_MetricsReportingProvisioning.yaml

reportingInterval: $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec'

Suggested Solution

One solution for this is to add a the following to the yaml definition:

minimum: 0
exclusiveMinimum: true

Related discussion

• QoE Metrics Reporting - M1 Provisioning - reportingInterval shall be greater than zero rt-5gms-application-function#145
• M1 Bugfix | Parameters checking of Metrics Reporting Configurations rt-5gms-application-function#147

[rjb1000]

Rel-18 change to TS 26.510 committed to 3GPP Forge project:

• https://forge.3gpp.org/rep/sa4/5gms_pro_ph2/-/tags/DurationSec-minima

Rel-17 fix will require a formal Change Request, but @davidjwbbc will provide a temporary workaround.

[rjb1000]

Change Request contributed to MBS ad hoc meeting post SA4#127-bis-e:

• TS 26.512 (OpenAPI YAML change only)
  • Rel-16: Won't correct because 5G-MAG's Reference Tools implementation uses Rel-17 as a starting point.
  • Rel-17: CR0069 "[5GMS3, TEI17] Metrics reporting corrections" in S4aI240047.
  • Rel-18: Changes to be handled directly in TS 26.510 V1.2.1.

[rjb1000]

Change Request treated at MBS ad hoc meeting post SA4#127-bis-e:

• TS 26.512
  • Rel-17: CR0069 "[5GMS3, TEI17] Metrics reporting corrections" in S4aI240047.
    • Endorsed and will be resubmitted to SA4#128 for agreement.
  • Rel-18: Changes to be handled directly in TS 26.510 V1.2.1.
    • Editor to check TS 26.510 prior to contribution.