ZTE UMTS RAN Perfomance Monitor Feature Guide

Operator Logo
RAN Performance Monitor

WCDMA RAN
Feature Guide
RAN Performance Monitor Feature Guide

Version
V4.5
Date
2010-10-15
Author
Zeng
lingling
Approved By
Remarks
WangSuShen
2010 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains propriet ary information of ZTE and is not to be
disclosed or used without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document
is subjected to change without notice.
ZTE Confidential Proprietary
TABLE OF CONTENTS
1
Functional Attributes.......................................................................................... 1
2
2.1
2.1.1
2.1.2
2.1.3
Overview .............................................................................................................. 1
Function Introduction ............................................................................................ 1
System Data Acquisition ....................................................................................... 1
Neighboring Cell Monitoring ................................................................................. 2
Meaturement Report Record ................................................................................ 3
3
3.1
3.1.1
3.1.2
3.1.3
3.2
1.1
Technical Description......................................................................................... 4
System Data Collection ........................................................................................ 4
Performance Data Collection................................................................................ 4
Signaling Tracing (ST) .......................................................................................... 5
Online Analysis of Radio Performance................................................................. 7
Neighboring Cell Monitoring ................................................................................. 8
Measurement Report Record ............................................................................. 14
4
4.1
4.2
4.2.1
4.2.2
4.3
4.3.1
Parameters and Configuration ........................................................................ 15

System Data Acquisition ..................................................................................... 15
Neighboring Cell Monitoring ............................................................................... 16
Parameter List..................................................................................................... 16
Parameter Configuration..................................................................................... 16
Measurement Report .......................................................................................... 17
Parameter List..................................................................................................... 17
2
4.4
4.4.1
4.4.2
4.5
Counter And Alarm ........................................................................................... 19

Counter List ......................................................................................................... 19
System Data Acquisition ..................................................................................... 19
Neighbouring Cell Monitoring ............................................................................. 19
Alarm List ............................................................................................................ 19
Glossary ............................................................................................................. 19
II
FIGURES
Figure 3-1 System Architecture of Performance Statistics ..................................................... 5
Figure 3-2 System Architecture of ST ..................................................................................... 6
Figure 3-3
Measurement ID1 for Handover............................................................................. 9
Figure 3-4
Measurement ID11 for Detected Set Statistics.................................................... 10
Figure 3-5
MRs Architecture ................................................................................................. 15
TABLES
Table 3-1 Key Functions of Online Tracing ............................................................................. 7
Table 3-2 Analysis of Neighboring Cell Monitoring ............................................................... 11
III
Functional Attributes
System version: [RNC V3.09, Node B V4.09, OMMR V3.09, and OMMB V4.09]
Attribute: [Optional]
Involved NEs:
MS
-
NodeB
-
RNC
MSC
-
MGW
-
SGSN
-
GGSN
-
HLR
-
Note:
*-: Not involved.
* : Involved.
Dependency: [None]
Mutually exclusive function: [None].
Remarks: [None]
Overview
2.1
Function Introduction
2.1.1
System Data Acquisition

ZTE RAN equipment supports the collection of the following system data:
Performance statistics
ZTE RAN equipment collects various records generated during whole -net work
users' call and service process. According to these records, we may customize
from an OMCR the out put reports which include the following KPIs:
RRC establishment success rate and RAB establishment s uccess rate
Call blocking rate and call drop rate of CS/PS
Soft handover success ratio, hard handover success ratio, and Inter-RA T
handover success ratio
Throughput and bandwidth utilization ratio of Iu/ Iub/Iur interface
Traffic and flow of RNC/cell
Cell load level, utilization ratio of code resource
E1/IMA link performance statistics, AAL5/AAL2 performance statistics
IP performance statistics of Ethernet port, etc.
Signaling message
Collect the signaling messages generated when specified users make calls,
support the signaling tracing tool of an OMCR, trace specific users ' messages to
observe their call process and status, and facilitate the analysis and location of call
drop.
Online analysis of Radio Performance

