PRS Product Description

iManager PRS
V100R014
Product Description
Issue
03
Date
2014-09-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

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.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Web site:
http://www.huawei.com
Email:
support@huawei.com
Issue 033 (2014-09-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
iManager PRS Product Description
1 Product Positioning and Features
Contents
1 Product Positioning and Features .............................................................................................. 1
1.1 Product Positioning .......................................................................................................................................... 1
1.2 Product Features ............................................................................................................................................... 1
2 Architecture .................................................................................................................................... 6
2.1 Position on the Network ................................................................................................................................... 6
2.2 Hardware Devices ............................................................................................................................................ 8
2.3 Software Architecture ....................................................................................................................................... 9
3 Products and Application Scenarios ....................................................................................... 11

3.1 RAN Statistics Performance Visibility ........................................................................................................... 11
3.2 RAN Service Visibility ................................................................................................................................... 11
3.3 PS Service Visibility....................................................................................................................................... 12
3.4 Real-time Monitoring ..................................................................................................................................... 14
4 Configurations ............................................................................................................................. 15
4.1 Configurations of the PRS Server .................................................................................................................. 15
4.2 Configurations of a PRS Client ...................................................................................................................... 15
5 Technical Specifications ............................................................................................................ 17

5.1 Management Capacity .................................................................................................................................... 17
5.1.1 Server Management Capacity (RAN Statistics Performance Visibility) ............................................... 17
5.1.2 Server Management Capacity (RAN Service Visibility) ....................................................................... 18
5.1.3 Server Management Capacity (PS Service Visibility) ........................................................................... 19
5.1.4 Server Management Capacity (PS KPI Real-Time Monitoring + PRS Service Visibility) ................... 19
5.2 Physical Bandwidth Requirements ................................................................................................................. 20
5.3 Data Storage Specifications............................................................................................................................ 22
5.4 Safety Standards ............................................................................................................................................. 23
5.5 EMC Specifications ....................................................................................................................................... 24
5.6 Environmental Requirements ......................................................................................................................... 24
5.6.1 Storage Environment............................................................................................................................. 25
5.6.2 Shipping Environment .......................................................................................................................... 27
5.6.3 Operating Environment ......................................................................................................................... 29
6 Acronyms and Abbreviations ................................................................................................... 32
Issue 033 (2014-09-30)

ii
Product Positioning and Features
1.1 Product Positioning

PRS is a part of the SingleOSS@MBB solution. It gives operators insights into MBB network
quality and helps operators maximize the value of their network assets.
The PRS centrally manages the network devices in the GSM BSS, UMTS RAN, LTE RAN,
CDMA BSS, WiMAX RAN, TD-SCDMA RAN, SingleRAN, and core network (CN). The
PRS also provides the following solutions: traditional KPI Insightcentered network
performance analysis, end-to-end capacity resource visibility, PS MBB service traffic
visibility, and user experience visibility.
1.2 Product Features

Comprehensive MBB Network Visibility
Integrated with a data parsing database (provided through professional services) that involves
more than 1000 protocols and 600,000 IMEI-TACs, the PRS can parse 95% of the data on an
MBB network and analyze the parsed data in the network, service, subscriber, and terminal
dimensions. This helps plan and maintain the MBB network and promote MBB services.
The PRS can analyze terminal service and signaling models and identify network capacity
bottlenecks, which helps plan the MBB network.
The PRS can quickly locate abnormal KPIs and identify terminal signaling exceptions, which
helps improve network maintenance efficiency.
The PRS can identify and analyze valuable subscribers, over-the-top (OTT) services,
applications, and smart terminals, which helps establish precise marketing strategies.
Closed-Loop MBB Management

The PRS supports policy establishment and policy execution result evaluation. The
Plan-Do-Check-Adjust cycle helps telecom operators set up a smart closed-loop MBB
management system.
Issue 03 (2014-09-30)
Plan (Point A): policy establishment. With MBB network performance and resource
visibility, telecom operators can obtain detailed information about the network and
establish bandwidth management and service promotion polices accordingly.

Do: policy execution. After polices are established, the PRS implements policy delivery
and execution by converting the policies to network configurations. With Huawei's smart
bandwidth management solution, telecom operators can dynamically establish various
polices for bandwidth management and service control based on subscriber priorities,
subscribers' access types, subscribers using a certain service package, service types,
network conditions, service usage, and flexible combinations of the preceding
information. This enables telecom operators to have full control on the services carried
on the MBB network.
Check (Point B): policy execution result evaluation. Telecom operators can collect
information about the network again and check whether the established and executed
polices have the expected effect and determine whether to adjust them.
Adjust: Adjust polices to achieve the optimal effect based the evaluation result.
Figure 1-1 MBB closed-loop management model
Flexible and Efficient Platform for Analyzing Performance

The PRS provides an end-to-end platform for customizing reports and the KPI benchmarking
and KPI dashboard functions for users to monitor performance flexibly and efficiently.
Figure 1-2 shows the procedure for customizing reports in the PRS.
Figure 1-2 Procedure for customizing reports
Issue 03 (2014-09-30)
Customizing KPIs

The PRS allows users to define counter formulas by performing combined operations on
original KPIs, system KPIs, and predefined KPIs. The operations include addition,
subtraction, multiplication, and division. Users can also define conditional counters such
as worst cell ratio and busiest cell ratio by using counter formulas containing if, min,
max, count, avg, and sum conditions.
Customizing busy-hour rules

The PRS allows users to customize busy-hour rules and identify busy hours based on
specific scenarios.
Customizing reports
The PRS allows users to customize reports such as simple reports, comparison reports,
combined reports, and database-based query reports. Users can also modify, delete, move,
import, and export these custom reports as required.
Customizing report formats

By correlating reports with Excel templates, the PRS allows users to export report query
results using the predefined Excel templates. Users can also edit reports by using various
Excel functions, such as fonts, panes, formulas, charts, and macros.
Generating and delivering reports on schedule

The PRS automatically generates reports based on the preset time and period. The
reports generated on schedule are delivered to a specified email box or FTP server. In
this way, users can obtain the reports by receiving emails or viewing files on the FTP
server.
Performance Analysis Expert

The PRS is the performance analysis expert and has the following advantages over third-party
software for northbound performance analysis:
Reduced data delay: less than 30 minutes
Enriched performance analysis themes: capacity visibility, KPI insight, and traffic trend
analysis
Short data delay improves the performance analysis efficiency.
For original performance data of Huawei devices whose measurement period is 30
minutes or above, the interval between data generation on Huawei devices and data
display on the PRS is less than 30 minutes. For original performance data whose
measurement period is 15 minutes, the interval between data generation and data display
on the PRS is less than 15 minutes. The data delay of third-party northbound
performance analysis software is usually greater than one hour. For example, the data
delay of MYCOM is five hours.
Performance analysis themes integrated with Huawei performance analysis
experience helps users quickly locate problems.
a. Capacity visibility helps users quickly locate network capacity bottlenecks.
The PRS collects performance data, configuration data, and license data of Huawei
devices periodically, and calculates predefined capacity KPIs automatically. The PRS
also displays capacity alarms on the entire network in predefined capacity visibility
reports and provides KPI alarms and GIS analysis functions for users to quickly
locate capacity bottlenecks.
In addition, the PRS provides the traffic trend prediction feature. This guarantees
network construction and traffic in festivals and holidays.
b.
Issue 03 (2014-09-30)
KPI insight helps users quickly locate abnormal network KPIs.

c.
Integrated with Huawei's rich experience in KPI analysis and the correlations
between KPIs and reports, the PRS monitors KPI alarms on the network. If KPI
alarms are detected, the PRS can quickly locate causes of abnormal KPIs through the
predefined correlations between KPIs and reports.
Multifunctional performance analysis platform supports quick and flexible
performance analysis.
The PRS allows users to customize object groups based on scenario characteristics
and provide scenario data aggregation and accurate performance analysis.
The result drilling and correlation query functions help users further analyze network
problems.
The GIS geographic observation supports the display of sites and cells in the GIS
window with cell performance data in different colors. This helps users analyze
network performance easily and efficiently.
Real-time KPI Monitoring

The PRS provides 1-minute KPI monitoring for the GSM BSS, UMTS RAN, and LTE RAN,
which helps users detect and rectify network risks in time during major events or holidays,
and therefore ensuring network stability.
The PRS allows users to select KPIs for monitoring. The PRS displays the data of the
KPIs in charts, thereby helping users monitor the changes of importance KPIs in real
time. The PRS also supports automatic screen scrolling, which helps users monitor
multiple themes or hotspots.
The PRS supports integrated monitoring and comparison monitoring on KPIs and
displays results in monitoring charts, which facilitates comparison and monitoring.
The PRS allows users to set a threshold line for each monitoring chart, which enables
users to quickly identify abnormal KPIs.
The PRS monitors and aggregates the real-time monitoring data of KPIs in specified
regions or hotspots, and then displays the aggregation results. This enables users to
monitoring the network status.
For the same KPI for multiple objects, the PRS displays the objects whose KPI values
are deteriorated and provides the possible causes.
The PRS allows users to select multiple objects at a time by selecting an object group.
By monitoring the object group and the Top N objects in the group, users can quickly
identify the objects which have abnormal KPIs.
Efficient and Intelligent Performance Threshold Alarms

It is inefficient for users to monitor network performance KPIs for a long period of time to
check for network risks and faults. The PRS automatically monitors network performance
counters, checks for risks and faults, and then reports performance threshold alarms to notify
users of risks and faults. Therefore, the O&M efficiency is improved.
When the NE performance results meet the trigger conditions for threshold alarms, the
PRS generates threshold alarms, and reports the alarms to the U2000. The performance
data for triggering threshold alarms is reported every 60 minutes or 24 hours. The object
dimension can be raw object or aggregation object.
Users can check whether performance data exceeds thresholds based on threshold and
incremental alarms.
Issue 03 (2014-09-30)

The algorithm principle for threshold alarms is as follows: When the value of a KPI
exceeds the preset threshold, a threshold alarm is generated. When the value is less than
the preset threshold, the alarm is cleared.
The algorithm principle for incremental alarms is as follows: When the offset (absolute
value or percentage) of a KPI in the current and latest periods exceeds the preset
threshold, an incremental alarm is generated.
Issue 03 (2014-09-30)

2 Architecture
Architecture
The PRS consists of the PRS server, PRS clients, and networking devices. The PRS software
consists of the PRS server software and PRS client software. The server software runs on the
PRS server, and the client software runs on a PRS client.
2.1 Position on the Network

If a statistics performance visibility PRS is deployed, HP DL 580, HP DL 980, or an ATAE
board can serve as the PRS server based on network scales.
If a service visibility PRS is deployed, only an ATAE board can serve as the PRS server, and
the configuration of ATAE boards varies based on networking scenarios and network scales.
Scenario 1 - Non-U2000 southbound and northbound network isolation

As shown in Figure 2-1. When the non-U2000 southbound and northbound network isolation
solution is used,
Raw statistics performance data on NEs is reported to the PRS server through the U2000.
The PSSAU can be deployed with PRS on the OSS side or independently deployed on
the NE side. PSSAUs deployed in different locations must use channels in the same
network to report data.
a.
User plane logs on the GGSN/P-GW are reported to the PRS server through the
service network between the GGSN/P-GW and the PSSAU.
b. Signaling plane logs on the SGSN/MME are reported to the PRS server through the
OM network between the SGSN/MME and the PSSAU.
c.
Issue 03 (2014-09-30)
User subscription logs on the policy and charging rules function (PCRF) are
reported to the PRS server through the service network between the PCRF and the
PSSAU.
BWM rule data and sampling rate information on the GGSN/P-GW are reported to the
PRS server through the OM network between the GGSN/P-GW and the U2000.

2 Architecture
Figure 2-1 Networking of the PRS system (non-U2000 southbound and northbound network
isolation)
NMS
Nastar
PRS Client
U2000 Client
Other
MCounter
FTP/Corba
U2000 Server
u se
rp
lan
on
pti
gp
PSSAU
cr i
alin
g
e lo
bs
sign
su
MML
lo
lane
us
er
MML
log
PRS Server
NEs
SGSN/MME
GGSN/P-GW
PCRF
OM network
GGSN/P-GW service network
PCRF service network
Scenario 2 - U2000 southbound and northbound network isolation

As shown in Figure 2-2. When the U2000 southbound and northbound network isolation
solution is used,
Raw statistics performance data on NEs is reported to the PRS server through the U2000.
PSSAUs deployed in different locations must use channels in different networks to

report data.
a.
If the PSSAU and PRS server are deployed in the same cabinet, the PSSAU has to
report data using the northbound network because the communication between the
PRS server and the U2000 and inside the PRS is based on the northbound network.
b. If the PSSAU is independently deployed on the NE side where only the OM network,
instead of the northbound network, is deployed, data is reported to the PRS server
only through the OM network.
Issue 03 (2014-09-30)
BWM rule data and sampling rate information on the GGSN/P-GW are reported to the
PRS server through the OM network between the GGSN/P-GW and the U2000.

2 Architecture
Figure 2-2 Networking of the PRS system (U2000 southbound and northbound network isolation)
Northbound
Network
NMS
Nastar
PRS Client
PSSAU
(PSSAU and PRS Server are
deployed in the same cabinet)
U2000 Client
Other
MCounter
a
MM
MM
signalin
g plan
NEs
SGSN/MME
log
an
ne
pl
pla
er
si g
in
al
us
Southbound
Network
g
lo
GGSN/P-GW
Co
un
te
r
on log
PRS Server
U2000 Server
user subscripti
orb
FTP/C
e log lane log

p
u se r
n
er tio
u s cr i p
bs log
u
s
PSSAU
PCRF
Northbound network
OM network
GGSN/P-GW service network
PCRF service network
2.2 Hardware Devices

The PRS system typically consists of PRS servers, PRS clients, alarm boxes, and some
networking devices. See Figure 2-3.
Figure 2-3 PRS hardware devices
Client 1
Client 2
Disk array
Issue 03 (2014-09-30)
Client N
ATAE subrack

2 Architecture
2.3 Software Architecture

The PRS software consists of the PRS server software and PRS client software. Figure 2-4
shows the software architecture of the PRS.
Figure 2-4 Software architecture of the PRS
Table 2-1 describes the components of the PRS system.

Table 2-1 Components of the PRS system
Component
Description
U2000
The U2000 is a centralized element management system (EMS) of

mobile networks. It manages NEs in a centralized manner.
PSSAU
Issue 03 (2014-09-30)
It collects the performance data from devices on GSM BSS,

UMTS RAN, LTE RAN, CDMA BSS, WiMAX RAN,
TD-SCDMA RAN, SingleRAN, and core networks, and reports to
the PRS server through the FTP interface.
It collects the BWM rule data and sampling rate information on

the GGSN/P-GW and reports to the PRS server through the FTP
interface.
It collects and preprocesses the user plane logs generated by the

GGSN/P-GW, the signaling plane logs generated by the SGSN/MME,
and the user subscription logs generated by the PCRF to meet the PRS
analysis requirements.

2 Architecture
Component
Description
PRS server
The PRS server can be divided into the following categories according
to different application scenarios:
Performance statistics server: Collects performance data and

configuration data from the U2000, parses the data, and generates
analysis results.
Service visibility server: Collects service data of the MBB network

from the PSSAU, parses the data, and generates analysis results.
KQI visibility server: Collects RNC log data from the Trace Server
of U2000, parses the data, and generates analysis results.
PRS client
Issue 03 (2014-09-30)
Real-time monitoring (RTM) server:

1. Collects NE performance statistics data from the U2000 to
implement one-minute-level KPI monitoring.
2. Collects real-time control plane (CP) and user plane (UP) data
from PSSAU, parses the data, and displays the results on the
monitoring GUI.
The PRS client software provides graphical user interfaces (GUIs) to

display the analysis results intuitively. You can log in to the PRS
server from either the Java-based PRS client or Web-based PRS client
and perform the corresponding operations after successfully login.

10
3 Products and Application Scenarios
Products and Application Scenarios
The PRS provides the visualization of network performance and service usage, which
facilitate network operation and maintenance.
3.1 RAN Statistics Performance Visibility

The PRS supports statistics performance visibility in different stages:
During network adjustment such as network relocation and NE upgrade, users can
compare the network performance before and after the adjustment by using the KPI
benchmarking function.
During network optimization, users can detect abnormal KPIs in real time and quickly
locate these KPIs based on the KPI Insight function.
During network maintenance, users can customize performance monitoring reports to

monitor network performance automatically based on the end-to-end platform for
customizing reports. With the network capacity visibility function, users can quickly
identify the bottlenecks of network capacity and adjust the network accordingly.
3.2 RAN Service Visibility
Service KQI visibility

For widely used services, such as web, video, and basic voice services, this feature helps
telecom operators learn user experience, and provides references for future user
experience improvement.
Specified subscriber KQI visibility

This feature helps to analyze experience of subscribers with specific scheduling priority
indicator (SPI) values, and better and faster optimize the network to improve experience
of such subscribers.
Terminal KQI visibility
Issue 03 (2014-09-30)
This feature allows users to analyze the relationships between terminal types and
subscriber experience so that the users can easily find the types of terminals with
poor subscriber experience. Then, users can optimize the network or motivate
terminal vendors to optimize terminals, thereby improving subscriber experience.

11
3.3 PS Service Visibility

The PRS supports service visibility in multiple dimensions:
Network Traffic Statistics
Application Traffic Statistics
Issue 03 (2014-09-30)
This feature helps telecom operators analyze traffic distribution and bandwidth usage
trend of websites and servers and identify frequently visited websites and servers in
the network. Based on the preceding information, telecom operators can prepare the
corresponding optimization policies to improve subscriber experience, such as
accelerating the network access or providing mirrored backup.
Blocked Traffic Statistics
This feature enables telecom operators to learn about the data service usage of
subscribers, identify TopN subscribers, and ensure service quality for important
subscribers.
Website Traffic Statistics
This feature helps telecom operators analyze smartphone behaviors so that they can
prepare corresponding policies to reduce the impact of smartphone usage on network
performance and improve subscriber experience.
Subscriber Traffic Statistics
This feature enables telecom operators to analyze the number and penetration of
different terminal types and terminals running in different operating systems. The
analysis results provide references for application promotion and service prediction.
Smartphone Traffic Statistics
This feature helps telecom operators collect statistics on the traffic ratio of each
application so that they can implement service control polices accordingly to provide
services required by subscribers. This helps telecom operators protect highly
profitable services and control the bandwidth usage of low-profit services.
Terminal Penetration Statistics
In the GSM, UMTS, and LTE networks, telecom operators can collect statistics on
the traffic and bandwidth change trend of services by NE, APN, RAT, and area to
identify TopN applications and services of each APN and RAT. For example, during
routine network maintenance, telecom operators can query the total traffic of a
network and analyze traffic distribution and bandwidth change trend of each NE. In
this way, they can identify light-load and overload NEs and adjust network planning
to improve resource usage and subscriber experience.
In a mobile network, the traffic is blocked if the traffic of a package is used up. In
addition, the data stream of certain subscribers may be discarded based on P-GW
control rules. In both cases, subscriber experience is affected. Telecom operators can
view block traffic, block traffic ratio, and TopN servers suffering traffic block in the
block traffic statistics report.
Policy and Rules Usage Statistics
It collects statistics on network traffic and bandwidth controlled by using Policy and
Charging Control (PCC) and Bandwidth Management (BWM) rules. These statistics
provide data references for telecom operators to adjust the rules.
This feature enables telecom operators to view, evaluate, and optimize the effect of
service control policies, helping telecom operators establish the optimal
service-differentiated policies to maximize revenues.
Service Plan Usage Statistics

12
This feature collects statistics on the traffic distribution of subscribers roaming

outside a PLMN in each PLMN, the distribution of subscribers roaming to a PLMN,
and the specific service traffic.
This feature helps telecom operators collect statistics on the traffic generated for
roaming subscribers so that they can design appropriate roaming service packages.
Smartphone Abnormal Event Statistics
This feature enables the PRS to collect statistics on TopN subscribers for TopN
websites by traffic, helping telecom operators establish accurate marketing strategies.
The PRS can also identify TopN websites for specified subscribers, helping telecom
operators maintain and optimize the related network resources accurately.
VoIP Call Statistics
Issue 03 (2014-09-30)
Based on the statistics on the traffic of smartphone browsers, telecom operators can
identify mainstream browsers used by subscribers, and consider implementing deep
cooperation with mainstream browser vendors to benefit from service providers (SPs)
by providing differentiated services or jointly deploying a network.
Website and Subscriber Associated Statistics
Signaling behaviors of smartphones vary according to the function implementation

mechanisms of smartphone models. Therefore, the signaling loads caused by
smartphones on the network also vary according to smartphone models. The PRS can
identify smartphone models that have frequent signaling interaction (such as Service
Request and Paging), helping telecom operators accurately evaluate the impact on
network signaling load based on the market share of these terminal models. Then,
telecom operators can take corresponding measures to prevent signaling storms.
Smartphone Browser Traffic Statistics
Different OTT services generate different network signaling loads. This feature helps
telecom operators learn about signaling usage characteristics of various OTT
applications. Then, telecom operators can perform network planning and
optimization based on network service situations to improve network resource usage.
Roaming Traffic Statistics
This feature enables the PRS to collect statistics on actual signaling behaviors of
smartphones. Telecom operators can view the signaling model for each major
signaling procedure (such as Service Request and Paging) by terminal model and OS
type in networks of different RATs and analyze subscriber distribution based on
signaling segments. This provides references for network planning and development.
Application Signaling Usage Statistics
The Tethering service is available and frequently used in many mobile networks.
Based on the statistics on the traffic and subscriber distribution of the Tethering
service collected by the PRS, telecom operators can learn about the current status and
development trend of this service and design appropriate service packages.
Smartphone Signaling Usage Statistics
In a mobile network, telecom operators need to analyze the number of subscribers,

traffic, quota usage, and ratio of over-usage subscribers for each package. Based on
the analysis results, telecom operators can determine whether packages are properly
designed, provide more competitive packages, and establish marketing policies for
over-usage subscribers.
Tethering Traffic Statistics
The PRS provides the voice over Internet Protocol (VoIP) service analysis function
for analyzing usage of the VoIP service on networks to help telecom operators

13
evaluate the impact of the VoIP service on the traditional voice service and provide
reference information for telecom operators to make decisions on services.
Roaming KPI Analysis
By collecting statistics about the traffic statistics counters related to roaming service
activation, the PRS helps telecom operators identify the areas where the roaming
service activation success rate is low and conduct network adjustment.
3.4 Real-time Monitoring
PS KPI real-time monitoring

For PS networks, this feature provides 1-minute KPI monitoring on signaling procedures
and allows users to set thresholds for KPIs to be monitored by each monitoring task.
This helps users check whether the value of each KPI exceeds the threshold, and quickly
detect network exceptions and locate problems through the drilldown function, thereby
reducing mean time to repair (MTTR).
Subscriber-based real-time traffic monitoring

For PS networks, this feature allows users to view the traffic of specific subscribers. The
PRS displays traffic data for 10 subscribers every five minutes. The traffic data includes
uplink traffic, downlink traffic, and total traffic. This helps users detect network risks
and solve network problems in time, thereby ensuring network stability during major
events or holidays. In addition, the PRS traces the traffic of specified subscribers.
Therefore, telecom operators can provide VIP services and reduce complaints.
Issue 03 (2014-09-30)

14
4 Configurations
Configurations
The PRS works in client/server (C/S) and browser/server (B/S) modes and allows the
connection of multiple clients.
4.1 Configurations of the PRS Server

If the PRS is deployed in the ATAE subrack, the number of boards to be configured varies
based on the network scale. Each board is configured in the same way. For details, see Table
4-1. The S3900 disk array is configured based on the deployment of OSS software. For details,
see iManager 14.0 Configuration Principle(ATAE Cluster&PC Server).
Table 4-1 Configuration of a PRS board
Item
Configuration
CPU
1 x 2.4 GHz (hexa-core)
Memory
48 GB
Hard disk
None
Operating system
SUSE Linux10 SP4 (X86_64)
Database software
Oracle 11g
4.2 Configurations of a PRS Client

Table 4-2 lists the minimum configuration requirements of a PRS client. If users log in to the
PRS server through the Citrix client, the PC used for login can be configured based on
requirements lower than those listed in this table.
Issue 033 (2014-09-30)

15
4 Configurations
Table 4-2 Minimum configuration requirements of a PRS client

Item
Configuration
CPU
E5300 or above
Memory
4 GB
Hard disk
320 GB or above
Accessory
DVD-RW/Ethernet adapter/19-inch LCD
Operating system
Windows 7 Professional
Windows XP Professional Service Pack 3 (32-bit) or a later version
Windows XP Professional Service Pack 2 (64-bit) + KB968730

patch
Windows Server 2008 (64-bit)
Windows Server 2003 R2 Service Pack 2 (32-bit) + KB968730

patch
Office 2007 or a later version
Firefox 10.0, Firefox 11.0 or Firefox 12.0 or IE 10.0
PRS client software
Application
software
Browser
Issue 03 (2014-09-30)
Firefox 17.0 is recommended and is compatible with Firefox 10.0,

Firefox 11.0, and Internet Explorer 10.0.

16
5 Technical Specifications
Technical Specifications
5.1 Management Capacity

Servers of varied management capacities are configured when different PRS features are
applied.
NOTE
When RAN statistics performance visibility and RAN service visibility are both enabled on the PRS,
they can share the standby service board and standby database board.
The management capacity of each server is measured by equivalent NE, equivalent subscriber, or
equivalent traffic. For details about the conversion relationship, see section "Description of
Management Capability" in iManager 14.0 Configuration Principle(ATAE Cluster&IBM PC Server).
If any algorithm for calculating is not included in the document, contact Huawei technical support.
The number of equivalent NEs is obtained by converting the number of physical NEs.
The number of equivalent subscribers is obtained by converting the number of simultaneously

attached users (SAUs).
The volume of equivalent traffic is obtained by converting the amount of traffic on the live
network.
5.1.1 Server Management Capacity (RAN Statistics Performance

Visibility)
Table 5-1 PRS server management capacity (RAN statistics performance visibility)
Management Capacity
(Number of Equivalent NEs)
ATAE Board Configuration
800
2 PRS server boards (1 master and 1 standby) + 2 PRS

DB boards (1 master and 1 standby)
1200
3 PRS server boards (1 master, 1 slave, and 1 standby)

+ 3 PRS DB boards (1 master, 1 slave, and 1 standby)
1600

2000

Issue 03 (2014-09-30)

17
5.1.2 Server Management Capacity (RAN Service Visibility)

Table 5-2 PRS server management capacity (RAN service visibility)
Management Capacity
(Equivalent Gbit/s)
5.0
3 PRS MBB RAN server boards (1 master, 1 slave, and 1

standby) + 2 PRS MBB RAN DB boards (1 master and 1
standby)
10.0

standby) + 3 PRS MBB RAN DB boards (1 master, 1 slave, and
1 standby)
20.0

