Data link control.pdf

11.1
Chapter 11
Data Link Control

• two main functions
• data link control: deals with the design and procedures for
communication between two adjacent nodes: node-to-node
communication
• media access control : how to share the link
• Data link control functions include framing, flow and error control
• Two types of channel : Noiseless and Noisy channel
11.2
Modified By: Kruti Dhyani

11.3
11-1 FRAMING
The data link layer needs to pack bits into frames, so
that each frame is distinguishable from another. Our
postal system practices a type of framing. The simple
act of inserting a letter into an envelope separates one
piece of information from another; the envelope serves
as the delimiter.
Fixed-Size Framing
Variable-Size Framing
Topics discussed in this section:

• Framing in the data link layer separates a message from one source to a
destination, or from other messages to other destinations
• The destination address defines where the packet is to go;
• the sender address helps the recipient acknowledge the receipt
• Can we send whole message in one pack?
• YES:
• What is the Disadvantange?
• frame can be very large, making flow and error control very inefficient.
When a message is carried in one very large frame, even a single-bit
error would require the retransmission of the whole message.
• Solution: a message is divided into smaller frames, a single-bit error
affects only that small frame.
11.4

• Fixed-Size Framing
• In fixed-size framing, there is no need for defining the boundaries of the
frames; the size itself can be used as a delimiter.
• An example of this type of framing is the ATM wide-area network, which
uses frames of fixed size called cells.
• Variable-Size Framing
• In variable-size framing, we need a way to define the end of the frame
and the beginning of the next.
• Two approaches were used for this purpose:
• a character-oriented approach
• a bit-oriented approach.
11.5

• CHARACTER ORIENTED PROTOCOL
• data to be carried are 8-bit characters from a coding system such as
ASCII
• Example
11.6

• CHARACTER ORIENTED PROTOCOL
• The header, which normally carries the source and destination addresses
and other control information, and the trailer, which carries error
detection or error correction redundant bits, are also multiples of 8 bits.
• To separate one frame from the next, an 8-bit (I-byte) flag is added at
the beginning and the end of a frame.
• The flag, composed of protocol-dependent special characters, signals the
start or end of a frame.
• popular when only text was exchanged by the data link layers
11.7

11.8
Figure 11.1 A frame in a character-oriented protocol

• In byte stuffing (or character stuffing), a special byte is added to the data
section of the frame when there is a character with the same pattern as
the flag.
• The data section is stuffed with an extra byte. This byte is usually called
the escape character (ESC), which has a predefined bit pattern.
• Whenever the receiver encounters the ESC character, it removes it from
the data section and treats the next character as data, not a delimiting
flag.
11.9

11.10
Figure 11.2 Byte stuffing and unstuffing

• Problem: What happens if the text contains one or more escape
characters followed by a flag?
• Solution: The receiver removes the escape character, but keeps the flag,
which is incorrectly interpreted as the end of the frame. To solve this
problem, the escape characters that are part of the text must also be
marked by another escape character. In other words, if the escape
character is part of the text, an extra one is
• added to show that the second one is part of the text.
11.11

11.12
Byte stuffing is the process of adding 1
extra byte whenever there is a flag or
escape character in the text.
Note

• BIT ORIENTED PROTOCOL
• The data section of a frame is a sequence of bits to be interpreted by the
upper layer as text, graphic, audio, video, and so on. However, in
addition to headers (and possible trailers)
• Still need a delimiter to separate one frame from the other. Most
protocols use a special 8-bit pattern flag 01111110 as the delimiter to
define the beginning and the end of the frame
11.13
Figure 11.3 A frame in a bit-oriented protocol

• BIT ORIENTED PROTOCOL
• Problem: What happens if the same pattern of the bit sequence is part
of the data bit?
• Solution: If the flag pattern appears in the data, we need to somehow
inform the receiver that this is not the end of the frame. We do this by
stuffing 1 single bit (instead of 1 byte) to prevent the pattern from
looking like a flag. The strategy is called bit stuffing.
11.14

11.15
Bit stuffing is the process of adding one
extra 0 whenever five consecutive 1s
follow a 0 in the data, so that the
receiver does not mistake
the pattern 0111110 for a flag.
Note

