Stop and Wait Protocol

ELEC3030 (EL336) Computer Networks
S Chen
Simplex Stop and Wait Protocol

Flow control deals with problem that
sender transmits frames faster than
receiver can accept, and solution is
to limit sender into sending no faster
than receiver can handle
Consider the simplex case: data is
transmitted in one direction (Note
although data frames are transmitted
in one direction, frames are going in
both directions, i.e. link is duplex)
sender sends
Stop and wait:
one data
frame,
waits for
acknowledgement
(ACK)
from
receiver before proceeding to transmit
next frame
This simple flow control will break
down if ACK gets lost or errors
occur sender may wait for ACK
that never arrives
49
S Chen
Simplex Stop and Wait with ARQ

For noisy link, pure stop and wait protocol will break down, and solution is to incorporate some
error control mechanism
Stop and wait with ARQ: Automatic Repeat reQuest (ARQ), an error control method, is
incorporated with stop and wait flow control protocol
If error is detected by receiver, it discards the frame and send a negative ACK (NAK), causing
sender to re-send the frame
In case a frame never got to receiver, sender has a timer: each time a frame is sent, timer is set
If no ACK or NAK is received during timeout period, it re-sends the frame
Timer introduces a problem: Suppose timeout and sender retransmits a frame but receiver
actually received the previous transmission receiver has duplicated copies
To avoid receiving and accepting two copies of same frame, frames and ACKs are alternatively
labeled 0 or 1: ACK0 for frame 1, ACK1 for frame 0
An important link parameter is defined by

a=
propagation time
Rd
=
frame time
VL
where R is data rate (bps), d is link distance (m), V is propagation velocity (m/s) and L frame
length (bits)
50
S Chen
Stop and Wait with ARQ (continue)

In error-free case, efficiency or maximum link
utilisation of stop and Wait with ARQ is:
Frame 0
ACK 1
Frame 1
1
1 + 2a
ACK0: frame 1 is received, waiting for next

(frame 0)
ACK1: frame 0 is received, waiting for next
(frame 1)
This is to have 1-bit sequence number, and
implies receiver have buffer for one frame
Frame lost:
A retransmits
ACK 0 lost:
A retransmits
Timeout
Illustration of how stop and wait with ARQ works:
ACK 0
Frame 0
Frame 0
Timeout
U =
B
Time
ACK 1
Frame 1
ACK 0
Frame 1
ACK 0
B discards
duplicate frame
For an LAN with R = 10 Mbps and d = 1 km, using V = 2 108 m/s and L = 500 bits,
a = 0.1 and stop-and-wait procedure has U = 0.83, which has adequate line utilisation
But for a satellite link, link utilisation for stop-and-wait procedure may only be U = 0.001 or
lower, which is clearly wasteful
51
S Chen
Sliding Window Protocol

For large link parameter a, stop and wait protocol is inefficient
A universally accepted flow control procedure is the sliding window protocol
Frames and acknowledgements are numbered using sequence numbers
Sender maintains a list of sequence numbers (frames) it is allowed to transmit, called sending
window
Receiver maintains a list of sequence numbers it is prepared to receive, called receiving window
A sending window of size N means that sender can send up to N frames without the need for
an ACK
A window size of N implies buffer space for N frames
For n-bit sequence number, we have 2n numbers: 0, 1, , 2n 1, but the maximum window
size N = 2n 1 (not 2n)
ACK3 means that receiver has received frame 0 to frame 2 correctly, ready to receive frame 3
(and rest of N frames within window)
In error-free case, efficiency or maximum link utilisation of sliding window protocol is:
1,
N > 2a + 1
U =
N
N < 2a + 1
1+2a ,
Thus it is able to maintain efficiency for large link parameter a: just use large widow size N
52
S Chen
Sliding Window (continue)

Note that U = 1 means that link has no idle time: there are always something in it, either data
frames or ACKs
A:
B:
0 1 2 3 4 5 6 0 1 2 3 4 5 6 0 1
Consider the case of 3-bit sequence 0 1 2 3 4 5 6 0 1 2 3 4 5 6 0 1 F
0
number with maximum window size
F1
N =7
F2
Sending and receiving windows can

shrink or grow during operation
0 1 2 3 4 5 6 0 1 2 3 4 5 6 0 1
0 1 2 3 4 5 6 0 1 2 3 4 5 6 0 1
ACK
0 1 2 3 4 5 6 0 1 2 3 4 5 6 0 1
The receiver do not need to

acknowledge every frames
F4
0 1 2 3 4 5 6 0 1 2 3 4 5 6 0 1
0 1 2 3 4 5 6 0 1 2 3 4 5 6 0 1
F5
F6
ACK
If both sending and receiving

window sizes are N = 1, the
sliding window protocol reduces to
the stop-and-wait
0 1 2 3 4 5 6 0 1 2 3 4 5 6 0 1
F3
This illustration shows that
0 1 2 3 4 5 6 0 1 2 3 4 5 6 0 1
0 1 2 3 4 5 6 0 1 2 3 4 5 6 0 1
In practice, error control must be incorporated with flow control, and we next discuss two common
error control mechanisms
53
S Chen
Go-back-n ARQ
The basic idea of go-back-n error control is: If frame i is damaged, receiver requests retransmission
of all frames starting from frame i
An example:
Notice that all possible cases of

damaged frame and ACK / NAK
must be taken into account
1
2
2
ACK ACK NAK
error
3
6
5
4
ACK ACK ACK ACK
discarded
For n-bit sequence number, maximum window size is N = 2n 1 not N = 2n with

