# On the Needs and Requirements Arising from Connected and Automated Driving
## 7 Conclusions  
5G Communication networks must be ready to satisfy the needs of connected and automated driving. Towards this, it is essential to be able to identify and quantify the requirements that the communication networks need to meet in order to enable advanced automotive use cases. The main goal of this paper is to describe future representative V2X use cases, identify their requirements, and then translate them into requirements for the design of 5G networks and beyond. We classify use cases into five big classes of automated driving. By doing so, the analysis of automotive requirements and translation into communication specifications can be done in an ordered and structured manner, while following a clear methodology. The proposed methodology has been applied to five representative use cases that have been studied in the 5 GCAR European-funded project: lane merge, see-through, network-assisted vulnerable road-user protection, high definition local map acquisition, and remote driving for automated parking. These use cases have been described in detail and their automotive requirements have been translated into specific and quantitative requirements for the communication network. This process is fundamental in ensuring that the telecom ecosystem is able to provide the communication performance that the automotive world needs to ensure that connected and automated driving can be made ready for public launch in the near future. For completeness, we have also discussed how the 3 GPP and the 5 GAA are addressing the challenge of defining the use cases and relevant KPIs, quantifying them and establishing the link between automotive and network-related KPIs. All in all, there is a need to harmonize the way that use cases are defined on the automotive sector, so that the telecom sector can provide the communication network that is needed for the vision of automated and connected mobility. This paper aims at contributing to this ongoing challenge, which shall be addressed by the smart mobility ecosystem in a holistic manner. \begin{table}
\begin{tabular}{c c} \hline \hline
**Technology Components** & **Brief Description** \\ \hline Positioning & Enhancement to real-time positioning, trajectory estimation and tracking. \\ \hline Multi-connectivity Cooperation & Improved service availability by jointly using several communication modes or technologies instead of relying only on one mode/technology (i.e., only Uu or only SL) that might not be able to support some use cases. \\ Multi-operator communication & Enhancements are required for dealing with the proper (in terms of delay and reliability) communication of the vehicles belonging to different operators or in cross-border scenarios. \\ Edge Computing Enhancements & Availability of computing capabilities at the edge of the network (i.e., edge computing) opens for several improvements in mobile networks to support vehicular use cases. Enhancements are needed from a core network perspective as well as from an access network point of view. \\ Network orchestration and management & Improved orchestration capabilities able to cope with the unique requirements of vehicular use cases and with improved network management and re-configurability capabilities to cope with the dynamicity in terms of traffic demand in vehicular scenarios. \\ \hline \hline \end{tabular}
\end{table} 
Table 4: Cont. **Author Contributions:** Conceptualization, T.A., A.E.F.B., A.K., T.M. and E.S. ; Investigation, A.E.F.B., M.B., K.C., L.G., A.K., Z.L., T.M., W.S., G.V. and J.A.-Z. ; Methodology, N.B., T.A., E.S. and T.S. ; Project administration, M.F. ; Validation, L.G. ; Visualization, T.S. and J.A.-Z. ; Writing-original draft, K.A., N.B., T.A., A.K., T.M., E.S. and G.V. ; Writing-review & editing, K.A., N.B., A.E.F.B., M.B., K.C., M.F., L.G., Z.L., W.S., E.S., T.S. and J.A.-Z. All authors have read and agreed to the published version of the manuscript.