Вы находитесь на странице: 1из 9

Drop Call Analysis in LTE Network

Ericsson Internal
DROP CALL ANALYSIS 1 (9)
Prepared (Subject resp) No.

EHEEXIG
Approved (Document resp) Checked Date Rev Reference

2012-04-09 PA1

Drop Call Analysis in LTE Network


Drop Call Analysis in LTE Network
Ericsson Internal
DROP CALL ANALYSIS 2 (9)
Prepared (Subject resp) No.

EHEEXIG
Approved (Document resp) Checked Date Rev Reference

2012-04-09 PA1

1 Description
The document is a drop call analysis of LGU+ LTE network, and from the case
analysis, we find out a big problem existed in LGU+ LTE network which affects
handover performance.

2 Key words
Drop call

LGU+

LTE

Handover performance

ANR

3 Outline
• Typical neighbor relation in LGU+ LTE NW

• ANR work flow

• Drop call analysis

• Solution and experience


Drop Call Analysis in LTE Network
Ericsson Internal
DROP CALL ANALYSIS 3 (9)
Prepared (Subject resp) No.

EHEEXIG
Approved (Document resp) Checked Date Rev Reference

2012-04-09 PA1

4 Case Analysis

4.1 Typical neighbor relation in LGU+ LTE NW

A typical neighbor relation in LGU+ LTE network is as following:

Picture 4.1.1 – a typical neighbor relation

The reasons resulting in the neighbor relation are because:

One eNB has at least six sectors and all sectors may be in different places which
may have more than 1km distance. At the same time one sector may have more
than one antenna.

All eNBs launched with different phases.

All neighbor relations are generated by ANR.

4.2 ANR Work Flow (only simple description)

Step 1:

UE reports neighbor cell PCI information;

Step 2:

If serving cell finds the reported PCI from UE is not in its neighbor relation, the
ANR function will ask UE to report CGI information of neighbor cell.
Drop Call Analysis in LTE Network
Ericsson Internal
DROP CALL ANALYSIS 4 (9)
Prepared (Subject resp) No.

EHEEXIG
Approved (Document resp) Checked Date Rev Reference

2012-04-09 PA1

Step 3:

ANR function creates a new neighbor relation when it gets neighbor CGI
information.

More detailed working flow of ANR is in feature description of Alex.

4.3 Drop Call Analysis

We met lots of drop calls in RF tuning procedure of Yeouido cluster in Seoul, and
we compared all drop calls of different test logfiles and found out most drop calls
are in specific cells, just as following example:

Picture 4.3.1 – Drop calls plot

So we chose a drop call in cell 72505_4 to do detailed analysis.

At first we checked messages flow when drop call occurred, just as following
pictures:
Drop Call Analysis in LTE Network
Ericsson Internal
DROP CALL ANALYSIS 5 (9)
Prepared (Subject resp) No.

EHEEXIG
Approved (Document resp) Checked Date Rev Reference

2012-04-09 PA1

Picture 4.3.2 - Uplink MR from UE

From the MR, we can know a new neighbor cell which has a PCI = 6 have a
better RF condition comparing to serving cell 72505_4. So the eNB sent
“RrcConnectionReconfiguration” message to UE and ask it handover to
candidate neighbor cell which PCI is 6.

Picture 4.3.3 – Rach Failure to candidate neighbor cell

The UE starts to synchronize with candidate cell (PCI =6) but fails at RACH
procedure because of “No RAR” reason.
Drop Call Analysis in LTE Network
Ericsson Internal
DROP CALL ANALYSIS 6 (9)
Prepared (Subject resp) No.

EHEEXIG
Approved (Document resp) Checked Date Rev Reference

2012-04-09 PA1

Note:

No RAR:

In RACH procedure, UE sends RACH preamble to eNB which names as “MSG 1” and eNB
responses MSG 1 if it receives the MSG 1. If UE doesn’t receive eNB response, we call it “No
RAR”.

After RACH uplink sync failure and RRC re-establishment failure, the UE entered
RRC_Idle mode. According Ch.5.3.7.8&5.3.12 of 3GPP TS 36.331 and Ch.5.2.7
of 3GPP TS 36.304, the UE will do cell-reselection operation. From picture 4.3.4,
we can know the UE camped on a cell PCI =6 (72506_0).

