PRS RAN Sevice Visibility

iManager PRS
V100R014
RAN Sevice Visibility (KQI)

Feature Description
Issue
02
Date
2014-07-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

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

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

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

Copyright Huawei Technologies Co., Ltd.
iManager PRS RAN Sevice Visibility (KQI) Feature Description
Contents
Contents
1 About This Document .................................................................................................................. 1
1.1 Scope ................................................................................................................................................................ 1
1.2 Product Versions ............................................................................................................................................... 1
1.3 Intended Audience ............................................................................................................................................ 1
1.4 Change History................................................................................................................................................. 2
2 Overview......................................................................................................................................... 3
3 Technical Description .................................................................................................................. 4
3.1 Basic Principles ................................................................................................................................................ 4
3.2 Basic Concepts ................................................................................................................................................. 7
3.2.1 KQIs for Evaluating the User Experience of Web Browsing Services .................................................... 7
3.2.2 KQIs for Evaluating the User Experience of Video Services .................................................................. 8
4 Introduction.................................................................................................................................. 10
4.1 Description ..................................................................................................................................................... 10
4.1.1 WOFD-091910 UMTS RAN KQI-Web Visibility ................................................................................ 10
4.1.2 WOFD-091911 UMTS RAN KQI-Video Visibility .............................................................................. 10
4.1.3 WOFD-091915 UMTS RAN KQI-Application Customization ............................................................ 11
4.1.4 WOFD-091916 UMTS RAN KQI-SPI Customization ......................................................................... 11
4.1.5 WOFD-091917 UMTS RAN KQI-Terminal Customization ................................................................ 11
4.2 Dependencies ................................................................................................................................................. 11
4.3 Impacts ........................................................................................................................................................... 11
5 Engineering Guidelines ............................................................................................................. 13

5.1 When to Use Web Browsing Acceleration ..................................................................................................... 13
5.1.1 Networking ........................................................................................................................................... 13
5.1.2 Hardware Requirements ........................................................................................................................ 16
5.1.3 IP Address Planning .............................................................................................................................. 17
5.1.4 License Requirements ........................................................................................................................... 18
5.2 Feature Deployment ....................................................................................................................................... 18
6 Technical Specifications ................................................................................................................ 19

A Acronyms and Abbreviations .................................................................................................. 20
Issue 02 (2014-07-30)

ii
Figures
Figures
Figure 3-1 KQI data generation process ................................................................................................................ 5
Figure 5-1 Networking of the RAN Service Visibility feature (one ATAE subrack is involved and the TS and
U2000 are deployed together in a cluster) ............................................................................................................ 14
Figure 5-2 Networking of the RAN Service Visibility feature (two ATAE subracks are involved and the TS and
U2000 are deployed together in a cluster) ............................................................................................................ 15
Figure 5-3 Networking of the RAN Service Visibility feature (the TS is deployed independently in a cluster) . 15
Issue 02 (2014-07-30)

iii
Tables
Tables
Table 3-1 KQI data generation process .................................................................................................................. 6
Table 3-2 Web browsing KQIs .............................................................................................................................. 7
Table 3-3 Video KQIs ............................................................................................................................................ 8
Table 4-1 Impacts of the RAN Service Visibility feature .................................................................................... 12
Table 5-1 Application scenarios and networking schemes of the RAN Service Visibility feature ...................... 13
Table 5-2 Requirements of the RAN Service Visibility feature on related product hardware ............................. 16
Table 5-3 Number of configured PRS boards ...................................................................................................... 16
Table 5-4 Number of configured TS boards (the TS and U2000 are deployed in a cluster) ................................ 17
Table 5-5 Number of configured TS boards (the TS is independently deployed in a cluster) ............................. 17
Table 5-6 Number of configured RNC boards ..................................................................................................... 17
Table 5-7 IP address planning .............................................................................................................................. 18
Table 5-8 Reference documents ........................................................................................................................... 18
Table 6-1 Technical specifications for the RAN service visibility feature ........................................................... 19
Issue 02 (2014-07-30)