1 standby)
40.0

1 standby)
Table 5-3 Trace Server management capacity (RAN service visibility, the TS and U2000 are
deployed in a cluster)
Management Capacity
(Number of
Equivalent
Subscribers)
20.0
1 Trace Server board (1 master)
40.0
2 Trace Server boards (1 master and 1 slave)
Table 5-4 Trace Server management capacity (RAN service visibility, the TS is independently
deployed in a cluster)
Management Capacity
(Number of
Equivalent
Subscribers)
20.0
2 Trace Server boards (1 master and 1 standby)
40.0
3 Trace Server boards (1 master, 1 slave, and 1 standby)
Issue 03 (2014-09-30)

18
5.1.3 Server Management Capacity (PS Service Visibility)

Table 5-5 PRS server management capacity (PS service visibility)
Management Capacity
(Number of Equivalent
Subscribers)
1,000,000
3 PRS MBB PS server boards (1 master, 1 slave, and 1 standby)

+ 3 PRS MBB PS DB boards (1 master, 1 slave, and 1 standby)
2,500,000

5,000,000

7,500,000

Table 5-6 PSSAU server management capacity (PS service visibility)

Management
Capacity
(Equivalent Gbit/s)
10.0
3 PSSAU server boards (1 master, 1 slave,

and 1 standby)
25.0

