5G-MAG / Standards

Specifications related to 5G-MAG's areas of work. Tracking comments, bug-fixing, request for new features, etc.
https://www.5g-mag.com/standards
12 stars 4 forks source link

TS 26.532: Clarification of Usage values of properties in structured data in Clauses 6 and 7 #115

Closed davidjwbbc closed 4 months ago

davidjwbbc commented 9 months ago

TS 26.532 v18.1.0 defines several structures in Clauses 6 & 7 which contain Usage values for properties which are not defined in Clause 5.5. Also there are other properties that are marked "RO" in the structure tables in Clauses 6 & 7 which are not flagged as read-only in the OpenAPI YAML in the Annex.

The following table picks out the properties from the structured data objects where the Usage defined does not make sense:

Table Object Property Usage Usage meaning OpenAPI YAML read-only status Remarks
6.3.2.1-1 DataReporting​ProvisioningSession provisioning​SessionId C: R Undefined read-write Needs to be declared read-only.
6.3.2.1-1 DataReporting​ProvisioningSession aspId C: W Undefined read-write Properties can't be declared immutable in OpenAPI, so read–write will have to do.
6.3.2.2-1 DataReporting​Configuration dataReporting​ConfigurationId C: R Undefined read-write Needs to be declared read-only.
7.3.2.1-1 DataReporting​Session sessionId C: — Not Applicable read-write Can't be Not Applicable as it's returned for the create operation
7.3.2.1-1 DataReporting​Session validUntil C: — Not Applicable read-write Can't be Not Applicable as it's returned for the create operation
7.3.2.1-1 DataReporting​Session sampling​Rules C: — Not Applicable read-write Can't be Not Applicable as it's returned for the create operation
7.3.2.1-1 DataReporting​Session reporting​Conditions C: — Not Applicable read-write Can't be Not Applicable as it's returned for the create operation
7.3.2.1-1 DataReporting​Session reporting​Rules C: — Not Applicable read-write Can't be Not Applicable as it's returned for the create operation

What are the correct Usage values and which OpenAPI YAML properties need a "readOnly: true" attribute setting?

rjb1000 commented 9 months ago

Agree this looks like a bit of a mess and could do with being rationalised.

Given that this issue affects the provisioning and reporting of UE data to 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.

rjb1000 commented 7 months ago

Change Requests contributed to SA4#127-bis-e for agreement:

rjb1000 commented 7 months ago

Change Requests agreed without revision at SA4#127-bis-e:

These will go to SA#104 for approval in June.

rjb1000 commented 4 months ago

New specification versions published following approval of CRs at SA#104: