Wcdma Ran Performance Management Ru30

Nokia Siemens Networks WCDMA RAN, Rel. RU30, Operating Documentation, Issue 01

WCDMA RAN Performance Management

DN70352185

Issue 04BApproval Date 2010-12-09

Confidential

2 DN70352185Issue 04B


Id:0900d8058081f1b4Confidential

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright Nokia Siemens Networks 2010. All rights reserved

f Important Notice on Product Safety Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Span-nung. Einige Teile knnen auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverlet-zungen und Sachschden fhren.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.

DN70352185 Issue 04B

3



Table of contentsThis document has 27 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1 Changes in performance management . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 RU30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 RU20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.3 RU10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.4 RAS06 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 Description of performance management . . . . . . . . . . . . . . . . . . . . . . . . 9

3 Architecture of performance management. . . . . . . . . . . . . . . . . . . . . . . 103.1 Architectural roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4 Performance data management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134.2 Performance data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134.2.1 Radio network measurement data provided by RNC. . . . . . . . . . . . . . . 144.2.2 Transport and HW measurement data provided by IPA-RNC . . . . . . . . 144.2.3 Transport and HW measurement data provided by mcRNC . . . . . . . . . 154.3 Data collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164.4 Data storage and usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164.5 Alarms for PM data transfer failures . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

5 Measurement administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185.1 Centralised measurement administration . . . . . . . . . . . . . . . . . . . . . . . 185.2 Local measurement administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

6 Collection of key counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

7 Key performance indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217.1 KPI calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

8 Threshold monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

9 Optional functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

10 Features per release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

11 Management data for performance management . . . . . . . . . . . . . . . . . 2611.1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2611.2 Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2611.3 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

12 Limitations and restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4 DN70352185Issue 04B



List of figuresFigure 1 WCDMA RAN performance management architecture (with IPA-RNC). 10Figure 2 WCDMA RAN performance management architecture (with mcRNC) . . 11Figure 3 Radio network measurements provided by RNC . . . . . . . . . . . . . . . . . . 14Figure 4 Transport and HW measurements provided by IPA-RNC . . . . . . . . . . . 15Figure 5 Transport and HW measurements provided by mcRNC. . . . . . . . . . . . . 15Figure 6 KPI calculation in the O&M mediator. . . . . . . . . . . . . . . . . . . . . . . . . . . . 21


5



List of tablesTable 1 Definition of used Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Table 2 Features per release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Table 3 RAN1161: Alarms for PM Measurement Data Transfer Failures . . . . . 26

6 DN70352185Issue 04B


Id:0900d8058081f4a6Confidential

Summary of changes

Summary of changes Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.

Changes between issues 04B (2010-12-09, WCDMA RAN RU30) and 04A DRAFT (2010-10-06, WCDMA RAN RU30)

4 Performance data management: CPICH Quality measurement added in the Radio network measurements

provided by RNC figure ATM VCC Bundle measurement added in the Transport and HW measurements

provided by IPA-RNC figure Section Transport and HW measurement data provided by mcRNC added Information on the mcRNC measurements added in the Radio network mea-

surement data provided by RNC section

Changes between issues 04A DRAFT(2010-10-06, WCDMA RAN RU30) and 04 DRAFT (2010-05-31, WCDMA RAN RU20)

3 Architecture of performance management: Figure 1 WCDMA RAN performance management architecture (with IPA-RNC)

updated Figure 2 WCDMA RAN performance management architecture (with mcRNC)

added Section OMS added

4 Performance data management: Section Transport and HW measurement data provided by RNC updated

5 Measurement administration Section Local measurement administration updated

6 Collection of key counters section updated 8 Threshold monitoring

Section Setting and activating thresholds in the RNC updated 10 Features per release

Table Features per release updated


7

WCDMA RAN Performance Management Changes in performance management

Id:0900d80580820142Confidential

1 Changes in performance management This chapter describes new, modified, and removed functions as compared to earlier releases.

