Commit 593007e2 authored by scottma's avatar scottma Committed by sunse
Browse files

Update _3gpp-common-trace.yang

parent 19069b12
Loading
Loading
Loading
Loading
+38 −11
Original line number Diff line number Diff line
@@ -471,7 +471,24 @@ module _3gpp-common-trace {
        The attribute is applicable for both Trace and MDT.";
    }

    leaf traceReportingFormat {
    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;
        enum STREAMING;
@@ -1048,16 +1065,26 @@ module _3gpp-common-trace {
        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.
        
        The attribute jobType specifies the kind of data to collect. Dependent 
        on the selected type various parameters shall be available. The 
        attributes jobType, traceReference, 
        traceCollectionEntityAddress and traceReportingFormat are mandatory 
        for all job types. If streaming reporting is selected for 
        traceReportingFormat, streamingTraceConsumerURI shall be present 
        additionally. The attribute PLMNTarget shall be present if trace 
        activation method is management based.
        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