Paging Calculation

Calculation
Huawei
Network
July 14th, 2013
marsudi.te2000@gmail.com
7/16/15
Summary
This slide will depict how to calculate paging utilization in
Huawei network
Simple paging description and paging cause will be
discussed also this slide
Why paging utilization less than 100% but congestion
already triggered can be check in this discussion
Counter use for monitoring after LAC/RAC splitting and DT
step should be taken will be listed in this slide
7/16/15
Paging
Paging is one of the most important procedures in WCDMA.
Paging is critical factor associated with the call setup success
rate of the network.
The network will initiate paging in the following three cases:
1. Mobile terminating call
2. UTRAN system information update
3. UE state transitions
. When receiving paging from core network, UTRAN decides the
paging type.
. When mobile in IDLE mode, CELL PCH and URA PCH, UTRAN
will send paging type 1 on PCCH.
. Paging type 2 for a UE in RRC Connected Mode (CELL_DCH
and CELL_FACH states) on DCCH.
. When UE idle mode, paging will be broadcasted in to LAC
area, when UE in CELL DCH, CELL PCH and CELL FACH, paging
attempt will be sent to respective cell, while UE in URA state,
paging will be broadcasted into URA area
7/16/15
Paging Messages
The paging message include:
CN Domain Indicator, used by the RNC to identify from
which domain the Paging message originates
Permanent NAS UE Identity (that is, IMSI) used for
calculation of paging group and also for WCDMA RAN
paging co-ordination.
The paging message may also contain the following:
The DRX Cycle Length Coefficient (if available) may be
included in the Paging message, and if present, the
WCDMA shall when applicable use it for calculating the
paging occasions for the UE.
Temporary UE ID (that is, the TMSI)
Paging Area. Can be the Location Area Identity (LAI), the
Routing Area Identity (RAI) and (if omitted) the whole RNC
Paging cause
7/16/15
Mobile Terminating Call

NSS
UE AS
UE NAS
paging
RR_PAING_IND
RANAP
MSC
paging
RANAP
RR_EST_REQ (PAGING RESPONSE)
RRC setup procedure

INITIAL_DIRECT_TRANSFER
AUTHENTICATION REQUEST
(PAGING RESPONSE)
AUTHENTICATION RESPONSE
RR_SECURITY_CONTROL_REQ
(IK CK)
security mode control

SETUP
CALL CONFIRM
RAB setup procedure

ALERT
CONNECT
CONNECT ACKNOWLEDGE
After sending paging response, RRC connection request will be

sent with establishment cause: terminating conversation call
7/16/15
UTRAN system information update
When cell system information changed, paging type 1 is used

to inform mobile to read the updated system information. It is
special for the mobile in IDLE mode, CELL PCH and URA PCH .
7/16/15
UE state transitions
UTRA RRC Connected Mode
URA_PCH
out of
service
in
service
CELL_DCH
out of
service
in
service
Establish RRC Release RRC

Connection
Connection
in
service
GSM
Connected
Mode
GPRS
Packet
Transfer
Mode
CELL_FACH
out of
service
Release RRC
Connection
GSM:
Handover
UTRA:
Inter-RAT
Handover
CELL_PCH
Cell reselection
Release of
temporary
block flow
Establish RRC
Connection
Release RR
Connection
Establish RR
Connection
Initiation of
temporary
block flow
GPRS Packet Idle Mode1

Camping on a UTRAN cell1
Camping on a GSM / GPRS cell1
Idle Mode
When UTRAN wants mobile to change its state from CELL PCH
or URA PCH to CELL FACH, UTRAN will send paging type 1 to
mobile.
7/16/15
Discontinuous Reception (DRX)

The UE may use Discontinuous Reception (DRX) in order to
reduce power consumption. When DRX is used the UE
needs only to monitor one Page Indicator, PI, in one Paging
Occasion per DRX cycle.
In FDD mode, DRX cycle length = 2^k, k is DRX cycle
length coefficient. The UE shall store each CN domain
specific DRX cycle length for each CN domain the UE is
attached to and use the shortest of those DRX cycle
lengths.
The CS CN specific DRX cycle length coefficient shall be
updated locally in the UE using information given in system
information.
The PS CN specific DRX cycle length coefficient shall be
updated after the negotiation between the UE and PS CN by
NAS procedure.
7/16/15
Paging Occasion
one paging
occasion
2^K-1
4095
PI PI
0
P I
q
PI
NP-1
Paging Occasion = {(IMSI div K) mod (DRX cycle length

div PBP)} * PBP + n * DRX cycle length + Frame Offset,
Where n = 0,1,2 as long as SFN is below its maximum
value. K is the number of SCCPCH bears the PCH.
In FDD mode, Paging Occasion = IMSI mod 2K + n*2K
7/16/15
Paging Indicator Channel (PICH)
One PICH radio frame of length 10 ms consists of 300 bits (b0, b1, , b299). Of these,
288 bits (b0, b1, , b287) are used to carry paging indicators.
In each PICH frame, Np paging indicators {P0, , PNp-1} are transmitted, where Np=18,
36, 72, or 144.
The PI calculated by higher layers for use for a certain UE, is associated to the paging
indicator Pq . PI = DRX index mod NP = (IMSI div 8192) mod NP
If a paging indicator in a certain frame is set to "1" it is an indication that UEs associated
with this paging indicator and PI should read the corresponding frame of the associated
S-CCPCH.
7/16/15
10
Paging Cycle Coefficient

In the idle mode, the UE can receive the paging indication
with DRX to reduce the power consumption. At this time,
the UE needs to detect only one paging indication in a
paging occasion within a DRX cycle. The DRX cycle length
of UTRAN domain is obtained by substituting this parameter
into the formula DRX cycle = 2K PBP frames. Where, K
is [the paging cycle coefficient], and PBP is the paging
block cycle coefficient (In the FDD mode, PBP = 1).
Influence on the network performance: If this
parameter is set too small, the UE will detect the paging
channel frequently, and thus the battery is consumed fast;
if it is set too big, the UE will react very slowly on the
paging, it will also occur that the system repeats the UE
paging, and the downlink interference will be increased.
7/16/15
11
Paging Indicator per Frame (Np)

Np is the number of paging indicators per frame. The value
range of this parameter is 18, 36, 72, or 144.
Influence on the network performance:
PI = DRX index mod NP = (IMSI div 8192) mod NP.
All of the IMSIs is divided into Np groups. If this parameter
is set too small, for one IMSI, the paged probability of this
IMSI will increase and it will consume too much power. If
this parameter is set too big, the paged probability will
decrease. The bit number of each PI decrease too, and it
requests high demodulation performance for UE
7/16/15
12
Why Paging Utilization<100% but with Paging Congestion?
Maximum
Paging 5
UE per TTI
Statistic
Period
Paging Channel Specification PCH channel support

maximum paging 5 user with 1 TTI(Transmission Time
Interval, 1TTI=10ms)
Because the paging attempt is not stable within the statistic
period, some times is higher, some times is lower, so we
will face the paging congestion while the PCH
Utilization<100% .
The LAC split should be consider if the paging congestion
greater than 1% OR paging attempt
greater than 500k/hour 13
7/16/15
How big the PCH utilization will trigger paging congestion
Base on the Erlang B Table, if the Number of Channel is 5, and the

GOS is 1%, it can bear 1.361 Erl traffic, in other words, the
utilization is 27.22% (=1.361/5) while the GOS=1%
The PCH channel can support paging 5 user within 1 TTI,
We can assume the Number of Channel of 5, base on Erlang B
table, when the the utilization just 27.22%, GOS/Congestion
Rate=1%.
Base on Erlang B table, the
1% congestion.
utilization=27.22% will trigger

7/16/15
14
Paging Utilization Calculation

CS paging will be transmitted over specific LAC area
PS paging will be transmitted over specific RAC Area
RAC configuration is under LAC, so paging PS means paging
LAC+RAC
PS paging is much bigger than CS paging, so to reduce
paging load, one LAC can be configured with several RAC
Huawei recommend maximum paging attempt specific
LAC+RAC is 500K/hour
LAC+RAC splitting also recommended to be split if paging
loss already greater than 1%
7/16/15
15
Paging Performance Utilization

