03 OS82123EN80GLA00 Performance Management

Legal notice

Version 1 Nokia Solutions and Networks

1 (202)

NetAct 8 Performance Management

.

Performance Management

Legal notice


2 (202)

Legal notice

Intellectual Property Rights

All copyrights and intellectual property rights for Nokia Solutions and Networks training documentation, product documentation and slide presentation material, all of which are forthwith known as Nokia Solutions and Networks training material, are the exclusive property of Nokia Solutions and Networks. Nokia Solutions and Networks owns the rights to copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia Solutions and Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia Solutions and Networks training material. Individuals can use the Nokia Solutions and Networks training material for their own personal self-development only, those same individuals cannot subsequently pass on that same Intellectual Property to others without the prior written agreement of Nokia Solutions and Networks. The Nokia Solutions and Networks training material cannot be used outside of an agreed Nokia Solutions and Networks training session for development of groups without the prior written agreement of Nokia Solutions and Networks.

Indemnity

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of Nokia Solutions and 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 Solutions and Networks. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Solutions and Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this document 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 in a separate agreement between Nokia Solutions and Networks and the customer. However, Nokia Solutions and 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 Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks, explain issues which may not be covered by the document.

Nokia Solutions and Networks will correct errors in the document as soon as possible. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY MONETARY 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 document and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The NSN logo is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Export Control Marks:

AL: N and ECCN=5E991 or AL: N and ECCN=N (as in TCM course core data)

This course is subject to the European Export Control Restrictions.

Copyright 2014 Nokia Solutions and Networks. All rights reserved.

.

Content


3 (202)

Content

1 Performance Management Principles 5

1.1 Overview 6

1.2 Purpose 8

1.3 Performance Management Process 9

1.4 Performance Management Applications 14

1.5 Using Performance Information 16

1.6 Reporting Needs 18

1.7 Main Concepts for Performance Management 27

1.8 Post - Processing of Measurement Data 35

2 NetAct PM Functionalities 41

2.1 Performance Management with NetAct 42

2.2 Administration of Measurements 44

2.3 Data Collection and Processing 46

2.4 Performance Manager 48

3 Measurements and Counters Information 49

3.1 Object Information Browser (OIB) 50

4 User Reporting Tasks: Getting Started with NMP 52

4.1 Performance Manager Overview 53

4.2 Web Page Components 54

4.3 Configuring Preferences 58

5 User Reporting Tasks: Browsing and Executing Reports 60

5.1 Overview 61

5.2 Reporting Suite View 62

5.3 Saved Reports View 65

5.4 Changing Selections for the Reports 71

5.5 Report Navigator 73

6 User Reporting Tasks: Working with the Report Output 75

6.1 Report Output Limits 76

6.2 Report Output Options 77

6.3 Report Details, Export Data and Visualization Options 81

6.4 Layout Options 94

6.5 Report Drillings 95

6.6 Data Reliability 98

7 User Reporting Tasks: Scheduling Reports 100

7.1 Scheduling Reports 101

8 User Reporting Tasks Rehoming Support 104

8.1 Rehoming 105

9 Advanced User Reporting Tasks: Managing Reports 107

Content


4 (202)

9.1 Report Creator Introduction 108

9.2 Report Creator Wizard 110

9.3 Editing Reports 129

10 Advanced User Reporting Tasks: Managing KPIs 131

10.1 KPI Creator Introduction 132

10.2 Creating a KPI 134

10.3 Editing a KPI using Custom KPIs 140

10.4 KPI Creator selection details 142

11 Administrator User Tasks: Managing Network Elements' Measurements 144

11.1 Administration of Measurements 145

11.2 Uploading Network Elements' Measurements Configuration 147

11.3 Checking the active measurement configuration 150

11.4 Creating a Measurement Plan 152

11.5 Creating a Template 158

11.6 Viewing detailed information of a plan 160

11.7 Activating Plans 160

12 Administrator User Taks: Publishing Reports 162

12.1 Reporting Suite Publisher 163