iv
1 About This Document
About This Document
1.1 Scope
This document describes the principles, deployment impacts, and deployment guidelines of
the RAN Service Visibility feature.
The RAN Service Visibility feature involves various features provided by the RNC, xSAU,
PRS, and Trace Server (TS). This document describes the following PRS features:
WOFD-091910 UMTS RAN KQI-Web Visibility
WOFD-091911 UMTS RAN KQI-Video Visibility
WOFD-091915 UMTS RAN KQI-Application Customization
WOFD-091916 UMTS RAN KQI-SPI Customization
WOFD-091917 UMTS RAN KQI-Terminal Customization
1.2 Product Versions

The following table lists the product versions related to this document.
Product Name
Product Version
RNC
BSC6900: UMTS V900R016 or later
BSC6910: UMTS V900R016 or later
xSAU
V200R013C00 and V200R014C00 or later
PRS
V100R014C00 or later
TS
V200R014C00SPC110 or later
1.3 Intended Audience

This document is intended for:
Issue 02 (2014-07-30)

Network planning engineers
Network management engineers
1 About This Document
1.4 Change History

This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
Feature change
Changes in features of a specific product version
Editorial change
Changes in wording or addition of information that was not described in the earlier
version
02 (2014-07-30)
This is the second commercial release for iManager PRS V100R014C00.
01 (2014-06-10)
This is the first commercial release for iManager PRS V100R014C00.
Issue 02 (2014-07-30)

2 Overview
Overview
User experience is an important indicator in assessing radio network quality. Requirements for
user experience differ according to service types. For example, users expect clear voice,
smooth video, and fast web browsing. Meanwhile, different services have different
requirements for quality of service (QoS). For example, a network with less than 64 kbit/s
bandwidth can provide clear voice services but unfavorable video services. To provide better
user experience, radio networks need to provide differentiated QoS schemes for different
types of services.
Traditional UMTS networks do not differentiate service types, and therefore provide the same
QoS scheme for all types of packet switched (PS) services. Such UMTS networks are referred
to as blind pipe.
To implement the smart pipe strategy, Huawei introduces the service awareness technology
and service type-based QoS management, which provide better user experience and help
operators manage QoS more easily.
Huawei provides features, hardware, and services in different RAN versions to facilitate smart
pipe management.
Issue 02 (2014-07-30)

3 Technical Description
Technical Description
3.1 Basic Principles

Figure 3-1 shows the data flow diagram of the RAN Service Visibility (KQI) feature. KQI is
short for key quality indicator.
Issue 02 (2014-07-30)

Figure 3-1 KQI data generation process

CHR data
Configuration data
Function control
channel
Web Client
PRS
Web Server
Configuration
Application
Database
Aggregation
ETL extraction
Collection
CORBA-based subscription
U2000
Trace Server
MML
Configuration
Mediation
MML-based subscription
RNC
SAU
OMU
Subscribe to data
SPU
NIU
Enable the service awareness function
Copy data
DPU
User service
packets
Process
packets
Obtain user
service flow
data
Sample user
service flow data
Implement
policies
Send
packets
The KQI data generation process involves the RNC, xSAU, TS, and PRS. Table 3-1 describes
the KQI data generation process.
Issue 02 (2014-07-30)

Table 3-1 KQI data generation process

Procedure
Involved
Device
Description
Sampling user
service flow data
RNC
The control plane of the RNC samples and adds sampling

flags to user data based on specified sampling rules. Then, the
dispatching unit (DPU) copies the service flow data whose
sampling flags have been set to the network interface unit
(NIU). KQIs are sampled based on cell settings. The cell-level
KQI sampling rate is 100%.
Identifying
services
RNC
A service awareness (SA) component is installed on the NIU

board of the RNC. This component identifies and analyzes
user service data flows and generates single-stream QoS KQIs.
Parsing services
RNC
The RNC associates and aggregates the multiple transactions

of single- or multi-service flows to identify the multiple HTTP
requests of a single web browsing service and generate a web
browsing service record, and to identify a single video service.
After the NIU board generates performance call history
records (PCHRs) periodically, the service process unit (SPU)
writes the generated PCHRs into PCHR files.
Extracting KQIs
SAU, PRS, and

TS
1. The configuration module of the PRS system delivers a

