4.3 IManager PRS Product Description

iManager PRS
V100R009
Product Description
Issue 02
Date 2013-04-15
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. 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 02 (2013-04-15) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
iManager PRS
Product Description Contents
Contents
1 Product Positioning and Features .............................................................................................. 1

1.1 Product Positioning .......................................................................................................................................... 1
1.2 Product Features ............................................................................................................................................... 1
2 Architecture .................................................................................................................................... 5
2.1 Typical Networking .......................................................................................................................................... 5
2.2 Hardware Architecture ..................................................................................................................................... 7
2.3 Software Architecture ....................................................................................................................................... 9
3 Products and Application Scenarios ....................................................................................... 11

3.1 Statistics Performance Visibility .................................................................................................................... 11
3.2 Service Visibility ............................................................................................................................................ 11
4 Configurations ............................................................................................................................. 14
4.1 Configurations of the PRS Server .................................................................................................................. 14
4.2 Configurations of a PRS Client ...................................................................................................................... 15
5 Operation and Maintenance Features ..................................................................................... 17

5.1 Comprehensive System Security Solution ..................................................................................................... 17
5.2 Citrix-Based PRS Client Integration Solution ................................................................................................ 18
6 Technical Specifications ............................................................................................................ 19

6.1 Management Capacity .................................................................................................................................... 19
6.2 Bandwidth Requirements ............................................................................................................................... 20
6.3 Storage Specifications .................................................................................................................................... 20
6.4 Safety Standards ............................................................................................................................................. 21
6.5 EMC Specifications ....................................................................................................................................... 22
6.6 Environmental Requirements ......................................................................................................................... 22
6.6.1 Storage Environment ............................................................................................................................. 22
6.6.2 Shipping Environment .......................................................................................................................... 24
6.6.3 Operating Environment ......................................................................................................................... 26
7 Acronyms and Abbreviations ................................................................................................... 29
Issue 02 (2013-04-15) Huawei Proprietary and Confidential ii

iManager PRS
Product Description 1 Product Positioning and Features
1 Product Positioning and Features
1.1 Product Positioning

The PRS highlights MBB network visibility (including performance visibility and resource
visibility) and facilitates the OM of MBB networks.
The PRS can centrally manage the following data:
 Performance data collected from devices on GSM BSS, UMTS RAN, LTE RAN, CDMA
BSS, WiMAX RAN, TD-SCDMA RAN, SingleRAN, and core networks
 Data on the control plane collected from USNs
 Data on the user plane collected from UGWs
Based on the preceding data, the PRS provides the following functions:
 MBB network performance visibility, including network performance statistics
management, network KPI insight, and terminal abnormal signaling visibility
 MBB network resource visibility, including network capacity visibility, network-,
service-, subscriber-, and terminal-based traffic, bandwidth, and signaling usage
visibility
1.2 Product Features

Comprehensive and Accurate 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.
Issue 02 (2013-04-15) Huawei Proprietary and Confidential 1

iManager PRS
Internal-Probe-based End-to-End Visibility

The PRS implements CN-PS+RAN end-to-end visibility by using internal probes integrated
into UGWs and USNs to collect user-plane data and control-plane data and then correlating
the data with the SingleRAN and SingleEPC performance data collected from the M2000.
Compared with the original external probes, internal probes have the following advantages:
 Deploying internal probes does not require new devices, which saves hardware, transport,
and space resources.
 Deploying internal probes does not change the network topology, and therefore the
networking is simple.
 Deploying internal probes takes a short period of time, which reduces the lead time.
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.
 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

iManager PRS
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
 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

iManager PRS
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. KPI insight helps users quickly locate abnormal network KPIs.
− 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.
c. 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.
ATAE Platform with Mass Storage Capacity and High Reliability

 Large-scale network management
The PRS can be deployed in the ATAE cluster system, which supports smooth network
expansion. As the network expands, the system may be incapable of managing
large-scale networks. In this case, users can increase the management capability of the
ATAE cluster system by adding only boards or disk arrays. This protects legacy
hardware and saves deployment costs.
 Mass data storage capacity
The PRS uses Huawei's storage area network (SAN) disk arrays as the storage medium
to achieve centralized storage and management of data for the whole network.
 High Reliability and High Security
