ZTE UMTS RAN Perfomance Monitor Feature Guide

8/19/2019 ZTE UMTS RAN Perfomance Monitor Feature Guide

1/23

RAN Performance MonitorWCDMA RAN

Feature Guide

Operator Logo


2/23

RAN Performance Monitor Feature Guide

ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. I


Version Date Author Approved By Remarks

V4.5 2010-10-15Zenglingling

WangSuShen

© 2010 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to bedisclosed 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.


3/23


ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. II

TABLE OF CONTENTS

1 Functional Attributes.......................................................................................... 1

2 Overview .............................................................................................................. 1

2.1 Function Introduction ............................................................................................ 1 2.1.1 System Data Acquisition ....................................................................................... 1 2.1.2 Neighboring Cell Monitoring ................................................................................. 2 2.1.3 Meaturement Report Record ................................................................................ 3

3 Technical Description......................................................................................... 4

3.1 System Data Collection ........................................................................................ 4 3.1.1 Performance Data Collection................................................................................ 4 3.1.2 Signaling Tracing (ST) .......................................................................................... 5

3.1.3 Online Analysis of Radio Performance................................................................. 7 3.2 Neighboring Cell Monitoring ................................................................................. 8 1.1 Measurement Report Record ............................................................................. 14

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

4.1 System Data Acquisition ..................................................................................... 15 4.2 Neighboring Cell Monitoring ............................................................................... 16 4.2.1 Parameter List ..................................................................................................... 16 4.2.2 Parameter Configuration..................................................................................... 16 4.3 Measurement Report .......................................................................................... 17 4.3.1 Parameter List ..................................................................................................... 17

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

4.4 Counter List ......................................................................................................... 19 4.4.1 System Data Acquisition ..................................................................................... 19 4.4.2 Neighbouring Cell Monitoring ............................................................................. 19 4.5 Alarm List ............................................................................................................ 19

3 Glossary ............................................................................................................. 19


4/23


ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. III

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 MR’s Architecture ................................................................................................. 15

TABLES

Table 3-1 Key Functions of Online Tracing ............................................................................. 7

Table 3-2 Analysis of Neighboring Cell Monitoring ............................................................... 11


5/23


ZTE Confidential Proprietary © 2010 ZTE Corporation. All rights reserved. 1

1 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]

2 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 -network

users' call and service process. According to these records, we may customize

from an OMCR the output reports which include the following KPIs:

RRC establishment success rate and RAB establishment success rate

Call blocking rate and call drop rate of CS/PS

Soft handover success ratio, hard handover success ratio, and Inter-RAT

handover success ratio

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


6/23



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 fewneighboring cells, or a wrong neighboring cell relationship will result in severe call drop.

The neighboring relationship between 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 there exists

overlapped coverage.

The excessive neighboring cells that is configured.

By checking the handover times and success ratio of UE between cells, 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.


7/23



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 measurement, service traffic 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, RSCP,

and Ec/N0 information, and displays the information in a geographic way. Through the

MR data, you can know the area of weak coverage or no coverage and give suggestions

of adding more base stations.

The MR based data 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 based statistical analysis allows you to know the RSCP and Ec/N0coverage and interference o f 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).


8/23



3 Technical Description

3.1 System Data Collection

3.1.1 Performance Data Collection

Performance management is one main management function of a telecommunication

management network. 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 fromvarious network units to implement network performance management. They also

confirm the physical and logical allocation of network, 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.

2 Data reporting: In each data collection granularity, data is collected and all counter

values are sent in the form of messages to an SBCX. The SBCX saves data as a

corresponding file so that an OMCR can read it.The basic architecture of the PM module is as follows:


9/23



Figure 3-1 System Architecture of Performance Statistics

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 theshared 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 SBCX, which saves it as performance file s.

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 ST task f rom

an RCT or CTS. The operation and maintenance subsystem works with the radio

subsystem to report the signaling which satisfies user-specified conditions to a

corresponding c lient. The key functions of ST are as follows:

1 Task control (including creating or deleting a tracing task)

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

corresponding client)

Legend: Counter query

message stream

Legend: Data stream

Legend: Active and standbydata area switching

ROMP

PM ManagerPMAgent

datasnapshot

area

shareddataarea

RNLCetc.

measurementdata

buffer

Transport

Module

SBCX

Performance File

OMC-R


10/23



The basic architecture of ST is as follows:

Figure 3-2 System Architecture of ST

The basic process of task control is as follows:

