PRS Product Description

iManager PRS
V100R017
Product Description
Issue 05
Date 2017-09-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. 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
Website: http://www.huawei.com
Email: support@huawei.com
Issue 05 (2017-09-30) 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 ............................................................................................................................ 6
2.1 Position on the Network ....................................................................................................................................................... 6
2.2 Hardware Devices .................................................................................................................................................................8
2.3 Hardware Description ........................................................................................................................................................... 9
2.4 Software Architecture ........................................................................................................................................................... 9
2.5 Virtualization Platform ....................................................................................................................................................... 10
3 Products and Application Scenarios .................................................................................. 12

3.1 RAN Statistics Performance Visibility .............................................................................................................................. 12
3.2 PS Service Visibility ........................................................................................................................................................... 13
3.3 MBB Service Visibility-RAN ............................................................................................................................................ 16
4 Configurations ..................................................................................................................... 20
4.1 Configurations of the PRS Server...................................................................................................................................... 20
4.2 Configurations of a PRS Web Client ................................................................................................................................. 21
5 Technical Specifications ..................................................................................................... 22

5.1 Management Capacity ........................................................................................................................................................ 22
5.1.1 Server Management Capacity (RAN Statistics Performance Visibility)...................................................................... 22
5.1.2 Server Management Capacity (RAN Service Visibility) .............................................................................................. 23
5.1.3 Server Management Capacity (PS Service Visibility)................................................................................................... 24
5.2 Physical Bandwidth Requirements .................................................................................................................................... 25
5.3 Data Storage Specifications ............................................................................................................................................... 28
5.4 Safety Standards.................................................................................................................................................................. 30
5.5 EMC Specifications ............................................................................................................................................................ 30
5.6 Environmental Requirements............................................................................................................................................. 30
5.6.1 Storage Environment ....................................................................................................................................................... 31
5.6.2 Shipping Environment..................................................................................................................................................... 33
5.6.3 Operating Environment ................................................................................................................................................... 35
6 A Acronyms and Abbreviations ......................................................................................... 38
Issue 05 (2017-09-30) Huawei Proprietary and Confidential ii

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

1.2 Product Features
1.1 Product Positioning

PRS is a part of the SingleOSS@MBB solution. It gives operators insights into MBB network
quality and help operators make precision investment.
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 Insight–centered 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.
Issue 05 (2017-09-30) Huawei Proprietary and Confidential 1

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

iManager 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
Short data delay improves the performance analysis efficiency.
For original performance data of Huawei devices whose measurement period is 15 minutes or
above, the interval between data generation on Huawei devices and data display on the PRS is
less than 30 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.

iManager PRS
Performance analysis themes integrated with Huawei performance analysis experience

helps users quickly locate problems.
1. 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.
2. KPI insight helps users quickly locate abnormal network KPIs.
− Integrated with Huawei's extensive 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.
3. 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

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

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 Position on the Network
2.2 Hardware Devices
2.3 Hardware Description
2.4 Software Architecture
2.5 Virtual Platform
2.1 Position on the Network

Scenario 1 - Non-U2000 southbound and northbound network isolation
As shown in Figure 2-1
 Raw statistics performance data on NEs is reported to the PRS server through the U2000.
 The TSP can be deployed with PRS on the OSS side or independently deployed on the
NE side. TSPs deployed in different locations must use channels in the same network to
report data.
1. 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 TSP.
2. Signaling plane logs on the SGSN/MME are reported to the PRS server through the OM
network between the SGSN/MME and the TSP.
3. 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 TSP.
 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.

iManager PRS
Figure 2-1 Networking of the PRS system (non-U2000 southbound and northbound network
isolation)
NMS Nastar
PRS Client
U2000 Client
Other …
FTP/Corba
U2000 Server
PRS Server TSP
NEs
SGSN/MME GGSN/P-GW PCRF
OM network
GGSN/P-GW 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.
 TSPs deployed in different locations must use channels in different networks to report
data.
1. If the TSP and PRS server are deployed in the same cabinet, the TSP 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.
2. If the TSP 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/P-GW are reported to the
PRS server through the OM network between the GGSN/P-GW and the U2000.

iManager PRS
Figure 2-2 Networking of the PRS system (U2000 southbound and northbound network isolation)
Northbound
Network
NMS Nastar
PRS Client TSP
U2000 Client (TSP and PRS Server are
deployed in the same cabinet)
Other …
PRS Server
U2000 Server
Southbound
Network
TSP
NEs
SGSN/MME GGSN/P-GW PCRF
Northbound network
OM network
GGSN/P-GW service network
PCRF service network
2.2 Hardware Devices

A common PRS system consists of a PRS server and networking devices. The server can be
deployed on the ATAE cluster system or virtual system. Figure 2-3 shows the basic hardware
structure of the PRS system.
Figure 2-3 PRS hardware devices

iManager PRS
2.3 Hardware Description

