

Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
Two common error control mechanisms, stop-and-wait automatic repeat request (arq) and go-back-n arq, used to mitigate errors in noisy channels. Stop-and-wait arq adds redundancy bits to frames and relies on the receiver's silence to detect errors. Go-back-n arq allows the sender to send multiple frames before receiving acknowledgments, but it can be inefficient for noisy links due to the increased likelihood of frame damage and resending.
What you will learn
Typology: Study notes
1 / 2
This page cannot be seen from the preview
Don't miss anything!
Q2. What are the two protocols for noisy channels? Ans- The two protocols for noisy channels are-
1. Stop-and-Wait Automatic Repeat Request:- The Stop-and-Wait Automatic Repeat Request (Stop-and-Wait ARQ), adds a simple error control mechanism to the Stop-and-Wait Protocol. To detect and correct corrupted frames, we need to add redundancy bits to our data frame. When the frame arrives at the receiver site, it is checked and if it is corrupted, it is silently discarded. The detection of errors in this protocol is manifested by the silence of the receiver. The protocol specifies that frames need to be numbered. This is done by using sequence numbers. A field is added to the data frame to hold the sequence number of that frame.
2. Go-Back-N Automatic Repeat Request:- In this protocol we can send several frames before receiving acknowledgments; we keep a copy of these frames until the acknowledgments arrive. Go-Back-N ARQ simplifies the process at the receiver site. The receiver keeps track of only one variable, and there is no need to buffer out-of-order frames; they are simply discarded. However, this protocol is very inefficient for a noisy link. In a noisy link a frame has a higher probability of damage, which means the resending of multiple frames. This resending uses up the bandwidth and slows down the transmission. Frames from a sending station are numbered sequentially. However, because we need to include the sequence number of each frame in the header, we need to set a limit.