Huawei Sharing Sessionn KPI - 250111

HUAWEI NPI Sharing Season
www.huawei.com
HUAWEI RNP
January 2011
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Analyze and Improve KPI CS (Voice)
Analyze and Improve KPI PS (Data)
Identify and Analyze HW Problem
How to using LMT/M2000 for change
parameter, query, etc

Page 2
In a live network maintain and optimization are regular
activities that need to do to keep network in good
performance.
SDSR, HOSR, TDR as KPI Voice and TBF SR,
GPRS/EDGE DL Throughput as KPI Data are Key
Performance Index in this NPI
Our sharing session will describe what we have done in
this NPI to improve KPI CS and PS, Analyze HW
Problem symptoms and How to use M2000 and LMT
for parameter change and query data.

Page 3
After this Sharing Session, we share and know:
What we have done to analyze and improve KPI CS and PS
Familiar how to identify Hardware problem from TRX Measurement
Result
Familiar to use M2000 and LMT for data collection and parameter
change

Page 4
SDSR
HOSR
TDR

Page 5
Analyze and Improve SDSR
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6

1. Check Alarm
Most likely sudden degradation SDSR due to alarm occurrence such as LAPD Alarm, Radio Link
Prompt Alarm, LAPD Link Congestion due to flicker Transmission Alarm, etc.
2. Check SD Blocking . If blocking :

Check if continue or spike. If spike check availability of cell (alarm) or neighbors site availability.
If continue check parameter idle mode such as RXLEV_ACCESS_MIN and CRO (2db). If not
proper adjust to proper parameter such as CRO (2dB) for GSM shall be 0 and DCS default by 13.
If no cell out of service and already standard parameter and no missing neighbors, check if still can
tune parameter (If DCS blocking reduce CRO (2dB) for DCS or if GSM blocking increase CRO
(2dB) for DCS) otherwise add SDCCH channel.
3. Check Frequency
Bad SDSR due to frequency most likely will have steady value until there is change in BCCH.
Checking base on Map is most suitable ways. Co-channel and Adjacent Cell head to head must be
avoid and tune if any. Retune BCCH is one of most effective to improve SDSR in cluster level.
4. Check Coverage
Coverage must be maintain to have good SDSR since excessive coverage (overshoot) will cause
interference and low downlink / uplink level. We can check coverage by CTRx counter (TA
Measurement) and check on map.
Downtilt is solution for this case but shifting some SDCCH from Hopping TRx to BCCH TRx can
help SDSR since avoid hit on hopping channel if BCCH more clear. Add T200 help also to
increase delay for SD Channel request due to low signal strength.

1. Check Alarm.
Most likely sudden bad SDSR due to alarm occurrence such LAPD Alarm, Radio Link Prompt Alarm, LAPD Link
Congestion due to flicker Transmission Alarm, etc.

2. Check SD Blocking . If blocking :
Check if continue or spike. If spike check availability of cell (alarm) or neighbors site availability.
If continue check parameter idle mode such as RXLEV_ACCESS_MIN and CRO (2db). If not proper adjust to proper
parameter such as CRO (2dB) for GSM shall be 0 and DCS default by 13.
If no cell out of service and already standard parameter and no missing neighbors, check if still can tune parameter
(If DCS blocking reduce CRO (2dB) for DCS or if GSM blocking increase CRO (2dB) for DCS) otherwise add
SDCCH channel.

3. Check Frequency
Bad SDSR due to frequency most likely will have steady value until there is change in BCCH. Checking base on Map
is most suitable ways. Co-channel and Adjacent Cell head to head must be avoid and tune if any. Retune BCCH is
one of most effective to improve SDSR in cluster level.

4. Check Coverage
Coverage must be maintain to have good SDSR since excessive coverage (overshoot) will cause interference and low
downlink / uplink level. We can check coverage by CTRx counter (TA Measurement) and check on map.
Downtilt is solution for this case but shifting some SDCCH from Hopping TRx to BCCH TRx can help SDSR since avoid hit
on hopping channel if BCCH more clear.
TA BEFORE
TA AFTER

