LTE access check and improvement

1.
Introduction

If an access fault occurs, UEs have difficulty accessing the network due to radio resource control (RRC)
connection setup failures or E-UTRAN radio access bearer (E-RAB) setup failures.

1.1 Background Information

This section provides counters and alarms related to access faults, and methods for analyzing TopN cells.

In Long Term Evolution (LTE) networks, access faults occur either during radio resource control (RRC)
connection setup or during E-UTRAN radio access bearer (E-RAB) setup. The access success rate is a key
performance indicator (KPI) that quantifies end user experience. An excessively low access success rate
indicates that end users have difficulty making mobileoriginated or mobile-terminated calls.

1.2 Related Counters

 RRC Connection Setup Measurement (Cell)(RRC.Setup.Cell)
 RRC Connection Setup Failure Measurement (Cell)(RRC.SetupFail.Cell)
 E-RAB Setup Measurement (Cell)(E-RAB.Est.Cell)
 E-RAB Setup Failure Measurement (Cell)(E-RAB.EstFail.Cell)
1.3 Related Alarms
 Hardware-related alarms
– ALM-26104 Board Temperature Unacceptable
– ALM-26106 Board Clock Input Unavailable
– ALM-26107 Board Input Voltage Out of Range
– ALM-26200 Board Hardware Fault
– ALM-26202 Board Overload
– ALM-26203 Board Software Program Error
– ALM-26208 Board File System Damaged
 Temperature-related alarms
– ALM-25650 Ambient Temperature Unacceptable
– ALM-25651 Ambient Humidity Unacceptable
– ALM-25652 Cabinet Temperature Unacceptable
– ALM-25653 Cabinet Humidity Unacceptable
– ALM-25655 Cabinet Air Outlet Temperature Unacceptable
– ALM-25656 Cabinet Air Inlet Temperature Unacceptable
 Link-related alarms
– ALM-25880 Ethernet Link Fault
– ALM-25886 IP Path Fault
– ALM-25888 SCTP Link Fault
– ALM-25889 SCTP Link Congestion
– ALM-26233 BBU CPRI Optical Interface Performance Degraded
– ALM-26234 BBU CPRI Interface Error
– ALM-29201 S1 Interface Fault
– ALM-29211 Excessive Packet Loss Rate in the Transmission Network
– ALM-29212 Excessive Delay in the Transmission Network
– ALM-29213 Excessive Jitter in the Transmission Network
 RF-related alarms
– ALM-26239 RX Channel RTWP/RSSI Unbalanced Between RF Units

Interne Groupe Sonatel

 – ALM-26520 RF Unit TX Channel Gain Out of Range
– ALM-26521 RF Unit RX Channel RTWP/RSSI Too Low
– ALM-26522 RF Unit RX Channel RTWP/RSSI Unbalanced
 Configuration-related alarms
– ALM-26245 Configuration Data Inconsistency
– ALM-26243 Board Configuration Data Ineffective
– ALM-26812 System Dynamic Traffic Exceeding Licensed Limit
– ALM-26815 Licensed Feature Entering Keep-Alive Period
– ALM-26818 No License Running in System
– ALM-26819 Data Configuration Exceeding Licensed Limit
– ALM-29243 Cell Capability Degraded
– ALM-29247 Cell PCI Conflict
1.4 TopN Cell Selection

TopN cells can be selected by analyzing the daily KPI file exported by the M2000.

 TopN cells with the largest amounts of failed RRC connection setups (L.RRC.ConnReq.Att -
L.RRC.ConnReq.Succ) and lowest RRC connection setup success rates
 TopN cells with the largest amounts of failed E-RAB setups and lowest E-RAB setup success rates
1.5 Tracing TopN Cells

After finding out topN cells and the periods when they have the lowest success rates, start Uu, S1, and X2
interface tracing tasks and check the exact point where the RRC connection or ERAB setup fails.

In addition, after the Evolved Packet Core (EPC) obtains the international mobile subscriber identity (IMSI) of
the UE with the lowest success rate based on the UE's temporary mobile subscriber identity (TMSI), you can
start a task to trace the UE throughout the whole network.

