3 Performance management requirements

12.043GPPPerformance data measurementsTS

3.1 Introduction

This subclause describes all basic functions to allow the system operator to collect measurement data from the NEs and to forward the results to the OS. All functions are gathered to provide the system operator with the means to administer, plan, execute measurements and to store and evaluate the measurement results.

3.1.1 Basic functions

The performance management concept as applicable in this specification is outlined in figure 1 and is based on the general framework for PLMN management as outlined in GSM 12.00 [8] and GSM 12.01 [9].

Figure 1: Performance management concept

The basic requirement from an NE for measurements is to collect data according to the definition of the measurements and to return results to the OS.

The OS shall be able to administer the measurements and to receive and store the collected data. The measurements that will generate this data are defined in annex B. This data may be used in its original form or processed according to the system operator requirements.

The data collected in the NE will be made available according to measurement parameters (scheduled reports), or on request from the OS (request current results).

Using OSI standardised mechanisms, the OS can control:

– the transfer of scheduled reports from the NE to the OS;

– the storage of scheduled reports in the NE; and

– deferred retrieval of scheduled reports stored in the NE.

The present document does not address the latter aspects in full detail, as general and generic functions apply. It does, however, describe the use of these functions in the PLMN measurement system.

As mentioned in subclause 2.2.5, measurement result presentation is considered to be a PLMN Operator concern. It is therefore not a subject of the present document. The format of the returned measurement results from OS point of view, however, will be ASN.1 using basic encoding rules.

3.1.2 Measurement administration

(Performance) measurement administration functions allow the system operator to determine measurement data collection and forwarding to an OS.

A (performance) measurement concept covers:

1) measurement data collection requirements:

Measurement types. Corresponds to the measurements as defined in annex B;

Measured network resources. The resource(s) to which the measurement types shall be applied have to be specified, e.g. one or more BTS(s);

Measurement recording, consisting of periods of time at which the NE is collecting (that is, making available in the NE) measurement data.

2) measurement reporting requirements:

– the measurement related information to be reported and the layout of this report have to be specified as part of the measurement. The frequency at which scheduled result reports shall be generated has to be defined.

3) measurement result transfer requirements:

– measurement results can be transferred from the NE to the OS according to the measurement parameters, and/or they are stored in the NE and can be retrieved by the OS when required. Current measurement results can be transferred from the NE to the OS on explicit OS request.

A (performance) measurement job, covers the measurement data collection and measurement reporting requirements, as described in points 1 and 2 above. A measurement job can be created, modified, displayed or deleted in the OS. In addition, measurement job activities can be suspended and resumed, and, if the measurement job is not suspended, the current values of the measurements that are included in the measurement job can be requested by the OS at any time, independent of the measurement parameters.

The system operator shall specify the required measurement parameters on initiation of a measurement job. These parameters consist of, among others, recording schedule, granularity, and measurement type(s).

3.2 Measurement jobs

When defining a measurement job, the following aspects have to be considered.

3.2.1 Measurement job characteristics

3.2.1.1 Measurement types

Every measurement job consists of one or more measurement types (defined in annex B), for which it collects measurement data. The measurement type(s) contained in a job may apply to one or more network resources of the same type, e.g. a measurement job may be related to one or several BTSs. A measurement job will only produce results for the measurement type(s) it contains.

3.2.1.2 Measurement schedule

The measurement schedule specifies the time frame during which the measurement job will be active. The measurement job is active as soon as the starttime – if supplied in the schedule – is reached. The system shall support a job starttime of up to at least 90 days from the job creation date. If no starttime is provided, the measurement job shall become active immediately. The measurement job remains active until the stoptime – if supplied in the schedule – is reached. If no job stoptime is specified the measurement job will run indefinitely and can only be stopped by manual intervention.

The time frame defined by the measurement schedule may contain one or more recording intervals. These recording intervals may repeat on a daily and/or weekly basis and specify the time periods during which the measurement data is collected within the NE. A recording interval is identified by an interval starttime and an interval endtime which lie between 00.00 and 24.00 hours, aligned on granularity period boundaries. Thus the length of a recording interval will be a multiple of the granularity period (if non-zero). For a single measurement type it shall be possible to specify several measurement jobs with different recording intervals as long as these intervals do not overlap. If it is required that a measurement type be observed by multiple measurement jobs with overlapping schedules than the system shall support multiple instances of that measurement type.

3.2.1.3 Granularity period

The granularity period is the time between the initiation of two successive gatherings of measurement data. Required values for the granularity period are 5 minutes, 15 minutes, 30 minutes, 1 hour. The minimum granularity period is 5 minutes in most cases, but for some measurements it may only make sense to collect data in a larger granularity period. The granularity period shall be synchronised on the full hour and its value is not required to be changeable during the lifetime of the job. If the specified granularity period is zero then the measurement data can only be gathered on request from the OS.

3.2.1.4 Measurement reporting

Scheduled measurement reports are produced at the end of each granularity period. All reports generated by a particular measurement job have the same layout and contain the information requested by the system operator. This information may consist of:

– an identification of the measurement job that generated the report;