For details about the hardware description of the ATAE cluster system, see the following
section in ATAE Cluster System Product Documentation: Description > Hardware
Description.
You can contact Huawei technical support to obtain ATAE Cluster System Product Documentation from
the following navigation path at http://support.huawei.com: On the Product Support tab page, enter
OSMU in the Search box and select the displayed navigation path.
For details about the hardware description of the virtual cluster system, see the following
section in SingleOSS-MBB Virtual System Hardware Description.
You can contact Huawei technical support to obtain SingleOSS-MBB Virtual System Hardware
Description from http://support.huawei.com by choosing Product Support > Wireless Network >
SingleOSS-MBB > SingleOSS-MBB > M2000-Common > iManager U2000-M.
2.4 Software Architecture

The PRS software consists of the PRS server software and web client. 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.

iManager PRS
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.
 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.
TSP The TSP (Trace Server Professional) is an enhanced component of the

U2000 Trace Server. It processes NE data (such as the CHRs, MRs,
user plane logs on UGWs, and signaling plane logs on USNs) and basic
information (such as NE configurations) in the MBB network channels.
The TSP provides basic capabilities, such as NE data collection,
aggregation, unified modeling, storage, and location, and the service
scalability capability. Based on the service scalability capability, the
TSP supports the customization of each upper-layer service. Data
sources processed by the TSP can be shared by upper-layer service
systems, such as the PRS, and support multiple service scenarios, such
as the MBB network deployment and inventory operation.
Trace Server The Trace Server, an optional component in the U2000 system, collects
and filters CHR, MR, and trace data of eNodeBs, CHR and trace data
of NodeBs, CHR and MR data of RNCs, signaling logs of VIP
subscribers, CS CHR data, PS CHR data, and PS MR data of BSCs,
CHR data of USNs, provides the data for upper-layer applications such
as the EBC, FARS, Nastar, SONMaster, and PRS.
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 TSP, parses the data, and 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 the Web-based PRS client and perform the corresponding
operations after successfully login.
2.5 Virtualization Platform

 Reduced TCO
The virtual platform decouples software and hardware of traditional telecom NEs by replacing
the dedicated hardware with the standard x86 servers and general storage and network devices,

iManager PRS
and migrating servers and storage and network devices to the cloud platform using the cloud
computing technology. As cloud nodes are extremely low-cost, device costs and power
consumption decrease significantly. Automatic and centralized management of the cloud
improves management and operation efficiency, and reduces OPEX. Compared with the
traditional system, the universality of the cloud increases resource usage more significantly.
 Shortened deployment time
On telecom networks with the virtualized architecture, site deployment and capacity
expansion become extremely simple and do not require complex site surveys and hardware
installation. As for service deployment, you only need to install and commission
corresponding software after applying for sufficient cloudization resources (computing,
storage, and network resources) as required. Compared with the traditional telecom NE
deployment, the whole process saves about 80% time.

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 RAN Statistics Performance Visibility
3.2 PS Service Visibility
3.3 MBB Service Visibility-RAN
3.1 RAN Statistics Performance Visibility

Table 3-1 describes the application scenarios of this feature during network operation and
maintenance.
Table 3-1 Application scenarios of the RAN Statistics Performance Visibility feature
Network Application Scenario

Operation and
Maintenance
Adjustment Provides a KPI Benchmarking function to help users compare the

performance changes before and after an adjustment, such as base
station reparenting and NE upgrade.
Optimization Provides a KPI visibility function to help users detect abnormal KPIs
in real time and quickly locate the causes of the abnormal KPIs.
Maintenance  Provides an end-to-end report customization function to help users

customize performance monitoring reports, thereby achieving
performance monitoring automation.
 Provides a capacity visibility function to help users detect network
capacity bottlenecks in real time, thereby providing a basis for
network adjustment.
 Provides a performance threshold alarm function to enable the
PRS to automatically check for risks and faults related to current
performance counters and notify users of detected risks and faults
through alarms.
 Provides a RAN sharing management function to help users focus

iManager PRS
Network Application Scenario

Operation and
Maintenance
on the performance data of a specified network, thereby
improving network O&M efficiency and experience.
3.2 PS Service Visibility

The PRS supports service visibility in multiple dimensions:
 Network Traffic 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.
 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.
 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 behavior 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 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 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.

iManager PRS
 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 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 behavior 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
Different OTT services generate different network signaling loads. This feature helps
telecom operators learn 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 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.
 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.
 Smartphone Abnormal Event Statistics
Signaling behavior of smartphones varies 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

iManager PRS
Based on the statistics on the traffic consumed by web browsers, telecom operators can
identify the leading web browsers used by subscribers, and can further cooperate with
the vendors of the leading web browsers to benefit from service providers (SPs) by
providing differentiated services or jointly deploying a network.
 VoIP Call 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 evaluate the
impact of the VoIP service on the traditional voice service and provide reference
information for telecom operators to make decisions on services.
 Cell Bandwidth Insight
The PRS uses Gn convergence nodes to collect statistics on network-wide data rates
instead of subscriber experience, and provides subscriber's experience data rate in each
cell under each RAT. In addition, the PRS calculates the target data rate based on the
service model used on a live network, helping users determine the distribution of
high-value regions where subscriber experience is poor and helping telecom operators'
network construction department to make periodic dynamic planning. This enables
telecom operators to make the best use of their budget and improve network
competitiveness, thereby improving subscriber loyalty.
 Integrated Service Statistics
This feature is an enhanced feature that is developed based on traditional protocols and
application reports. Based on the differentiated service rules and charging control rules
for telecom operators' proprietary services and third-party services, the PRS analyzes the
traffic, number of subscribers, quality, and standard bandwidth of the proprietary
services. This helps users manage such services conveniently and quickly.
 Email SPAM User Statistics
The PRS collects statistics on and displays the TopN connections used by all subscribers
to send emails and the TopN blocked connections for sending emails in lists. This helps
telecom operators analyze the subscribers who send a large number of emails within a
short period of time and cause network congestion, thereby evaluating the gateway's
function of blocking emails when a large number of emails sent within a short period of
time cause network congestion.
 Rating Group Traffic Statistics
This feature enables the PRS to collect statistics on traffic trends by rating group (RG),
thereby helping telecom operators determine whether the RG classification rules are
proper and adjust improper RG classification rules to increase revenue. This feature also
enables the PRS to check whether all traffic is charged based on CDRs, thereby helping
telecom operators reduce income losses caused by the traffic that is not charged.
 Provisioning Event
This feature enables the PRS to access the Provision EDR data sources of the UPCC to
obtain subscription event records. The PRS allows users to query the subscription event
records and trend report of a specified subscriber within 90 days before the current date.
 Policy Control
This feature enables the PRS to access the rule-based EDR data sources of the UPCC to
obtain the records for the events triggered by subscriber policies. The PRS allows users
to query the records for the events triggered by subscriber policies for a specified
subscriber within 90 days before the current date, helping telecom operators handle
subscriber complaints.
 Per Subscriber Quota Usage
This feature enables the PRS to access UPCC USDR data sources for querying the
historical daily quota consumption of a specified subscriber. Telecom operators can

iManager PRS
specify any subscriber and query the quota consumption and remaining quota of the
subscriber within a specified time period per day. This provides a basis for analyzing
quota usage.
 User Group Identification
This feature enables the PRS to collect statistics on and analyze the UFDR data reported
by the Huawei GGSNs and identify five types of user groups on the UMTS/GSM
networks: UMTS only users, UMTS users falling back to GSM, GSM users using UMTS
terminals, GSM users with high PS activities, and GSM users with low PS activities.
With this feature, the PRS displays the quantity, traffic, data transmission duration, and
proportion of various user groups in pie charts and tables, and supports TopN cell
ranking. Geographical distribution of each type of user group on the networks is also
displayed on the GIS map, helping users identify UMTS network problems and explore
the value space of GSM-to-UMTS user migration.
 VoLTE Quality Visibility-PS CN
In a single-EPC scenario, this feature enables the PRS, based on USN CHRs and UGW
UFDRs, to evaluate and demarcate VoLTE service quality in the entire network, NE, cell
group, and specified cell dimensions and to display KPIs related to accessibility,
retainability, and integrity in the GIS. In an eRAN+EPC scenario, this feature enables the
PRS, based on USN CHRs, UGW UFDRs, and eRAN CHRs, to perform joint evaluation
and demarcation in the specified cell dimension.
 PS CN Custom Traffic Report
This feature allows users to customize reports, and set filter criteria for data sources and
the report generation format to meet report customization requirements.
 HTTP 2.0 Traffic Report
This feature describes how to view PRS HTTP2.0 traffic distribution on the traffic
distribution and trend by encryption type or protocol version. The query results help
operators assess networks.
 QUIC Report
The PRS system allows operators to view the proportion and trend of QUIC or
non-QUIC traffic and learn QUIC traffic growth, providing reference for deploying
charging and control features later.
 U-vMOS Report
The U-vMOS feature can gather statistics on distribution of unencrypted video quality,
video playing duration, and resolution on the live network. It allows you to analyze the
distribution from the perspectives of the entire network, radio access technologies
(RATs), and host.
3.3 MBB Service Visibility-RAN

 UMTS xMbps Visibility – Cell Level
If a cell does not reach the xMbps fill rate, this feature analyzes the cause of the problem
based on geographic information, and displays the xMbps fill rate of the cell in the GIS.
This helps telecom operators achieve xMbps visibility and improve subscriber
experience.
 LTE xMbps Visibility – Cell Level
This feature enables the PRS to display whether each cell on the live network reaches the
xMbps fill rate in the GIS based on Huawei RAN devices, thereby identifying hotspot
areas. The UE throughput capability of each cell is calculated through a specified