1.6 Analyzing Environmental Interference to TopN Cells

Environmental interference to a cell consists of downlink (DL) interference and uplink (UL) interference to the
cell. The following methods can be used to check the environmental interference:

 To check DL interference, use a spectral scanner. If both neighboring cells and external systems may
cause DL interference to the cell, locate the exact source of the DL interference.
 To check UL interference, start a cell interference detection task and analyze the result.
2. Troubleshooting Method

This section describes how to identify and troubleshoot the possible cause.

2.1 Possible Causes

Scenario Fault Description Possible Causes

1- The UE cannot search
cells. 1-Parameters of the UE or eNodeB are incorrectly
The RRC
2- A fault occurs in radio configured.
connection fails
interface processing. 2- The radio environment is abnormal.
to be set up.
3- Top user problems 3- The UE is abnormal.
occur.
1- Resources are 1- Parameters of the UE or eNodeB are incorrectly
The E-RAB fails
insufficient. configured.
to be set up.
2- A fault occurs in radio 2- The radio environment is abnormal.

Interne Groupe Sonatel

 interface processing. 3- Parameters of the Evolved Packet Core (EPC) are
3- Top user problems incorrectly configured.
2.2 Troubleshooting Procedure
1. Select topN cells.
2. Check whether parameters of the UE or eNodeB are incorrectly configured.
a. Yes: Correct the parameter configurations. Go to 3.
b. No: Go to 4.
3. Check whether the fault is rectified.
a. Yes: End.
b. No: Go to 4.
4. Check whether the radio environment is abnormal.
a. Yes: Handle abnormalities in the radio environment. Go to 5.
b. No: Go to 6.
5. Check whether the fault is rectified.
a. Yes: End.
b. No: Go to 6.
6. Check whether parameters of the EPC are incorrectly configured.
a. Yes: Correct the parameter configurations. Go to 7.
b. No: Go to 8.
7. Check whether the fault is rectified.
a. Yes: End.
b. No: Go to 8.
8. Contact provider technical support.
2.3 Troubleshooting Access Faults Due to Incorrect Parameter Configurations

This section provides information required to troubleshoot access faults due to incorrect parameter
configurations. The information includes fault descriptions, background information, possible causes, fault
handling method and procedure, and typical cases.

2.3.1 Fault Description

 The UE cannot receive broadcast information from the cell.
 The UE cannot receive signals from the cell.
 The UE cannot camp on the cell.
 The end user complains about an access failure, and the value of the performance counter
L.RRC.ConnReq.Att is 0.
 An RRC connection is successfully set up for the UE according to standard interface tracing results, but
then the mobility management entity (MME) releases the UE because the authentication procedure
fails.
 The end user complains that the UE can receive signals from the cell but is unable to access the cell.
 According to the values of the performance counters on the eNodeB side, the number of RRC
connections that are successfully set up is much greater than the number of E-RABs that are
successfully set up.
 According to the KPIs, the E-RAB setup success rate is relatively low, and among all cause values, the
cause values indicated by L.E-RAB.FailEst.TNL and L.E-RAB.FailEst.RNL contribute a large proportion.
2.3.2 Possible Causes
 Cell parameters are incorrectly configured. For example, the E-UTRA absolute radio frequency number
(EARFCN), public land mobile network (PLMN) ID, threshold used in the evaluation of cell camping,
pilot strength, and access class.

Interne Groupe Sonatel

  The UE has special requirements for authentication and encryption.
 Parameters of the subscriber identity module (SIM) card or registration-related parameters on the
home subscriber server (HSS) are incorrectly configured.
 The authentication and encryption algorithms are incorrectly configured on the Evolved Packet Core
(EPC).
 The IPPATH or IPRT managed objects (MOs) are incorrectly configured.
