
0
1
1 1
2 7
6 0
7 6
9 2
1 2 4
1 1 3
1 1 1
9 6
5 5
3 0
1 8
1 0
4
2
1
5
3
0 0 0 0
2
0
- 1 0 0 1 0 2 0 3 0 4 0
0
5 0
1 0 0
1 5 0
C o u n t
P
m e a s u r e d
- P
p r e d
[ d B m ]
Figure 6: Comparison of real world measurements vs. the
predictions. The mean difference is 0.99 dBm with a stan-
dard deviation of 7.35 dbm. Values on the right result from
a too pessimistic modeling.
levels were predicted (see Fig. 5 for an example).
These were compared against the RSSI measured
during the test drive. In case there was more than
one measurement per hexagon, the 80% percentile of
all measurements was used. This was done to ex-
clude certain cases of NLOS, e.g., if communication
was blocked by another vehicle. For evaluation, 841
predicted values were compared with measurements,
where the measured values were retrieved from all
intersections included in the measurement campaign.
The result of this comparison can be seen in Fig. 6.
The difference between measured and predicted val-
ues usually lies between −15dBm − 20 dBm, with
some outliers greater than 25 dBm. These outliers
could be traced to an erroneously assigned NLOS
connection. This is due to the inaccuracy in GNSS,
i.e., the reported position resulted in NLOS connec-
tion, but the real position had LOS.
Generally, modeling differences larger than 0 dBm
do not cause problems, as long as all registration
points are still covered (for the case of TSP), as
this means that the actual connection was even better
than predicted. Values smaller than 0 dBm are more
concerning. Detailed investigations have shown that
these values appear mainly near the submitting sta-
tion, which means that some propagation properties
of the radios are not fully considered by the path-loss
model. As reception levels near the radio are typically
very high, this does not cause an issue for the overall
tool.
Although previous research (Eltahir, 2007) has
shown that the choice of the radio propagation model
has a significant impact on the results of the simu-
lations, our results actually validate the choice of a
simple path-loss model with a penalty term for NLOS
connections, at least if used for V2X infrastructure
planning. Compared to the ray-launching method
proposed by Granda et al. (Granda et al., 2017),
a similar mean error was achieved (0.99 dBm here
vs. 1.75 dBm). In contrast, their method achieves
a much lower standard deviation (2.54 dBm) ver-
sus 7.35 dBm. Although the results obtained us-
ing the ray-launching method are more accurate, ray-
launching requires ray-tracing software and hardware,
which are rather expensive to obtain and to oper-
ate, whereas the proposed algorithm runs on an of-
fice notebook. Given that V2X planning is mainly
contracted by public communities, the offset in costs
could justify the use of a less accurate model, espe-
cially if the results are still good enough for the de-
sired task.
4 CONCLUSIONS & OUTLOOK
Taking real-world measurements for 11 of the 38 sig-
nalized intersections required two people and a day of
work. Measurement of all intersections would have
taken nearly a week. In comparison, generating the
predictions took less than twenty minutes on an of-
fice notebook, most of this computation time. In gen-
eral, the proposed approach leads to a significant de-
crease in planning RSU placement. Furthermore, it
was shown that the model was able to sufficiently pre-
dict real-world radio propagation. Although the com-
parison was performed using IEEE 802.11p, it can be
equally used for C-V2X as the physical propagation
and radio frequencies are the same for both technolo-
gies.
However, there are some limitations of the cur-
rent approach. It works best when the local path-
loss exponent can be accurately estimated, which still
relies on real-world measurements. This is neces-
sary, as this exponent can vary wildly given the local
circumstances, for example, (Goldsmith, 2005) cites
measured path-loss exponents between 2.7 − 6.5. On
the other hand, already existing RSU could help with
this part by comparing reception levels with the posi-
tion reported in the CAM by connected vehicles al-
ready on the road today. Furthermore, currently a
constant difference between the height of RSU and
OBU are assumed. Although the model could also
handle varying height differences, this would com-
plicate the computations, e.g., buildings would need
to be checked for NLOS connections, but also the
ground, especially in hilly regions.
The current approach relies on OSM data. Since
this is an open-source effort, the quality of the data
differs. For some regions in Germany, for example,
Saxony, there exists a digital height model with 25 cm
A Tool for V2X Infrastructure Placement
643