Professional Documents
Culture Documents
An Experimental Study of ARQ Protocol in 802.11b Wireless LAN
An Experimental Study of ARQ Protocol in 802.11b Wireless LAN
2 more:
Self-collision of TCP traffic
Changes in collision rates due to
Algorithm
Skip
Why?
Transmission error in air
Channel noise
Channel interference
Packet collisions
No direct collision detection in 802.11b
TCP or UDP on top of 802.11b
Misinterpret packet loss as congestion
loss (TCP)
Set-up for Experiments
Statistics from AP Manager
Multiple Transmit Retry Count (MTRC)
>= 2 retransmission attempts (successful)
Transmit Retry Count (TRC)
>= 1 retransmission attempts (successful)
Transmit Failed Count (TFC)
Still failed after 3 retransmission attempts
Experiment (I)
Is ARQ adequate to compensate for packet lo
ss due to transmission error?
Server: NetProbe
Client: NetProbe
Protocol: UDP
Packet size: 1460 bytes
Data rate: 500kbps
Number of packets: 100,000
Distance: 5m (best), 15m (good),
25m (marginal)
Result of experiment (I)
Link quality Best Good Marginal
TRC 661 2322 18073
MTRC 16 1172 4030
TFC 10 264 760
Loss rate 0.01% 0.26% 0.76%
Let be this
Result of experiment (I)
TRC MTRC 4 * TFC
Ploss
num _ of _ packets TRC MTRC 4 * TFC
200
Reno
Throughput(kBytes/s)
180
160
140
120
100
80
60
40
20
0
1.00E-05 1.00E-04 1.00E-03 1.00E-02 1.00E-01 1.00E+00
IDEAL
y=p(1-p)x
p=0.0676
REAL
Conclusions
One-way traffic
No collision
ARQ is effective in keeping the loss rate to
below 0.01
Two-way traffic
Collisions exist
Loss rate may rise beyond 0.01
Conclusions
Two possible improvements
Strengthen the link-layer ARQ
Modify TCP
Two issues to be studied
Self-collision in TCP
Movements of clients
Packet loss in 802.11b is not random