Huawei LTE TDD Paging Fault Locating and Optimization Guide

Security Level: Internal Only
LTE TDD Paging Fault

Locating and
Optimization Guide
www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

About This Document
 This document describes the basic paging principles, locating

methods for paging faults, defined actions for processing paging
faults, and typical paging fault analysis.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2

Contents
 Introduction to Basic Paging Principles
 Paging Fault Analysis
 Paging Fault Locating
 Paging Fault Cases

Introduction to the Paging Process
When the network side triggers paging for a UE, the MME sends paging messages to all eNodeBs
included in the TAC list with which the UE registers.
After receiving the message, the eNodeBs send the messages to all cells included in the TAC list.
After receiving the paging message, the UE sends an RRC connection request with the cause value
MT-ACCESS to the eNodeB. After the RRC connection is established, the UE sends an NAS message
Extended Service Request in response to the paging message.
Note 1: Multiple cells served by one eNodeB can be configured with different TACs. In live networks, cells served by one
eNodeB are configured with one TAC, and one cell maps to only one TAC.
Note 2: In this document, the expression of "TAC list" and "TAC" is the same.
Note 3: A system message change can also trigger paging. In eRAN6.0, paging triggered by system message updating and
paging triggered by the network side are calculated separately.

Paging in Different Service Scenarios
S-TMSI-based EPS service paging
This kind of paging is triggered when NAS signaling or user-plane data needs to be sent to the UE, but the UE is
not configured with an S1 link.
CN domain indicator is set to PS.
After the T3413 timer expires, paging messages will be retransmitted. (The number of retransmissions is controlled
by the N3413 timer.)
IMSI-based EPS service paging
If S-TMSI of the UE cannot be obtained due to network exceptions, the MME initiates IMSI-based EPS paging.
The network side does not start the T3413 timer.
After receiving the IMSI-based paging message, the UE initiates the detach procedure and reinitiates the attach
procedure.
CSFB-based paging
This kind of paging is triggered if the UE registers with both PS and CS service and receives a CS call.
CN domain indicator is set to CS.
The paging ID is based on S-TMSI or IMSI. (In this scenario, IMSI-based paging is normal.)
The MSC server in the CS domain controls the retransmission of paging messages. The MME does not start the
T3413 timer.
The UE sends a NAS message with the cause value EXTENDED SERVICE REQUEST in response to the paging
message.
SMS-based paging
This kind of paging is triggered when short messages are sent to the UE in idle mode.
If S-TMSI-based paging is used, the process is the same as that of S-TMSI-based EPS paging. If IMSI-based
paging is used, the process is the same as that of the IMSI-based EPS paging.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page5

Basic Paging Concepts
Basic paging concepts
DRX cycle: In a DRX cycle, the UE needs to monitor only one paging occasion, which saves
power.
Paging occasion (PO): The system sends paging messages in specific subframes for paging.
Paging Frame (PF): PF is a radio frame, and it contains one or multiple POs.
nB: Indicates the number of POs in a paging period. In a paging period, a UE has only one
PO, and a cell has nB POs. The paging period is configured on the eNodeB and contains 128
radio frames by default.

Calculation of the frame number and subframe number of a PO
Calculation of the paging frame number
SFN mod T= (T/N) x (UE_ID mod N)
SFN indicates the system frame number.
Index i_s can be obtained by querying the table shown in the next page.
i_s = floor(UE_ID/N) mod Ns
T: indicates the DRX cycle of the UE
nB: 4T, 2T, T, T/2, T/4, T/8, T/16, T/32.
N : min (T, nB).
Ns : max (1, nB/T).
UE_ID: IMSI mod 1024.

PO Calculation–Example
If DRX cycle (T) = 128s nB = 1 T = 128s UE_ID = IMSI mod 1024 = 5;
Then
N = min (T, nB) = T = 128, Ns: max (1, nB/T) = 1, T div N = 1, UE_ID mod N = 5
PF:
If SFN = 5, 128 + 5, …
SFN mod T = (T/N) x (UE_ID mod N) =5
PO:
i_s = (UE_ID/N) mod Ns = 0
By querying the following table, you can know that PO is the subframe 9.
Ns PO when i_s=0 PO when i_s=1 PO when i_s=2 PO when i_s=3
1 9 N/A N/A N/A
2 4 9 N/A N/A
4 0 4 5 9
1280 ms
Frame 0 1 2 3 4 5 6 …
PF
PO
Subframe 0 1 2 3 4 5 6 7 8 9
10 ms

Paging-related Parameters
 Paging-related parameters for the EPC
Parameter ID Parameter Name Parameter Description
T3413 T3413(s) Indicates the duration of the T3413 timer. This timer starts when a paging request is sent and stops when a service request is
received. After the timer expires, the UE retransmits the message.
Value range: 3-12 (Unit: Second)
The initial value in the system is 6s.
N3413 N3413(times) Indicates the retransmission times of a paging request before a response is received.
Value range: 0-5 (Unit: time)
The initial value in the system is 2 times.
PAGINGDEL Paging Indicates the time interval increased for retransmitting paging requests when the UE does not receive a service request.
TA retransmitting Value range: 0-20 (Unit: Second)
interval increment The initial value in the system is 0s.
 Paging-related parameters for the eNodeB

Parameter ID MML Commands Parameter Name Parameter Description
Indicates the default paging period for the cell. It is also called the DRX period. If the EPC specifies a DRX
period for a UE, the UE compares this period with the value of this parameter and uses the smaller one as its
DRX period. If the EPC does not specify a DRX period, the UE uses the value of this parameter, which is
DefaultPagin Default paging
MOD PCCHCFG delivered in the system information, as its DRX period. For details, see 3GPP TS 36.304. A larger value of
gCycle cycle
this parameter may lead to a longer delay in paging a UE but help reduce the power consumption of the UE.
A smaller value of this parameter may lead to a shorter delay in paging a UE but cause more power
consumption of the UE. Recommended Value: rf128(128 radio frames)
Indicates the number of paging occasions (subframes) contained in a paging cycle. Impact on Radio Network
Performance: For a certain paging load, a larger value of this parameter indicates a larger paging capacity
Nb MOD PCCHCFG NB
during a specific period, and a smaller value of this parameter indicates a smaller paging capacity during a
specific period. For details, see 3GPP TS 36.304. Recommended Value: ONET
Indicates the offset of the transmit power for the paging information relative to the RS reference signal power.
PchPwr MOD CELLCHPWRCFG PCH power
The unit is 0.005 dB.

Paging-related Counters for the MME
Counter Description Measurement Points
S1_mode_Paging _request_times This counter counts the number of paging requests that the The value of this counter increases by 1 when the
MME sends to the eNodeB over the S1 interface in a MME sends a paging request to the eNodeB over the
measurement period. S1 interface.
S1_mode_Paging _success_times This counter counts the number of paging success The value of this counter increased by 1 when the
messages that the MME received from the eNodeB over MME receives a paging success message from the
the S1 interface in a measurement period. eNodeB over the S1 interface.
S1_mode_Paging This counter counts the number of paging requests that the The value of this counter increased by 1 when the
_request_repeat_times MME retransmits to the eNodeB over the S1 interface in a MME retransmits a paging request to the eNodeB over
measurement period. the S1 interface.
S1_mode_Paging_request_initial_suc This counter counts the number of initial paging success The value of this counter increased by 1 when the
cess_times messages that the MME received from the eNodeB over MME receives a paging response from the eNodeB
the S1 interface in a measurement period. over the S1 interface after it first sends a page request
to the eNodeB.
S1_mode_SMS_Paging_request_tim This counter counts the number of paging requests that the The value of this counter increased by 1 when the
es MME sends to the eNodeB for the SMS service over the MME sends a paging request to the eNodeB for the
S1 interface in a measurement period. SMS service over the S1 interface.
S1_mode_CSFB_Paging_request_ti This counter counts the number of paging requests that the The value of this counter increased by 1 when the
mes MME sends to the eNodeB for CSFB over the S1 interface MME sends a paging request to the eNodeB for CSFB
in a measurement period. over the S1 interface.

Paging-related Counters for the eNodeB
Counter Description Measurement Points
This counter counts the number of The value of this counter increases by 1 when the eNodeB receives a paging message from the MME and
paging messages received over the the cell TAC belongs to the TAC list contained in the paging message.
S1 interface in a cell in a
L.Paging.S1.Rx measurement period.
This counter counts the number of The value of this counter increases based on the number of UEs contained in a paging message over the
UEs contained in a paging messages Uu interface. In eRAN2.1, the eNodeB retransmits the paging message over the Uu interface. In eRAN3.0,
over the Uu interface in a the eNodeB does not resend the paging message. Therefore, the value of this counter is equal to the value
measurement period. of L.Paging.S1.Rx in a measurement period. Point A in the following figure on the right represents a
L.Paging.UU.Att measurement point.
This counter counts the number of The value of this counter increases by 1 when the eNodeB receives an RRC Connection Request message
paging message responses received from the UE with EstablishmentCause set to mt-Access. Paging messages are broadcasted to all
from UEs in a cell in a measurement eNodeBs contained in the TAC/TAC list, and therefore, the value of this counter is less than that of
L.Paging.UU.Succ period. L.Paging.UU.Att. Point B in the following figure on the right represents a measurement point.
This counter counts the number of The value of this counter increases by 1 when the eNodeB discards a paging message in a cell. At present,
paging messages discarded in a cell paging messages discarded due to flow control or exceeding specified amount are not counted in this
after the eNodeB receives them from counter. It only counts the discarded paging messages due to board communication failures. Therefore, if
L.Paging.Dis.Num the MME. the value of this counter is not 0, communication between the eNodeB and MME is abnormal.
This counter counts the number of The value of this counter increases by 1 when a paging message is sent due to system message updating
paging messages sent due to system in a cell. For Huawei eNodeBs, based on the system message updating times, the number of paging
L.Paging.UU.SIUpdat message updating in a cell in a messages sent is 128, 256, … ModifyPeriodCoeff x 128. ModifyPeriodCoeff is set to 4.
e measurement period.

Paging Success Rate and Paging Success
Measurement Points
Paging success rate on the EPC side = (Number of paging responses in

response to the initial paging messages + Number of paging responses in
response to retransmitted paging messages)/Number of initial paging messages
Initial paging success rate on the EPC side = Number of paging responses in
response to initial paging messages/Number of initial paging messages
∑L.Paging.UU.Succ/L.Paging.S1.Rx x 100%
Note 1: Paging messages are broadcasted to all eNodeBs included in the TAC or TAC
list, the paging success rate of a single cell does not make sense. Only the paging
success rate calculated based on all eNodeBs in the TAC or TAC list can be used for
paging success rate comparison between different networks.
Note 2: L.Paging.UU.Succ: Indicates the number of paging responses received in a cell.
L.Paging.S1.Rx: Indicates the number of paging requests received in a cell. Cells
included in the TAC list receive the same number of paging requests. The paging
success rate on the eRAN side is the number of paging responses received in all cells
included in the TAC list divided by the number of paging requests a cell received.
A: number of paging requests on the EPC side (When calculating the paging
success rate, only the number of initial paging messages is counted.)
D: number of paging responses on the EPC side
B: number of paging attempts on the eRAN side
C: number of paging success times on the eRAN side

Contents

Paging Fault Analysis in Different Scenarios
Upgrade or migration
The wireless environment for upgrade and migration is the same. Paging faults caused by air interface factors, such as weak
coverage or interference are not considered.
Check whether paging-related parameter configuration is consistent before and after an upgrade or migration.
Check whether counter definition is consistent before and after an upgrade or migration.
Check whether TAC area division is consistent before and after an upgrade or migration.
Check whether paging-related counter definition is consistent between versions and between vendors before and after an upgrade
or migration.
If the fault is not rectified, check the paging fault based on the complete paging fault locating process.
New deployment or live network
Check whether the paging counters of the live network meet the requirements based on the paging counters of similar networks.
Check the paging fault based on the complete paging fault locating process.
Networks that support inter-RAT operations
Check the network reselection performance of the UE, whether the reselections are in time, and whether ping-pong reselections
exist.
Check whether UEs registered with the 2G or 3G network are paged on the LTE network.
MOCN-enabled or S1-FLEX-enabled networks
Compare paging statistics between two operators or EPCs on the EPC side. If the paging statistics for these two operators or EPCs
is different, preferentially check EPC configuration.
For the S1-FLEX-enabled network, check whether subscribers' paging responses are routed to the incorrect EPC.

