Updated Tracejob description

        -measurementQuantity (conditional for 1F event reporting),

        -beamLevelMeasurement (conditional for M1 in NR),

        -excessPacketDelayThresholds (conditional for M6 UL measurement in NR).

        -layerOneRsrpPeriodicity (conditional for M10 measurements in NR),

        -eventTriggerConfig (conditional for event reporting for M10 measuremen

       For immediate MDT, the measurement reporting is dependent on the

       configured measurements:

        - Measurements M8 and M9 in NR or LTE are reported according to

        configured M1 and/or M6 related UE measurement reporting.

        - For management based Immediate MDT M10 measurements 

        layerOneRsrpPeriodicity in NR, the 

        measurement is optionally triggered with periodically or event based . 

        The parameter layerOneRsrpPeriodicity determines the interval between 

        two successive UE measurements. If parameter eventTriggerConfig is 

        configured, the logging is performed only at the condition indicated 

        by eventTriggerConfigis met.

        ";

    leaf listOfMeasurements {

      description "A TraceJob instance represents the Trace Control and

        Configuration parameters of a particular Trace Job (see TS 32.421 and

        TS 32.422 for details). It can be name-contained by SubNetwork,

        ManagedElement, ManagedFunction.

        ManagedElement, ManagedFunction. In case of signalling based trace 

        activation, it shall be name-contained by the UDMFunction, see TS 28.541.

        To activate Trace Jobs, a MnS consumer has to create TraceJob object

        instances on the MnS producer. A MnS consumer can activate a Trace Job

        4.1.2.1.2 of TS 32.422.

        When a MnS consumer wishes to deactivate a Trace Job, the MnS consumer

        shall delete the corresponding TraceJob instance.

        For details of management Trace Job activation/deactivation see clause

        4.1.1.1.2 of TS 32.422.

        shall delete the corresponding TraceJob instance. For details of 

        management Trace Job deactivation see clauses 4.1.3.8 to 4.1.3.11 a

        nd 4.1.4.10 to 4.1.4.13  of TS 32.422

        The attribute traceReference specifies a globally unique ID and

        identifies a Trace session. One Trace Session may be activated to

        multiple Network Elements. The traceReference is populated by the

        consumer that makes the request for a Trace Session.

        consumer that makes the request for a Trace Session, TS 32.422.

        The jobId attribute presents the job identifier of a TraceJob instance.

        The jobId can be used to associate  multiple TraceJob instances.

        stream-based reporting the attribute traceReportingConsumerUri

        specifies the streaming target.

        The mandatory attribute traceTarget determines the target object of

        the TraceJob. Dependent on the network element to which the Trace

        Session is activated different types of the target object are possible.

        The attribute traceTarget determines the target object of the 

        TraceJob. Dependent on the network element to which the Trace Session 

        is activated different types of the target object are possible.

        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.

        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.

        The attribute listOfTraceMetrics allows configuraton of which metrics

        shall be recorded.