Umts Radio Network Kpi-108

UMTS Radio Network KPI
ZTE University
Content
 KPI Classification
 RAN KPI Definition and Measurement
 KPI Optimization
 KPI monitor
 KPI Case study
KPI Overview
 NetNumen™M31 (RAN) Mobile Network Element
Management System is ZTE Element Management
System of operation and management for one or more
NEs. (FM, PM, CM)
 Performance Monitor (according to the importance and
usage):
 KPI
 PI: Performance Indicator
 SPI: statistical performance indicator: with statistical rule such as
call completion rate>95%.
 Customized performance index
 EMS KPI Monitor Tools:
 Performance management
 Fault Management
 Configuration Management
RAN KPI Category
Coverage Class Mobility Class
Capacity Class
 Coverage Probability  RNC Soft Handover Success
 CS Capacity rate
 PS Capacity  Inter-Frequency Hard
 Cell UL Load Factor Handover Success rate
 Block Call rate  Inter-RAT Hard Handover
 … Success rate (CS domain and
PS domain)
…
QoS Class
RAN KPI Class
Resource Usage Class
 RRC Establishment success rate
 Trouble Cell rate  RAB Establishment success rate
 Busy Cell rate  Radio Access Success Rate
 Sleeping Cell rate  Call drop rate
 …  Average UL/DL Throughput
 RTT Ping with 32 Bytes
…
Content
 KPI monitor
 KPI Case study
Coverage Probability
Indicator Indicator Indicator
Signaling Flow
Description Definition Extension
 Statistic Period：－
 Statistic Area：Clutter-wise
 Indoor or Outdoor：BOTH
 Measurement Methods：DT or CQT
 Index Meaning：The coverage probability reflects the RF coverage

strength and RF signal quality.
Coverage Probability

Signaling Flow
Downlink: F=RSCP > R & Ec/Io > S
Uplink: TxPwr < T
Coverage Probability is defined as the percentage of the samples

whose F=1 for all the measured samples
(Note：Unreasonable samples are not included）
R and S are different for different services

RRC Establishment Success Rate
Signaling Flow
 Statistic Period :15 Mins, 30 Mins,1 Hour…. 1Day….
 Statistic Area ：cell-wise
 Indoor or Outdoor：BOTH
 Measurement Method：calculate based on the OMC Counters’

value
 Indicator Meaning：this indicator reflects the accessibility of the

Cell

Signaling Flow
＝RRC Connection Setup Complete Times

/RRC Connection Request Times×100%
Signaling Flow
UE RNC CN
RRC Connection Setup
RRC Connection Request Request Times
RRC Connection Complete Complete Times
DT Message Exchange
RAB Assignment Request
Radio Bearer Setup Established
Radio Bearer Setup Complete

RAB Assignment Response
RAB Establishment Success Rate
Signaling Flow
 Statistic Period : 15 Mins, 30 Mins,1 Hour…. 1 Day….
 Statistic Area: RNC & Cell-wise
 Indoor or Outdoor: BOTH
 Measurement Method: calculate based on the OMC Counters’

value
 Indicator Meaning: RAB assignment is the last step of the service

connection. If it is successfully assigned, the connection to the
User Panel is Successfully Setup

Signaling Flow
RAB Establishment Success rate
＝（CS RAB Assignment Success Times

+PS RAB Assignment Success Times）
/(CS RAB Assignment Request Times
＋PS RAB Assignment Request Times）×100%
Signaling Flow
UE RNC CN
RRC Connection Request

RRC Connection Complete
DT Message Exchange RAB Assignment

Request Times

RAB Assignment
Radio Bearer Setup Complete Success Times
RAB Assignment Response

Signaling Flow
 CS RAB Establishment Success rate

 PS RAB Establishment Success rate
 AMR RAB Establishment Success rate
 CS C 64/64 RAB Establishment Success rate
 PS I 64/64 RAB Establishment Success rate
 ……
Radio Access Success Rate
Signaling Flow
 Statistic Period: 15 Mins, 30 Mins, 1 Hour…. 1 Day….
 Statistic Area: Cell-wise
 Measurement Method: calculate based on the OMC counters’

value
 Indicator Meaning: this indicator reflects the accessibility of the

service of the Cell
Signaling Flow
Call Setup Success Rate
＝RRC Establishment Success Rate (Service Related)

×RAB Establishment Success rate×100%
Signaling Flow
UE RNC CN
RRC Connection Setup RRC Establishment

RRC Connection Complete Success Rate
DT Message Exchange

RAB
Radio Bearer Setup Complete Establishment
RAB Assignment Response Success Rate

Signaling Flow
 AMR Call Setup Success rate

 CS C 64/64 Call Setup Success rate
 PS I 64/64 Call Setup Success rate
 PS S 64/64 Call Setup Success rate
 ……
Call Drop Rate
Signaling Flow
 Statistic Period: 15 Mins, 30 Mins, 1 Hour…. 1Day….
 Statistic Area: RNC & Cell-wise

 Measurement Method: calculate based on the OMC Counters’

value
 Indicator Meaning: this indicator reflects the Retainability of the

network, it is one of the most important indicators of the
customer’s experience.
Call Drop Rate
Signaling Flow
Call Drop Rate
＝（RNC Triggered CS RAB Release Number

＋RNC Triggered PS RAB Release Number）
/(Total RAB Release number for CS
+ Total RAB Release number for PS)
×100%
Call Drop Rate
Signaling Flow
RNC Triggered RAB

Release Times
RNC CN
RAB
RELEASE REQUEST
Call Drop Rate

Signaling Flow
 CS Call Drop rate

 PS Call Drop rate
 AMR Call Drop rate
 CS C 64/64 Call Drop rate
 PS 64/64 Call Drop rate
 ……
Call Blocking Rate
Signaling Flow
 Statistic Period: 15 Mins, 30 Mins, 1 Hour…. 1Day
 Statistic Area: Cell-wise

 Measurement Method: calculate based on the OMC Counters’ value
 Indicator Meaning: Rate of blocked calls due to resource shortage.

This index partially reflects the degree of congestion in the cell.
Call Blocking Rate

Signaling Flow
Call Blocking Rate
The number of blocked calls

＝
/ The number of call admission requests Times×100%
Soft Handover Success Rate

Signaling Flow
 Statistic Period: 15 Mins, 30Mins, 1Hour…. 1Day

 Statistic Area: RNC-wise

value
 Indicator Meaning: this indicator reflects the soft handover

mobility in the RNC control area.

Signaling Flow
＝（Soft Handover Attempted Times

－Soft Handover Failure Times）
/Soft Handover Attempted Times×100%
Signaling Flow
UE Success flow UTRAN
ACTIVE SET UPDATE

Soft Handover
A Attempted Times
ACTIVE SET UPDATE COMPLETE
B
UE Failure Flow UTRAN
Soft Handover Failure Times.

ACTIVE SET UPDATE
A
ACTIVE SET UPDATE FAILURE

B

Signaling Flow
 Configuration unsupported failure caused handover failure rate

 Physical channel failure caused handover failure rate
 Incompatible simultaneous reconfiguration caused handover
failure rate
 Protocol error caused handover failure rate
 Cell update occurred caused handover failure rate
 Invalid configuration caused handover failure rate
 No reply caused handover failure rate
 ……
Inter-Frequency Hard Handover Success Rate

Signaling Flow
 Statistic Period: 15Mins, 30Mins, 1Hour…. 1Day

 Statistic Area: cell-wise

value
 Indicator Meaning: this indicator reflects the hard handover

mobility in the RNC control area.
Signaling Flow
＝（Inter-Frequency Hard Handover Attempted Times

－ Inter-Frequency Hard Handover Failure Times ）
/ Inter-Frequency Hard Handover Attempted Times ×100%
Inter-Frequency Hard Handover should Include

Intra-RNC Hard Handover and Inter-RNC Hard Handover
Signaling Flow
UE Success Flow SRNC
Inter-frequency hard
PHYSICAL CHANNEL RECONFIGURATION handover Attempted times
Intra-RNC
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
Inter-Frequency
Hard Handover
Flow
UE Failure Flow SRNC
PHYSICAL CHANNEL RECONFIGURATION
Inter-frequency hard
PHYSICAL CHANNEL RECONFIGURATION FAILURE
handover failure times
Node B Node B
UE Drift RNS Serving RNS Drift RNC Serving RNC MSC/SGSN
Decision to execute
Hard Handover
[A1] Relocation
Required
RANAP RANAP
[A2]
RANAP Relocation Request RANAP
Radio Link Setup
Inter-RNC
NBAP NBAP
Radio Link Setup Response
NBAP NBAP
Inter-Frequency RANAP
Relocation Request Ack.
RANAP
Relocation
Hard Handover RANAP
Command
RANAP
Physical Channel Reconfiguration
Flow RRC
Radio Link Restore Indication
RRC
Sent from SRNC
NBAP NBAP
Relocation Detect
RANAP RANAP
Physical Channel Reconfiguration Complete

RRC RRC
[B2] Relocation Complete Feedback to DRNC

RANAP RANAP
UE Mobility Information
RRC RRC
UE Mobility Information CONFIRM [B1] Iu Release

RRC RRC
Command
RANAP RANAP
Iu Release
Complete
RANAP RANAP
Radio Link Deletion Request

NBAP NBAP
Radio Link Deletion Response
NBAP NBAP
Signaling Flow
 Configuration unsupported caused intra-NodeB inter-frequency

hard handover failure rate
 Configuration unsupported caused intra-RNC inter-frequency
 Configuration unsupported caused inter-RNC inter-frequency
 Physical channel failure caused intra-NodeB inter-frequency hard
handover failure rate
 Physical channel failure caused intra-RNC inter-frequency hard
 Physical channel failure caused inter-RNC inter-frequency hard
 ……
Inter-RAT CS Outgoing Handover Success
rate（UMTS->GSM）
Signaling Flow
 Statistic Period: 15Mins, 30Mins, 1Hour…., 1Day

 Statistic Area: cell-wise or RNC-wise
 Measurement Method：Calculate based on OMC Counters’ value
 Indicator Meaning: this indicator reflects the Inter-RAT CS handover mobility, the
handover is from UMTS system to GSM system.
Rate（UMTS->GSM）
Signaling Flow
CS Inter-RAT Handover Success Rate（UMTS->GSM）
＝1－CS Inter-RAT Handover From UTRAN Failure Times

/CS Inter-RAT Handover From UTRAN Required Times×100%
Rate（UMTS->GSM）
Signaling Flow
Success Flow
UE RNC CN 2GMSC CS Inter-RAT Handover From
Relocation UTRAN Required Times
required Prepare handover
Relocation Prepare handover

Handover from
command response
UTRAN command
Handover complete
UE UTRAN
Failure Flow
HANDOVER FROM UTRAN COMMAND
CS Inter-RAT Handover From UTRAN

Failure Times, if the handover is failed,
RNC will receive this message HANDOVER FROM UTRAN FAILURE
Rate（UMTS->GSM）
Signaling Flow
 Configuration unsupported caused CS Inter-RAT handover from UTRAN

failure rate
 Physical channel failure caused CS Inter-RAT handover from UTRAN
failure rate
 Configuration incomplete caused CS Inter-RAT handover from UTRAN
failure rate
 Protocol error caused CS Inter-RAT handover from UTRAN failure rate
 Cell update occurred caused CS Inter-RAT handover from UTRAN failure
rate
 Invalid configuration caused CS Inter-RAT handover from UTRAN failure
rate
 No reply caused CS Inter-RAT handover from UTRAN failure rate
 ……
Inter-RAT PS Outgoing Handover Success
Rate（UMTS->GPRS）

Signaling Flow
 Statistic Period: 15Mins, 30Mins, 1Hour…. 1Day


value
 Indicator Meaning: this indicator reflects the Inter-RAT handover

mobility, the handover is from UMTS system to GPRS system.

Signaling Flow
PS Inter-RAT Handover Success Rate（UMTS->GPRS）
＝1－PS Inter-RAT Handover From UTRAN Failure Times

/PS Inter-RAT Handover From UTRAN Required Times×100%
Signaling Flow
Success Flow
UE NODEB RNC 3G SGSN
Cell change order from UTRAN Iu Release

Command
RL Del Req
PS Inter-RAT handover from
RL Del Resp UTRAN required Times
Iu Release
Complete
UE Failure Flow UTRAN
PS Inter-RAT handover from UTRAN failure CELL CHANGE ORDER FROM UTRAN
times. If the RNC received this message, or
response message of Iu Release Command is not
received by RNC, it means the PS handover from CELL CHANGE ORDER FROM UTRAN FAILURE
UTRAN is failed.
Inter-RAT outgoing PS Handover Success
Signaling Flow
 configuration unsupported caused PS Inter-RAT handover from

UTRAN failure rate
 physical channel failure caused PS Inter-RAT handover from UTRAN
failure rate
 configuration incomplete caused PS Inter-RAT handover from UTRAN
failure rate
 protocol error caused PS Inter-RAT handover from UTRAN failure rate
 cell update occurred caused PS Inter-RAT handover from UTRAN
failure rate
 invalid configuration caused PS Inter-RAT handover from UTRAN
failure rate
 No reply caused PS Inter-RAT handover from UTRAN failure rate
 ……
Inter-RAT Incoming PS Handover Success
Rate（GPRS->UMTS）
Signaling Flow

 Indicator Meaning: this indicator reflects the Inter-RAT handover mobility, the
handover is from GRRS system to UMTS system.
Rate（GPRS->UMTS）
Signaling Flow
PS Inter-RAT Handover to UTRAN Success rate（GPRS->UMTS）
＝PS Inter-RAT Handover to UTRAN Success Times

/PS Inter-RAT Handover to UTRAN Attempted Times×100%
Rate (GPRS->UMTS）
Signaling Flow
UE Serving RNC CN
The flow of PS Inter-RAT

1. UE initiated signaling connection establishment handover to UTRAN is
similar to the PS setup
flow on the UTRAN Side
2. Direct Transfer
3. Radio Access Bearer Establishment
RNC received message RRC Connection Request（from UE, the cause is Inter-RAT
cell reselection）can be used for calculating the PS Inter-RAT handover to UTRAN
required times；RNC received message RRC Connection Complete (From UE) can
be used for calculating the PS Inter-RAT handover to UTRAN success times
CS12.2K Service Access Time
Signaling Flow
 Statistic Period: －
 Statistic Area: －
 Measurement Method：DT&CQT
 Indicator Meaning: this indicator reflects the integrity of CS 12.2K

service. It is one of the most important indicators of the

Signaling Flow
＝Average 【T（CC Alert)

－T（ RRC Connection Request ）】
Signaling Flow
UE RNS CN Incoming CN
RRC Connection Setup T（RRC Connection Request）

RRC Connection Setup Complete
CN Signaling Connection Process

RRC DT(CM Service Request)
Authority and Safe Mode Process

RRC DT(Setup)
RRC DT(Call Proceeding)
RAB Assignment Process

ISUP IAM
T（CC Alert） CN Bear Setup Process
RRC DT (Alert) ISUP ACM
RRC DT(Connect) ISUP ANM
RRC DT(Connect ACK)
Service data （talking…）
CS64K Service Access Time
Signaling Flow
 Measurement Method： DT&CQT
 Indicator Meaning: this indicator reflects the integrity of CS 64K

Signaling Flow
＝Average 【T（RRC Request)

－T（CM Service Request）】
Signaling Flow
RRC Connection Setup T（RRC Connection Request）

CN Signaling Connection Process

RRC DT(CM Service Request)

RRC DT (Setup)
RRC DT (Call Proceeding)

ISUP IAM
T（CC Alert） CN bear setup process
RRC DT (Connect) ISUP ANM
RRC DT (Connect ACK)
PS Service Access Time
Signaling Flow
 Measurement Method： DT&CQT
 Indicator Meaning: this indicator reflects the integrity of PS

Signaling Flow
＝Average 【T（ Active PDP Context Accept)