– an identification of the involved measurement type(s) and the measured network resource(s) (e.g. BTS);

– a time stamp, referring to the end of the granularity period;

– for each measurement type, the result value and an indication of the validity of the result value;

– an indication that the scan is not complete, and the reason why the scan could not be completed.

Whatever method of data compression is selected, the returned measurement result shall not be compromised, i.e. it shall not result in loss of any necessary information.

Some flexibility is provided in order to limit the information that is to be reported by the NE, reducing the amount of data to be transferred between NE and OS. Options that can be selected are:

– suppressing the reporting of the identification of the observed network resource;

– reporting the measurement results in an agreed order, so an explicit identification of the associated measurement type is not required in the measurement reports;

– suppressing multiple reporting of measurement results when they are the same across all observed network resources.

3.2.2 Measurement job state and status attributes

According to the OSI systems management concept, the state of a resource is reflected in indicators (attributes). Status attributes are provided to qualify these state attributes. Full details are provided in ITU-T Recommendation X.731 [16]. As for a measurement job, the following information is provided:

Administrative state: The administrative state attribute allows the system operator to permit or prohibit administratively the execution of the measurement job.

Operational state: The operational state attribute reflects the operability of the measurement job.

Availability status: The availability status attribute denotes particular conditions applicable to the measurement job. It indicates:

– whether or not the measurement job is collecting measurement data according to its schedule;

– if, for whatever reason, some of the requested measurement data cannot be collected by the measurement job, in particular whether the measurement schedule inhibits the collection of measurement data.

3.2.3 Measurement job administration

Creating a measurement job: On creation of a measurement job, all information has to be supplied in order to collect the required data from the selected network resources as specified by the measurement job characteristics (see subclause 3.2.1).

Modifying a measurement job: In general, the modification of measurement job parameters may be requested by the OS during the lifetime of a measurement job when the job is suspended (explained below).

Displaying a measurement job: The system operator shall be able to get a list of all measurements that are currently defined, together with all available actual information as stored in the NE. This information consists of the data that is supplied on creation/modification and the actual state and status information of the measurement job.

Deleting a measurement job: A measurement job is automatically deleted by the system when it reaches the job endtime and all scheduled or explicitly requested measurement reports have been generated. A created measurement job can also be deleted by manual intervention at any time. When deleted, the measurement process associated with the job is stopped, and all allocated resources are freed.

Suspending/resuming a measurement job: On normal operation, the measurement job collects measurement data within the NE according to the actual values of the measurement job parameters. However, the system operator may decide for some reason to discard temporarily the collection of measurement data (e.g. in case of system overload or congestion, measurement results not used, …). The system operator therefore is able to suspend a defined measurement job at any time, using the Administrative State. This implies that the measurement job definition remains in the system, but that no measurement gathering activities are performed for this job. When the measurement job is resumed, measurement data collection is started again at the next granularity period within the measurement schedule.

Requesting the current measurement result values of a measurement job: The system operator may for some reason be interested in the current values of the measurement results of a particular measurement job, independently of the scheduled data collection and subsequent reporting, e.g. for tracing the increment of some of the counters. To this aim, the system operator is able to request the actual values of the measurement results for the same network resources as defined in the measurement job. The current results are returned in the reply message for this request in a format which is identical to scheduled reports that are generated by the measurement job at the end of the granularity period. Any such request does not affect the measurement job, and may only be issued when the measurement job is active and not suspended, otherwise an error will be returned.

3.3 Measurement results

3.3.1 Measurement result characteristics

Each measurement produces a result at the end of the granularity period or on request of the OS, see above. Annex B provides for each measurement type a description of the expected measurement result.

Scheduled reports: Measurement results for all measurements of a particular measurement job are gathered in a single report at the end of the granularity period. The system operator may to some extent determine in what format the measurement results are to be reported, since reporting requirements can be included in the measurement job definition. The report may contain, in addition to the specific measurement results, fixed information that 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.

Request current results: On receipt of the request, the appropriate result values are produced, and a reply to the request is generated. The measurement job specific information contained in the reply and its format is identical to scheduled reports.

3.3.2 Transfer of measurement results

The measurement results are contained in scheduled reports and are generated by the measurement job according to the measurement job definition parameters, or they are sent to the OS as a result of a "request current results"-operation.

Scheduled measurement reports: Are generated at the end of each granularity period if the measurement job is not suspended. They can be transferred to the OS in two ways:

1) immediate notifications:

– The reports are automatically forwarded to the OS 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. These requirements are covered completely by OSI standardised functions (Event Report Management Functions ITU-T Recommendation X.734 [17], Log Control Functions ITU-T Recommendation X.735 [18], CMIS, ITU-T Recommendation X.710 [13], FTAM, ISO 8571 [21], SNMP Recommendation IETF RFC 1157 [24], FTP Recommendation IETF RFC 959 [28] ), Common Management Functions that are provided in GSM 12.00 [8] and the generic services that are provided in annex D of the present document.

Request current results: Upon receipt of the request, the NE will generate an appropriate reply and send it immediately to the OS. There is no further control of the forwarding of the reply and no storage of the reply in the NE.