Analysis Report on Low Paging Success Rate due to CN

configuration

Internal Use only

Analysis Report on
Low Paging Success Rate due to CN
configuration

Drafted by:

Nicole Chng Joe

Date:

8/7/2011

Huan (702394)
Reviewed by:

Date:

Reviewed by:

Date:

Approved by:

Date:

2016-06-07

HUAWEI Confidential

Page1, Total14

Analysis Report on Low Paging Success Rate due to CN

configuration

Internal Use only

Contents

Analysis Report on..............................................................................................................................1

Low Paging Success Rate due to CN configuration...........................................................................1
1. Problem Description....................................................................................................................3
2. Cause Analysis.............................................................................................................................5
i.
Parameter and figure related to Paging Audit:...................................................................5
v. Paging discard due to High SPU flow control:..................................................................5
vi. LAC Boundary Planning and Configuration Audit:..........................................................8
vii.
Paging Losses due to PCH Channel Congestion at UU interface.................................9
viii.
Paging Counter and KPI Audit....................................................................................10
ix. Inconsistent LAC Setting for certain cells in Core network............................................11
3. Suggestion and Summary........................................................................................................14

2016-06-07

HUAWEI Confidential

Page2, Total14

Analysis Report on Low Paging Success Rate due to CN

configuration

Internal Use only

1. Problem Description
In Country I Operator H, customer complaint on call access failure in good RF condition.
From CN CHR log checking, the call is released due to this call has been released (normal
call clearing) by subscriber-self because MS did not receive the Paging response message
from Iu interface.

From performance statistic, the trends of Paging Success Rate in CN are not match with the
RNC. From CN, the Paging success rate is average 80% while RNC Paging Success rate is
average 60% only.

2016-06-07

HUAWEI Confidential

Page3, Total14

Analysis Report on Low Paging Success Rate due to CN

configuration

Internal Use only

Figure 1: Paging Success Rate in Core network

Figure 2 : Paging Success Rate in RNC

2016-06-07

HUAWEI Confidential

Page4, Total14

Analysis Report on Low Paging Success Rate due to CN

configuration

Internal Use only

2. Cause Analysis
The analysis steps have been taken are:
i.Parameter and figure related to Paging Audit:
ii.Paging discards due to High SPU flow control:
iii.LAC Boundary Planning and Configuration Audit:
iV.Paging Losses due to PCH Channel Congestion at UU interface.
V.Paging Counter and KPI Audit
Vi.Inconsistent LAC Setting for certain cells in Core network
i.

Parameter and figure related to Paging Audit:

Core Network Parameter and Setting:

i.

Paging Retry for CN: 2 times paging

ii.

Interval for Paging retry: Interval for retry: First paging duration is 7 seconds and
Second paging duration is 4 seconds.

iii.

Whole Network Paging Switches() : OFF

RNC Parameter and Setting:

i.

DRX cycle Coefficient: 6 (ADD UCNDOMAIN)

ii.

Paging Retry for RNC: MaccPageRepeatTimes =1 (SET UDPUCFGDATA)

iii.

PICH Power Offset: -7 (MOD UPICHPWROFFSET)

iv.

PCH channel Power Offset: -20 (MOD USCCPCH)

As parameter setting checking, all the parameter are set to reasonable value which will not
cause abnormal paging success rate.
ii.

Paging discards due to High SPU flow control:

Figure 3: RNC Processor Load

2016-06-07

HUAWEI Confidential

Page5, Total14

Analysis Report on Low Paging Success Rate due to CN

configuration

Internal Use only

Figure 4: VS.RANAP.PagingLoss vs Paging Success Rate

When the SPU CPU usage reaches certain threshold, the flow control algorithm will start. It is
the basic feature in RNC to protect the hardware and stability of system.
The Paging discard due to flow control will trigger the measurement on counters
VS.RANAP.CsPaging.Loss, VS.RANAP.PsPaging.Loss.
The flow control threshold that related to paging can be find as command below.
SET

FCCPUTHD:BRDCLASS=XPU,

SLPAGECTHD=80,

SLPAGERTHD=70,

CPAGECTHD=90, CPAGERTHD=75. The detail of the parameter can be obtained in Table 1 :

