LTE X2 handover data path changes PDF - EventHelix.com
LTE X2 handover data path changes PDF - EventHelix.com
LTE X2 handover data path changes PDF - EventHelix.com
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
^{Uplink}|{Downlink} Interfaces (Successful Handover)<br />
<strong>LTE</strong> Mobile eNodeB Network Core Network<br />
UE Target eNodeB Source eNodeB SGW PGW<br />
EventStudio System Designer 6<br />
20-Apr-13 20:28 (Page 1)<br />
Before the <strong>handover</strong><br />
Downlink <strong>data</strong> flow before <strong>handover</strong><br />
Downlink Data<br />
Downlink Data<br />
s1_teid_dl1<br />
s1_teid_dl1<br />
Downlink Data<br />
Uplink <strong>data</strong> flow before <strong>handover</strong><br />
Uplink Data<br />
Uplink Data<br />
s1_teid_ul1<br />
s1_teid_ul1<br />
Uplink Data<br />
Handover preparation<br />
s1_teid_ul2<br />
Uplink S1 Bearer Establishment<br />
s1_teid_ul2<br />
GTP connect for the uplink side is<br />
established between the Target<br />
eNodeB and the serving SGW.<br />
Handover execution<br />
Downlink <strong>data</strong> flow during <strong>handover</strong> preparation<br />
Downlink Data<br />
x2_teid<br />
x2_teid<br />
Downlink Data<br />
Downlink Data<br />
s1_teid_dl1<br />
s1_teid_dl1<br />
Uplink <strong>data</strong> flow during <strong>handover</strong> preparation<br />
Uplink Data<br />
Uplink Data<br />
s1_teid_ul1<br />
s1_teid_ul1<br />
Uplink Data<br />
Synchronizing with target cell<br />
Transmit transmission of queued downlink<br />
<strong>data</strong><br />
Downlink Data<br />
Downlink Data
^{Uplink}|{Downlink} Interfaces (Successful Handover)<br />
<strong>LTE</strong> Mobile eNodeB Network Core Network<br />
UE Target eNodeB Source eNodeB SGW PGW<br />
Downlink Data<br />
EventStudio System Designer 6<br />
20-Apr-13 20:28 (Page 2)<br />
Downlink <strong>data</strong> flow during <strong>handover</strong> execution<br />
Downlink Data<br />
Downlink Data<br />
x2_teid<br />
x2_teid<br />
Downlink Data<br />
Downlink Data<br />
s1_teid_dl1<br />
s1_teid_dl1<br />
Uplink <strong>data</strong> flow during <strong>handover</strong> execution<br />
Uplink Data<br />
s1_teid_ul2<br />
Uplink Data<br />
s1_teid_ul2<br />
Uplink Data<br />
Handover <strong>com</strong>pletion<br />
Switching <strong>path</strong><br />
Send end marker<br />
Downlink <strong>data</strong> flow after <strong>handover</strong><br />
Downlink Data<br />
s1_teid_dl2<br />
Downlink Data<br />
s1_teid_dl2<br />
SGW is now sending the <strong>data</strong> using<br />
the target eNodeB TEID.<br />
Downlink Data
Change language