13 Administrator User Tasks: Publishing KPIs 167

13.1 Sharing KPIs with KPI Publisher 168

14 Administrator User Tasks: Managing Scheduled Reports 171

14.1 Scheduler Functions 172

15 Administrator User Tasks: Administering the PM Platform 175

15.1 Getting Started with Admin ToolKit 176

15.2 Data Reliability 178

15.3 Adaptation Configuration 178

15.4 Storing Period Configuration 180

15.5 Administration of Aggregates 181

16 Administrator User Tasks: PM Data Export Interfaces 182

16.1 PM North Mediation Interface 183

17 Administrator User Tasks: SW Asset Monitoring 186

17.1 Overview 187

18 Exercises 190

Exercise 1 192

Exercise 2 193

Exercise 3 195

Exercise 4 197

Exercise 5 199

Exercise 6 201

Performance Management Principles


5 (202)

1 Performance Management Principles



6 (202)

1.1 Overview

As the communication world transforms to a service-oriented system, the next generation operators have to deal with multi-technology, multi-vendor networks. The operators not only have to provide a varied set of services to their customers but also need to contend with the pressure on the networking resources as the services multiply. In such a scenario, it is essential that the operator has a consistent view of the performance and utilization of the entire network. Only then can the operator efficiently utilize and plan the network resources available.

The performance and maximum utilization of the network is not the only challenge for operators. Next-generation architectures and service delivery platforms will enable them to deliver highly personalized services to their customers. To successfully deliver this kind of services it is required to correlate network information up to the customer level. Combining customer-specific information with relevant operations data such as information from the billing, customer care, and performance data from the network will enable the operator to achieve a complete view of each customer and his or her value.

This information on network performance and resource utilization is continuously produced at different points and different abstractions of management (Element level, Network level, Service level, etc.). In the real worlds complex systems, the amount of Performance data that can be produced is huge, but not everything is required at the time. Performance Management tools have to provide then the means to collect the required data timely and on demand and be able to provide the users and the organization processes with specific information to fulfill the described management needs of the operators.



7 (202)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 2014 Nokia Solutions and Networks. All rights reserved.

Performance ManagementOverview

"Any evaluation of PLMN system behavior will

require performance data collected and

recorded by its Network Elements according to

a schedule established by the OSS. This aspect

of the management environment is termed

Performance Management."

Performance data measurements in ETSI, GSM

specification 12.04 version 4.3.1

Fig. 1



8 (202)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 Purpose


Performance ManagementPurpose

The aim of any performance management activity is to collect data

to support the following activities:

Plan, troubleshoot and optimize the network

Verify the physical and logical configuration of the PLMN

Monitor continuously how the network functions.

Localize potential problems as early as possible.

Monitor subscriber behavior.

Provide optimum services to mobile subscribers

Providing data to other management processes, for example service and business management.

Fig. 2



9 (202)

1.3 Performance Management Process

The performance management process comprises the description of a view on the PM tasks the operators follow in order to monitor, assess the quality of the network and obtain the requested output information for the different users and processes inside the operators organization.

1.3.1 Defining or revising Quality of Service goals

When managing a particular network, the Quality of Service (QoS) represents the effective maintenance state of the quality for the network services according to some agreed criteria. Maintaining and improving the QoS of the network includes regular monitoring of the service performance and the evaluation of the service performance problems with respect to the targeted level of service delivery.

To improve the service, it is necessary to define QoS goals that guide the evaluation of network and service performance. These goals can represent, for example, the point of view of the operator (efficient hardware usage, for example efficient use of network elements considering the type and capacity of the NEs, their location and number to support the services) or the point of view of the subscriber (availability, speed, and accuracy of the service).

As the network evolves and expands, these QoS goals might have to be updated and revised. Mature operators competing for more market share benefit from introducing new services to differentiate themselves from other service providers. At this point, all kinds of service and profile measurements are useful. The quality of service becomes extremely important and, for example, optimization measurements must be taken. The following tasks belong to this stage:

Setting objectives for the desired level of quality

