Can Edge Computing fulfill the requirements of automated vehicular services using 5G network ?
Communication and computation services supporting Connected and Automated Vehicles (CAVs) are characterized by stringent requirements, in terms of response time and reliability. Fulfilling these requirements is crucial for ensuring road safety and traffic optimization. The conceptually simple soluti...
Saved in:
Main Authors | , , , , |
---|---|
Format | Journal Article |
Language | English |
Published |
08.04.2024
|
Subjects | |
Online Access | Get full text |
Cover
Loading…
Summary: | Communication and computation services supporting Connected and Automated
Vehicles (CAVs) are characterized by stringent requirements, in terms of
response time and reliability. Fulfilling these requirements is crucial for
ensuring road safety and traffic optimization. The conceptually simple solution
of hosting these services in the vehicles increases their cost (mainly due to
the installation and maintenance of computation infrastructure) and may drain
their battery excessively. Such disadvantages can be tackled via Multi-Access
Edge Computing (MEC), consisting in deploying computation capability in network
nodes deployed close to the devices (vehicles in this case), such as to satisfy
the stringent CAV requirements. However, it is not yet clear under which
conditions MEC can support CAV requirements and for which services. To shed
light on this question, we conduct a simulation campaign using well-known
open-source simulation tools, namely OMNeT++, Simu5G, Veins, INET, and SUMO. We
are thus able to provide a reality check on MEC for CAV, pinpointing what are
the computation capacities that must be installed in the MEC, to support the
different services, and the amount of vehicles that a single MEC node can
support. We find that such parameters must vary a lot, depending on the service
considered. This study can serve as a preliminary basis for network operators
to plan future deployment of MEC to support CAV. |
---|---|
DOI: | 10.48550/arxiv.2404.05296 |