1) ACCESSIBILITY SOLVE Parameter configuration issues

RRC Faults -Cell Parameters are incorrectly configured: EARFCN, PLMN

-UE cannot search cells -UE with special requirements for Authentication this is just
-Authentication fails -SIM card or registration-related Parameters on HSS are inco
-A fault in RF -Authentication and encryption algorithms are incorrectly c
-IP path related Parameters are incorrectly configured this i

ERAB Faults RF environment issues

-Resources are insufficient -RF interference: DL interference from neighbouring cells, D
-Weak coverage: if RSRP values reported by UEs are relative
-Imbalance between UL and DL power.
Possible Causes -eNodeB hardware: tilts and azimuth (if two antennas are p
-Parameters UE/eNodeB incorrectly configured
-RF environment abnormal
-EPC parameters incorrectly configured
-UE is abnormal
y configured: EARFCN, PLMN ID, threshold used in the evaluation of Cell camping, pilot strength, and access class.
for Authentication this is just for certain user failures.
d Parameters on HSS are incorrectly configured this is just for certain user failures.
n algorithms are incorrectly configured on the EPC this is for certain user or massive failures.
e incorrectly configured this is for all the setup attempts in certain nodeRF environment issues.

ce from neighbouring cells, DL interference from external systems, and UL interference, etc.
s reported by UEs are relatively low, it is highly probable that issue is weak coverage (lack of coverage or cross-cell coverage)

zimuth (if two antennas are placed, they should have same tilt and azimuth), physical connectors, patch cords, etc.
oss-cell coverage)
Power Adjustment Method:

Subcarriers share the transmit power of an eNodeB, and therefore the transmit power of each subcarrier depends on
the configured system bandwidth (such as 5 MHz and 10 MHz). A larger bandwidth will result in lower power of each subcarrie
power.?
A: indicates the ratio of the data subcarrier power of OFDM symbols excluding pilot symbols to the pilot subcarrier power.?
B: indicates the ratio of the data subcarrier power of OFDM symbols including pilot symbols to the pilot subcarrier power.
Service power configuration (calculating PDSCH power based on RS power): RS power PA and PB are delivered using RRC signal
For two antennas, PA is ?A and ?B is calculated based on the below table.
PDSCH power is calculated based on PA and PB. Currently, it is recommended that PB be set to 1 dB and PA be set to -3 dB. Tha
including pilot symbols accounts for 1/3. This setting optimizes network performance and ensures that the pilot power for Type
to the service channel power. In scenarios with special requirements,

for example, in rural scenarios requiring low edge rates, PB can be set to 2 or 3 dB to enhance coverage.
subcarrier depends on
n lower power of each subcarrier. LTE uses PA and PB parameters to adjust

o the pilot subcarrier power.?

the pilot subcarrier power.
PB are delivered using RRC signalling.

1 dB and PA be set to -3 dB. That is, the pilot power for symbols
ures that the pilot power for Type A and Type B symbols are equivalent
 3)eRAB Drops Single eNodeB faults
Whole network faults -Performance counters are abnormal for certain Cell
-Performance counters are abnormal -Alarms reported
-Alarms reported

SOLVEFor Whole Network:

-Check cutover, replacement, upgrade, or patch installation
-Check eNodeB Parameters changes for A big amount of cells
-Check traffic volumeRF faults
-Caused by faults such as the number of RLC retransmissions reaching the maximum, UE uplink out-of-synchronization, or signa
-Weak coverage
-UL interference
-UE exceptions

TXON faults
-Caused by TXON exceptions between eNodeB and MME
-Check TXON related Alarms

Congestion
-Any resource reaches the limit
-Capacity expansion
-Recommended action: Enable MBL
-Possible other actions: make easier outgoing HO and harder incoming HO; reduce power; increase minimum required level; re

HO Failures

-Check parameter settings for destination cells with HO failures

-Check parameter settings for origin Cell if all destination cells are failing
-See HO sections

MME Faults
-it has to be identified on the EPC side
 Possible Causes
-Data transmission is abnormal
-Network planning is improper
-EPC works abnormally (for whole Network fault)
-Insufficient Resources (for single Cell)
-Weak coverage (for single Cell)
-interference (for single Cell)

k out-of-synchronization, or signalling procedure failures

ease minimum required level; reduce bit rate; reduce resources assignment
4)Inter-RAT HO

-SR of IRAT HO is low

Possible Causes
-UE does not support IRAT HO ???????????
-IRAT HO Parameters are wrongly configured
-EPC Parameters are wrongly configured
-Weak coverage or interference

SOLVE
-Review IRAT HO Parameters
-If no HO is performed: check destination cell(s) definition in EPC and origin cell definition in UMTS/GSM CN
-if LTE Cell is interfered, See interference problems solutions
-If UMTS/GSM destination cell is interfered -> proceed to solve UMTS/GSM interference
MTS/GSM CN
5)Rate faults

A common way to find a cause is as follows: First, check whether the service involved is a UDP service or a TCP service. If it is a
inject uplink and downlink UDP packets on a single thread and check whether the uplink and downlink UDP rates can reach the
the way" for TCP rate fault diagnosis. For example, eliminate rate limiting at the network adapter and rectify radio parameter s
faults. If the service involved is a UDP service, locate the fault by investigating link from the server to the UE in an end-to-end m
Second, if the UDP rate can reach its peak value but the TCP rate cannot, the fault exists in the TCP transmission mechanism. T
but I dont understand properly yet; there is also a detailed procedure for this.

SOLVE
Single UE abnormal rate
-fault in the Data source at the server
-TXON problems or bottleneck (Check bandwidth is correctly set along the transmission link and transmission bandwidth on th
-RF faults: eNodeB alarms related to RF, signal quality (RSRP and SINR; BLER higher than 10% channel condition is poor), param
is connected to the appropriate CQI; check algorithms), problems caused by multiple UEs online (very high number of users), li
Does LTE work with similar to channel elements components, as UMTS does?
-fault in the UE or PC connected to UE
-TCP parameter setting, TCP transmission fault

Multiple UE abnormal rates

-TXON problems or bottleneck (check bandwidth is correctly set along the transmission link and transmission bandwidth on th
greater than the peak value)

-RF faults: eNodeB alarms related to RF, signal quality (RSRP and SINR; BLER higher than 10% channel condition is poor; UL inte
(data services user is connected to the appropriate CQI; check algorithms), problems caused by multiple UEs online (very high
service or a TCP service. If it is a TCP service,
ownlink UDP rates can reach their peak values. The purpose is to "clear
er and rectify radio parameter setting errors before handling TCP rate
ver to the UE in an end-to-end manner.
TCP transmission mechanism. This has been copied from the source,

d transmission bandwidth on the transmission link is greater than the peak value)
hannel condition is poor), parameter setting errors (data services user
e (very high number of users), license issues, and UL interference (RSSI)

d transmission bandwidth on the transmission link is

hannel condition is poor; UL interference RSSI), parameter setting errors

y multiple UEs online (very high number of users), license issues, and UL interference (RSSI)