I have come across different VANET papers about beacons simulations and they implement different size of beacons in their simulations. What is the best choice for beacon size in bytes, the payload data size in beacon message to be more precise? Since beacon data contains timestamp, current location, current speed, heading, acceleration, steering wheel angle, etc. but is there any standard (something in DSRC/WAVE) that we can follow in VANET simulations?
Usually the periodic beacon messages size is a design parameter, which requires an investigation on the impact of its size and frequency on performance of the protocol. Therefore, it can vary based on the protocol requirements. Some authors take it as 50Bytes, while others go with 200Bytes. But still as i said, its a design parameter.
I would suggest that you decide first what you are willing to send inside each beacon, and based on the content, the payload size will be defined, hence the overall beacon size. Hope this helps...
Regards,
Dear Osama
Thank you for your detailed reply. I agree with you 100% and that is what my point of view is. But as i said before th3 confusion comes from different implementations. And from implementation standpoint, some authors have tried to optimized the size of each data type inside beacons and reduced the size of the data in beacons up to 70%. To be more precise, they have optimized the size of beacons from size perspective. However, dont you think that DSRC already figured out the necessary data for beacons like time, position, velocity, azimooth, and so forth?
Rest is upto us to define the payload for ourselves for instance i want to piggyback more data other than the signatory beacon data.
Regards
I am not really sure of the contents that have been proposed in DSRC standard for periodic beacons, but the fact is not all proposed works utilize all those suggested information. For instance many protocols may not require the usage of speed and azimuth. Some may only utilize positioning coordinates and nodes ID. Other may introduce their own customized list of information that is not included in the first place in DSRC standard.
So eventually things are very flexible on what to include and what not. As i said before, its all about the requirement of your protocol. There is no need to including information that you ll eventually not use. This would be an in-efficient design and waste of bandwidth.
Good Luck...
Yeah Osama, thank you so much for your reply. I agree with what you just said, however I believe that the same class of applications, for instance traffic information dissemination application will use all those parameters suggested in the draft of DSRC. Another thing is that, beacons are mainly used for cooperative awareness, nonetheless they can be used for some other applications as well.
salam alikoum, i want to simulate VANET network in order to trace a norrmal network before the addition of a malicious node, i would like to do this with NS2.35, have you any ideas how it could be the simulation, I have successfuly installed NS2 on UBUNTU 12.04 LTS. Thnaks in advance
I have seen that severa authors have used beacon sizes between 283 bytes and 791 bytes that were proposed by:
M.Raya and J.P. Hubaux, “The security of vehicular ad hoc networks,”
In Proc. the 3rd ACM Workshop on Security of Ad Hoc and Sensor
Networks (SASN), Alexandria, VA, USA, pp. 11-21, November 2005
- Badges
- Science topic
- Similar topics
- Computer Communications (Networks)
- Simulators