Update _3gpp-common-qmcjob.yang

      Integration Reference Point (IRP);

      Information Service (IS)";

  revision 2024-11-05 { reference "CR-xxxx"; } 

  revision 2024-04-04 { reference CR-0334; } 

  revision 2023-09-18 { reference CR-0271 ; } 

  revision 2023-02-14 { reference "CR-0234"; }

    list areaScope {

      key "idx";

      leaf idx { type uint32 ; }

      description "It specifies the area where data shall be collected. 

        List of eNB/list of gNB/eNB/gNB for RLF or RCEF.

        List of cells or Tracking Area for QMC.          

        Cell, TA, LA, RA are mutually exclusive.";

      reference "Clause 5.10.2 of 3GPP TS 32.422";

      description "It defines the area scope of QoE, which is specified

       in clause 5.4 of TS 28.405.;"  

      uses trace3gpp:AreaScopeGrp;      

    }

       producer. For details of Management Based Activation of QoE Measurement 

       Collection see clause 4.5 and for details of Signalling Based 

       Activation of QoE Measurement Collection see clause 4.6 of TS 28.405. 

       The attributes areaScope and pLMNTarget are only relevant when 

       The attribute  pLMNTarget is only relevant when 

       Management Based Activation is used and the attribute qoETarget is 

       only relevant when Signalling Based Activation is used. All other 

       attributes are common for both Management Based Activation and 

       Signalling Based Activation.

       The areaScope attribute defines the area scope of QoE, which is 

       specified in clause 5.4 of TS 28.405.

       When a MnS consumer wishes to deactivate a QMC Job, the MnS consumer 

       shall delete the corresponding QMCJob instance. 

       NOTE:  If the reporting is ongoing, when a request to delete a QMCJob 

       jobId can be used to associate  multiple QMCJob instances. For example, 

       it is possible to configure the same jobId value for multiple QMCJob 

       instances required to produce the data (e.g. Streaming services and 

       MTSI reports) for a specific network analysis.

       The QoE Measurement Collection provides capability for collecting QoE 

       information from:

       - UEs which are in the specified area in case of Management Based 

       Activation or 

       - an individual UE in case of Signalling Based Activation.

       The QoE Measurement Collection enables collection of application layer 

       from the UE for specified end user service type. The supported service 

       types are:

       - Streaming services, see TS 26.247. 

       - MTSI services, see TS 26.114.

       - VR services, see TS 26.118.

       A QMCJob instance represents the job for collecting QoE measurements 

       according to the job parameters. For details of the QoE measurement 

       collection configuration parameters see clause 5 of TS 28.405. A QMCJob 

       instance can be name-contained by SubNetwork or ManagedElement. 

       A QMC Job is activated by creating a QMCJob object instance in the 

       MnS producer. For details of Management Based Activation of QoE 

       Measurement Collection see clause 4.5 and for details of Signalling 

       Based Activation of QoE Measurement Collection see 

       clause 4.6 of TS 28.405. The attributes areaScope and pLMNTarget are 

       only relevant when Management Based Activation is used and the 

       attribute qoETarget is only relevant when Signalling Based Activation 

       is used. All other attributes are common for both Management Based 

       Activation and Signalling Based Activation.

       When a MnS consumer wishes to deactivate a QMC Job, the MnS consumer 

       shall delete the corresponding QMCJob instance. 

       NOTE:  If the reporting is ongoing, when a request to delete a QMCJob 

       instance is received, the reporting does not end. The QMCJob instance 

       is deleted, when the last reporting for the QMC Job expires.

       The jobId attribute presents the job identifier of a QMCJob instance. 

       The jobId can be used to associate  multiple QMCJob instances. 

       example, it is possible to configure the same jobId value for multiple 

       QMCJob instances required to produce the data (e.g. Streaming services 

       and MTSI reports) for a specific network analysis.";

       MTSI reports) for a specific network analysis.";

      key id;

      uses top3gpp:Top_Grp;

      container attributes {