Understanding Data Link Control: Flow Control, Error Detection, and Correction, Slides of Network Programming

An in-depth exploration of data link control and protocols, focusing on flow control mechanisms like stop and wait and sliding windows, error detection techniques such as parity and cyclic redundancy check, and error correction methods like automatic repeat request (arq).

Typology: Slides

2011/2012

Uploaded on 07/06/2012

umi
umi 🇮🇳

4.5

(13)

63 documents

1 / 25

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Data Link Control and Protocols
docsity.com
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19

Partial preview of the text

Download Understanding Data Link Control: Flow Control, Error Detection, and Correction and more Slides Network Programming in PDF only on Docsity!

Data Link Control and Protocols

The Data Link Layer

Model of Frame Transmission

Stop and Wait

Source transmits frame Destination receives frame and replies with acknowledgement Source waits for ACK before sending next frame Destination can stop flow by not sending ACK Works well for a few large frames

Sliding Windows Flow Control

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

Sliding Window Diagram

Sliding Window Enhancements

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)

Error Detection

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

Error Control

Detection and correction of errors Lost frames Damaged frames Automatic repeat request Error detection Positive acknowledgment Retransmission after timeout Negative acknowledgement and retransmission

Back to Flow Control

Stop and Wait ;; Sliding Window. What can go wrong: Lost frame Lost Ack Frame in error – damaged Ack in error – damaged Duplicate frame Duplicate Ack

Stop and Wait

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 ACK

Stop and Wait -

Diagram

High Level Data Link Control

HDLC

ISO 33009, ISO 4335

Other DLC Protocols (LLC)

Logical Link Control (LLC) IEEE 802 Different frame format Link control split between medium access layer (MAC) and LLC (on top of MAC) No primary and secondary - all stations are peers Two addresses needed Sender and receiver Error detection at MAC layer 32 bit CRC Destination and source access points (DSAP, SSAP)