4G Paging Guidelines

LTE Paging Procedure

LTE Paging Process
LTE paging process mainly includes the following steps:
（1）MME Pass S1-AP Paging Message in S1-interface. The paging is issued to the all
corresponding eNodeBs under same TAL.
（2）When S1-AP Paging Message reach eNodeB, it will be queued for the first valid PO. If
for some reasons such as page blocking, the first valid PO the paging message cannot be
sent properly, the eNodeB will try to get another valid PO in the next DRX cycle.
（3） UE use P-RNTI periodic monitoring PDCCH to understand PDSCH Page is available or
not. If there is, then decode PDSCH information loaded on the PCH Paging Message.
（4）If UE receive a pager message with a UE ID list, UE need to check their own UE ID is
contained in a pager message. UE ID check is made to determine whether the paging
message is for itself, and if so, continue to subsequent paging process, if it does not match,
UE go back to standby.

LTE paging policy:

The core network first use TA List to send a page, if there is no paging response, resend
paging, the number of resend can be used (the value range is 0~5). When reach maximum,
still do not receive paging response, the core network may consider expanding the paging
area (that is, Global paging). Depending on the core network policy, the number of global
paging is also configurable (range of 0~4)
If global paging is still unresponsive, the core network may consider further IMSI Paging
(depending on the policy of the core network), based on IMSI there are two types of
paging, respectively, based on TA List with IMSI Paging and global-based IMSI Paging
 Paging Capacity Based on Configuration
• In the TAC planning, the number of cell should be consideration in the same TAC. If there are so many cells in the same TAC, maybe
the paging is heavy loading, if there are few cells in the same TAC, maybe the location update is heavy loading, so TAC planning
should be joint consideration with the n umber of cell, whether related high speed cell and TA list including the number of TA.
• The UE may use Discontinuous Reception (DRX) in idle mode in order to reduce power consumption. One Paging Occasion (PO) is a
sub frame where there may be P-RNTI transmitted on PDCCH addressing the paging message. One Paging Frame (PF) is one Radio
Frame, which may contain one or multiple Paging Occasion(s). When DRX is used the UE needs only to monitor one PO per DRX cycle.
PF and PO is determined by following formula using the DRX parameters provided in System Information:
• UEs in idle mode monitor the PDCCH channel for P-RNTI used for paging to receive paging message from eNB. The UE needs to
monitor the PDCCH only at certain UE specific paging occasion, i.e. only at specific subframe in specific radio frame. At other times, the
UE may go to sleep mode to save battery power. One of the DRX parameters ‘nB’ is the deciding factor for paging capacity in a cell.
FDD Sub frame Pattern
Paging Frame Calculation Paging Occasion Calculation
PO when PO when PO when PO when
SFN mod T= (T div N)*(UE_ID mod N) i_s = floor (UE_ID/N) mod Ns Ns
i_s=0 i_s=1 i_s=2 i_s=3
where, Index i_s points to PO from the 1 9 N/A N/A N/A
- T: DRX cycle of the UE. 2 4 9 N/A N/A
sub-frame pattern defined in
4 0 4 5 9
- nB: 4T, 2T, T, T/2, T/4, T/8, T/16, T/32. the below table will be derived
- N: min(T,nB) from following calculation: TDD Sub frame Pattern
- Ns: max(1,nB/T)
- UE_ID: IMSI mod 1024
N: number of Paging Frame (PF) in DRX cycle
nB: number of Paging Occasion (PO) in DRX cycle
Ns: number of Sub Frame in PF used for paging
Paging Capacity Based on Configuration Cont.
Sample-1
Sample-2
Sample-3
 Paging Dimensioning with GOS
eNodeB Paging capacity refers to UE Number can have paging per second. The theoretical value of paging capacity depends on MaxNoofPagingRecords,
Paging cycle T (i.e. Paging DRX Cycle) and Nb parameters, the specific formula is as Follows:

P =（maxNoOfPagingRecords×N×Ns）/（T×0.01）
In the above formula
N = min (T, Nb)， N Represents the number of paging frames within each paging cycle T;
Ns = Max (1,Nb/T)， Ns Represents the number of paging sub-frames in each paging frame;