data subscription request to the TS over the CORBA
interface.
2. The TS issues a command to the operation and
maintenance unit (OMU) of the RNC through the
mediation service of the U2000. Then, the OMU
delivers the subscription information to the control plane
and user plane boards. The TS connects to the SAU
board of the RNC to manage settings about uploading
PCHR files from the SAU.
3. The SAU filters and compresses PCHR files, and then
uploads the PCHR files to the TS.
4. The collection module of the PRS downloads PCHR
files from the TS, and then submits the PCHR files to
the extract, transform, and load (ETL). The ETL then
starts processing and parsing the PCHR files.
5. After the PRS obtains PCHR files, it parses the PCHR
files and extracts KQI data. The PRS aggregates KQI
data from object dimensions (such as cell and RNC),
and then stores the aggregation results in the PRS
database.
Aggregating
KQIs
PRS
The PRS aggregates hourly KQI data by day periodically

every day, and stores the aggregation results in the PRS
database. Engineers can query KQIs on a web-based PRS
client.
Issue 02 (2014-07-30)

3.2 Basic Concepts

With the widespread use of intelligent terminals, mobile broadband (MBB) traffic increases
sharply. Various PS data services gradually replace traditional voice services and become
mainstream services of radio networks. Among PS data services, web browsing and video on
demand have a high penetration rate.
In the voice service era, network key performance indicator (KPI) management focuses on the
control plane of a mobile network. Counters are used to evaluate user experience based on
signaling messages transmitted over the mobile network. For example, the call completion
rate reflects user experience in successfully initiating calls and the call drop rate reflects user
experience in enjoying smooth calls.
In the MBB service era, users are more sensitive to the user plane of data services, for
example, the delay in opening web pages and whether video playback is smooth. Such userplane-dependent user experience cannot be reflected by network KPIs based on the control
plane.
KQIs are extensions and enhancements of existing network KPIs. KQIs together with KPIs
serve as the basis for network capacity expansion and network optimization.
3.2.1 KQIs for Evaluating the User Experience of Web Browsing

Services
The RNC performs service type awareness on the radio network user plane to determine
whether a data service is web browsing. For a web browsing service, the RNC parses key
events during data transmission to obtain the KQIs described in Table 3-2.
Table 3-2 Web browsing KQIs
KQI Name
Definition
Description
Page
Response
Success Ratio
This counter indicates the

probability of successful
web page connection setup
after a user initiates a
request for browsing a web
page.
Web page connection setup includes three

processes: connecting to the DNS, setting
up a TCP link, and sending the first HTTP
connection request by the terminal. A user
cannot browse a web page if these processes
fail.
Page
Response
Delay

interval between the time a
user initiates a web page
browsing request and the
time the web page
connection is successfully
set up.
A web page response includes three

processes: connecting to the DNS, setting
up a TCP link, and sending the first HTTP
connection request by the terminal. All
delays in the three processes comprise the
page response delay.
Issue 02 (2014-07-30)

KQI Name
Definition
Description
Page
Browsing
Success Ratio

probability that a user can
successfully download all
desired web page contents.
After a web page connection is successfully

set up, the browser on the terminal side will
parse the contents returned by the server.
Based on the web page contents, the
browser automatically initiates GET
connection requests to request the
downloading of page contents until the page
contents are completely downloaded.
Different GET requests are used to
download different web page contents. If
the terminal sends a GET request but the SP
server does not respond or the ACK
message is incomplete, some contents in the
web page cannot be displayed, which affects
user experience.
Page
Browsing
Delay

period between the time the
SP server sends the first
packet with a response
code and the time all web
page contents are
successfully downloaded.
After a web page connection is successfully

set up, the browser on the terminal side will
parse the contents returned by the server.
Based on the web page contents, the
browser automatically initiates GET
connection requests to request the
downloading of page contents until the page
contents are completely downloaded.
Subscribers can perceive the delay of
downloading web page contents. The delay
depends on the size of the web page.
Page
Download
Throughput

download rate of contents
displayed on the page.
This counter indicates the average rate of

downloading web page contents and reflects
the data transmission capability of the
network.
3.2.2 KQIs for Evaluating the User Experience of Video Services

The RNC performs service type awareness on the radio network user plane to determine
whether a data service is HTTP-based video service. For a video service, the RNC parses key
events during data transmission to obtain the KQIs described Table 3-3.
Table 3-3 Video KQIs
KQI Name
Definition
Description
Streaming Start
Success Ratio