The CTS creates a tracing task by means of an OMM forwarding subsystem or an ST

Tool.

Both the clients deliver task parameters to the ST Manager.

The ST Manager checks the parameters, for example, whether there are too many tasks.

If the parameters are suitable, the ST manager delivers task data to the ST 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 returns 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 invoke the interface of the ST Agent to report signaling data to the ST

Manager.

The ST Manager reports the signaling to the client which creates a corresponding task.

The system provides the following ST functions:

RCT

ROMP

ST

Manager

ST Agent

OMM

Forwarding CTS ST Agent

Control

Message

Data

Message

RNLC

RNLC

peripheral board

peripheral board


11/23



1 UE-oriented ST, which uses an IMSI as the object and traces the signaling of UE at

the Iub, Uu, Iur, or Iu interface

2 Common ST at the Iub inter face, which uses Nodeb or a cell as the object

3 Common ST at the Iu interface, which may speci fy CS domain or PS domain

4 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; RANAP signaling is traced at the Iu

interface; RRC layer 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, whichprovides all the above tracing functions. If accessed, the Call Trace Server (CTS),

together with other NEs, can implement whole-network tracing. The CTS only supports

UE-oriented ST.

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 sense in that in online tracing, a

radio signaling control subsystem does not report the original signaling, but necessary

data extracted from the signaling. The data displayed by the OMCR is not simple databrowse. 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

TracedObject

Tracing Type Reported Content

UE

Uplink power control

tracing Current uplink power

Downlink power controltracing

Current downlink power

Uplink DCH link tracing

Quality of uplink DCH link, including

number of packets being sent and errorpackets.

Outer loop power controltracing

SIR of uplink

Service cell handoverstatus tracing

Cell active set, cell information of intra-

frequency, inter-frequency or inter-system handover.


12/23



Cell

Code tree resource tracingThe code tree resource use of thecurrent cell

Downlink power controltracing

Downlink power of cell, including TCP,NonHsTCP, and HsRequiredPower

RTWP tracing RTWP of the current cell

CE resource tracing UE resource use of the current cell

3.2 Neighboring Cell MonitoringNeighboring cell monitoring is an optional function. When the NbrCellMonSupInd 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.

2 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 to the restriction of

air interface messages.

3 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 intra-

frequency handover and detected set handover. The neighboring cells obtained from

event reporting o f measurement ID1, which plus active set cell times is handover times.

The RNC uses 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 set to roughly

estimate how many times the neighboring cells which miss configuring are virtually

added to an active set. These times are called virtual handover times. Set Reporting

deactivation threshold of measurement ID11 as 6. Even if the active set is 3, 1A events

can be normally reported.

The event parameters in measurement 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:


13/23



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

Event 1AR 1a Event 1AH1a/2

R 1b

H1b/2

Event 1B

PCPICH1

Time

Measurement

quantity

Measurement

ID 1

PCPICH2


14/23



Figure 3-4 Measurement ID11 for Detected Set Statistics

Event 1AR 1a Event 1A

H1a/2

PCPICH1

Time

Measurement

quantity

Measurement

ID 11

PCPICH2

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 measurement ID;

2 R1a the parameter of "Reporting Range Constant " in Event 1A. R1b indicates the

parameter of "Reporting Range Constant" in Event 1B

3 H1a indicates the parameter of "Hysteresis" in Event 1A. H1b indicates the

parameter o f "Hysteresis" in Event 1B.

According to the above description, the trigger condition of Event 1A in measurementID11 is equivalent to Event 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 which fails to be

configured, it will necessarily trigger a 1A event first. Therefore, Event 1A in

measurement ID11 is comparable to Event 1A + Event 1C in measurement ID1 and is

accurately matched with Event 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.


15/23



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 o f measurement ID11 according to the status o f 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 maintenance subsystem. Then, the operation and maintenance

subsystem reports the handover counter of the detected 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 Analysis of Neighboring Cell Monitoring

Name of

Neighboring Cell

Scrambling code

Handov

erTimes/V

irtualHandov

erTimes

Handover

Times ofMonitored

set

Neighboring Cell

Handover/V

irtualHandoverTimes of

Non-monitored

set

Neighboring Cell

Handov

erSuccess

Ratio

Handov

erFailure

Rate

HandoverRatio

Distance (km)

Neig

hbor ingCell

Priority

Type 1

Configured

neighboring cell 1

Scrambling code 1

Handov

er times1

Handover