MaxNoofPagingRecords represents the maximum number of pages that can be contained in a paging message which can include multiple UE, and can share
a PO. The corresponding UE identification UE_ID take value 0~1023. UE_ID = IMSI mod 1024, so as long as UE_ID is assigned to within a paging cycle PO, that
is, in the same PO, UE starts page monitoring on the Location. T Represents a paging cycle, which is Paging DRX Cycle；
3GPP TS36.331 agreement provisions MaxNoofPagingRecords the maximum value is 16, so In the case of the limit value in MaxNoofPagingRecords Equals
16, the above eNodeB The theoretical value calculation formula for paging capacity can be simplified to:
P=1600×N×Ns/T
For the sake of convenience, eNodeB paging capacity theoretical value and the paging period T And Nb. See the table below for the corresponding
relationship.
Paging Dimensioning with GOS Cont.
As can be seen from the above table, eNodeB Maximum Ue paging per second, the theoretical value of the number is only affected by Nb related,
and Independent of Paging cycles T. As example, in Nb=T when eNodeB can be sent paging records per second as maximum as 1600, i.e. eNodeB
paging per second up to 1600 UE (multiple UE share a PO), and regardless the size of the paging cycle T.
If you consider 2% GOS, then the average UE paging in a PO is 9.83 (according to 2% The blocking rate query Erl-B table), so consider GOS=2% and
eNodeB maximum UE paging per second as showed in the table Below.
LTE Paging Parameters
LTE Paging Counter
TAL Planning
The TAL size is estimated based on the following parameters:

• MME paging volume: includes the number of boards in an MME and board paging volume.
• eNodeB paging volume: includes the paging load processed by the CPU, paging overhead allowed by the PDCCH
and PDSCH, and paging blocking rate.
• Maximum number of UEs concurrently attached to the network in the served area of an MME.
• Paging arrival rate during busy hours, which depends on the MME paging traffic model.
• Busy-hour paging traffic model of UEs.

Looking in into MME and eNodeB Paging Volume, normally MME supports paging volume 16 times more than
eNodeB which lead us to a conclusion:

MME normally doesn't limit TAL size --> TAL size is limited by eNodeB capabilities for paging volume
(pages/second).
TAL Dimensioning Based on Hardware Paging Capacity
TAL dimensioning means to estimate the eNodeB Number In all TA under the TA List Based on eNodeB Paging capacity
The size of TA List depends on the regional traffic profile and the paging intensity of each user, which can be calculated by following formula:
𝐶𝑒𝑁𝐵
𝑁𝑒𝑁𝐵,𝑇𝐴𝐿 =
𝑛𝑠𝑢𝑏,𝑒𝑁𝐵 x 𝐼𝑝𝑎𝑔𝑖𝑛𝑔,𝑠𝑢𝑏
In the calculation formula above:

𝐶𝑒𝑁𝐵 , eNodeB Paging capacity;

𝑛𝑠𝑢𝑏,𝑒𝑁𝐵 , represents each eNodeB Design of Attach Number of users; Based on ZTE CC boards paging capacity can be
supported up to 1600 paging/second
𝐼𝑝𝑎𝑔𝑖𝑛𝑔,𝑠𝑢𝑏 , Indicates that each Attach Page strength for users (paging times/seconds);
𝑁𝑒𝑁𝐵,𝑇𝐴𝐿 , represents number of eNB in one TAL

In meeting eNodeB paging capacity, The maximum number of eNodeB each TAL support is calculated as Follows:
If every eNodeB (single BP board) support for attach number of users is 4000, and the average number of pages per attached user is 3 times, then the maximum
eNodeB supported in a TAL, the calculation is:

3 1600
𝐼𝑝𝑎𝑔𝑖𝑛𝑔,𝑠𝑢𝑏 = Paging/subs/sec 𝑁𝑒𝑁𝐵,𝑇𝐴𝐿 = = 480 eNodeB/TAL
3600 4000 x 0.000833
= 0.000833 Paging/subs/sec
If there is repeat paging configuration 1, this number should be divided by two
TA Boundary Recommendation
• LTE Single Site Building Model
For an initial network, given its small user base, nB can be set to be small value. In this example, nB is 2T. In accordance with the description in the
previous chapter, a maximum of 3200 paging requests can be sent per second, and if one base station is seen as three cells, the number of paging
requests per second of a base station is 9600.
• LTE Site Building Based on Existing Sites
Currently in field implementation, the LTE + 2G, LTE + 3G, and LTE + 2G + 3G site building models are used, which means that LTE sites are build
on existing networks. In this case, the paging areas (2G: LAC; 3G: RAC) of existing networks can truly reflect the status of network load. Thus, the
original paging area division method can be used for the LTE paging area division. If three GUL collocates use the same site, use the RAC as the
TAC for LTE.
• Notes for TAC Division
The periphery of a tracking area needs to be kept away from such areas with high traffic volume as busy downtowns, but kept near such areas
with low traffic volume as suburbs or factories or near areas with lower-end users. These areas feature cells of low density, small changing scope
of mobile station location, and a small network load caused by the cross-area location update. If the periphery of a tracking area unavoidably
covers a busy downtown, the periphery needs to be kept near such areas with lower user mobility as residential areas.
The periphery of a tracking area needs to be kept in a vertical or skew position from the road, and it should be kept away from such areas with
high user mobility such as overlapping tracking areas. Thus a large number of ping-pong location updates and ping-pong handover can be
avoided when tracking area is shifted from one to another. An improper configuration in this procedure has a great impact on the system.
The periphery of several tracking areas should avoid being put in a small area to reduce the constant location update and handover of the mobile
station between tracking areas.
The growing trend of traffic volume also needs to be considered in the demarcation of the tracking area periphery. In the design of the paging
volume and traffic volume of a tracking area, enough expansion margins need to be considered to avoid frequent demarcation and split of the
tracking area.
Paging Analysis and Solution Flow
Paging Congestion
As LTE terminals are mostly multi-mode ones, users may be
frequently handed over between 3G and 2G systems, causing
great amount of system reselections and location updates.
Have Y
Alarm/Transport Troubleshoot Alarm
Issue? Therefore, 2G and 3G networks are recommended to be co-sited.
The unified TA and LA planning reduces later maintenance work.
N
N If there is a mature 3G network, the LTE TA area usually will
Parameter follow the LA setting in 3G network. This setting has a benefit: A
Setting Already Optimize Parameter
Optimize ? CSFB UE registered in two networks.

Y And if the UE didn’t change the TAC, when CSFB happens there
wouldn’t have a LAU process in 3G.
TAC <= 3G LAC N
Re-boundary
boundary ? Maximize Paging Capacity by increasing parameters
MaxNoofPagingRecords up to 16
Y Nb parameters up to 4T
TAC Division End
TAC Division follow criteria recommendation
 Paging Parameter Explained
