0% found this document useful (0 votes)
5 views32 pages

Chapter Seven

The document discusses various data transmission techniques, focusing on flow control, error detection, and acknowledgment mechanisms. It outlines methods such as Stop and Wait, Go Back N, and Selective Reject for managing frame transmission and retransmissions. Additionally, it covers HDLC protocols and configurations for primary and secondary stations in data communication.

Uploaded by

angelina54320291
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
5 views32 pages

Chapter Seven

The document discusses various data transmission techniques, focusing on flow control, error detection, and acknowledgment mechanisms. It outlines methods such as Stop and Wait, Go Back N, and Selective Reject for managing frame transmission and retransmissions. Additionally, it covers HDLC protocols and configurations for primary and secondary stations in data communication.

Uploaded by

angelina54320291
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 32

 Ensuring the sending entity does not

overwhelm the receiving entity


› Preventing buffer overflow
 Transmission time
› Time taken to emit all bits into medium
 Propagation time
› Time for a bit to traverse the link
 Source transmits frame
 Destination receives frame and replies
with acknowledgement
 Source waits for ACK before sending
next frame
 Destination can stop flow by not send
ACK
 Works well for a few large frames
 Large block of data may be split into
small frames
› Limited buffer size
› Errors detected sooner (when whole frame
received)
› On error, retransmission of smaller frames
is needed
› Prevents one station occupying medium for
long periods
 Stop and wait becomes inadequate
 Allow multiple frames to be in transit
 Receiver has buffer W long
 Transmitter can send up to W frames
without ACK
 Each frame is numbered
 ACK includes number of next frame
expected
 Sequence number bounded by size of
field (k)
› Frames are numbered modulo 2k
 Receiver can acknowledge frames without
permitting further transmission (Receive
Not Ready)
 Must send a normal acknowledge to
resume
 If duplex, use piggybacking
› If no data to send, use acknowledgement frame
› If data but no acknowledgement to send, send
last acknowledgement number again, or have
ACK valid flag (TCP)
 Additional bits added by transmitter for
error detection code
 Parity
› Value of parity bit is such that character
has even (even parity) or odd (odd parity)
number of ones
› Even number of bit errors goes undetected
 For a block of k bits transmitter
generates n bit sequence
 Transmit k+n bits which is exactly
divisible by some number
 Receive divides frame by that number
› If no remainder, assume no error
› For math, see Stallings chapter 7
 Detection and correction of errors
 Lost frames
 Damaged frames
 Automatic repeat request
› Error detection
› Positive acknowledgment
› Retransmission after timeout
› Negative acknowledgement and
retransmission
 Stop and wait
 Go back N
 Selective reject (selective
retransmission)
 Source transmits single frame
 Wait for ACK
 If received frame damaged, discard it
› Transmitter has timeout
› If no ACK within timeout, retransmit
 If ACK damaged,transmitter will not
recognize it
› Transmitter will retransmit
› Receive gets two copies of frame
› Use ACK0 and ACK1
 Simple
 Inefficient
 Based on sliding window
 If no error, ACK as usual with next
frame expected
 Use window to control number of
outstanding frames
 If error, reply with rejection
› Discard that frame and all future frames
until error frame received correctly
› Transmitter must go back and retransmit
that frame and all subsequent frames
 Receiver detects error in frame i
 Receiver sends rejection-i
 Transmitter gets rejection-i
 Transmitter retransmits frame i and all
subsequent
 Frame i lost
 Transmitter sends i+1
 Receiver gets frame i+1 out of
sequence
 Receiver send reject i
 Transmitter goes back to frame i and
retransmits
 Frame i lost and no additional frame sent
 Receiver gets nothing and returns neither
acknowledgement nor rejection
 Transmitter times out and sends
acknowledgement frame with P bit set to
1
 Receiver interprets this as command
which it acknowledges with the number of
the next frame it expects (frame i )
 Transmitter then retransmits frame i
 Receiver gets frame i and send
acknowledgement (i+1) which is lost
 Acknowledgements are cumulative, so
next acknowledgement (i+n) may arrive
before transmitter times out on frame i
 If transmitter times out, it sends
acknowledgement with P bit set as before
 This can be repeated a number of times
before a reset procedure is initiated
 As for lost frame (2)
 Also called selective retransmission
 Only rejected frames are retransmitted
 Subsequent frames are accepted by
the receiver and buffered
 Minimizes retransmission
 Receiver must maintain large enough
buffer
 More complex login in transmitter
 HDLC
 ISO 33009, ISO 4335
 Primary station
› Controls operation of link
› Frames issued are called commands
› Maintains separate logical link to each
secondary station
 Secondary station
› Under control of primary station
› Frames issued called responses
 Combined station
› May issue commands and responses
 Unbalanced
› One primary and one or more secondary
stations
› Supports full duplex and half duplex
 Balanced
› Two combined stations
› Supports full duplex and half duplex
 Normal Response Mode (NRM)
› Unbalanced configuration
› Primary initiates transfer to secondary
› Secondary may only transmit data in
response to command from primary
› Used on multi-drop lines
› Host computer as primary
› Terminals as secondary
 Asynchronous Balanced Mode (ABM)
› Balanced configuration
› Either station may initiate transmission
without receiving permission
› Most widely used
› No polling overhead
 Asynchronous Response Mode (ARM)
› Unbalanced configuration
› Secondary may initiate transmission
without permission form primary
› Primary responsible for line
› rarely used

You might also like