This clause describes all basic functions to allow the system operator to have measurement data collected by the NEs and to forward the results to one or more OS(s), i.e. EM and/or NM. 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.
Building on the concept established in
clause 4 of the present document, the following clauses further specify the requirements that all standard GSM, UMTS and LTE implementations shall comply to.
The Performance Management concept as applicable in the present document is based on the general framework for 3G-telecom management defined in
TS 32.101 and
TS 32.102. A particular feature of this general framework is the existence of the fully standardised interface labelled
"Itf-N", that connects the network with the Network Manager (NM). In the context of Performance Management, Itf-N can be used for:
-
the transfer of files containing performance measurement result data generated in the network;
-
the emission of "performance alarms" (notifications).
It should be pointed out that, on the network side, Itf-N may be implemented either in the NEs or in the EM, according to vendor choice.
As an example,
Figure 1 outlines this concept in the context of the UTRAN.
As the O&M functions for NodeB are partitioned into Logical and Implementation Specific O&M (see
TR 32.800), it should be understood that the functionalities described in the present document are completely within the scope of Implementation Specific O&M. This implies that no information pertaining to measurement administration and result transfer, as described here, is exchanged between the RNC and NodeB via the Iub interface. Such information may, however, be sent or received by the NodeB over the Iub physical bearer, see
TS 25.442.
The basic requirement from an NE for measurements is to collect data according to the definition of the measurement jobs and to provide results to at least one OS (EM and/or NM). The data collected in the NE shall be made available for collection by or transfer to the OS(s) according to the schedule defined by the measurement job parameters. The NE shall be able to supply the result data at least to the NM if the Itf-N is implemented in the NEs, result provision from the NE to the EM is optional in this case. The NE shall be able to provide the result data to the EM if the Itf-N is implemented in the EM.
The EM shall be able to administer the measurements, e.g. create/delete measurement jobs and define their schedules. If the measurement results are transferred from the NEs to the EM, then the EM can control:
-
the immediate ("real time") transfer of scheduled reports from the NE to the EM;
-
the storage of scheduled reports in the NE; and
-
deferred retrieval by the EM of scheduled reports stored in the NE.
In GSM, the optional Q3 interface specified in
TS 52.402 can be used to perform these functions, while in UMTS, they are executed through a proprietary interface. Depending on the implementation option chosen for the Itf-N, the EM and/or NM may be involved in the control of the measurement result transfer to the NM.
The basic functions of the NM are beyond the scope of the present document. However, any NM that supports the network functions as described here must provide the NM side of the Itf-N, and the ability to handle the measurement result data that it receives, according to the file format(s) specified in the Performance Measurement File Format Definition
TS 32.432. The measurement result data may then be used in its original form or post-processed according to the system operator requirements. It is further anticipated that NM systems will have sophisticated functions for the management, preparation and presentation of the measurement result data in various forms.
The following clause summarises the measurement administration functions required in GSM, UMTS and LTE networks. They are then specified in more detail in clauses 5.x below.
(Performance) measurement administration functions allow the system operator, using functions of the EM, to determine measurement data collection in the network and forwarding of the results to one or more OS(s).
(Performance) measurement administration functions cover:
-
measurement data collection requirements:
-
measurement types. Corresponds to the measurements as defined in TS 52.402, TS 32.405, TS 32.406, TS 32.407, TS 32.408, TS 32.409, TS 32.425, TS 32.426, 32.452 [39] , 32.453 [40] , TS 28.402 and TS 28.403 or defined by other standards bodies, or manufacturer defined measurement types;
-
measured network resources. The resource(s) to which the measurement types shall be applied have to be specified, e.g. one or more NodeB(s);
-
measurement recording, consisting of periods of time at which the NE is collecting (that is, making available in the NE) measurement data.
-
measurement reporting requirements:
-
this allows the system operator to specify the measurement related information to be reported, if required (e.g. omitting zero valued counts).. The frequency at which scheduled result reports shall be generated also has to be defined, if it may deviate from the granularity period. Particular functions, which exceed the requirements set out in the present document, are provided if the optional Q3 interface specified in TS 52.402 is implemented for GSM.
-
measurement result transfer requirements:
-
The result transfer requirements in the present document are limited to the file based Itf-N, used to forward the measurement results to the NM. If ItF-N is implemented in the EM, then measurement results can be transferred from the NE to the EM, and/or they are stored locally in the NE and can be retrieved when required. If Itf-N is implemented in the NEs, then the PM result files are sent directly from the NE to the NM, involving control by the EM as required, The EM shall support all administration functions necessary to fulfil the above result transfer requirement.;
-
measurement results can be stored in the network (NEs or EM, depending on implementation option chosen for Itf-N) for retrieval by the NM when required.
A (performance) measurement job, covers the measurement data collection as described in point 1 above. If the Q3 interface for GSM is implemented, it also covers the measurement reporting requirements, as described in point 2 above. In UMTS, the reporting requirements may be covered by the measurement job, or they may be administered per NE, per management domain, or per EM, as chosen by the vendor. It is up to the implementation whether requirements for the result transfer or the local storage of results are specified within the measurement job, particularly since the use of standard protocols, such as FTP, is foreseen.
A measurement job can be created, modified, displayed or deleted by the EM. In addition, measurement job activities in the NE can be suspended and resumed on request of the EM.
The system operator shall specify the required measurement parameters upon initiation of a measurement job. These parameters consist of, among others, recording schedule, granularity, and measurement type(s), as listed above.
A standard set of measurements that generate the required data is defined in
TS 52.402 for GSM, in 3GPP
TS 32.405,
TS 32.406,
TS 32.407,
TS 32.408 for UMTS and combined GSM/UMTS systems,in
TS 32.409 for IMS, in
TS 32.425 for E-UTRAN, in
TS 32.426 for EPC, in
TS 32.452 for Home Node B (HNB) Subsystem (HNS) and in TS.32.453 [40] for Home enhanced Node B (HeNB) Subsystem (HeNS) , in
TS 28.402 for Evolved Packet Core (EPC) and non-3GPP access Interworking System and in
TS 28.403 for Wireless Local Area Network (WLAN). However, a significant number of additional measurements is expected from real implementations. These will mainly consist of measurements for the underlying technologies, which are not 3GPP specific, such as ATM or IP, but is also due to specific vendor implementations. While the NM interface (Itf-N) for result transfer of both standard and non-standard measurements is fully standardised Performance Measurement File Format Definition
TS 32.432, the interface between EM and NE is only standardised in functional terms. In UMTS, implementation details of this interface are vendor specific. In GSM, it may be implementation specific or implemented in compliance with the OSI interface specified in
TS 52.402.
To be completed in a later Release.