Flow Control threshold parameter that related to paging.
Based on SPU load checking, Plaza Kuningan mean SPU load is maintain around 50% while
the

maximum

SPU

load

is

around

60%

only.

While

the

value

for

counters

VS.RANAP.CsPaging.Loss, VS.RANAP.PsPaging.Loss are zero which indicate that no

paging message loss due to flow control.
By consistency check from the RNC configuration, the flow control threshold related to paging
is set correctly and current SPU load have not reach the flow control threshed.
Measurement point for VS.RANAP.CsPaging.Loss and VS.RANAP.PsPaging.Loss
The measurement is triggered at point A as shown in the figure. When the RNC receives from
the CN a PAGING message in which the CN Domain Indicator IE indicates the CS domain,
the measurement of this counter is triggered if the RNC does not send a Paging type 1 or
Paging type 2 message. The reason why the RNC does not send a Paging type 1 or Paging
2016-06-07

HUAWEI Confidential

Page6, Total14

Analysis Report on Low Paging Success Rate due to CN

configuration

Internal Use only

type 2 message might be Iu flow control, or high CPU usage. If the RNC does not respond to
a paging message that is consecutively retransmitted, the RNC counts it only once.

Table 2 : Flow Control threshold parameter that related to paging

Parameter ID

Parameter

Parameter Description

Name
SLPAGECTHD

SS and LCS

Meaning: CPU usage threshold for paging flow control

page

over supplementary services (SS) and location service

control

threshold

(LCS). When the average CPU usage of sliding windows

reaches or exceeds the threshold, SS and LCS paging
flow control is triggered.
Recommended Value: 80

SLPAGERTHD

SS and LCS

Meaning: CPU usage threshold for recovery from paging

page

flow control over supplementary services and location

restore

threshold

service. When the average CPU usage of sliding windows

is lower than the threshold, SS and LCS paging flow
control is stopped.
Recommended Value: 70

CPAGECTHD

Call

page

Meaning: CPU usage threshold for call paging control.

control

When the average CPU usage of sliding windows reaches

threshold

or exceeds the threshold, call paging flow control is

triggered.
Recommended Value: 90

CPAGERTHD

Call

page

Meaning: CPU usage threshold for recovery from call

restore

paging control. When the average CPU usage of smooth

threshold

windows is lower than the threshold, call paging flow

control is stopped.

2016-06-07

HUAWEI Confidential

Page7, Total14

Analysis Report on Low Paging Success Rate due to CN

configuration

Internal Use only

Recommended Value: 75

iii.

LAC Boundary Planning and Configuration Audit:

As next step, the LAC boundary planning and configuration is taken place.

Extract the LAC information from command ADD UCELLSETUP and make a summary table
as below:
LAC

RNC
994

995

Grand Total

9992

414

414

9993

363

363

9994

533

533

9995

555

558

9996

714

720

9997

256

256

9999

Grand

1575

1270

2845

Total
From the summary table, it is found out there are 9 cells(LAC9995 and9996 in RNC 994)
that share LAC with RNC 995. After further analysis, 9 cells already re-home from RNC 994 to
RNC 995. Those Cell information havent been deleted from RNC 994 only.
This kind of duplication Cell information in RNC will not cause any major performance issue
like low Paging Success rate. Anyway, the duplication cells ID have been deleted.
The cell with LAC9999 is testbed cell only.
Then draw the LAC thematic map in map info tools. The LAC boundary planning is plan
appreciate where no island LAC site in RNC.

2016-06-07

HUAWEI Confidential

Page8, Total14

Analysis Report on Low Paging Success Rate due to CN

configuration

iv.

Internal Use only

Paging Losses due to PCH Channel Congestion at UU interface.

Figure 5: Cell PCH Channel usage rate and RRC.Paging1Loss due to PCH Congestion
Iu Paging Congestion Cell ratio is 0% and PCH bandwidth usage rate is around 50%.
i) Iu Paging Congestion Cell ratio: The PCH Channel is not congested based on the
performance

statistic

checking.

The

counter

that

measured

is

VS.RRC.Paging1.Loss.PCHCong.Cell. In daily, VS.RRC.Paging1.Loss.PCHCong.Cell is less