probability that video
playing successfully starts
after a user initiates a video
request and the initial buffer
is complete.
Before video playing begins, an

amount of data must be buffered. If the
buffer fails, the user cannot watch the
video.
Issue 02 (2014-07-30)

KQI Name
Definition
Description
Streaming Start
Delay

period between the time the
user initiates a video request
and the time the video
playing begins.
Initial buffering begins after the server

responds to the video request. When
the terminal receives a certain amount
of data, video playing begins. Users
can directly experience the initial
buffering delay.
Streaming Stall
Frequency

number of pauses caused by
the network rate fluctuation
during video playing.
During video playing, if the buffer data

of the player is cleared because of
network rate fluctuation, the UE will
re-buffer data. After a certain amount
of data is received, the video playing
will resume. User experience will be
affected by the number of video
pauses.
Average
Streaming Stall
Time

time length of the pauses
caused by the network rate
fluctuation during video
playing.
During video playing, if the buffer data

of the player is cleared because of
network rate fluctuation, the UE will
re-buffer data. After a certain amount
of data is received, the video playing
will resume. User experience will be
affected by the time length of video
pauses.
Streaming
Download
Throughput

download rate during the
whole video service.
This counter indicates the average

download rate of streaming videos and
reflects the transmission capacity of the
network.
In a few cases, the measured KQIs cannot reflect the actual situations:
When a user's network connection is dropped, the user's web browsing and video services may be
interrupted, and accordingly the KQI measurement ends. Subsequently, if the user re-establishes a
network connection, the web browsing and video services can resume. In this case, the KQIs reflect
only the situation before the network connection is dropped.
In an inter-RAT handover procedure or SRNS relocation procedure, if the UE is processing web

browsing or video services, the KQI measurement ends when it moves out of the source RNC. In
this case, the KQIs cannot reflect the situation under the target RNC.
To achieve visibility of web browsing and video KQIs, Huawei PRS must be deployed and
the RAN Service Visibility (KQI) feature must be enabled.
Issue 02 (2014-07-30)

4 Introduction
Introduction
The RAN Service Visibility feature of the PRS includes the following functions, which can
help operators detect abnormal KQIs in time and perform network capacity expansion and
optimization accordingly:
WOFD-091910 UMTS RAN KQI-Web Visibility
WOFD-091911 UMTS RAN KQI-Video Visibility
4.1 Description
4.1.1 WOFD-091910 UMTS RAN KQI-Web Visibility
After this feature is activated, engineers can achieve visibility of web browsing service
experience. Engineers can select objects and specify a time range to query web browsing
KQIs based on the selected objects and time range.
The objects can be one or more RNCs or cell groups.
The time range can be set to one or more days or several consecutive hours within one day.
The PRS displays the average KQI values for the specified objects within the specified time range.
The average KQI values that exceed the preset thresholds will be highlighted.
The data displayed on the PRS supports data drilling. This helps engineers learn the KQIs for the
specified objects or view the line chart that shows the KQI change trends within the specified time
range.
4.1.2 WOFD-091911 UMTS RAN KQI-Video Visibility

After this feature is activated, engineers can achieve visibility of video service experience.
Engineers can select objects and specify a time range to query video KQIs based on the
selected objects and time range.
Issue 02 (2014-07-30)

10
4 Introduction
The objects can be one or more RNCs or cell groups.
The time range can be set to one or more days or several consecutive hours within one day.
The PRS displays the average KQI values for the specified objects within the specified time range.
The average KQI values that exceed the preset thresholds will be highlighted.
The data displayed on the PRS supports data drilling. This helps engineers learn the KQIs for the
specified objects or view the line chart that shows the KQI change trends within the specified time
range.
4.1.3 WOFD-091915 UMTS RAN KQI-Application Customization

After this feature is activated, engineers can achieve visibility of KQIs that are defined based
on users' visited application protocols. In addition to selecting objects and specifying a time
range, engineers can select application protocols to query KQI statistics based on the selected
application protocols.
4.1.4 WOFD-091916 UMTS RAN KQI-SPI Customization

on users' scheduling priority indicators (SPIs). In addition to selecting objects and specifying
a time range, engineers can select SPIs to query KQI statistics based on the selected SPIs.
4.1.5 WOFD-091917 UMTS RAN KQI-Terminal Customization