iManager PRS
algorithm based on traffic statistics. It helps telecom operators learn UE throughput

capability information about the live network, and provides a basis for capacity
expansion to ensure satisfactory subscriber experience.
 UMTS /LTE xMbps Visibility – Grid Level
This feature enables the PRS to analyze and collect statistics on the following rate
indicators in target areas within a certain period:
− Rate capability
Indicates the rate available to subscribers based on the resource configuration,
subscriber distribution, and radio environment.
− Actual rate
Indicates the actual service rate for subscribers on the live network.
With this feature, the PRS is able to render grids in different colors indicated by the
specified indicator value ranges on a GIS map so that you can easily learn the
service rates on the live network.
 User Fallback (GSM-UMTS) – Cell Level
This feature analyzes UMTS UEs' data services that fall back to GSM networks,
identifies the locations, time, and causes of the fallback, and displays the analysis results
in charts. This helps telecom operators formulate proper solutions to prevent UMTS UEs'
data services from falling back to GSM networks, thereby achieving migration of UEs
from GSM networks to UMTS networks.
 LTE User Fallback – Cell Level – FDD/TDD
This feature analyzes LTE UEs' data services that fall back to GSM or UMTS networks,
identifies the locations, UE quantity, and causes of the fallback, and evaluates the
cooperation quality of GSM, UMTS, and LTE networks and the UE traffic loss. This
helps telecom operators formulate proper solutions, make accurate investments, and
improve profits from data services.
 UMTS User Migration – Fallback Analysis – Grid level
The feature enables the PRS to intuitively display top areas with severe fallback
problems based on grid-level geographic observation of inter-RAT handover events.
With this feature, telecom operators can identify UMTS network problems, accelerate
user migration from GSM to UMTS, improve user experience of data services, and
increase network data traffic, average revenue per user (ARPU), and telecom operators'
revenue.
 Traffic Map
Based on the geographic location results of MR and CHR data, the traffic map feature
collects statistics on traffic indicator values by grid and allows operators to efficiently
learn distribution differences between hotspot areas on the live network, providing a
basis for future load distribution, capacity expansion, site planning, and HETNET
deployment.
 Coverage Visibility
Before this feature is used, identifying network coverage problems mainly depends on
drive tests (DTs). The problem locating and analysis period is long with low efficiency,
the network coverage analysis is not systematic, and network planning and optimization
demands huge investment with frequent optimization. This feature provides guidance for
users to quickly identify and evaluate coverage problems on the network based on the
geographic locating results of MR and CHR data and helps improve problem resolving
efficiency and reduce customers' network planning and optimization costs. It also
provides guidance for customers to purposefully plan and invest networks.
 VoLTE Quality Visibility - TDD/FDD

iManager PRS
VoLTE quality evaluation and geographic visibility at the area, cell, and grid levels and
joint analysis in the indoor and outdoor coverage, packet loss, and handover dimensions
help users identify causes for voice quality problems on the eRAN side.
 WTTx Suite
The WTTx Suite feature offers a complete solution for WTTx service O&M and
provides the following functions: WTTx map, WTTx post-evaluation, CPE log query,
abnormal CPE analysis and northbound allocation data interconnection. This feature
involves the WTTx theme of the PRS and the LTM (Light Terminal Manager). The LTM
collects logs from CPEs. The PRS obtains CPE logs from the LTM for post-evaluation,
CPE log query, and abnormal CPE analysis.
 WTTx map
− With this function, the PRS displays the allocation capability on grid-level maps.
After you click any grid on a map, the PRS displays number allocation analysis
results. Address searching is supported.
− This function supports two number allocation methods: number allocation by
coverage and number allocation by package rate. For number allocation by
coverage, the PRS checks whether CPE number allocation is allowed based on the
RSRP of a grid and further checks whether indoor or outdoor CPE number
allocation is allowed if CPE number allocation is allowed. For number allocation by
package rate, the PRS checks whether CPE number allocation is allowed for each
package rate based on the RSRP and capability throughput of a grid, further
determines CPE models for number allocation if CPE number allocation is allowed,
and provides the number of remaining CPEs for each CPE package in each cell.
Simulated data and MRs are data sources for number allocation analysis. For
number allocation by coverage, if MRs are unavailable, the PRS uses simulated
data for number allocation analysis; if MRs are available, the PRS corrects
simulated data based on MRs and uses the obtained data for number allocation
analysis. For number allocation by package rate, the PRS uses the MR of each grid
for number allocation analysis and uses simulated data for number allocation
analysis for grids without MRs.
− The PRS can display areas with number allocation forbidden and cells with number
allocation frozen due to heavy load.
− Some telecom operators have their own number allocation systems and want to
integrate number allocation analysis data of WTTx Suite into their own systems.
The northbound allocation data interconnection function allows the PRS to export
number allocation analysis results to files and actively transmit files to the number
allocation systems of telecom operators using SFTP. Based on number allocation
analysis results, telecom operators can further improve their number allocation
systems.
 WTTx post-evaluation