Collect real-time Radio Performance during user call, including transmission power
and quality of radio links, transmission power of a cell, and uplink interference. The
graphic interfaces provided by an OMCR, such as curve diagrams and forms, make
it more convenient for users to analyze and browse..
2.1.2
Neighboring Cell Monitoring

Defining a neighboring cell relationship correctly is of vital importance to maintain
superior mobility of UE and to avoid unnecessary interference. Too many or too few
neighboring cells, or a wrong neighboring cell relationship will result in severe call drop.
The neighboring relationship bet ween cells in a network is always defined at the network
planning stage. But actual network construction and radio environment may make actual
cell coverage inconsistent with simulated network planning. As a result, the Radio
Performance (for example, adjacent cell) configured according to network planning, may
not be reasonable. Thus, the network handover success ratio is reduced and the call
drop ratio is increased.
ZTE RAN equipment supports the following modes of neighboring cell monitoring:
The neighboring cells that misses configuring.

By controlling detected set measurement of UE, the RNC can find that a cell fails to
be configured as a co-frequency neighboring cell, but actually ther e exists
overlapped coverage.
The excessive neighboring cells that is configured.

By checking the handover times and success ratio of UE between c ells, the RNC
can find that a cell is configured as a co-frequency neighboring cell at the
background, but actually there does not exist any overlapped coverage.
The neighoring cells with specific handover priority

By checking the handover success ratio of UE between neighboring cells, the RNC
can recommend configuring the handover priority for the neighboring cell of a cell. If
a neighboring cell with a high handover success ratio is configured with a high
priority, the probability of handover to this neighboring cell may be increased.
The functions provided by this feature can serve as the substitute for complex and
expensive third-party network optimization tools. Avoid inefficient but high-cost modes,
such as coverage survey and drive test, and optimize network fast and effectively.
2.1.3
Meaturement Report Record

The measurement report (MR) sent by the UE covers intra-frequency measurement,
inter-frequency measurement, inter-system meas urement, service t raffic measurement,
quality information, UE internal measurement, and location information. This attribute
supports collection, storage, and output of detailed measurement information.
The MR based data provides local cell synchronization/measurement information, RS CP,
and Ec/N0 information, and displays the information in a geographic way. Through the
MR dat a, you can know the area of weak coverage or no coverage and give suggestions
of adding more base stations.
The MR based dat a provides inter-system cell measurement information, allowing you to
know the coverage of another system and configure adjacent cells of another system.
The MR data bas ed statistical analysis allows you to know the RS CP and Ec/N0
coverage and interference of the overall network.
Based on the correlated measurement information of the local cell and adjacent cell and
UE transmit power, you can swiftly identify the areas with weak coverage, cross -cell
coverage, and pilot pollution, and diagnose external interference and optimize the
adjacent cells.
Therefore, based on the measurement report records (MRR) of the existing network
users and network planning & analysis tool, the system diagnoses the net work coverage
and interference in replacement of high-cost network optimization methods (such as
drive test).
Technical Description
3.1
System Data Collection
3.1.1
Performance Data Collection

Performance management is one main management function of a telecommunication
management net work. It collects network performance data in real time, monitors some
service events in network running in real time, and stores network performance data for
a long time. This provides a basis for the assessment and trend analysis of a public land
mobile network system. Performance management is implemented by means of
performance measurement and service statistics. By working out a series of
measurement tasks, network maintenance personnel collect performance indexes from
various net work units to implement net work performanc e management. They also
confirm the physical and logical allocation of net work, and find out any potential problem
as soon as possible.
The PM module is functionally categorized as data collection and data reporting.
1
Data collection: collect and summarize the counter values .
Data reporting: In eac h data collection granularity, data is collected and all counter
values are sent in the form of messages to an SB CX. The SB CX saves data as a
corresponding file so that an OMCR can read it.
The basic architecture of the PM module is as follows:
Figure 3-1
System Architecture of Performance Statistics

