Uplift to results of SA#109 (TS 26.532 V18.5.0)

[davidjwbbc]

The results of SA#109 have been pushed to the forge.3gpp.org/rep/all/5G_APIs repository for Release 18 under the TSG109-Rel18 tag.

The core TS 26.532 types have not changed, however there are a couple of key changes in types pulled in from other specifications:

1. The ClientQosSpecification object, pulled in from TS26510_CommonData.yaml, has been renamed ClientPolicySpecification.
2. The NwdafEvent enumeration, pulled in from TS29520_Nnwdaf_EventsSubscription.yaml, has had 5 values removed (these have been moved to the AnalyticsSubset enumeration instead, which we don't use):
   • NUM_OF_UE
   • MOV_UE_RATIO
   • AVR_SPEED
   • SPEED_THRESHOLD
   • MOV_UE_DIRECTION

These appear to be the only changes between TSG105-Rel18 and TSG109-Rel18 which affect the Data Collection AF.

[rjb1000]

The ClientQosSpecification object, pulled in from TS26510_CommonData.yaml, has been renamed ClientPolicySpecification.

Is ClientQosSpecification actually used anywhere in TS 26.532?

The NwdafEvent enumeration, pulled in from TS29520_Nnwdaf_EventsSubscription.yaml, has had 5 values removed (these have been moved to the AnalyticsSubset enumeration instead, which we don't use).

Is this NwdafEvent actually used anywhere in TS 26.532?

These appear to be the only changes between TSG105-Rel18 and TSG109-Rel18 which affect the Data Collection AF.

I think the first job is to establish whether the changes have any material impact on the Data Collection AF. I suspect none.