LTE49 Paging

And Tracking Area

dimensioning
Bartlomiej Bednarz, Krzysztof Golebiewski
MBB CS Network Engineering
Wroclaw, 10.07.2014

Please always check the latest version of this slides!

1 27/06/2017 Nokia 2014 - MBB Customer Support Network Engineering

For internal use
 Tracking Area planning Small TAs MME
On the boundary of each TA,
TAU is triggered. More TAUs
Tracking Area concept: when the same area size is B
TA3
Tracking Area (TA) is an equivalent of LA/RA considered
TA5
TA consists of a set of contiguous cells TA2

TA is defined by TAI (Tracking Area Identity) TA4

TA1 A
MCC MNC TAC
TAI vs.
TAs can be aggregated into Tracking Area List (TAL) MME
Easier replanning thanks to TAL concept (it is possible to aggregate two or more
TAs in one TAL instead of replanning of one TA) Big TAs
For future: TAL will be able to change dynamically, e.g. last TA that UE was Only one TAU is triggered B
previously registed can be added to new TAL that UE is now registered TA2
It should ensure that ping-pong effect will not appear
From the Paging Capacity point of view amount of cells/eNBs in TAL
matters rather than association of TA to TA list.
While UE is moving within one TA(L) no TAU (Tracking Area Update) is TA1 A
triggered
2 With bigger TA(L),
27/06/2017 MME
Nokia 2014 - MBB and eNB
Customer TAUNetwork
Support Loads diminish
Engineering [UL]
For internal use
MME knows UE position with an accuracy to one TA(L)
 Tracking Area planning

Tracking Area concept:

If TA(L) is used, paging to one UE must be sent to each cell within one TA(L) according to known
(reported) UE location accuracy

MME Big TAs

Small TAs MME Paging is sent to all cells in whole
TA(L), the more eNBs in TA, the
Paging is sent to all cells in
whole TA(L), less eNBs in TA,
less S1AP Pagings triggered
vs. more S1AP Pagings are triggered

Reported UE location accuracy (3cells)

Reported UE location accuracy (3cells)