PM Manager
PMAgent
RNLC
etc.
Trans port
Module
shared
data
area
measure
ment
data
buffer
data
snapshot
area
OMC-R
ROMP
Counter query
message stream
Data stream
Active and standby
data area switching
Legend:
Legend:
Legend:
Performa
nce File
SBCX
The basic process of performance data collection and reporting is as follows:

When a defined event happens, the RNLC etc. invokes the interface provided by the PM
and writes count to the shared data area.
When a measurement period expires, the PM execution module sends the content in the
shared data area to the measurement data buffer of the PM master control module.
To avoid any data conflict, the PM execution module switches over the data snapshot
area to the shared data area.
The PM master control module on the ROMP board summarizes the content in the
measurement data buffer, and sends it to the SB CX, which saves it as performance files.
The OMC-R reads the performance file and warehouses the data.
3.1.2
Signaling Tracing (ST)

ST is an important function of equipment maintenance. WRNC receives an S T task f rom
an RCT or CTS. The operation and maint enance subsystem works with the radio
subsystem to report the signaling which satisfies user -specified conditions to a
corresponding client. The key functions of S T are as follows:
1
Task control (including creating or deleting a tracing task)
Data reporting (report the signaling which satisfies task conditions to a

corresponding client)
The basic architecture of S T is as follows:
Figure 3-2
System Architecture of S T
ROM P
peripheral board
ST Agent
RNLC
RCT
ST
M anager
peripheral board
CTS
OMM
Forwarding
ST Agent
RNLC
Control
Message
Data
Message
The basic process of task control is as follows:

The CTS creates a tracing task by means of an OMM forwarding subsystem or an S T
Tool.
Both the clients deliver task parameters to the ST Manager.
The S T Manager checks the parameters, for example, whether there are too many tasks.
If the parameters are suitable, the S T manager delivers task data to the S T Agent on the
RCP.
The ST Agent delivers task control parameters to an associated subsystem, which
returns a response value, indicating that task creation succeeds or fails.
In an opposite direction, the response message ret urns the data to a corresponding
client. The client may know whether task creation succeeds or fails.
The basic process of data reporting is as follows:
While processing a signaling, the RNLC checks whether this signaling satisfies the
filtering condition of the created task. If the signaling satisfies such conditions, the
subsystem will invok e the interface of the S T Agent to report signaling data to the ST
Manager.
The S T Manager reports the signaling to the client which creates a corresponding task.
The system provides the following S T functions:
UE-oriented S T, which uses an IMS I as the object and traces the signaling of UE at
the Iub, Uu, Iur, or Iu int erface
Common S T at the Iub interface, which uses Nodeb or a cell as the object
Common S T at the Iu interface, which may specify CS domain or PS domain
Multiple cell users tracing, that is, the system can trace a specified number of UE in
a specified cell. The reported signaling covers the Iub, Uu, Iur, and Iu interfaces.
The above ST is only used to trace high service protocol layer information. That is,
NBAP layer signaling is traced at the Iub interface; RA NAP signaling is traced at the Iu
interface; RRC lay er signaling is traced at the Uu interface; RASAP layer signaling is
traced at the Iur interface.
In addition, WRNC tracing provides service for two kinds of clients. One is RCT, which
provides all the above tracing functions. If accessed, the Call Trac e Server (CTS ),
together wit h other NEs, can implement whole-net work tracing. The CTS only supports
UE-oriented S T.
3.1.3
Online Analysis of Radio Performance

Online analysis of Radio Performance fully borrows the architecture and flow of ST. It is
different from the signaling trace system in a general sens e in that in online tracing, a
radio signaling control subsystem does not report the original signaling, but necessary
data extracted from t he signaling. The data display ed by the OMCR is not simple data
browse. The OMCR provides some more friendly display modes, such as curve
diagrams and forms, which makes it more convenient for users to analyze and browse.
Online tracing provides the following functions:
Table 3-1
Key Functions of Online Tracing
Traced
Object
UE
Tracing Type
Reported Content
Uplink power control

tracing
Current uplink power
Downlink power cont rol

tracing
Current downlink power
Uplink DCH link tracing
Quality of uplink DCH link, including