Checking Paging Faults
Check paging-related parameters.
 Check whether DefaultPagingCycle and Nb configurations are consistent before and after an
upgrade or migration.
 Check whether PCH power and RS signal power configurations are consistent before and after an
upgrade and migration.
Check paging-related parameters on the EPC side.
Check TAC area division.
 Check whether TAC area division is the same before and after network planning.
 Check whether TAC parameter values in the configuration scripts are correct.
 Check the TAU times measured on the EPC side.
Check product implementation.
 Check the DL GRANT aggregation level of the paging message in the PDCCH.
 Check the code rate of the paging message in PDSCH.
 Check whether paging messages are retransmitted over the air interface proactively.
 Check the definition of the paging success rate.
 Check whether paging-related counter definition is consistent before and after upgrade or
migration.

Contents

Process-based Paging Fault Classification
Faults related to paging success rate are checked in four
processes as shown in the left figure.
: Check whether paging messages sent from the EPC to
the eNodeB over the S1 interface are discarded.
: Check whether paging messages are sent over the Uu
interface and determine the possible causes that RRC
connection request cannot be sent to the eNodeB. The
possible causes include:
Paging messages are not sent due to eNodeB internal faults.
Paging messages are discarded due to paging congestion
(air interface capacity limitation), weak coverage, or paging
black hole.
: Check whether RRC connections are established after
RRC connection request with the cause value MT-ACCESS
is sent to the eNodeB.
: Check whether the EPC side receives the paging
responses.
Faults occur in , , and  will decrease paging

success rate on the EPC side but do not have impact on
the paging success rate on the eRAN side.
Faults occur in  decrease the paging success rate on
both the EPC and eRAN sides.

Process-based Paging Fault Classification (Cont.)
Paging success rate on the EPC Action 1: Check whether paging

side sharply decreases. messages sent over the S1 interface
Paging success rate on the are discarded or the eNodeB
eRAN side remains unchanged. experiences an internal exception.
EPC paging success rate

decreases. Action 2: Check whether paging
eRAN paging success rate messages are not sent over the air
decreases. interface.
EPC paging success rate

remains unchanged. Action 3: Check whether the EPC
eRAN paging success rate paging success rate is normal, and the
decreases. eRAN paging success rate decreases.

Action 1: Checking Whether Paging Messages Sent over the S1
Interface Are Discarded or the eNodeB Experiences Internal Exception
Characteristic
As shown in the left figure, this fault occurs
because communication between the
eNodeB and EPC over the S1 interface is
abnormal. Air interface paging and response
are normal.
Causes
Paging messages sent over the S1 interface
are discarded due to CPU flow control.
RRC connection establishment success rate
for RRC request with the cause value MT-
ACCESS decreases.
RRC connection establishment for RRC
request with the cause value MT-ACCESS is
successful but the service layer of the EPC
does not receive the paging response.
Rules
This fault is generally caused by an internal
eNodeB exception. Logs are required for
analyzing the fault. If RRC connection
establishment success rate for RRC requests
with the cause value MT-ACCESS is normal,
air interface paging optimization cannot
rectify this fault.

(Cont.)
1. Paging messages sent over the S1 interface are discarded due to
paging congestion or CPU overload.
Cause Identification Method Solution
eNodeB main ALM-26202 BOARD In eRAN3.0 SPC320, paging

control board OVERLOAD ALARM is messages over the S1 interface
overload causes generated. discarded caused by main control
the eNodeB to L.Paging.Dis.Num is set to board CPU overloaded are not
discard paging a non-zero value. counted to L.Paging.Dis.Num. The
message sent fault has been rectified in eRAN3.0
over the S1 SPC360.
interface. Analyze the causes for CPU overload
and find solutions to decrease CPU
load.

(Cont.)
Paging messages sent over the S1 interface are discarded due to paging
congestion or CPU overload.
 As defined in the As defined in the 3GPP TS 36.331 V9.12.0 chapter 6.4, a maximum of 16 UEs can be paged in a