11.16
Figure 11.4 Bit stuffing and unstuffing

11.17
11-2 FLOW AND ERROR CONTROL
The most important responsibilities of the data link layer are flow control and
error control. Collectively, these functions are known as data link control.
Flow Control
Error Control

• FLOW CONTROL
11.18

11.19
Flow control refers to a set of procedures
used to restrict the amount of data
that the sender can send before
waiting for acknowledgment.
Note

11.20
Error control in the data link layer is
based on automatic repeat request,
which is the retransmission of data.
Note

• Connectionless and Connection Oriented
• Connectionless Protocol
• In a connectionless protocol, frames are sent from one node to the next
without any relationship between the frames; each frame is
independent.
• Note that the term connectionless here does not mean that there is no
physical connection (transmission medium) between the nodes; it
means that there is no connection between frames.
• The frames are not numbered and there is no sense of ordering. Most of
the data-link protocols for LANs are connectionless protocols.
11.21

• Connectionless and Connection Oriented
• Connection-Oriented Protocol
• In a connection-oriented protocol,
• a logical connection should first be established between the two nodes (setup phase).
• After all frames that are somehow related to each other are transmitted (transfer
phase),
• the logical connection is terminated (teardown phase).
• In this type of communication, the frames are numbered and sent in
order.
• If they are not received in order, the receiver needs to wait until all
frames belonging to the same set are received and then deliver them in
order to the network layer.
• Connection oriented protocols are rare in wired LANs, but we can see
them in some point-to-point protocols, some wireless LANs, and some
WANs.
11.22

11.23
11-3 PROTOCOLS
• Now let us see how the data link layer can combine
framing, flow control, and error control to achieve
the delivery of data from one node to another. The
protocols are normally implemented in software by
using one of the common programming languages.

11.24
Figure 11.5 Taxonomy of protocols discussed in this chapter

• All the protocols we discuss are unidirectional in the sense that the data
frames travel from one node, called the sender, to another node, called
the receiver.
• Although special frames, called acknowledgment (ACK) and negative
acknowledgment (NAK) can flow in the opposite direction for flow and
error control purposes, data flow in only one direction.
11.25

11.26
11-4 NOISELESS CHANNELS
Let us first assume we have an ideal channel in which
no frames are lost, duplicated, or corrupted. We
introduce two protocols for this type of channel.
Simplest Protocol
Stop-and-Wait Protocol

• Simplest Protocol
• It is call the Simplest Protocol for lack of any other name, is one that has
no flow or error control.
• it is a unidirectional protocol in which data frames are traveling in only
one direction-from the sender to receiver.
• We assume that the receiver can immediately handle any frame it
receives with a processing time that is small enough to be negligible.
• The data link layer of the receiver immediately removes the header from
the frame and hands the data packet to its network layer.
• In other words, the receiver can never be overwhelmed with incoming
frames.
11.27

11.28
Figure 11.6 The design of the simplest protocol with no flow or error control

11.29
Algorithm 11.1 Sender-site algorithm for the simplest protocol

11.30
Algorithm 11.2 Receiver-site algorithm for the simplest protocol

11.31
Below figure shows an example of communication using this protocol. It is very
simple. The sender sends a sequence of frames without even thinking about the
receiver. To send three frames, three events occur at the sender site and three events
at the receiver site. Note that the data frames are shown by tilted boxes; the height
of the box defines the transmission time difference between
the first bit and the last bit in the frame.
Example 11.1

11.32
Figure 11.8 Design of Stop-and-Wait Protocol

11.33

11.34
Algorithm 11.3 Sender-site algorithm for Stop-and-Wait Protocol

11.35
Algorithm 11.4 Receiver-site algorithm for Stop-and-Wait Protocol

11.36
Figure 11.9 shows an example of communication using this protocol. It is still very
simple. The sender sends one frame and waits for feedback from the receiver.
When the ACK arrives, the sender sends the next frame. Note that sending two
frames in the protocol involves the sender in four events and the receiver in two
events.
Example 11.2

