FP7 ICT-SOCRATES
Handover parameter
- ptimization in LTE self-
- rganizing networks
organizing networks TD (10)10068 COST 2100, 10 th MCM Athens, - - PowerPoint PPT Presentation
FP7 ICT-SOCRATES Handover parameter optimization in LTE self- organizing networks TD (10)10068 COST 2100, 10 th MCM Athens, Greece February 3 rd 5 th TUBS, Braunschweig, Germany IBBT, Ghent, Belgium VOD, Newbury, England Outline 1.
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
2/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
3/22
WWW.FP7-SOCRATES.EU
Assembling Scenario Data Processing Data
User locations Environment Network Braunschweig Scenario Traffic Distri- bution Network data OpenSteetMap
Generating Source Data
Correlated User Snapshots Decorated User Snapshots Network Information LTE Simulator
Simulations
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
4/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
5/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
Start Read input data Build Network Build Users
Yes No
End of Simulation? Set Power Mask Call Generation End Update RSRP/SINR HO procedure HO algorithm Next step 6/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
7/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
n
fad
ue
c
8/22
WWW.FP7-SOCRATES.EU
Simulation parameter Value Simulation time 200 [s] Simulation step time 0.01 [s] Simulation area (mobile users) 1.5 km * 1.5 km Number of users 30 eNodeB transmit power 46 [dBm] Number of considered cells in the scenario 76 Measured cells (N) 21 Considered interfering cells for SINR calculations 20 Critical ping-pong handover time (T_crit) 5 [s] Handover execution time 0.25 [s] SINR averaging window 0.1 [s]
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
9/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
2 4 6 8 10 0.1 0.25 0.5 2 1 5 0.02 0.04
Hysteresis [dB] Handover Failures Time-to-Trigger [s] Handover failure ratio
10/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
2 4 6 8 10 0.1 0.25 0.5 1 2 5 0.2 0.4 0.6 0.8
Hysteresis [dB] Ping-Pong Handovers Time-to-Trigger [s] Ping-Pong handover ratio
11/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
2 4 6 8 10 0.1 0.25 0.5 1 2 5 0.2 0.4 0.6 0.8
Hysteresis [dB] Call drops Time-to-Trigger [s] Call dropping ratio
12/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
13/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
2 4 6 8 10 0.1 0.25 0.5 1 2 5 0.5 1
Hysteresis [dB] Handover Performance (weights = [1 0.5 2]) Time-to-Trigger [s] Normalised sum of weighted HO failure rate, ping-pong HO rate and call dropping rate
14/22
WWW.FP7-SOCRATES.EU
1 2 3 4 5 6 7 8 9 10 0.1 0.25 0.5 1 2 5
Operating Points (Threshold: 5%) Hysteresis [dB] Time-to-Trigger [s]
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
15/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
16/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
100 200 300 400 500 600 700 800 900 1000 5 10 15 20 25
Time [s] Ratio [%] Handover Performance for the operating point (4, 0.48)
Handover failure Ping-Pong handover Call dropping
17/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik 100 200 300 400 500 600 700 800 900 1000 0.5 1 1.5 2 2.5 3 3.5 4
Time [s] Handover failure ratio [%] Handover failure performance Operating point (4, 0.48) Operating point (6, 0.32) Operating point (8, 0.1) Operating point (9, 0.08) 100 200 300 400 500 600 700 800 900 1000 5 10 15 20 25 Time [s] Ping-Pong handover ratio [%] Ping-Pong handover performance Operating point (4, 0.48) Operating point (6, 0.32) Operating point (8, 0.1) Operating point (9, 0.08) 100 200 300 400 500 600 700 800 900 1000 1 2 3 4 5 6
Time [s] Call dropping ratio [%] Call dropping performance Operating point (4, 0.48) Operating point (6, 0.32) Operating point (8, 0.1) Operating point (9, 0.08)
18/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
HO SON algortihm Next cell 1) Update HPIs HPIs < threshold? Yes No Increase bad performance time Increase good performance time 2) 4) Reset good performance time Reset bad performance time Good perform- ance? Yes No Decrease HPI thresholds Bad perform- ance? No Reset good performance time Change handover
Yes Reset bad performance time 11) 8) 3) 5) 6) 7) 9) 10) 12) 13)
< 5 dB ↑ TTT
19/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
100 200 300 400 500 600 700 800 900 1000 1 2 3 4 5 6 7 8 9 10
Time [s] Ratio [%] Handover performance for the operating point (6, 0.32)
Handover failure Ping-Pong handover Call dropping
20/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
100 200 300 400 500 600 700 800 900 1000 1 2 3 4 5 6 7 8
Time [s] Ratio [%] Handover performance (Optimisation)
Handover failure Ping-Pong handover Call dropping
21/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
22/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik
HO procedure Next active user HO command send? Yes No Find the best server Yes Connected to the best server? 1) 2) 3) 4) No Save best server as HO candidate 5) 8) If new cell is best server set back HO
6) Increase handover criteria time 7) Yes HO criteria time > TTT? No Send Handover command
24/22
WWW.FP7-SOCRATES.EU
Dipl.-Ing. Thomas Jansen, TU Braunschweig, Institut für Nachrichtentechnik Yes No 13) Increase HO duration time 10) HO duration > HO execution? 11) Handover complete 12) Save successful Handover Update UE History 14) Next active user 1) HO failure
17) Save Handover failure 18) Hand back successful? 19) Yes No Yes No Reconnect to Source eNode B 21) Save call drop during Handover 20) Ping-Pong HO detected? 15) No Yes Save Ping-Pong Handover 16)
25/22