and 1 standby)
50.0

and 1 standby)
75.0
13 PSSAU server boards (1 master, 11

slave, and 1 standby)
100.0
16 PSSAU server boards (1 master, 14

slave, and 1 standby)
The PSSAU is used to collect user-plane log data on the GGSN or P-GW, control-plane log
data on the SGSN or MME, and subscriber subscription log data on the PCRF. Then the
PSSAU preprocesses the data to meet PRS requirements.
5.1.4 Server Management Capacity (PS KPI Real-Time Monitoring +

PRS Service Visibility)
The PS KPI real-time monitoring and PRS service visibility features need to be deployed on
both the PRS and PSSAU sides.
Issue 03 (2014-09-30)

19
Table 5-7 PRS server management capacity (PS KPI real-time monitoring + PRS service
visibility)
Management Capacity
(Number of
Equivalent SAUs)
5,000,000
1 PRS RTM server board (1 master)

NOTE
Two features share DB boards and standby service boards.
10,000,000
2 PRS RTM server boards (1 master and 1 slave)

NOTE
Two features share DB boards and standby service boards.
Table 5-8 PSSAU server management capacity (PS KPI real-time monitoring + PRS service
visibility)
Management Capacity
(Number of
Equivalent
Subscribers)
5,000,000
2 PSSAU RTM server boards (1 master and 1 slave)

