Commit 2738ad84 authored by Jose Antonio Ordoñez Lucena's avatar Jose Antonio Ordoñez Lucena
Browse files

Update _3gpp-common-trace.yang

parent 450ed5ff

yang-models/_3gpp-common-trace.yang

+14 −13
Original line number Diff line number Diff line
@@ -1611,13 +1611,14 @@ module _3gpp-common-trace { 
    leaf-list ueCoreMeasurements {

      type string;

      description "List of 5GC UE level measurements identified by name. 

        allowedValues: The list may include 5GC UE level measurements 

        The list may include 5GC UE level measurements 

        defined in TS 28.558, or vendor specific measurements.

        

        For 5GC UE level measurements defined in TS 28.558, the name is constructed as follows:

        -	family.measurementName.subcounter for measurement type with specified subcounter

        -	family.measurementName.ALL for measurement type with all supported subcounters

        -	family.measurementName for measurement type without subcounters

        -	family for measurement family, including all measurement types and 

        -	'family.measurementName.subcounter' for measurement type with specified subcounter

        -	'family.measurementName.ALL' for measurement type with all supported subcounters

        -	'family.measurementName' for measurement type without subcounters

        -	'family' for measurement family, including all measurement types and 

        the associated subcounters under this family.

        For non-3GPP specified 5GC UE level measurements the name is defined elsewhere.";

    }
@@ -1777,20 +1778,20 @@ module _3gpp-common-trace { 
        attribute is applicable for both Trace and MDT. This attribute

        includes the ID type of the target as an enumeration and the ID value.



        The traceTarget shall be PUBLIC_ID in case of a Management Based

        The traceTarget shall be 'PUBLIC_ID' in case of a Management Based

        Activation is done to an SCSCFFunction (Serving Call Session Control Function) 

        or PCSCFFunction (Proxy Call Session Control Function). 

        The traceTarget shall be UTRAN_CELL only in case of the UTRAN cell traffic 

        The traceTarget shall be 'UTRAN_CELL' only in case of the UTRAN cell traffic 

        trace function.



        The traceTarget shall be E-UTRAN_CELL only in case of E-UTRAN cell

        The traceTarget shall be 'E-UTRAN_CELL' only in case of E-UTRAN cell

        traffic trace function.



        The traceTarget shall be NG-RAN_CELL only in case of NR cell

        The traceTarget shall be 'NG-RAN_CELL' only in case of NR cell

        traffic trace function.



        The traceTarget shall be either IMSI, IMEI or

        IMEISV if the Trace Session is activated to any of the following

        The traceTarget shall be either 'IMSI', 'IMEI' or

        'IMEISV' if the Trace Session is activated to any of the following

        ManagedEntity(ies):

        - HssFunction

        - MscServerFunction
@@ -1802,7 +1803,7 @@ module _3gpp-common-trace { 
        - ServingGWFunction

        - PGWFunction



        The traceTarget shall be either SUPI or IMEISV if the Trace Session

        The traceTarget shall be either 'SUPI' or 'IMEISV' if the Trace Session

        is activated to any of the followed ManagedEntity(ies):

        - AFFunction

        - AMFFunction
@@ -1816,7 +1817,7 @@ module _3gpp-common-trace { 
        - UDMFunction



        In case of signalling based MDT, the traceTarget attribute should

        be able to carry PUBLIC_ID, IMSI, IMEI, IMEISV or SUPI.

        be able to carry 'PUBLIC_ID', 'IMSI', 'IMEI', 'IMEISV' or 'SUPI'.



        In case of management based 5GC UE level measurements collection, 

        the traceTarget attribute shall be able to carry the corresponding