number of packets being sent and error
packets.
Outer loop power control

tracing
SIR of uplink
Service cell handover

status tracing
Cell active set, cell information of intrafrequency, inter-frequency or intersystem handover.
Cell
3.2
Code tree resource tracing
The code tree resource use of the

current cell
Downlink power cont rol

tracing
Downlink power of cell, including TCP,

NonHs TCP, and Hs RequiredP ower
RTWP tracing
RTWP of the current cell
CE resource tracing
UE resource use of the current cell

Neighboring cell monitoring is an optional function. When the Nb rCellMonSupInd is close,
the measurement ID11 cannot be opened, so this function is also disabled.
For the sake of description, neighboring cells of UE are categorized as follows:

1
Monitored set neighboring cells: They are configured for UE by means of the
neighboring cell list of measurement control messages.
Non-monitored set neighboring cells: Measurement control messages can only be

configured with 32 neighboring cells at most. When an active set includes multiple
cells, there may be more than 32 neighboring cells. Non-monitored set neighboring
cells refer to those configured for an OMC-R, but not for UE due t o the restriction of
air interface messages.
Neighboring cells which miss configuring: The neighboring cells which miss
configuring in an OMC-R.
To UE, non-monitored set neighboring cells and the neighboring cells which miss
configuring are all detected set neighboring cells. WRNC supports UE -triggered
detected set handover of measurement reports of non-monitored set neighboring cells,
and UE-triggered detected set statistics on the neighboring cells which miss configuring.
The RNC uses intra-frequency measurement ID1 for handover, including normal intrafrequency handover and detected set handover. The neighboring cells obtained from
event reporting of meas urement ID1, which plus active set cell times is handover times.
The RNC us es intra-frequency measurement ID11 for detected set statistics. To save
intra-frequency events, measurement ID11 includes 1A events only. 1A event
parameters, such as Reporting Range Constant and Hysteresis, can be s et to roughly
estimate how many times the neighboring cells which miss configuring are virtually
added to an active set. These times are called virt ual handover times. Set Reporting
deactivation threshold of meas urement ID11 as 6. Even if the active set is 3, 1A events
can be normally reported.
The event parameters in meas urement ID1 and those in measurement ID11 can be set
respectively. It is recommended to configure the event parameters as follows in order to
make the handover times related to measurement ID1 comparable to the virtual
handover times related to measurement ID11 and to facilitate the analysis of the
neighboring cells which miss configuring the priority:
R1a(ID1)-1/2H1a(ID1) = R1a(ID11)-1/2H1a(ID11)
(1)
R1b(ID1)+1/2H1b(ID1) = R1a(ID11)+ 1/2H1a(ID11)
(2)
The event1a criterion of measurement ID1 and measurement ID11 are same based on
the formulae (1) and (2) , refer to the following figures.
Figure 3-3
Measurement ID1 for Handover
Measurement
ID 1
Measurement
quantity
PCPICH1
R1a
H1a/2
Event 1A
Event 1A
R1b
PCPICH2
H1b/2
Event 1B
Time
Figure 3-4
Measurement ID11 for Detected Set Statistics
Measurement
ID 11
PCPICH1
Measurement
quantity
Event 1A
R1a
Event 1A
H1a/2
PCPICH2
Time
According to the equations (1) and (2), we can get

H1a (ID11) = R1b(ID1) - R1a(ID1) +1/2[H1b(ID1)+ H1a(ID1)]
R1a (ID11) = 1/2[R1a(ID1)+R1b(ID1)]+1/4[H1b(ID1)-H1a(ID1)]
Remarks:
1
The subscript in the brackets indicates the measur ement ID;
R1a the paramet er of " Reporting Range Constant" in E vent 1A. R1b indicates the
parameter of "Reporting Range Constant" in E vent 1B
H1a indicates the parameter of "Hysteresis" in E vent 1A. H1b indicates the
parameter of "Hysteresis" in Event 1B.
According to the above description, the trigger condition of E vent 1A in measurement