than 200 which contribute Paging Congestion ratio only 0.0030% or below.
Measurement point for VS.RRC.Paging1.Loss.PCHCong.Cell
The measurement is triggered when the RNC discards a paging message due to PCH
congestion. This counter indicates the number of Paging Messages Discarded Due to PCH
Congestion for Cell.
ii) PCH bandwidth usage rate: Overall PCH Usage is quite high where the recommended
threshold is only 50%.
To resolve the PCH bandwidth usage rate, LAC re-planning and adding more SCCPCH
channel can be the solution.
2016-06-07

HUAWEI Confidential

Page9, Total14

Analysis Report on Low Paging Success Rate due to CN

configuration

Internal Use only

For this case, verify whether the number of attempt are reasonable are not are the next steps
to verify before any expansion or re-plan activity taken place.

v.

Paging Counter and KPI Audit

RNC: IU Paging Success Ratio

=(VS.RANAP.Paging.Succ.IdleUE/VS.RANAP.Paging.Att.IdleUE)*100%

Core Network: Paging Success Rate

= (Number of First Paging Responses from Iu Interface+Number of Repeated Paging
Responses from Iu Interface)/Number of First Pagings to Iu Interface)*100%

2016-06-07

HUAWEI Confidential

Page10, Total14

Analysis Report on Low Paging Success Rate due to CN

configuration

Internal Use only

For this case, verify whether the number of attempt are reasonable are not are the next steps
to verify before any expansion or re-plan activity taken place.
As steps to verify whether the number of paging attempt are reasonable or not, compare the
number of paging attempt between RNC and MSC. It is found out that the paging that receive
from RNC are 6 times higher than MSC.

As consequence, suspect that mismatching on RNC attempt might coming from wrong
counter in RNC or CN.
To verify it, start Iu Paging tracing in RNC web LMT for 10 hour from 7pm, 11 May until 5am,
12 May. From the comparison result, the paging receive from core network are matching with
the RNC counter vs.RANAP.CsPaging.Att. Thus, RNC counter measurement are accurate.

2016-06-07

HUAWEI Confidential

Page11, Total14

Analysis Report on Low Paging Success Rate due to CN

configuration

Internal Use only

in order to compare the number of paging attempt from RNC and Core network,

vi.

Inconsistent LAC Setting for certain cells in Core network

From further analysis on the Iu paging tracing, it is found out that LAC distribution in

RNC994 are as table below:

LAC 270B and 270C are not the LAC in RNC995, it is belongs to RNC994. Why MSC also
send the RNC995 paging to RNC 994?
Escalate to CN core network engineer to carry out cell and LAC consistency check between
MSC and RNC.
It is found out that wrong LAC information have been defined for certain amounts of cell due
to some cells are NodeB re-home from RNC994 to RNC995 but the CN configuration are not
update to new RNC after the NodeB re-home activity.
By re-do the Iu Paging Tracing, no more paging message receive by RNC994 on LAC 270B
and 270C. It indicates that Cell and LAC configuration consistency check and correction are
done successfully.

2016-06-07

HUAWEI Confidential

Page12, Total14

Analysis Report on Low Paging Success Rate due to CN

configuration

Internal Use only

After correct those inconsistency cell in MSC, the paging success rate improve from around
60% to 70%. But 70% for Paging Success rate still consider unacceptable. Why the paging
success rate still low?

It is suspect the RAC configuration in SGSN might be inaccurate as well. Escalate it to PS

core team for the Cell ID and RAC consistency checking.
The result of the consistency checking show that the RAC95, RAC4, RAC1 and RNC96 are
unnecessary and extra RAC that configure to RNC 994.

2016-06-07

HUAWEI Confidential

Page13, Total14

Analysis Report on Low Paging Success Rate due to CN

configuration

Internal Use only

PS Core teams delete the inaccurate RAC in SGSN. The paging success rate further
improves from 70% to 90% which is under acceptable range now.

3. Suggestion and Summary

In this case, inaccurate RNCID for certain Cell in MSC and additional RAC in SGSN caused
the Low Paging Success Rate.
Coordination with CS core team, PS core team and HQ are essential to solve the network
issue efficiency.

2016-06-07

HUAWEI Confidential

Page14, Total14