problem in stop and wait ARQ and find their solutions?
Answers
Answer:
Hey mate here is ur answer
Explanation:
Stop and Wait protocol, its problems and solutions. It is the simplest flow control method in which the sender will send the packet and then wait for the acknowledgement by the receiver that it has received the packet then it will send the next packet. ... Note: Stop and wait is better for less distance.
Answer:
Explanation:
- The problem of a damaged data packet
In STOP and WAIT protocol whenever a data packet is damaged/corrupted, the receiver then sends negative feedback to the sender and then it re sends the same data packet.
2. Limitations
The Stop & Wait ARQ is very less efficient because the sender window size is 1, which allows the sender to keep only one frame without feedback. So, the sender sends a data packet and waits for the feedback, and it gets the feedback it sends another data packet.
3.Improving Efficiency
In STOP and WAIT protocol in order to improve efficiency, we can increase the window size on both ends.
4. The problem of lost Feedback
The problem of delayed/lost feedback(which used to happen in Stop & Wait protocol) is solved by putting sequence numbers on data packets.
5. Problem of a lost data packet
For solving this problem, we use time out timer, after transmitting the data packet to the receiver through the communication channel, the sender starts the time out timer. Now if the data packet's feedback is received by the sender before the timer expires, then the sender stops the timer and transmits the next data packet