内部公开▲

FDD LTE Products Special Issue

September 29, 2015, No. 2

© ZTE All rights reserved

1
 内部公开▲

Maintenance Experience
FDD LTE Products Special Issue
2015, No. 2, Issue 286
Publication date: September 29, 2015

Editorial Committee
Director: Chen Jianzhou
Deputy Director: Wang Dianping
Chief Editor: Zhao Haijun
Executive Editor: Zhu Lijia, Luo Liming
Responsible Editors: Mou Dan, Qiu Quan
Technical Senior Editors: Cai Haoyi, Hu Hao, Hu Yuxi, Li Yan, Shi Wenyan, Wang Jun,
Wang Ping, Wang Zhenhai, Zhao Yanli

Editorial Office
Address: ZTE Plaza, No.55, Hi-tech Road South, Shenzhen, P.R.China
Postcode: 518057
Tel: +86-755-26776084
Email: doc@zte.com.cn

© ZTE All rights reserved

2
 Maintenance Experience

Contents
Network Operation Skills—Four Steps for You to Easily Query Electronic Downtilt Angles in Batches2
Dropped Calls Caused by X2 Interface Handover Failure When the Transmission Delay Is Long ......... 5
Low Indoor Download Rate ...................................................................................................................... 8
Attach Failure Caused by Incorrect Access Probability Factors ............................................................. 10
The Flow for UEs to Return to the 4G Network Is Abnormal Because RAU Fails When the CSFB
Function Is Used ..................................................................................................................................... 18
Co-Channel Handover Failure Caused by Incorrect A3 Event Indexes .................................................. 22
Inter-System Handover Preparation Failure Caused by Different CN IDs of MMEs of Different NEs . 25

FDD LTE Products Special Issue︱ 1

 Case Analysis

Network Operation Skills—Four Steps for

You to Easily Query Electronic Downtilt
Angles in Batches
 Xiao Hewei / ZTE Corporation

The following uses figures to describe how In the Dynamic Command navigation tree
to query electronic downtilt angles of on the Dynamic Management tab,
eNodeBs in batches in the EMS. double-click Query RET Tilt. The electronic
downtilt angle query list is displayed, see
On the NE Management tab on the left in
Figure 3.
the EMS, right-click a node that NE
management is enabled for and select Select cells whose downtilt angles are to be
Dynamic Management from the shortcut queried from the list. Click . The query
menu. The Dynamic Management tab is result is displayed on the Detailed
displayed, see Figure 1. Information of Operation tab in the lower
From the NE list on the Dynamic part, see Figure 4 Querying Electronic
Management tab, select NEs whose downtilt Downtilt Angles.
angles are to be queried, see Figure 2.

2 ︱Maintenance Experience Issue 286

 Maintenance Experience

Figure 1 Opening the Dynamic Management Tab

Figure 2 Selecting eNodeBs whose Electronic Downtilt Angles Are to Be Queried

FDD LTE Products Special Issue︱ 3

 Case Analysis

Figure 3 Opening the Electronic Downtilt Angle Query List

Figure 4 Querying Electronic Downtilt Angles

4 ︱Maintenance Experience Issue 286

 Maintenance Experience

Dropped Calls Caused by X2 Interface

Handover Failure When the Transmission
Delay Is Long
 Quan Guoqiang / ZTE Corporation

15 dB in this period. As a result, the target

Symptom
eNodeB cannot receive the handover
During the X2 interface handover test completion message. In addition, the X2
performed on new eNodeBs in an LTE interface of the target eNodeB sends the
project, the UE submits multiple HANDOVER_CANCEL message, which
measurement reports after the A3 event is means that the handover fails.
triggered, but no handover instruction is (2) After the handover fails, the UE sends a
delivered, and calls are dropped. link reestablishment request immediately.
According to signaling, a link is
Probable Cause
reestablished. However, because the UE
After the UE submits multiple measurement receives no SRB2 or DRB1 reconfiguration
reports, the source eNodeB originates an X2 message, the user context is released when
interface handover request. The source the maximum number of retransmissions is
eNodeB receives a response after several reached. As a result, when the UE sends a
seconds. However, the target eNodeB does link reestablishment request again, the
not receive any handover completion request is rejected and the connection is
message. As a result, the handover fails. released, because the eNodeB has no user
The UE sends a link reestablishment context.
request, but the request is rejected and calls The handover fails and calls are dropped
are dropped. because the period after the
(1) According to the data recorded by CXT HANDOVER_REQUEST message is sent
and the signaling records of the eNodeBs, it and before the
takes nearly three seconds for the source HANDOVER_REQUEST_ACKNOWLEDGE
eNodeB to originate the X2 interface message is received is long, see Figure 1.
handover request and receive the response
Action
from the target eNodeB. For handover
1. Check the hardware of the two
preparations, this response time is long.
eNodeBs to see whether the
According to the observation through CXT,
hardware has alarms.
the RSRP of the target cell is increased by