The ATAE cluster system adopts the N+1 deployment scheme. When one board
malfunctions, a standby board quickly takes over the services of the faulty board. All the
data in an ATAE cluster system is stored in the SAN disk arrays. Therefore, data will not
be lost if a board in the ATAE subrack malfunctions.

iManager PRS
Product Description 2 Architecture
2 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 Typical Networking

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-M2000 southbound and northbound network isolation

As shown in Figure 2-1. When the non-M2000 southbound and northbound network isolation
solution is used,
 Raw statistics performance data on NEs is reported to the PRS server through the
M2000.
 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/PGW are reported to the PRS server through the
service network between the GGSN/PGW 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. 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/PGW are reported to the
PRS server through the OM network between the GGSN/PGW and the M2000.

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

As shown in Figure 2-2. When the M2000 southbound and northbound network isolation
solution is used,
 Raw statistics performance data on NEs is reported to the PRS server through the
M2000.
 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 M2000 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.
 BWM rule data and sampling rate information on the GGSN/PGW are reported to the
PRS server through the OM network between the GGSN/PGW and the M2000.

iManager PRS
Figure 2-2 Networking of the PRS system (M2000 southbound and northbound network
isolation)
Northbound
Network
NMS Nastar
PRS Client PSSAU
M2000 Client (PSSAU and PRS Server are
deployed in the same cabinet)
Other … MCounter
orb a
FTP/C PRS Server
M
M2000 Server Co
un
te
r
ption log
og
log
l
e
an
ne
pl
user subscri
pla
g
Southbound al
in
er
n
Network si g
us
MM MM
L L
n
er tio
e log lane log u s cr i p
g plan p PSSAU
signalin u se r u b s og
l
s
NEs
SGSN/MME GGSN/PGW PCRF
2.2 Hardware Architecture

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. For details about the relationship
between server models and network scales, see Table 6-1 "Management capability of the
statistics performance visibility PRS."
Figure 2-3 shows the hardware architecture when HP DL580 is used.
Figure 2-3 Hardware architecture when HP DL580 is used
Client 1 Client 2 Client N
Disk array PC server
Figure 2-4 shows the hardware architecture when HP DL980 is used.

iManager PRS
Figure 2-4 Hardware architecture when HP DL980 is used
Disk array PC server
Figure 2-5 shows the hardware architecture when the PRS is deployed in the ATAE subrack.
Figure 2-5 Hardware architecture when the PRS is deployed in the ATAE subrack
Disk array ATAE subrack
If a service visibility PRS is deployed, only an ATAE board can serve as the PRS server, and
the number of ATAE boards varies based on network scales. For details about the relationship
between the number of ATAE boards and network scales, see Error! Reference source not
found. "Error! Reference source not found.." Figure 2-5 shows the hardware architecture of
the service visibility PRS.

iManager PRS
2.3 Software Architecture

The PRS software consists of the PRS server software and PRS client software. Figure 2-6
shows the software architecture of the PRS.
Figure 2-6 Software architecture of the PRS
PRS client
JAVA GUI WEB GUI
PRS server
Statistics
Data Service
Performance
Base Visibility
Visibility
M2000 PSSAU
GGSN/ SGSN/
NE NE NE PCRF
PGW MME
Figure 2-6 describes the components of the PRS system.
Component Description
M2000 The M2000 is a centralized element management system (EMS)
of mobile networks. It manages NEs in a centralized manner.
 It collect the performance data from devices on GSM BSS,
UMTS RAN, LTE RAN, CDMA BSS, WiMAX RAN,
TD-SCDMA RAN, SingleRAN, and core networks, and
report to the PRS server through the FTP interface.
 It collect the BWM rule data and sampling rate information
on the GGSN/PGWand report to the PRS server through
the FTP interface.
PSSAU It collects and preprocesses the user plane logs generated by the
GGSN/PGW, the signaling plane logs generated by the
SGSN/MME, and the user subscription logs generated by the
PCRF to meet the PRS analysis requirements.

iManager PRS
Component Description
PRS server According to the different usage scenarios, PRS server can be
divided into the following two categories:
 Statistics Performance Visibility server : The PRS server
analyzes the performance and configuration data collected
from the M2000 and generates analysis results.
 Service Visibility server : The PRS server obtains and
analyzes the service data of MBB networks from the
PSSAU and then generates analysis results.
PRS client 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.

iManager PRS
Product Description 3 Products and Application Scenarios
3 Products and Application Scenarios
The PRS provides the visualization of network performance and service usage, which
facilitate network operation and maintenance.
3.1 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 Service Visibility

