Commit ab1de0af authored by lengyelb's avatar lengyelb Committed by lengyelb
Browse files

CR-0104 S5-213476 PerMetricJob desc updates

parent 83e0b97f

yang-models/_3gpp-common-measurements.yang

+269 −247
Original line number Diff line number Diff line
@@ -53,6 +53,7 @@ module _3gpp-common-measurements { 
      Integration Reference Point (IRP);

      Information Service (IS)";



  revision 2021-07-22 { reference "CR-xxxx"; }

  revision 2020-11-06 { reference "CR-0118"; }

  revision 2020-09-04 { reference "CR-000107"; }

  revision 2020-06-08 { reference "CR-0092"; }
@@ -60,7 +61,7 @@ module _3gpp-common-measurements { 
  revision 2020-03-11 { reference "S5-201581, SP-200229"; }

  revision 2019-11-21 { reference "S5-197275, S5-197735"; }

  revision 2019-10-28 { reference "S5-193516"; }

  revision 2019-06-17 { }

  revision 2019-06-17 { reference " "; }



  grouping ThresholdInfoGrp {

    description "Defines a single threshold level.";
@@ -167,9 +168,8 @@ module _3gpp-common-measurements { 
        min-elements 1;

        description "Performance metrics include measurements defined in

          TS 28.552 and KPIs defined in TS 28.554. Performance metrics can

          also be those specified by other SDOs or vendor specific metrics. 

          Performance metrics are identfied with their names. A name can also 

          identify a vendor specific group of performance metrics.

          also be specified by other SDOs or be vendor specific.

          Performance metrics are identfied with their names.



          For measurements defined in TS 28.552 the name is constructed as

          follows:
@@ -179,7 +179,10 @@ module _3gpp-common-measurements { 
          - 'family' for measurement families



          For KPIs defined in TS 28.554 the name is defined in the KPI

          definitions template as the component designated with e).";

          definitions template as the component designated with e).



          A name can also identify a vendor specific performance metric or a

          group of vendor specific performance metrics.";

      }



      leaf-list granularityPeriods {
@@ -396,8 +399,7 @@ module _3gpp-common-measurements { 
        can be name-contained by SubNetwork, ManagedElement, or ManagedFunction.



        To activate the production of the specified performance metrics, a MnS

        consumer needs to create a PerfMetricJob instance on the MnS producer 

        and ensure that the adminState is sUNLOCKED>. 

        consumer needs to create a PerfMetricJob instance on the MnS producer.

        For ultimate deactivation of metric production, the MnS consumer should

        delete the job to free up resources on the MnS producer.
@@ -406,7 +408,7 @@ module _3gpp-common-measurements { 
        producer may disable metric production as well, for example in overload

        situations. This situation is indicated by the MnS producer with setting

        the operational state attribute to disabled. When production is resumed

        the operational state is set again to enabled.

        the operational state is set back to enabled.



        The jobId attribute can be used to associate metrics from multiple

        PerfMetricJob instances. The jobId can be included when reporting
@@ -446,6 +448,26 @@ module _3gpp-common-measurements { 
        file location by the MnS producer, file-based reporting with selection

        of the file location by the MnS consumer and stream-based reporting.



        For file-based reporting, all performance metrics that are produced

        related to a 'PerfMetricJob' instance for a reporting period shall be

        stored in a single reporting file.



        When the administrative state is set to 'UNLOCKED' after the creation

        of a 'PerfMetricJob' the first granularity period shall start. When

        the administrative state is set to 'LOCKED' or the operational state

        to 'DISABLED', the ongoing reporting period shall be aborted, for

        streaming the ongoing granularity period. When the administrative

        state is set back to 'UNLOCKED' or the operational state to 'ENABLED'

        a new reporting period period shall start, in case of streaming a new

        granularity period.



        Changes of all other configurable attributes shall take effect only at

        the beginning of the next reporting period, for streaming at the

        beginning of the next granularity period.



        When the 'PerfMetricJob' is deleted, the ongoing reporting period shall

        be aborted, for streaming the ongoing granularity period.



        A PerfMetricJob creation request shall fail, when the requested

        performance metrics, the requested granularity period, the requested

        repoting method, or the requested combination thereof is not supported