Please write detailed REVIEW on Following Topic. It required only one page.

Energy Efficient MAC Protocol with Fair Scheduling Technique in Multi-hop MANETs

In this paper, the author proposed a fair scheduling technique for MAC protocol with inelastic packets flow in Mobile Ad-hoc Networks (MANETs). I think this selected topic will be helpful in today’s network prevailing world as MANETs are widely used.

In the introduction part, the author gave a good overview of MANETs and its scheduling. This makes it easy for readers to understand the basic concepts. But in problem identification, he could have explained about the problem that he identified in his previous work rather than explaining what is done in his previous work. It could have been more effective if he provided a solution to the problem which he identified. For more information, he proposed an energy efficient MAC protocol in MANET in his earlier work, which helps in the error-free data flow by RTS and CTS frame. For scheduling in MANETs, time slots are used in Time Division Multiple Access (TDMA) technique to transmit and receive data. However, this technique is applicable only when the network size is small, as the nodes with fixed length configurations fail in vast networks. So, a comparison could have been done with other efficient and advanced techniques as well other than TDMA for better understanding.

In related work section, the author has given useful information regarding other similar works, but he could have explained the unknown terms, such as dual decomposition, stochastic process analysis, max-min fairness schemes because not defining such terms initially creates ambiguity in the reader. At least he could have included the meaning in appendix or footnotes for clear understanding to the reader. He could have also mentioned elsewhere, the uniqueness of his paper when compared to other similar works.

In this fair scheduling technique, the incoming data is distinguished into two types i.e., elastic, and inelastic data flows. The inelastic data flow is given more priority than the elastic data flow. A function called utility function is estimated after the packet is dispatched, based on the channel state information, channel utilization, and packet delay value. When it reaches the scheduler, it checks the nature of the data flow and regulates the priority queue depending on delay value (if inelastic flow) or assign a time (if elastic flow). This concept is explained very well by the author with the help of equations, figures, tables, and algorithms. And the algorithms help the reader to easily understand the logic because of its step-by-step procedure. But he explained this main concept over and over and that causes disinterest while reading the paper.

Simulation results are given based on simulation model and parameters, and performance metrics. The author compares the Energy Efficient MAC protocol with Fair-Scheduling technique (EEMACFS) with Optimal Scheduling for Fair Resource Allocation (OSFRA) technique depending on rate vs received bandwidth, received delay, delivery ratio, packet drop, residual energy, and throughput. From the graphs, we can conclude that the EEMACFS technique is higher than the OSFRA technique in received bandwidth, delivery ratio, residual energy and throughput by 87%, 83%, 16%, and 87%. And EEMACFS technique is lesser than the OSFRA technique in received delay and packet drop by 49% and 40%. From the above data, the author claims that EEMACFS technique is better than OSFRA technique. But the chosen parameter values are all assumptions. Hence, when we use the system in real time environment it can be out-of-the-box. This weakens the author’s claim.

In the beginning, the author discussed basic concepts clearly. There aren’t any grammatical corrections and spelling mistakes. He used simple language to understand better. And a lot of references are given to gain proper knowledge of the topic. This paper can be further improved by giving more explanation for the graphs in performance metrics and by discussing OSFRA technique and its implementation briefly. The author did not discuss the technical issues that might arise during scheduler implementation, and he didn’t even suggest any future work.