times 1 ofmonitored

setneighboringcell

Handover

times 1-

handovertimes 1 of

monitoredsetneighboringcell

Handover

successratio

1-handoversuccessratio 1

Handover

times 1/∑(handovertimes1+…handover timesm)

Distance1

P1

Configured

neighboring cell 2

Scrambling code 2

Handov

er times2

Handover

times 2 ofmonitored

setneighboring

cell

Handover

times 2-handovertimes 2 of

monitoredset

neighboringcell

Handove

r

successratio

1-

handoversuccessratio 2

Handover

times 2/∑(handovertimes1+…handover times

m)

Distance2

P2

… … … … … … …

Configured

neighboring cell m

Scrambling code m

Handov

er timesm

Handover

times m ofmonitoredset

neighboringcell

Handover

times m-

handovertimes m ofmonitored

setneighboringcell

Handove

rsuccessratio

1-

handove

rsuccessratio m

Handover

times m/∑(handover

times1+…handover timesm)

Distancem

Pm

Neighborin Scramblin Virtual Null Null Null Null Null Distance Pn


16/23



Name of

Neighboring Cell

Scrambling code

Handov

er

Times/Virtual

Handov

erTimes

Handover

Times of

Monitoredset

Neighboring Cell

Handover/V

irtualHandover

Times ofNon-

monitored

setNeighborin

g Cell

Handov

erSuccess

Ratio

Handov

erFailure

Rate

HandoverRatio

Distance (km)

Neig

hbor

ingCellPriority

Type 2

g cell whichmiss

configuring(1)

g code n handover times n

n

Neighborin

g cell whichmiss

configuring(2)

Scramblin

g coden+1

Virtual

handove

r timesn+1

Null Null Null Null NullDistance

n+1

Pn+

1

… … … … … … …

Type 3

Neighborin

g cell whichmissconfiguring(t)

Scrambling code t

Virtual

handover times t

Null Null Null Null NullDistancet

Pt

Neighborin

g cell whichmiss

configuring(t+1)

Scrambling code t

0 Null Null Null Null NullDistancet+1

Null

Neighborin

g cell whichmissconfiguring(t+2)

Scrambling code t

0 Null Null Null Null NullDistancet+2

Null

… … … … … … …

Type 4

NullScrambling code w

Virtual

handover timesw

Null Null Null Null Null Null Null

Null

Scramblin

g codew+1

Virtual

handover timesw+1

Null Null Null Null Null Null Null

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.


17/23



2 Handover times/ virtual handover times: soft handover (including softer handover)

radio link addition attempts in the measurement object reported by WRNC + inter-

cell detected set statistics.

3 Handover times of monitored set neighboring cell: inter-cell monitored set handover

statistics of newly added counters in the measurement objects reported by WRNC.

4 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.

5 Handover ratio: It refers to the ratio of the handover times of a monitored set or non-

monitored set cell to the total handover times of all monitored set or non-monitored

set cells.

6 Distance: It is calculated according to on the latitude and longitude of neighboring

cells and source cells.

7 Neighboring cell priority: For a monitored set or non-monitored set cell, neighboring

cell priority comes from database configuration. For a detected 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 monitored 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 rate, and handover ratio by means of a

performance measurement counter. The neighboring cell priority of Type 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 set

handover times are provided for this type of neighboring cells.

2 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 virtual 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.

3 Type 3: It refers to the neighboring cells which miss configuring and multiple

matched cells queried from a database according to the scrambling code reported

by WRNC. This type indicates that scrambling code is multiplexed. When reports

are generated, all matched cells will be displayed. 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


18/23



code multiplexing is 0, which 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 virtual handover times and handover times.

4 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.

1.1 Measurement Report Record

Measurement Report includes the following information:

1 MR-UE coverage measurement

i Event handover measurement report: UE intra-frequency/ inter-frequency

/inter-rat measurement report

ii Event traffic volume measurement report: UE traffic volume measurement

report

iii Event internal measurement report: UE transmitted power measurement report

iv Period handover measurement report: UE intra-frequency measurement report

v Period internal measurement report: UE transmitted power measurement

report

vi Period quality measurement report: UE DL DCH BLER measurement report,

RNLU UL DCH BLER measurement report

2 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:


19/23



Figure 3-5 MR’s Architecture

RNLC

MR

Forwar

ding

MR

Saving

Module

SBCXRCP

MR Control

Table

ROMP

MR Control

Table

MR Data File

