Commit 3d3d6974 authored by scottma's avatar scottma Committed by lengyelb
Browse files

Update _3gpp-common-trace.yang

parent 4742197f
Loading
Loading
Loading
Loading
+37 −34
Original line number Diff line number Diff line
@@ -594,8 +594,8 @@ module _3gpp-common-trace {
        -	beamLevelMeasurement (conditional for M1 in NR),
        -	excessPacketDelayThresholds (conditional for M6 UL measurement in NR).

       For immediate MDT, the measurement reporting is dependent on the configured
       measurements: 
       For immediate MDT, the measurement reporting is dependent on the 
       configured measurements: 
       -	For measurement M1 in LTE or NR, it is possible to select between 
        periodical, event triggered, event triggered periodic reporting or 
        reporting according to all configured RRM event triggers. For M1 and M2 
@@ -605,39 +605,42 @@ module _3gpp-common-trace {
        methods is selected and in case of event triggered or event-triggered 
        periodic, which is the decisive event type. For periodical reporting, 
        parameters reportInterval and reportAmount determine the interval between
        two successive reports and the number of reports. This means the periodical 
        reporting terminates after reportAmount reports have been sent as long 
        asreportAmount is configured with a value different from infinity. For 
        event-triggered periodic reporting, these two parameters apply in addition 
        to parameter eventThreshold which determines the threshold of the event. 
        In this case up to reportAmount reports are sent with a periodicity of 
        reportInterval after the entering condition is fulfilled. The reporting 
        is stopped, if the leaving condition is fulfulled and is restarted if the 
        configured event reoccurs. For event based reporting, there is only one 
        report sent after the event occurs. The parameters to configure are 
        reportingTrigger and eventThreshold. In case of UMTS and 1f event reporting,
        additionally parameter measurementQuantity is necessary in order to determine
        for which measurement(s) the event threshold is applicable.  Parameter 
        beamLevelMeasurement determines whether beam level measurements shall be 
        included in case of NR.
        
        -	For measurement M2 in LTE or NR, reporting is according to RRM configuration, 
        see TS 38.321, TS 36.321 and TS 38.331, TS 36.331.  For measurement M4 in 
        UMTS, reporting is either according to RRM configuration, see TS 25.321 and
        TS 25.331 or periodic or event triggered periodic using parameter 
        collectionPeriodRrmUmts and eventThresholdUphUmts.
        
        -	For measurement M3 in UMTS, the reporting is done upon availability, 
        see TS 37.320.
        
        -	For measurements M4, M5, M6 and M7 in NR, for measurements M3, M4, M5, M6
        and M7 in LTE and for measurements M5, M6 and M7 in UMTS periodical reporting 
        is applied. The configurable parameter is the interval between two measurements
        (collectionPeriodRrmNr, collectionPeriodM6NR, collectionPeriodM7Nr, 
        collectionPeriodRrmLte, measurementPeriodLte, collectionPeriodM6Lte, 
        collectionPeriodM7Lte, collectionPeriodRrmUmts, measurementPeriodUmts). 
        If no collection period is configured for M5 in UMTS, all available measurements 
        are logged according to RRM configuration.";
        two successive reports and the number of reports. This means the 
        periodical reporting terminates after reportAmount reports have been
        sent as long as reportAmount is configured with a value different from 
        infinity. For event-triggered periodic reporting, these two parameters 
        apply in addition to parameter eventThreshold which determines the 
        threshold of the event. In this case up to reportAmount reports are 
        sent with a periodicity of reportInterval after the entering condition 
        is fulfilled. The reporting is stopped, if the leaving condition is 
        fulfulled and is restarted if the configured event reoccurs. For event 
        based reporting, there is only one report sent after the event occurs. 
        The parameters to configure are reportingTrigger and eventThreshold. 
        In case of UMTS and 1f event reporting, additionally parameter 
        measurementQuantity is necessary in order to determine for which 
        measurement(s) the event threshold is applicable.  Parameter 
        beamLevelMeasurement determines whether beam level measurements shall
        be included in case of NR.
        
        -	For measurement M2 in LTE or NR, reporting is according to RRM
        configuration, see TS 38.321, TS 36.321 and TS 38.331, TS 36.331.  
        For measurement M4 in UMTS, reporting is either according to RRM 
        configuration, see TS 25.321 and TS 25.331 or periodic or event
        triggered periodic using parameter collectionPeriodRrmUmts and 
        eventThresholdUphUmts.

        -	For measurement M3 in UMTS, the reporting is done upon
        availability, see TS 37.320.
        
        -	For measurements M4, M5, M6 and M7 in NR, for measurements 
        M3, M4, M5, M6 and M7 in LTE and for measurements M5, M6 and M7 
        in UMTS periodical reporting is applied. The configurable parameter
        is the interval between two measurements (collectionPeriodRrmNr, 
        collectionPeriodM6NR, collectionPeriodM7Nr, collectionPeriodRrmLte,
        measurementPeriodLte, collectionPeriodM6Lte, collectionPeriodM7Lte,
        collectionPeriodRrmUmts, measurementPeriodUmts).  If no collection
        period is configured for M5 in UMTS, all available measurements are
        logged according to RRM configuration.";
        
  leaf listOfMeasurements {
      when 'jobType = "IMMEDIATE_MDT_ONLY"';