ID11 is equivalent to E vent 1A triggered in measurement ID1. In normal cases, the
threshold which triggers 1C is greater than that which triggers 1A. In measurement ID1,
if the cell which triggers a 1C event is used as the neighboring cell whic h fails to be
configured, it will necessarily trigger a 1A event first. Therefore, E vent 1A in
measurement ID11 is comparable to E vent 1A + E vent 1C in measurement ID1 and is
accurately matched with E vent 1A in measurement ID1. By comparing handover times
with virtual handover times, we can evaluate how important the neighboring cells which
miss configuring are to the configured neighboring cells. Meantime, we can optimize the
priority of the configured neighboring cells.
10
In actual applications, we first need to turn on the measurement task of detected set
monitor in the configuration interface. When UE enters CELL_DCH status, or the best
cell in UE active set changes, the RNC enables or disables the detected set
measurement of measurement ID11 according to the status of the detected set reporting
measurement task of the best cell. If the measurement set of measurement ID11 is
opened, the wireless control subsystem will report detected set information to the
operation and maint enance subsystem. Then, the operation and maintenance
subsystem reports the handover counter of the det ected set to the OMCR, which
processes the counter value.
For final analysis content, refer to the following table (interfaces slightly vary with
implementation):
Table 3-2
Name of
Neighbori
ng Cell
Typ
e1
Analysis of Neighboring Cell Monitoring
Handover/V
Handov
irtual
Handover
er
Handover
Handov Handov
Times of
Times/V
Times of
Scrambli
Monitored
er
er
irtual
Nonng code
set
Succe ss Failure
Handov
monitored
Ratio
Rate
Neighborin
er
set
g Cell
Times
Neighborin
g Cell
Handover
Ratio
Neig
hbor
Di stanc ing
e (km) Cell
Prio
rity
Configured
Handov
Scramblin
neighborin
er times
g code 1
g cell 1
1
Handover
times 1 of
monitored
set
neighboring
cell
Handover
times 1handover
times 1 of
monitored
set
neighboring
cell
1Handove
handove
r
r
success
success
ratio
ratio 1
Handover
times 1/
(handover
times
1+hando
ver times
m)
Distance
P1
1
Configured
Handov
Scramblin
neighborin
er times
g code 2
g cell 2
2
Handover
times 2 of
monitored
set
neighboring
cell
Handover
times 2handover
times 2 of
monitored
set
neighboring
cell
1Handove
handove
r
r
success
success
ratio
ratio 2
Handover
times 2/
(handover
times
1+hando
ver times
m)
Distance
P2
2
Configured
Handov
Scramblin
neighborin g code m er times
g cell m
m
Handover
times m of
monitored
set
neighboring
cell
Handover
times mhandover
times m of
monitored
set
neighboring
cell
1Handove
handove
r
r
success
success
ratio
ratio m
Handover
times m/
(handover
times
1+hando
ver times
m)
Distance
Pm
m
Neighborin Scramblin Virtual
Null
Null
Null
Null
Distance Pn
Null
11
Name of
Neighbori
ng Cell
Typ
e2
Handover/V
Handov
irtual
Handover
er
Handover
Handov Handov
Times of
Times/V
Times of
Scrambli
Monitored
er
er
irtual
Nonng code
set
Succe ss Failure
Handov
monitored
Ratio
Rate
Neighborin
er
set
g Cell
Times
Neighborin
g Cell
g cell which g code n

miss
configuring
(1)
handove
r times n
Neighborin
Virtual
g cell which Scramblin
handove
miss
g code
Null
r times
configuring n+1
n+1
(2)
Typ
e3
Handover
Ratio
Neig
hbor
Di stanc ing
e (km) Cell
Prio
rity
Null
Null
Null
Null
Distance Pn+
n+1
1
Neighborin
Virtual
g cell which
Scramblin
miss
handove Null
g code t
r times t
configuring
(t)
Null
Null
Null
Null
Distance
Pt
t
Neighborin
g cell which
Scramblin
0
miss
g code t
configuring
(t+1)
Null
Null
Null
Null
Null
Distance
Null
t+1
Neighborin
g cell which
Scramblin
0
miss
g code t
configuring
(t+2)
Null
Null
Null
Null
Null
Distance
Null
t+2
Null
Virtual
Scramblin handove
Null
g code w r times
w
Null
Null
Null
Null
Null
Null
Null
Virtual
Scramblin
handove
g code
Null
r times
w+1
w+1
Null
Null
Null
Null
Null
Null
Typ
e4
The longitudinal title column is described as follows:

