Open davidjwbbc opened 4 months ago
Moving Usage attributes and read-only discrepancies to a new clarification issue.
This one looks like a straightforward bug in TS 26.532 that needs to be corrected in table 6.3.2.1-1.
I suspect the original intent was for the eventId property to be nominated by the Application Service Provider. The absence of the readOnly
flag in the OpenAPI YAML seems to (correctly) model this, so no API change is needed, I think.
Given that this issue affects the provisioning of the standalone Data Collection AF (i.e. for exposure of the basic SA2 events to NWDAF), I think changes to both Rel-17 and Rel-18 are justified, even though 5G-MAG Reference Tools is only implementing Rel-18.
The Rel-17 fix could potentially be folded in to TS 26.532 CR0007 that is already addressing #114.
Context
Table 6.3.2.1-1 in TS 26.532 V17.2.0 and V18.1.0 defines the DataReportingProvisioingSession object. The eventId property is marked as read-only in Table 6.3.2.1-1. It is unclear how the Data Collection AF knows which event type is intended in order to fill this field in for the response.
In clause B.3, the OpenAPI YAML for the _NdcafDataReportingProvisioning service API declares eventId to be a required property of DataReportingProvisioningSession data type, but does not mark it as
readOnly
.Clarification question
How should the AF derive this value, or should this field be read-write instead, and set by the ASP's Provisioning AF?