N = 2n confusion may occur
Consider n = 3, if N = 8 what may happen:
Suppose that sender transmits frame 0 and gets
an ACK1
It then transmits frames 1,2,3,4,5,6,7,0 (this is
allowed, as they are within the sending window
of size 8) and gets another ACK1
F0 *
ACK1*
F1,F2,...,F7,F0
ACK1
Either
Ive received F1,...,F7,F0
waiting for (next) F1
or
Ive received F0* then nothing
else, timeout, retrainsmit ACK1*
This could means that all eight frames were received correctly
It could also mean that all eight frames were lost, and receiver is repeating its previous ACK1
With N = 7, this confusing situation is avoided
54
S Chen
Selective-Reject ARQ
In selective-reject ARQ error control, the only frames retransmitted are those
receive a NAK or which time out
An illustrative example:
Selective-reject would appear to be
more efficient than go-back-n, but it
is harder to implement and less used
1
2
2
4
6
5
3
ACK ACK NAK ACK ACK ACK ACK
E
error
buffered
F2-5 released
The window size is also more restrictive: for n-bit sequence number, the maximum
2n
window size is N = 2 to avoid possible confusion
Go-back-n and selective-reject can be seen as trade-offs between link bandwidth
(data rate) and data link layer buffer space
If link bandwidth is large but buffer space is scarce, go-back-n is preferred
If link bandwidth is small but buffer space is pretty, selective-reject is preferred
55
S Chen
From Simplex to Duplex

So far, we consider data transmission in one direction (simplex), although the link is duplex
If two sides exchange data (duplex), each needs to maintain two windows: one for transmitting and
one for receiving
In duplex communication, frames transmitted from either side can be data, ACKs and NAKs
the need to distinguish them
Frame type: Recall in frame header there is a control field, and part of it is typically used as frame
type field to tell what type the frame is
Piggybacking: In duplex situations, piggybacking is often used If one has data and an ACK to
send, it sends both in one frame
Discussion so far: data link layer is primarily concerned with making point-to-point link reliable
It is responsible for transmitting frames from sender to receiver (service to network layer), and
can only uses physical layer to do the job
It has to take into account that transmission error may occur and sender/receiver may operate at
different speeds error control/flow control (ACKs, NAKs, CRC, windows, sequence numbers)
Next lecture will see how all these fit into some data link layer protocols
56
S Chen
Sliding Window with Go-back-n C Codes
57
S Chen
Protocol Verification
How to know a protocol really works specify and verify protocol using, e.g. finite state machine
Each protocol machine (sender or receiver) is at a specific state at every time instant
Each state has zero or more possible transitions to other states
One particular state is initial state: from initial state, some or possibly all other states may be
0
reachable by a sequence of transitions
To
00
Simplex stop and wait ARQ protocol:

State SRC : S = 0, 1 which
frame sender is sending; R = 0, 1
which frame receiver is expecting;
C = 0, 1, A (ACK), (empty)
channel state, i.e. what is in channel
There are 9 transitions
01
7
0
1
000
2
3
10A
0
101
111
0
8
11
10
Who
Frame
Frame network
Transition runs? accepted emitted layer
01A
010
0
1
2
3
4
5
6
7
8
R
S
R
S
R
R
S
S
(frame lost)
0
A
1
A
0
1
(timeout)
(timeout)
A
1
A
0
A
A
0
1
Yes
Yes
No
No
8
(a)
(b)
Initial state (000): sender has just sent frame 0, receiver is expecting frame 0, and frame 0 is
currently in channel
Transition 0 consists of channel losing its contents, transition 1 consists of channel correctly
delivering frame 0 to receiver, and so on
During normal operation, transitions 1,2,3,4 are repeated in order over and over: in each cycle,
two frames are delivered, bringing sender back to initial state
58
S Chen
Summary
Flow control and error control techniques for data link layer:
Stop and wait ARQ, sliding window, go-back-n, selective-reject (repeat)
Data link layer (part I) discussed so far:
It is concerned with making a point-to-point link reliable, and is responsible for
transmitting frames from sender to receiver, can only use physical layer to do job
Error control and flow control (ACKs, NAKs, CRC, sliding windows, sequence
numbers, go-back-n etc.):
How these are included in a data link layer protocol will be discussed in next lecture
59

Stop and Wait Protocol

Uploaded by

Copyright:

Available Formats

Stop and Wait Protocol

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Stop and Wait Protocol

Uploaded by

Copyright:

Available Formats

ELEC3030 (EL336) Computer Networks

Simplex Stop and Wait Protocol

ELEC3030 (EL336) Computer Networks

Simplex Stop and Wait with ARQ

An important link parameter is defined by

ELEC3030 (EL336) Computer Networks

Stop and Wait with ARQ (continue)

ACK0: frame 1 is received, waiting for next

Illustration of how stop and wait with ARQ works:

ELEC3030 (EL336) Computer Networks

Sliding Window Protocol

ELEC3030 (EL336) Computer Networks

Sliding Window (continue)

Sending and receiving windows can

The receiver do not need to

If both sending and receiving

This illustration shows that

ELEC3030 (EL336) Computer Networks

Notice that all possible cases of

For n-bit sequence number, maximum window size is N = 2n 1 not N = 2n with

ELEC3030 (EL336) Computer Networks

ELEC3030 (EL336) Computer Networks

From Simplex to Duplex

ELEC3030 (EL336) Computer Networks

Sliding Window with Go-back-n C Codes

ELEC3030 (EL336) Computer Networks

Simplex stop and wait ARQ protocol:

ELEC3030 (EL336) Computer Networks

You might also like