LAC Merge
Some case if number of LAC in current network can be reduce thus can decrease SD Load since Location Update due to cross
border will reduce also improve SDSR in area with. We do LAC Merging in our NPI period also base on Total Paging Load in
some LAC that will be merge.
Sample : BSC Margorejo (4677 4758

Analyze and Improve HOSR

1. Check Alarm and Hardware
Spike degradation on HOSR can be happen due to alarm occurrence such Cell Out of
Service Alarm due to Hardware Alarm of neighbors site. Hardware problem without
alarm also can degrade HOSR since to fast Handover occur due to poor signal strength
caused by hardware problem.
2. Check Neighbor Relation

Check missing neighbors or not proper neighbors (not needed).
Define which relation that having bad success ratio. Check target cell that having bad
success rate from all incoming, If all incoming have bad success rate check alarm and
hardware problem, if not check parameter per relation adjacent and modify.
3. Check Db Internal and External Cell

Check database especially external adjacent to make sure database created in external
adjacent is updated with current database (BCCH, BSIC, LAC)
4. Check Handover Parameter Threshold

Threshold parameter can be set depends on network situation. If set to high can cause
unnecessary HO but if set too low can have late HO and call may be drop. Some case
we render more hard to attempt HO to reduce HO fail in network by Increase Inter cell
HO Hysteresis, Min Access Level Offset, PBGT HO Threshold for same layer or
Increase Adjacent Cell Inter Layer for different layer.

16-bit queuing NPI Project

HO Reason Algorithm NPI Project






NPI Project
Min UP Power on HO Candidate Cell : The M criterion supports the minimum value
constraint of uplink receive level of the adjacent cell.
Expected uplink level of the adjacent cell >= (Min UP Power on HO Candidate Cell + Min
Access Level Offset)
The M criterion is met if the Filtered downlink level of the adjacent cell >= (Min DL Power on
HO Candidate Cell + Min Access Level Offset); otherwise, the M criterion is not met.
The value of this parameter ranges from 0 to 63 (corresponding to -110 dBm to -47 dBm).
Min DL level on Candidate Cell : This parameter specifies the minimum downlink receive
level of a neighbor cell.
Expected downlink level of the neighbor cell >= (Minimum downlink power of the candidate
cell for handover + Minimum access level offset)
The M criterion is met if the Expected uplink level of the neighbor cell >= (Minimum uplink
power of the candidate cell for handover + Minimum access level offset); otherwise, the M
criterion is not met
DL / UL Qual. Threshold : This parameter specifies the downlink / uplink receive quality
threshold of an emergency handover. An emergency handover is triggered when the
downlink / uplink receive quality is greater than or equal to the DL / UL Qual. Threshold.
When an emergency handover is triggered, an inter-cell handover should be preferentially
selected. An intra-cell handover, however, is triggered if no candidate cell is available and if
intra-cell handovers are allowed.

NPI Project
Edge HO DL RX_LEV Threshold : If the DL receive level remains lower than the Edge HO
DL RX_LEV Threshold for a period, the edge handover is triggered. If the PBGT handover
is enabled, the relevant edge handover threshold can be decreased. If the PBGT handover
is not enabled and the edge handover threshold is not properly set, cross coverage, co-
channel interference, and adjacent channel interference are likely to occur. The Edge HO
DL RX_LEV Threshold should be adjusted based on the handover performance statistics
and the actual network performance to achieve the UL/DL balance.
Edge HO UL RX_LEV Threshold : If the UL receive level remains lower than the Edge HO
UL RX_LEV Threshold for a period, the edge handover is triggered. If the PBGT handover
is enabled, the relevant edge handover threshold can be decreased. If the PBGT handover
is not enabled and the edge handover threshold is not properly set, cross coverage, co-
channel interference, and adjacent channel interference are likely to occur. The Edge HO
UL RX_LEV Threshold should be adjusted based on the handover performance statistics
and the actual network performance to achieve the UL/DL balance.

NPI Project
Inter-layer HO Threshold : This parameter is used to determine the inter-layer in the 16
bits to sort the candidate cells for handovers.
Inter-layer HO threshold of a serving cell = configured Inter-layer HO Threshold - Inter-layer
HO Hysteresis
Inter-layer HO Threshold of an adjacent cell = configured Inter-layer HO Threshold + Inter-
layer HO Hysteresis of an adjacent cell - 64.
Inter-layer HO Hysteresis: This parameter specifies the hysteresis of an inter-layer or

inter-priority handover. This parameter is used to avoid inter-layer ping-pong handovers.
Actual Inter-layer HO Threshold of a serving cell = configured Inter-layer HO Threshold -
Inter-layer HO Hysteresis
Actual Inter-layer HO Threshold of an adjacent cell = configured Inter-layer HO Threshold +
Inter-layer HO Hysteresis of an adjacent cell - 64.

NPI Project
Location of some handover parameters in Emergency HO Data

NPI Project
Some parameters works depends on other setting such as Adjacent Cell Inter Layer HO Hysteresis on different layer

NPI Project
Some handover parameters related in Handover data and Adjacent relation

Case 1. (Parameter change)
Adjust Handover
Parameter Threshold
9-10 Nov 2010

Case 2. (Neighbors audit )
Audit neighbors (delete/add) can improve HOSR since best candidate can be choice

Case 3.
Parameter Trial (Co-BSC/MSC) :

Global Parameter Change from Yes to No
This parameter specifies whether to adjust the sequence of candidate cells. After the sequence is adjusted, the
handover within the same BSC/MSC takes priority.
If this parameter is set to Yes, the target cell to which the MS is handed over may not be the cell with the best signal
quality.

Case 4. (Troubleshoot Hardware Problem on Juwana II-0)

Case 5. (Poor Success Rate to one of some adjacent cells due to HW Problem)




Analyze and Improve TDR

1. Check Alarm / Hardware Problem
Like SDSR sudden degradation on TDR due to alarm occurrence such as Radio Link Prompt Alarm,
Cell Out of Service, LAPD OML fault, etc. Some case alarm not occurred but hardware having
problem
2. Check Frequency.
Bad frequency planning causing high interference. This can be on BCCH TRx or on Hopping TRx.
For BCCH TRx mainly on BCCH channel assigned and for Hopping TRx depends on Mal Id, HSN and
MAIO assigned.
3. Check Neighbors
Neighbors relation must be checked to guarantee continuity of mobile user. Wrong or missing
adjacent relation lead to wrong handover scenario or causing call dragging and easy to occur drop
call. Neighbors database check also needed especially for different BSC. Correction of missing
neighbors will improve TDR also HOSR as well
4. Check Coverage
Similar with SDSR case, excessive TA distribution can increase drop call since interference happened
and poor signal strength on uplink or downlink easy to have more drop call. Tilting the cell to have
more proper coverage will improve TDR, addition adjacent to overshoot area sometimes help TDR but
not always improve. Sometimes need to check RxLevelAccessMin to be proper not too small value
and CRO (2dB) not too high value
5. Reduce blocking on TCH
Blocking on TCH can degrade TDR in a network since TCH can not be accessed especially for
handover case. Blocking when handover occurred can cause call dragging and lead to increment of
drop call. This TCH Blocking can be reduce by traffic sharing, increase HR portion, Lower PDTCH
ratio.

Sample 1. Alarm Occurrence Impact to TDR

Sample 2. (Troubleshoot Hardware Problem without alarm occurrence)

Sample 3. (Retune BCCH)

Sample 4. (Tilting)

Sample 5. (Reduce Blocking by Traffic Sharing to DCS)

TBF Completion Success Rate
GPRS DL Throughput
EDGE DL Throughput

Page 43
Improvement TBF Completion SR
Global Change Parameter
1. Release Delay of Downlink TBF(ms)
This parameter specifies the release delay of the downlink TBF.
After sending the last downlink RLC data block and confirming that all downlink data blocks are received, the network
does not immediately notify the MS of releasing this TBF but forcedly set the last data block not received. Therefore,
keep this TBF unreleased by continuously resending the last downlink data block with the Relative Reserved Block
Period (RRBP) flag.
If this parameter is set to a higher value, this wastes the wireless resources and influences the the access performance
of other MSs in the network, thus causing the useless signaling seizing the channel bandwidth and wasting the downlink
resources.
2. Inactive Period of Extended Uplink TBF(ms)
This parameter specifies the inactive period of the extended uplink TBF.
Upon receiving the last uplink RLC data blocks (CountValue=0) from the MS that supports the extended uplink TBF
function, the network does not release this uplink TBF immediately but set it to the inactive mode
If this parameter is set to a higher value, the release delay of the uplink TBF increases, thus wasting the uplink
resources.
3. Support 11BIT EGPRS Access
This parameter specifies whether the 11-bit EGPRS access is supported.
Yes: supported
No: not supported
No Condition Parameter Name Before After

1 All Cell Release Delay of Downlink TBF(ms) 2400 1000
2 All Cell Inactive Period of Extended Uplink TBF(ms) 2400 1000
3 All Cell Support 11BIT EGPRS Access Yes No

Global Change Parameter
Parameter change in PS Network Optimization Parameters on GPRS Attributes

Result of Global Change Parameter
TBF Completion Success Rate
98.5
98
97.5
97
96.5
96
95.5
95
94.5 1 2
94
9/1/2010
9/3/2010
9/5/2010
9/7/2010
9/9/2010
10/11/2010
10/13/2010
10/15/2010
10/17/2010
10/19/2010
10/21/2010
10/23/2010
10/25/2010
9/11/2010
9/13/2010
9/15/2010
9/17/2010
9/19/2010
9/21/2010
9/23/2010
9/25/2010
9/27/2010
9/29/2010
10/1/2010
10/3/2010
10/5/2010
10/7/2010
10/9/2010
2G-Kudus 2G-Purwokerto 2G-Yogyakarta
1. Applied in 2 BSC Pilot in Cluster Yogyakarta at 30th September 2010 night time
2. Applied in All BSC in NPI Cluster at 5th October 2010 night time

Improvement GPRS DL Throughput
PDTCH Re-Dimensioning
In this NPI Project, we follow PDTCH Dimensioning as follow :
Combine EDGE & GPRS-Tsel RNP Configuration Rules:

TRX/Sector
(Static PDCH Configuration Numbers)
If TRX<=4, PDTCH channel to BCCH
1 2 TRX.
If 8=>TRX>4, 4 PDTCH in BCCH TRX,
2 2 and left should be configure to 1st
3 3 TRX on 2nd GRFU / DRFU Board.
If TRX>8, configure 4 PDCH in BCCH
4 4 TRX, 4 in 1st TRX of 2nd Board and
left should be configured to 1st TRX
5 6 of 3rd Board. (Avoid malfunction of
6 7 DRFU)
7 7
8 8
9 10
10 11
11 12
12 13

PDTCH Re-Dimensioning

Result of PDTCH Re-Dimensioning
GPRS DL Throughput
90
80
70
60
50
40
30
20 1 2
10
0
9/2/2010
9/3/2010
9/5/2010
9/6/2010
9/8/2010
9/9/2010
9/4/2010
9/7/2010
9/10/2010
9/11/2010
9/12/2010
9/13/2010
9/14/2010
9/16/2010
9/17/2010
9/19/2010
9/20/2010
9/22/2010
9/23/2010
9/24/2010
9/25/2010
9/27/2010
9/28/2010
9/30/2010
10/1/2010
10/3/2010
10/4/2010
10/5/2010
9/15/2010
9/18/2010
9/21/2010
9/26/2010
9/29/2010
10/2/2010
2G-Kudus 2G-Purwokerto 2G-Yogyakarta
1. Applied in BSC under Cluster Yogyakarta at 27th September 2010 night time
2. Applied in BSC under Cluster Kudus and Purwokerto at 28th September 2010 night time

Improvement EDGE DL Throughput
1. PDTCH Re-Dimensioning
2. Additional Idle Time Slot
Addition Idle Time Slot for Site with :
1. Limited by current E1 installed
2. Calculation Idle Time Slot can be configured with :
a. Multiplexed Mode used
b. Number of TRx installed
c. Number of TCH+PDTCH Channel
d. Number of BCCH and SDCCH
e. Maximum Ratio Threshold of PDCHs
User Data rate Main TS 16Kbps Additional Idle TS
Coding Scheme TS 16Kbps
(Kbit/s) PDTCH 16Kbps
CS-1 9.05 1 0 1
CS-2 13.4 1 0 1
CS-3 15.6 1 1 2
CS-4 21.4 1 1 2
MCS-1 8.8 1 0 1
MCS-2 11.2 1 0 1
MCS-3 14.8 1 1 2
MCS-4 17.6 1 1 2
MCS-5 22.4 1 1 2
MCS-6 29.6 1 1 2
MCS-7 44.8 1 2 3
MCS-8 54.4 1 3 4
MCS-9 59.2 1 3 4

Example with current E1:
Site : Banyusoco (3 Sector, 1 E1, Multiplexed Mode (2:1), #TRx = 9, #BCCH =
3, #SDCCH = 7, Maximum Ratio Threshold of PDCHs = 30%.
From this information we can calculate number of TCH + PDTCH Channel (A)
A = 9 (TRx) * 8 (Tsl) 3 (BCCH) 7 (SDCCH)
= 62 Channel
TS for RSL = Roundup (9 (TRx) / 2 (Multiplex mode))
= 5 (64 Kbps)
Idle Time Slot can be configured = 1*128 (E1) 62 (TCH+PDCH) 5*4 (RSL)-
4*1 E1 (OML) 4 (buffered)
= 38 Idle time slot (16 Kbps)
Example with Maximum Ratio Threshold of PDCHs
From information PDCHs maximum will be = rounddown (30% * 62 Channel)
= 18 Channel
Idle Time Slot needed with this config
= 18 * 3 (Idle Time Slot in ABIS to get high MCS (8/9))
= 54 Idle time slot (16 Kbps)
E1 required = (62 (TCH + PDCH) + 5*4 (RSL) + 54 (Idle TS) + 4 (OML) )/ 124 (E1
4 buffered)
= 1.13 (Need 2 E1 / Add 1 E1 from current).


0
100
140
180
120
160
200
20
40
60
80
9/2/2010
9/3/2010
9/4/2010
9/5/2010
9/6/2010
9/7/2010
9/8/2010
9/9/2010
9/10/2010
9/11/2010
9/12/2010
9/13/2010
HUAWEI TECHNOLOGIES CO., LTD.

2G-Kudus
9/14/2010
9/15/2010
9/16/2010
9/17/2010
9/18/2010
9/19/2010
9/20/2010
9/21/2010
9/22/2010
9/23/2010
9/24/2010
9/25/2010
9/26/2010
9/27/2010
Huawei Confidential
9/28/2010
2G-Purwokerto
9/29/2010
2. Result Additional Idle Time Slot
9/30/2010
10/1/2010
1
10/2/2010
10/3/2010
10/4/2010
EDGE DL Throughput
10/5/2010
10/6/2010
10/7/2010
2
10/8/2010
10/9/2010
Page 53
10/10/2010
1. Applied in BSC Teluk2 and Kerteg under Cluster Purwokerto at 6th October 2010 night time
10/11/2010
10/12/2010
2G-Yogyakarta
10/13/2010
10/14/2010
2. Applied in BSC Teluk1 and Purwonegoro under Cluster Purwokerto at 7th September 2010 night time
10/15/2010
10/16/2010
10/17/2010
10/18/2010
10/19/2010
10/20/2010
THANK YOU!

Huawei Sharing Sessionn KPI - 250111

Uploaded by

Copyright:

Available Formats

Huawei Sharing Sessionn KPI - 250111

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Huawei Sharing Sessionn KPI - 250111

Uploaded by

Copyright:

Available Formats

HUAWEI NPI Sharing Season

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6

2. Check SD Blocking . If blocking :

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 7

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 8

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 9

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 10

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13

2. Check Neighbor Relation

3. Check Db Internal and External Cell

4. Check Handover Parameter Threshold

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 14

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Inter-layer HO Hysteresis: This parameter specifies the hysteresis of an inter-layer or

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Location of some handover parameters in Emergency HO Data

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Some handover parameters related in Handover data and Adjacent relation

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 28

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 29

Parameter Trial (Co-BSC/MSC) :

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 30

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 31

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 32

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 33

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 34

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 35

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 36

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 37

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 38

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 39

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 40

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 41

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 42

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

No Condition Parameter Name Before After

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 44

Parameter change in PS Network Optimization Parameters on GPRS Attributes

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 45

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 46

Combine EDGE & GPRS-Tsel RNP Configuration Rules: