| Literature DB >> 35922653 |
Amar A Mahawish1,2, Hassan J Hassan3.
Abstract
Congestion control plays an essential role on the internet to manage overload, which affects data transmission performance. The random early detection (RED) algorithm belongs to active queue management (AQM), which is used to manage internet traffic. The RED is used to eliminate weakness in default control of the Transport Control Protocol (TCP) drop-tail mechanism. The drawback of RED is parameter tuning, while adaptive RED (ARED) automatically adjusts these parameters. In this study, the suggested algorithm, the Markov decision process RED (MDPRED) uses the Markov decision process (MDP) to suitably adapt values for queue weight in the RED algorithm based on average queue length to enhance the performance of the traditional RED during TCP Slow Startup phase. This study is conducted based on fluctuations among the rate of service, queuing weight, and the mean queue length by using open-source network simulator NS3. The study shows efficient results by fluctuating end-to-end packet throughput and fast response to the inception of congestion in the network. The modified algorithm achieves a low level of drop packets by evaluating the results with other five algorithms, which is done by increasing the algorithm's response when the average queue size becomes close to the maximum queue length threshold.Entities:
Mesh:
Year: 2022 PMID: 35922653 PMCID: PMC9349322 DOI: 10.1038/s41598-022-17528-x
Source DB: PubMed Journal: Sci Rep ISSN: 2045-2322 Impact factor: 4.996
Figure 1NS3 Point-To-Point Dumbbell topology before starting simulation.
Figure 2NS3 Point-To-Point Dumbbell topology after 10 sec of run time.
Figure 3The effect of the avg as a function of and the load rate.
The value of avg based on the queue length state.
| State | Value of |
|---|---|
| 0.002 | |
| 0.004 | |
| 0.006 | |
| 0.008 |
The parameter values of the implemented algorithm.
| Parameter name | Value |
|---|---|
| 0.001 | |
| Packet size | 512 Bytes |
| Data rate | 10 Mbps |
| Bottleneck link capacity | 1 Mbps |
| 5 | |
| 15 |
The sample of implementation reading for number of drop packets.
| No. of Nodes | RED | ARED | GRED | NLRED | RNLGRED | MDPRED |
|---|---|---|---|---|---|---|
| 5 | 162 | 140 | 174 | 161 | 174 | 142 |
| 50 | 1348 | 1320 | 1433 | 1315 | 1575 | 1241 |
| 100 | 5116 | 3731 | 3562 | 4579 | 3094 | 2940 |
| 150 | 11029 | 4905 | 5705 | 10877 | 5361 | 4725 |
| 200 | 18196 | 8387 | 7762 | 18300 | 7251 | 7180 |
Figure 4Drop Packets based on the different data loads.
The sample of implementation reading for number of Forced drop packets.
| No. of Nodes | RED | ARED | GRED | NLRED | RNLGRED | MDPRED |
|---|---|---|---|---|---|---|
| 5 | 160 | 129 | 117 | 160 | 117 | 79 |
| 50 | 1262 | 911 | 496 | 1201 | 496 | 469 |
| 100 | 4899 | 1547 | 848 | 4281 | 848 | 772 |
| 150 | 10679 | 2474 | 1421 | 10348 | 1419 | 1340 |
| 200 | 17748 | 3869 | 1979 | 17571 | 1859 | 1975 |
Figure 5The force packets drop based on the different data loads.
The sample of implementation reading for number of Unforced drop packets.
| No. of Nodes | RED | ARED | GRED | NLRED | RNLGRED | MDPRED |
|---|---|---|---|---|---|---|
| 5 | 2 | 11 | 57 | 1 | 57 | 63 |
| 50 | 86 | 409 | 937 | 114 | 1079 | 772 |
| 100 | 217 | 2184 | 2714 | 298 | 2246 | 2168 |
| 150 | 350 | 2431 | 4284 | 529 | 3942 | 3385 |
| 200 | 448 | 4518 | 5783 | 729 | 5392 | 5205 |
Figure 6The unforced Packets drop based on the different data loads.