40 likes | 165 Vues
This document explains the concepts of congestion onset and abatement in buffer management. It outlines how congestion onset is indicated when a specified threshold is reached, marking the buffer as congested. Congestion abatement occurs when the volume of allocated messages falls back below the abatement threshold. Additionally, it highlights the discard threshold that triggers message discards when oversaturated. Users are informed through indications of congestion and message discard events, ensuring effective buffer management.
E N D
Congestion onset and abatement • Indications of congestion onset and congestion abatement are provided to the user • The buffer has a congestion onset threshold and a congestion abatement threshold
Congestion onset • Congestion onset indication is generated when the congestion onset threshold is reached • From this point the buffer is considered to be in congestion until abatement occurs
Congestion abatement • Congestion abatement is indicated when the number of messages allocated drops back below the abatement threshold • An abatement indication will only be generated when the buffer is in a congested state • No further abatement indications will be generated unless congestion onset is reached • The congestion state has cleared
Congestion discard • The signalling link and board congestion buffers have a discard threshold • When the discard threshold is reached addition messages sent to the buffer are discarded • An indication of message discard is sent to the user