11.37
11-5 NOISY CHANNELS
Although the Stop-and-Wait Protocol gives us an idea of
how to add flow control to its predecessor, noiseless
channels are nonexistent. We discuss three protocols in
this section that use error control.
Stop-and-Wait Automatic Repeat Request
Go-Back-N Automatic Repeat Request
Selective Repeat Automatic Repeat Request

Stop and Wait ARQ Protocol
• Stop-and-Wait Automatic Repeat Request.
• Lost frames are more difficult to handle than corrupted ones.
• The received frame could be the correct one, or a duplicate, or a frame
out of order.
• The solution is to number the frames. When the receiver receives a data
frame that is out of order, this means that frames were either lost or
duplicated.
• So, The completed and lost frames need to be resent in this protocol.
• If the receiver does not respond when there is an error, how can the
sender know which frame to resend?
• Solution: The sender keeps a copy of the sent frame. At the same time, it
starts a timer. If the timer expires and there is no ACK for the sent frame,
the frame is resent, the copy is held, and the timer is restarted.
11.38

11.39
Error correction in Stop-and-Wait ARQ is
done by keeping a copy of the sent
frame and retransmitting of the frame
when the timer expires.
Note

• Stop and Wait ARQ Protocol
• Since an ACK frame can also be corrupted and lost, it too needs
redundancy bits and a sequence number.
• The ACK frame for this protocol has a sequence number field.
• The sender simply discards a corrupted ACK frame or ignores an out-of-
order one.
• Sequence Numbers
• Every frame has allocated a unique sequence number to identify that
frame.
• A field is added to the data frame to hold the sequence number of that
frame
• the range of the sequence numbers should be smallest range that
provides unambiguous communication.
• The sequence numbers of course can wrap around.
• For example, if we decide that the field is m bits long, the sequence
numbers start from 0, go to 2m - 1, and then are repeated.
11.40

• Stop and Wait ARQ Protocol
• 3 Scenarios that could be happened with Stop and wait ARQ
I. Frame arrives same and receive by receiver
II. ACK frame Lost
III. Frame is corrupted and never arrives at receiver side:
• Acknowledgment Number
• The acknowledgment numbers always announce the sequence number
of the next frame expected by the receiver.
• For example, if frame 0 has arrived safe and sound, the receiver sends an
ACK frame with acknowledgment 1. If frame 1 has arrived safe and
sound, the receiver sends an ACK frame with acknowledgment 0.
11.41

11.42
Figure 11.10 Design of the Stop-and-Wait ARQ Protocol

11.43
In Stop-and-Wait ARQ, we use sequence
numbers to number the frames.
The sequence numbers are based on
modulo-2 arithmetic.
Note

11.44
In Stop-and-Wait ARQ, the
acknowledgment number always
announces in modulo-2 arithmetic the
sequence number of the next frame
expected.
Note

11.48
Figure shows an example of Stop-and-Wait ARQ. Frame 0 is sent and
acknowledged. Frame 1 is lost and resent after the time-out. The resent frame 1 is
acknowledged and the timer stops. Frame 0 is sent and acknowledged, but the
acknowledgment is lost. The sender has no idea if the frame or the
acknowledgment is lost, so after the time-out, it resends frame 0, which is
acknowledged.
Example 11.3

11.49
Assume that, in a Stop-and-Wait ARQ system, the bandwidth of the line is 1 Mbps,
and 1 bit takes 20 ms to make a round trip. What is the bandwidth-delay product? If
the system data frames are 1000 bits in length, what is the utilization percentage of
the link?
Solution
The bandwidth-delay product is
Example 11.4
The system can send 20,000 bits during the time it takes for the data to go from the
sender to the receiver and then back again. However, the system sends only 1000
bits. We can say that the link utilization is only 1000/20,000, or 5 percent. For this
reason, for a link with a high bandwidth or long delay, the use of Stop-and-Wait
ARQ wastes the capacity of the link.