NOTE
Two features share standby service boards.
10,000,000
4 PSSAU RTM server boards (1 master and 3 slave)

NOTE
Two features share standby service boards.
5.2 Physical Bandwidth Requirements

Table 5-9 describes the physical bandwidth requirements between the PRS server and
peripheral systems.
Table 5-9 Bandwidth requirements between the PRS server and U2000 server or PRS client
Physical Entity
Bandwidth Requirement (Mbit/s)
PRS and M2000 servers
100 Mbit/s or higher
PRS server and PRS client
10 Mbit/s or higher
Issue 03 (2014-09-30)

20
Table 5-10 Bandwidth requirements between the PSSAU and PRS

Management Capacity (Number of
Equivalent Subscribers)
1,000,000
30
2,500,000
75
5,000,000
150
7,500,000
225
Table 5-11 Bandwidth requirements between the PSSAU and UPCC

Management Capacity (Number of
Equivalent Subscribers)
1,000,000
2,500,000
5,000,000
12
7,500,000
18
Table 5-12 Bandwidth requirements between the PSSAU and USN

Management Capacity
(Number of Equivalent
Subscribers)
Bandwidth
Requirement (Mbit/s)
Bandwidth Requirement
(Mbit/s)
USN OMU
USN EVU
1,000,000
30
2,500,000
15
75
5,000,000
30
150
7,500,000
45
225
Table 5-13 Bandwidth requirements between the PSSAU and U-GW