Measuring the quality of service by monitoring real-time data and long-term trends

Planning corrective actions

1.3.2 Translating Quality of Service goals to network performance requirements

To achieve the defined QoS goals, it is necessary to prepare or update the detailed requirements for the network, including the requirements on network performance. For example, the quality of a voice service can be correlated with the number and ratio of dropped calls, while the accuracy of an IP service can be correlated with the number of received packets.



10 (202)

1.3.3 Defining reporting requirements

The network performance requirements serve as the basis for reporting requirements and provide information on which measurements you have to monitor with the PM applications.

1.3.4 Identifying other reporting needs

Monitoring the day-to-day performance of the network is not the only reason for using performance reports. Information from reports can be used, for example, to examine short-term changes due to system upgrades or to revise long-term trends to gather information for optimizing or expanding the existing network.

If these reporting needs are translated into measurements, the reporting requirements are then clear and can be translated into measurement activation criteria. However, some reporting requirements can give rise to a need for a new or an additional PM application. You might also need a new or additional PM report when you are investigating uncommon situations or when you have upgraded or expanded your network.

Before establishing new reports, it is recommended that you check whether the active measurements already provide the counter information that you need, or whether the required measurements are available but have not been activated yet, or whether it is sufficient to change the measurement settings to obtain the needed information.

1.3.5 Defining reports

You can define and schedule your reports based on the reporting requirements. The details of defining reports mostly depend on the OSS solution.

1.3.6 Adapting the measurement load and the OSS

If you need a new measurement, you have to ensure that the capacity of the OSS, for example, disk space and insertion time, is not exceeded when the new measurement is implemented and activated. If the OSS capacity could be exceeded, you can adapt the entire measurement set by reducing the number of the measurements or increase the measurement intervals, or you can increase the OSS capacity, for example, with additional processors. If the capacity has not been exceeded, you can proceed with initializing the additional measurements.



11 (202)

1.3.7 Initializing measurements

Activating all the necessary measurements across the network could impose a significant but unnecessary load on the database and the PM processes. So, it is recommended to consider the following factors:

Period when measurements are active in the network element or the measurement information is uploaded from the network element to the network management system

Measurement intervals

Number and distribution of the network elements for which the measurement is activated

1.3.8 Defining thresholds

Network management systems allow you to define thresholds for the measurements. When a measurement value exceeds a threshold, an alarm is raised. So, you can follow the status of network performance with the fault management applications in which the alarm is visible and also with the performance management applications in which the measurement information is processed. The details of defining thresholds mostly depend on the Operations Support System (OSS) solution.

1.3.9 Collecting data

The measurement information can be preprocessed in the network element, depending on the NE type and the configuration of the NE. If preprocessing is applied, the data is filtered, that is, not all of the measurement information is forwarded to the network management system) or some calculation is done on the measurement data before it is uploaded to the OSS through the NE-specific interface.

The data can also undergo further processing in a post-processing phase, for example, when busy hour information is needed for a report. The results of the post-processing are also stored in the OSS database. The data is used by the reporting applications or is exported through the open interfaces to external systems.

1.3.10 Monitoring network performance

You can typically find performance-related problems by checking the alarms, the measurements, and the customer complaint reports. You also can use information from drive tests and call detail reports (CDRs).

Regular reporting such as running a report once a day or once a week is too slow for continuous network monitoring. Furthermore, the default measurement interval for most counters, one hour, may create a huge delay. However, you can also analyze the traffic statistics and collect detailed information from the network for further analysis with reports when you discover a problem. Prompt reaction is sometimes required. So, it is recommended that you set thresholds for the performance indicators so that the OSS raises alarms based on the indicator values in unusual situations or when errors occur.



12 (202)

1.3.11 Generating and distributing reports

When you defined the reporting requirements, you also gathered information on the user groups and on the types and frequency of the reports that they need. You have to ensure that the users of the OSS have access to or receive the reports that best support their work.

Reporter applications allow you to turn the often overwhelming amount of measurement data into information on the performance of the resources in your network, which you can use for determining whether the network performance goals are met and whether problem-determination procedures should be initiated based on performance.

