lower layer implementation measurements

12
MPTCP Lower Layer Implementation & Measurements Georg Hampel, Anil Rana, Thierry Klein Bell Labs, Alcatel-Lucent

Upload: others

Post on 17-Mar-2022

4 views

Category:

Documents


0 download

TRANSCRIPT

MPTCP

Lower Layer Implementation &

Measurements

Georg Hampel, Anil Rana, Thierry Klein Bell Labs, Alcatel-Lucent

Host + L4 MPTCP Impl

TCP

Application

MPTCP

Subflow

L1/L2 L1/L2

TCP

IP

Relay

IP

Subflow

IP

Application

IP

MPTCP

Host + LL MPTCP Impl

Packet in New Packets Packet out

Filter rules

Sequential processing à No payload buffering!

Priorities 1.  Mobility across middle-boxes (MBB & BBM)

2.  Incremental deployment (MPTCP Proxy)

3.  (Limited) Multipath support

Handover Trials •  Lab Wi-Fi ó Lab LTE

•  Wi-Fi + Corporate Nwk (NJ) ó Carrier LTE

•  Wi-Fi + ISP (Manhattan Apt) ó Carrier LTE

•  Wi-Fi + ISP (Manhattan Café) ó Carrier LTE

Middle-box traversal

client server

LTE

Wi-Fi

NJ Lab NJ Lab

client server

LTE

Wi-Fi

1.   NJ Lab 2.   NY Apt

3.   NY Cafe NJ Lab

Carrier

1.  Corp Nwk 2.  ISP 2 3.  ISP 3

ISP1

client server

LTE

Wi-Fi

NJ Lab NJ Lab

Lab Trial

0.00E+00

2.00E+06

4.00E+06

6.00E+06

8.00E+06

1.00E+07

1.20E+07

1.40E+07

1.60E+07

1.80E+07

2.00E+07

5 6 7 8 9 10 11 12 13Time (sec)

TCP

SEQ

No

(nor

mal

ized

)

Handover

Handover

MPTCP-based Mobility - Make before Break -

Wi-Fi

LTE(~12.5Mbps)

Wi-Fi(~50Mbps)

LTE

Handover

0.00E+00

2.00E+06

4.00E+06

6.00E+06

8.00E+06

1.00E+07

1.20E+07

1.40E+07

1.60E+07

1.80E+07

2.00E+07

18 20 22 24 26 28 30 32 34 36 38 40Time (sec)

TCP

SEQ

No

(nor

mal

ized

)

Handover

Handover

Handover

MPTCP-based Mobility - Make before Break -

Corporate Wi-Fi

Carrier LTE(~8Mbps)

Corporate Wi-Fi(~8Mbps)

Carrier LTE

client server

LTE

Wi-Fi

Carrier

Corp ISP 1

Corporate Nwk

On TELNET ü

client server

LTE

Wi-Fi

Carrier

ISP 2 ISP 1

0.00E+00

2.00E+06

4.00E+06

6.00E+06

8.00E+06

1.00E+07

1.20E+07

1.40E+07

1.60E+07

1.80E+07

2.00E+07

0 10 20 30 40 50 60 70 80 90 100 110 120Time (sec)

TCP

SEQ

No

(nor

mal

ized

)

Handover

Handover

MPTCP-based Mobility - Make before Break -

IPS-2 Wi-Fi

Carrier LTE(~0.6 Mbps)

ISP-2 Wi-Fi(~6.5 Mbps)

Carrier LTE

Handover

Manhattan Apartment

client server

LTE

Wi-Fi

Carrier

ISP 3 ISP 1

Manhattan Cafe

0.00E+00

2.00E+06

4.00E+06

6.00E+06

8.00E+06

1.00E+07

1.20E+07

1.40E+07

1.60E+07

1.80E+07

0 10 20 30 40 50 60 70Time (sec)

TCP

SEQ

No

(nor

mal

ized

)

Handover

Handover

MPTCP-based Mobility - Make before Break -

ISP-3 Wi-Fi

Carrier LTE(~ 1.3 - 5 Mbps)

ISP-3 Wi-Fi(~1.4 Mbps)

Carrier LTE

Handover

client server

LTE

Wi-Fi

Carrier

Corp ISP 1

Corporate Environment

Make before Break

9.04E+06

9.08E+06

9.12E+06

9.16E+06

9.20E+06

9.24E+06

9.28E+06

9.32E+06

29.4 29.45 29.5 29.55 29.6 29.65 29.7Time (sec)

TCP

SEQ

/AC

K N

o (n

orm

aliz

ed)

SEQ No - Wi-Fi ACK No - Wi-Fi SEQ No - LTE ACK No - LTE

Wi-Fi Subflow ACK with MP_PRIO option

MPTCP-based Mobility - Make before Break -

Carrier LTE

Corporate Wi-Fi

~150msec

client server

LTE

Wi-Fi

Carrier

Corp ISP 1

Corporate Environment

Make before Break

4.50E+06

4.55E+06

4.60E+06

4.65E+06

4.70E+06

4.75E+06

4.80E+06

4.85E+06

4.90E+06

25.1 25.15 25.2 25.25 25.3 25.35 25.4Time (sec)

TCP

SEQ

/AC

K N

o (n

orm

aliz

ed)

SEQ No - Wi-Fi ACK No - Wi-Fi SEQ No - LTE ACK No - LTE

LTE Subflow ACK with MP_PRIO option

MPTCP-based Mobility - Make before Break -

Corporate Wi-Fi

Carrier LTE

~ 80msec

1.38E+07

1.39E+07

1.39E+07

1.40E+07

1.40E+07

1.41E+07

1.41E+07

1.42E+07

1.42E+07

44.5 45 45.5 46 46.5 47 47.5 48 48.5 49 49.5 50

Time (sec)

TCP

SEQ

/AC

K N

o (n

orm

aliz

ed)

SEQ No - Wi-Fi ACK No - Wi-Fi SEQ No - LTE ACK No - LTE

MPTCP-based Mobility - Break before Make -

Corporate Wi-Fi

Carrier LTE

3 sec delay without SACK !

client server

LTE

Wi-Fi

Carrier

Corp ISP 1

Corporate Environment

Break before Make

Cross-Subflow Retransmissions Packet

Loss

Problems with present MPTCP design

1.  No inference from subflow ACK to data ACK:

à Should work if only one active subflow

2.  Unnecessary overhead when only 1 active subflow

Conclusion: Enhance MPTCP design for mobility use cases