Management Capacity (Volume of
Equivalent Traffic)
10 Gbit/s
200
25 Gbit/s
500
50 Gbit/s
1000
75 Gbit/s
1500
Issue 03 (2014-09-30)

21

Equivalent Traffic)
100 Gbit/s
2000
Table 5-14 Bandwidth requirements between the PSSAU and NMS

Equivalent Traffic)
10 Gbit/s
30
25 Gbit/s
75
50 Gbit/s
150
75 Gbit/s
225
100 Gbit/s
300
Table 5-15 Bandwidth requirements between the Trace Server and PRS
Management Capacity (Volume of RAN
Traffic)
5 Gbit/s
10
10 Gbit/s
20
20 Gbit/s
40
40 Gbit/s
80
5.3 Data Storage Specifications

Table 5-16, Table 5-17, and Table 5-18 list the specifications for saving data on the PRS.
Table 5-16 Data storage specifications (RAN statistics performance visibility)
Data
Default Storage Duration
Raw data (unit: day)
Hour granularity data (unit: day)
31
Day granularity data (unit: day)
180
Week granularity data (unit: week)
106
Month granularity data (unit: month)
36
Issue 03 (2014-09-30)

22
Data
Daily busy hour data (unit: day)
93
Weekly busy hour data (unit: week)v
106
Monthly busy hour data (unit: month)
36
Maximum storage duration of data