X
Paging load increases with bigger size of TA(L) [DL]
One cell can belong to only one TA TA can`t overlaps
In NSN product, each cell of one eNB must belong to the same TA TA1 TA2
(3GPP assumes that cells from one eNB can belong to different TA)
TA3
3 27/06/2017 Nokia 2014 - MBB Customer Support Network Engineering
For internal use
 Tracking Area planning

Tracking Area planning rules: TAU messages

Tracking areas should be planned to be relatively large,

rather than relatively small to minimize Tracking Area
Update
Their size may be reduced subsequently if
the experienced paging load becomes high
Existing 2G and 3G location area and routing area
boundaries may be used as a basis for defining LTE
tracking area boundaries
Tracking areas should not run close to and parallel to
major roads nor railways. Likewise, boundaries should Note: Boundaries of TA along main roads,
railways and so on are highly not
not traverse dense subscriber areas (if possible) recommended. Many undesired and frequent
There might be specific requirements to coordinate TAUs will be experienced.
Tracking Area planning with Location Area in case of CS Ping pong effect could be visible too.
fallback procedure (CSFB)
TA size (number of eNB within TA)
4 27/06/2017 Nokia 2014 - MBB Customer Support Network Engineering should be relatively large rather than
For internal use relatively small to minimize TAU
 Tracking Area dimensioning (concept)

1a Paging Capacity and 1b Paging Intensity

Example: 5 UEs camped under eNB1 are paged.

eNB1 eNB1
eNB2 eNB2
TA1 TA1
TA2 5 pagings/s
5 pagings/s 5 pagings/s 5 pagings/s

5 pagings/s
5 pagings/s PIeNB means how many 5 pagings/s 5 pagings/s
unique pagings (not duplicated) 5 pagings/s
are sent towards UEs that are
TA consists of only one eNB (3 cells). UE position is camped under one eNB.
known with accuracy of this one eNB. One S1AP
paging directed to TA1 can be addressed to proper Duplicated pagings. UE is not under
eNB (it does not have to be duplicated). ENb that eNB2 however it is not known.
received S1AP Paging Message is obliged to provide Paging has to be directed towards eNB2 as well.
RRC Paging Message to each own cell. MME
MME
TA consists of two eNBs (6 cells). UE position is known with
accuracy of two eNBs. Each S1AP Paging Message triggered
PCeNB means how many S1AP pagings from MME (both by MME has to be duplicated and sent to each eNB in tracking
unique and duplicated) can be served by one eNB. area. Then each eNB is responsible for providing RRC Paging
The higher number of eNBs in TA the higher number of Message to each own cell.
duplicated pagings.
5 27/06/2017 Nokia 2014 - MBB Customer Support Network Engineering
For internal use
 Tracking Area dimensioning (concept)

Paging Capacity and Paging Intensity TA1 PIeNB = 25 pagings/s

PCeNB = 100pagings/s
Example: 25pagings/s

Paging requests in RRC Paging Messages

PCeNB = 100 pagings/s (assumption)
100 S1AP Paging Messages can be
25pagings/s
handled and sent from each eNB
towards UEs

PIeNB = 25 pagings/s (assumption) 25pagings/s

25 unique S1AP Paging Messages
are assumed to be sent from each
eNB 25pagings/s
each unique S1AP Paging is duplicated
and sent towards each eNB in the Tracking
Area

6 27/06/2017 Nokia 2014 - MBB Customer Support Network Engineering

n * PIeNB PCeNB
For internal use where: n number of eNBs in TA
 Tracking Area dimensioning
1d Traffic Model
INPUTSTraffic Model (3 cells/eNB):
TM provides network and UE
specific behavior for planning Users (RRC Connected + RRC Idle) per eNB 450
(e.g. TA planning) MTC/MOC for VoIP 50%/50%
MTC/MOC for PS/background 30%/70%
Note: variety of applications and VoIP holding time 90 sec.
smartphone types cause that the PS data mean holding time 312 sec.
real network behavior might be PS data sessions per user per Busy Hour (BH) 1
significantly different comparing VoIP sessions per user per BH 1
to given TM that is taken for Background traffic per every user
example calculation purposes Paging repetition factor 5%
InactivityTimer: 10 sec.

OUTPUT:
PIeNB,TM = 4,3 pagings/s/eNB - Paging traffic generated
towards UEs from one eNB
7 27/06/2017 Nokia 2014 - MBB Customer Support Network Engineering
For internal use
 Tracking Area dimensioning
1e Counters
Counters define real network behavior INPUTSCounters/KPIs
comparing to Traffic Model and can be EPS Paging attempts/MME (M50C011) 5145000
used for TA replanning, giving possibility
Average EPS EMM-REGISTERED users (flns_5035a) 300000
to define average paging intensity
(PIeNB,Counters) per eNB #eNBusers 450

Counter M50C011 and KPI flns_5035a

can be taken from MME. They are M 50C 011 eNBusers
considered with one hour (BH) accuracy PI eNB ,Counters
in considered example flns _ 5035a 3600
#eNBusers is reflected in the average Average #pagings per UE during BH

number of users per eNB in considered OUTPUT:

area PIeNB,Counters = 2,14 pagings/s/eNB Paging traffic
generated towards UEs from one eNB

M50C011 EPS Paging attempts the number of Paging Attempts. Initial and repeated are counted.
flns_5035a
8
Avg EPS EMM-REGISTERED users This KPI shows the average number of users in EMM-REGISTERED state.
27/06/2017 Nokia 2014 - MBB Customer Support Network Engineering
For internal use
Tracking Area dimensioning
Tracking Area size

PCeNB 300
TAsize = 55 eNBs *
PI eNB 4,3 *20% of safety margin with respect
to maximum value assumed

PIeNB,TM = 4,3 pagings/s OR PIeNB,Counters = 2,14 pagings/s

For this example calculated value according to TM is taken into further calculations

Note:
Calculated TAsize is based on maximum Paging Capacity what may lead to situation that any increase of Paging Load would cause Paging
rejections
Safety Margin ensures some buffer that prevents mentioned issue
Blocking can still happen in scenarios where high deviations comparing to average Paging Intensity (PI) between different eNBs are present
For averaging purposes, it is assumed that each eNB has exactly the same parameter settings what gives the same Paging Capacity.
Analologously average Paging Intensity is assumed to be the same for each eNB as well

9 27/06/2017 Nokia 2014 - MBB Customer Support Network Engineering

For internal use
 Tracking Area optimization (CS fallback)

TA planning impacts on CS Fallback functionality: TA3 LA

Combined TA/LA update procedures are crucial for CS fallback
feature
MSC is informed by MME in which LA particular UE is located via SGs B
interface TA2 A
Operators who have existing 2G or 3G networks should consider TA1
to plan their TA or TAL boundaries to coincide with their Location
Combined
Area (LA) boundaries and reflect them in TA/LA mapping in MME TA/LA Update

LA3 LA2
B
A TA1
If LA on 2G/3G is really small please
consider use of dedicated 2G/3G features to TA4
extend paging capacity and increase LA size
10 27/06/2017 Nokia 2014 - MBB Customer Support Network Engineering
For internal use
LTE1234 Whatever the feature name

Backup

11 27/06/2017 Nokia 2014 - MBB Customer Support Network Engineering

For internal use