2.3.3 Fault Handling Procedure
1. Check whether cell parameters are incorrectly configured. Pay special attention to the following
parameter settings as they are often incorrectly configured: the EARFCN, PLMN ID, threshold used in
the evaluation of cell camping, pilot strength, and access class.
a. Yes: Correct the cell parameter configurations. Go to 2.
b. No: Go to 3.
2. Check whether the fault is rectified.
a. Yes: End.
b. No: Go to 3.
3. Check the type and version of the UE and determine whether the authentication and encryption
functions are required.
a. Yes: Enable the authentication and encryption functions. Go to 4.
b. No: Go to 5.
4. Check whether the fault is rectified.
a. Yes: End.
b. No: Go to 5.
5. Check whether parameters of the SIM card or registration-related parameters on the HSS are
incorrectly configured. The parameters of the SIM card include the K value, originating point code
(OPC), international mobile subscriber identity (IMSI), and whether this SIM card is a UMTS SIM (USIM)
card.
a. Yes: Correct the parameter configurations. Go to 6.
b. No: Go to 7.
6. Check whether the fault is rectified.
a. Yes: End.
b. No: Go to 7.
7. Check whether the authentication and encryption algorithms are incorrectly configured on the EPC.
For example, check whether the switches for the algorithms are turned off.
a. Yes: Modify the parameter configuration on the EPC. Go to 8.
b. No: Go to 9.
8. Check whether the fault is rectified.
a. Yes: End.
b. No: Go to 9.
9. Check whether the IPPATH or IPRT MOs are incorrectly configured.
a. Yes: Correct the MO configurations. Go to 10.
b. No: Go to 11.
10. Check whether the fault is rectified.
a. Yes: End.
b. No: Go to 11.
11. Check whether the fault can be diagnosed by tracing the access signaling procedure.
a. Yes: Handle the fault. Go to 12.
b. No: Go to 13.
12. Check whether the fault is rectified.
a. Yes: End.
b. No: Go to 13.

Interne Groupe Sonatel

 13. Contact provider technical support.
2.4 Troubleshooting Access Faults Due to Radio Environment Abnormalities

This section provides information required to troubleshoot access faults due to radio environment
abnormalities. The information includes fault descriptions, background information, possible causes, fault
handling method and procedure, and typical cases.

2.4.1 Fault Description

 During a random access procedure, the UE cannot receive any random access responses.
 During an RRC connection setup process, the eNodeB has not received any RRC connection setup
complete messages within the related timeout duration.
 During an E-RAB setup process, the response in security mode times out.
 The eNodeB has not received any RRC connection reconfiguration complete messages within the
related timeout duration.
 At the eNodeB side, both the RRC connection setup success rate and the E-RAB setup success rate are
low.
2.4.2 Background Information

Radio environment abnormalities include radio interference, imbalance between the uplink (UL) and downlink
(DL) quality, weak coverage, and eNodeB hardware faults (such as distinct antenna configurations). The items
to be investigated as well as the methods of investigating these items are described as follows:

 Investigating radio interference: DL interference from neighboring cells, DL interference from external
systems, and UL interference need to be investigated. To investigate the DL interference, use a
spectral scanner. To investigate the UL interference, start a cell interference detection task.
 Investigating weak coverage: The reference signal received power (RSRP) values reported by UEs
during their access need to be investigated. If most of these values are relatively low, it is highly
probable that the access difficulties lie in the weak coverage provided by the cell. The actual radius of
cell coverage as well as the signal quality variation need to be investigated so that users can determine
whether wide coverage or cross-cell coverage occurs.
 Investigating the imbalance between UL and DL quality: The transmit power of the remote radio unit
(RRU) and UE need to be investigated to check whether UL or DL limitations have occurred, because
imbalance between UL and DL quality is caused by UL limitations or DL limitations. The UL and DL radii
of cell coverage need to be investigated using drive tests.
 Investigating eNodeB hardware: If two antennas are used, the tilt and azimuth of each antenna need