generated during holidays (unit: month)
13
Storage duration of raw data (unit: day)
32
Maximum number of days within holidays

(unit: day)
Table 5-17 Data storage specifications (RAN service visibility)

Data
14
92
Table 5-18 Data storage specifications (PS service visibility)

Data
5 minute raw data (unit: day)
7
NOTE
Only the following reports support data stored

on a five-minute basis: Network > By
Network Element, Network > By APN,
Network > By RAT, Network > By Rules,
Network > By Blocked Traffic,
Subscriber > TopN Subscribers,
Subscriber > Specified Subscriber (Group).
14
92
Week granularity data (unit: week)
52
Month granularity data (unit: month)
36
5.4 Safety Standards

The PRS complies with the following safety standards:
Issue 03 (2014-09-30)

23
IEC 60950-1
IEC/EN41003
EN 60950-1
UL 60950-1
CSA C22.2 No 60950-1
AS/NZS 60950-1
BS EN 60950-1
IS 13252
GB4943
5.5 EMC Specifications

The PRS complies with the following Electromagnetic Compatibility (EMC) standards:
CISPR22 Class A
EN55022 Class A
EN50024
ETSI EN 300 386 Serial Class A
ETSI EN 301 489 Class A
ICES 003 Class A
AS/NZS CISPR22 Class A
GB9254 Class A
VCCI Class A
CNS 13438 Class A
5.6 Environmental Requirements

