 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| n |
design
does not cache packets from MH to FH
|
|
|
|
– |
bulk
of packet losses will be between MH and base
|
|
|
|
– |
but
snooping on packets generates requests for retransmissions at base
|
|
|
much
faster than from remote FH
|
|
|
|
– |
enhance
TCP implementation at MH with “selective ACK” option:
|
|
|
|
n |
base
keeps track of packets lost in a transmission window
|
|
|
|
n |
sends
bit vector back to MH to trigger retransmission of lost packets
|
|
|
| n |
mobility
handling:
|
|
|
|
– |
when
handoff is requested by MH or anticipated by base station,
|
|
|
nearby
base stations begin receiving packets destined for MH, priming
|
|
their
cache
|
|
|
|
– |
caches
synchronized during actual handoff (since nearby bases cannot
|
|
|
snoop
on ACKs)
|
|