Default Paging Cycle: This is known as “T” and it is the value after which the UE wakes up from idle mode to read the paging messages. Usually it is set to
1280 ms or 128 frames. This means that if a UE woke up in frame # 3 then it will wake up again in frame # 131 (after 128 frames) and then at frame # 259
and so on. It will read the PDCCH and if the PDCCH directs it to a paging message, it will read the paging message. However, this only indicates that there
is a paging message in this subframe but it might not be addressed to that UE as there can be multiple UEs using the same paging cycle. “T” is
transmitted in SIB-2 but can also be shared by the MME and in that case the smaller value of the two is used. For instance, if T in SIB-2 is 1280ms and T
shared by MME is 640ms then the system will use 640ms as the T’s value.
NB: This parameter depicts the number of paging subframes within a Default Paging Cycle. If NB is set equal to T, then every frame contains one Paging
subframe. If NB is set to 2T, then every frame will contain 2 paging subframes. If NB is set to 1/2T then every second frame will have a paging subframe.
So, in short, this parameter can impact the paging capacity but at the same time it can increase or decrease the paging overhead as well. This is also
shared in SIB-2.
Paging Mechanism: These parameters are contained in the SIB-2 so the UE knows it’s paging subframe or paging occasion from the parameters in SIB-2
and from the function of it’s IMSI value. The UE will wake-up at the subframe where it expects it’s PO and will read the paging messages. The paging
messages contain the TMSI value so if the UE does not find it’s TMSI inside the paging messages, it will assume that it is not paged, and it will go back to
idle mode. However, if the UE finds it’s TMSI in one of the paging messages, it will understand that the page is addressed to it and it will initiate a RRC
Connection.
From the core’s perspective, if there is downlink data, the SGW will inform the MME and the MME will send a paging message to the eNB over the S1
interface. The S1 paging message contains a UE ID value which is obtained from a function of the IMSI. Based on this number and the value of N
(N=min(NB,T)), the eNB calculates the PO of the UE and it buffers the paging message until the PO. Since the UE already knows it’s IMSI and the eNB
derives it from the UE ID in the S1 Paging message, both the UE and eNB are synchronized and they use the same PO subframe. Once, the UE receives the
paging message addressed to itself, it initiates RACH process by sending a RACH preamble to the eNB. The eNB responds with a Random Access
Response. The UE then sends the RRC Connection Request and the cause value of this request is set to mt-access which indicate that the UE is initiating
the connection due to a paging message. The eNB responds with RRC Connection Setup and UE finally sends the RRC Connection Setup Complete to the
eNB resulting in completion of the RRC Connection. The eNB sends a S1 Initial UE Message to the MME with the Service Request and this message is
considered by the MME as the paging success.
 Paging Parameter Explained
Timer T3413 : The MME maintains a timer T3413 for paging messages. Once it sends the paging message to the UE, it starts the T3413 and it stops it
after receiving the Service Request in S1 Initial UE Message. In case, the Service Request is not received and T3413 expires then the MME will resend
the paging message to the UE.
However, this timer only works for PS pages and not for CS pages. In case of CS page, the page is retransmitted from the CS core.
Impact of Default Paging Cycle : The paging cycle or T as explained above tells the periodicity with which the UE wakes up to check the paging
messages. The smaller the value of T, the UE will need to wake up more frequently. This means that a smaller value of T will lead to higher battery
consumption or utilization and UEs will have to be charged more frequently. However, a larger value means that the latency for the UE will increase. For
instance, if we use 1280ms for T, the incoming pages at the eNB will be buffered longer on average and that will increase delay. This is not significant for
data services but it can be important for CS pages (CSFB) or for VoLTE and can increase call setup time. So, a compromise needs to be maintained
between battery consumption and expected paging delay.
Paging Failures : Another important aspect is to ensure that paging messages are successfully reaching the destined users. The paging failures can be
caused by decoding issues if the paging modulation scheme is aggressive or if the PDCCH allocation for paging is not using a robust aggregation layer.
So, it is a good idea to keep the Paging MCS on the PDSCH much lower in order to ensure successful decoding and also to ensure that the PDCCH is using
a conservative aggregation level like Aggregation Level 4 or 8.
Another issue that causes paging failures is frequent TAUs (Tracking Area Update). When the UE moves from one tracking area to another tracking area,
it initiates a TAU and if during this process a paging message is received then the UE might not be able to read it as it is undergoing a TAU. The problem
here is that when the UE is in idle mode, the MME knows it’s location at a TA or TAL (Tracking Area List) level. So, when the page comes for the UE, MME
sends this paging message to all the eNBs in that TA or TAL. If the UE moves from one TA/TAL to another TA/TAL then the UE needs to do a TAU to tell
the MME that the UE has moved to another TA/TAL and thus the MME will send the next paging messages for that UE to the new TA/TAL. If the UE is
undergoing TAU and the TAU is not completed yet and a paging message comes for this UE, the MME will send it to the old TA/TAL and the UE will not
be able to receive it. Thus, it is very important that the TAC planning is properly done to mitigate this issue. I will address the TAC dimensioning and
paging capacity in the next short article.
Thank You