Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
www.huawei.com
Objectives
Upon completion of this course, you will be able to:
Deep understand the handover procedure Solve the typical handover fault
Page1
Course Name
Contents
1. Handover Procedure Review 2. Handover KPI Introduction 3. Handover Fault Analysis 4. Case Study
Page2
Page3
Course Name
Page4
Page5
Course Name
Page6
Page7
Course Name
Page8
Contents
1. Handover Procedure Review 2. Handover KPI Introduction 3. Handover Fault Analysis 4. Case Study
Page9
Course Name
Page10
Page11
Course Name
Page12
L.HHO.Prep.FailOut.MM Number of outgoing handover preparation failures E due to faults in the EPC L.HHO.Prep.FailOut.NoR Number of outgoing handover preparation failures eply due to no responses from the target cell L.HHO.Prep.FailOut.Prep Number of outgoing handover preparation failures Failure due to handover preparation failures at the target cell L.HHO.Prep.FailOut.HOC Number of outgoing handover failures due to ancel handover cancellation messages sent by the source cell
Page13
Course Name
Contents
1. Handover Procedure Review 2. Handover KPI Introduction 3. Handover Fault Analysis 4. Case Study
Page14
Contents
3. Handover Fault Analysis
3.1 Typical Handover Fault Scenarios
Page15
Course Name
Early Handover
Page16
Delayed Handover
Page17
Course Name
Page18
Contents
3. Handover Fault Analysis 3.1 Typical Handover Fault Scenarios
3.2 Generic Procedure
Page19
10
Course Name
Page20
Configuration problem
Check the neighbor/ANR configuration Check the X2 configuration Check EPC authentication & security configuration
Transmission problem
Check relevant alarm Check the latency using some packet analysis tools
Page21
11
Course Name
Contents
3.3 Problem Diagnosis & Analysis
3.3.1 No measurement report 3.3.2 No handover command 3.3.3 No handover complete message
Page22
Page23
12
Course Name
Page24
Scenario : UE receives measurement control message, but UE doesnt send any measurement report
Copyright 2013 Huawei Technologies Co., Ltd. All rights reserved. Page25
13
Course Name
Page26
Solution This case is considered as delayed handover, we can enable MRO feature to optimize it automatically
Copyright 2013 Huawei Technologies Co., Ltd. All rights reserved. Page27
14
Course Name
Contents
3.3 Problem Diagnosis & Analysis
3.3.1 No measurement report 3.3.2 No handover command 3.3.3 No handover complete message
Page28
Page29
15
Course Name
Page30
Due to the high load of target cell, it rejects the admission of handover in service Solution: Enable relevant load control algorithms on target cell
Copyright 2013 Huawei Technologies Co., Ltd. All rights reserved. Page31
16
Course Name
Page32
Page33
17
Course Name
Page34
Contents
3.3 Problem Diagnosis & Analysis
3.3.1 No measurement report 3.3.2 No handover command 3.3.3 No handover complete message
Page35
18
Course Name
Page36
RLF Occurs
Due to poor uplink channel quality, eNodeB doesnt receive random access preamble until UE sends maximum preambles
Copyright 2013 Huawei Technologies Co., Ltd. All rights reserved. Page37
19
Course Name
Contents
1. Handover Procedure Review 2. Handover KPI Introduction 3. Handover Fault Analysis 4. Case Study
Page38
Page39
20
Course Name
Analysis
In the handover request message, source eNodeB deliver the target GTPU ID (SGW IP address) to let target eNodeB setup uplink S1 bearer directly. We check the IP address of SGW in the message, and find that it is not identical with target eNodeB configuration
Page40
Solution
Later we confirm this issue, this TA border is also the border of two regions which use different SGW. And in each region ,only one IP path is configured for current eNodeB to SGW. So the handover will be failure when cross the different SGW. Solution
Configure S1 IP path from the target eNodeB to source SGW, then the problem is solved
Suggestion: This is a very typical problem, on the border cell of inter SGW, we should remember to configure the IP path to the SGW which belongs to the target cell as well.
Page41
21
Course Name
Page42
Case 2 Analysis
From the previous message, we can see that before the measurement report, eNB sends one RRC reconfiguration message, but the UE doesnt feedback the complete message. Then we check trace on UE side, and find that UE doesnt receive the RRC reconfiguration message
Page43
22
Course Name
Case 2 Conclusion
Due to poor DL coverage, UE doesnt receive the RRC reconfiguration message, thus no complete feedback. As the previous RRC reconfiguration procedure is not completed, eNodeB is still waiting for reconfiguration feedback and measurement report is not processed.
Page44
Summary
Handover flow analysis Troubleshooting for typical handover fault
Page45
23
Course Name
Page46
Thank you
www.huawei.com
24