The PRS supports service visibility in multiple dimensions:
 Network Traffic Statistics
− In the GPRS, 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.
 Application 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.

iManager PRS
 Terminal Penetration 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 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 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 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
− 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 PGW
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
− 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 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
− 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

iManager PRS
− 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 resouce usage.
 Roaming Traffic Statistics
− 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
− 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
− 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
− 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.

iManager PRS
Product Description Contents
4 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

Table 4-1 lists the configurations of the PRS server when HP DL580 G7 is used.
Table 4-1 Configurations of the PRS server when HP DL580 G7 is used
Item Configuration
CPU 4 x 2.0 GHz E7-4820 (oct-core) or above
Memory 8 x 4 GB
Hard disk 8 x 300 GB
Tape drive 1 x HP LTO4
Accessory DVD ROM
Operating system SUSE Linux10 SP4 (X86_64)
Database software Oracle 11g
Application PRS server software
software
Table 4-2 lists the configurations of the PRS server when HP DL980 G7 is used.
Table 4-2 Configurations of the PRS server when HP DL980 G7 is used
Item Configuration
CPU 8 x 1.86 GHz E7-4807 (hexa-core)

Memory 16 x 4 GB

iManager PRS
Product Description 4 Configurations
Item Configuration
Hard disk 2 x 300 GB
Disk array 1 x S3900 disk array (24 x 600 GB)
Tape drive 1 x HP LTO4
Accessory DVD ROM
Application software PRS server software
If the PRS is deployed in the ATAE subrack, the number of boards to be configured varies
based on the network scale. For details about the relationship between the number of boards
and the network scales, see Table 6-1 "Management capability of the statistics performance
visibility PRS" and Error! Reference source not found. "Error! Reference source not
found.". Each board is configured in the same way. For details, see Table 4-3. The S3900 disk
array is configured based on the deployment of OSS software. For details, see the iManager
M2000 V200R013 Configuration Principle.
Table 4-3 Configuration of an ATAE board for the PRS
Item Configuration
CPU 1 x 2.4 GHz (hexa-core)
Memory 48 GB
Hard disk None
4.2 Configurations of a PRS Client

Table 4-4 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.
Table 4-4 Minimum configuration requirements of a PRS client
Item Configuration
CPU E5300 or above
Memory 4 GB

iManager PRS
Product Description 4 Configurations
Item Configuration
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
Application  Office 2007 or a later version
software  PRS client software

iManager PRS
Product Description 5 Operation and Maintenance Features
5 Operation and Maintenance Features
5.1 Comprehensive System Security Solution

The PRS provides a comprehensive solution to ensure the security of the PRS system.
Security of the Operating System and Database

The PRS enhances the security of operating systems in the following ways:
 Disabling insecure operating system services
 Restricting access to files and directories
 Securing user accounts and passwords
 Adjusting operating system kernel parameters
The PRS provides specialized database security tools for customized hardening of the Oracle
database on the PRS server. This reduces security loopholes and improves server security.
User Security
The PRS helps telecom operators implement security control and management by centrally
managing and authenticating PRS users and user rights.
Centralized management and authentication are implemented by the single sign-on (SSO)
function. On an OSS where the PRS and the M2000 are deployed, the M2000 server is
configured as the SSO server and the SSO client software is installed on each OSS client. By
doing this, users can visit all authorized OSSs at the same time and switch between them after
entering the correct user name and password for authentication and logging in to the SSO
server.
Data Security
Data backup and restore prevents data loss caused by system errors, and therefore is an
important means of ensuring secure system operation. When system errors occur, users can
restore the system to the latest backup status using the backup data.
Users can set backup policies as required and back up applications and real-time data
periodically through system backup tasks. If applications and real-time data are damaged or
missing, users can restore the data by using the corresponding backup package. Users can also
restore the data of the entire operating system by using the professional backup and restore
tool provided by the PRS.

iManager PRS
Product Description 5 Operation and Maintenance Features
On a network where the PRS and the M2000 are deployed, if the Veritas NetBackup (NBU)
suite is installed on the M2000, the PRS serves as a Veritas NBU client. This Veritas-based
solution allows users to back up and restore important data of the PRS system.
Network Security
The PRS provides the OSS antivirus solution to protect OSSs from the attacks of viruses,
worms, and spyware and ensure the security of network OM data. In this solution, OfficeScan
is deployed to provide antivirus protection for the PRS clients and Citrix clients and servers
running Windows. ServerProtect for Linux 3.0 and Control Manager are deployed to provide
antivirus protection for the PRS servers running SUSE Linux operating systems.
Security of Sensitive Information