− With this function, the PRS analyzes the impact of WTTx services on the entire
network and user experience of CPEs after number allocation.
− With this function, the PRS analyzes the percentage of CPEs whose throughput is
less than the target throughput, number of CPEs whose RSPR is less than the
threshold, number of allocated CPEs, number of cells with number allocation frozen
due to heavy load, ratio of the average cell-level throughput for WTTx services to
the target throughput. The LTM is required for analyzing the percentage of CPEs
whose throughput is less than the target throughput, number of CPEs whose RSPR
is less than the threshold, and number of allocated CPEs.
− The PRS collects statistics on causes for poor CPE experience. The possible causes
include heavy cell load, weak signal coverage, poor SINR, and CPE fault.

iManager PRS
− The PRS analyzes the WBB and MBB traffic trends for each cell and provides
correlation analysis for RRC-CONNECTED UEs. The correlation analysis covers
the number of CPEs, throughput, traffic volume, and downlink PRB utilization.
− The PRS provides abnormal CPE analysis for identifying suspected offline CPEs
and CPE location changes.
− The PRS allows you to view the status change trend (including the throughput,
RSRP, SINR, and detailed log information) of any CPE and its resource change
trend (including the downlink PRB utilization and number of RRC_CONNECTED
UEs).
− The PRS also provides automatic post-evaluation to analyze load of each cell every
day. The PRS identifies cells with heavy resource load (including the PRB
utilization, CPU load, S1 bandwidth utilization, and number of
RRC_CONNECTED UEs) and freezes number allocation for such cells.
 CA Feature Gain Visibility – FDD/TDD
This feature allows telecom operators to evaluate gains after LTE CA enabling and CA
support conditions of UEs and check main CA failure scenarios. With this feature,
operators can evaluate gains after the LTE CA feature is enabled, simplify CA O&M, and
improve efficiency.
 LTE UE Capability Visibility – FDD/TDD
This feature provides the distribution reports of LTE UEs by category, protocol version,
RAT, frequency band, and feature, helps telecom operators learn UE capabilities in terms
of the category, protocol version, RAT, frequency band, and feature. Based on UE
capabilities, telecom operators can determine whether to deploy a certain feature, such as
CA and VoLTE sub-feature (including ROHC, TTI Bundling, and Semi Persistent).
 MBB-online@PRS
With this feature, users can learn network conditions on the whole network and in key
areas using a pad anytime and anywhere.

iManager PRS
Product Description 4 Configurations
4 Configurations
The PRS works in browser/server (B/S) modes and allows the connection of multiple clients.
4.1 Configurations of the PRS Server
4.2 Configurations of a PRS Web Client
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.
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)
 SUSE Linux11 SP3 (X86_64)
Database software Oracle 11g
Table 4-2 lists the configurations of the PRS VM in the virtual solution.
Table 4-2 Configuration of a PRS VMs

VM Name vCPUs Total vCPU Memory (GB)
Frequency (MHz)
vOSMU VM 4 4400 16
PRS Service VM 8 8800 48

iManager PRS
Product Description 4 Configurations
VM Name vCPUs Total vCPU Memory (GB)

Frequency (MHz)
PRS Master DB VM 8 8800 48

PRS Slave DB VM 8 8800 48
PRS support by-integration solution and pre-integration solution for virtual system.. In by-integration
solution, customers purchase and deploy a data center, including the server, storage system, and network.
OSS systems are integrated into the data center. The PRS system support deployed on VMs created on
the VMware 5.1 /VMware 5.5/Fusionshpere 6.0 virtual platform. In pre-integration solution, OSS
provides the end to end solution based on the FusionShpere virtual platform.
4.2 Configurations of a PRS Web Client

Table 4-3 lists the minimum configuration requirements of PC for PRS client.
Table 4-3 Minimum configuration requirements of PC for PRS client

Item Configuration
CPU E5300 or above
Memory 4 GB
Operating system  Windows 10 (64-bit)

 Windows 7 (32-bit) and (64-bit)
 Windows 2003 R2 Server Service Pack
2 (32-bit) and (64-bit) + KB968730
Patch + KB938397 Patch
 Windows 2008 Server (64-bit)
 Windows 2008 R2 Server (64-bit)
 Windows 2012 Server (64-bit)
Application software Office 2007 or a later version
Browser Firefox 38 is recommended and Firefox 31,

Internet Explorer 10, 11
Resolution 1280 x 1024 is recommended.

iManager PRS
Product Description 5 Technical Specifications
5 Technical Specifications
5.1 Management Capacity

5.2 Physical Bandwidth Requirements
5.3 Data Storage Specifications
5.4 Safety Standards
5.5 EMC Specifications
5.6 Environmental Requirements
5.1 Management Capacity