The basic function flow is as following:

1 The user set parameter of MR Acquisit ion by OMC;

2 ROMP get the parameter in the MR control table and forward them to the RCP;

3 The RNLC subsystem get the parameter and control the measurement report of

UE/Nodeb by them. UE/Nodeb send the MR to the RNLC and then RNLC send

them to the “MR Forwarding” module;

4 “MR Forwarding” module send MR to the “MR Saving module” on the SBCX;

5 “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.

4 Parameters and Configuration

4.1 System Data Acquisition

N/A


20/23



4.2 Neighboring Cell Monitoring

4.2.1 Parameter ListNo. Abbreviated name Parameter name

1 NbrCellMonSupInd Neighboring Cell Monitoring Support Indicator

2 RptRange Reporting Range Constant for Event 1A/1B

3 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 Resource

Management-> RNC Configuration Supplement Parameters-> Neighbouring Cell

Monitoring Support Indicator

Parameter Configuration

0: Not supported. The neighboring-cell-monitoring function is disabled.

1:.Suported. 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 Resource

Management-> Modify Advanced Parameter->UE Intra-frequency Measurement

Configuration->Reporting Range Constant Event 1A/1B (dB)


The wider the reporting range of Event 1a is, the easier Event 1a is to be triggered; the

narrower the reporting range is, the more difficult Event 1a is to be triggered.

The narrower the reporting range of Even 1b is, the easier Even 1b is to be triggered;

the wider the reporting range is, the more difficult Even 1b is to be triggered.

4.2.2.3 Hysteresis (Intra)

OMC Path


21/23



Path: View->Configuration Management->RNC NE->RNC Radio Resource

Management-> Modify Advanced Parameter->UE Intra-frequency Measurement

Configuration-> Hysteresis


This parameter 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 ListNo. Abbreviated name Parameter name

1 MrSwitch MR Function Switch

2 MrUeMeas TypeSwit MR-UE Measurement Type Switch

3 MrUeMeasRptInt MR-UE Measurement Reporting Interval

4 MrUeMeasRptTrMod MR-UE Measurement Report Transfer Mode

5 MrUeLocMeaRptIntMR-UE Location Measurement ReportingInterval(ms)

6 MrUeMeasSwit MR-UE Measurement Switch

4.3.1.1 MR Function Switch

OMC Path

View->Configuration Management->RNC NE->RNC Radio Resource Management-

>Advanced Parameter Manager->RNC Radio Resource 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


>Advanced Parameter Manager->RNC Radio Resource Management->MR-UE

Measurement Type Switch



22/23



This Parameter defines which type of MR-UE should be collected:

1 Power Measurement Type Switch

2 Quality Measurement Type Switch

3 Location Measurement Type Switch

4.3.1.3 MR-UE Measurement Reporting Interval

OMC Path



Measurement Reporting Interval(ms)


This parameter defines the MR-UE’s reporting interval.

4.3.1.4 MR-UE Location Measurement Reporting Interval

OMC Path

View->Configuration Management->RNC NE->RNC Radio Resource Management->

Modify Advanced Parameter->RNC Radia Resource Management->MR-UE Location

Measurement Reporting Interval


This parameter defines the MR-UE’s Location reporting interval.

4.3.1.5 MR-UE Measurement Report Transfer Mode

OMC Path



Measurement Report Transfer Mode

Parameter ConfigurationThis parameter defines the MR-UE’s reporting Transfer Mode.

4.3.1.6 MR-UE Measurement Switch

OMC Path


>UltranCell->UltranCellXXX->Advanced Parameter Manager->UTRAN Cell->MR-UE

Measurement Switch



23/23



This parameter defines whether the MR report should be collected in the preferred cell.

2 Counter And Alarm

4.4 Counter List

4.4.1 System Data Acquisition

None.

4.4.2 Neighbouring Cell MonitoringCounter ID The Description Measurement Type

C310880137

Number of attempted radio link addition

for soft handover(including softerhandover) between cells

Statistics of soft handoverbetween cellsC310880138

Number of Successful radio link addition

for soft handover(including softerhandover) between cells

C310880167Statistics of soft handover between cellsfor monitor set

C310910200Number of detected set cell can beadded in active set

Statistics of detected set

4.5 Alarm List

None.

3 Glossary

None.

ZTE UMTS RAN Perfomance Monitor Feature Guide

Documents

Transcript of ZTE UMTS RAN Perfomance Monitor Feature Guide