PO. (maxPageRec INTEGER ::= 16) For Huawei eNodeBs, a maximum of 16 UEs can be paged in a PO for a cell
whose bandwidth is higher than 10 MHz, and a maximum of 7 UEs can be paged in a PO for a cell whose bandwidth is
lower than 10 MHz. If the number of paging messages contained in a PO exceeds the specification, the exceeded
paging messages are discarded.
 Based on the default setting of Huawei paging-related parameters, Nb is set to one T, which means that each 10 ms
has a PO. Then the paging channel usage can be calculated. For a cell whose bandwidth is 20 MHz, Paging channel
usage = Number of paging messages/(SP x 100 x 16)
 Note: In this formula, SP is the measurement period, 100 indicates each second has 100 POs, and 16 indicates the
maximum number of UEs can be paged in a PO.
 UEs are paged randomly. If the number of subscribers paged simultaneously exceeds 16, PO conflicts occur and the
exceeded paging messages are discarded. High paging channel usage results in more PO conflicts. For example, if the
paging congestion rate allowed by an operator is 2%, the theoretical paging capacity reaches 1200 paging messages
per second and the paging channel usage is 75%.
 However, for a Huawei eNodeB, the maximum paging capacity is 500 paging messages per second, and the paging
channel usage is 31%. If CPU load increases due to other reasons, the paging capacity will be decreased due to flow
control.
 Paging messages are sent randomly. If the number of paging messages sent per second exceeds 300 in busy hours,
operations for decreasing the paging capacity need to be performed.

(Cont.)
1. Paging messages sent over the S1 interface are discarded due to paging
 Optimization 1: Prolong the duration of the UE inactivity timer (by running MOD RRCCONNSTATETIMER on the
eNodeB), prolong UE online duration, and reduce the number of paging messages sent over the air interface.
EPC EPC
eNodeB eNodeB
Cell Cell Cell Cell

TAC
Idle mode Connection mode
Principle: When the UE is in connection mode, the EPC does not send the paging message to all the
cells listed in the TAC. Instead, the EPC sends the signaling to relevant cells, which significantly reduces
the paging capacity.
Increased UE power consumption and eNodeB signaling processing caused by the prolonged UE
inactivity timer duration can be solved by technologies, such as DRX.

Interface Are Discarded or the eNodeB Experiences Internal
Exception (Cont.)
1. Paging messages sent over the S1 interface are discarded due to paging
 Optimization 2: Divide a TAC area into multiple TAC areas.
Advantage: Reduce the paging messages sent over the air
interface.
Disadvantages:
TAC division results in TAU increasing, which then
TAC1 TAC2
increases system load.
UEs at cell edges perform TAUs multiple times, decreasing
the paging success rate.
TAC division is difficult to be implemented, especially on
MOCN-enabled networks. This is because data of two
EPCs needs to be modified.
 Optimization 3: Check whether UEs are paged based on S-TMSI in the CS domain
and preferentially sends the paging message to eNodeBs in the TAC area.
When a UE is paged in the CS domain, the paging message must be preferentially sent to eNodeBs in
the TAC area. If the UE cannot be paged, the paging message is sent to all eNodeBs on the entire
network. In this case, the number of sent paging messages is reduced.

(Cont.)
2. RRC connection establishment success rate for RRC request with the cause
value MT-ACCESS decreases.
Cause Criterion Solution
The eNodeB determines that paging Check whether the success rate of RRC connection Increase the RRC
messages are successfully sent over the air establishment with the cause value MT-ACCESS decreases. connection establishment
interface when it receives an RRC The eNodeB processes RRC connection requests with different success rate by following
connection request with the cause value cause values in the same way, which means that only the the instructions provided in
MT-ACCESS from the UE. However, the success rate of RRC connection establishment with the cause OMD_LTE TDD Network
MME determines that the paging is value MT-ACCESS decreases is impossible. Access Fault Diagnosis
successful when it receives a NAS message Guide-20130315-A-3.0.
from the UE in response to the paging
message.
3. RRC connection establishment with the cause value MT-ACCESS is successful

