Efficient Mobile Vehicle Data Sharing Scheme Based on Consortium Blockchain
Round 1
Reviewer 1 Report
he paper is well structured, but needs to be improved, the theme is current and quite ambitious. the topic dealt with systems that use the various sensors to perceive the environment, analyze and calculate information applied to intelligent algorithms. It can help detect possible hazards and effectively increase driving safety e comfort. I recommend to fix the introductory part, improve it considerably and fix the conclusions by inserting a discussion section. revise the English language. above all to arrange the format of the paper. all bibliographic references are missing ... integrate the bibliography I suggest the following references:
Decision tree method to analyze the performance of lane support systems
Pappalardo, G., Cafiso, S., Di Graziano, A., Severino, A.
, ,
Real-Time Data Filling and Automatic Retrieval Algorithm of Road Traffic Based on Deep-Learning Method
J Zhu, W Xu - Symmetry, 2021
Author Response
Please see the attachment
Author Response File: 
Author Response.docx
Reviewer 2 Report
The paper addresses a blockchain-based system for sharing data among moving self-driven vehicles and other vehicles, trafic authorities, etc.
The subject and motivation for the work should have been better introduced, in the Introduction section.
The authors should have surveyed or referenced existing approaches for sharing moving vehicles data, before presenting their proposal, in order to allow discussion and comparison before final conclusion.
Sections 2, 3 and 4 lack readable descriptions and examples, that would help in understanding the presented formulas and equations.
Section 5 provides a theoretical analysis, based of a simulation study using MATLAB.
The previous statements enable concluding that this is an early result of a probably on-going work. It lacks implementation and comparison to other approaches to solutions to the same problem.
Author Response
Please see the attachment
Author Response File: Author Response.docx
Reviewer 3 Report
The text should be proofread for minor issues. For example, line 38 says "introduction of Trusted Authority (TA) using pseudonyms to avoid user privacy". I guess the right phrase would be "to enforce user privacy".
There are a couple of places in the text where a phrase "alliance blockchain" is used probably instead of "consortium blockchain".
Line 142: it is stated that TA issues private keys (among other data) to other entities in the system. This should not be the case, please check that statement.
Lines 184-189: what can be the cause of data duplication? This should be elaborated to make the discussion clearer.
Lines 208-209: Is there a possibility of a race condition since generation of a data sharing record and fusing records to obtain a new block is taking place concurrently.
Line 362: "Otherwose" is a typo.
Section 5.1: The simulation was restricted to an area of 600m x 600m. This is a rather small area. Could you elaborate on how to scale the simulation, along with the system itself, to the level of a city? What would be the limitations of the system, and the simulation setup? This discussion is important as it will greatly improve the applicability of the presented solution.
Lines 484-486: check the grammar for the sentence that starts with "In this paper, 10 peer points..."
Author Response
Please see the attachment，thanks.
Author Response File: Author Response.docx
Round 2
Reviewer 2 Report
The paper’s structure has been improved since the previous version. The paper’s subject and motivation for the work are also better introduced. Some English errors persist… see for example sentence “the existing data sharing and transmission schemes of mobile vehicles in IoV still exist some problems“, where it should most probably be “the existing data sharing and transmission schemes of mobile vehicles in IoV still have some problems”.
Sections 2 to 5 are better explained. Section 3 header is badly formatted.
Conclusions are short.
Author Response
Please see the attachment
Author Response File: Author Response.docx
