Change Request Details

Spec #:	26.532
CR #:	0007
Revision #:	2
Impacted version:	17.2.0
Target Release:	Rel-17
Title:	[EVEX] Essential maintenance
WG TDoc:	S4-240553
WG status:	Agreed
New version:	17.3.0
Category:	F

TSG TDoc:	SP-240683
TSG status:	Approved

Entities:

UICC

ME

RAN

CN

Related Work Items

UID	Acronym	Title	Resp. grp(s)


960051	EVEX	5GMS AF Event Exposure	S4		False

Clauses Affected:	5.4.2.1A (new), 5.4.2.2, 5.4.3.2 (new), 5.4.3.3 (new), 6.3.2.1, 6.3.2.2, 6.3.2.2A, 6.3.3.2, 7.3.2.2 (voided), 7.3.3.2 (voided), 7.3.3.3 (voided), B.2, B.3, B.4.
Reason For Change:	ReportingCondition structure is required to be populated in the client-facing DataReportingSession, but cannot currently be provisioned in the DataReportingProvisioningSession.https://github.com/5G-MAG/Standards/issues/114Reporting format URI is a redundant property of DataReportingRule becase the format is a fixed JSON data type.https://github.com/5G-MAG/Standards/issues/111eventId property of DataReportingProvisioingSession data type is incorrectly marked as read-only in table 6.3.2-1 (but not in clause B.3).https://github.com/5G-MAG/Standards/issues/113Maps in DataReportingSession specified in table 7.3.2.11 are not faithfully rendered in YAML specification in clause B.4.https://github.com/5G-MAG/Standards/issues/116DataAggregationFunctionType declared enumerated value NULL which is a reserved identifier in some software implementation languages.https://github.com/5G-MAG/Standards/issues/117The "Usage" column of tables in clauses 6 and 7 is inconsistently specified and some read-only properties are not correctly marked in the OpenAPI YAML in annex B.https://github.com/5G-MAG/Standards/issues/115
Summary Of Change:	Add a reference to ReportingCondition from DataReportingConfiguration. Move ReportingCondition, ReportingConditionType enumeration and ReportingEventTrigger enumeration into common data types. Rename ReportingCondition to DataReportingCondition.Made reportingFormat property optional in shared DataReportingRule data type in clauses 5.4.2.2 and B.2.Made eventId property of DataReportingProvisioingSession data type not read-only in table 6.3.2-1.Corrected DataReportingSession properties in clause B.4 to be OpenAPI associative arrays.Renamed NULL as NONE in table 6.3.3.2-1 and clause B.2.Fixed "Usage" column on tables in clauses 6 and 7. Marked certain OpenAPI YAML properties as read-only in annex B.
Consequence If Not Approved:	Impossible to provision reporting conditions to trigger the sending of data reports by the Direct Data Collection Client in the UE.Inconsistent implementation of service-based interfaces.
Other Comments:	Changes to the Ndcaf_DataReportingProvisioning service are non-backwards-compatible.Changes to the Ndcaf_DataReporting service are backwards-compatible, so there is no material impact on the UE.
CR Revision History:	CR 0007r2 [S4-240553]: Additional changes 2–5 above.
Other Core Specs:		Other Core Specifications:
Test Specs:		Test Specifications:
OM Specs:		OM Specifications:

Remarks (0)

Creation date	Author	Remark


No Remarks Added

Exit