1
Name of neighboring cell: site name of a cell, matched according to a cell ID or

scrambling code.
12
Handover times/ virtual handover times: soft handover (including softer handover)
radio link addition attempts in the measurement object reported by WRNC + intercell detected set statistics.
Handover times of monitored set neighboring cell: inter-cell monitored set handover
statistics of newly added counters in the meas urement objects reported by WRNC.
Handover success ratio: soft handover (including softer handover) radio link
addition success times in the measurement object reported by WRNC/soft handover
(including softer handover) radio link addition attempts.
Handover ratio: It refers to the ratio of the handover times of a monitored set or nonmonitored set cell to the total handover times of all monitored set or non -monitored
set cells.
Distance: It is calculat ed according to on the latitude and longitude of neighboring

cells and source cells.
Neighboring cell priority: For a monitored set or non-monitored set cell, neighboring
cell priority comes from database configuration. For a det ected set cell, the system
automatically generates a recommended priority during report formulation according
to the virtual handover times of the cell.
Traverse records are classified as follows:

1
Type 1: It refers to the neighboring cells configured for UE by means of an OMC -R,
including monit ored set neighboring cells and non-monitored set neighboring cells.
This type of neighboring cells can be handed over. Therefore, we can calculate the
handover success ratio, handover failure rat e, and handover ratio by means of a
performance measurement counter. The neighboring cell priority of Ty pe 1 is
configured by means of an OMC-R. Only this type of neighboring cells can be
handed over. Handover times of monitored set neighboring cell and monitored s et
handover times are provided for this type of neighboring cells.
Type 2: It refers to the neighboring cells which miss configuring and the only
matched cell queried from a database according to the scrambling code reported by
WRNC. The virt ual handover time of this type of neighboring cells is obtained from
detected set tracing statistics. The neighboring cell priority of Type 2 is a
recommended priority, which is automatically generated by the s ystem according to
the relative relationship between the virtual handover times and handover times.
Type 3: It refers to the neighboring cells which miss configuring and multiple
matched cells queried from a database according to the scrambling code report ed
by WRNC. This type indicates that scrambling code is multiplexed. When reports
are generated, all matched cells will be dis played. These cells have the same
scrambling code. Detected set tracing statistics serves as the virtual handover times
of the cell (among these cells with scrambling code multiplexing) which is the
nearest to the source cell. The virtual handover times of other cells with scrambling
13
code multiplexing is 0, whic h indicates that the system makes calculations and
recommends the nearest cell to be the neighboring cell which misses configuring.
The neighboring cell priority of Type 3 is a recommended priority, which is
automatically generated by the system according to the relative relationship
between the virt ual handover times and hando ver times.
4
1.1
Type 4: It indicates that some cells cannot be matched according to a reported

scrambling code. These cells may not belong to this network or may be interfering
signal. Cell information cannot be obtained; therefore, cell name and distance
cannot be obtained, either. We can only record their virtual handover times.
Measurement Report Record

Measurement Report includes the following information:
1
MR-UE coverage measurement

i
E vent handover measurement report: UE intra-frequency/ inter-frequency

/inter-rat measurement report
ii
E vent traffic volume measurement report: UE traffic volume measurement

report
iii
E vent internal measurement report: UE transmitted power measurement report
iv
Period handover measurement report: UE intra-frequency measurement report
Period internal measurement report: UE transmitted power measurement

report
vi
Period quality measurement report: UE DL DCH BLE R measurement report,