The PRS adopts the anonymous policy to protect sensitive information about subscribers,
such as IMSI, IMEI, MSISDN, and MAC address. This ensures that the sensitive information
is transmitted between NEs and the PRS or displayed as the input or output in an anonymous
way.
5.2 Citrix-Based PRS Client Integration Solution

The PRS supports the Citrix-based PRS client integration solution, which brings about the
following advantages:
 The number of connected clients is not subject to the hardware capability of the PRS
server.
 Client installation, upgrade, and maintenance are performed on the Citrix server. This
improves the efficiency of deploying and maintaining PRS applications.
 The Citrix has a low bandwidth requirement for each client, reducing the total bandwidth
requirement.
 A PRS client is installed on the Citrix server that is deployed together with the PRS
server. Both the Citrix server and the PRS server are protected by a firewall. This
minimizes the exposure to unauthorized access, virus infection, and malicious attacks.
 The Citrix can convert GUIs of a PRS client to web pages and then send the web pages
to the Citrix client. Therefore, users need to install only the Citrix client to remotely log
in to the PRS and perform routine O&M on the PRS by using the Internet Explorer (IE)
or Netscape browser.

iManager PRS
Product Description 6 Technical Specifications
6 Technical Specifications
6.1 Management Capacity

Table 6-1 and Error! Reference source not found. list the management capability of the
PRS when different server models are used.
 Physical NEs are converted into equivalent NEs based on specified conversion factors. For details
about the conversion relationship between physical NEs and equivalent NEs, see section "Methods
of Converting Physical NEs into Equivalent NEs" in the iManager PRS V100R009 Configuration
Principles. If any algorithm for calculating equivalent NEs is not included in the document,
contact Huawei technical support.
 If a PRS is used for both statistics performance visibility and service visibility, the standby PRS
service board and standby database board can be shared.
 If a PRS is used for service visibility, the management capability of a PRS server is determined by
the number of simultaneous attached users (SAUs). Therefore, the PRS server is configured based
on the scales of SAUs, including 1 million SAUs, 2.5 million SAUs, and 5 million SAUs. The
management capability of a PSSAU is determined by traffic. Therefore, the PSSAU is configured
based on the amount of traffic, including 10 Gbit/s, 25 Gbit/s, and 50 Gbit/s.
Table 6-1 Management capability of the statistics performance visibility PRS
Server Management Capability (Number of

Equivalent NEs)
HP DL 580 ≤ 280
HP DL 980 ≤ 800
ATAE ≤ 400: 2 PRS service boards (1 active board
and 1 standby board) + 2 PRS database board
When the PRS is deployed in the ATAE
(1 active board and 1 standby board)
subrack, the management capability of the
PRS is in direct proportion to the number of
≤ 800: 2 PRS service boards (1 active board
boards. and 1 standby board) + 2 PRS database board
(1 active board and 1 standby board)
≤ 1200: 3 PRS service boards (1 master board,
1 slave board, and 1 standby board) + 3 PRS
database boards (1 master board, 1 slave board,
and 1 standby board)

iManager PRS
6.2 Bandwidth Requirements

Table 6-2 lists the bandwidth requirements for the PRS.
Table 6-2 Bandwidth requirements for the PRS
Physical Entity Bandwidth Requirement
PRS server and M2000 server 100 Mbit/s or higher

PRS server and PRS client 10 Mbit/s or higher
PRS server and PSSAU server Equal to or greater than 0.1% of the traffic over
the Gn interface.
GGSN/PGW and PSSAU server Equal to or greater than 2% of the traffic over
the Gn interface.
SGSN/MME and PSSAU server Equal to or greater than 2% of the traffic over
the Gn interface.
PCRF and PSSAU server Equal to or greater than N Mbit/s.
N = Number of subscribers (in ten thousand) x
6%.
For example, if the number of subscribers is
200,000, N = 20 x 6% = 1.2.
6.3 Storage Specifications