－T（ Activate PDP Context Request ）】
Signaling Flow

Activate PDP CN Signaling Connection Process

Context RRC DT(CM Service Request)
Request
RRC DT (Activate PDP Context Request )
RRC DT (Active PDP Context Accept )
Active PDP ISUP IAM
Context Accept CN bear setup process
RRC DT (Connect) ISUP ANM
RRC DT (Connect ACK)
CS Service Traffic Erlang
Signaling Flow

 Indicator Meaning: this indicator reflects the traffic Erlang of the CS conversation
service
Signaling Flow
CS Call Duration
＝∑【Time（Radio Link Setup Response）

－ Time（Radio Link Deletion Response）】
CS Service Traffic ERL＝Total CS Call Duration of a Certain Period/3600

Signaling Flow
 CS AMR Voice Service Traffic Erlang
 CS Video Phone Service Traffic Erlang

PS Service Throughput
Signaling Flow

 Indicator Meaning: this indicator reflects the total throughput of PS service

Signaling Flow
UL PS Service Throughput＝RNC Received Total RLC PDU Bytes

DL PS Service Throughput＝RNC Sent Total RLC PDU Bytes
（Including user data，RLC head data，retransfer data，signaling data，Unit：Kbytes）

Signaling Flow
 PS I 64/64 UL Throughput
 PS I 64/64 UL Throughput
 PS B 64/64 UL Throughput
 PS B 64/64 UL Throughput
 PS S 64/64 UL Throughput
 PS S 64/64 UL Throughput
 ……
