Content for  TS 32.401  Word version:  17.0.0

Void.

Measurement jobs can be administered by the EM according to the following stipulations. Creating a measurement job: Modifying a measurement job: Displaying a measurement job: Deleting a measurement job: Suspending/resuming a measurement job:

During its specified recording intervals, each measurement job produces a result at the end of the granularity period if it is not suspended. Performance Measurement File Format Definition TS 32.432 provides for each measurement type that is specified within the present document a description of the expected measurement result. Measurement results for all measurements of a particular measurement job are gathered in a single report at the end of the granularity period. The report may contain - in addition to the specific measurement results - fixed information, which is global for all measurement results associated with that measurement job, such as an identification of the involved network resources and a time stamp referring to the time at which the NE started collecting the measurement results. If measurement results are sent to the EM then the exact format may be vendor specific. For details about the standard file format for the transfer of measurement results to the NM via Itf-N Performance Measurement File Format Definition TS 32.432. Once the result reports have been generated, they shall be stored locally within the NE if so requested by the EM/system operator. The storage capacity and duration as well as the method how the data may be deleted from the NE will be implementation dependent. If some or all of the requested measurement data cannot be collected by a measurement job, this shall be indicated in the measurement report, cf. clause 5.4.1.5. In extreme cases, no report at all can be generated by the measurement job. This means that the destination of the result report (EM and/or NM) shall be capable of coping with missing or incomplete measurement reports.

During the recording intervals specified for a measurement job, scheduled measurement reports are generated at the end of each granularity period if the measurement job is not suspended. These reports can be transferred to the EM in either of two ways:

1. immediate notifications:
   • the reports are automatically forwarded to the EM at the end of the granularity period.
2. deferred retrieval:
   • the reports are stored locally in the NE, where they can be retrieved when required.

For each individual report, the transfer of measurement results in either one or both ways is to be established by the system operator, i.e. under the control of the EM. The actual control of the result transfer and the mechanisms applied may be implementation specific. Each implementation shall support a file transfer facility to an external OS (i.e. not supplied by the NE vendor), such as an NM. This facility shall be implemented using either the FTAM ISO 8571 [7], (T)FTP protocol or FTIRP([30]). This interface may be located either in the NEs or the EM, as chosen by the vendor. As a result, it may not at all be necessary to transfer measurement result reports to the EM, if:

• the NM interface is implemented in the NEs, and
• the Operator chooses to post-process measurement results only in the NM.

Details of the file format to be used on the NM interface can be found in Performance Measurement File Format Definition TS 32.432. The measurement report file conventions and transfer procedure are also specified in Performance Measurement File Format Definition TS 32.432. The results of the measurement job can be forwarded to the EM in either of two standard ways:

1. the scheduled result reports generated by the NE (notifications) can be sent to the EM as soon as they are available;
2. the reports can be stored in the NE (files) and transferred to or retrieved by the EM when required.

It shall be possible for the EM to specify the details for its result retrieval as a part of the measurement administration. Measurement results can be forwarded to the NM via a bulk transfer interface. It is an implementation option whether this interface resides in the EM or the NEs. Depending on the implementation, the control of the bulk transfer of measurement results to the NM may involve the EM and/or the NM. See Performance Measurement File Format Definition TS 32.432 for details. In a network with more than one OS (e.g. EM and NM) the data produced may be required by several OSs. It is therefore necessary to support the possibility for multiple destinations for transfer of data. All scenarios for the result transfer, as far as they are relevant for standardisation of 3GPP systems, are defined above. It should be noted that, depending on an Operator's needs, measurement results may have to be transferred to the EM only, the NM only, or both. Depending on a vendor's implementation, measurement results may be transferred to the NM directly from the NE or via the EM. This implies that not all of the result transfer options described above shall be implemented in all cases, however, those procedures that are implemented shall comply with the present document. A detailed specification of the measurement result transfer to the NM can be found in Performance Measurement File Format Definition TS 32.432.