but the service layer of the EPC does not receive the paging response.
The eNodeB does not send or the MME does Start S1 interface tracing on the eNodeB and Refer to OMD_LTE TDD Network Access
not receive the paging response. MME and use Wireshark to capture data Fault Diagnosis Guide-20130315-A-3.0.
packets sent over the S1 interface.
In MOCN-enabled or S1-FLEX networks, the Start S1 interface tracing on the eNodeB Perform further analysis according to site
paging response is sent to another MME. side. The tracing results show that the paging requirements.
response is sent to another EPC other than
the EPC that sends the paging message.

Action 2: Checking Whether Paging Messages Are Failed to
be Sent over the Air Interface
Characteristic: The UE paged is served by the
eNodeB. Due to an eNodeB internal exception
or poor network coverage, the eNodeB does
not receive the RRC connection request with
the cause value MT-ACCESS from the UE.
Causes
The paging message is not sent to the UE
over the air interface due to an eNodeB
internal exception.
The UE does not receive the paging message
sent over the air interface or the eNodeB does
not receive the RRC connection request sent
by the UE due to poor network coverage,
paging black hole, eNodeB hardware fault, or
sleeping cell.
TAU and cell reselection or inter-RAT cell
reselection of the UE are too frequent.
The paging message is not sent to the UE due
to paging congestion (paging channel capacity
limitation).
Rules: Rectify eNodeB internal faults and
optimize paging over the air interface.

be Sent over the Air Interface (Cont.)
1. eNodeB internal exception

An internal Check whether the value of L.Paging.UU.Att is Submit signaling
module of much smaller than that of L.Paging.S1.Rx. If the messages sent over
the eNodeB value of L.Paging.UU.Att is much smaller than that standard interfaces
is of L.Paging.S1.Rx, paging messages are and one-key logs.
abnormal. discarded by the eNodeB.

2. Weak coverage, paging black hole, eNodeB hardware fault, sleeping cell,
or cell unavailability
 Analysis procedure
Filter paging black hole cells based on the EPC statistics and logs. This operation
may not be useful if the EPC and E-UTRAN are provided by different vendors.
Find out weak coverage points in the paging cell. (Find out weak coverage point by
testing signal on roads at cell edges and detect the onsite wireless environment.
Optimize signal coverage based on different causes.)
 Causes
Incorrect parameter configuration, incorrect antenna angle, capacity insufficiency,
hardware fault, weak coverage, and cell unavailability
 Solution
Modify the parameters, adjust the antenna angle, expand the capacity, replace the
hardware, cover weak coverage holes, and solve cell unavailability.
If the cell is a sleeping cell, solve the problem by following the instructions
provided in Cell Outage Detection and Compensation(eRAN3.0).

3. Frequent TAU or intra-system or inter-system cell reselection for the UE in
idle mode
After the UE in idle mode enters a new TAC area, the Check whether TAU is frequent Divide TAC areas and capacity according to
UE initiates TAU. If the UE is paged at this time, the based on the traffic volume. TAC planning.
paging message sent from the EPC contains the old
TAC of the UE, and the eNodeB sends the paging
message to all cells in the old TAC.
The UE in idle mode reselects between the G/U/L Check whether ping-pong Check cell selection and reselection
networks frequently due to improper parameter reselection occurs based on the parameters to prevent ping-pong
settings. traffic volume. reselection.
If a UE in idle mode is called while it is being handed Check parameter settings. Check cell selection and reselection
over from one cell to another, paging fails. In normal parameters to prevent ping-pong
cases, paging is interrupted for about 50 ms during cell reselection.
reselection.
4. Paging congestion (paging channel capacity limitation)

 The maximum paging message processing capacity of the main control board is 500 paging
messages per second, which is much smaller than the processing capacity of the paging channel
1200 paging messages per second with 2% paging congestion. The probability of paging
messages discarded due to limited paging channel capacity is low, much lower than 1%.

