Loading yang-models/_3gpp-common-trace.yang +76 −60 Original line number Diff line number Diff line Loading @@ -596,7 +596,8 @@ module _3gpp-common-trace { enum VENDORMAXIMUM; } default MAXIMUM; description "It specifies the trace depth. The attribute is applicable only for Trace."; description "It specifies the trace depth. The attribute is applicable only for Trace."; reference "Clause 5.3 of 3GPP TS 32.422."; } Loading Loading @@ -856,13 +857,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 logged according to RRM configuration. reportAmountM7NR, reportAmountM4LTE, reportAmountM5LTE, reportAmountM6LTE, reportAmountM7LTE). If no collection period is configured for M5 in UMTS, all available measurements ar elogged 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. "; leaf listOfMeasurements { Loading @@ -883,8 +884,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."; } Loading @@ -899,8 +901,8 @@ module _3gpp-common-trace { enum ALL_CONFIGURED_RRM_FOR_LTE; enum ALL_CONFIGURED_RRM_FOR_UMTS; } description "It specifies whether periodic or event based measurements should be collected. description "It specifies whether periodic or event based measurements should be collected. The attribute is applicable only for Immediate MDT and when the listOfMeasurements is configured for M1 (for both UMTS and LTE) or M2 (only for UMTS)."; Loading Loading @@ -1034,9 +1036,10 @@ 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. The attribute is applicable only for Immediate MDT."; 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."; } Loading Loading @@ -1346,7 +1349,8 @@ 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 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 Loading @@ -1354,19 +1358,22 @@ module _3gpp-common-trace { 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 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, 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, TS 38.304). In case 'out of coverage' is selected as event type, the 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, 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. Furthermore, logging is performed immediately upon transition from the Loading Loading @@ -1535,7 +1542,8 @@ module _3gpp-common-trace { description "Defines the configuration parameters of IOC TraceJob which are specific for MDT. The attribute anonymizationOfMdtData specifies the level of anonymization of MDT data. The attribute areaScope defines the area scope of MDT, which is specified in clause 5.10.2 of TS 32.422. The of MDT data. The attribute areaScope defines the area scope of MDT, which is specified in clause 5.10.2 of TS 32.422. The optional attribute sensorInformation allows to specify the sensor information to include. Based on the value configured for attribute jobType in IOC TraceJob, the attributes Loading Loading @@ -1606,8 +1614,9 @@ module _3gpp-common-trace { grouping UECoreMeasConfigGrp { description "Represents the UECoreMeasConfig dataType. This <<dataType>> defines the aconfiguration parameters of IOC TraceJob which are specific for 5GC UE level measurements collection."; This <<dataType>> defines the aconfiguration parameters of IOC TraceJob which are specific for 5GC UE level measurements collection."; leaf-list ueCoreMeasurements { type string; Loading @@ -1615,13 +1624,19 @@ module _3gpp-common-trace { The list may include 5GC UE level measurements defined in TS 28.558, or vendor specific measurements. For 5GC UE level measurements defined in TS 28.558, the name is constructed as follows: - 'family.measurementName.subcounter' for measurement type with specified subcounter - '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 For 5GC UE level measurements defined in TS 28.558, the name is constructed as follows: - 'family.measurementName.subcounter' for measurement type with specified subcounter - '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 the associated subcounters under this family. For non-3GPP specified 5GC UE level measurements the name is defined elsewhere."; For non-3GPP specified 5GC UE level measurements the name is defined elsewhere."; } leaf ueCoreMeasGranularityPeriod { Loading Loading @@ -1674,8 +1689,9 @@ module _3gpp-common-trace { } default TRACE_ONLY; description "It specifies whether the TraceJob represents only MDT, Logged MBSFN MDT, Trace, or 5GC UE level measurements job, or a combined job. It also defines the MDT mode."; TraceJob represents only MDT, Logged MBSFN MDT, Trace, or 5GC UE level measurements job, or a combined job. It also defines the MDT mode."; reference "Clause 5.9a of 3GPP TS 32.422."; } Loading Loading @@ -1780,10 +1796,10 @@ 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) or PCSCFFunction (Proxy Call Session Control Function). The traceTarget shall be 'UTRAN_CELL' only in case of the UTRAN cell traffic trace 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 'E-UTRAN_CELL' only in case of E-UTRAN cell traffic trace function. Loading Loading
yang-models/_3gpp-common-trace.yang +76 −60 Original line number Diff line number Diff line Loading @@ -596,7 +596,8 @@ module _3gpp-common-trace { enum VENDORMAXIMUM; } default MAXIMUM; description "It specifies the trace depth. The attribute is applicable only for Trace."; description "It specifies the trace depth. The attribute is applicable only for Trace."; reference "Clause 5.3 of 3GPP TS 32.422."; } Loading Loading @@ -856,13 +857,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 logged according to RRM configuration. reportAmountM7NR, reportAmountM4LTE, reportAmountM5LTE, reportAmountM6LTE, reportAmountM7LTE). If no collection period is configured for M5 in UMTS, all available measurements ar elogged 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. "; leaf listOfMeasurements { Loading @@ -883,8 +884,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."; } Loading @@ -899,8 +901,8 @@ module _3gpp-common-trace { enum ALL_CONFIGURED_RRM_FOR_LTE; enum ALL_CONFIGURED_RRM_FOR_UMTS; } description "It specifies whether periodic or event based measurements should be collected. description "It specifies whether periodic or event based measurements should be collected. The attribute is applicable only for Immediate MDT and when the listOfMeasurements is configured for M1 (for both UMTS and LTE) or M2 (only for UMTS)."; Loading Loading @@ -1034,9 +1036,10 @@ 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. The attribute is applicable only for Immediate MDT."; 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."; } Loading Loading @@ -1346,7 +1349,8 @@ 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 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 Loading @@ -1354,19 +1358,22 @@ module _3gpp-common-trace { 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 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, 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, TS 38.304). In case 'out of coverage' is selected as event type, the 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, 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. Furthermore, logging is performed immediately upon transition from the Loading Loading @@ -1535,7 +1542,8 @@ module _3gpp-common-trace { description "Defines the configuration parameters of IOC TraceJob which are specific for MDT. The attribute anonymizationOfMdtData specifies the level of anonymization of MDT data. The attribute areaScope defines the area scope of MDT, which is specified in clause 5.10.2 of TS 32.422. The of MDT data. The attribute areaScope defines the area scope of MDT, which is specified in clause 5.10.2 of TS 32.422. The optional attribute sensorInformation allows to specify the sensor information to include. Based on the value configured for attribute jobType in IOC TraceJob, the attributes Loading Loading @@ -1606,8 +1614,9 @@ module _3gpp-common-trace { grouping UECoreMeasConfigGrp { description "Represents the UECoreMeasConfig dataType. This <<dataType>> defines the aconfiguration parameters of IOC TraceJob which are specific for 5GC UE level measurements collection."; This <<dataType>> defines the aconfiguration parameters of IOC TraceJob which are specific for 5GC UE level measurements collection."; leaf-list ueCoreMeasurements { type string; Loading @@ -1615,13 +1624,19 @@ module _3gpp-common-trace { The list may include 5GC UE level measurements defined in TS 28.558, or vendor specific measurements. For 5GC UE level measurements defined in TS 28.558, the name is constructed as follows: - 'family.measurementName.subcounter' for measurement type with specified subcounter - '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 For 5GC UE level measurements defined in TS 28.558, the name is constructed as follows: - 'family.measurementName.subcounter' for measurement type with specified subcounter - '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 the associated subcounters under this family. For non-3GPP specified 5GC UE level measurements the name is defined elsewhere."; For non-3GPP specified 5GC UE level measurements the name is defined elsewhere."; } leaf ueCoreMeasGranularityPeriod { Loading Loading @@ -1674,8 +1689,9 @@ module _3gpp-common-trace { } default TRACE_ONLY; description "It specifies whether the TraceJob represents only MDT, Logged MBSFN MDT, Trace, or 5GC UE level measurements job, or a combined job. It also defines the MDT mode."; TraceJob represents only MDT, Logged MBSFN MDT, Trace, or 5GC UE level measurements job, or a combined job. It also defines the MDT mode."; reference "Clause 5.9a of 3GPP TS 32.422."; } Loading Loading @@ -1780,10 +1796,10 @@ 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) or PCSCFFunction (Proxy Call Session Control Function). The traceTarget shall be 'UTRAN_CELL' only in case of the UTRAN cell traffic trace 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 'E-UTRAN_CELL' only in case of E-UTRAN cell traffic trace function. Loading
