Professional Documents
Culture Documents
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.
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.
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.
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.
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.
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.
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
Is RRC or
ERAB
Setup SR
low?
True
True
True
True
UE
abnormal True Problem False
? solved?
End
EnodeB
Correct cell parameters
cell False
configuration.
parameter
correct?
True
True
True
True
End
Random
access errir
occurs?
True
Authenticat
UE mismatches EnodeB does not
ion/encrypt
the Re-auth receive msg3
ion
request message
parameter
correct?
Multiple UEs
The enodeB The EnodeB The UE is
The UL path loss initiate
does not does not located
downlink bit is random
receive any send the re- beyond the
error rate is excessively access
preamble auth request cell
high large simultaneou
from the UE. message coverage sly and
preamble
collition
occurs
Power
transmission The
Coverage is
for the preamble
facing
preamble of transmission
problems.
the UE is time out.
low.
Problem False
solved?
True
End