_3gpp-common-qmcjob.yang update according to S5-226672 ; add jobid (d8860bb0) · Commits · SA5 – Management & Orchestration and Charging / Management and Orchestration APIs

yang-models/_3gpp-common-qmcjob.yang

+83 −1

Original line number	Diff line number	Diff line
		@@ -25,6 +25,7 @@ module _3gpp-common-qmcjob {
		Integration Reference Point (IRP);
		Information Service (IS)";

		revision 2023-02-14 { reference "CR-0234"; }
		revision 2022-11-04 { reference "CR-0215"; }
		revision 2022-08-17 { reference "CR-0185"; }
		revision 2022-04-29 { reference "CR-0171"; }
		@@ -88,6 +89,16 @@ module _3gpp-common-qmcjob {
		The QMC ID is generated by the management system or the operator.";
		}

		leaf jobId {
		type string;
		description "The jobId attribute presents the job identifier of a
		QMCJob instance. The jobId can be used to associate multiple QMCJob
		instances. For example, it is possible to configure the same jobId
		for multiple QMCJob instances required to produce the data
		(e.g. Streaming services and MTSI reports) for a specific network
		analysis.";
		}

		list sliceScope {
		description "Contains a list of S-NSSAIs (Single Network Slice Selection
		Assistance Information). A Network Slice end to end is identified by
		@@ -126,7 +137,78 @@ module _3gpp-common-qmcjob {
		grouping QMCJobSubTree {
		description "Helps with augmenting QMCJob into multple places.";
		list QMCJob {
		description "Represents the QMCJob IOC.";
		description "The QoE Measurement Collection provides capability for
		collecting QoE information from:
		- UEs which are in the specified area in case of Management Based
		Activation or
		- an individual UE in case of Signalling Based Activation.
		The QoE Measurement Collection enables collection of application layer
		measurements from the UE for specified end user service type.
		The supported service types are:
		- Streaming services, see TS 26.247
		- MTSI services, see TS 26.114
		- VR services, see TS 26.118
		A QMCJob instance represents the job for collecting QoE measurements
		according to the job parameters. For details of the QoE measurement
		collection configuration parameters see clause 5 of TS 28.405.
		QMCJob instance can be name-contained by SubNetwork or ManagedElement.
		A QMC Job is activated by creating a QMCJob object instance in the
		producer. For details of Management Based Activation of QoE Measurement
		Collection see clause 4.5 and for details of Signalling Based
		Activation of QoE Measurement Collection see clause 4.6 of TS 28.405.
		The attributes areaScope and pLMNTarget are only relevant when
		Management Based Activation is used and the attribute qoETarget is
		only relevant when Signalling Based Activation is used. All other
		attributes are common for both Management Based Activation and
		Signalling Based Activation.

		When a MnS consumer wishes to deactivate a QMC Job, the MnS consumer
		shall delete the corresponding QMCJob instance.
		NOTE: If the reporting is ongoing, when a request to delete a QMCJob
		is received, the reporting does not end. The QMCJob instance is deleted,
		when the last reporting for the QMC Job expires.

		The jobId attribute presents the job identifier of a QMCJob instance.
		jobId can be used to associate multiple QMCJob instances. For example,
		it is possible to configure the same jobId value for multiple QMCJob
		instances required to produce the data (e.g. Streaming services and
		MTSI reports) for a specific network analysis.
		The QoE Measurement Collection provides capability for collecting QoE
		information from:
		- UEs which are in the specified area in case of Management Based
		Activation or
		- an individual UE in case of Signalling Based Activation.
		The QoE Measurement Collection enables collection of application layer
		from the UE for specified end user service type. The supported service
		types are:
		- Streaming services, see TS 26.247.
		- MTSI services, see TS 26.114.
		- VR services, see TS 26.118.
		A QMCJob instance represents the job for collecting QoE measurements
		according to the job parameters. For details of the QoE measurement
		collection configuration parameters see clause 5 of TS 28.405. A QMCJob
		instance can be name-contained by SubNetwork or ManagedElement.
		A QMC Job is activated by creating a QMCJob object instance in the
		MnS producer. For details of Management Based Activation of QoE
		Measurement Collection see clause 4.5 and for details of Signalling
		Based Activation of QoE Measurement Collection see
		clause 4.6 of TS 28.405. The attributes areaScope and pLMNTarget are
		only relevant when Management Based Activation is used and the
		attribute qoETarget is only relevant when Signalling Based Activation
		is used. All other attributes are common for both Management Based
		Activation and Signalling Based Activation.

		When a MnS consumer wishes to deactivate a QMC Job, the MnS consumer
		shall delete the corresponding QMCJob instance.
		NOTE: If the reporting is ongoing, when a request to delete a QMCJob
		instance is received, the reporting does not end. The QMCJob instance
		is deleted, when the last reporting for the QMC Job expires.

		The jobId attribute presents the job identifier of a QMCJob instance.
		The jobId can be used to associate multiple QMCJob instances.
		example, it is possible to configure the same jobId value for multiple
		QMCJob instances required to produce the data (e.g. Streaming services
		and MTSI reports) for a specific network analysis.";
		key id;
		uses top3gpp:Top_Grp;
		container attributes {