Update _3gpp-common-trace.yang (5980b387) · Commits · SA5 – Management & Orchestration and Charging / Management and Orchestration APIs

yang-models/_3gpp-common-trace.yang

+50 −42

Original line number	Diff line number	Diff line
		@@ -866,13 +866,13 @@ module _3gpp-common-trace {
		measurementPeriodLte, collectionPeriodM6LTE, collectionPeriodM7LTE,
		collectionPeriodRRMUMTS, measurementPeriodUMTS) and the number of
		reports (reportAmountM4NR, reportAmountM5NR, reportAmountM6NR,
		reportAmountM7NR, reportAmountM4LTE, reportAmountM5LTE, reportAmountM6LTE,
		reportAmountM7LTE). If no collection period is configured for M5 in UMTS,
		all available measurements are
		reportAmountM7NR, reportAmountM4LTE, reportAmountM5LTE,
		reportAmountM6LTE,reportAmountM7LTE). If no collection period
		is configured for M5 in UMTS, all available measurements are
		logged according to RRM configuration.

		- Measurements M8 and M9 in NR or LTE are reported according to configured
		M1 and/or M6 related UE measurement reporting.
		- Measurements M8 and M9 in NR or LTE are reported according to
		configured M1 and/or M6 related UE measurement reporting.

		";

		@@ -894,8 +894,9 @@ module _3gpp-common-trace {
		enum M8;
		enum M9;
		}
		description "It specifies the UE measurements that shall be collected in
		an Immediate MDT job. The attribute is applicable only for Immediate MDT.";
		description "It specifies the UE measurements that shall be
		collected in an Immediate MDT job. The attribute is
		applicable only for Immediate MDT.";
		reference "Clause 5.10.3 of 3GPP TS 32.422.";
		}

		@@ -1045,8 +1046,9 @@ module _3gpp-common-trace {
		enum 1min;
		}
		mandatory true;
		description "It specifies the measurement period for the Data Volume (M4) and
		Scheduled IP throughput measurements (M5) for LTE MDT taken by the eNB.
		description "It specifies the measurement period for the
		Data Volume (M4) and Scheduled IP throughput
		measurements (M5) for LTE MDT taken by the eNB.
		The attribute is applicable only for Immediate MDT.";
		reference "Clause 5.10.23 of 3GPP TS 32.422.";
		}
		@@ -1359,27 +1361,31 @@ module _3gpp-common-trace {
		Based on the value configured for attribute jobType in IOC TraceJob,
		different attributes are available. In case of LOGGED_MDT_ONLY, the
		attributes reportType, eventListForEventTriggeredMeasurement,
		eventThresholdL1, hysteresisL1, timeToTriggerL1, areaConfigurationForNeighCells
		and npnIdentityList are applicable. In case of LOGGED_MBSFN_MDT,
		the attribute mbsfnAreaList is applicable. The optional attribute plmnList
		allows to specify the PLMNs where
		measurement collection, status indication and log reporting is allowed,
		the optional attribute areaConfigurationForNeighCell allows to specify
		the area for which UE is requested to perform measurements logging for
		neighbour cells which have list of frequencies.
		eventThresholdL1, hysteresisL1, timeToTriggerL1,
		areaConfigurationForNeighCells and npnIdentityList are applicable.
		In case of LOGGED_MBSFN_MDT,
		the attribute mbsfnAreaList is applicable. The optional attribute
		plmnList allows to specify the PLMNs where
		measurement collection, status indication and log reporting is
		allowed, the optional attribute areaConfigurationForNeighCell
		allows to specify the area for which UE is requested to perform
		measurements logging for neighbour cells which have list of
		frequencies.

		For logged MDT in UMTS and LTE, the reporting is periodical. Parameter
		loggingInterval determines the interval between the reports and parameter
		loggingDuration determines how long the configuration is valid meaning after
		this duration has passed no further reports are sent. In NR, the reporting
		can be periodical or event based, determined by parameter reportType. For periodical
		reporting the same parameters as in LTE and UMTS apply. For event based reporting,
		loggingDuration determines how long the configuration is valid meaning
		after this duration has passed no further reports are sent. In NR, the
		reporting can be periodical or event based, determined by parameter
		reportType. For periodical reporting the same parameters as in LTE and
		UMTS apply. For event based reporting,
		parameter eventListForEventTriggeredMeasurement configures the event type,
		namely 'out of coverage' or 'L1 event'. In case 'L1 event' is selected as
		event type, the logging is performed according to parameter loggingInterval
		at regular intervals only when the conditions indicated by eventThresholdL1,
		hysteresisL1, timeToTriggerL1 (defining the thresholds, hysteresis and time
		to trigger) are met and if UE is 'camped normally' state (TS 38.331,
		at regular intervals only when the conditions indicated by
		eventThresholdL1, hysteresisL1, timeToTriggerL1 (defining the thresholds,
		hysteresis and time to trigger) are met and if UE is 'camped normally'
		state (TS 38.331,
		TS 38.304). In case 'out of coverage' is selected as event type, the
		logging is performed according to parameter loggingInterval at regular
		intervals only when the UE is in 'any cell selection' state.
		@@ -1575,7 +1581,6 @@ module _3gpp-common-trace {
		key "idx";
		leaf idx { type uint32 ; }
		description "It specifies the area where data shall be collected. ";
		min-elements 0;
		max-elements 1;
		uses AreaScopeGrp;
		}
		@@ -1634,12 +1639,12 @@ module _3gpp-common-trace {

		For 5GC UE level measurements defined in TS 28.558, the name is
		constructed as follows:
		- 'family.measurementName.subcounter' for measurement type with
		'family.measurementName.subcounter' for measurement type with
		specified subcounter
		- 'family.measurementName.ALL' for measurement type with all supported
		'family.measurementName.ALL' for measurement type with all supported
		subcounters
		- 'family.measurementName' for measurement type without subcounters
		- 'family' for measurement family, including all measurement types and
		'family.measurementName' for measurement type without subcounters
		'family' for measurement family, including all measurement types and
		the associated subcounters under this family.
		For non-3GPP specified 5GC UE level measurements the name is defined
		elsewhere.";
		@@ -1820,10 +1825,11 @@ module _3gpp-common-trace {
		includes the ID type of the target as an enumeration and the ID value.

		The traceTarget shall be 'PUBLIC_ID' in case of a Management Based
		Activation is done to an SCSCFFunction (Serving Call Session Control Function)
		Activation is done to an SCSCFFunction (Serving Call
		Session Control Function)
		or PCSCFFunction (Proxy Call Session Control Function).
		The traceTarget shall be 'UTRAN_CELL' only in case of the UTRAN cell traffic
		trace function.
		The traceTarget shall be 'UTRAN_CELL' only in case of the UTRAN
		cell traffic trace function.

		The traceTarget shall be 'E-UTRAN_CELL' only in case of E-UTRAN cell
		traffic trace function.
		@@ -1863,7 +1869,8 @@ module _3gpp-common-trace {
		In case of management based Immediate MDT, the traceTarget attribute
		shall be null value. In case of management based Logged MDT, the
		traceTarget attribute shall carry an 'eNB' or a 'gNB' or an 'RNC'.
		The Logged MDT should be initiated on the specified eNB/gNB/RNC in traceTarget.
		The Logged MDT should be initiated on the specified
		eNB/gNB/RNC in traceTarget.

		In case of RLF reporting, or RCEF reporting, or RRC reporting, the
		traceTarget attribute shall be null value.
		@@ -1985,25 +1992,26 @@ module _3gpp-common-trace {
		The attribute pLMNTarget defines the PLMN for which sessions shall be
		selected in the Trace Session in case of management based activation
		when several PLMNs are supported in the RAN.The MDT configuration may
		include area scope defined by network slice, in which case the attribute
		pLMNTarget is not applicable.
		include area scope defined by network slice, in which case
		the attribute pLMNTarget is not applicable.

		The attribute listOfTraceMetrics allows configuraton of which metrics
		shall be recorded.

		The attribute jobType specifies the kind of data to collect. In case of
		TRACE_ONLY, the configuration parameters of attribute traceConfig shall
		be applied. In case of IMMEDIATE_MDT_ONLY, LOGGED_MDT_ONLY, RLF_REPORT_ONLY,
		RCEF_REPORT_ONLY and LOGGED_MBSFN_MDT the configuration parameters of
		TRACE_ONLY, the configuration parameters of attribute traceConfig
		shall be applied. In case of IMMEDIATE_MDT_ONLY, LOGGED_MDT_ONLY,
		RLF_REPORT_ONLY, RCEF_REPORT_ONLY and LOGGED_MBSFN_MDT the
		configuration parameters of
		attribute mdtConfig or a subset of these shall be applied. In case of
		5GC_UE_LEVEL_MEASUREMENTS_ONLY, the configuration parameters of attribute
		ueCoreMeasConfig shall be applied. In case of any combination of Trace,
		Immediate MDT, and 5GC UE level measurements, the configuration parameters
		of the corresponding attributes, traceConfig, mdtConfig and ueCoreMeasConfig
		are applicable.
		of the corresponding attributes, traceConfig, mdtConfig and
		ueCoreMeasConfig are applicable.

		If jobType has the value RRC Report, the attribute rrcReportType shall be
		present. The rrcReportType allows the tracing of RRC reports.
		If jobType has the value RRC Report, the attribute rrcReportType shall
		bepresent. The rrcReportType allows the tracing of RRC reports.

		Creation and deletion of TraceJob instances by MnS consumers is
		optional; when not supported, the TraceJob instances may be created