FDD LTE Products Special Issue︱ 5

 Case Analysis
For example, check whether the
RRU operates properly, whether
there are X2 link alarms, and
whether the cell is blocked.
Result: No alarm is found.
2. Check configurations.
For example, check whether the
handover thresholds and delays of
the two eNodeBs are default and
whether neighbor cells are
configured properly.
Result: The configurations of the
two eNodeBs are default, and no
configuration error is found.
3. When the UE uses download
services in the two cells, engineers
find that the throughput of the UE in
the target cell is low, and DUmeter
shows that the rate is reduced
dramatically but is soon recovered.
Engineers think that transmission
may be faulty.
6 ︱Maintenance Experience Issue 286
4. When the ping command is
used to check the delay of the
transmission from the eNodeBs to
the server, engineers find that the
delay of one of the eNodeBs is long
and the transmission is not stable.
5. Use Wireshark on the server
to capture packets. Through packet
analysis, engineers find that the
delay of the packet transmission
from the eNodeB to the server is
long.
6. Tell the transmission engineer
to check transmission.
According to the feedback of the
transmission engineer, momentary
interruption has occurred on the
eNodeB during transmission.
7. The same test is performed
after the momentary interruption
problem is solved, and handover
succeeds.
 Maintenance Experience

Figure 1 Handover Flow

Summary normal and whether cell signals are

of good quality. Focus on the
If calls are dropped during the X2 interface
arrival time of signaling at signaling
handover test:
points. If the arrival time of
signaling is abnormal, transmission
(1) Check alarms and
may be faulty.
configurations first. Ensure that
there are no hardware alarms and
(3) Capture packets during
configurations are correct.
transmission to locate the fault
cause and fix the fault.
(2) Analyze signaling to check
whether the signaling flow is


FDD LTE Products Special Issue︱ 7

 Case Analysis

Low Indoor Download Rate

 Zhu Hong / ZTE Corporation

Symptom
During an indoor LTE test in a convention
center, testing engineers find that the
average download rate is only 24 Mbps.
This eNodeB demonstrates the customer's
LTE services, and the target average
download rate should be higher than 50
Mbps. Therefore, the problem must be
solved immediately.
Before the eNodeB of the convention
center is optimized, no limit is set for
LTE eNodeB transmission, and this is
confirmed with the transmission side.
Therefore, the fault is not caused by
transmission quality.
 Radio environment
troubleshooting:

Probable Cause The onsite radio environment tested by

After the problem occurs, engineers perform testing engineers is as follows: the

troubleshooting from the following four RSRP is lower than –80 dBm and the

aspects: eNodeB alarms, parameters, SINR is lower than 10. The main cause

transmission, and radio environment. of the low download rate may be that
the radio environment is poor.
 eNodeB alarm troubleshooting:
Generally, after indoor system
Alarms in the EMS are checked. The coverage is deployed, the radio
eNodeB of the convention center does environment shall not be poor. Further
not have alarms, so the fault is not an troubleshooting is performed from the
explicit fault of the eNodeB. following two aspects:

 Parameter troubleshooting:  Product troubleshooting:

The radio and terrestrial key The output power of the RRU is
parameters of the existing network are checked. The output carrier power of
set globally, so parameter settings have the eNodeB is checked, and the output
no fault. power is 33 dBm. Therefore, the
product has no fault. Engineers
 Transmission troubleshooting:
basically determine that signals are
poor because of indoor system
problems.

8 ︱Maintenance Experience Issue 286


 Indoor system troubleshooting:
The indoor system manufacturer is
informed that cable routing must be
checked, especially combiners and
feeders. The indoor system
manufacturer finds that a WLAN
combiner that does not support 4G
technologies is connected, and the
feeder from the RRU to the antenna is
long (200 meters). The fault cause is
determined.
Action
The indoor system manufacturer is informed
about the following rectifications:
 The cable routing of the LTE