on terminal type-specific application protocols. In addition to selecting objects and specifying
a time range, engineers can select terminal types to query KQI statistics based on the selected
terminal types.
4.2 Dependencies
The functions provided by the PRS's RAN Service Visibility feature can be deployed together
once and for all. After the deployment, these functions can be enabled separately.
Engineers must check that the PRS's basic features have been deployed before they deploy the
RAN Service Visibility feature.
The following functions can be enabled only after WOFD-091910 UMTS RAN KQIWeb Visibility and WOFD-091911 UMTS RAN KQI-Video Visibility are enabled:
4.3 Impacts
The deployment of the RAN Service Visibility feature affects the RNC, xSAU, and TS. For
details, see Table 4-1.
Issue 02 (2014-07-30)

11
4 Introduction
Table 4-1 Impacts of the RAN Service Visibility feature

Impact
Description
Impact on the RNC

and xSAU
The RAN Service Visibility feature does not affect the

performance of any RNC accessed by the PRS. However, this
feature requires that one SAUc or ESAUa board be added to the
subrack of each RNC accessed by the PRS.
Impact on the TS
The RAN Service Visibility feature affects the TS performance.

Therefore, new TS boards need to be added based on site
conditions.
Issue 02 (2014-07-30)
If the TS provides services (such as reporting data) only for the

PRS, new TS boards need to be added based on the
management capacity (equivalent Gbit/s) of the PRS.
One TS board needs to be added if the required management

capacity of the PRS is 20 Gbit/s or less.
Two TS boards need to be added if the required management

capacity of the PRS is 40 Gbit/s or higher.
If the TS provides services for multiple upper-layer applications

simultaneously, 15% of hardware resources need to be added
for every new application to be served by the TS. For details,
contact Huawei technical support.

12
5 Engineering Guidelines
Engineering Guidelines
5.1 When to Use Web Browsing Acceleration

The RAN Service Visibility (KQI) feature must be deployed before network design. The
network design covers networking, transmission, interfaces, resource capacity, and feature
services with network security, load balance, scalability, and reliability fully considered to
provide guidelines for engineering implementation and construction and ensure the highquality operation of operators' networks.
The network design is not described in this document. For details about the network design, see
iManager PRS V100R014 MBB Service Visibility Network Design Guide.
5.1.1 Networking
Table 5-1 describes the application scenarios and networking schemes of the RAN Service
Visibility feature.
Table 5-1 Application scenarios and networking schemes of the RAN Service Visibility feature
Scenario
Scenario Description
Networking
Scenario 1
The Statistical Performance Visibility feature has been

deployed on an HP server, and you want to add the RAN
Service Visibility feature to the existing U2000/M2000
ATAE cabinet.
See Figure 5-1.
Scenario 2
The Statistical Performance Visibility feature has been

deployed on an HP server, and you want to independently
deploy the RAN Service Visibility feature in a new ATAE
cabinet.
See Figure 5-2.
Scenario 3
You want to deploy the RAN Service Visibility and

Statistical Performance Visibility features in a new ATAE
cabinet.
See Figure 5-3.
Scenario 4
You want to add the RAN Service Visibility feature to an

ATAE cabinet where the Statistical Performance Visibility
feature has been deployed.
See Figure 5-3.
Issue 02 (2014-07-30)

13
Boards related to the RAN Service Visibility feature as shown in Figure 5-1 and Figure 5-2 are as
follows:
TS boards: include the master, slave, and standby TS boards.
PRS boards: include the master and slave MBB RAN boards, the standby PRS board, and the active
and standby MBB database (DB) boards.
Figure 5-1 Networking of the RAN Service Visibility feature (one ATAE subrack is involved and
the TS and U2000 are deployed together in a cluster)
Issue 02 (2014-07-30)

14
Figure 5-2 Networking of the RAN Service Visibility feature (two ATAE subracks are involved
and the TS and U2000 are deployed together in a cluster)
Figure 5-3 Networking of the RAN Service Visibility feature (the TS is deployed independently in
a cluster)
Issue 02 (2014-07-30)

15
5.1.2 Hardware Requirements