Action 3: Checking Whether the Paging Success Rate on the
EPC Side Is Normal, and the Paging Success Rate on the
eRAN Side Decreases
1. The measurement range of the EPC and eRAN is inconsistent.
The measurement range for paging Check parameter configuration on Explain to the customer that the paging success
messages is different between the EPC and the EPC side. rate on the EPC side represents the paging
eRAN, or the eRAN does not count paging Confirm the eRAN measurement success rate that the UE experienced, and explain
messages of all cells in the TAC. range. to the customer why paging success rate on the
eRAN side is low.
2. Initial paging success rate on the EPC side decreases but the repeated
paging success rate increases.
Cause Identification Method Solution
The initial paging success rate on the EPC side Check statistics on the EPC side. In normal cases, first paging failures are
decreases and the repeated paging success rate caused by the air interface. Troubleshoot
increases. The formulas for calculating the paging this fault by following the instructions
success rate on the eNodeB and MME is different. As provided in Action 2.
a result, the paging success rate on the eNodeB side Explain to the customer that the paging
decreases. success rate on the EPC side represents
In normal cases, some paging messages fail to be sent the paging success rate that the UE
for the first time due to the air interface. However, the experienced, and explain to the customer
second or third paging is successful. why paging success rate on the eRAN side
is low.

Analysis of Paging Impact on Service Connection
When a UE on the LTE network serves as the calling party, the call connection delay is short: If
authentication is not required, the delay is less than 100 ms. When the UE serves as the called party,
the delay is longer than 640 ms due to paging. The DRX cycle is set to 1.28s by default.
If the first paging fails and the EPC initiates the second paging, the delay prolongs as the paging
interval is controlled by the T3413 timer and PAGINGDELTA parameter. Ensure that the UE can be
paged at the first time, especially for CS paging.
If the initial paging success rate is Check the initial Improves the initial paging success
less than 96% and the paging paging success rate rate by following the instructions
interval is set to a value greater on the EPC side. provided in the preceding section.
than 3s, call delays for UEs that Check the paging Set the paging retransmission interval
are failed to be paged for the first retransmission to a smaller value.
time prolong. interval.
The paging DRX cycle is Check the DRX cycle Set the paging DRX cycle to 640 ms
changed. value. so that the paging delay can be
optimized to 320 ms.

Contents

Case 1: Number of Paging Messages over the Uu
and S1 Interfaces Are Different
Symptom: During xx site maintenance, the maintenance personnel find that the number of paging messages over
the Uu interface is much less than that over the S1 interface.
Checking procedure
This problem occurs randomly.
In eRAN3.0, paging messages are not retransmitted over the Uu interface. Theoretically, the number of paging
messages over the Uu interface is the same as that over the S1 interface. If the paging messages sent over the Uu
and S1 interfaces are different, the eNodeB discards paging messages due to flow control or TAC inconsistency.
Problem analysis
According to DBG logs, time on the baseband board is adjusted in time segments when the paging messages sent
over the Uu and S1 interfaces are different. Therefore, this problem may be caused by time adjustment.
Paging over the S1 interface is measured on the main control board whereas paging over the Uu interface is
measured on the baseband board. Due to a defect in eRAN3.0, the number of paging messages measured over the
Uu interface is less than the actual paging messages sent over the Uu interface. Therefore, the number of paging
messages over the Uu interface is less than that over the S1 interface.

Thank you
www.huawei.com

Huawei LTE TDD Paging Fault Locating and Optimization Guide

Uploaded by

Document Information

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 LTE TDD Paging Fault Locating and Optimization Guide

Uploaded by

Copyright:

Available Formats

Security Level: Internal Only

LTE TDD Paging Fault

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

 This document describes the basic paging principles, locating

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 4

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page5

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page6

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page7

 Paging-related parameters for the eNodeB

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page8

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page9

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page10

Paging success rate on the EPC side = (Number of paging responses in

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 14

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15

Faults occur in , , and  will decrease paging

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 16

Paging success rate on the EPC Action 1: Check whether paging

EPC paging success rate

EPC paging success rate

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 17

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 18

Cause Identification Method Solution

eNodeB main ALM-26202 BOARD In eRAN3.0 SPC320, paging

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 19

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 20

Cell Cell Cell Cell

Idle mode Connection mode

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 21

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 22

3. RRC connection establishment with the cause value MT-ACCESS is successful

Cause Criterion Solution

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 23

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 24

1. eNodeB internal exception

Cause Criterion Solution

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 25

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 26

Cause Criterion Solution

4. Paging congestion (paging channel capacity limitation)

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Cause Criterion Solution

Cause Identification Method Solution

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Cause Criterion Solution

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 30

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 31

You might also like