1.1 RU30New functions in RU30RAN1438: Automatic Object List Update in RNC Measurements.

Modified functions in RU30No changes.

Removed functions in RU30No changes.

1.2 RU20New functions in RU20FlexiBTS Transport measurements can be managed with NetAct.

Modified functions in RU20No changes.


1.3 RU10New functions in RU10No changes.

Modified functions in RU10Measurement administration was modified because new features RAN1188: Pre-Aggregation of RCPM Data in RNC and RAN1214: Increased Monitoring Capacity for VCC Measurements were introduced.


1.4 RAS06New functions in RAS06RAN1160: Collection of Key Counters.

RAN1161: Alarms for PM Data Transfer Failures.

Modified functions in RAS06No changes.

8 DN70352185Issue 04B



Changes in performance management

Removed functions in RAS06No changes.


9

WCDMA RAN Performance Management Description of performance management

Id:0900d805808201c1Confidential

2 Description of performance managementPerformance management (PM) consists of processing, storing, and administering of performance-related statistical data. This is required before this data can be further used by various network and service management tools. The performance management includes the following:

Performance Data Management Measurement Administration Collection of Key Counters Key Performance Indicators (KPI) Threshold MonitoringThe actual tools are not described in detail here. For further information, see Managing and Viewing RNC Measurements, Monitoring and measuring AXC in Operating and Maintaining AXC, and the NetAct Product Documentation for Reporting, Monitoring and Optimization Functionality.

The contents of performance management statistics are described in RNC Counters RNW Part, RNC Counters Transport and HW Part, WBTS Counters, and AXC Coun-ters.

10 DN70352185Issue 04B


Id:0900d8058081f473Confidential

Architecture of performance management

3 Architecture of performance management The performance management function is distributed across the network, as illustrated in the following figure.

Figure 1 WCDMA RAN performance management architecture (with IPA-RNC)


11

WCDMA RAN Performance Management Architecture of performance management


Figure 2 WCDMA RAN performance management architecture (with mcRNC)

3.1 Architectural rolesNetActNetAct consolidates data from different data producers across the network, and provides access to this data in a consistent format through different tools and interfaces.

NetAct offers a centralized administrative function for most of the data collection.

RNCThe Radio Network Controller (RNC) collects statistics from its own units and interfaces, and from data reported via external interfaces, for example, Iub.

The RNC also provides some specific functions for data processing, for example, threshold monitoring.

BTSThe BTS collects statistics about the BTS-related functions and resources, and sends them to the O&M mediator and NetAct for further processing.

12 DN70352185Issue 04B



Architecture of performance management

AXCThe ATM cross-connection (AXC) collects statistics about AXC-related functions and resources, and makes them available for the NetAct data collection.

Element ManagersElement managers provide element-specific administrative capabilities and some methods for viewing the collected statistics locally.

OMSThe OMS is acting as an O&M mediator. It is responsible for collecting the PM report files from the distributed NEs, concentrating them into larger files, buffering in a tempo-rary file storage, and forwarding to NetAct PM database for central storage of the PM data.


13

WCDMA RAN Performance Management Performance data management

Id:0900d8058081fd70Confidential

4 Performance data management

4.1 IntroductionPerformance data refers to statistics about network performance, for example, Radio Access Bearer (RAB) setup attempts. The data is presented as counters or performance indicators that are grouped into administrative entities called measurements.

Performance data management includes collecting, transferring, storing, and to some extent, processing of measurements. This is required in order to make the data available for the various end-user tools for different purposes.

The statistics are generated by data producers that are distributed across the network. RAN performance management covers the following:

RNC statistics BTS statistics AXC statisticsThe data, produced in different places and in various formats, is stored and consolidated in NetAct for network-wide use and availability.

The actual data contents are described in RNC Counters RNW Part, RNC Counters Transport and HW Part, WBTS Counters, and AXC Counters.