Picture 4.3.4 – cell reselection to cell 72506_0

From above analysis, we can know the drop call is because of handover failure,
so we checked the neighbor relation of serving cell 72505_4, and found out an
existed neighbor relation between 72505_4 and 69704_0 which has same PCI =
6 with cell 72506_0, just as picture 4.3.5 showing:
Drop Call Analysis in LTE Network
Ericsson Internal
DROP CALL ANALYSIS 7 (9)
Prepared (Subject resp) No.

EHEEXIG
Approved (Document resp) Checked Date Rev Reference

2012-04-09 PA1

Picture 4.3.5 – neighbor relation between 72505_4 and 69704_0

From the map we can know the distance between 72505_4 and 69704_0 is
3.5km, and distance between 72505_4 and 72506_0 is only about 0.2km. From
analysis above, we knew the target cell is not 69704_0 but 72506_0, but because
a PCI confusion, the handover is directed to cell 69704_0 and failed because far
distance.
Drop Call Analysis in LTE Network
Ericsson Internal
DROP CALL ANALYSIS 8 (9)
Prepared (Subject resp) No.

EHEEXIG
Approved (Document resp) Checked Date Rev Reference

2012-04-09 PA1

5 Solution and Experience


We suggested to set parameter “isHoAllowed” to false for the relation 72505_4
<>69704_0 and check handover performance.

Two week later customer deleted all neighbor relations of eNB 72505 and
creates again by ANR, certainly the handover and drop call performance are
going better than before for cell 72505_4.

From this case, we further analyze handover performance of Yeouido cluster and
found out lots of PCI confusion which result in poor handover performance, just
as table 5.1:

pmH
pmHo H
Target Target Target Existed Existed oExe
S_cell S_cell S_cell Existed ExeAt O
n_cell n_cell n_cell n_Cell n_cell Succ
name CGI PCI n_cell ID tLteIn S
name CGI PCI CGI PCI LteIn
traF R
traF
4506- 4506- 4506- 0
72505_5 72505-5 123 72508_2 72508-2 201 71176_4 71176-4 201 7303 0 %
4506- 4506- 4506- 0
72505_4 72505-4 407 71180_3 71180-3 249 69725_3 69725-3 249 1308 0 %
4506- 4506- 4506- 0
72505_4 72505-4 407 72508_2 72508-2 201 71176_4 71176-4 201 743 0 %
4506- 4506- 4506- 0
72505_4 72505-4 407 72539_3 72539-3 250 69713_5 69713-5 250 276 0 %
4506- 4506- 4506- 0
71491_0 71491-0 33 71386_0 71386-0 178 71410_0 71410-0 178 3845 0 %
4506- 4506- 4506- 0
71426_3 71426-3 405 72506_0 72506-0 6 71172_3 71172-3 6 2251 0 %
4506- 4506- 4506- 0
72540_0 72540-0 24 72506_1 72506-1 212 72538_3 72538-3 212 1243 0 %
4506- 4506- 4506- 0
72507_2 72507-2 401 72506_0 72506-0 6 72530_5 72530-5 6 1163 0 %
4506- 4506- 4506- 0
71559_4 71559-4 186 72506_0 72506-0 6 72530_5 72530-5 6 569 0 %
4506- 4506- 4506- 0
71180_4 71180-4 219 72506_1 72506-1 212 72538_3 72538-3 212 747 0 %
4506- 4506- 4506- 0
71426_2 71426-2 391 72506_0 72506-0 6 71172_3 71172-3 6 525 0 %

Table 5.1 PCI confusion cell list

From this case, we got experience to improve handover performance:


Drop Call Analysis in LTE Network
Ericsson Internal
DROP CALL ANALYSIS 9 (9)
Prepared (Subject resp) No.

EHEEXIG
Approved (Document resp) Checked Date Rev Reference

2012-04-09 PA1

• Check 24 hours statistics of target cells

• Check handover execution success ratio

HoSuccRate = HoPrepSuccRate * HoExeSuccRate.

If the handover execution success ratio is zero, you’d better to check


neighbor relations of target cell, and most of them are because of same
reason like case above.