Servers of varied management capacities are configured when different PRS features are
applied.
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 16.1 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 ATAE Board Configuration VMs Configuration
Capacity (Number
of Equivalent NEs)
≤ 400 2 PRS server boards (1 master and 1*PRS Service

1 standby) + 2 PRS DB boards (1 VM+1*PRS Master DB
VM+1*PRS Slave DB

iManager PRS
Management ATAE Board Configuration VMs Configuration

Capacity (Number
of Equivalent NEs)
master and 1 standby) VM
≤ 800 2 PRS server boards (1 master and 2*PRS Service
1 standby) + 2 PRS DB boards (1 VM+1*PRS Master DB
master and 1 standby) VM+2*PRS Slave DB
VM
≤ 1200 3 PRS server boards (1 master, 1 3*PRS Service

slave, and 1 standby) + 3 PRS DB VM+1*PRS Master DB
boards (1 master, 1 slave, and 1 VM+3*PRS Slave DB
standby) VM
standby) VM
standby) VM
standby) VM
≤ 4000 NA 10*PRS Service

VM+1*PRS Master DB
VM+10*PRS Slave DB
VM
5.1.2 Server Management Capacity (RAN Service Visibility)

Table 5-2 PRS ATAE server management capacity (RAN service visibility)
Configuration RAT Management ATAE Board

Capacity Configuration
Configuration 1 UMTS Less than 6,000 cells 2 PRS MBB PS

and less than server boards (1
300,000 online users master and 1
standby) + 3 PRS
LTE Less than 6,000 cells MBB PS DB boards
and less than 30,000 (1 master, 1 slave,
connected users and 1 standby)

iManager PRS
Table 5-3 PRS virtual system management capacity (RAN service visibility)
Configuration 1 1*PRS Service VM+1*PRS Master DB VM+2*PRS Slave DB VM


The management capacity is obtained based on the standard traffic model. For details about the traffic
model, see iManager PRS V100R017 Management Capacity Specifications.
The management capacity rely on the features to be deployed, so you can only generate the
configuration based on the management capacity and the features to be deployed.
5.1.3 Server Management Capacity (PS Service Visibility)

Table 5-4 PRS server management capacity (PS service visibility)
Configuration ATAE Board VMs Configuration

Configuration
Configuration 1 2 PRS MBB PS server 1*PRS Service VM+1*PRS

boards (1 master and 1 Master DB VM+2*PRS
standby) + 3 PRS MBB PS Slave DB VM
DB boards (1 master, 1
slave, and 1 standby)

boards (1 master, 1 slave, Master DB VM+4*PRS
and 1 standby) + 5 PRS Slave DB VM
MBB PS DB boards (1
master, 3 slave, and 1
standby)

iManager PRS
Configuration ATAE Board VMs Configuration

Configuration

MBB PS DB boards (1
standby)
MBB PS DB boards (1
standby)
Configuration 7 NA 8*PRS Service VM+1*PRS

Master DB VM+20*PRS
Slave DB VM
Table 5-5 TSP server management capacity (PS service visibility)
Management Capacity (Equivalent ATAE Board Configuration

Gbit/s)
≤10.0 4 TSP server boards
≤ 25.0 6 TSP server boards

The TSP 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 TSP
preprocesses the data to meet PRS requirements.
5.2 Physical Bandwidth Requirements

The bandwidth between the PRS server and PRS client must be greater than or equal to 10
Mbit/s.
The following tables list physical bandwidths required between the PRS server and its
peripheral systems:
Table 5-6 Bandwidth requirements between the PRS server and U2000 server
Management Capacity (Number of Bandwidth Requirement (Mbit/s)

Equivalent NEs)

iManager PRS

Equivalent NEs)
≤ 400 20
≤ 800 40
≤ 1200 60
≤ 1600 80
≤ 2000 100
≤ 3200 100
Table 5-7 Bandwidth requirements between the TSP and PRS

Equivalent Subscribers)
≤ 1,000,000 125
≤ 2,500,000 250
≤ 5,000,000 375
≤ 7,500,000 500
≤ 10,000,000 875
≤ 20,000,000 1250
Table 5-8 Bandwidth requirements between the TSP and UPCC
Management Capacity Bandwidth Requirement Bandwidth Requirement

(Number of Equivalent (Mbit/s) (Mbit/s)
Subscribers) UPCC(USDR) UPCC(EDR)
≤ 1,000,000 3 4
≤ 2,500,000 6 10
≤ 5,000,000 12 20
≤ 7,500,000 18 30
≤ 10,000,000 24 40

iManager PRS
Table 5-9 Bandwidth requirements between the TSP and USN
Management Capacity Bandwidth Requirement Bandwidth Requirement