Table 6-3 and Table 6-4 list the storage specifications of the statistics performance visibility
PRS and service visibility PRS.
Table 6-3 Storage specifications of the statistics performance visibility PRS
Data Dimension Default Storage Duration

Raw 3 days
Hour 31 days
Day 180 days
Week 106 weeks
Month 36 months
Daily busy hour 93 days
Weekly busy hour 106 weeks
Monthly busy hour 36 months
Special date 13 months

iManager PRS

3DBH 106 weeks
Table 6-4 Storage specifications of the service visibility PRS

Reports of 5-minute level 7 days
Only the following reports support the 5-minute

level data storage:
 Network traffic analysis
 APN traffic analysis
 RAN traffic analysis
 Traffic analysis for bandwidth control
policies
 PCC rule analysis
 Traffic blocking analysis
 TopN application analysis
 Application analysis for specified
subscribers/subscriber groups
Reports of 1-hour level 14 days
Reports of 1-day level 92 days
Reports of 1-week level 52 weeks
Reports of 1-month level 36 months
6.4 Safety Standards

The PRS complies with the following safety standards:
 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

iManager PRS
6.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
6.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
6.6.1 Storage Environment

Climatic Requirements
Table 6-5 Climatic requirements for storage
Item Value Range

Temperature -20°C (-4ºF)–60°C (140ºF)
Relative humidity 8%–93%
Altitude ≤ 5000 m
Atmospheric pressure 70 kPa–106 kPa
Solar radiation ≤ 1120 W/m²
Heat radiation ≤ 600 W/m²
Wind speed ≤ 30 m/s

iManager PRS
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 6-6.
Table 6-6 Requirements for the density of physically active materials
Physically Active Material Unit Density

Suspended dust mg/m³ ≤ 5.00
Deposited dust mg/m² h ≤ 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 6-7.
Table 6-7 Requirements for the density of chemically active materials
Chemically Active Unit Density

Material
SO2 mg/m³ ≤ 0.30

H2S mg/m³ ≤ 0.10
NO2 mg/m³ ≤ 0.50

iManager PRS
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 6-8 Mechanical stress requirements
Item Sub-Item Value Range

Sinusoidal vibration Offset ≤ 7.0 mm -
Accelerated speed - ≤ 20.0 m/s²
Frequency range 2 Hz–9 Hz 9 Hz–200 Hz
Unsteady impact Impact response spectrum ≤ 250 m/s²
II
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.
6.6.2 Shipping Environment

Table 6-9 Climatic requirements for shipping
Item Value Range
Temperature -20°C (-4ºF)–60°C (140ºF)

Relative humidity 8%–93%
Altitude ≤ 5000 m

iManager PRS
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.

Table 6-10.
Physically Active Material Unit Density

Suspended dust mg/m³ -
Deposited dust mg/m² h ≤ 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 6-11.

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

iManager PRS
Chemically Active Material Unit Density

HCl mg/m³ ≤ 0.10
HF mg/m³ ≤ 0.01
O3 mg/m³ ≤ 0.05
Table 6-12 Mechanical stress requirements for shipping environment

Sinusoidal Offset ≤ 7.5 mm - -
vibration
Accelerated speed - ≤ 20.0 m/s² ≤ 40.0 m/s²
Frequency range 2 Hz–9 Hz 9 Hz–200 Hz 200 Hz–500
Hz
Random Spectrum density of 10 m²/s³ 3 m²/s³ 1 m²/s³
vibration accelerated speed
Frequency range 2 Hz–9 Hz 9 Hz–200 Hz 200 Hz–500
Hz
Unsteady Impact response ≤ 300 m/s²
impact spectrum II
Static payload ≤ 10 kPa
 Static payload: refers to the capability of the equipment in package to bear the pressure from the top
in normal pile-up method.
6.6.3 Operating Environment

Table 6-13 Temperature and humidity requirements for operation
Temperature Relative Humidity
5°C (41ºF)–35°C (95ºF) 20%–80%

iManager PRS
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 6-14 Other climatic requirements for operation

Item Value Range
Altitude ≤ 4000 m

Table 6-15.
Physically Active Unit Density

Material
Dust particle particle/m³ ≤ 3 x 104

(No visible dust exists on the desktop
within three days.)
Dust particle: diameter ≥ 5 μm
Table 6-16.

iManager PRS
Chemically Active Unit Density

Material
SO2 mg/m³ ≤ 0.20