Table 5-2 describes the requirements of the RAN Service Visibility feature on related product
hardware.
Table 5-2 Requirements of the RAN Service Visibility feature on related product hardware
Product
Hardware Requirement
PRS
New MBB RAN service boards and DB boards need to be deployed. The
number of required new MBB RAN service boards and DB boards is
determined by operators' requirement on network management capacity.
For details, see Table 5-3.
TS
New TS service boards need to be deployed. The number of required new

TS service boards is determined by operators' requirement on network
management capacity. For details, see Table 5-5.
If TS boards have been deployed on the live network, new TS service

boards need to be added based on the number of existing TS boards and
the required management capacity to expand network management
capacity.
If no TS boards have been deployed, new TS boards need to be installed.
BSC6900
NIUa boards and SAU (SAUa or SAUc) boards need to be deployed. For
details about the number of required NIUa boards and SAU boards, see
Table Table 5-6.
BSC6910
ENIUa boards and ESAUa boards need to be deployed. For details about
the number of required ENIUa boards and ESAUa boards, see Table 5-6.
Table 5-3 Number of configured PRS boards

Management Capacity
(Equivalent Gbit/s)
ATAE Board Configuration
5.0
3 PRS MBB RAN server boards (1 master, 1 slave, and 1

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

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

40.0

Issue 02 (2014-07-30)

16
Table 5-4 Number of configured TS boards (the TS and U2000 are deployed in a cluster)
Management Capacity
(Number of Equivalent
Subscribers)
20.0
1 Trace Server board (1 master)
40.0
2 Trace Server boards (1 master and 1 slave)
Table 5-5 Number of configured TS boards (the TS is independently deployed in a cluster)

Management Capacity
(Number of Equivalent
Subscribers)
20.0
2 Trace Server boards (1 master and 1 standby)
40.0
3 Trace Server boards (1 master, 1 slave, and 1 standby)
Table 5-6 Number of configured RNC boards

RNC
Board
Type
Number
Description
BSC6900
SAUc
SAUa
The SAUa or SAUc board can be inserted into the main

processing subrack (MPS) or EPS-3. EPS is short for
extended processing subrack.
The SAUa or SAUc board has high requirements on heat
dissipation, and therefore must be inserted in the lowest
subrack of the cabinet.
BSC6910
NIUa
The NIUa board can be inserted in the MPS or EPS-3.
ESAUa
ENIUa
The ESAUa or ENIUa board can be inserted in the

MPS or EPS-3.
5.1.3 IP Address Planning

When the U2000 is not deployed by using the southbound and northbound isolation solution,
only an O&M IP address needs to be planned. For details, see Table 5-7.
When the U2000 is deployed by using the southbound and northbound isolation solution,
southbound and northbound IP addresses need to be planned in addition to the preceding
O&M IP address.
Issue 02 (2014-07-30)

17
Table 5-7 IP address planning

Management Capacity
(Equivalent Gbit/s)
Total Number of IP Addresses (One IP Address Is

Planned for Each New Board)
OSMU
PRS
TS
RAN SAU
5 Gbit/s
10 Gbit/s
20 Gbit/s
40 Gbit/s
15
Planned
based on the
number of
RNCs on
the live
network
5.1.4 License Requirements

Engineers need to apply for a license that provides a sufficient smart service processing
throughput rate for RNCs. Each NIUa board provides a smart service processing throughput
rate of 50 Mbit/s by default. If more capacity is required or new ENIUa boards are configured,
engineers need to apply for additional licenses.
5.2 Feature Deployment

The deployment of the RAN Service Visibility feature involves operations on the SAU of the
RNC, the PRS, and the TS. For details about the deployment procedure, see the following
section in iManager PRS Product Documentation: Installation and Commissioning > PRS
ATAE Cluster System Commissioning Guide (SUSE10, S3900) > PRS Commissioning
Processes. This procedure is a general end-to-end procedure and engineers must follow this
procedure to deploy the RAN Service Visibility feature.
Table 5-8 lists reference documents related to the deployment of the RAN Service Visibility
feature.
Table 5-8 Reference documents
Product
Reference Document
RAN SAU
iManager Tool(OSS-SAU) V100R001C00 User Guide
NIUa board
(For Customer)RAN16.0 Feature Documentation xx (HDX)-EN
TS
U2000 Trace Server User Guide (ATAE Cluster,

Standalone)(V200R014C00_xx)(PDF)-EN
Issue 02 (2014-07-30)

18
6 Technical Specifications
Technical Specifications
Table 6-1 Technical specifications for the RAN service visibility feature
Function
Specification
Value
Data storage time
Reports of 1 hour level (unit:

day)
14
Reports of 1 day level (unit:

day)
92
Delay for processing data of

1 hour level (unit: minute)
15 to 30
Page response time of the

browser (unit: second)
10
Number of IMEI-TACs
defined by users
50,000
Maximum number of userdefined terminal groups that

can be configured on the
PRS
Maximum number of
terminal subgroups in a userdefined terminal group
10
Location management
Maximum number of
regions that can be
configured on the PRS
100
Service management
KQI Concerned Applications

(Web)
10
KQI Concerned Applications

(Video)
10
Processing performance
Terminal management
Issue 02 (2014-07-30)

19
A Acronyms and Abbreviations
Acronyms and Abbreviations
D
DB
Database
DPU
Dispatching Unit
E
EPS
Extended Processing Subrack
ETL
Extract, Transform, and Load
K
KPI
Key Performance Indicator
KQI
Key Quality Indicator
M
MBB
Mobile Broadband
MPS
Main Processing Subrack
N
NIU
Network Interface Unit
O
OMU
Operation and Maintenance Unit
P
PCHR
Issue 02 (2014-07-30)
Performance Call History Record

20
PS
A Acronyms and Abbreviations
Packet Switched
Q
QoS
Quality of Service
S
SA
Service Awareness
SPI
Scheduling Priority Indicator
SPU
Service Process Unit
T
TS
Issue 02 (2014-07-30)
Trace Server

21

PRS RAN Sevice Visibility

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

PRS RAN Sevice Visibility

Cargado por

Copyright:

Formatos disponibles

iManager PRS

RAN Sevice Visibility (KQI)

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

iManager PRS RAN Sevice Visibility (KQI) Feature Description

5 Engineering Guidelines ............................................................................................................. 13

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

Huawei Proprietary and Confidential

iManager PRS RAN Sevice Visibility (KQI) Feature Description

Huawei Proprietary and Confidential

iManager PRS RAN Sevice Visibility (KQI) Feature Description

Huawei Proprietary and Confidential

iManager PRS RAN Sevice Visibility (KQI) Feature Description

1 About This Document

About This Document

WOFD-091910 UMTS RAN KQI-Web Visibility

WOFD-091911 UMTS RAN KQI-Video Visibility

WOFD-091915 UMTS RAN KQI-Application Customization

WOFD-091916 UMTS RAN KQI-SPI Customization

WOFD-091917 UMTS RAN KQI-Terminal Customization

1.2 Product Versions

BSC6900: UMTS V900R016 or later

BSC6910: UMTS V900R016 or later

V200R013C00 and V200R014C00 or later

1.3 Intended Audience

Huawei Proprietary and Confidential

iManager PRS RAN Sevice Visibility (KQI) Feature Description

Network planning engineers

Network management engineers

1 About This Document

1.4 Change History

Huawei Proprietary and Confidential

iManager PRS RAN Sevice Visibility (KQI) Feature Description

Huawei Proprietary and Confidential

iManager PRS RAN Sevice Visibility (KQI) Feature Description

3.1 Basic Principles

Huawei Proprietary and Confidential

iManager PRS RAN Sevice Visibility (KQI) Feature Description

Figure 3-1 KQI data generation process

Enable the service awareness function

Huawei Proprietary and Confidential

iManager PRS RAN Sevice Visibility (KQI) Feature Description

Table 3-1 KQI data generation process

The control plane of the RNC samples and adds sampling

A service awareness (SA) component is installed on the NIU

The RNC associates and aggregates the multiple transactions

SAU, PRS, and

1. The configuration module of the PRS system delivers a

The PRS aggregates hourly KQI data by day periodically

Huawei Proprietary and Confidential

iManager PRS RAN Sevice Visibility (KQI) Feature Description

3.2 Basic Concepts

3.2.1 KQIs for Evaluating the User Experience of Web Browsing

This counter indicates the

Web page connection setup includes three

This counter indicates the

A web page response includes three

Huawei Proprietary and Confidential

iManager PRS RAN Sevice Visibility (KQI) Feature Description

This counter indicates the