Академический Документы
Профессиональный Документы
Культура Документы
V100R016
Issue 01
Date 2016-09-15
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Overview
The PRS can centrally manage performance data collected from devices on the GSM BSS,
UTRAN, E-UTRAN, CDMA BSS, WiMAX RAN, TD-SCDMA RAN, SingleRAN, and core
networks. Based on such data, the PRS provides the MBB network performance visibility
function, including network statistics performance management, network KPI insight, and
network capacity visibility.
Product Version
The following table lists the product version for this document.
PRS V100R017C00
Intended Audience
This document is intended for:
l Network optimization engineers
l System engineers
Change History
01 (2016-09-15)
This issue is the first official release for V100R017C00. Compared with last version, this
issue has no changes.
Draft A (2016-04-07)
This issue is the first release of the V100R017C00 beta version.
Organization
1 Basic Principles
The PRS is a comprehensive performance report management solution for telecom operators.
It provides professional system (predefined) reports on the RANs and core networks of
different radio access technologies (RATs), such as GSM, WCDMA, LTE, CDMA, and
WiMAX. It displays analysis results in reports of various types and supports user-defined
reports. This allows users to flexibly define key performance indicators (KPIs) and service
performance reports and helps users learn about network performance.
2 Functions Description
The network performance management function of the PRS can be classified into KPI
management, object group management, report management, report query, KPI analysis,
report correlation and drilling, and GIS support. This section describes these functions and
corresponding interfaces.
3 Typical Application
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Symbol Description
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl
+Alt+A means the three keys should be pressed
concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Contents
3 Typical Application.....................................................................................................................22
3.1 Capacity Visibility........................................................................................................................................................ 24
3.2 KPI Insight....................................................................................................................................................................26
3.3 Benchmarking Management.........................................................................................................................................29
1 Basic Principles
The PRS is a comprehensive performance report management solution for telecom operators.
It provides professional system (predefined) reports on the RANs and core networks of
different radio access technologies (RATs), such as GSM, WCDMA, LTE, CDMA, and
WiMAX. It displays analysis results in reports of various types and supports user-defined
reports. This allows users to flexibly define key performance indicators (KPIs) and service
performance reports and helps users learn about network performance.
In the PRS, the data collection module periodically collects performance files and
configuration files from the data storage directory of the element management system. Then,
the data collection module transfers the files to the data storage directory of the PRS using
FTP/SFTP.
PRS-FS, which indicates the PRS file service (FS) module, periodically parses the files in the
PRS data storage directory and imports the original configuration data, performance data and
license data into the sumdb database. It also clears obsolete original data from the sumdb
database.
PRS-DS, which indicates the PRS data service (DS) module, periodically collects original
data from the sumdb database according to the preset rules and the period set for collecting
performance counters. After setting and aggregating original data, the DS module saves the
processed data in the sumdb database for report analysis.
The PRS-ReportService service for KPI management and report management and the PRS-
ReportEngine service for KPI query obtain summary data from the sumdb database
according to search criteria. Then, the module provides the following services according to
the commands from the PRS client: report management, KPI management, and KPI analysis.
Data Collection
A measurement period refers to the interval for NEs to report performance measurement
results. After an U2000 user sets a measurement period, NEs measure counters based on the
period and report measurement results. The U2000 parses the results and saves them in the
database. Report periods may vary according to measurement counters. Measurement periods
may vary according to NE types. The measurement periods supported by NEs may be one or
several of the following periods: 5 minutes, 15 minutes, 30 minutes, 60 minutes, or 24 hours.
The NodeB does not support the 5-minute measurement period.
After NE's performance measurement results are reported to the U2000, the U2000 exports
the results from the performance database to the specified path on the server based on the
northbound export parameters set on the client. Then, the U2000 sends the results to the PRS.
The northbound export parameters set on the U2000 do not distinguish periods. The U2000
generates performance data for the PRS based on the periods of performance data reported by
NEs. If NEs do not report performance data, no performance data exists on the U2000. The
performance measurement results of multiple periods can co-exist.
According to the performance data collection period set on the client, the PRS selects the
performance result files generated in one period from all the original files exported from the
U2000 as the original result files.
NOTE
The PRS does not import all the counters collected from the U2000 into the database. Therefore, in the
KPI Management dialog box on the web-based PRS client, you must check whether the required
counters have been activated. By default, KPIs have been activated. If the counters are not activated,
activate them on the web-based PRS client.
Data Aggregation
Data aggregation is a process in which data is gathered and expressed in a summary form.
Through data aggregation, the PRS obtains original performance data according to system
settings and saves the data in the sumdb database. This helps you query and analyze
performance data. Figure 1-2 describes the data aggregation process in the PRS.
Data aggregation in busy hours is a process in which the PRS periodically calculates
busy hours according to the preset busy-hour calculation algorithm and aggregates and
saves the data generated in the busy hours.
l Data aggregation on user-defined time
Data aggregation on user-defined time is a process in which the PRS aggregates data on
the time customized during KPI analysis or report query. Such data aggregation
aggregates data generated for a time type at a lower level.
NOTE
Compared with data aggregation on default time, data aggregation on user-defined time allows you
to perform query on the fly for the data aggregated within the customized period. For example, to
aggregate the data generated from Monday to Friday, you can customize a time type that spans
from Monday to Friday. After selecting the time type, you can query the data aggregated from
Monday to Friday immediately.
Data aggregation by object is categorized into aggregation by default object and aggregation
by object group.
l Data aggregation by default object
Data aggregation by default object is a process in which the PRS automatically
aggregates performance data according to the preset object type relationship and saves it
as the data of a higher object type. You can view the default object types for data
aggregation on the web-based PRS client.
l Data aggregation by object group
Data aggregation by object group is a process in which the PRS aggregates data by
object group.
NOTE
In KPI analysis or performance report query, the PRS immediately starts aggregating original data and
hourly data after parsing collected original performance data and configuration data. You can quickly
view the latest summary data in the query results. The parsed data is not aggregated on day, week,
month, daily busy hours, weekly busy hours, or monthly busy hours until the next time the scheduled
aggregation is triggered.
Data Storage
The performance result files collected by the PRS from the OSS are saved in the specified
directory on the PRS server for 1 to 32 days. You can change the period for storing collected
data files on the server in Data Collection Parameters in the OSS Management window on
the PRS client.
The original result data that has been parsed by the PRS FS can be saved for 1 to 14 days.
After choosing Maintenance > Business Configuration on the web-based PRS client, you
can choose Report > Object Storage Time from the navigation tree in the left pane and then
change the value of Original Data (day). The FS service deletes obsolete original result
data at 04:15 every day by default.
Table 1-1 lists the periods for saving the data that is aggregated by the PRS DS by hour, day,
week, month, daily busy hours, weekly busy hours, and special date. After choosing
Maintenance > Business Configuration on the web-based PRS client, you can choose
Report > Object Storage Time from the navigation tree in the left pane and then change the
value of a data type. By default, the DS deletes obsolete data at 04:15 every day by default.
NOTE
Generally, the data stored in a system cannot reach the upper storage threshold. In some special cases
where storage space cannot meet onsite requirements, such as non-standard server type and excessive
NEs connected, the PRS provides a protection mechanism to ensure that new data can be handled
properly. By default, the PRS samples the usage of the sumdb database. Once the usage of the sumdb
database reaches 90%, the PRS starts the protection mechanism and deletes the oldest data from hourly
data.
Data Query
The PRS allows you to query data. During KPI analysis or performance report query, you can
query performance data according to the default or new conditions in the sumdb database.
You can customize query criteria such as object and time to query and obtain specified data
from the sumdb database. The query in the KPI Analysis window is a one-time operation.
The query criteria cannot be saved for future use.
You can create required reports in the Report Management window by setting query criteria.
Then, you can perform Query operation to query and obtain specified data from the sumdb
database. The query criteria set in the Report Management window can be saved as a
template for future use. Once the reports that meet the query criteria are selected, you can
query and obtain the corresponding data.
2 Functions Description
The network performance management function of the PRS can be classified into KPI
management, object group management, report management, report query, KPI analysis,
report correlation and drilling, and GIS support. This section describes these functions and
corresponding interfaces.
The PRS provides an end-to-end platform for customizing reports. Figure 2-1 shows the
procedure for customizing reports in the PRS.
l Customizing KPIs
The PRS enables users to define counter formulas by performing combined operations,
namely, addition, subtraction, multiplication, and division, on original KPIs, system
KPIs, and predefined KPIs. In addition, users can also define conditional KPIs such as
worst cell ratio and busy cell ratio by using counter formulas that contain if, min, max,
count, avg, and sum conditions.
l Customizing busy-hour rules
The PRS allows users to customize busy-hour rules and identifies busy hours based on
specific scenarios.
l Customizing reports
The PRS allows users to customize reports such as simple reports, comparison reports,
combined reports, and DB-based reports. Users can also modify, delete, move, import,
and export these custom reports as required.
l Customizing report formats
By correlating reports with XLS templates, the PRS enables users to export report query
results by using the predefined XLS templates. Users can also edit reports by using
various Excel functions, such as fonts, panes, charts, formulas, and macros.
l Generating and delivering reports on schedule
The PRS automatically generates reports according to the preset time and period. Then,
reports generated on schedule are delivered to a specified email address or FTP server. In
this way, users can obtain the report data by receiving emails or viewing files on the FTP
server.
2.1 Supporting Engineering Parameters
Engineering parameters imported into the PRS are important to network monitoring and
analysis, enabling you to analyze the network accurately and easily.
2.2 KPI Management
KPI management allows you to define KPIs as required during routine network monitoring
and problem analysis. This improves routine OM efficiency.
2.3 Object Group Management
Object group management allows you to select multiple objects to aggregate data according to
object groups during KPI analysis and report creation. This improves routine OM efficiency.
2.4 Report Management
The PRS provides powerful report customization functions, helping telecom operators
flexibly obtain key data on networks that frequently change and develop user-defined reports
based on OM experience. The report customization functions also meet telecom operators'
short-term requirements on user-defined reports, helping telecom operators reduce
investments in report customization and improve overall service competitiveness.
2.5 Report Query
Users can quickly search for data based on default or specified criteria. This facilitates routine
network monitoring and troubleshooting.
2.6 KPI Analysis
Network problems occur randomly. Therefore, predefined reports cannot meet all query
requirements. With the KPI analysis feature, users can quickly query data without defining
templates. This facilitates quick troubleshooting and problem analysis.
2.7 Report Correlation and Drilling
The report correlation and drilling function allows you to quickly locate and analyze a
problem in multiple dimensions when you find the abnormal data in a report.
2.8 GIS Support
The geographic information system (GIS) enables you to manage base stations and locate
areas where exceptions occurred on a map. The GIS helps you view information explicitly
and visually during network optimization and analysis.
Function Description
The PRS system supports the import of engineering parameters of the GSM, CDMA, UMTS,
TD-SCDMA, WiMAX, LTE network systems. The template for importing engineering
parameters varies according to the network system. You can export, delete, or refresh the
imported engineering parameters.
If an engineering parameter is imported into Engineering Parameter Management, the PRS
supports the application of the engineering parameter in three scenarios listed by Table 2-1.
Creating a report During Creating a Report, you can select engineering parameters in
the process of Set Object Display Attributes. In this manner, the
engineering parameters are displayed in the query result.
GUI
Figure 2-2 shows the Engineering Parameter Management window. Navigation Path:
Choose Report > Engineering Parameter Management on the Web-based PRS client.
Function Description
You can define KPI formulas and create user-defined KPIs as required, and select these KPIs
for query and analysis during KPI analysis or report creation.
KPI management includes the following functions:
l Creating custom KPIs: Users can select raw counters to define a custom KPI formula by
using plus, minus, multiply, and division operation symbols based on system KPIs and
defined custom KPIs. Users can also define custom KPI formulas containing functions
such as if, min, max, count, avg, sum, ifnull, log10, and power. With these functions,
conditional KPIs such as worst cell proportion and busiest cell proportion can be defined
easily.
l Modifying custom KPIs or Deleting custom KPIs: The PRS allows users to delete all the
KPIs created by a specified user and modify the affected reports, scheduled tasks,
dashboards, and benchmark rules.
l Importing and exporting KPIs: The PRS allows users to import and export custom KPIs,
predefined KPIs, and related formulas in an XML file for KPI sharing between PRSs.
l Setting KPI conditional formats, thresholds, and zero divided rules: The PRS allows
users to set KPI formatting, including font color and background color. The PRS allows
users to set thresholds for KPIs. If the actual value of a KPI is greater than the upper
limit, the upper limit is displayed in the query result. If the actual value of a KPI is less
than the lower limit, the lower limit is displayed in the query result. If a KPI value meets
a preset condition, the KPI value is displayed according to the conditional format. For a
KPI formula contains the division operation, users can set the zero divided rule so that
the KPI can be displayed as specified when it is divided by zero.
l Correlating KPIs with reports and searching KPI reference relationships: By correlating
a KPI with reports, users can query service reports related to this KPI, which facilitates
GUI
Figure 2-3 shows the KPI Management page. Navigation path: Choose Report > KPI
Management on the Web-based PRS client.
Function Description
You can add objects of the same type to an object group so that the PRS can aggregate data
according to the object group. You can also create or query data according to object groups
during KPI analysis and report creation.
GUI
Figure 2-4 shows the Object Group Management window. Navigation path: Choose Report
> Object Group Management on the Web-based PRS client.
Function Description
The user-defined report management of the PRS solves the problem that default performance
reports cannot meet users' requirements. With this function, you can create performance
reports on the PRS client as required and repeatedly use the reports to query related
performance data.
When creating reports, users can select either an object group or a single object in an
object group. In addition, users can select objects by object group type, including manual
group, conditional group, and automatic group.
GUI
Figure 2-5 shows the Report Management page. Navigation path: Choose Report > Report
Management on the web-based PRS client.
Function Description
Report query allows you to directly view the statistics in reports on the PRS client. You can
query reports based on either default or specified criteria, and sort, filter, export, and print the
query results. The following describes the specific functions:
l Query based on default criteria: Default criteria are predefined in the PRS. Based on the
predefined conditions, users can search for required data quickly to generate reports.
l Query based on specified criteria: The PRS provides report templates. Users can specify
date, time, period, and objects in the templates and then search for required performance
data based on the specified criteria. Reports can be generated for the search results.
l Filter criteria prioritization: Users can define multiple filter criteria for one report and
also arrange the priorities of the criteria.
l TopN query: Users can obtain TopN object records that meet the filter criteria.
GUI
Figure 2-6 and Figure 2-7 show different report query interfaces. Navigation path:
l On the Report Management page of the web-based PRS client, select a report directory.
In the report list in the right pane, select a report and click the report name or . The
query results are displayed on a new page.
l On the KPI Analysis page of the web-based PRS client, set NE, object, and time
information, and select a report you want to query. The query results are displayed in the
right pane of the KPI Analysis page.
Function Description
You can set object, KPI, and time information and then perform KPI analysis to quickly query
qualified data.
GUI
Figure 2-8 show the web-based and Java-based KPI Analysis window. Navigation Path:
Choose Report > KPI Analysis on the web-based PRS client.
Function Description
Report correlation and drilling allows you to correlate reports, drill reports by object and time,
drill down to KPI formula, and correlate KPIs with reports for analysis.
l Correlating reports: If there are service relationships between multiple performance
reports of one object type, users can correlate these reports. This improves data query
efficiency and facilitates quick troubleshooting.
l Drilling reports by object and time and drilling down to KPI formula:
Drilling reports by object: The PRS supports report drilling by different object
levels. For example, drilling from the entire network to BSCs, from a BSC to cells
under the BSC, from carriers to a cell, from cells to a BSC, and from BSCs to the
entire network.
Drilling reports by time: The PRS supports report drilling by different time levels.
For example, drilling a month to days, from a day to hours, from hours to a day,
from days to a week, and from days to a month.
Drilling KPIs: The PRS allows users to search the composition of a KPI formula
and the counter values used for calculating the KPI when the KPI value exceeds the
threshold.
l Correlating KPIs with reports: If reports are correlated with a KPI, users can drill the
reports correlated with the KPI by selecting the KPI and object dimensions during report
query. This helps solidify OM experience for facilitating problem analysis.
GUI
Navigation path of the GUI for correlating reports
l Correlating reports: On the Report Management page of the web-based PRS client,
select a report in the report list and choose > Configure Related Report next to
the report name.
l Querying correlated reports: You can query the correlated reports of a report in the query
results after you set the correlations between reports.
On the query result page of the web-based PRS client, select a result record and select
Associated Query > Report name from the displayed menu.
l On the query result page of the web-based PRS client, click a time period by which you
want to drill data and select *** from the displayed menu. The characters *** indicates
the time dimension for drilling.
On the KPI Management page of the web-based PRS client, click in the
Operation column of the KPI you want to correlate with reports in the KPI list.
l Querying correlated reports of a KPI: After you set correlations between the KPI and the
reports, you can query the correlated reports of a KPI in the query results.
On the query result page of the web-based PRS client, click a cell in a KPI column and
select KPI Associated Report > Report name from the displayed menu.
Function Description
The web-based GIS support includes the following functions:
l The web-based GIS integrates third-party maps such as Google Maps or local map
servers such as ArcGIS Server and provide a web-based management page. You can
manage the map-related parameters.
l You can zoom in or out on a map, drag, measure distance, view the panorama of a map,
and select a rectangular area on the map.
l You can view engineering parameters on a GIS map. Key engineering parameters are
displayed in a floating window. The GIS also supports the geographical display of base
stations related to capacity visibility reports and cells based on engineering parameters.
l You can filter cells and objects based on engineering parameters on the map.
l You can select NEs, cells, and objects, and create object groups the GIS map.
l It renders cells or base stations (only base stations related to capacity visibility reports).
You can define the rendering colors and thresholds.
l You can navigate to the GIS from the query results of reports, KPI insight, or capacity
visibility.
GUI
Figure 2-16 show the web-based GIS. Navigation path:Choose GIS on the web-based PRS
client.
3 Typical Application
preset thresholds, you can analyze the causes and solve the problems accordingly to ensure
that the network runs properly.
3.2 KPI Insight
This section describes the KPI insight feature. Different from common KPI statistical tools
(providing only reports), the PRS allows users to obtain the network performance data for
monitoring network performance from each network object dimension by using one-click
query, and displays network performance data in indicator charts, charts, and reports. The
feature has integrated rich network optimization experience, which helps users perform
network quality correlated analysis. KPI insight supports the following object dimensions:
whole network, BSC/RNC, and cell cluster.
3.3 Benchmarking Management
The KPI benchmarking function of the PRS enables you to set benchmarking rules for the
specified KPIs of specified objects or object groups. By using the function, the PRS compares
the current value of the performance data and the benchmark value. Then, it identifies the
KPIs, objects, or object groups that change significantly in comparison with the benchmark
value. This helps network maintenance engineers quickly identify network exceptions and
improves problem locating efficiency.
The PRS collects traffic statistics reported by the NEs through the U2000. After analyzing the
statistics, the PRS generates network resource usage results, and displays the results.
1. NEs implement performance statistics dotting.
2. The U2000 periodically obtains performance counter measurement results from the NEs
based on measurement settings, and saves the results to the U2000 database.
3. The PRS periodically collects performance and configuration files from the data storage
directory of the U2000 and transfers the files to the data storage directory of the PRS
using FTP or SFTP.
4. The PRS processes the obtained files and saves the results to the PRS database.
5. Users query resource status, resources, resource historical trends, and traffic trends, and
view the query results in charts and tables on PRS GUIs. The PRS also displays resource
status in the topology view, GIS, and device panel.
6. Users export resource capacity reports using the report export function.
GUI
Figure 3-2 shows the Capacity Visibility page. Navigation path: Choose Topic > Capacity
Visibility on the web-based PRS client.
The capacity visibility function allows you to monitor and analyze network capacity resource
status, and set related thresholds during the monitoring and analysis.
l KPI Threshold Management
Users can set thresholds for network quality evaluation KPIs when monitoring and
analyzing network capacity resource status. The PRS renders KPI indicators based on
these thresholds. They can also modify the thresholds based on experience and scenario
requirements during monitoring and analysis.
l Monitoring of Network Capacity Resource Status
The capacity panel of the PRS displays status of base stations, base station controllers,
northbound interfaces, air interfaces, and their available resources. It can display the
status of multiple NEs that you have selected.
l Analysis of network capacity resource status
The PRS displays the resource usage of boards on board panels according to base station
controller types. Board data displayed on the panels is synchronized from board
configuration data. You can click a board to view its usage trend. The displayed
information is not affected by the board status such as active, standby, or online.
Function Specifications
Performance Counter Specification
Based on the rich KPI optimization experience of Huawei, the PRS presets monitoring models
for monitored key KPIs and network performance analysis models for correlated KPIs, and
thereby monitoring network KPIs from multiple object dimensions. In addition, it allows you
to drill down to correlated reports of abnormal KPIs to quickly locate problems that cause the
abnormal KPIs.
1. NEs collect performance KPIs.
2. The U2000 periodically obtains performance counter measurement results from the NEs
based on measurement settings, and saves the results to the U2000 database.
3. The PRS periodically collects performance and configuration files from the data storage
directory of the U2000 and transfers the files to the data storage directory of the PRS
using FTP or SFTP.
4. The PRS processes the obtained files and saves the results to the PRS database.
5. Users query monitored KPI status, KPIs, KPI historical trends and view the query results
in charts and tables on PRS GUIs. Users can also drill down to correlated reports of KPIs
for analysis. The PRS displays resource status in KPI indicators charts and tables and on
the GIS map.
6. Users export KPI reports using the report export function.
GUI
Figure 3-4 shows the KPI Insight page. Navigation path: Choose Topic > KPI Insight on
the web-based PRS client.
The KPI insight function allows you to monitor network quality KPIs and analyze root causes
of network quality problems, and set thresholds during the monitoring and analysis. It also
allows you to perform drill-down operations, view the trends of causes, and highlights data of
the same date.
l KPI threshold management
Users, onsite network optimization engineers, or network monitoring personnel can set
thresholds for network quality KPIs when monitoring network quality and analyzing
problems. This facilitates prompting and rendering of problematic KPIs. They can also
modify thresholds based on experience and scenario requirements during operations.
l Network quality monitoring
Based on the rich network OM experience of Huawei, key KPIs related to NEs of
different RATs are selected and used to monitor network quality from the dimensions of
entire network, GSM and UMTS base station controller and eNodeB, and cluster.
You can query KPIs according to report types and set the time range of report query.
After the report type and time range are set, the PRS automatically aggregates KPIs
monitored in a certain object dimension and displays corresponding trend charts in one-
click way. This helps you monitor network quality conveniently.
l Analysis of network quality root causes
The PRS presets the network performance analysis service models for typical KPIs. By
using the Drill by KPI function, users can further find correlated causes of a problem
KPI based on the service reports in the preset service model related to this KPI.
For example, during TCH call drop ratio analysis, you can separately analyze Call drop
rate > Call Drops Causes on Radio Interface in the Stable State > Radio Causes
Distributed Proportion On Call Drop > Radio Network Environment in sequence
and quickly locate root causes.
The PRS can perform online correlation analysis for problem KPIs, which improves the
efficiency of locating network quality problems.
Function Specifications
Performance Counter Specification
GUI
Figure 3-5 shows the KPI Benchmarking window. Navigation Path: Choose Performance
Report > Benchmark Management on the Java-based PRS client.
l Data collected before and after relocation is compared to identify the areas with poor
network quality. Data collected before relocation is used as the benchmark data. In this
way, network optimization can be performed effectively to ensure that network quality
has not been negatively impacted by relocation.
l Data collected before and after network optimization is compared to optimize network
performance and evaluate network optimization results. Data collected before network
optimization is used as the benchmark data.
l During routine monitoring, KPI benchmarking compares the performance measurement
data of an object with benchmark data calculated by using historical values. This helps
identify areas where KPIs change remarkably. This feature helps users quickly identify
network exceptions and increase troubleshooting efficiency.
Function Specifications
Performance Counter Specification
For details see Description > PRS Technical Specification in PRS Product Documentation.
NOTE
To obtain the PRS Product Documentation, log in to http://support.huawei.com and choose Product
Support > Wireless Network > SingleOSS > SingleOSS > M2000-Common > iManager PRS.