RNLU UL DCH BLER measurement report
MR-UE Location Measurement (Only one can be supported at the same time):
i
UEB AGPS, which need UE which support this feature,..
ii
CELL-ID+ RTT
MR Acquisition s Architecture is as following:
14
Figure 3-5
MRs Architecture
SBCX
RCP
MR
Forwar
ding
RNLC
MR Control
Table
MR
Saving
Module
MR Data File
ROMP
MR Control
Table
The basic function flow is as following:

1
The user set parameter of MR Acquisition by OMC;
ROMP get the paramet er in the MR control table and forward them to the RCP ;
The RNLC s ubsystem get the parameter and control the meas urement report of
UE/Nodeb by them. UE/Nodeb send t he MR to the RNLC and then RNLC send
them to the MR Forwarding module;
MR Forwarding module send MR to the MR Saving module on the SBCX;
MR Saving module saves the data as MR data file.
Other tool can get the MR data files on the SBCX by FTP for other purpose.
Parameters and Configuration
4.1

N/A
15
4.2
4.2.1
Parameter List
No.
Abbreviated name
Parameter name
NbrCellMonSupInd
Neighboring Cell Monitoring Support Indicator
RptRange
Reporting Range Constant for E vent 1A/1B
Hysteresis
Hysteresis
4.2.2
Parameter Configuration
4.2.2.1
Neighboring Cell Monitoring Support Indicator
OMC Path
Interface Path: View->Configuration Management ->RNC NE-> RNC Radio Res ource
Management-> RNC Configuration Supplement Parameters-> Neighbouring Cell
Monitoring Support Indicator
0: Not supported. The neighboring-cell-monitoring function is disabled.

1:.Suport ed. The neighboring-cell-monitoring function is enabled.
4.2.2.2
Reporting Range Constant for Event 1A/1B
OMC Path
Path:
View->Configuration
Management-> RNC
NE-> RNC
Radio
Res ource
Management-> Modify Advanced Parameter->UE Intra-frequency Measurement
Configuration->Reporting Range Constant E vent 1A/1B (dB)
The wider the reporting range of E vent 1a is, the easier E vent 1a is to be triggered; the
narrower the reporting range is, the more difficult E vent 1a is to be triggered.
The narrower the reporting range of E ven 1b is, the easier E ven 1b is to be triggered;
the wider the reporting range is, the more diffic ult Even 1 b is to be triggered.
4.2.2.3
Hysteresis (Intra)
OMC Path
16
Path:
View->Configuration
Management-> RNC
NE-> RNC
Radio
Res ource
Management-> Modify Advanced Parameter->UE Intra-frequency Measurement
Configuration-> Hysteresis
This paramet er indicates the hysteresis for judging whether an event satisfies trigger
conditions. It serves to avoid the trigger status change due to very small change. This
parameter is related to the measurement quantity and the event type.
To reduce the hysteresis, you may increase the probability of reporting corresponding
events; to increase the hysteresis, you may decrease the probability of event reporting.
4.3
Measurement Report
4.3.1
Parameter List
No.
4.3.1.1
Abbreviated name
Parameter name
MrSwitch
MR Function Switch
MrUeMeas TypeS wit
MR-UE Measurement Type S witch
MrUeMeasRpt Int
MR-UE Measurement Reporting Interval
MrUeMeasRpt TrMod
MR-UE Measurement Report Trans fer Mode
MrUeLocMeaRpt Int
MR-UE Location Measurement Reporting

Interval(ms)
MrUeMeasSwit
MR-UE Measurement Switch
MR Function Switch
OMC Path
View-> Configuration Management->RNC NE ->RNC Radio Resource Management>Advanced Parameter Manager-> RNC Radio Resourc e Management->MR Function
Switch
This parameter will decide whether the MR should be collected. If this parameter is set to
closed, all the other parameter about the MR Acquisition will not take effect.
4.3.1.2
MR-UE Measurement Type Switch
OMC Path
View-> Configuration Management->RNC NE ->RNC Radio Resource Management>Advanced P arameter Manager->RNC Radio Resource Management->MR-UE
Measurement Ty pe Switch
17
This Parameter defines which type of MR-UE should be collected:
4.3.1.3
Power Meas urement Type S witch
Quality Measurement Type Switch
Location Measurement Type Switch
MR-UE Measurement Reporting Interval
OMC Path
Measurement Reporting Interval(ms)
This parameter defines the MR-UEs reporting interval.
4.3.1.4
MR-UE Location Measurement Reporting Interval
OMC Path
View-> Configuration Management-> RNC NE ->RNC Radio Resourc e Management->