1.3.12 Analyzing the results

PM reports are mostly used for two purposes: to gather information for troubleshooting (short-term reports and ad-hoc reports), for prevention, and for developing the network and the services (longer-term reports).

For example, the top management of an operator can use PM reports for obtaining high level information on the network operation at a glance. It is possible to use a report about the length of the calls to determine whether the service is becoming more or less popular among the subscribers and in what times of the day subscribers use particular services the most. The call durations plotted against the day gives information on the preferences of the subscribers and helps you decide about marketing campaigns, special rates for busy hours or off-peak hours.

You can also monitor whether a network expansion has the expected results on the quality of services by regularly checking your own customized reports. With regular checks you can avoid significant negative impact by taking corrective actions as soon as deviations are observed in the quality of the service. When you have to optimize your network or when you consider an expansion, you can use various PM reports to gather information on the past.

You can also use the reports for monitoring the network performance over a certain period of time and check how the QoS and other quality objectives are met and identify possible problem areas in the network. For optimization, for example, you might need detailed quality information on particular measurements in a particular BSS. For expansion and planning, you might need a less detailed report but over a longer period of time to observe trends in the subscriber behavior or network resource usage.



13 (202)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Performance Management ProcessDefine or revise QoS Goals

Translate QoS goals to network

performance requirements

Define reporting requirements

Define thresholds Define

reports

Identify other reporting

needs (for example trends)

Adapt the measurement

Load and the OSS

Initialize (additional)

measurements

Collect data (storing and

processing)

Generating and distributing

reports

Analyse the results

Plan measurements

Set thresholds

No

Yes

Monitor

thresholds

Is OSS

Capacity

OK?

Fig. 3



14 (202)

1.4 Performance Management Applications

Depending on how the performance management applications use the collected data, they can be divided into two main types: performance monitoring and performance reporting applications.

Performance monitoring is online-oriented and provides you with relatively real-time information on the network. Therefore, performance monitoring applications generally use shorter measurement output intervals because faster reaction is needed in severe problem cases, in which a 24-hour interval would be too long. The outputs of performance monitoring applications are mainly used as additional information for problem cases in which no alarm information is available. Performance monitoring rules are intelligent threshold rules and can be calculated before or after the measurements are stored in the database.

Performance reporting is offline-oriented and provides information on what happened in the network over a certain period of time. Performance reporting applications mainly rely on performance indicators and produce reports, which you can use, for example, when you are troubleshooting, planning, or optimizing the network



15 (202)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Performance Management Applications

Performance Monitoring Apps:

Online oriented

Near real-time information about the network

Use shorter measurement output intervals

Depending on how the performance management applications use the

collected data, they can be divided into two main types:

Performance Reporting Apps:

Offline oriented

Rely on Performance Indicators and produce

reports

Use longer measurement output intervals

NetAct Reporter

Fig. 4



16 (202)

1.5 Using Performance Information

The operator organization can use the various types of performance information for monitoring and managing the network.

When monitoring a network performance, different types of data are collected in order to locate potential problems as early as possible and to verify the physical and logical configuration of the network. The performance data can also be used to monitor subscriber behavior by charting out the usage of different services that are available to the end-users. Such information provides the operator with input for business and service management decisions when you are optimizing and expanding the network.

Performance-related information in the network is of vital importance for taking management decisions and identifying possible current or future problems and opportunities.



17 (202)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Using Performance Information

Traffic levels within the PLMN, including the level of both the user traffic and the signalling traffic.

Verification of the network configuration.

Resource access measurements.

Quality of Service (QoS)

Resource availability.

Network elements produce data to support performance

evaluation, for example on the following areas:

Fig. 5



18 (202)

1.6 Reporting Needs

Networks continuously produce an enormous amount of performance data. PM applications need to filter the information to suit the needs of various users:

Management and operational levels at the operator.

Technical considerations in the network, for example monitoring the radio access and the core network separately.

End-user perception of the services about traffic, quality, or availability of the services.