(Number of Equivalent (Mbit/s) (Mbit/s)
Subscribers) USN OMU USN EVU
≤ 1,000,000 6 30
≤ 2,500,000 15 75
≤ 5,000,000 30 150
≤ 7,500,000 45 225
Table 5-10 Bandwidth requirements between the TSP and UGW
Management Capacity (Volume of Bandwidth Requirement (Mbit/s)

Equivalent Traffic)
≤ 10 Gbit/s 200
≤ 25 Gbit/s 500
≤ 50 Gbit/s 1000
≤ 75 Gbit/s 1500
≤ 100 Gbit/s 2000
Table 5-11 Bandwidth requirements between the TSP and NMS

Management Capacity (Volume of Bandwidth Requirement (Mbit/s)
Equivalent Traffic)
≤ 10 Gbit/s 30
≤ 25 Gbit/s 75
≤ 50 Gbit/s 150
≤ 75 Gbit/s 225
≤ 100 Gbit/s 300
Table 5-12 Bandwidth requirements between the TSP and Trace Server
Management Capacity RAT Bandwidth Requirement
(Typical) (Mbit/s)
30,000 connected users LTE 200

(About 1000 sites)

iManager PRS
Management Capacity RAT Bandwidth Requirement

(Typical) (Mbit/s)
300,000 online users (About UMTS 50

1000 sites)
5.3 Data Storage Specifications

Table 5-13 and Table 5-15 list the specifications for saving data on the PRS.
Table 5-13 Data storage specifications (RAN statistics performance visibility)
Data Default Storage Duration
Non-Neighboring Value range: 1 to 14.

Cell Object The default value is 3.
Raw data (unit: day)
Neighboring Cell Value range: 0 to 14.
Object The default value is 3.

Hour granularity data (unit: day)

Day granularity data (unit: day)

Week granularity data (unit: week)

Month granularity data (unit: month)

Daily busy hour data (unit: day)

iManager PRS

Weekly busy hour data (unit: week)v

Monthly busy hour data (unit: month)

Maximum storage duration of data
generated during holidays (unit: month) Value range: 0 to 13.
Neighboring Cell
Storage duration of raw data (unit: day) 32
Maximum number of days within

7
holidays (unit: day)
Table 5-14 Data storage specifications (RAN service visibility)
Hour granularity data (unit: day) 14
Day granularity data (unit: day) 92
Week granularity data (unit: week) 52

Month granularity data (unit: month) 36
Table 5-15 Data storage specifications (PS service visibility)
5 minute statistic 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 Location(When
TopN by is set to Traffic, (SGSN/S-GW)/LAI/TAI),
Network > By RAT, Network > By Rules, Network >
By Blocked Traffic, Subscriber > TopN Subscribers,
Subscriber > Specified Subscriber (Group).
Hour granularity data (unit: day) 14

iManager PRS
Day granularity data (unit: day) 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:
 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:

iManager PRS
 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
5.6.1 Storage Environment

Climatic Requirements
Table 5-16 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
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-17

iManager PRS
Table 5-17 Requirements for the density of physically active materials
Physically Active Unit Density

Material
Suspended dust mg/m³ ≤ 5.00

Deposited dust mg/m²h ≤ 20.0
Sand mg/m³ ≤ 300
NOTE
 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-18
Table 5-18 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
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-19 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 ≤ 250 m/s²

spectrum II

iManager PRS
Static payload ≤ 5 kPa
NOTE
 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-20 Climatic requirements for shipping

Item Value Range
Temperature -20°C (-4ºF)–60°C (140ºF)

Relative humidity 8%–93%
Altitude ≤ 5000 m
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 5-21

iManager PRS

Material
Suspended dust mg/m³ -

Deposited dust mg/m²h ≤ 3.0
Sand mg/m³ ≤ 100
NOTE
 Suspended dust: diameter ≤ 75 μm
 Deposited dust: 75 μm ≤ diameter ≤ 150 μm
 Sand: 150 μm ≤ diameter ≤ 1000 μm
Table 5-22

Material
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-23 Mechanical stress requirements for shipping environment

Sinusoidal Offset ≤ 7.5 mm - -

vibration
Accelerated - ≤ 20.0 m/s² ≤ 40.0 m/s²
speed
Frequency 2 Hz–9 Hz 9 Hz–200 Hz 200 Hz–500 Hz

range

iManager PRS
Random Spectrum 10 m²/s³ 3 m²/s³ 1 m²/s³

vibration density of
accelerated
speed
Frequency 2 Hz–9 Hz 9 Hz–200 Hz 200 Hz–500 Hz

range
Unsteady Impact response ≤ 300 m/s²
impact spectrum II
Static payload ≤ 10 kPa
NOTE
 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-24 Temperature and humidity requirements for operation
Temperature Relative Humidity
5°C (41ºF)–35°C (95ºF) 20%–80%
NOTE
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-25 Other climatic requirements for operation
Item Value Range
Altitude ≤ 4000 m


iManager PRS

Table 5-26.

Material
Dust particle particle/m³ ≤ 3 x 104

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

Material
SO2 mg/m³ ≤ 0.20
H2S mg/m³ ≤ 0.006
NH3 mg/m³ ≤ 0.05
Cl2 mg/m³ ≤ 0.01
Table 5-28 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