4.2 Performance dataPerformance data is provided periodically as statistics about network performance. This data is collected in counters, which are grouped into measurements for administration purposes.

The following table describes the most important terms used here and in 3GPP docu-mentation.

Measurement data are provided for the following two major areas:

Radio network measurements Transport and Hardware measurements

NSN term Definition Nearest 3GPP term

Measurement, Measurement type

The administrative unit that activates or deactivates a group of PM counters.

Measurement family

PM counter PM counters that count either defined events, or samples of specific situations, or real measured values.

Measurement type, Measurement sub type

Key Perfor-mance Indica-tor (KPI)

A performance indicator that has a high value for the operator. KPI is calculated as a function of one or more counters.

Key Performance Indi-cator (KPI)

Table 1 Definition of used Terms

14 DN70352185Issue 04B



Performance data management

4.2.1 Radio network measurement data provided by RNCRadio network measurements by the RNC provide statistical information on the quality of service (QoS), resource usage, radio connection, mobility, and signaling events within the radio network.

Radio network measurements are listed in the pyramid of the following figure. For more detailed measurement and counter information, see RNC Counters RNW Part.

g The mcRNC provides the same radio network measurements as the IPA-RNC.

Figure 3 Radio network measurements provided by RNC

4.2.2 Transport and HW measurement data provided by IPA-RNCThe IPA-RNC Transport and HW measurements provide statistical information on trans-port network signaling, ATM/IP transport, DSP resources, transport network L1 trans-mission, and RNC computer units.

Measurements that describe the transport network and the RNC computer unit perfor-mance are listed in the pyramid of the following figure. For more detailed measurement and counter information, see RNC Counters Transport and HW Part.

All the newly added/deleted RNC transport objects are updated dynamically in the measured object list. This function is activated if the ALL-objects parameter was set in the measurement administration.


15



Figure 4 Transport and HW measurements provided by IPA-RNC

4.2.3 Transport and HW measurement data provided by mcRNCThe mcRNC Transport and HW measurements are listed in the following figure.

Figure 5 Transport and HW measurements provided by mcRNC

g In case of mcRNC, instead of computer units (plates), the application SW is divided into functional units like: CSPU, USPU, CFCP. Each instance of a functional unit is assigned to a specific Octeon multi-core processor.

For more detailed measurement and counter information, see RNC Counters Trans-port and HW Part.

16 DN70352185Issue 04B



Performance data management

4.3 Data collectionMost of the statistics from the whole network can be collected in the NetAct. The RNC PM data is mediated by the Operation and Maintenance Server (OMS). The RNC collects the data from internal data producers and the OMS prepares it for transfer to the NetAct.

The data transfer interface between the OMS and the NetAct uses measurement data files, notifications, and scheduled file queries. The primary method for collecting RNC data is based on a notification mechanism. The OMS notifies NetAct about the data ready to be transferred, then the NetAct handles the actual transfer and, for example, the related acknowledgements and transfer state.

The interface includes various recovery mechanisms. There is also a scheduled file query that ensures the proper transfer of all data, even if the notifications are temporarily blocked, for example, due to software upgrades.

The BTS data is also mediated through the OMS in a similar manner, but AXCs are handled as separate entities, because of the interfaces and their role in the network. NetAct has a direct PM data collection interface towards the AXCs, and the data collec-tion is always initiated by the NetAct. NetAct supports collection of measurements from a predefined set of counters from the AXCs, from a limited area or number of network elements.

4.4 Data storage and usageThe main data storage is in the NetAct, which provides a network-wide view of the sta-tistics. There are several options for storing the data. Typically, the data is stored as such for a relatively short period, for example, for a week or two. It can also be aggre-gated over time or network dimensions, for example, to get daily or network element level values, and kept for longer periods to provide historical and trend data. There are different data warehousing capabilities depending on the system configuration.

