QoE Metrics Reporting: metricsReportingConfigurationId missing in TS26512_M5_ServiceAccessInformation.yaml.

[dsilhavy]

Description

TS 26.512 Table 11.2.3.1-1 defines the ServiceAccessInformation resource. The ServiceAccessInformation resource contains a property clientMetricsReportingConfigurations. Each entry in the clientMetricsReportingConfigurations has a property metricsReportingConfigurationId. The metricsReportingConfigurationId is missing in the corresponding TS26512_M5_ServiceAccessInformation.yamlfile:

clientMetricsReportingConfigurations:
          type: array
          minItems: 1
          items:
            type: object
            required:
            - serverAddresses
            - scheme
            - samplePercentage
            - urlFilters
            - samplingPeriod
            - metrics
            properties:
              serverAddresses:
                $ref: '#/components/schemas/ServerAddresses'
              scheme:
                $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
              dataNetworkName:
                $ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn'
              reportingInterval:
                $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec'
              samplePercentage:
                $ref: 'TS26512_CommonData.yaml#/components/schemas/Percentage'
              urlFilters:
                type: array
                items:
                  type: string
                minItems: 0
              samplingPeriod:
                $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec'
              metrics:
                type: array
                items:
                  type: string

Suggested solution

Add the metricsReportingConfigurationId as a required parameter to the TS26512_M5_ServiceAccessInformation.yaml

Related issue

• Client metrics reporting configurations in 5GMS Service Access Information lack unique configuration identifier required by Metrics Reporting API #46

[rjb1000]

(@davidjwbbc has provided a temporary workaround in 5G-MAG/rt-common-shared#35.)

[rjb1000]

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

• TS 26.512
  • 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.