iManager PRS
Unsteady impact Impact response ≤ 100 m/s²

spectrum II
Static payload 0
NOTE
 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 6 A Acronyms and Abbreviations
6 A Acronyms and Abbreviations
APN access point name

ATAE Advanced Telecommunications Application
Environment
CDR Call Details Record
FTP File Transfer Protocol
GGSN Gateway GPRS Support Node
L
LTE Long Term Evolution
M
MBB mobile broadband
MME mobility management entity
P
PCC Policy and Charging Control

iManager PRS
Product Description 6 A Acronyms and Abbreviations
PCRF policy and charging rules function

P-GW Packet Data Network Gateway
PS packet switched
SAU service aware unit

SGSN Serving GPRS Support Node
S-GW serving gateway

SP service provider
UDR User Data Record
UGW unified gateway
UPCC Unified Policy and Charging Controller
USN unified service node


PRS Product Description

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

PRS Product Description

Diunggah oleh

Hak Cipta:

Format Tersedia

iManager PRS

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 05 (2017-09-30) Huawei Proprietary and Confidential i

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

3 Products and Application Scenarios .................................................................................. 12

5 Technical Specifications ..................................................................................................... 22

6 A Acronyms and Abbreviations ......................................................................................... 38

Issue 05 (2017-09-30) Huawei Proprietary and Confidential ii

1 Product Positioning and Features

1.1 Product Positioning

1.1 Product Positioning

1.2 Product Features

Issue 05 (2017-09-30) Huawei Proprietary and Confidential 1

Closed-Loop MBB Management

Figure 1-1 MBB closed-loop management model

Flexible and Efficient Platform for Analyzing Performance

Issue 05 (2017-09-30) Huawei Proprietary and Confidential 2

Figure 1-2 Procedure for customizing reports

Performance Analysis Expert

Issue 05 (2017-09-30) Huawei Proprietary and Confidential 3

Performance analysis themes integrated with Huawei performance analysis experience

Real-time KPI Monitoring

Efficient and Intelligent Performance Threshold Alarms

Issue 05 (2017-09-30) Huawei Proprietary and Confidential 4

Issue 05 (2017-09-30) Huawei Proprietary and Confidential 5

2.1 Position on the Network

Issue 05 (2017-09-30) Huawei Proprietary and Confidential 6

SGSN/MME GGSN/P-GW PCRF

GGSN/P-GW service network

Scenario 2 - U2000 southbound and northbound network isolation

Issue 05 (2017-09-30) Huawei Proprietary and Confidential 7

SGSN/MME GGSN/P-GW PCRF

GGSN/P-GW service network

PCRF service network

2.2 Hardware Devices

Figure 2-3 PRS hardware devices

Issue 05 (2017-09-30) Huawei Proprietary and Confidential 8

2.3 Hardware Description

2.4 Software Architecture

Figure 2-4 Software architecture of the PRS

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

Issue 05 (2017-09-30) Huawei Proprietary and Confidential 9

Table 2-1 Components of the PRS system

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

TSP The TSP (Trace Server Professional) is an enhanced component of the

2.5 Virtualization Platform

Issue 05 (2017-09-30) Huawei Proprietary and Confidential 10

Issue 05 (2017-09-30) Huawei Proprietary and Confidential 11

3 Products and Application Scenarios

3.1 RAN Statistics Performance Visibility

Network Application Scenario

Adjustment Provides a KPI Benchmarking function to help users compare the

Maintenance  Provides an end-to-end report customization function to help users

Issue 05 (2017-09-30) Huawei Proprietary and Confidential 12

Network Application Scenario

3.2 PS Service Visibility

Issue 05 (2017-09-30) Huawei Proprietary and Confidential 13

 Policy and Rules Usage Statistics

Issue 05 (2017-09-30) Huawei Proprietary and Confidential 14

Issue 05 (2017-09-30) Huawei Proprietary and Confidential 15

3.3 MBB Service Visibility-RAN

Issue 05 (2017-09-30) Huawei Proprietary and Confidential 16

Configuration 1 1PRS Service VM+1PRS Master DB VM+2*PRS Slave DB VM

Configuration 2 1PRS Service VM+1PRS Master DB VM+3*PRS Slave DB VM

Configuration 4 2PRS Service VM+1PRS Master DB VM+4*PRS Slave DB VM

Configuration 5 2PRS Service VM+1PRS Master DB VM+5*PRS Slave DB VM

Configuration 6 4PRS Service VM+1PRS Master DB VM+10*PRS Slave DB VM

Configuration 1 2 PRS MBB PS server 1PRS Service VM+1PRS

Configuration 4 3 PRS MBB PS server 2PRS Service VM+1PRS

Configuration 5 3 PRS MBB PS server 2PRS Service VM+1PRS

Configuration 7 NA 8PRS Service VM+1PRS