to be investigated. If their tilts or azimuths are significantly different from each other, adjust them so
that their tilts and azimuths are the same. The jumper connection needs to be investigated by
analyzing drive test results. If the jumper is reversely connected, the UL signal level will be much lower
than the DL signal level in the cell, in which case UEs remote from the eNodeB will easily encounter
access failures. Therefore, if the jumper is reversely connected, rectify the jumper connection. The
physical conditions of feeders need to be investigated. If a feeder is damaged, water immersed,
bending, or not securely connected, a large number of call drops will occur. If a voltage standing wave
ratio (VSWR) alarm is reported, such problems exist and you need to replace the faulty feeder.
2.4.3 Possible Causes
 The cell provides weak coverage.
 The UE does not use the maximum transmit power.
 Inter-modulation interference exists.
 The UE is located at cell edge.
2.4.4 Fault Diagnosis

Interne Groupe Sonatel

To effectively diagnose access faults due to radio environment abnormalities, you are advised to firstly find out
whether this fault is caused by radio interference or weak coverage. The following procedure is recommended:

2.4.5 Fault Handling Procedure

1. Check whether related alarms are reported.
a. Yes: Handle these alarms. Go to 2.
b. No: Go to 3.
2. Check whether the fault is rectified.
a. Yes: End.
b. No: Go to 3.
3. Check whether interference exists. By using a spectral scanner, check whether there is DL interference
from neighboring cells or external systems. By analyzing the cell interference detection result, check
whether there is UL interference.
a. Yes: Minimize the interference. Go to 4.
b. No: Go to 5.
4. Check whether the fault is rectified.
a. Yes: End.
b. No: Go to 5.
5. Check whether the transmit power of the RRU and UE falls beyond link budgets.
a. Yes: Adjust the UL and DL transmit power. Go to 6.
b. No: Go to 7.
6. Check whether the fault is rectified.
a. Yes: End.
b. No: Go to 7.
7. Check whether cell coverage is abnormal.
a. Yes: Based on the RSRP distribution of the UEs attempting to access the cell, investigate and
handle possible coverage, interference, and imbalance between UL and DL quality by using
drive tests. Go to 8.
b. No: Go to 9.
8. Check whether the fault is rectified.
a. Yes: End.
b. No: Go to 9.
9. Contact provider technical support.
3. Diagram

Interne Groupe Sonatel

Ma
 rre
Co
rec
ct
rre
tiv
par
ct
e
am
par
act
ete
am
ion
rs
etes
wr
rs
of
on
Sta
En
wr
RF
Fals
Tru g
Tru
Fals
on
(ref
rt
d
eeco
erg
nfi
co
to
gur
nfi
rel
ati
gur
eva
on
ati
nt
in
on.
do
EPIs
cu
C.RR
me
nt)C
or
ER
AB
Set
up
SR
low
?

En
od
e
Par
am
ete
rs
cor
rec
t?

RF
che
ck
do
ne
an
d
nor
mal
?

EP
C
par
am
ete
r
cor
rec
t?

UE Pro
ab ble
nor m
mal sol
? ved
?

Start Interne Groupe Sonatel

 parameter False Correct cell parameters configuration.
correct?

True

Authenticati Enable/disable (align)

on/encrypti False encryption/authentication parameters
on between UE and Network.
parameter
correct?

True

Parameters
for EPC- False
Correct interconnection parameters
NodeB between EnodeB and EPC
connection
correct?

True

IPPATH
and IPRT False Correct MOs configuration
MOs
correct?

True

True Problem False

Make signaling trace and analysis.
solved?

End

Start

Random
Interne Groupe Sonatel
access errir
occurs?

True
 Authenticati
UE mismatches the EnodeB does not
on/encrypti
Re-auth request receive msg3
on
message
parameter
correct?

True True True

Multiple UEs
initiate
The enodeB The EnodeB random
does not The UE is UL path loss
The downlink does not access
receive any located is
bit error rate send the re- simultaneous
preamble beyond the excessively
is high auth request ly and
from the UE. cell coverage large
message preamble
collition
occurs

Power
transmission Coverage is The preamble
for the facing transmission
preamble of problems. time out.
the UE is low.

Problem False
solved?

True

End

Interne Groupe Sonatel

Interne Groupe Sonatel