Enhancing 5G Vehicular Edge Computing Efficiency with the Hungarian Algorithm for Optimal Task Offloading

Round 1

Reviewer 1 Report

Comments and Suggestions for Authors

The paper is mainly about developing novel methodology to distribute and optimize computation tasks in modern vehicular edge computing scenarios by using the Hungarian algorithm for task offloading. As such, it is a relevant study item in the context of 5G vehicular communications.

Main comments

Structure: The overall structure of the manuscript is quite balanced with a feasible amount of sections, subsections and references. The abstract is brief enough but yet manages to highlight the scope and key results of the paper. The introduction leads well to the study item with cited prior concepts and developments in the area and closes with the statements of own contributions. Related work and literature is further covered in Section 2 and then actual technical sections follow with system model, mathematical problem formulation and numerical results.   

Clarity: Although the previously described structure of the manuscript is good, the clarity and general outlook could be improved in various ways. First, mathematical problems and equations should be presented as integral parts of the text around them. Pay attention to leading words, punctuation, spacing, consistent font setting (capital/small, italic/nonitalic), indentation, and other technical writing principles. See Minor comments below for further details. Second, readability of figures could be improved as the appear to be somewhat blurry (small details especially). Third, there are some other types of outlook related issues listed in Minor comments that are also important to be addressed.  

Scientific soundness: The paper does not introduce any groundbreaking new ideas but is more like applied type of contribution to advance existing known technologies and algorithms with own variations for a specific application. Methods are well-established mathematical derivations and simulations. Key variables, simulation parameters, flow charts and algorithms are defined in the manuscript. Bar charts (Figs. 3-6) are quite hard to read in the sense to get an overall picture of the methods and rank their order of preference. Would there be a better graphical or other way to show these results?      

Minor comments

The next comments are more detailed comments/remarks/examples (many of which editorial/general outlook in nature) that should be taken into consideration in the revision.

-          Page 2, Introduction, line number 86: … concludes in Section -> … concludes in Section 6.

-          Page 4, Section 3.2, line number 162: Use consistent numbering format (Section IV -> Section 4).

-          Page 5, Section 3.3, line numbers 171-173: Embed equations fully to surrounding phrases with proper punctuation, indentation and other formal professional technical writing criteria. This applies to the rest of the manuscript as well.

-          Page 7, Section 5, line numbers 291-295: … Km … -> … km … Also, be consistent in leaving one character space between numbers and units.

-          Pages 12-13, Figures 5 and 6: Add y-axis label and respective measure unit.

Author Response

Please refer to the attached "Response_to_Reviewer_#1"

Author Response File: Author Response.pdf

Reviewer 2 Report

Comments and Suggestions for Authors

Dear authors,

the article is interesting, but requires some additional information

Paragraph 5 of the article requires much more explanation:

How you used the data from Table 1 in the simulation program?

How did you use the HATO algorithm in the ns3 program?

In accordance with Figure 2, I recommend you to present the HATO algorithm.

How did you use the input data (see lines 291 -- 297) in the simulation program?

I recommend that you present an algorithm in which the reader can easily see what its input and output data.

I recommend that you insert figures 5 and 6 at the end of paragraph 5 of the article.

 

Author Response

Please refer to the attached "Response_to_Reviewer_#2"

Author Response File: Author Response.pdf