system must be independent.
Because the eNodeB is a key eNodeB
for FDD function demonstration, it must
provide a high rate. Independent cable
routing can avoid interference
introduced by the combination of other
radio systems.
 The feeder from the RRU to the
antenna must be shorter than 80
meters.
The feeder length is controlled to
reduce loss. The length 80 meters is
determined according to
measurement. The distance between
the RRU and antenna can be shorter
than 80 meters after the RRU is
relocated.
Maintenance Experience
After the above rectifications of the
indoor system manufacturer, the RSRP
of the LTE network in the convention
center is increased to –62 dBm, the
SINR is 25, and the average indoor
download rate is higher than 60 Mbps,
which exceeds the customer's
expectation.
Summary
The concept to analyze and locate the low
indoor rate fault is as follows:
1. Perform alarm, transmission,
configuration troubleshooting first.
2. RSRP coverage is the key
factor. Generally, the SINR of an
indoor system is not low. If the
RSRP coverage of the indoor
system is poor and the product has
no fault, the fault can be
determined in the indoor system.
Notify the indoor system
manufacturer for troubleshooting.
(If the output power of the RRU is
lower than 20 dBm, it means that
the product is faulty.)
3. If RSRP is normal, check
transmission to see whether
throughput is abnormal (incoming
traffic is insufficient) because the
FTP server or transmission is
onsite faulty.
4. If the fault is not located after
the above operations and the
system is a dual-stream indoor
system, check whether channels
are balanced.
FDD LTE Products Special Issue︱ 9
 Case Analysis

5. If the fault is still not located, antenna and perform a comparison

connect an electrically small test to troubleshoot the product.

Attach Failure Caused by Incorrect Access

Probability Factors
 Yu Mingyang / ZTE Corporation

following table, all lines, except the line in

Symptom
yellow, show that the attach procedure fails
During Drive Testing (DT) of a FDD-LTE
when signals are normal. For the line in
project, the attach procedure fails when
yellow, the attach procedure fails because
signals are normal. The probability of attach
signals are of poor quality.
failure, which is 5% in the network, is high.
The log of one failure is as shown in Figure
A cluster is analyzed, and the result is
1 and Figure 2.
shown in the following table 1. In the
Table 1 The result of analysis

10 ︱Maintenance Experience Issue 286

 Maintenance Experience

Figure 1 Two ATTACH REQ Messages Sent by the UE

Figure 2 Interval Between the Two ATTACH REQ Messages

The UE has sent two ATTACH REQ attach procedure fails, T3410 shall be 15
messages, see Figure . However, no RRC seconds.
Connection Request message is sent after
Probable Cause
the first ATTACH REQ message is sent. The
Check the hardware and software mode of
interval between the two ATTACH REQ
the terminal first for troubleshooting. If the
messages is 4 seconds, see Figure .
fault is not located, check whether EMS
Generally, after sending an ATTCH REQ
parameters are set properly.
message, the UE shall send an RRC
Connection Request message, and after the

FDD LTE Products Special Issue︱ 11

 Case Analysis

1. Replace the terminal and testing still exists. This means that the fault is not
software. caused by terminal hardware or testing
software.
Engineers think the terminal or testing
software may be faulty so the RRC 2. Modify the attach mode of the
Connection Request message is not sent. terminal.
Therefore, the terminal and testing software
The ATTACH REQ message is observed,
are replaced.
see Figure .
MF823 is replaced with MF831, and testing
software is replaced with QXDM. The fault

Figure 3 ATTACH REQ Message

Engineers find that att_type on site is 2.
Generally, att_type shall be 1. Att_type = 2
means "EPS attach combined EPS/IMSI
attach". Engineers think the fault cause may
be that with a combined attach procedure,
UE fails to get registered to the 2G/3G core
network but gets registered to the EPS.
In QXDM, the Service Domain Preference
parameter of the terminal is modified from
CS+PS to PS, see Figure 4 Registration

the UE is going to get registered to the EPS Mode of the Terminal on the Network Side
and the 2G/3G core network. However, the
. This means that the registration mode of
the terminal on the network is modified from

12 ︱Maintenance Experience Issue 286

 Maintenance Experience

circuit domain+data domain to data domain. by the incorrect configuration of the attach
In this way, whether attach failure is caused type of the terminal can be determined.

