Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 26

19-23 May 2008

Beijing, China

Distributed Protocol
Stacks

Dzmitry Kliazovich and Fabrizio Granelli

University of Trento, Italy


TCP/IP Layering
 TCP/IP protocol reference model, the de facto standard in
Internet, is based on ISO/OSI layering principles
 Reasons: Interoperability and Fast Deployment

 TCP/IP layering drove the success of Internet in 90s


 Demonstrates good performance in homogeneous networks
which rely on similar PHY technologies

However, nowadays networks are


different - Heterogeneous !!!

26 - 30 November 2007 Fabrizio Granelli (granelli@dit.unitn.it)


Heterogeneity
 Network Heterogeneity
 Devices: hand-held, mobile, sensors
 Links & protocols: Wireless and Wired
 Services: variety of applications, data and services
 Need for rapid deployment and organization

 Leads to poor TCP/IP performance, due to


 Strict layering
 Lack of cooperation and coordination

C. Barakat, E. Altman, and W. Dabbous, “On TCP performance in a


heterogeneous network: a survey”, IEEE Communications Magazine,
vol. 38, no. 1, January 2000, pp. 40 – 46.

26 - 30 November 2007 Fabrizio Granelli (granelli@dit.unitn.it)


TCP/IP optimization in
Heterogeneous Networks
 Cross-Layering
 Allows awareness and cooperation between protocol layers
 Joined, coupled design
 Examples: TCP notification of non-congestion related losses

 Agent-Based Networking
 Aims at introduction of active functionalities in the passive
network core
 Examples: Web-proxy, cashing proxy

26 - 30 November 2007 Fabrizio Granelli (granelli@dit.unitn.it)


Our Approach
Agent-based
Layered Design Cross-Layering
Networking

Distributed Protocol Stacks

 Idea: Extend the idea of protocol stack


modularity making it network-wide
26 - 30 November 2007 Fabrizio Granelli (granelli@dit.unitn.it)
Distributed Protocol Stacks
 Design Details
 Each functional block of the protocol stack (a protocol layer or
its part) can be abstracted into a separate module and
implemented at a different node in the network
 Communication between host protocol stack and removed
module is performed using a custom “lightweight” protocol

 Applications (or What is it for?)


 Move protocol stack functions that generate high communication
overhead into the network core behind the bottleneck link
 Caution: not all the protocol stack functions can be abstracted
and separated

26 - 30 November 2007 Fabrizio Granelli (granelli@dit.unitn.it)


Distributed Protocol Stacks
Wide-Area
Network (WAN) Subnet

Host Node
Network Element
Module Running Layer n
Environment (MRE)

Functional
block
Functional Block
Library
layer n layer 3
Internal Module
Connection Interface
(IMCI)
layer 2 layer 2

layer 1 layer 1

Module Interconnection
Protocol (MIP)
Router protocol stack Host protocol stack

External Module
Connection Interface
(EMCI)

26 - 30 November 2007 Fabrizio Granelli (granelli@dit.unitn.it)


Distributed Protocol Stacks
Wide-Area
Network (WAN) Subnet

Host Node
Network Element

Design Procedures
Module Running Layer n


Environment (MRE)

Functional
block
Functional Block
Library
layer n layer 3
Internal Module
Connection Interface
(IMCI)

 Abstraction: identification and isolation of a


layer 2 layer 2

particular function or set of functions of the


layer 1 layer 1

Module Interconnection
Protocol (MIP)

protocol stack
Router protocol stack Host protocol stack

External Module
Connection Interface
(EMCI)

 Detachment: separation of the chosen function or a set of functions into


a standalone functional block as well as its registration, transfer, and
execution with “friendly” network elements (routers, switches, or
gateways)

 Communication between detached functional block and the host


protocol stack

 Execution: triggered by the host node or performed automatically by


Module Running Environment (MRE) implemented by the network
element
26 - 30 November 2007 Fabrizio Granelli (granelli@dit.unitn.it)
Distributed Protocol Stacks
 Concerns
 Interoperability
 Incremental deployment

 Benefits
 Protocol stack performance
 Enablers for new user applications
 Driven by network operator perspective

Design of Distributed Protocol Stack solutions should be driven


by cost/benefits analysis !!!

26 - 30 November 2007 Fabrizio Granelli (granelli@dit.unitn.it)


A Case Study
3G LTE background Bottleneck
link

IP network

File Server Base station User Terminal

Transport TCP data Transport


Output()
TCP ACKs TCP ACKs
ACK gen

Module running
Network environment Network

Link Link Link Link

Physical Physical Physical Physical

Custom
protocol

26 - 30 November 2007 Fabrizio Granelli (granelli@dit.unitn.it)


ARQ Proxy - Approach

Evolved Packet
Core
File Server User Equipment
Enhanced Node B
(UE)
(eNB)
TCP ARQ Proxy MAC MAC ARQ Client TCP

TCP Data
PHY /LL TCP
Headers Data
TCP Data

o Access TCP header Generate


o Get IP addr, port, etc. TCP ACK
TCP ACK
o Generate TCP ACK & store
HARQ TCP
+ Index
TCP ACK ACK Index
Index o Compute TCP ACK
identification index
TCP ACK

26 - 30 November 2007 Fabrizio Granelli (granelli@dit.unitn.it)


ARQ Proxy - Benefits
 Reduced RTT (Round Trip Time)
TCP Data

IP Network
Fixed Host
Enhanced Node B Mobile Node
(FH ) (eNB) (MN)

TCP ACK

Medium Access + TCP ACK


Transmission over radio channel

Dzmitry Kliazovich
(kliazovich@dit.unitn.it) Sept. 11, 2007
ARQ Proxy - Benefits
 End-to-end TCP semantics are maintained