The environmental requirements of the PRS involve three types of environments: storage
environment, shipping environment, and operating environment. The PRS complies with the
following specifications:
GB 4798 Application environmental conditions of electric and electronic products
ETS 300019 Equipment Engineering (EE); Environmental conditions and environmental

tests for telecommunications equipment
IEC 60721 Classification of environmental conditions
Issue 03 (2014-09-30)

24
5.6.1 Storage Environment

Climatic Requirements
Table 5-19 Climatic requirements for storage
Item
Value Range
Temperature
-20C (-4F)60C (140F)
Relative humidity
8%93%
Altitude
5000 m
Atmospheric pressure
70 kPa106 kPa
Solar radiation
1120 W/m
Heat radiation
600 W/m
Wind speed
30 m/s
Waterproof Requirements
Field equipment must be stored indoors.
Water does not accumulate on the ground or fall on the package.
The equipment is kept away from water sources such as a hydrant and
air-conditioner.
In the case of outdoor storage, the following requirements must be met:
The package is intact.
Waterproof measures are taken to prevent water penetration.
Water does not accumulate on the ground or fall on the package.
The package is not exposed directly to sunlight.
Biological Requirements
The environment should not be conducive to the growth of fungus or mildew.
There should be no rodents such as rats.
Air Purity Requirements
The air must be free of explosive, conductive, magnetic conductive, or corrosive dust.
The density of physically active materials must comply with the requirements listed in
Table 5-20.
Table 5-20 Requirements for the density of physically active materials

Physically Active Material
Unit
Density
Suspended dust
mg/m
5.00
Issue 03 (2014-09-30)

25
Unit
Density
Deposited dust
mg/mh
20.0
Sand
mg/m
300
Suspended dust: diameter 75 m
Deposited dust: 75 m diameter 150 m
Sand: 150 m diameter 1000 m
The density of chemically active materials must comply with the requirements listed in
Table 5-21.
Table 5-21 Requirements for the density of chemically active materials

Chemically Active
Material
Unit
Density
SO2
mg/m
0.30
H2S
mg/m
0.10
NO2
mg/m
0.50
NH3
mg/m
1.00
Cl2
mg/m
0.10
HCl
mg/m
0.10
HF
mg/m
0.01
O3
mg/m
0.05
Mechanical Stress Requirements

Table 5-22 Mechanical stress requirements
Item
Sub-Item
Value Range
Sinusoidal vibration
Offset
7.0 mm
Accelerated speed
20.0 m/s
Frequency range
2 Hz9 Hz
9 Hz200 Hz
Impact response spectrum

II
250 m/s
Unsteady impact
Issue 03 (2014-09-30)

26
Item
Sub-Item
Value Range
Static payload
5 kPa
Impact response spectrum: refers to the maximum acceleration response curve generated by the
equipment under specified impact excitation. Impact response spectrum II means that the duration of
semi-sine impact response spectrum is 6 ms.
Static payload: refers to the capability of the equipment to bear the pressure from the top when it is
packed in the normal pile-up method.
5.6.2 Shipping Environment

Table 5-23 Climatic requirements for shipping
Item
Value Range
Temperature
-20C (-4F)60C (140F)
Relative humidity
8%93%
Altitude
5000 m
70 kPa106 kPa
Solar radiation
1120 W/m
Heat radiation
600 W/m
Wind speed
30 m/s
Waterproof Requirements
Before shipping the equipment, ensure that the following requirements are met:
The package is intact.
Waterproof measures are taken to prevent water penetration.
No water is accumulated inside the shipping vehicle.
Issue 03 (2014-09-30)

27
Table 5-24.

Unit
Density
Suspended dust
mg/m
Deposited dust
mg/mh
3.0
Sand
mg/m
100
Suspended dust: diameter 75 m
Deposited dust: 75 m diameter 150 m
Sand: 150 m diameter 1000 m
Table 5-25.

Chemically Active Material
Unit
Density
SO2
mg/m
0.30
H2S
mg/m
0.10
NO2
mg/m
0.50
NH3
mg/m
1.00
Cl2
mg/m
0.10
HCl
mg/m
0.10
HF
mg/m
0.01
O3
mg/m
0.05

