6. Figure 4-43 Workflow of Analysis on Missed Matching of Neighboring Cells................................49
Figure 4-44 Signaling in Case of No Response for Measurement Report.....................................50
Figure 4-45 Analysis on Missed Matching of Neighboring Cells -1 ...............................................51
Figure 4-46 Analysis on Missed Matching of Neighboring Cells -2 ...............................................51
Figure 4-47 Analysis on Missed Matching of Neighboring Cells -3 ...............................................52
Figure 4-48 Analysis on Missed Matching of Neighboring Cells -4 ...............................................53
Figure 4-49 Handover Restores after Elimination of Missed Matching..........................................53
Figure 4-50 Ping-Pong Handover ..................................................................................................55
Figure 4-51 Workflow of Elimination of Ping-Pong Handover Problem .........................................56
Figure 4-52 Analysis on Ping-Pong Handover Problem ................................................................57
Figure 4-53 Signaling Process of Handover on Control Plane ......................................................59
Figure 4-54 Overtime Handover.....................................................................................................61
Figure 4-55 Workflow of Solving the Handover Failure Problem...................................................62
Figure 4-56 Handover Failure ........................................................................................................63
Figure 4-57 Analysis of Handover Failure -1 .................................................................................63
Figure 4-58 Analysis of Handover Failure -2 .................................................................................64
Figure 4-59 SINR Value after Adjustment of Antenna Downtilt .....................................................65
Figure 4-60 Workflow of Analyzing Traffic Problem.......................................................................66
Figure 4-61 Cells Whose Maximum Traffic is Less than 5M..........................................................68
Figure 4-62 DT Test Data of Area 1...............................................................................................68
Figure 4-63 DT Test Data of Area 2...............................................................................................69
Figure 4-64 Cells Whose Average Traffic Ranges from 5M to 10M ..............................................71
Figure 4-65 DT Test Data -1 ..........................................................................................................71
Figure 4-66 DT Test Data -2 ..........................................................................................................72
Figure 4-67 DT Test Data -3 ..........................................................................................................73
Figure 4-68 DT Test Data -4 ..........................................................................................................74
Figure 4-69 Cause Analysis Procedure for Call Failures...............................................................75
Figure 4-70 Procedure for Troubleshooting an RRC Connection Establishment Problem............77
Figure 4-71 Authentication Failure Message (Cause Value: MAC Failure)...................................81
Figure 4-72 Authentication Failure Message (Cause Value: Synch Failure) .................................82
Figure 5-1 OMM-Level Performance Statistics Analysis Procedure..............................................89
Figure 5-2 Cell-Level Performance Statistics Analysis Procedure ................................................90
Figure 5-3 RRC Connection Establishment Procedure .................................................................91
Figure 5-4 Initial E-RAB Connection Establishment Procedure.....................................................94
Figure 5-5 Initial Context Setup Procedure....................................................................................99
Figure 5-6 E-RAB Setup Procedure...............................................................................................99
Figure 5-7 Handover Process Diagram ..........................................................................................101
Figure 5-8 Signaling Process Diagram of Handover Inside the eNB .............................................103
Figure 5-9 X2 Handover Signaling Process Diagram.....................................................................104
Figure 5-10 S1 Handover Signaling Process Diagram...................................................................105
Figure 5-11 Process of Analyzing Handover Problem....................................................................107
Figure 5-12 Process Flow When No Handover Command Received upon the Sent Measurement
Report ........................................................................................................................109
Figure 5-13 Process of Analyzing Msg1 Problem ..........................................................................110
Figure 5-14 Process of Analyzing RAR Problem............................................................................110
Figure 5-15 LTE Call Drop Problem-Solving Workflow ..................................................................116
8. 1 INTRODUCTION
The document presents the solution of FDD LTE radio network optimization for
Wireless Network.
The construction of the wireless communication network is a gradual, dynamic
process. After a period of operation, with the increase of subscribers,
environment transformation and some other uncontrollable factors, there would
be decrease of connection success ratio, fall of call quality and faded signals etc.
The formerly planned network can no longer keep pace with the rapid
development. To make adjustments and expansion of the systemic resources
and related parameters, that is scope of network optimization.
The objective of this document is to describe:
Network optimization preparation
Network Optimization process
Cluster Optimization
OSS KPI Optimization
2 NETWORK OPTIMIZATION PREPARATION
Before the network optimization, the RNO (Radio Network Optimization)
manager should assure that manpower and equipments are available. At the
same time the optimization schedule should be made and the following
information is collected:
Radio network planning report;
Latest site configuration table and radio parameter configuration table;
OMM statistic data;
Subscriber complaints of the existing network;
Requirements for network performance targets, including specific requirements for
the coverage, capacity and QoS of the network;
The responsibility matrix definition
The project acceptance criteria.
10. 2.2.1 CNT
ZXPOS CNT is an advanced wireless network air interface test tool. It is used
for trouble shooting, evaluation, optimization, and maintenance of the mobile
network. This tool integrates the professional and final-user senses and feelings,
completely tests and analyzes the self-network and that of the competitors, and
provides precise measurement means for various network KPIs.
ZXPOS CNT supports all standards of 2G (GSM/GPRS/EDGE, CDMA IS95/1X),
3G (TD-SCDMA, WCDMA, CDMA2000), and 4G (LTE) networks and various
frequency bands of 900/1800/2100/2600MHz, 850/1900MHz, and 450MHz.
Support LTE test services including Ping, FTP, HTTP, and TCP/UDP data service
test
Support LTE Qualcomm test terminal
Support CW, spectrum and TopN scan by PCTEL scanner
Support ms-level frame exporting function of key data
Support KPI real-time statistics
Support indoor and outdoor tests
Simple configuration, easy operation, stable and reliable for test
Support real-time statistics function to quickly obtain test results
Support tests of new techniques and new service quickly with continuous research
innovation capability to meet test requirements on new techniques of operators
2.2.2 CNA
ZXPOS CNA is an intelligent wireless network optimization analysis system. It
supports all 2G, 3G, and 4G networks such as
GSM/GPRS/EDGE/CDMA/EVDO/WCDMA/ HSDPA/HSUPA/TD-SCDMA/LTE.
ZXPOS CNA provides network oriented data processing and analysis report on
network optimization. ZXPOS CNA also provides multi-service QoS analysis for
multi-network quality evaluation.
The main function is as following:
Support LTE data analysis and processing
Support simultaneous loading and viewing of up to 108 test data
12. The service distribution
The same TAC region information
The sites in a cluster should not too many and the overlap between clusters is
needed. The definition of cluster should be confirmed by customer and ZTE
together.
3 NETWORK OPTIMIZATION PROCESS
In this section, three stages of optimization are introduced, and the high level
optimization plans are presented for each individual stage of network
implementation and performance acceptance. Items under consideration are
target of optimization, methods of optimization and output for optimization, etc.
3.1 Optimization Milestone
Figure 3-1: LTE Radio Network Optimization Milestone
Network Construction
Network Design
Soft Launch Optimization
Pre-Launch Optimization
Site Survey
Single Site Verification
Cluster Optimization
Installation & Commissioning & Test
Network Soft Launch
Start End
Launched Optimization
Network Commercial
Network Design Commissioning PAC FAC
LTE radio network optimizations include three major stages: Pre-launch
Optimization, Soft Launch Optimization and Launched Optimization.
The main objective of Pre-launch Optimization is to control RF network air
interference, assure network hardware functionality work normally, and ensure
the KPIs target of Preliminary Acceptance Test is achieved. Pre-launch
Optimization includes two steps:
1 Single Site Verification
2 Cluster Optimization
14. Table 3-1: Single Site Verification:
Equipment related Engineering related Configuration related
Abnormal power alarm
PA alarm
Transmission broken
Board related alarms
Internal/external link alarms
Antenna VSWR alarm
Clock source/GPS alarm
Cell/eNodeB down alarm
SW version alarm
…
Feeder
Loose connection of
connectors
Unreasonable antenna
position
Signal obstacle by buildings
Wrong antenna tilt and
azimuth
…
Center frequency
PCI
TAC
Cell status
Transmission
bandwidth
PRACH Configuration
…
Above mentioned problems are to be solved by corresponding technical staffs.
Most of equipment related problems are to be solved by base station engineers,
engineering related problems are to be solved by RF optimization engineers and
installation engineers together, and configuration related problems are to be
solved by RF optimization engineers and OMC engineers. After site verification,
it should be free of obvious problems that might cause the site incapable of
being put on air.
The SSV process is mainly based on stationary check and drive test, and the
former means performing desktop check on items according to configuration
data, or walking around the site using test UEs. For the stationary check,
needed materials are as the following list:
Technical Site Survey (TSS) report
Planned Engineering Parameters
Planned Radio Parameters
Site Configuration Parameters.
These materials might also be used in drive test verification of the site.
Before Single Site Verification, the critical and major level alarms for sites should
be eliminated. Most part of configuration related items can be fulfilled by
stationary check, whether the transmission bandwidth and center frequency
configuration can match the design requirement, whether the cell is in state of
reserved or barred, etc. The verification of some other items can also be
stationary as compared to drive test method. For example, the UL/DL frequency
assignment, the Physical Cell Identifier, the TAC of cells can be identified by
using a test UE with engineering mode, but these items can also be verified by
drive test. The drive test can be used to identify problems related to coverage,
handover, service accessibility and data throughput, which in turn will drill down
to problems related to engineering and configuration faults, such as feeders,
insufficient transmission bandwidth configuration, etc.
16. 3 Cluster Optimization Test Schedule
Generally the ratio of on-air eNodeB of one cluster is over 80%, the cluster
optimization can be executed. The prior cluster can be arranged to optimize first.
After the optimization suggestion is adopted, a new test schedule will be made
to do justify if it is effective.
4 Test Route Planning
Before cluster optimization, it is necessary to definite test route. It is required to
keep the continuous coverage along test route when not all of sites are on air.
5 Network Parameters Checking
Before cluster optimization, the system parameters should be imported into the
OMC, such as eNodeB ID, Cell ID, TAC, Neighbor List, etc.
6 Optimization Method Definition
The methods of optimization include two aspects. One is engineering
parameters adjustment, such as antenna azimuth, down tilt, height, etc. Another
is radio parameters adjustment, such as channel power allocation, handover
parameters, etc.
7 Document Preparation
The following documents are necessary to prepare before cluster optimization:
Technical Site Survey report (TSS)
Single Site Verification report (SSV)
Site Engineering Parameters Table
OMC Configuration Parameters
8 Optimization Equipments Preparation
Optimization equipments include: data collection software, post-processing
software, test handset, Scanner, laptop, digital map, GPS, test vehicles, etc.
3.3 Soft Launch (Trial-running Period) Optimization
When network construction and pre-launch optimization work are finished, the
network can be put into a soft-launch stage, which means friendly users with
special access right can begin to use services provided by network and
generate useful feedback for the enhancement of network performance. The
goal of soft-launch optimization is to further optimize the whole network in order
18. The optimization process in this stage is mainly driven by KPIs analysis result.
For selected KPIs, daily analysis is made to keep up-to-date view on the
dynamically changing network performance. If any problems are identified and
classified into specific domains, corresponding teams from different domains are
responsible for the trouble shooting work, and make possible adjustments and
verifications until the problematic KPIs fall into the acceptable level again.
The output from this optimization stage would be daily and weekly KPI reports,
and also monthly performance test report through drive test. Typical or critical
trouble shooting reports made in this stage are documented and reported as
well.
4 CLUSTER OPTIMIZATION
4.1 Single-Cell Coverage Analysis
After the thorough drive test of the network, you need to check the antenna
connection sequence, single-cell overshooting, antenna side/back lobe
coverage, and zero-coverage cell based on data obtained from this test so as to
work out the actual coverage of each cell.
During the single-cell coverage analysis, you will use the LTE COVER LINE and
PCI RSRP functions provided by CNA. (or other DT analysis tool)
Figure 4-1 CNA LTE COVER LINE
20. Modify engineering connection for the cell where wrong antenna connection
exists.
Study Case
The antenna in Beiting Square of Guangzhou University campus should have
covered the cell FE2 (PCI94). Actually, it covers the cell FE1 (PCI93). In this
case, the engineering parameters and PCI are proved to be accurate, so the
antenna connection in this area is wrong.
Figure 4-3 Coverage Direction of Cell FE2 (PCI94)
4.1.2 Checking the Overshooting
Problem Description
Overshooting appears when signals of a cell are found in its non-neighboring
cells, and RSRP of this cell is larger than -100 dBm. Overshooting usually leads
to overlapped coverage, pilot frequency pollution and ping-pong handover.
22. Case
Overshooting problem is found in the cell FE3 (PCI 125) in the teaching building
of Guangzhou Medical University. The engineer adjusts the antenna azimuth
and RS power in this cell, and finally solve this problem.
Figure 4-6 Cell Coverage Before and After the Azimuth & RS Power Adjustment
4.1.3 Checking the Coverage of Antenna Side Lobe and Back Lobe
Problem Description
Strong coverage is found on the direction of antenna side lobe and back lobe. It
leads to pilot frequency pollution, poor SINR and abnormal handover.
Problem Analysis
Find out the cell which has strong coverage at the direction of antenna side lobe
and back lobe by analyzing the test data and using the PCI coverage analysis
function provided by CNA. This problem is usually caused by reflection, wrong
feeder connection, wrong version file and wrong antenna.
Solution
Troubleshoot this problem based on actual situation.
Case
In the Arts Building of Guangzhou Foreign Language College, the coverage area
of cell FE1 (PCI 138) is found overlapped with the cell FE3 (PCI 140). This is
due to reflection of cell FE3 (PCI 140).
24. Figure 4-8 PCI's RSRP Function
Alternatively, you can find out the zero-coverage area by exporting PCI and
RSRP of all main serving cells and their neighboring cells into an excel, and
check this parameters in the excel. Compare the PCIs in this excel with the PCIs
of the whole test area. The cell without PCI can be considered as the cell with
zero coverage.
Solution
Check the working status, parameter configuration, location and coverage of
current cell.
Case
The cells with zero coverage are listed in the table below:
Table 4-1 Cells with Zero Coverage
NE ID PCI Reason Solution
6006_Guangzhou Traditional
Medical College, FE2
4 Broken link
2871_Western Inner Circle
Road, Guangzhou, FE4
0 Broken link
1008_Geigang, Guangzhou,
FE1
114
Wrong parameter
configuration
26. Therefore, the main task of network optimization is to eliminate poor coverage
area and overlapped coverage area.
4.2.3 Weak-Coverage Optimization
4.2.3.1 Definition of Weak-Coverage
Weak coverage refers to the situation where signal is not strong enough to
guarantee a stable network and required network performance.
The area whose RSRP is less than -110dBm is considered as a weak coverage
area.
4.2.3.2 How to Find out Weak-Coverage Area
Perform the following steps to find out weak coverage area based on DT test
data:
In the CNA, find Server Cell RSRP under the sub-node Measurement of MS1
from navigation tree on the left, right-click Server Cell RSRP and select View In
Map from the short-cut menu, or click and drag Server Cell RSRP into the map
window on the right.
Figure 4-9 Weak Coverage Area Analysis -1
Find Dynamic Link under the MS1 node from the navigation tree on the left,
right-click it to select Add from the short-cut menu.
28. Figure 4-12 Weak Coverage Area Analysis -4
Check the line connection of server cell and RSRP legends, and you can find
signal intensity of your desired area.
Figure 4-13 Weak Coverage Area Analysis -5
4.2.3.3 How to Eliminate Weak-Coverage
Use the following methods to eliminate the weak coverage area:
Adjust the antenna height, azimuth and tilting.
Add new sites, RRU long-distance connection and cell long-distance connection.
Adjust the RS power.
Re-configure the neighboring cell relationship.
30. Figure 4-15 Coverage Effect of Cell PCI48, PCI43 and PCI12
Solution
Based on the site survey results, adjustment of engineering parameters is
proved to be invalid for weak coverage elimination. In this study case, new cells
are added to improve the coverage effect.
PCI30 Weak Coverage
Problem Description
Weak coverage is found in the cell PCI30.
Figure 4-16 DT Test Results-2
Problem Analysis
As shown in Figure 4-17, the section 1 is covered by the cell PCI30 and PCI18,
but the coverage effect in this section is quite weak.
32. Figure 4-19 DT Test Results after Adjustment of Antenna Tilting and Azimuth
4.2.4 SINR Optimization
4.2.4.1 SINR Definition
SINR (signal to interference plus noise ratio) indicates the ratio between
strength of received transmission signals and strength of received interference
signals (including noises and interference).
PDCCH SINR = RS power of best serving cell / interference from the coverage
cell
SINR requirements vary with operators and network construction stages. China
Mobile requires that SINR of 95% cells should be larger than -3dB. In actual
projects, we will conduct network optimization to guarantee that SINR of 1%
cells in a project is less than -3dB, and SINR of 5% cells in a project is less than
0dB
Root cause of Low SINR : weak coverage/Interference
4.2.4.2 How to Find a Cell of Low SINR
Perform the following steps to find a cell of low SINR based on the DT test data:
In the CNA, find Server Cell RSRP under the sub-node Measurement of MS1
from navigation tree on the left, right-click Server Cell RSRP and select View In
Map from the short-cut menu, or click and drag Server Cell RSRP into the map
window on the right.
34. Figure 4-22 Low SINR Cell Analysis -3
From the toolbar, click and select LTE-SC Link from the drop-down list.
The GPS dotted line is selected.
Figure 4-23 Low SINR Cell Analysis -4
Check the line connection of server cell and RSRP legends, and you can find
out the signal intensity of your desired area.
36. Figure 4-25 Low SINR Caused by Handover Failure
Problem Analysis
eNodeB does not make judgement after the test UE sends out the measurement
report for cell PCI150. Two seconds later the test UE triggers RRC re-
establishment but is rejected. However, the neighboring cell relationship
configuraiton is proved to be correct.
On this occasion, you can make a conclusion that no judgement on
measurement report and refusal on RRC re-establishment appear because of
low-speed measurement.
Figure 4-26 Handover Failure Analysis
Solution
Make an offset of 3dB when the test UE conducts handover from cell PCI150 to
cell PCI144.
38. Figure 4-28 Overlapped Coverage Analysis -1
Find Dynamic Link under the MS1 node from the navigation tree on the left,
right-click it to select Add from the short-cut menu.
Figure 4-29 Low SINR Cell Analysis -2
In the pop-up dialog box, select LTE-SC Link and click Apply. Wait until the
success message is displayed.
40. Figure 4-32 Overlapped Coverage Analysis -5
4.2.5.3 How to Solve Overlapped Coverage
Use the following methods to eliminate overlapped coverage:
Adjust the antenna azimuth, tilting and antenna height.
Adjust RS power.
Combine two cells when the angle between antennas for these two cells is too
small.
4.2.5.4 Study Cases
Overlapped Coverage from Cell PCI160, PCI144 and PCI150
Problem Description
The SINR of sections shown in figure is lower than -3dB.
Problem Analysis
The coverage of cell PCI160 and that cell PCI150 is overlapped in section 1,
and ping-pong handover is also found in this section. The coverage of cell
PCI150 and that of cell PCI144 is also overlapped.
42. In LTE system, it is considered that pilot frequency pollution is posed on a point
when the following two conditions are met:
RSRP of more than four cells is larger than -100dB.
RSRP(strongest) - RSRP(weakest) <= 6dB
4.2.6.2 How to Find an Area with Pilot Frequency Pollution
Perform the following steps to find a cell of low SINR based on the DT test data:
In the CNA, find Server Cell RSRP under the sub-node Measurement of MS1
from navigation tree on the left, right-click Server Cell RSRP and select View In
Map from the short-cut menu, or click and drag Server Cell RSRP into the map
window on the right.
Figure 4-34 Pilot Frequency Pollution Analysis -1
Select IE Label Select from the Map toolbar.
44. If more than one PCI is found in an area, it means that pilot frequency pollution
is posed on this area.
You can also find the area with pilot frequency pollution by checking call drops
and handover failure through CNA/CNT.
4.2.6.3 How to Eliminate Pilot Frequency Pollution
To eliminate pilot frequency pollution, you need to determine a cell and use it to
provide main strong pilot frequency. To enable a cell to provide main strong pilot
frequency:
Adjust engineering parameters of antenna
Adjust RS power.
4.2.6.4 Study Cases
Pilot Frequency Pollution in Cell PCI113 and Cell PCI134
Problem Description
SINR of the section covered by cell PCI113 and cell PCI134 is quite low.
Figure 4-38 Pilot Frequency Pollution
Problem Analysis
As shown below, when the UE conducts handover from cell PCI113 to cell
PCI149, two measurement reports have not been judged. The section shown
below is covered by the third cell, and pilot frequency pollution is also found in
this section.
46. 5
After all required statistics in this table is complete, you need to work out the
following information accordingly:
Location where the handover takes place
Figure 4-40 Location Where the Handover Takes Place
RSRP when the handover takes place
Table 4-3 RSRP When the Handover Takes Place
RSRP Statistics
RSRP
Range
> -80dBm > -90dBm > -100dBm > -110dBm <= -110dBm
Counts
Remarks
Handover results
48. frequencies. Later on, the UE reports the cells which enjoy strongest signal
intensity which is beyond the handover threshold.
When the missed matching of neighboring cells exists, you will find that:
The UE tries to send out measurement report for several times.
The UE does not receive any response from the system after it sends out the
measurement report.
Low SINR (< -3dB)
You need to analyze the handover failure and the measurement reports sent out
by the UE.
If the UE sends out the measurement report but does not receive response from
the system, you can find the signaling tracing statistics as shown below:
Figure 4-42 Signaling in Case of Missed Matching of Neighboring Cells
Comply with the workflow shown below to conduct the analysis on missed
matching of neighboring cells:
50. If the PCI of the target handover cell can be found in the neighboring cell list, it
indicates the handover problem is caused by other factors but the missed
matching of neighboring cells.
4.3.1.3 How to Solve the Problem of Missed Matching of Neighboring Cells
Add new neighboring cell
4.3.1.4 Study Cases
Problem Description
In the signaling shown below, many measurement reports are sent out but no
response is received.
Figure 4-44 Signaling in Case of No Response for Measurement Report
Problem Analysis
As shown in the following handover takes place according to last measurement
report, it is another cell but not the target cell where the handover takes place.
This handover takes place one minute after the first measurement report.
The content of the first measurement report and that of the second
measurement report are the same:
52. Figure 4-47 Analysis on Missed Matching of Neighboring Cells -3
In this neighboring cell list, you can find cell PCI19 but not the cell PCI20. It
indicates that cell PCI20 has not been configured as the neighboring cell for cell
PCI72, and thus handover between these two cells fails.
54. 4.3.2 Wrong Matching of Neighboring Cells
4.3.2.1 Definition of Wrong Matching of Neighboring Cells
Wrong matching of neighboring cells refers to the situation that two cells of the
same PCI are configured as neighboring cell for main serving cell, or PCI of
neighboring cell is the same as that of main serving cell.
4.3.2.2 How to Find Wrong Matching of Neighboring Cells
Wrong matching of neighboring cells exists when:
The handover fails frequently after the measurement report is sent out.
The UE is not handed over to the cell of strongest signal intensity.
SINR is quite low, usually lower than -3dB.
At least two cells in the measurement list are of the same PCI.
4.3.2.3 How to Eliminate Wrong Matching of Neighboring Cells
Modify the PIC of neighboring cell.
4.3.3 Ping-Pong Handover
4.3.3.1 Definition of Ping-Pong Handover
Ping-pong handover refers to the situation that the UE conducts handover
frequently in the handover belt between more than two cells.
4.3.3.2 How to Find Ping-Pong Handover
You can check the downloading rate and handover quantity through GIS. Ping-
pong handover exists when:
The downloading rate is quite low.
SINR is quite low.
The UE conducts handover for more than three times in the handover belt.
56. Figure 4-51 Workflow of Elimination of Ping-Pong Handover Problem
Process the DT test data
through CAN and then export
a file containing location
information of handover
points
Display handover points in
MAPINFO
Display traffic in MAP
Eliminate ping-pong
handover problem
Ping-pong handover
exists?
Y
Solve this problem in the
same way of elimination of
pilot frequency pollution
N
4.3.3.4 Study Cases
Problem Description
In the area shown below, traffic is quite low and the UE conducts handover
frequently.
58. Solution
Lower the antenna tilting 3 degrees in both cell PCI161 and cell PCI150.
Verification Test Results
After the adjustment of antenna downtilt, traffic and SINR in these two cells
restores, and ping-pong handover disappears.
4.3.4 Handover Latency
4.3.4.1 Definition of Handover Latency
Handover latency here refers to the handover latency on control plane. The
latency starts at the time the UE receives the RRC Connection Reconfiguration
message, and ends at the time when the UE reports the MSG3 message.
4.3.4.2 How to Find Handover Latency
The handover latency is considered to be quite large when it is larger than the
latency value set by the network operator.
The signaling on control plane during the handover goes through two stages:
Latency from the reception of RRC Connection Reconfiguration message to the
sending of MSG1 message
Latency from the sending of MSG1 message to the reception of MSG2.
4.3.4.3 How to Solve the Handover Latency Problem
Comply with the workflow shown below to solve the handover latency problem:
60. If the MSG1 is not re-transmitted but the interval between MSG1 retransmission
and RRC connection reconfiguration message is quite large, check the value of
PRACH Config Index, which indicates the interval of PRACH transmission (for
more details, see protocol 36211.5.7). If the value of PRACH Config Index is
quite large, please set it to a lower value.
If frequent MSG1 transmission is found, you need to collect statistics of packets
received on PRACH. Also, you need to the uplink interference information. If the
electrical level of interference is larger than -110dBm, please troubleshoot the
uplink interference problem or modify the value of expected PRACH reception
power. Also, you can adjust the detection threshold of absolution PRACH prefix.
If the UE has received MSG1 and the system has sent out MSG2, there may be
something wrong with the uplink. In this case, you can adjust engineering
parameters, RS power, PCI, initial CCE convergence degree.
For clear idea of troubleshooting methods for handover latency, see solutions
listed below:
Table 4-5 Solutions for Handover Latency Problem
SN
Uplink or
Downlink?
Solution Remarks
1
Uplink
Adjust the PRACH Config Index
2
Troubleshoot the uplink interference
problem
3
Raise the expected PRACH reception
power
4
Lower the detection threshold of the
absolute PRACH prefix
5
Downlink
Adjust the engineering parameters
6 Adjust the RS power
7 Adjust the PCI settings
8 Raise the initial convergence degree
4.3.5 Handover Failure
4.3.5.1 Definition of Handover Failure
Handover failure starts from the time the RRC Connection Reconfiguration
message is sent out, and ends at the time the RRC reconnection is triggered.
You can analyze this problem by using different measurement indexes, such as
RSRP and SINR.
62. Figure 4-55 Workflow of Solving the Handover Failure Problem
Check whether there is
any problem with RSRP,
SINR and MSG2
reception
Troubleshoot the
coverage problem
Process the DT test data
Check neighboring cells
Check whether there is
any problem with MGS1
transmission
Troubleshoot the
neighboring cell
problem
Troubleshoot the
MSG1 problem
Check whether the
threshold of synchronous
detection is too small
Modify the value of
related parameters
Check whether T304 works
overtime
Modify the value of
T304
End
Y
Y
Y
Y
Y
N
N
N
N
N
If RSRP, SINR and RAR reception are abnormal, it indicates that the handover
failure is caused by poor downlink coverage and non-synchronization between
UE and target cell. On this occasion, you need to improve the network coverage
effect.
During the neighboring cell check, what you have to do is to check whether
there exist cells of the same PCI.
If the MSG1 transmission is abnormal, troubleshoot this problem by modifying
the value of handover latency.
If the value of synchronization detection threshold is too small, non-
synchronization may appear, thus leading to RRC re-establishment.
64. As shown in Figure 4-58, the UE conducts handover between cell PCI304 and
PCI161. At the same time, the value of SINR is quite low, as shown in Figure
4-58.
Figure 4-58 Analysis of Handover Failure -2
Solution
Lower the antenna tilting 3 degrees in cell PCI60.
Verification Test Results
66. Check whether any alarm is reported for the fault site.
Check whether interference or weak coverage exists.
Check engineering parameters and transmission.
Write down problem description and check results and send this problem report
to R&D engineers.
Figure 4-60 Workflow of Analyzing Traffic Problem
Any alarm is reported for the
fault cell
Clear the alarm
Find out the area of low service rate
based on DT test data
Does the rate meet
requirements of radio
environment
Are the parameters of serving
cell meet requirements
Improve the coverage effect for the
area of low rate
Modify the value of abnormal
parameter
Is the transmission abnormal
Submit problem report to the
customer and ask help for solving
transmission problem
Y
Y
Y
Y
N
N
N
N
There may be something wrong with
the Version file. Report the problem
and problem location, track the
progress and verify the network
performance after adjustment
68. Figure 4-61 Cells Whose Maximum Traffic is Less than 5M
4.4.3.1 Area 1
Figure 4-62 DT Test Data of Area 1
Problem Description
When the UE is conducting handover from cell PCI149 to cell PCI134, it sends
out measurement report but does not receive any response. It triggers RRC
connection re-establishment in target handover cell but is refused. Therefore, it
triggers the re-establishment of a new service.
Problem Analysis
70. The cell PCI64 poses network coverage on a campus, and the coverage radius
here is quite small. When the UE conducts handover between cell PCI41 and
cell PCI64, signals from cell PCI64 fade away quickly, thus leading to low SINR,
call drops and no service traffic.
Solution
To solve the ping-pong handover problem, you need to eliminate cell PCI64's
coverage on this area. Therefore, lower the antenna inclination angle in this cell
3 degrees, or reduce the RS power in this cell.
Verification Test Results
After the adjustment, ping-pong handover and call drops disappear, and traffic
also restores.
4.4.4 Analyzing the Cell with the Average Downloading Rate Ranging from
5M to 10M
Table 4-8 Cells Whose Average Traffic Ranges from 5M to 10M
SN PCI Average PDCP Traffic (Mbps) Date
1 64 0.07 2012/7/16
2 149 0.51 2012/7/16
3 61 3.65 2012/7/16
4 139 3.67 2012/7/16
5 134 4.56 2012/7/16
6 82 5.85 2012/7/16
7 114 5.91 2012/7/16
8 88 6.26 2012/7/16
9 2 8.47 2012/7/16
10 37 8.94 2012/7/16
11 94 9.11 2012/7/16
12 140 9.42 2012/7/16
13 121 9.42 2012/7/16
72. Problem Description
As shown above, when the UE conducts handover between cell PCI11 and cell
PCI21, it sends out measurement report but eNodeB does not receive this report,
or UE does not receive the handover judgment sent by eNodeB, thus leading to
handover failure, service re-establishment and low rate.
Problem Analysis
Area 2 is covered by cell PCI11, cell PCI21, cell PCI28 and cell PCI69, and
RSRP here is about -101dB. The cell PCI is about one kilometer away from this
area, namely its signal overshoot to this area. Also, cell PCI11 and cell PCI21
are not neighboring cells. Therefore, when the UE moves through cell PCI11, it
cannot receive handover judgment for handover to cell PCI21 from eNodeB
although it has sent the measurement report.
Solution
Lower the tilting in cell PCI11, or configure neighboring cell relationship for cell
PCI11 and cell PCI21.
4.4.4.3 Area 3
Figure 4-66 DT Test Data -2
Problem Description
When the UE is making phone calls or using data service in cell PCI25, it
detects strong RSRP from cell PCI68, so it triggers handover from PCI25 to
74. Configure neighbour cell relationship for cell PCI27 and cell PCI37.
4.4.4.5 Area 5
Figure 4-68 DT Test Data -4
Problem Description
When the UE moves from cell PCI53 to PCI61, the UE sends out a lot of
handover requests to eNodeB, but does not receive any handover judgment.
Problem Analysis
There are residential buildings between cell PCI53 and PCI61, and there is a
high-rise crossroad in area 5. On this occasion, signals from PCI53 fade away
quickly at the turning corner.
Solution
Lower the RS power of cell PCI53 from 12dBm to 9dBm, and raise the RS
power of cell PCI61 from 6dBm to 9dBm. Moreover, increase neighboring cell
offset by 3dB.
Verification Test Results
After the adjustment, handover and rate in area 5 restore.
76. 4. Using the STS signaling trace tool and UE signaling procedure, locate the radio
access failure problem by following this cause analysis procedure.
5. Analyze and solve the radio access problem by following the specific
troubleshooting procedure, including RRC connection establishment, authentication
and encryption, E-RAB connection establishment, and equipment fault.
4.5.2 RRC Connection Establishment Failures
4.5.2.1 Procedure for Troubleshooting an RRC Connection Establishment Problem
An RRC connection establishment failure can be processed by using the UE
signaling procedure and STS signaling trace tool, as shown in Figure 4-70.
78. Call signaling interruption because the call is originated from a poorly covered cell
with weak signals
Uplink RACH problem
Paging failure during the TAU
Cell reselection parameter misconfiguration: The call is not originated from the best
cell due to cell reselection time delay.
RS power and power allocation parameter misconfiguration
Traffic congestion
Equipment fault
It is highly likely that an RRC connection establishment failure may occur due to
the following factors:
Weak signals in the downlink
Uplink RACH problem
Cell reselection parameter misconfiguration
Equipment fault
4.5.2.3 Solutions to Highly Probable RRC Connection Establishment Problems
To solve these highly probable problems, ZTE recommends the following
solutions:
Perform the RF optimization to solve an undershooting or overshooting problem.
Optimize the TA edges to reduce unnecessary location update. If possible, it is best
to include the TA edges in a sparsely populated area.
To ensure that the UE can reselect a preferable cell for originating the call, optimize
the cell reselection parameters of the problematic cell.
Modify such random access and power allocation parameters as PRACH, PCCH,
PDCCH, PDSCH, and Msg3 power offset, whenever necessary.
Modify the RS power to cover the cell radius as expected.
80. 4.5.2.6 Delivering the RRC Connection Reject Message
After receiving RRC Connection Request message, the eNodeB delivers the
RRC Connection Reject message to the UE. When finding the RRC
Connection Reject message, you need to check the specific cause value:
Congestion: In this case, you need to check the network usage.
Unspecified: In this case, you need to check the log information.
When receiving the RRC Connection Setup message, the UE fails to deliver
the RRC Connection Setup Complete message. If the signals in the downlink
are normal, you can infer that this problem may be caused by a handset fault.
When the UE delivers the RRC Connection Setup Complete message, the
eNodeB fails to receive the RRC Connection Setup Complete message. There
is a very small probability that this problem will occur because the transmit
power of the UE will be increased through the initial uplink power control.
Temporarily, no good solution is readily available to this problem.
4.5.3 Authentication and Encryption Failures
When an authentication failure occurs, you need to analyze potential factors,
depending on the cause value (MAC Failure or Synch Failure) carried in the
Authentication Failure message that is sent from the UE to the MME.
4.5.3.1 MAC Failure
During the authentication procedure, the UE checks the AUTN parameter
carried in the Authentication Request message that is sent from the MME.
When finding incorrect MAC information, the UE delivers the Authentication
Failure message that carries the cause value (MAC Failure) to the MME, as
shown in Figure 4-71.
82. Figure 4-72 Authentication Failure Message (Cause Value: Synch Failure)
UE MME
Stop T3420
AUTHENTICATION REQUEST
Start T3420 Stop T3460
AUTHENTICATION FAILURE (cause = "synch failure")
Start T3460
Perform
re-synch
with HSS
AUTHENTICATION REQUEST
Stop T3460
AUTHENTICATION RESPONSE
Start T3460
This problem may usually be caused by these potential factors:
Illegal subscriber
Equipment fault
4.5.4 E-RAB Connection Establishment Failures
Based on the drive test data, the initial E-RAB connection establishment
success rate is measured from the time when the UE sends out the PDN
Connectivity Request message to the time when the UE returns the Activate
Default EPS Bearer Context Accept message.
An E-RAB connection establishment failure may usually be caused by these
potential factors:
Weak signals
UE/MME rejects
Parameter misconfiguration
Corner effect
Equipment faults
84. In this case, you need to increase the intra-frequency cell reselection threshold and
speed. This can force the UE to quickly station in an optimum cell.
4.5.4.2 UE/MME Rejects
The UE rejects may usually be caused by these potential factors:
The reject is resulted from the activated EPS bearer context.
The reject is resulted from the security mode of the NAS layer.
When the MME delivers the Attach Reject message, the cause value may
include:
Network failure
EPS services not allowed in this PLMN
ESM failure
No EPS bearer context activated
For more information about the UE/MME rejects during the radio access
procedure, please refer to the corresponding message description guide.
To solve this problem, ZTE recommends the following solutions:
If a UE reject problem occurs because the UE is mal-functioning, you need to
upgrade the HW/SW version or replace the UE.
If an MME reject problem occurs, you need to check the STS signaling trace data
on the eNodeB side to see if it is caused by a poor coverage or S1 link failure
problem. If not, you need to hand this problem to the core network technical
support team.
4.5.4.3 Parameter Misconfiguration
When a radio access failure occurs, we need to first compare the parameters of
a well-functioning cell to those of a mal-functioning cell to see if they are
consistently configured. If not, check whether such a failure is caused by
parameter misconfiguration. In normal cases, it is recommended to enable the
intra-frequency measurement and cell reselection. To solve this problem, ZTE
recommends you configure scenario-specific parameters as required.