11.50
What is the utilization percentage of the link in Example 11.4 if we have a
protocol that can send up to 15 frames before stopping and worrying about the
acknowledgments?
Solution
The bandwidth-delay product is still 20,000 bits. The system can send up to 15
frames or 15,000 bits during a round trip. This means the utilization is
15,000/20,000, or 75 percent. Of course, if there are damaged frames, the
utilization percentage is much less because frames have to be resent.
Example 11.5

• Pipelining
• a task is often begun before the previous task has ended. This is known
as pipelining.
• There is no pipelining in Stop-and-Wait ARQ because we need to wait for
a frame to reach the destination and be acknowledged before the next
frame can be sent.
• Pipelining improves the efficiency of the transmission if the number of
bits in transition is large with respect to the bandwidth-delay product
11.51

11.52
11-6 HDLC
High-level Data Link Control (HDLC) is a bit-oriented
protocol for communication over point-to-point and
multipoint links. It implements the ARQ mechanisms
we discussed in this chapter.
Configurations and Transfer Modes
Frames
Control Field

11.53
Figure 11.25 Normal response mode

11.54
Figure 11.26 Asynchronous balanced mode

11.55
Figure 11.27 HDLC frames

11.56
Figure 11.28 Control field format for the different frame types

11.57
Table 11.1 U-frame control command and response

11.58
Figure 11.29 shows how U-frames can be used for
connection establishment and connection release. Node A
asks for a connection with a set asynchronous balanced
mode (SABM) frame; node B gives a positive response
with an unnumbered acknowledgment (UA) frame. After
these two exchanges, data can be transferred between the
two nodes (not shown in the figure). After data transfer,
node A sends a DISC (disconnect) frame to release the
connection; it is confirmed by node B responding with a
UA (unnumbered acknowledgment).
Example 11.9

11.59
Figure 11.29 Example of connection and disconnection

11.60
Figure shows an exchange using piggybacking.
Node A begins the exchange of information with
an I-frame numbered 0 followed by another I-
frame numbered 1. Node B piggybacks its
acknowledgment of both frames onto an I-frame
of its own. Node B’s first I-frame is also
numbered 0 [N(S) field] and contains a 2 in its
N(R) field, acknowledging the receipt of A’s
frames 1 and 0 and indicating that it expects
frame 2 to arrive next. Node B transmits its
second and third I-frames (numbered 1 and 2)
before accepting further frames from node A.
Example 11.10

11.61
Example 11.10
Its N(R) information, therefore, has not
changed: B frames 1 and 2 indicate that node B
is still expecting A’s frame 2 to arrive next.
Node A has sent all its data. Therefore, it
cannot piggyback an acknowledgment onto an
I-frame and sends an S-frame instead. The RR
code indicates that A is still ready to receive.
The number 3 in the N(R) field tells B that
frames 0, 1, and 2 have all been accepted and
that A is now expecting frame number 3.

11.62
Figure shows an exchange in which a frame
is lost. Node B sends three data frames (0, 1,
and 2), but frame 1 is lost. When node A
receives frame 2, it discards it and sends a
REJ frame for frame 1. Note that the
protocol being used is Go-Back-N with the
special use of an REJ frame as a NAK
frame. The NAK frame does two things
here: It confirms the receipt of frame 0 and
declares that frame 1 and any following
frames must be resent. Node B, after
receiving the REJ frame, resends frames 1
and 2. Node A acknowledges the receipt by
sending an RR frame (ACK) with
acknowledgment number 3.
Example 11.11

11.63
11-7 POINT-TO-POINT PROTOCOL
Although HDLC is a general protocol that can be used
for both point-to-point and multipoint configurations,
one of the most common protocols for point-to-point
access is the Point-to-Point Protocol (PPP). PPP is a
byte-oriented protocol.
Framing

11.64
Figure 11.32 PPP frame format

11.65
PPP is a byte-oriented protocol using
byte stuffing with the escape byte
01111101.
Note

11.67
Figure 11.34 Multiplexing in PPP

11.70
Table 11.3 Common options

11.71
Figure 11.36 PAP packets encapsulated in a PPP frame

11.72
Figure 11.37 CHAP packets encapsulated in a PPP frame

Data link control.pdf

More Related Content

Similar to Data link control.pdf (20)

Recently uploaded (20)

Data link control.pdf