The storage provides a consolidated view over the whole network or cluster, depending on the configuration, and the data can be used with various NetAct tools. Some of them also provide some intelligence for combining data of various types, including, for example, the configuration parameters. PM data can also be exported to third party systems via the measurement data export function. For comprehensive details on the function available via the NetAct, see NetAct product documentation for Reporting, Mon-itoring and Optimization Functionality.

Data is also stored in the OMS for short periods for NE-level usage. It can be used with local element management applications for simple reporting or troubleshooting. Data is also used for specific applications like threshold monitoring, but there are no options for exporting it to any third party system from the OMS.

To show the measurement results in graphical and textual format, use the RNW Mea-surement Presentation GUI.

For more information on measurement presentation, see Managing and Viewing RNC measurements.

The BTS and the AXC also provide a short-term local view of the data. This can be used only through element manager applications.


17



4.5 Alarms for PM data transfer failuresIt is crucial for the data users that the statistics data flow is reliable. There are many in-built mechanisms for automatic recovery from problems without unnecessary user action or loss of data, but it is inevitable that problems will sometimes occur.

The PM architecture is based on several distributed entities communicating over a data communication network of variable quality. There are several ways to detect general problems in the data pipe, such as DCN connection breaks, but PM-specific indicators are available as well. These specific alarms are meant to complement the generic notices, and are only generated for situations that:

result in loss of data require explicit action for resolution indicate a problem in the performance of measurement data processing or transferMore specifically, they are introduced for the following failure situations:

The OMS is not able to retrieve measurement data from the RNC Operation and Maintenance Unit (OMU) or the BTS.

NetAct is not able to retrieve measurement data from the OMS. There are problems in measurement data processing.Alarms are cancelled after the situation has recovered.

18 DN70352185Issue 04B



Measurement administration

5 Measurement administrationPerformance management includes functions for administering the measurement data collection. With these functions, it is possible to define the schedule, interval, and the collection of desired measurements for most of the different statistics.

Schedule refers to settings that determine the planned time of data collection. Interval is used to set the measurement granularity, for example, 60 minutes.

5.1 Centralised measurement administrationNetAct provides centralized management for the AXC, BTS, and RNC RNW measure-ments that form the majority of the statistics in the RAN. The function is based on a mea-surement plan concept. It is possible to create plans with the desired settings, and to activate them on the selected network elements without configuring each element and measurement separately.

Measurement plan activationActor: Measurement Administrator

Tool: NetAct Administration of Measurements application

Frequency: Seldom

1. The user creates a plan that includes the required measurements and settings.2. The user selects the network elements for the plan activation.3. NetAct activates the plan on the selected network elements.After the measurements are activated, NetAct receives data from the selected statistics. The plan and measurements are active for the relevant network elements.

The RCPM raw measurements are exceptions, as they include special parameter set-tings, or are only intended for monitoring limited area or connection types at a time. These and the IPA-based statistics for RNC transport and platform must be adminis-tered on a network element basis with the Element Manager at O&M mediator.

RCPM pre-aggregated measurements can be managed with NetAct.

BTS and AXC measurements always use a predefined interval, so that setting is not relevant for them.

5.2 Local measurement administrationIt is also possible to use the local element manager function for administering RNC RNW measurements. The centralized management application is also notified if there are local modifications to the measurement settings.

Local administration and measurement administration notificationsActor: Measurement Administrator

Tools: Element Manager at O&M mediator, NetAct Administration of Measure-ments application

Frequency: Seldom

1. The user changes some measurement settings locally with element manager.2. The network element sends a notification about the change to the NetAct.


19

WCDMA RAN Performance Management Measurement administration


The change information is visible for the end user in the NetAct Administration of Mea-surements application.

20 DN70352185Issue 04B



Collection of key counters

6 Collection of key countersNetAct provides a separate key counter measurement, which can include a collection of priority counters from the cell-level measurements produced by the RNC. The data is accessible through NetAct tools and interfaces, in the same way as other PM data.

Once installed and activated, the feature can be used via the normal PM data collection and activation mechanisms.