UL Interference Load Factor
Signaling Flow
 Measurement Method: Calculate based on Measurement Report

value
 Indicator Meaning: this indicator reflects the cell average UL load

factor in a defined period, it is calculated based on the RTWP
value on a certain frequency.

Signaling Flow

＝（UL RTWP measurement value－N0 ）
/UL RTWP measurement value×100%
DL Power Load Factor
Signaling Flow

 Measurement Method: Calculate based on Measurement Report

value
 Indicator Meaning: this indicator reflects the cell average DL load

degree in a defined period, it is calculated based on the base
station Tx power.
Signaling Flow
＝DL Average Transmitting Carrier Power/

Configured DL Maximal Transmitting Carrier Power×100%
Trouble Cell Rate
Signaling Flow

 Indicator Meaning: this indicator reflects the rate of dead cells to

total cells, it is an assistant to analyze the QoS of whole network.
Trouble Cell Rate
Signaling Flow
Trouble Cell Rate
＝Trouble Cell Number/ Active Cell Number×100%
Trouble Cell is the cell whose call drop rate >a％ or Radio Access Success rate <b％
Busy Cell Rate
Signaling Flow

 Indicator Meaning: this indicator reflects the rate of busy cells to

Busy Cell Rate
Signaling Flow
Busy Cell rate
＝Busy Cell Number/Active Cell Number×100％
Busy cell is the cell whose DL Power Load factor >c％

