DSRC Meeting minute
Date: October
the 25th, 2002
Action Items for next meeting
- Marco: will create a
new section on the web-page called "reading material";
- Koushik and Paul:
will provide the paper list to add to the web-site to Marco;
- Koushik: will list
the things that has to be done to use NS for our simulation (i.e. list
the needed modifications and their priorities)
- Paul: will write one
paragraph summary of the BOSH paper;
- Paul: will attend
the monthly DSRC meeting;
- Paul: will summarize
and present to us the DSRC meeting discussion;
- Paul: will create
the test guidelines;
- Paul: will get a SAS
license
- Paul: will provide a
traffic trace with time step of 100 ms;
- Paul: will study the
differences between the first test and future one (what data is
missing in the first test? What can we get out of it? Which technique
can be used or reused?)
- Tony: will go
through the Justin McNeal presentation on DSRC MAC;
- Tony: will work on
the beacon problem (how to allow broadcast and disable beacon at the
same time);
- Tony: will start to
read the 802.11 standard;
- Tony: will start to
create a documentation of the Atheros drivers (function dependencies,
architecture, etc);
- Thomas: will fix the
CTK bugs;
Next
week the testing kit (a couple of laptops equipped with radio, GPS,
antennas and the CTK software) are going to be assembled. Because of it we
are going to be able to do start to gather data and analyze it soon. It
will be a first data set, with rough data. We are planning to be able more
information in the future. This first set should be enough though to so a
first set of analysis. We should be able to create a first model of power
vs. distance for example.
Eight
testing kits are going to be assembled. Seven of them are going to be
distributed among seven different car companies and one of them will be
given to Berkeley.
Now
we do not want to end up with eight test dataset. We should try to have
different group to do different test (e.g. the group A should test the
freeway environment; the group B should test the tunnel environment and so
on).
This
is where the Paul's test guidelines come into the pictures: they are going
to be used by the car companies to produce a unique dataset.
We
should focus our attention of the data set we are going to be able to
gather, to understand the differences between this set and the
"complete set of information" we are going to be gathering in
future.
First test, the questions that has to be answered:
- What is the size of
the data we are going to get?
- How we are going to
clean the data?
- How we are going to analyze
the data?
- How to generate the
models?
Progress report
- Marco: the web site
is up and running;
- Koushik: worked on
NS. A new routine has been added that create a list of the neighbors
of a car given the transmission power.
- Tony: worked on the
drivers;
- Thomas: debugged
CTK;
|