Figure 4 Registration Mode of the Terminal on the Network Side

After the registration mode of the terminal is 3. Check access probability

modified, the fault still exists. This means factors.
that the fault is not caused by the
After the consultation with experts,
registration mode configuration.
engineers find that the settings of two
According to steps 1 and 2, the fault is access parameters in the SIB2 message
irrelevant to the terminal. EMS parameter sent by the eNodeB may be the fault cause,
settings are checked subsequently. see Figure 5.

FDD LTE Products Special Issue︱ 13

 Case Analysis

Figure 5 Access Probability Factors

EMS, select Radio Parameter >
ac-BarringForMO-Signalling and
LTE-FDD > Cell Reselection
ac-BarringForMO-Data respectively indicate
Configuration > E-UTRAN Cell
Probability Factor of Signaling Access and
Reselection. The E-UTRAN Cell
Probability Factor of Call Access
Reselection tab is displayed.
parameters.
Modify Probability Factor of
Action
Signaling Access and Probability
1. In the configuration Factor of Call Access from
management navigation tree in the 0.95[15] to 1. See Figure 6.

14 ︱Maintenance Experience Issue 286

 Maintenance Experience

Figure 6 Modifying Access Probability Factors

2. After the two access
According to the principles of the
probability factors are modified,
parameters, they shall be set to non-1
perform an onsite test.
values only when the network has dense

The attach procedure succeeds 37 times on users, for example, cells are busy, to share

the eNodeB. users with other cells.

The attach procedure succeeds 96 times in  Parameter Functions

drive testing.
Probability Factor of Signaling Access
Engineers determine that the attach failure and Probability Factor of Call Access
is caused by the two parameters. parameters prohibit or allow calling signaling

Parameter Descriptions services (for example, the attach service) or

calling data services. If you want to prohibit
The incorrect settings of the two parameters
signaling, data, or UEs, set
may cause a certain ratio of access failure.
ac-BarringForMO-Signalling and/or
In this case, the parameters are set to 0.95.
ac-BarringForMO-Data.
Thus, 5% of access fails. The purpose of the
two parameters is to prevent mass terminals No matter what attach type is set on the

from accessing the LTE system. Otherwise, terminal, the cause value in the RRC

the radio access network is overloaded and Connection Request message sent is

more serious problems are caused. mo-Signaling. Therefore, the attach

FDD LTE Products Special Issue︱ 15

 Case Analysis

procedure is mainly affected by the If the UE inactivity timer is enabled for

Probability Factor of Signaling Access
parameter. If the attach procedure fails in
the calling flow of the terminal, the failure is
caused by Probability Factor of Call
Access.
ac-BarringForMO-Signalling, the
parameter is for mobile phones when they
attach during registration to the network and
the periodic TAU or for the RRC connections
of normal TAU.

Corresponding to these two parameters, ac-BarringForMO-Data is for the calling

there are two support
Signaling Access-Deny Time and Call
Access-Deny Time. These two support
parameters are 4 (seconds) by default.
Therefore, the interval between two attach
operations is 4 seconds instead of 15
seconds configured for T3410.
parameters: mo-data (for example, the Internet services
of mobile phone, FTP data, and SMS
messages) of data services.
 Parameter Structures
Parameter structures is as shown in Figure
7.

 Parameter Differences

Figure 7 Parameter Structures

The applicable to UEs whose access classes is as shown in Table 1.

Table 1 The applicable to UEs whose access classes

Applicable to UEs Whose Access Classes (ACs) are 1 to 9

 ac-BarringFactor: indicates access barring probability. p00 to p95 (p00 = 0, p05 = 0.05, p10 =
0.10,…,p95 = 0.95) in the above figure are access probabilities.
After a UE whose AC is in the range of 1 to 9 obtains this value from the system message and originates a
connection, the UE creates a random number in the range of 0 to 1, and compares the number with the
obtained ac-BarringFactor. If the number is smaller than ac-BarringFactor and SBI1 that permits the call
attempt is obtained, it means that the call attempt is allowed. Otherwise, the access attempt is prohibited.
 ac-BarringTime: Indicates the time when access is prohibited according to ac-BarringFactor. s4 to
s512 in the above figure are options.

Applicable to UEs Whose ACs are 11 to 15

ac-BarringForSpecialAC: applicable to UEs whose ACs are 11 to 15. Five bits are contained, and they are

