answersLogoWhite

0

In Stop and Wait ARQ, the sender needs to stop and wait for acknowledgement to each data frame that it has sent to the receiver When the sender sends a data frame to the receiver it starts timer. If the frame that the sender has sent is damaged. The receiver will not get any frame received So, it doesn't send any acknowledgement to that frame. By then, if the timer expires, the sender will resend that frame. In this protocol, sender has to set the timer every time it sends a frame. How ever in Go Back n ARQ, the sender need not wait for the acknowledgement of the first frame it has sent. Sender can send multiple frames while waiting for acknowledgement. Several frames can be sent before we receive news about the previous frames. This s aves time. A task has begun before the previous task has ended. Here the task is sending all the subsequent frames after sending the first frame before getting the acknowledgement for the first frame. so eventually multiple frames are to be put in transition while waiting for acknowledgement. This is called Pipelining. this improves the efficiency of the transmission.

User Avatar

Wiki User

15y ago

What else can I help you with?

Continue Learning about Communications