or Code Resource Occupation Factor >d％
Sleeping Cell Rate
Signaling Flow

 Indicator Meaning: this indicator reflects the rate of idle cells to

Sleeping Cell Rate
Signaling Flow
Sleeping Cell rate
＝Sleeping Cell Number/Active Cell Mumber×100%
Sleeping Cell is the cell whose DL power load factor <e％

Content
 KPI monitor
 KPI Case study
EMS KPI Optimization Process
EMS KPI Optimization Process
Key KPIs Worth Your Attention
RRC Cell RAB Cell RAB Cell RAB Cell Cell Inter-RAT
Radio Call Cell
Establis Establishme Establishme Establish PS CS Outgoing
Access Drop Success
hment nt Success nt Success ment Call Handover Success
Succes Rate - Rate of
Success Rate, CS Rate, PS Success Drop Rate(UMTS-
s Rate Voice SHO
Rate domain domain Rate Rate >GSM)
 Radio access success rate = RRC establishment success
rate × RAB establishment success rate
 This formula indicates that RRC establishment rate and
RAB establishment rate need to be considered in the
background statistics.
 RRC establishment success rate = Number of successful
RRC connection setup times of each cell / Number of RRC
connection request times of each cell × 100％
 Note: related with services (RRC connection)
 RAB establishment success rate = Number of successful
RAB establishment times / Number of RAB establishment
attempts × 100%
 RAB establishment success rate is categorized by service.
Access Success Rate Analysis Process
Access Failure Caused by RAB Establishment
Failure
 There are two restraints in RAB establishment process.
One is RB establishment which is the UE configuration
process (usually no problems occur in this process); and
the other is radio link re-configuration process in which
NodeB links are configured. Failures often occur in the
latter process. The usual causes for these failures include
radio link re-configuration preparation failure (it occurs
when problems occur in NodeB resources.), and radio link
re-configuration cancellation (it occurs when problems
occur in RNC internal resources or process). Another
factor may also cause RAB failures, that is, when the load
of a cell is relatively heavy, RNC sends out a reject
command via admission control.
Call Drop Optimization
Handover Success Rate Optimization
 Factors affecting handover success rate
 Handover area is too small, so that UEs have not enough time to
complete handover.
 Handover parameters are wrongly set, so that neighbor cells
cannot be added or deleted timely, or causing ping-pong handover.
 Neighbor cells are not configured. This may cause damage to the
network, not only directly causing call drop, but also brings extra
interference towards the network.
Content
 KPI monitor
 KPI Case study
Resource KPI monitor
 One reason for resource limitation is number of 3G user increase, and
operator changing fee decrease also lead to the increase of average
erlang. The other reason is the strategy for design is focus on user
feeling and KPI but not system capacity. For example HK user average
Erl cold be up to 0.5E.
 Single user erlang could be 0.45erl on BH：
 Resource KPI and threshold.
 Resource KPI mainly include DL power, UL capacity, code resource
and CE resource.
Resource Type KPI id and name threshold
C301320150 Number of rejected services,DCH downlink TCP limit 50
PI30167 Average non-HSDPA TCP 40%
TCP
PI30092 Maximum Cell TCP (%) 100%
PI30093 Average Cell TCP 70%
PI30029 Handover Blocking Rate 0.5%
UL Traffic
KPI RTWP（in busy hour） -98dBm
C301320153 Number of rejected services, DCH no code 50
Code PI30205 Average Cell HSUPA Users 12
PI30172 Cell Average HSDPA Users 16
PI301830006 Maximum use Ratio of Uplink NodeB CE 60%
CE
PI301830010 Maximum use Ratio of Downlink NodeB CE 60%
 Related KPI
DL power monitor
 RNC TCP limitation with CS call drop
