0% found this document useful (0 votes)
6 views21 pages

25 Control Congestion Avoidance Mechanisms 04-11-2024

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1/ 21

Transport Layer

Host and Media Layer

2
Congestion Control
• Technique or mechanism to
• Prevent before it happens
• Remove after it has happened

TYPES:
• Open loop congestion control(prevention)
• Closed loop congestion control(Removal)
• Retransmission Policy
Retransmission is sometimes unavoidable. If the sender feels that a
sent packet is lost or corrupted, the packet needs to be retransmitted.
Retransmission in general may increase congestion in the network.
However, a good retransmission policy can prevent congestion. The
retransmission policy and the retransmission timers must be designed
to optimize efficiency and at the same time prevent congestion.
• Window Policy
The type of window at the sender may also affect congestion. The
Selective Repeat window is better than the Go-Back-N window for
congestion control
• Acknowledgment Policy
The acknowledgment policy imposed by the receiver may also affect
congestion. If the receiver does not acknowledge every packet it
receives, it may slow down the sender and help prevent congestion.
• Discarding Policy
A good discarding policy by the routers may prevent congestion and at
the same time may not harm the integrity of the transmission. For
example, in audio transmission, if the policy is to discard less sensitive
packets when congestion is likely to happen, the quality of sound is still
preserved and congestion is prevented or alleviated.
• Admission Policy
An admission policy, which is a quality-of-service mechanism, can also
prevent congestion in virtual-circuit networks. Switches in a flow first
check the resource requirement of a flow before admitting it to the
network. A router can deny establishing a virtual circuit connection if
there is congestion in the network or if there is a possibility of future
congestion.
Closed loop control
• A choke packet is a packet sent by a node to the source to inform it of
congestion. Note the difference between the backpressure and choke
packet methods. In backpressure, the warning is from one node to its
upstream node, although the warning may eventually reach the source
station. In the choke packet method, the warning is from the router,
which has encountered congestion, to the source station directly
• Implicit Signaling
In implicit signaling, there is no communication between the congested
node or nodes and the source. The source guesses that there is a
congestion somewhere in the network from other symptoms. For
example, when a source sends several packets and there is no
acknowledgment for a while, one assumption is that the network is
congested. The delay in receiving an acknowledgment is interpreted as
congestion in the network; the source should slow down
Ex: TCP
• Explicit Signaling
The node that experiences congestion can explicitly send a signal to the
source or destination. The explicit signaling method, however, is
different from the choke packet method. In the choke packet method, a
separate packet is used for this purpose; in the explicit signaling
method, the signal is included in the packets that carry data.
Ex: Frame delay congestion control
Transmission control Protocol-TCP
User Datagram Protocol-UDP

You might also like