The following figure shows reporting needs in a combined model. Each chunk of the pyramid corresponds to a report set or report group that PM applications can provide to the various user groups.

The applications allow you to turn the often overwhelming amount of measurement data into information on the performance of the resources in your network, which you can use for determining whether the network performance goals are met and whether problem-determination procedures should be initiated based on performance.

Various user groups can use performance measurement data for managing the network and what kind of PM applications they can use depend on the objectives.



19 (202)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Reporting Needs

Networks continuously produce an enormous amount of performance data. PM applications need to filter the information to suit the needs of various groups of users:

Top Management

Technical Management and Marketing

NW Monitoring

NW Optimization

PLMN Level:

Fewer number of ReportsMainly trend Reports Graphical Output type

NE Level:

Higher number of Reports Detailed or Top-N ReportsMatrix or Graphical Output type

Fig. 6



20 (202)

1.6.1 Performance Management User Groups

Top management

Monitoring the current network status with ad-hoc reports

Forecasting future trends with longer-term reports

Following the trends of the network development, for example, monitoring QoS and usage statistics of various services

PLMN-level information condensed in few reports

Mainly about trends

In graphical format

Mainly offline report generation

Monthly or longer periods

Historical information tendencies

With graphs

For example, network outages of the last month (number, length, and number of affected sites)

Marketing

Observing subscriber behavior and capacity issues from longer-term reports based on QoS and usage statistics

Planning new services by analyzing the recent and current trends

Monthly, with more details on the last day or week

Graphs or tables

For example service usage statistics

Technical management

Higher-level information with drilling possibility to problem areas.

Checking daily the most important performance indicators at the PLMN level or for each maintenance region, and if necessary, for each NEs.

Tracking measurements and observations accurately to monitor, for example, the MSC, BSC, and BTS levels separately.

Weekly or monthly, with more details on the last day or week.

Graphs or tables.

For example SLA reports including the main KPIs for network elements.

Operations and Maintenance

Detecting faults by enabling measurement based alarms.

Localizing potential problem areas by evaluating longer-term reports on network coverage.

Solving faults by using PM reports for root-cause analysis.

Low-level information and easy access to all the counter information.

Fast navigation, switching between performance indicators, when checking for particular counters in a certain network element or a group of network elements for troubleshooting.

Daily KPI reports, especially on failing NEs.

Mainly textual and some graphical reports.



21 (202)

Optimization, Planning

Monitoring network capacity by evaluating longer-term reports on the use of network resources.

Monitoring network quality by evaluating reports that include performance indicators about the quality of the services.

Verifying radio network coverage by evaluating reports that include performance indicators such as the number and percentage of hand over failures in a geographic distribution.

BSC and MSC level that can be processed into traffic profiles to provide information on subscriber behavior and the overall performance of the network and the network usage through time and locations.

Quality of service (QoS) monitoring, which can include monitoring the quality of service as seen by the subscribers, and the quality of the network from the technical point of view.

Longer-term traffic profiles to determine pricing strategies.

Tendency reports at higher or lower level, depending on the planning work.

Both raw and summarized information if performed at the lowest level.

Mainly matrix type and some graphical reports.

Customer Care

Informing subscribers about current problems by obtaining and analyzing up-to-date information on the network status from ad-hoc reports.

Responding more quickly to service complaints by identifying the cause of network problems.

Frequent, preferably daily, status reports on the status of the network and on the status of failing NEs.

Frequent and regular.



22 (202)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Using Performance InformationUser Groups

User Group PM Objectives Report Needs Report Type

Top

Management

Monitoring the current network status with ad-

hoc reports

Forecasting future trends with longer-term reports

Following the trends of the network

development, for

example, monitoring

QoS and usage statistics

of various services

PLMN-level information

condensed in few

reports

Mainly about trends

In graphical format

Mainly offline report generation

Monthly or longer periods

Historical information, trends.

With graphs

For example, network outages of the last

month (number,

length, and number of

affected sites)

Fig. 7



23 (202)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