Table 5-26 Mechanical stress requirements for shipping environment
Item
Sub-Item
Value Range
Sinusoidal
vibration
Offset
7.5 mm
Accelerated speed
20.0 m/s
40.0 m/s
Frequency range
2 Hz9 Hz
9 Hz200 Hz
200 Hz500
Hz
Issue 03 (2014-09-30)

28
Item
Sub-Item
Value Range
Random
vibration
Spectrum density of
accelerated speed
10 m/s
3 m/s
1 m/s
Frequency range
2 Hz9 Hz
9 Hz200 Hz
200 Hz500
Hz
Impact response
spectrum II
300 m/s
Static payload
10 kPa
Unsteady
impact
Static payload: refers to the capability of the equipment in package to bear the pressure from the top
in normal pile-up method.
5.6.3 Operating Environment

Table 5-27 Temperature and humidity requirements for operation
Temperature
Relative Humidity
5C (41F)35C (95F)
20%80%
The values are measured 1.5 m above the floor and 0.4 m in front of the equipment, without protective
panels in front of or behind the cabinet.
Short-term operation means that the continuous working hours are shorter than 48 and the total working
days per year are fewer than 15 days.
Table 5-28 Other climatic requirements for operation

Item
Value Range
Altitude
4000 m
70 kPa106 kPa
Solar radiation
700 W/m
Heat radiation
600 W/m
Wind speed
1 m/s
Issue 03 (2014-09-30)

29
Table 5-29.

Physically Active
Material
Unit
Density
Dust particle
particle/m
3 x 104
(No visible dust exists on the desktop
within three days.)
Dust particle: diameter 5 m
Table 5-30.

Chemically Active
Material
Unit
Density
SO2
mg/m
0.20
H2S
mg/m
0.006
NH3
mg/m
0.05
Cl2
mg/m
0.01

Table 5-31 Mechanical stress requirements
Item
Sub-Item
Value Range
Sinusoidal vibration
Offset
3.5 mm
Accelerated speed
10.0 m/s
Frequency range
2 Hz9 Hz
9 Hz200 Hz
Issue 03 (2014-09-30)

30
Item
Sub-Item
Value Range
Unsteady impact
Impact response
spectrum II
100 m/s
Static payload
Issue 03 (2014-09-30)
Static payload: refers to the capability of the equipment to bear the pressure from the top when it is
packed in the normal pile-up method.

31
6 Acronyms and Abbreviations
Acronyms and Abbreviations
A
APN
access point name
ATAE
Advanced Telecommunications Application Environment
C
CDR
Call Details Record
F
FTP
File Transfer Protocol
G
GGSN
Gateway GPRS Support Node
L
LTE
Long Term Evolution
M
MBB
mobile broadband
MME
mobility management entity
P
PCC
Policy and Charging Control
PCRF
policy and charging rules function
P-GW
Packet Data Network Gateway
Issue 033 (2014-09-30)

32
PS
6 Acronyms and Abbreviations
packet switched
S
SAU
service aware unit
SGSN
Serving GPRS Support Node
S-GW
serving gateway
SP
service provider
U
UDR
User Data Record
UGW
unified gateway
UPCC
Unified Policy and Charging Controller
USN
unified service node
Issue 03 (2014-09-30)

33

PRS Product Description

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

PRS Product Description

Загружено:

Авторское право:

Доступные форматы

iManager PRS

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Issue 033 (2014-09-30)

Huawei Proprietary and Confidential

iManager PRS Product Description

1 Product Positioning and Features

3 Products and Application Scenarios ....................................................................................... 11

5 Technical Specifications ............................................................................................................ 17

6 Acronyms and Abbreviations ................................................................................................... 32

Issue 033 (2014-09-30)

Huawei Proprietary and Confidential

iManager PRS Product Description

1 Product Positioning and Features

Product Positioning and Features

1.1 Product Positioning

1.2 Product Features

Closed-Loop MBB Management

Huawei Proprietary and Confidential

iManager PRS Product Description

1 Product Positioning and Features

Figure 1-1 MBB closed-loop management model

Flexible and Efficient Platform for Analyzing Performance

Huawei Proprietary and Confidential

iManager PRS Product Description

1 Product Positioning and Features

Customizing busy-hour rules

Customizing report formats

Generating and delivering reports on schedule

Performance Analysis Expert

Reduced data delay: less than 30 minutes

KPI insight helps users quickly locate abnormal network KPIs.

Huawei Proprietary and Confidential

iManager PRS Product Description

1 Product Positioning and Features

Real-time KPI Monitoring

Efficient and Intelligent Performance Threshold Alarms

Huawei Proprietary and Confidential

iManager PRS Product Description

1 Product Positioning and Features

Huawei Proprietary and Confidential

iManager PRS Product Description

2.1 Position on the Network

Scenario 1 - Non-U2000 southbound and northbound network isolation

Huawei Proprietary and Confidential

iManager PRS Product Description

Scenario 2 - U2000 southbound and northbound network isolation

PSSAUs deployed in different locations must use channels in different networks to

Huawei Proprietary and Confidential

iManager PRS Product Description

e log lane log

2.2 Hardware Devices

Huawei Proprietary and Confidential

iManager PRS Product Description

2.3 Software Architecture

Table 2-1 describes the components of the PRS system.

The U2000 is a centralized element management system (EMS) of

It collects the performance data from devices on GSM BSS,

It collects the BWM rule data and sampling rate information on

It collects and preprocesses the user plane logs generated by the

Huawei Proprietary and Confidential