2009-06-09 RNC Call Drop Rate,CS Traffic Volume, CS AMR(Erl) Number of rejected services,DCH downlink TCP limit
00:00:00 01:00:00 1.24% 851.54 56
01:00:00 02:00:00 1.07% 481.2097 22
02:00:00 03:00:00 1.09% 253.1742 12
03:00:00 04:00:00 0.70% 134.0175 5
04:00:00 05:00:00 0.61% 84.9817 11
05:00:00 06:00:00 0.54% 66.0458 11
06:00:00 07:00:00 0.64% 102.6633 31
07:00:00 08:00:00 1.06% 259.94 235
08:00:00 09:00:00 1.31% 658.3644 2262
09:00:00 10:00:00 1.11% 1242.4528 1875
10:00:00 11:00:00 0.91% 1798.6944 3261
11:00:00 12:00:00 1.04% 2266.3008 7064
12:00:00 13:00:00 1.09% 2629.905 8398
13:00:00 14:00:00 0.99% 2488.7411 3719
14:00:00 15:00:00 1.05% 2494.8219 7936
15:00:00 16:00:00 1.05% 2598.1903 10515
16:00:00 17:00:00 1.16% 2762.4531 11489
17:00:00 18:00:00 1.20% 2930.3844 9926
18:00:00 19:00:00 1.45% 3336.4133 22875
19:00:00 20:00:00 1.29% 2674.1925 5196
20:00:00 21:00:00 1.04% 1946.7989 1288
21:00:00 22:00:00 1.13% 1858.4106 616
22:00:00 23:00:00 1.32% 1818.2567 575
23:00:00 00:00:00 1.35% 1445.835 216
DL power monitor
 Modify reserve HSDPA power according to system algorithm.
 MinHsdpaPower（MinHspaPwrRto）+NoHsPower >Node B
admission threshold（MinHsdpaPower stands for HSDPA reserved
power ），DL congestion control will start (downgrade DL DCH rate)
。MinHspaPwrRto default value is 20%.
Number of rejected services,Handover
2500
2000
1500
1000
500
-500
0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0 8:0 9:0 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: 23:
0 0 0 0 0 0 0 0 0 0 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2009-6-12 6 1 1 0 0 0 0 2 22 99 556649108471821954108121201760 66 9 19 13
2009-6-17 0 2 0 0 0 0 2 0 6 28 113187252 95 214261285367643 86 10 11 4 3
DL power monitor
 Because high load cell often be with high admission failure, normally
we should fast downgrade to release radio resource ASAP. Avoid
handover user could not handover in the cell then call dropped.(this
action is only take effect in cell with much more PS users, if all users in
the cell is in CS service. It will not take effect).
Abbreviated Range and Current Update

Parameter name remark
Name Step Value value
Maximum Number of Degraded Uplink Downgrade from
UlDnMaxStg [1, 8] 1 2
Load Steps Every Time 384kbps to 16kbps
Maximum Number of Degraded Downlink Downgrade from
DlDnMaxStg [1, 8] 1 3
Load Steps Every Time 384kbps to 8kbps
DL power monitor
 Through decrease DL Eb/No could lead to reduced congestion. While
we need detailed evaluation to avoid some other bad effect. Table
showed record for the modification, and can be consider as the
reference. ZTE engineering experience showed downgrade Eb/No for
13.6K signaling channel could reduce TCP limitation effectively, while
the performance of access will not be affect so much.
Abbreviated Parameter Current Update Modify

remark
Name name Value value purpose
Downlink B class parameter，service related parameter, Reduce TCP
DlEbNo 7.5 5.1
Traffic Eb/No modify 13.6K signaling only (service class 5) Limit
UL capacity monitor
 Call drop rate increasing not means UL capacity limitation, but call
drop increasing is the most common scene for limitation. Because call
drop rate is most cared KPI, and be observed every day.
7.00%
6.00%
5.00%
4.00%
3.00%
2.00%
1.00%
0.00%
0:00:00
1:00:00
2:00:00
3:00:00
4:00:00
5:00:00
6:00:00
7:00:00
8:00:00
9:00:00
10:00:00
11:00:00
12:00:00
13:00:00
14:00:00
15:00:00
16:00:00
17:00:00
18:00:00
19:00:00
20:00:00
21:00:00
22:00:00
23:00:00
Cell Call Drop Rate,CS1 Cell Call Drop Rate,CS2
UL capacity monitor
 RTWP increasing is the most directly representation for UL limitation,