16 ︱Maintenance Experience Issue 286

 Maintenance Experience

described as follows.

Bit1 Bit2 Bit3 Bit4 Bit5

AC 11 AC 12 AC 13 AC 14 AC 15

Bit 1: UEs whose Bit 1: UEs whose Bit 1: UEs whose Bit 1: UEs whose Bit 1: UEs whose
ACs are 11 cannot ACs are 12 cannot ACs are 13 cannot ACs are 14 cannot ACs are 15 cannot
access. access. access. access. access.
Bit 0: UEs whose Bit 0: UEs whose Bit 0: UEs whose Bit 0: UEs whose Bit 0: UEs whose
ACs are 11 can ACs are 12 can ACs are 13 can ACs are 14 can ACs are 15 can
access. access. access. access. access.

 ACs of UEs access attempts. Otherwise, the access

attempts of the UE are prohibited.
All UEs are mobile populations randomly
divided into 10 classes, which are defined as The applicable scenarios of the ACs are as

ACs 0 to 9. The population number of each follows:

UE is saved in the SIM or USIM card. In Classes 0–9: Home and visited PLMNs
addition, each mobile terminal may be
Classes 11 and 15: Home PLMN only if the
classified into one or multiple special
EHPLMN list is not present or any EHPLMN
classes (five special classes in total: classes
11 to 15), and the special classes of each Classes 12, 13, and 14: Home PLMN and

mobile terminal is also saved in the SIM or visited PLMNs of the home country only

USIM card. These special classes are for For this purpose, the home country is
special advanced users. See the following defined as the country of the MCC part of
details (the order of the following classes is the IMSI
not the priority order):
Summary
Class 15 - PLMN Staff
During the access of a UE, if Probability
-"- 14 - Emergency Services Factor of Signaling Access and

-"- 13 - Public Utilities (for Probability Factor of Call Access

example, water and gas suppliers) parameters are set to 0.95, the probability of
access failure is 5% no matter what services
-"- 12 - Security Services
the UE is to use. This has a great impact on
-"- 11 - For PLMN Use delay indicators involved in the access. For

If a UE belongs to at least one of the ACs example, the UE can send the ATU

corresponding to the permitted classes of message successfully only the second time

the air interface, and the current network the UE sends the message. As a result, the

supports the ACs, the UE can originate Fast Return delay is long.

FDD LTE Products Special Issue︱ 17

 Case Analysis

The typical symptom of this fault is that no Probability Factor of Signaling Access
RRC Connection Req or MSG1 message is and Probability Factor of Call Access
sent after the Attach Req message is sent. parameters to see whether their settings are
When this symptom occurs, check incorrect.


The Flow for UEs to Return to the 4G

Network Is Abnormal Because RAU Fails
When the CSFB Function Is Used
 Fan Wenqiang / ZTE Corporation

address of the UE is changed, and the

Symptom
pending services before CSFB are lost.
During the CSFB function test in a place,
The signaling flow of the test is as follows.
UEs return to the LTE network from the
Figure 1 shows the abnormal signaling flow
UMTS through the attach flow. Generally,
(the UE returns to the LTE network through
UEs shall return to the LTE network through
the attach flow), and Figure 2 shows the
the TAU flow. If a UE returns to the LTE
normal flow (the UE returns to the LTE
network through the attach flow, the IP
network through the TAU flow).

Figure 1 Abnormal Flow (Return to the LTE Network Through the Attach Flow)

18 ︱Maintenance Experience Issue 286

 Maintenance Experience

Figure 2 Normal Flow (Return to the LTE Network Through the TAU Flow)

Probable Cause result, after the UE returns to the LTE

network, the TAU flow is replaced with the
The signaling shows that after the CSFB to
attach flow.
the UMTS, a CM SERVICE REQUEST
message is originated, and then RAU is Figure 3 shows RAU signaling.
originated immediately. However, RAU is
Figure 4 shows the details of the RAU
rejected (RAU REJECT). Because RAU fails
REJECT message.
after CSFB, the EMM and GMM state of the
UE is changed to DEREGISTERED. As a

Figure 3 RAU Signaling

FDD LTE Products Special Issue︱ 19

 Case Analysis

Figure 4 RAU REJECT Signaling

Related Principles GMM-REGISTERED.NO-CELL-AVAILABL