H2S mg/m³ ≤ 0.006
NH3 mg/m³ ≤ 0.05
Cl2 mg/m³ ≤ 0.01
Table 6-17 Mechanical stress requirements

Sinusoidal vibration Offset ≤ 3.5 mm -
Accelerated speed - ≤ 10.0 m/s²
Frequency range 2 Hz–9 Hz 9 Hz–200 Hz
Unsteady impact Impact response ≤ 100 m/s²
spectrum II
Static payload 0
 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.

iManager PRS
Product Description 7 Acronyms and Abbreviations
7 Acronyms and Abbreviations
A
APN Access Point Name
ATAE Advanced Telecommunications Application Environment
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
PGW PDN GateWay
PS Packet Switched
PSSAU -

iManager PRS
Product Description 7 Acronyms and Abbreviations
S
SAU Service Aware Unit
SGSN Serving GPRS Support Node
SGW Serving GateWay
SP Service Provider
U
UGW Unified Gateway
UPCC Unified Policy and Charging Controller
USN Unified Service Node


4.3 IManager PRS Product Description

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

4.3 IManager PRS Product Description

Uploaded by

Copyright:

Available Formats

iManager PRS

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2013-04-15) Huawei Proprietary and Confidential i

1 Product Positioning and Features .............................................................................................. 1

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

5 Operation and Maintenance Features ..................................................................................... 17

6 Technical Specifications ............................................................................................................ 19

7 Acronyms and Abbreviations ................................................................................................... 29

Issue 02 (2013-04-15) Huawei Proprietary and Confidential ii

1 Product Positioning and Features

1.1 Product Positioning

1.2 Product Features

Issue 02 (2013-04-15) Huawei Proprietary and Confidential 1

Internal-Probe-based End-to-End Visibility

Closed-Loop MBB Management

Figure 1-1 MBB closed-loop management model

Issue 02 (2013-04-15) Huawei Proprietary and Confidential 2

Flexible and Efficient Platform for Analyzing Performance

Figure 1-2 Procedure for customizing reports

Performance Analysis Expert

Issue 02 (2013-04-15) Huawei Proprietary and Confidential 3

Short data delay improves the performance analysis efficiency.

ATAE Platform with Mass Storage Capacity and High Reliability

Issue 02 (2013-04-15) Huawei Proprietary and Confidential 4

2.1 Typical Networking

Scenario 1 - Non-M2000 southbound and northbound network isolation

Issue 02 (2013-04-15) Huawei Proprietary and Confidential 5

SGSN/MME GGSN/PGW PCRF

Scenario 2 - M2000 southbound and northbound network isolation

Issue 02 (2013-04-15) Huawei Proprietary and Confidential 6

SGSN/MME GGSN/PGW PCRF

2.2 Hardware Architecture

Figure 2-3 Hardware architecture when HP DL580 is used

Client 1 Client 2 Client N

Disk array PC server

Figure 2-4 shows the hardware architecture when HP DL980 is used.

Issue 02 (2013-04-15) Huawei Proprietary and Confidential 7

Figure 2-4 Hardware architecture when HP DL980 is used

Client 1 Client 2 Client N

Disk array PC server

Client 1 Client 2 Client N

Disk array ATAE subrack

Issue 02 (2013-04-15) Huawei Proprietary and Confidential 8

2.3 Software Architecture

Figure 2-6 Software architecture of the PRS

Figure 2-6 describes the components of the PRS system.

Issue 02 (2013-04-15) Huawei Proprietary and Confidential 9

Issue 02 (2013-04-15) Huawei Proprietary and Confidential 10

3 Products and Application Scenarios

3.1 Statistics Performance Visibility

3.2 Service Visibility

Issue 02 (2013-04-15) Huawei Proprietary and Confidential 11

 Terminal Penetration Statistics

Issue 02 (2013-04-15) Huawei Proprietary and Confidential 12

Issue 02 (2013-04-15) Huawei Proprietary and Confidential 13

4.1 Configurations of the PRS Server

Table 4-1 Configurations of the PRS server when HP DL580 G7 is used

Table 4-2 Configurations of the PRS server when HP DL980 G7 is used

CPU 8 x 1.86 GHz E7-4807 (hexa-core)

Issue 02 (2013-04-15) Huawei Proprietary and Confidential 14

Table 4-3 Configuration of an ATAE board for the PRS

4.2 Configurations of a PRS Client