Technical

Management

and

Marketing

Observing subscriber behavior

and capacity issues

from longer-term

reports based on

QoS and usage

statistics

-Planning new services by

analyzing the recent

and current trends

Higher-level information with drilling possibility to

problem areas

Checking daily the most important counters at the

PLMN level or for each

maintenance region, and

if necessary, for each

NEs

Tracking measurem and observations accurately

to monitor, for example,

the MSC, BSC, and BTS

levels separately

Weekly or monthly, with more details on

the last day or week

Graphs or tables

BSC level is important

For example service usage statistics

Fig. 8



24 (202)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




Operations

and

Maintenance

Detecting faults by enabling measurement-

based alarms

Localizing potential problem areas by

evaluating longer-term

reports on network

coverage

Solving faults by using PM reports for root-

cause analysis

Low-level information and easy access to all

the counter information

Fast navigation, switching between

counters, when

checking for particular

counters in a certain

network element or a

group of network

elements for

troubleshooting

Daily KPI reports, especially on failing

NEs

Mainly textual and some graphical

reports

Fig. 9



25 (202)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




PM Analysis,

Optimization,

Planning

Monitoring network capacity by evaluating

longer-term reports on the

use of network resources

Monitoring network quality by evaluating reports that

include counters or kpis

about the quality of the

services

Verifying radio network coverage by evaluating

reports that include

counters or kpis such as

the number and

percentage of hand over

failures in a geographic

distribution

BSC and MSC level that can be processed into traffic profiles to

provide information on

subscriber behavior and the

overall performance of the

network and the network usage

through time and locations

Quality of service (QoS) monitoring, which can include

monitoring the quality of service

as seen by the subscribers, and

the quality of the network from

the technical point of view

Longer-term traffic profiles to determine pricing strategies

Tendency reports at higher or lower

level, depending on

the planning work

Both raw and summarized

information if

performed at the

lowest level

Mainly textual and some graphical

reports

Fig. 10



26 (202)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




Customer

Care

Informing subscribers about current problems

by obtaining and

analyzing up-to-date

information on the

network status from ad-

hoc reports

Responding more quickly to service

complaints by

identifying the cause of

network problems

Frequent, preferably daily, status reports on

the status of the

network and on the

status of failing NEs

Frequent and regular

Fig. 11



27 (202)

1.7 Main Concepts for Performance Management

1.7.1 Counters, Measurements and Observations

A counter is a register which is updated in the NE each time an event occurs. There are different types of counters based on how they can be updated. Cumulative counters represent a running count of, for example, how many times an event occurred while gauge counters take the value of what they measure, for example how many data packets are in a buffer.

When a measurement interval ends, the values of the measurement counters are transferred to the OSS and the counters are reset for the next period.

A counter provides the result in specified units, for example, in integers or Erlangs. The term counter is used as a synonym of Performance Indicator.

A measurement is an action where the system collects information about e.g. traffic and network events and then processes this information.

A measurement is a fixed set of counters.

An observation is a function where the system either collects information about certain events or directly produces information about single events in the system.

It is possible to set certain objects under observation and to set conditions which must be fulfilled before the system produces reports or alarms

Observations are typically used to locate the part of the network system causing problems.

A measurement is in fact a collection of statistics, or to be more precise, a collection of counters. All of these counters are counting a particular event that relates to the measurement name. The measurements are grouped in this manner to allow better functionality and handling. This provides the user with easier selection of certain measurements necessary at a particular time. All measurements are independent of each other but the same user interface is used for handling all measurements.

Each network element can have only one instance of each measurement running. In other words, the measurement is either active or not. Each measurement has a reporting period, therefore at set intervals, each counter will return with a value for each object.

The output interval determines for how long counters are collected into a measurement. Measurements can be collected at regular intervals: 15 - 30 - 60 minutes, 2 - 3 - 4 - 6 - 12 - 24 hours.



28 (202)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

03 OS82123EN80GLA00 Performance Management

Documents

Transcript of 03 OS82123EN80GLA00 Performance Management