Commit 290630f7 authored by scottma's avatar scottma Committed by ruiyue
Browse files

Update _3gpp-common-trace.yang

parent 60041545

yang-models/_3gpp-common-trace.yang

+33 −9
Original line number Diff line number Diff line
@@ -22,6 +22,7 @@ module _3gpp-common-trace { 
      Integration Reference Point (IRP);

      Information Service (IS)";



  revision 2023-02-15 { reference "CR-0232"; }

  revision 2022-04-27 { reference "CR-0159"; }

  revision 2021-10-18 { reference "CR-0139"; }

  revision 2021-07-22 { reference "CR-0137"; }
@@ -456,12 +457,20 @@ module _3gpp-common-trace { 
    leaf tjTraceRecordSessionReference {

      type string;

      mandatory true;

      config false;

      description "An identifier, which identifies the Trace Recording Session. 

        The attribute is applicable for both Trace and MDT.

        See the clause 5.7 of 3GPP TS 32.422 for additional details on the 

        allowed values.";

    }

    

    leaf traceRecordingSessionActive {

      type boolean;

      mandatory true;

      config false;

      description "Indicates whether a Trace Recording Session is active.";

    }



    leaf tjTraceReportingFormat {

      type enumeration {

        enum FILE_BASED;
@@ -1036,14 +1045,29 @@ module _3gpp-common-trace { 
        For details of management Trace Job activation/deactivation see clause

        4.1.1.1.2 of TS 32.422.

        

        The attribute tjJobType specifies the kind of data to collect. Dependent 

        on the selected type various parameters shall be available. The 

        attributes tjJobType, tjTraceReference, tjTraceRecordSessionReference, 

        tjTraceCollectionEntityAddress and tjTraceReportingFormat are mandatory 

        for all job types. If streaming reporting is selected for 

        tjTraceReportingFormat, tjStreamingTraceConsumerURI shall be present 

        additionally. The attribute tjPLMNTarget shall be present if trace 

        activation method is management based.

        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, TS 32.422 [30].

        

        The attribute traceRecordingSessionReference identifies a Trace 

        Recording Session within a Trace Session. Two different trace 

        sessions could e.g. be caused by two different trigger events. The 

        traceRecordingSessionReference is populated by the traffic node

        that initiates the Trace Recording Session, TS 32.422 [30]. 

        

        The attribute traceRecordingSessionActive indicates whether a Trace 

        Recording Session is active or not.

        

        The attribute tjJobType specifies the kind of data to collect. 

        Dependent on the selected type various parameters shall be available.

        The attributes tjJobType, tjTraceReference, 

        tjTraceRecordSessionReference, tjTraceCollectionEntityAddress and 

        tjTraceReportingFormat are mandatory for all job types. If streaming 

        reporting is selected for tjTraceReportingFormat, 

        tjStreamingTraceConsumerURI shall be present additionally. The 

        attribute tjPLMNTarget shall be present if trace activation method is 

        management based.



        For the different job types the attributes are differentiated as follows:

        - In case of TRACE_ONLY additionally the following attributes shall be