Key counter measurement provides an opportunity to save capacity in the network man-agement systems. The source measurements can be collected in parallel with the key counter measurement, but the measurement interval for the new measurement can be set to be different. This enables the key counter measurement to collect some of the data more frequently, without compromising too much on the system capacity by collect-ing everything at the finest granularity. The new measurement can be collected, for example, at 15-minute intervals, while keeping the source measurements at 60 minutes.

There can only be one key counter measurement, and its definition must be consistent across all the RNCs in the network.

There are some specific constraints that apply to the usage and settings of the measure-ment:

The supported intervals are 15, 30, and 60 minutes. In addition, the interval must be shorter than, or equal to the interval of the source measurements on which the key counters are based. The maximum interval for a source measurement is 60 minutes.

The key counter measurement contains 500 counters, which must be from the cell-level measurements that are produced by the RNC.

The key counter measurement is only available from the NetAct, but it can be forwarded through the export interface towards other management systems.


21

WCDMA RAN Performance Management Key performance indicators


7 Key performance indicatorsThe Key Performance Indicator (KPI) is a function of performance measurements. In its simplest form, a KPI is an individual counter, but usually it is a calculation formula made of several counters.

With carefully defined KPIs, the operator can easily see the overall status of the network performance, for example, if the RRC or RAB setup success ratio is as expected, if the RAB drop ratio is at an acceptable level, or if there are severe problems with the handover success ratio.

There are different kinds of KPIs:

official RAN KPIs (as defined in RAN documentation) other Nokia Siemens Networks-defined KPIs (as defined by NetAct documentation) user-defined KPIs

7.1 KPI calculationKPI calculation can be carried out in O&M mediator, NetAct, and 3rd party tools. This description focuses on KPI calculation carried out in the O&M mediator.

The operator can view the RNC KPIs through the O&M mediator. The KPIs can be viewed through the RNW Measurement Presentation GUI.

The operator can use predefined KPIs (a subset of RAN KPIs) or define their own cus-tomized KPI formulas. The operator can create and modify their own KPIs through the NE Threshold Management GUI (part of the O&M mediator).

Figure 6 KPI calculation in the O&M mediator.

By using the tools available in the O&M mediator, the user can analyze in detail the mea-surement data related to a specific area of interest. This is also useful if the operator does not want to transfer all measurement data up to NetAct (for example, for capacity reasons).

NetAct tools can be used to get an overall picture of network performance, and O&M mediator tools can be used to see deeper into the network element, for example, for troubleshooting.

22 DN70352185Issue 04B



Key performance indicators

For more information on RAN KPI calculation, see Overview of WCDMA RAN key per-formance indicators, or the online help of the RNC Threshold Management GUI (part of the OMS Element Manager).


23

WCDMA RAN Performance Management Threshold monitoring


8 Threshold monitoringPerformance statistics can often indicate a problem or a noteworthy event in the network or service functionality. The OMS provides an automated means to analyze RNC-level statistics as they are collected. This makes it possible to raise an alarm or notification based on predefined thresholds, as soon as the statistics are available in the O&M medi-ator. Threshold alarms are handled in the same way as any other fault management (FM) data, so they can be monitored with the common FM tools.

The O&M mediator element manager provides a tool for creating and managing thresh-old rules. Performance thresholds can be set for the variables, such that exceeding them indicates a problem worthy of attention. The variables can be either single counters or KPIs, which can be calculated from several counters using a user-defined formula. It is also possible to export the definitions and apply them to the other RNCs as well, without a need to create all the rules separately for each element.

The threshold rules and related measurements must be explicitly activated before they are in effect. After that, the OMS evaluates data against the rules and generates alarms accordingly. The alarm contains some basic information, but the details are also stored in the OMS for further study. The alarm information is processed further, as described in the fault management documentation.

Setting and activating thresholds in the RNCActors: administrator, network engineer