Paging Utilization (%) = 100*Paging Attempt/
(3600*(5/0.01))
Paging Attempt: Max VS.UTRAN.AttPaging1 in 1 cell
under respective LAC+RAC during 1 hour
(5/0.01) every TTI PCH can page 5 user
Paging Loss (%) = 100*Paging Loss/Paging Attempt
Paging Loss: Max VS.RRC.Paging1.Loss.PCHCong.Cell in
1 cell under respective LAC+RAC during 1 hour
Paging Attempt: Max VS.UTRAN.AttPaging1 in 1 cell
under respective LAC+RAC during 1 hour
7/16/15
16
Sample Paging Utilization Before & After Split LAC
Paging utilization LAC 6073 decrease after splitting

to be LAC 6073 & 6070
7/16/15
17
Sample Paging Attempt Before & After Split LAC
Paging attempt & paging loss decrease after LAC splitting
7/16/15
18
Important Thing During LAC/RAC Splitting

1. LAC splitting will impact to charging system, so LAC should be
created in Online Charging System before created new LAC
2. LAC should be linked to specific RNC, so paging from core can
identify which RNC should be page
3. If this LAC has neighbor LAC from different MSS, this new LAC
should be defined as external LAC in neighbor MSS (if not MSS in
pool)
4. Add new RAC, need RAC definition in SGSN
5. Avoid LAC/RAC border in crowded area to avoid high location area
update/routing area update
6. If MSS pool, 1 LAC should be defined in all MSC in respective pool
Item should be test after LAC/RAC splitting
. Functionality test CS (MOC & MTC) & PS
. Check charging
. Test handover to neighbor LAC (outgoing & incoming)
7/16/15
19
Monitoring after LAC/RAC Splitting

Check traffic each cell which has new LAC/RAC (if much
traffic degradation, check consistency LAC RNC and LAC in
core
Check counter terminating:
RRC.AttConnEstab.TmConvCall Most important sample
RRC.AttConnEstab.TmInterCall
RRC.AttConnEstab.TmLwPrSig SMS
RRC.AttConnEstab.TmHhPrSig
RRC.AttConnEstab.TmBkgCall
Counter terminating can be used to predict paging load
after LAC splitting assumption as below:
Paging generated by cell: (RRC Terminating cell/Total RRC
terminating cell )* Paging attempt
7/16/15
20
Sample Script (Modify LAC RAC)

1. Add ULAC:
ADD ULAC:CNOPINDEX=0, LAC=6220, PLMNVALTAGMIN=61, PLMNVALTAGMAX=68;
2. Add URAC
ADD URAC:CNOPINDEX=0,LAC=6220,RAC=17,PLMNVALTAGMIN=141,PLMNVALTAGMAX=148;
3. Add USAC
ADD USAC: CnOpIndex=0, LAC=6220, SAC=31011;
4. MOD UCELLACINFO
MOD UCELLACINFO: CellId=31011, LAC=6204, SAC=31011, CfgRacInd=REQUIRE, RAC=17;
Note:
. If only RAC modification (use existing RAC), can directly to mod ucellacinfo, no need to add USAC
. Dont forget to modify external in other RNC or 2G if respective cell defined as external cell
7/16/15
21
Thank You

Paging Calculation

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Paging Calculation

Hochgeladen von

Copyright:

Verfügbare Formate

Calculation

Mobile Terminating Call

RR_EST_REQ (PAGING RESPONSE)

RRC setup procedure

security mode control

RAB setup procedure

After sending paging response, RRC connection request will be

UTRAN system information update

When cell system information changed, paging type 1 is used

Establish RRC Release RRC

GPRS Packet Idle Mode1

Camping on a GSM / GPRS cell1

Discontinuous Reception (DRX)

Paging Occasion = {(IMSI div K) mod (DRX cycle length

Paging Indicator Channel (PICH)

Paging Cycle Coefficient

Paging Indicator per Frame (Np)

Why Paging Utilization<100% but with Paging Congestion?

Paging Channel Specification PCH channel support

How big the PCH utilization will trigger paging congestion

Base on the Erlang B Table, if the Number of Channel is 5, and the

utilization=27.22% will trigger

Paging Utilization Calculation

Paging Performance Utilization

Sample Paging Utilization Before & After Split LAC

Paging utilization LAC 6073 decrease after splitting

Sample Paging Attempt Before & After Split LAC

Paging attempt & paging loss decrease after LAC splitting

Important Thing During LAC/RAC Splitting

Monitoring after LAC/RAC Splitting

Sample Script (Modify LAC RAC)

Das könnte Ihnen auch gefallen