while sometimes reason for RTWP increasing could be external
interference. And it’s hard to eliminate this reason.
110
105
100
95
90
85
80
75
0:00:00
1:00:00
2:00:00
3:00:00
4:00:00
5:00:00
6:00:00
7:00:00
8:00:00
9:00:00
10:00:00
11:00:00
12:00:00
13:00:00
14:00:00
15:00:00
16:00:00
17:00:00
18:00:00
19:00:00
20:00:00
21:00:00
22:00:00
23:00:00
Maximum RTWP(dBm)1 Maximum RTWP(dBm)2
UL capacity monitor
 Erlang is determining factor for UL limitation either. There are many
factors related to the erlang of a cell. Normally we should care for cell
capacity, if erlang in a cell exceed 20 erlang in BH.
30
25
20
15
10
0
0:00:00
1:00:00
2:00:00
3:00:00
4:00:00
5:00:00
6:00:00
7:00:00
8:00:00
9:00:00
10:00:00
11:00:00
12:00:00
13:00:00
14:00:00
15:00:00
16:00:00
17:00:00
18:00:00
19:00:00
20:00:00
21:00:00
22:00:00
23:00:00
Cell Traffic Volume, CS(Erl)1 Cell Traffic Volume, CS(Erl)2
UL capacity monitor
 UL Power control parameter modification. The quality of users will be
down as a consequent of capacity increasing. Optimization will do
trade-off between capacity and quality.
Abbreviated Current new

Parameter meaning Modification object effect
Name Value value
Uplink 3.4k/13.6k Signaling，Uplink
ULINITSIR Uplink Initial SIR target (dB) 4-5 3.5 Obviously
12.2k AMR
Maximum Uplink SIR target Uplink 3.4k/13.6k Signaling，Uplink
ULMAXSIR 15 10 Obviously
(dB) 12.2k AMR
B class BLER Period Factor / Tolerance Uplink 3.4k/13.6k Signaling，Uplink
2/250 1/70 Obviously
parameter BLER Period 12.2k AMR
Uplink SIR Target Down Step Uplink 3.4k/13.6k Signaling，Uplink A few
UlSirTargDnStep 0.1 0.2
Size (dB) 12.2k AMR improvement
UL capacity monitor
 Through UL power control parameter optimization we can improve
RTWP increasing, but some cells will be in trouble for user increasing.
And further modification to SIRtarget will affect subscriber feeling. For
this case ZTE suggest to define another set of power control
parameter which is special for these high load cells. The following
table is comparison of parameters for special site and parameters for
normal site.
SRVTYPE ULINITSIR ULMAXSIR ULMINSIR

0 3.5->1.5 10.0->3.5 2.0->1.0
104 4.0->2.0 15.0->5.0 0.5->0
28 3.5->1.5 10.0->3.5 0.5->0
50 6.0->2.0 15.0->5.0 2.0->0
54 6.0->2.0 15.0->5.0 2.0->0
Code resource monitor
 Through observing "Number of rejected services, DCH no code”
we could know cell is in code limitation. Also “average code
resource usage” and “HSDPA user number” could be factor for
determination and optimization. We could modify the code
allocation to reduce code limitation.
 OcuRateNoHspdsch+OcuRateHspdsch+DpchCodeHy+32<=512
formula 1
 OcuRateNoHspdsch+OcuRateHspdsch+CodeUptHyA>512
formula 2
 “OcuRateHspdsch” is the number of code (SF=512) which is blocked by the
code occupied by HS-PDSCH channel.
 “OcuRateNoHspdsch” is the number of code (SF=512) which is blocked by
the code occupied by not HS-PDSCH channel.
 “DpchCodeHy” is the number of code (SF=512) reserved for DPCH channel.
 “CodeUptHyA” is the threshold to determine if we need decrease HS-PDSCH
channel number.
 When formula1 is fulfilled NO. of HS-PDSCH +1.
 When formula 2 is fulfilled NO. of HS-PDSCH -1.
Code resource monitor
 To assure R99 user accessibility, the modification is apply.
Abbreviated Parameter Range Current Update
remark
Name name and Step Value value
DPCH Code To decrease the number of
DpchCodeHy 0..512 16 28
Hysteresis rejected services for DCH no code
Code Update To decrease the number of
CodeUptHyA 0..512 16 28
Hysteresis A rejected services for DCH no code
Content
 KPI monitor
 KPI Case study
Case 1: TCP Congestion at Victory Park
 Background
 Victory Park more than
100,000 People Gathering
 Time is 20:00 June 4th
 KPI Indication
 Performance deteriorate for
site VPK at Victory Park
 Call Drop Rate Increase
 Site VPK Transmission
Code Power Congestion
Case 1:Call Drop Rate & Number is high in
VPK
Case 1:VPK Radio Access Rate and Rejected
Services by TCP limit
Case 2: Wrong LAC Configuration
 After the configuration data check, we found that there are