Tools: NE Threshold Management application, NetAct Administration of Mea-surements

Frequency: Seldom

1. The user creates threshold rules based on individual counters or KPI definitions.2. The user exports the rules and imports them to other relevant O&M mediator.3. The user activates the desired measurements with the NetAct Administration of

Measurements.4. The user activates the thresholds in the O&M mediator.RNCs trigger a threshold alarm according to the applied rules.

24 DN70352185Issue 04B



Optional functionality

9 Optional functionalityParts of the Performance Management functions are optional.

Optional PM counters are those that are related to a license (including counters tied to a feature under license).

Feature licenses are managed centrally by the OMS. See the product documentation for details.

Only licensed PM counters are contained in the PM report files and are visible at NetAct or Element Manager.


25

WCDMA RAN Performance Management Features per release


10 Features per releaseThe following table lists the features related to this functional area. The features are arranged according to the release in which they were introduced. Note that a feature may belong to more than one functional area.

RAN1.5

RAN1.054: Performance Management

RAN04

RAN2.0026: KPI Calculations in OMS element manager

RAN2.0027: Threshold Based PM Notification Triggering

RAS05

RAN844: Management for BTS Performance Data

RAS05.1

None

RAS05.1 ED

None

RAS06

RAN1160: Collection of Key Counters

RAN1161: Alarms for PM Measurement Data Transfer Failures

RU10

RAN1188: Pre-Aggregation of RCPM Data in RNC

RAN1214: Increased Monitoring Capacity for VCC Measurements

RU20

None

RU30

RAN1438: Automatic Object List Update in RNC Measurements

Table 2 Features per release

26 DN70352185Issue 04B



Management data for performance management

11 Management data for performance manage-ment

11.1 AlarmsThis section lists the alarms per feature. For the release information, see Features per release.

For alarm categories, see the Alarm Structure document. See also the Reference Infor-mation Service in NOLS.

There are no alarms related to the following features:

RAN1.054: Performance Management RAN844: Management for BTS Performance Data RAN1160: Collection of Key Counters RAN1188: Pre-Aggregation of RCPM Data in RNC RAN1214: Increased Monitoring Capacity for VCC Measurements RAN1438: Automatic Object List Update in RNC Measurements

11.2 CountersThere are no counters related to this functionality.

11.3 ParametersThere are no parameters related to this functionality.

Alarm number Alarm name

71000 PM FTP CONNECTION FAILED

71001 MEASUREMENT DATA NOT TRANS-FERRED

71002 MEASUREMENT DATA ERROR

71003 OMS MEASUREMENT DATA PRO-CESSING OVERLOAD

Table 3 RAN1161: Alarms for PM Measurement Data Transfer Failures


27

WCDMA RAN Performance Management Limitations and restrictions


12 Limitations and restrictionsFor details on limitations and restrictions in managing the performance statistics data, see Managing and Viewing RNC Measurements, Monitoring and measuring AXC in Operating and Maintaining AXC, and descriptions of particular measurements in RNC Counters RNW Part, RNC Counters Transport and HW Part.

WCDMA RAN Performance ManagementTable of contentsList of figuresList of tablesSummary of changes1Changes in performance management 1.1RU301.2RU201.3RU101.4RAS06

2Description of performance management3Architecture of performance management 3.1Architectural roles

4Performance data management 4.1Introduction4.2Performance data4.2.1Radio network measurement data provided by RNC4.2.2Transport and HW measurement data provided by IPA-RNC4.2.3Transport and HW measurement data provided by mcRNC

4.3Data collection4.4Data storage and usage4.5Alarms for PM data transfer failures

5Measurement administration5.1Centralised measurement administration5.2Local measurement administration

6Collection of key counters7Key performance indicators7.1KPI calculation

8Threshold monitoring9Optional functionality10Features per release11Management data for performance management11.1Alarms11.2Counters11.3Parameters

12Limitations and restrictions

Documents

Wcdma Ran Performance Management Ru30