The following information describes how
RAU affects the EMM state of a UE and
determines whether the UE returns to the
4G network through the attach or TAU flow:
If GMM and EMM are both enabled, a UE
capable of S1 mode and A/Gb mode or Iu
mode or both shall maintain one common
registration for GMM and EMM indicating
whether the UE is registered for packet
services or not.
A UE that is not registered shall be in state
GMM-DEREGISTERED and in
EMM-DEREGISTERED.
If the UE performs a successful attach or
combined attach procedure in S1 mode, it
shall enter substates
E and
EMM-REGISTERED.NORMAL-SERVICE.
If the UE performs a successful GPRS
attach or combined GPRS attach procedure
in A/Gb or Iu mode, it shall enter substates
GMM-REGISTERED.NORMAL-SERVICE
and
EMM-REGISTERED.NO-CELL-AVAILABLE
.
At intersystem change from A/Gb or Iu
mode to S1 mode when no PDP context
state
is active, the UE shall move to state
EMM-DEREGISTERED and state
GMM-DEREGISTERED and then initiate
an attach procedure.

20 ︱Maintenance Experience Issue 286

 Maintenance Experience

After successful completion of routing area Action

updating or combined routing area updating
(1) The cause of the RAU REJECT
and tracking area updating or combined
message cannot be determined
tracking area updating procedures in both
according to signaling analysis. Trace
S1 mode and A/Gb or Iu mode, if the
RNC signaling in the UMTS, see Figure
network has indicated that ISR is activated,
5. Because every RAU REJECT
the UE shall maintain registration and
message is originated by the SGSN,
related periodic update timers in both GMM
engineers think that the core network
and EMM.
configuration may be faulty.

Figure 5 RNC Signaling in the UMTS

(2) After this thought is provided to
core network engineers, they trace
signaling and find that data is not
configured in the DNS. After data is
configured in the DNS, RAU succeeds
and UEs return to the LTE network from
the UMTS through the TAU flow.
whether RAU succeeds affects the EMM
state of mobile phones and determines
whether UEs return to the 4G network
through the attach or TAU flow.
All interoperations in the network, for
example, CSFB and LTE-to-UMTS
handover, require parameter settings in the

Summary core network. Therefore, it is recommended

to strictly check parameters in the core
The CSFB function requires core network
network after they are set.
engineers to configure data for NEs
including the MME, SGSN, and DNS, and


FDD LTE Products Special Issue︱ 21

 Case Analysis

Co-Channel Handover Failure Caused by

Incorrect A3 Event Indexes
 Wang Zhenhai/ ZTE Corporation

the measurement packet within the valid

Symptom
period.
An eNodeB has three cells whose IDs are:
4. The data configuration is incorrect, so
75, 76, and 77. When co-channel handover
no control information related to the
conditions are met, intra-eNodeB handover
handover event is delivered. (The data
fails. In addition, any of cells 75, 76, and 77
configuration of the cells must be compared
cannot be handed over to any co-channel
with that of a normal cell. Generally, errors
cell of a neighbor eNodeB. In these two
occur in handover threshold, delay, and TTT
cases, handover conditions are met, and
configurations.)
calls are dropped.

Probable Cause
Fault analysis in this case:
Troubleshoot handover faults from the
following aspects: (1) According to the parsing of air
interface messages, neighbor cells are
1. Neighbor cells are not configured.
configured properly. Figure 1 shows air
2. The terminal is faulty and does not
interface messages.
submit the measurement report.
Connect cell 77 to 14:23:30:183, and the
3. Handover is not performed in a timely
RRCConnectionReconfiguration message
manner, so the mobile phone cannot submit
shows that cells 75 and 76 are configured as
the neighbor cells of cell 77.

22 ︱Maintenance Experience Issue 286

 Maintenance Experience

Figure 1 Air Interface Messages of Cell 77

(2) Testing signals are analyzed, and
the result shows that cell 75 meets the
conditions of the A3 event for
co-channel handover, but the UE does
not submit any measurement report of
the A3 event within 10 seconds.
The measurement configuration data in the
RRCConnectionReconfiguration message
of the source cell during a normal handover
is checked, see Figure 2. For a normal
handover, signaling contains the
configuration information about the A3 event.
However, in the current signaling, the
RRCConnectionReconfiguration signaling
message does not contain the configuration
information about the A3 event but contains
the configuration information about the A5
event, see Figure 3.

Figure 2 Normal Signaling Messages

FDD LTE Products Special Issue︱ 23

 Case Analysis