several cells with a wrong LAC configuration.
 We need KPI monitor tools to give us an evidence.
 Use SAY Site as an example:
 Number of attempted RRC Establishment is more than 100,000
times while only around 6,000 times for services.
Case 3：High Call Drop Rate Due To The
NSN Sites Interference
 Background
 After the KPI monitoring, we found the drop rate around
Convention and Exhibition Center is quite high.
 After the drive test and KPI analysis, we found the reason
is that the NSN LUR site F1 is still open.
 After the site is turned off on 12th May the call drop rate
decreased.
Case 3：High Call Drop Rate Due To The
NSN Sites Interference
Case 4: High Call Drop Rate due to Power Alarm
 Site CTW has very high call drop rate.

 After checking the Fault management Alarm, there are a
lot of “board reboots alarm”.
 After checking the NodeB, the reason for this alarm is non-
sufficient power supply due to GSM, UMTS and NSN BTS
in very narrow space with a temporary power solution.
 Three times “Node B is out of service(198083023)” during
15:00 to 16:00 on June 11th.
Case 5: Iub E1/T1 Bandwidth Limitation
 Background:
 After 80% NSN UMTS users are cut into the network on may 11th,
subscriber number increased a lot
 KPI Indication:
 “Cell RAB establishment success rate” decreased a lot.
 Analysis
 Capacity related.
 After checking the related configuration, Iub interface E1/T1
bandwidth limitation is a key reason for the problem.
 Solution:
 Decrease some of the cells Pilot Channel Power
 Increase Iub interface bandwidth
Case 5: Iub E1/T1 Bandwidth Limitation

Umts Radio Network Kpi-108

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Umts Radio Network Kpi-108

Încărcat de

Drepturi de autor:

Formate disponibile

UMTS Radio Network KPI

 Measurement Methods：DT or CQT

 Index Meaning：The coverage probability reflects the RF coverage

Indicator Indicator Indicator

Downlink: F=RSCP > R & Ec/Io > S

Uplink: TxPwr < T

Coverage Probability is defined as the percentage of the samples

R and S are different for different services

 Statistic Period :15 Mins, 30 Mins,1 Hour…. 1Day….

 Statistic Area ：cell-wise

 Measurement Method：calculate based on the OMC Counters’

 Indicator Meaning：this indicator reflects the accessibility of the

Indicator Indicator Indicator

RRC Establishment Success Rate

＝RRC Connection Setup Complete Times

RAB Assignment Request

Radio Bearer Setup Established

Radio Bearer Setup Complete

 Statistic Period : 15 Mins, 30 Mins,1 Hour…. 1 Day….

 Statistic Area: RNC & Cell-wise

 Indoor or Outdoor: BOTH

 Measurement Method: calculate based on the OMC Counters’

 Indicator Meaning: RAB assignment is the last step of the service

Indicator Indicator Indicator

RAB Establishment Success rate

＝（CS RAB Assignment Success Times

RRC Connection Request

RRC Connection Setup

DT Message Exchange RAB Assignment

Radio Bearer Setup Established

Indicator Indicator Indicator

 CS RAB Establishment Success rate

 Statistic Period: 15 Mins, 30 Mins, 1 Hour…. 1 Day….

 Statistic Area: Cell-wise

 Indoor or Outdoor: BOTH

 Measurement Method: calculate based on the OMC counters’

 Indicator Meaning: this indicator reflects the accessibility of the

Call Setup Success Rate

＝RRC Establishment Success Rate (Service Related)

RRC Connection Request

RRC Connection Setup RRC Establishment

RAB Assignment Request

Radio Bearer Setup Established

Indicator Indicator Indicator

 AMR Call Setup Success rate

 Statistic Period: 15 Mins, 30 Mins, 1 Hour…. 1Day….

 Statistic Area: RNC & Cell-wise

 Measurement Method: calculate based on the OMC Counters’

 Indicator Meaning: this indicator reflects the Retainability of the

Call Drop Rate

＝（RNC Triggered CS RAB Release Number

RNC Triggered RAB

Indicator Indicator Indicator

 CS Call Drop rate

 Statistic Period: 15 Mins, 30 Mins, 1 Hour…. 1Day

 Statistic Area: Cell-wise

 Measurement Method: calculate based on the OMC Counters’ value

 Indicator Meaning: Rate of blocked calls due to resource shortage.

Indicator Indicator Indicator

Call Blocking Rate

The number of blocked calls

Indicator Indicator Indicator

 Statistic Period: 15 Mins, 30Mins, 1Hour…. 1Day

 Indoor or Outdoor: BOTH