Commit 5841c7e4 authored by lengyelb's avatar lengyelb
Browse files

Update tracejob description and ImmediateMdtConfig

parent ccc672ee
Loading
Loading
Loading
Loading
Loading
+119 −18
Original line number Diff line number Diff line
@@ -25,6 +25,7 @@ module _3gpp-common-trace {
      Integration Reference Point (IRP);
      Information Service (IS)" ;

  revision 2026-03-20 { reference "CR-xxxx" ; }
  revision 2026-02-07 { reference "CR-1682" ; }
  revision 2025-10-07 { reference "CR-0573" ; }    
  revision 2025-10-01 { reference "CR-0578" ; }
@@ -745,6 +746,75 @@ module _3gpp-common-trace {
    }
  }

  grouping EventTriggerConfigGrp {
    description "Represent the EventTriggerConfig data type. Defines the 
      configuration parameters of trigger event used for M10 measurement in NR. 
      For details, please refer to TS 32.422 subclause 5.10.45.";
    
    leaf eventType {
      type enumeration {
        enum eventA1 { value 0; }
        enum eventA2 { value 1; }
      }
      mandatory true;
      description "It indicates the event type. Either Event A1 or Event A2 
        can be configured. See also clause 5.10.45 of TS 32.422.";
    }
    
    leaf thresholdRAN {
      type uint8 {
        range 0..127;
      }
      mandatory true;
      description "Threshold parameter for an event. It is used to define the 
        entering and leaving condition of the event. For further details see 
        RSRP-Range in TS 38.331. See also clause 5.10.45 of TS 32.422";
    }
    
    leaf measurementQuantityRAN {
      type int32;
      mandatory true;
      description "It indicates the measurement quantity. For further details 
        see MeasTriggerQuantity in TS 38.331. See also clause 5.10.45 of 
        TS 32.422";
    }
    
    leaf hysteresisRAN {
      type uint8 {
        range 0..30;
      }
      mandatory true;
      description "Hysteresis parameter for an event. It is used to define the 
        entering and leaving condition of the event. For further details see 
        Hysteresis in TS 38.331. See also clause 5.10.45 of TS 32.422";
    }
    
    leaf timeToTriggerRAN {
      type enumeration {
        enum 0ms { value 0; }
        enum 40ms { value 1; }
        enum 64ms { value 2; }
        enum 80ms { value 3; }
        enum 100ms { value 4; }
        enum 128ms { value 5; }
        enum 160ms { value 6; }
        enum 256ms { value 7; }
        enum 320ms { value 8; }
        enum 480ms { value 9; }
        enum 512ms { value 10; }
        enum 640ms { value 11; }
        enum 1024ms { value 12; }
        enum 1280ms { value 13; }
        enum 2560ms { value 14; }
        enum 5120ms { value 15; }
      }
      mandatory true;
      description "It defines the time during which specific criteria for the 
        event needs to be met in order to trigger an action. 
        For further details see TimeToTrigger in TS 38.331 and clause 5.10.45 of TS 32.422.";
    }
  }
  
  grouping ImmediateMdtConfigGrp {
   description "Represents the ImmediateMdtConfig dataType.
      This <<dataType>> defines the configuration parameters of
@@ -783,6 +853,8 @@ module _3gpp-common-trace {
        -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:
@@ -840,6 +912,13 @@ module _3gpp-common-trace {
        - 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 {
@@ -864,6 +943,7 @@ module _3gpp-common-trace {
        enum M7;
        enum M8;
        enum M9;
        enum M10;
      }
      description "It specifies the UE measurements that shall be
        collected in an Immediate MDT job. The attribute is
@@ -1395,6 +1475,26 @@ module _3gpp-common-trace {
        measurements and applicable only for NR.";
      reference "Clause 5.10.6 of TS 32.422.";
    }
    
    leaf layerOneRsrpPeriodicity {
      type enumeration {
        enum 2 {value 0; }
        enum 3 {value 1; }
        enum 4 {value 2; }
        enum 5 {value 3; }
      }
      description "It defines the periodicity that the UE shall use for the  
        M10 measurements.";
    }
    
    list eventTriggerConfig {
      description "It specifies the event-triggered configuration used for M10 
        measurements.";
        max-elements 1;
        key idx;
        leaf idx { type uint32; }
      uses EventTriggerConfigGrp;
    }
  }

  grouping LoggedMdtConfigGrp {
@@ -2067,7 +2167,8 @@ module _3gpp-common-trace {
      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
@@ -2079,15 +2180,14 @@ module _3gpp-common-trace {
        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.
@@ -2103,14 +2203,15 @@ module _3gpp-common-trace {
        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.