Modify Advanced Parameter->RNC Radia Resource Management ->MR-UE Location
Measurement Reporting Interval
This parameter defines the MR-UEs Location reporting interval.
4.3.1.5
MR-UE Measurement Report Transfer Mode
OMC Path
Measurement Report Trans fer Mode
This parameter defines the MR-UEs reporting Trans fer Mode.
4.3.1.6
MR-UE Measurement Switch
OMC Path
View-> Configuration Management->RNC NE ->RNC Radio Resource Management>UltranCell->UltranCellXXX->Advanced Paramet er Manager-> UTRAN Cell ->MR-UE
Measurement Switch
18
This parameter defines whether the MR report should be collected in the preferred cell.
Counter And Alarm
4.4
Counter List
4.4.1

None.
4.4.2
4.5
Neighbouring Cell Monitoring

Counter ID
The Description
C310880137
Number of attempted radio link addition

for soft handover(including softer
handover) between cells
C310880138
Number of Successful radio link addition

for soft handover(including softer
handover) between cells
C310880167
Statistics of soft handover bet ween cells

for monitor set
C310910200
Number of detected set cell can be

added in active set
Measurement Ty pe
Statistics of soft handover

between cells
Statistics of detected set
Alarm List
None.
Glossary
None.
19

ZTE UMTS RAN Perfomance Monitor Feature Guide

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ZTE UMTS RAN Perfomance Monitor Feature Guide

Caricato da

Copyright:

Formati disponibili

Operator Logo

RAN Performance Monitor

RAN Performance Monitor Feature Guide

RAN Performance Monitor Feature Guide

2010 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

RAN Performance Monitor Feature Guide

Parameters and Configuration ........................................................................ 15

Counter And Alarm ........................................................................................... 19

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

RAN Performance Monitor Feature Guide

Measurement ID1 for Handover............................................................................. 9

Measurement ID11 for Detected Set Statistics.................................................... 10

MRs Architecture ................................................................................................. 15

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

RAN Performance Monitor Feature Guide

System Data Acquisition

RRC establishment success rate and RAB establishment s uccess rate

Call blocking rate and call drop rate of CS/PS

Throughput and bandwidth utilization ratio of Iu/ Iub/Iur interface

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

RAN Performance Monitor Feature Guide

Traffic and flow of RNC/cell

Cell load level, utilization ratio of code resource

E1/IMA link performance statistics, AAL5/AAL2 performance statistics

IP performance statistics of Ethernet port, etc.

Online analysis of Radio Performance

Neighboring Cell Monitoring

The neighboring cells that misses configuring.

The excessive neighboring cells that is configured.

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

RAN Performance Monitor Feature Guide

The neighoring cells with specific handover priority

Meaturement Report Record

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

RAN Performance Monitor Feature Guide

System Data Collection

Performance Data Collection

Data collection: collect and summarize the counter values .

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

RAN Performance Monitor Feature Guide

System Architecture of Performance Statistics

The basic process of performance data collection and reporting is as follows:

Signaling Tracing (ST)

Task control (including creating or deleting a tracing task)

Data reporting (report the signaling which satisfies task conditions to a

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

RAN Performance Monitor Feature Guide

The basic architecture of S T is as follows:

The basic process of task control is as follows:

ZTE Confidential Proprietary

2010 ZTE Corporation. All rights reserved.

RAN Performance Monitor Feature Guide

Common S T at the Iu interface, which may specify CS domain or PS domain

Online Analysis of Radio Performance

Key Functions of Online Tracing