TCP Data

IP Network
Fixed Host
Enhanced Node B Mobile Node
(FH ) (eNB) (MN)

TCP ACK LL-ACK

Dzmitry Kliazovich
(kliazovich@dit.unitn.it) Sept. 11, 2007
ARQ Proxy - Benefits
 Higher channel error rates tolerance
Wired channel Wireless channel
(BER = 10-6 to 10-8) (BER = 10-3 to 10-1)

IP Network
Fixed Host
Enhanced Node B Mobile Node
(FH ) (eNB) (MN)

TCP ACK

No TCP ACK over radio channel

Dzmitry Kliazovich
(kliazovich@dit.unitn.it) Sept. 11, 2007
ARQ Proxy - Benefits
 Mobility & Incremental deployment
No TCP state
related information
is maintained

IP Network
Fixed Host
Enhanced Node B Mobile Node
(FH ) (eNB) (MN)

ARQ Proxy ARQ Client

Dzmitry Kliazovich
(kliazovich@dit.unitn.it) Sept. 11, 2007
Current Activities and Future Work
 ARQ proxy material
 ARQ proxy for WiFi (IEEE 802.11)
• F. Granelli, D. Kliazovich, J. Hui, and M. Devetsikiotis, "Performance Optimization of Single-
Cell Voice over WiFi Communications Using Quantitative Cross-Layering Analysis," 20th
Iternational Teletraffic Congress (ITC'20), Ottawa, Canada, June 2007.

 ARQ proxy for 3G LTE (Super-3G)


• D. Kliazovich, F. Granelli, S. Redana and N. Riato, “Cross-Layer Error Control Optimization
in 3G LTE,” IEEE Global Communications Conference (GLOBECOM), Washington, DC, U.S.A,
December 2007.

 ARQ proxy for WiMAX (IEEE 802.16)


• Submitted for publication in Globecom 2008.

Dzmitry Kliazovich
(kliazovich@dit.unitn.it) Sept. 11, 2007
Current Activities and Future Work
 ARQ proxy material
 EU patent-pending
• D. Kliazovich, F. Granelli, S. Redana, and N. Riato, “Cross-Layer Error
Recovery Optimization for 3G LTE Systems,” EP 07425087.9

 Proposal to 3GPP standardization group

 Under consideration for next generation equipment


produced by Nokia Siemens Network (NSN)

Dzmitry Kliazovich
(kliazovich@dit.unitn.it) Sept. 11, 2007
Conclusions
 Reallocation of protocol stack functions in the network
creates an additional degree of freedom for optimization

 The proposed Distributed Protocol Stacks are considered


for Next Generation Internet (NGI)

 Brings novel applications, optimal protocol stack


performance, and better configurability at the expense
of reduced interoperability and incremental deployment

Dzmitry Kliazovich
(kliazovich@dit.unitn.it) Sept. 11, 2007
Thank you!

26 - 30 November 2007 Fabrizio Granelli (granelli@dit.unitn.it)


ARQ Proxy – Packet Identification
 3G LTE: Hash values  WiFi: Frame Sequence Numbers
Input Hash Value PHY LL
TCP data
Header Header
PHY LL
TCP data
Hash DCF53473
Header Header
function
Sequence
Address 3 Address 4
Control

B0 B3 B4 B15
Fragment Sequence Number
Number

Bits: 4 12

Hybrid ARQ (HARQ-ACK)


or

HARQ
ACK

Enhanced Node B User Equipment


(eNB) (UE)

26 - 30 November 2007 Fabrizio Granelli (granelli@dit.unitn.it)


ARQ Proxy - Limitations
 TCP ACKs are not substituted:
 During connection establishment and connection
termination packets (identified by SIN and FIN flags)
 For TCP ACK encapsulated into TCP data packet in
case of bidirectional data transfer
 For Duplicate TCP ACKs
 TCP ACK advertising exhausted receive buffer
resources (rwnd field)

Dzmitry Kliazovich
(kliazovich@dit.unitn.it) Sept. 11, 2007
Evaluation: 3G LTE scenario
 Round Trip Time (RTT)  Hash value errors
90 0.7

80
0.6

Average TCP Throughput (Mb/s)


70
0.5
60
RTT (ms)

50 0.4

40 0.3

30
0.2
20
0.1
10 TCP
TCP + ARQ Proxy
0 0
0 20 40 60 80 100 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8
Simulation time (s) Hash error rate

Dzmitry Kliazovich
Sept. 11, 2007 (kliazovich@dit.unitn.it)
WiFi: Evaluation Results
 Throughput performance
6 ARQ proxy ON
ARQ proxy OFF
Improvement: 20%
5
Throughput (Mb/s)

Improvement:1
up to 100%

VoIP and Multimedia 0 TCP file transfer,


0 300 600 900 1200 1500
Applications TCP/IP datagram size (Bytes) Ethernet MTU
Dzmitry Kliazovich
(kliazovich@dit.unitn.it) Sept. 11, 2007
WiFi: Evaluation Results
 Round Trip Time (RTT) improvement
60
ARQ proxy OFF

50 Order of
milliseconds
Smooth RTT (msec)

40

30 ARQ proxy ON

20

10

0
0 10 20 30 40 50
Simulation time (seconds)
Dzmitry Kliazovich
(kliazovich@dit.unitn.it) Sept. 11, 2007
WiFi: Evaluation Results
 High error rate tolerance
7
ARQ proxy ON
ARQ proxy OFF
6

5
Throughput (Mb/s)

0
0 0.05 0.1 0.15 0.2 0.25 0.3 0.35
Packet Error Rate (PER)
Dzmitry Kliazovich
(kliazovich@dit.unitn.it) Sept. 11, 2007

You might also like