Figure 3 Abnormal Signaling Messages

indexes. Indexes 60 and 61 correspond to

Based on the comparison between normal
the A5 event, but indexes 50 and 51
signaling and the current abnormal signaling,
correspond to the A3 event. Because of
the fault is determined that the eNodeB does
these settings, the configuration information
not deliver the configuration information
about the A5 event instead of the A3 event
about the A3 event but delivers the
is contained in the
configuration information about the A5 event.
RRCConnectionReconfiguration message.
As a result, co-channel handover fails.
(3) Select Radio Parameter > LTE FDD >
Action
Measurement Parameter
(1) Check parameters related to the
Configuration >Measurement Config
co-channel handover event of cells 75, 76,
Group, and modify the Coverage-Based
and 77. The Coverage-Based
Intra-Frequency Handover Measurement
Intra-Frequency Handover Measurement
Configuration Index parameter to 50;51.
Configuration Index parameter of cell 77 is
Intra-eNodeB co-channel handover of cells
set to 60;61.
75, 76, and 77 succeeds, and inter-eNodeB
(2) Select Radio Parameter > LTE FDD > co-channel handover also succeeds.
Measurement Parameter Configuration >
UE E-UTRAN Measurement to check


24 ︱Maintenance Experience Issue 286

 Maintenance Experience

Inter-System Handover Preparation Failure

Caused by Different CN IDs of MMEs of
Different NEs
 Lin Guoyong / ZTE Corporation

Symptom Probable Cause

According to the EMS KPIs of an office, the
success rate of inter-system handover is
dramatically reduced. Through analysis,
engineers find that the cause is that the
handover preparation on the target side fails
(Number of Outgoing
Inter-RAT(LTE->UTRAN) Handover
Preparation Failure due to Dst Preparation
Failure).
Inter-system handover involves two phases:
preparation and implementation. Figure1
shows the normal handover preparation
flow.
The KPI statistical point is shown in the
following figure (according to the KPI
description manual, the KPI statistical point
is 7 in Figure2 ).

Figure 1 Inter-System Handover Preparation Flow

FDD LTE Products Special Issue︱ 25

 Case Analysis

Figure 2 Handover Signaling Flow

engineering determine that KPI degradation

According to the handover flow, this fault
is caused by this operation. Signaling trace
cannot be fixed on the source (eNodeB) side.
and analysis are required to find the specific
The fault can be located only through the
cause.
analysis of the target (MME/3G) side.
Action
Because KPIs are changed dramatically, the
target side must be checked first to see (1) Perform the handover test in the area of
whether there are operations that change the faulty eNodeB.
the network. Engineers find that the time
According to the signaling trace of the 3G
when KPIs are changed is the same as the
RNC, relocation fails and CN ID 0 is pointed,
time when the combo operation for the MME
see Figure 3.
and SGSN is performed. Therefore,

26 ︱Maintenance Experience Issue 286

 Maintenance Experience

Figure 3 Signaling Trace of the RNC

bearer information of the UE is obtained

(2) Check parameter settings of the SGSN.
from the 3G side to the LTE side. Obviously,
Engineers find that MME IDs 3 and 4 (two
relocation fails because the IDs configured
MMEs) are configured on the SGSN, see
are different.
Figure 4. Because of these settings, the
source cannot be found when the original

FDD LTE Products Special Issue︱ 27

 Case Analysis

Figure 4 MMEs Configured on the SGSN

(3) Modify the CN IDs on the SGSN to 3 and 4. The CN IDs indicated during relocation are the
same as the specified IDs, and the handover flow is normal, see Figure 5 and Figure 6.

Figure 5 Signaling Flow After the CN IDs on the SGSN Are Modified 1

28 ︱Maintenance Experience Issue 286

 Maintenance Experience

Figure 6 Signaling Flow After the CN IDs on the SGSN Are Modified 2

Summary
2. The operation plan for the onsite core
1. If an inter-system handover fails on the network and KPIs after operations are
target side, the fault can be located only on performed must be paid attention to. Thus,
the target side. The LTE radio side can only problems that occur after the operations can
assist troubleshooting, and all professional be found and handled in a timely manner.
teams should be coordinated for
troubleshooting.


FDD LTE Products Special Issue︱ 29

 Case Analysis

30 ︱Maintenance Experience Issue 286

 内部公开▲

© ZTE All rights reserved