1 Compare I-TCP, S-TCP and M-TCP 2 Understand CO3: Assignment # 2
1 Compare I-TCP, S-TCP and M-TCP 2 Understand CO3: Assignment # 2
1) Indirect TCP
2) Snooping TCP
3) Mobile TCP
I-TCP segments a TCP connection into a fixed part and wireless part.
Standard TCP is used between CH and AP. In teh same way, Wireless TCP is used between MH and AP.
Here, AP can act as proxy, i.e. -> AP will behave here MH for CH, and CH for MH.
If CH send packet,the AP will take it and ACK to CH, and later will try to forward these packet to MH.
Similarly, if MH wants to send packet, the AP will ACK it and tries to forward the packet to CH.
If packet lost in wireless link, the MH will notice this, and immediately retransmit it.
Socket and State Migration- Please refer the diagram from internet source.
---------------------------
After the registartion to a new FA by MH, this new FA responsibility to inform the old FA, about the
current location to enable packet forwarding.
Sockets and buffer content must migrate to new FA. In socktes, there is a current state of TCP resides -
sequence no., address, port.
The problem in I-TCp is an MH never ack to CH, for every packet it receives.
As 1.FA takes the data from CH, then directly ACK it to CH (which is not good), as CH will always think
that the packet reached to MH (as CH thinks that FA = MH)
In such case, we have 2.improvided I-TCP to Snooping TCP (please refer the diagram from internet).
Here is snoop TCP, the FA will not directly send the ack to CH, but will buffer 3.(buffering) all data from
CH first, then slowly sends these packts to MH (snooping).
If FA doesn't receive an ACK from MH, withing certain amount of time, CH will assume, that either the
packet or ACK lost, and now FA could retransmit pckt directly from buffer, performing much faster
retranmission.
Mobile-TCP (M-TCP) -- Please refer the diagram from internet source
-------------------------------------
* SH responsible for exchangined data between both part similar to proxy in I-TCP.
* If a packet lost on wireless link, it has to be transmitted by original sender (maintain end to end
semantics)
* If SH doesnt receive an ACK for sometime from MH, it assumes the MH is disconnected.
* SH will choke the sender by setting the sender window size = 0 --> forces the sender to go into
persistent mode (it cannot send the data, or retransmission).
* As soon as, the SH detects the connectivity again, it reopens the window of the sender to the old
value.
Slow start is most useful mechanism in fixed network(Wired link), but it decreases efficiency of TCP
whenever there is a mobility of sender and receiver.
From a missing ACK, TCP only concludes it is because of congestion situation, but it always not main
reason for packet loss or ACK loss.
a) Error rates on wireless links are order of magnitude higher compared to fixed network (wired).
Packet loss much common in this area, and cannot always be compansated by layer 2 retransmission
(ARQ and FEC),
We are transmitting the same packet twice (duplicate packets)over a bad link, which is not good.
detection of these duplicate packets on layer 2 is hard, as more no. of devices using end-end encryption.
When using Mobile IP, there could be still some packets in transit to the old FA, while MN movies to the
new FA.
The old FA may not be able to forward those packet to the new FA, or even cannot buffer it, if MN takes
too long time to come back to old FA.
---> Traditional TCP mechanism detects missing ACK via time-outs, and always concludes packets loss
due to "congestion".
Sender receving continous ACK for the same packet, this informs two things -
The gap in the packet stream is not due to severe congestion always, but it could be a simple packet loss
due to a transmission error.
Once it find out by sender, the sender can now retransmit the missing packet before the timer expires -
This behavoir is known as Fast Retransmit.
The recepient of ACK shows that there is no congestion, to justify a slow start. The sender can continue
with the current congestion window, the sender can perform "Fast Recovery" from packet loss or any
crash happens.
WAP Forum developes standards for application deployment over wireless devices like PDA, mobile
phone.
The wap request from the browser (user agent) is routed through a wap gateway.
The gateway acts as an intermediary node between client and network throgh a wireless last mile (GSM,
GPRS, CDMA).
The gateway also does encoding and decoding of the wap request and wap response from client to the
server and vice versa.
The purpose of encoding and decoding is to minimize the size of data transfer over the air.
//././/././
Mobility supports relies on the existence of at least some infrastructure,
However, there may be several situation where users of a network cannot rely on infrastructure
network ?? ---> because it is too expnesive, in that situation, user will not rely on it.
Effectivness --> Services provided by existing infrastructure might be too expensive for certain
application. For example --> An application sends only small status information every other minute, it
would be too expensive if uses infrastructure network.
There are two approaches based on the connection you are using – Wired Connection - >
Detection and recovery after the congestion
This thing needs to -> have better flow control mechanism.