<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.3 20070202//EN" "journalpublishing.dtd">
<article article-type="research-article" dtd-version="2.3" xml:lang="EN" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">Front. Future Transp.</journal-id>
<journal-title>Frontiers in Future Transportation</journal-title>
<abbrev-journal-title abbrev-type="pubmed">Front. Future Transp.</abbrev-journal-title>
<issn pub-type="epub">2673-5210</issn>
<publisher>
<publisher-name>Frontiers Media S.A.</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">742731</article-id>
<article-id pub-id-type="doi">10.3389/ffutr.2022.742731</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Future Transportation</subject>
<subj-group>
<subject>Original Research</subject>
</subj-group>
</subj-group>
</article-categories>
<title-group>
<article-title>Practical Challenges in Hybrid Communication Ecosystems Based on ITS-G5 and LTE for CACC and GLOSA</article-title>
<alt-title alt-title-type="left-running-head">Cimoli et&#x20;al.</alt-title>
<alt-title alt-title-type="right-running-head">Hybrid-Communications for CACC and GLOSA</alt-title>
</title-group>
<contrib-group>
<contrib contrib-type="author" corresp="yes">
<name>
<surname>Cimoli</surname>
<given-names>Bruno</given-names>
</name>
<xref ref-type="aff" rid="aff1">
<sup>1</sup>
</xref>
<xref ref-type="corresp" rid="c001">&#x2a;</xref>
<uri xlink:href="https://loop.frontiersin.org/people/991045/overview"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Xing</surname>
<given-names>Haitao</given-names>
</name>
<xref ref-type="aff" rid="aff2">
<sup>2</sup>
</xref>
<uri xlink:href="https://loop.frontiersin.org/people/1622329/overview"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Ho</surname>
<given-names>Victor</given-names>
</name>
<xref ref-type="aff" rid="aff3">
<sup>3</sup>
</xref>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Passchier</surname>
<given-names>Igor</given-names>
</name>
<xref ref-type="aff" rid="aff3">
<sup>3</sup>
</xref>
<uri xlink:href="https://loop.frontiersin.org/people/1670931/overview"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Kakes</surname>
<given-names>Geerd</given-names>
</name>
<xref ref-type="aff" rid="aff4">
<sup>4</sup>
</xref>
<uri xlink:href="https://loop.frontiersin.org/people/1649616/overview"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Rommel</surname>
<given-names>Simon</given-names>
</name>
<xref ref-type="aff" rid="aff1">
<sup>1</sup>
</xref>
<uri xlink:href="https://loop.frontiersin.org/people/1120016/overview"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Nijmeijer</surname>
<given-names>Henk</given-names>
</name>
<xref ref-type="aff" rid="aff2">
<sup>2</sup>
</xref>
<uri xlink:href="https://loop.frontiersin.org/people/1029854/overview"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Tafur Monroy</surname>
<given-names>Idelfonso</given-names>
</name>
<xref ref-type="aff" rid="aff1">
<sup>1</sup>
</xref>
<uri xlink:href="https://loop.frontiersin.org/people/1672051/overview"/>
</contrib>
</contrib-group>
<aff id="aff1">
<label>
<sup>1</sup>
</label>
<institution>Department of Electrical Engineering</institution>, <institution>Eindhoven University of Technology</institution>, <addr-line>Eindhoven</addr-line>, <country>Netherlands</country>
</aff>
<aff id="aff2">
<label>
<sup>2</sup>
</label>
<institution>Department of Mechanical Engineering</institution>, <institution>Eindhoven University of Technology</institution>, <addr-line>Eindhoven</addr-line>, <country>Netherlands</country>
</aff>
<aff id="aff3">
<label>
<sup>3</sup>
</label>
<institution>Siemens Industry Software Netherlands</institution>, <addr-line>Helmond</addr-line>, <country>Netherlands</country>
</aff>
<aff id="aff4">
<label>
<sup>4</sup>
</label>
<institution>KPN</institution>, <addr-line>The Hague</addr-line>, <country>Netherlands</country>
</aff>
<author-notes>
<fn fn-type="edited-by">
<p>
<bold>Edited by:</bold> <ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/971653/overview">Jose Santa</ext-link>, Universidad Polit&#xe9;cnica de Cartagena, Spain</p>
</fn>
<fn fn-type="edited-by">
<p>
<bold>Reviewed by:</bold> <ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/961005/overview">Felipe Boeira</ext-link>, Link&#xf6;ping University, Sweden</p>
<p>
<ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/1605781/overview">Tahir Sar&#x131;</ext-link>, Ford Otosan, Turkey</p>
</fn>
<corresp id="c001">&#x2a;Correspondence: Bruno Cimoli, <email>b.cimoli@tue.nl</email>
</corresp>
<fn fn-type="other">
<p>This article was submitted to Connected Mobility and Automation, a section of the journal Frontiers in Future Transportation</p>
</fn>
</author-notes>
<pub-date pub-type="epub">
<day>11</day>
<month>03</month>
<year>2022</year>
</pub-date>
<pub-date pub-type="collection">
<year>2022</year>
</pub-date>
<volume>3</volume>
<elocation-id>742731</elocation-id>
<history>
<date date-type="received">
<day>16</day>
<month>07</month>
<year>2021</year>
</date>
<date date-type="accepted">
<day>24</day>
<month>01</month>
<year>2022</year>
</date>
</history>
<permissions>
<copyright-statement>Copyright &#xa9; 2022 Cimoli, Xing, Ho, Passchier, Kakes, Rommel, Nijmeijer and Tafur Monroy.</copyright-statement>
<copyright-year>2022</copyright-year>
<copyright-holder>Cimoli, Xing, Ho, Passchier, Kakes, Rommel, Nijmeijer and Tafur Monroy</copyright-holder>
<license xlink:href="http://creativecommons.org/licenses/by/4.0/">
<p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (CC BY). The use, distribution or reproduction in other forums is permitted, provided the original author(s) and the copyright owner(s) are credited and that the original publication in this journal is cited, in accordance with accepted academic practice. No use, distribution or reproduction is permitted which does not comply with these&#x20;terms.</p>
</license>
</permissions>
<abstract>
<p>In this paper we report the implementation and experimental evaluation of a proposed hybrid communication ecosystem for CCAM applications such as cooperative adaptive cruise control (CACC) and smart intersections. Three wireless technologies have been suggested for communications between vehicles and intelligent traffic lights and are evaluated in this work: ITS-G5 based on IEEE 802.11p and LTE sidelink with PC5 air interface for direct short range links, and regular mobile LTE with LTE Uu air interface for long range or indirect links. The applications used are independent of the communication channel, to enable a comparison on the application level of the different communication technologies. Field experiments were carried out with two CACC-equipped vehicles and three intelligent traffic lights in two field test locations under ideal, i.e.,&#x20;no-traffic, conditions and with real traffic. Experimental results related to CACC show that the best performance in terms of latency is achieved by the ITS-G5 system, while LTE PC5 and LTE Uu links show a penalty of 20 and 50&#xa0;ms respectively. However, experimental results show that all three communication technologies were still able to guarantee string stable performance of the vehicle platoon. Regarding the smart intersections, an analysis based on field measurements and comparison between long- and short-range solutions is proposed; the analysis includes the impact of each channel on the applications such as speed advisory and green light prediction. The reported experimental evaluation shows the potential of current mobile technologies for CCAM use cases and highlights the way for further CCAM applications based on 5G and beyond mobile networks.</p>
</abstract>
<kwd-group>
<kwd>C-ITS</kwd>
<kwd>ITS-G5</kwd>
<kwd>LTE Uu</kwd>
<kwd>LTE PC5</kwd>
<kwd>CACC</kwd>
<kwd>GLOSA</kwd>
<kwd>MEC</kwd>
<kwd>MQTT</kwd>
</kwd-group>
<contract-num rid="cn001">INEA/CEF/TRAN/M2016/1364071</contract-num>
<contract-sponsor id="cn001">Connecting Europe Facility<named-content content-type="fundref-id">10.13039/100013294</named-content>
</contract-sponsor>
</article-meta>
</front>
<body>
<sec id="s1">
<title>1 Introduction</title>
<p>The past decades have seen a significant increment of the number of vehicles, while the road capacity could not follow at the same pace. Moreover, multiple studies have shown the low efficiency of human driving due to human distractions, slow reaction time, and non-optimal maneuver decisions (<xref ref-type="bibr" rid="B26">World Health Organization, 2018</xref>). These limitations pushed the development of cooperative, connected, and automated mobility (CCAM) technologies and applications with the goal to improve traffic efficiency, road safety and autonomous driving. The European Union proposed connected cooperative intelligent transport systems (C-ITSs) to provide vehicle-to-vehicle (V2V) and vehicle-to-infrastructure (V2I) connectivity for enabling cooperation and information sharing, which are essential for CCAM applications (<xref ref-type="bibr" rid="B5">C-ITS Platform, 2018</xref>). The most common technology for V2V communication is referred as ITS generation 5 (ITS-G5) (<xref ref-type="bibr" rid="B7">ETSI EN 302&#x20;663, 2012</xref>) and it is based on IEEE 802.11p for the physical layer (<xref ref-type="bibr" rid="B13">IEEE 802.11p, 2010</xref>) and the GeoNetworking protocol for the transport layer (<xref ref-type="bibr" rid="B8">ETSI EN 302&#x20;665, 2010</xref>). Recently, cellular technologies have been investigated as an alternative for the implementation of C-ITSs. In this scenario communication between vehicles is achieved indirectly via the mobile network, i.e.,&#x20;vehicle-to-network V2N communication. The feasibility of C-ITSs based on LTE networks has been investigated (<xref ref-type="bibr" rid="B16">Lianghai et&#x20;al., 2017</xref>) and has been proven for different CCAM use cases (<xref ref-type="bibr" rid="B18">Nafi et&#x20;al., 2014</xref>; <xref ref-type="bibr" rid="B6">Dey et&#x20;al., 2016</xref>). The advantage of mobile network based solutions is that they can provide a broader coverage and they can enable multi-access edge computing (MEC) for more complex applications (<xref ref-type="bibr" rid="B22">Pyyk&#xf6;nen et&#x20;al., 2020</xref>). However, these solutions are also typically affected by larger latency and lower bandwidth efficiency compared to direct ITS-G5 systems. A solution to these limitations will be the imminent deployment of 5G networks that, combined with MEC, are expected to significantly reduce the gap to ITS-G5 in terms of network key performance indicators (KPIs) (<xref ref-type="bibr" rid="B3">5G-PPP, 2021</xref>). Another mobile technology developed for C-ITSs is LTE sidelink, which supports direct V2V communications while the mobile network role is limited to the initial vehicle localization and link configuration (<xref ref-type="bibr" rid="B9">ETSI TS 303&#x20;613, 2020</xref>). LTE sidelink has arisen as an alternative to ITS-G5 because, theoretically, it is comparable in terms of latency and coverage (<xref ref-type="bibr" rid="B11">Gonzalez et&#x20;al., 2019</xref>; <xref ref-type="bibr" rid="B10">Giambene et&#x20;al., 2020</xref>; <xref ref-type="bibr" rid="B1">5GAA P-190033, 2019</xref>).</p>
<p>In this paper we investigate a C-ITS solution based on a hybrid network ecosystem that combines ITS-G5 and mobile LTE. The proposed ecosystem has been developed for two CCAM use cases: Vehicle platooning with cooperative adaptive cruise control (CACC) and smart intersections for green light optimized speed advisory (GLOSA) (<xref ref-type="bibr" rid="B2">5GAA Working Group1, 2019</xref>). The platoon use case was implemented with field experiments that were carried out with two CACC-equipped vehicles under ideal traffic conditions (<xref ref-type="bibr" rid="B28">Xing et&#x20;al., 2021</xref>). The GLOSA use case was evaluated with a vehicle crossing three intersections with smart traffic lights under real traffic conditions.</p>
<p>The outline of this paper is as follows: <xref ref-type="sec" rid="s2">Section 2</xref> introduces the ecosystem architecture and CACC strategy, <xref ref-type="sec" rid="s3">Sections 3</xref>, <xref ref-type="sec" rid="s4">4</xref>report the CACC and GLOSA evaluation and results respectively, and <xref ref-type="sec" rid="s5">Section 5</xref> summarizes and concludes the&#x20;paper.</p>
</sec>
<sec id="s2">
<title>2 Hybrid Ecosystem Architecture and Cooperative Adaptive Cruise Control Strategy</title>
<sec id="s2-1">
<title>2.1 Hybrid Ecosystem Architecture</title>
<p>The proposed hybrid ecosystem supports V2V and infrastructure-to-vehicle (I2V) communications as shown in <xref ref-type="fig" rid="F1">Figure&#x20;1</xref>. In terms of communication scenarios, direct V2V is clearly defined by messages originating from vehicles and targeting other vehicles, whereas I2V is more complex due to the several different sort of C-ITS infrastructures that can be source or destination of messages. Furthermore, indirect V2V and I2V, i.e.,&#x20;vehicle-to-everything (V2X), communications results in V2N2V and I2N2V communications respectively, where &#x201c;N&#x201d; represents the network backend, comprising servers, communication lines, and related ICT services. ITS-G5 and LTE sidelink, with PC5 air interface, are the two technologies considered for the implementation of the direct or short range V2X link. The frequency band allocated for both systems is (5.855, 5.925)&#x2009;GHz, which is defined in (<xref ref-type="bibr" rid="B7">ETSI EN 302&#x20;663, 2012</xref>) and (<xref ref-type="bibr" rid="B9">ETSI TS 303&#x20;613, 2020</xref>). For indirect or long range link the proposed technology is regular LTE, with Uu air interface. Two LTE bands are available: B20, which has uplink (0.832, 0.862)&#x2009;GHz and downlink (0.791, 0.821)&#x2009;GHz, and B3, which has uplink (1.710, 1.785)&#x2009;GHz and downlink (1.805, 1.880)&#x2009;GHz. Furthermore, the LTE Uu solution includes an edge computing solution based on the message queuing telemetry transport (MQTT) protocol, which runs over TCP/IP and is based on the publish/subscribe principle. For all technologies the allocated bandwidth is 10&#xa0;MHz, except for LTE Uu when using B3 in which case 20&#xa0;MHz are available.</p>
<fig id="F1" position="float">
<label>FIGURE 1</label>
<caption>
<p>Hybrid ecosystem for CACC and GLOSA with short and long range communication technologies. The LTE network includes evolved packet core (ePC), MEC, traffic light exchange (TLEX) and data services hub (DSH).</p>
</caption>
<graphic xlink:href="ffutr-03-742731-g001.tif"/>
</fig>
<p>
<xref ref-type="fig" rid="F2">Figure&#x20;2</xref> shows the messages exchanged over the V2X links for CACC and GLOSA. More specifically, for CACC cooperative awareness messages (CAMs) and i-GAME cooperative lane change messages (iCLCMs) are exchanged at 25&#xa0;Hz, while for GLOSA signal phase and time (SPAT) and mapdata (MAP) messages are exchanged at 1&#xa0;Hz (<xref ref-type="bibr" rid="B24">Santa et&#x20;al., 2014</xref>; <xref ref-type="bibr" rid="B4">Amsterdam Group, 2015</xref>; <xref ref-type="bibr" rid="B25">van de Sluis et&#x20;al., 2015</xref>). Moreover, real-time kinematic positioning (RTK) GPS is used for vehicle localization and clock synchronization.</p>
<fig id="F2" position="float">
<label>FIGURE 2</label>
<caption>
<p>Message types exchanged over V2V and I2V links for CACC and GLOSA use&#x20;cases.</p>
</caption>
<graphic xlink:href="ffutr-03-742731-g002.tif"/>
</fig>
<p>The V2V communication stacks of the three communication technologies are similar, as shown in <xref ref-type="fig" rid="F3">Figure&#x20;3</xref>. The two top layers, i.e.,&#x20;application and facility, are identical for the three technologies. The network layer of the two short range technologies includes public key infrastructure (PKI) for security and Geonet basic transport protocol (BTP) encoding. On the other hand, the network layer of the LTE Uu solutions includes transport layer security (TLS) and the MQTT encoding on top of TCP/IP. MQTT headers are used by the MEC to distribute messages according to the publish/subscribe principle. The access layer implementations of the two short range technologies follow different strategies: ITS-G5 is based on carrier sense multiple access, which allows data transmission only after verifying the absence of other traffic, while LTE PC5 access layer is based on time synchronization using semi-persistent scheduling (SPS) (<xref ref-type="bibr" rid="B9">ETSI TS 303&#x20;613, 2020</xref>).</p>
<fig id="F3" position="float">
<label>FIGURE 3</label>
<caption>
<p>V2V OSI stack with main functions and protocols.</p>
</caption>
<graphic xlink:href="ffutr-03-742731-g003.tif"/>
</fig>
<p>For the smart intersection scenario, the V2I link connects a vehicle to the intelligent traffic light controller (iTLC), which is installed together with the traffic light. The iTLC broadcasts MAP and SPAT messages to the approaching vehicles; therefore, communications are monodirectional I2V in the wireless domain. The communication stack of the direct V2I link is identical to the direct V2V except for the message types and their frequency. On the other hand, the indirect I2V link includes a wired connection between the iTLC and the traffic light exchange (TLEX), which is a central platform that collects data from the different traffic lights. From the TLEX the data is then sent to a data services hub (DSH) where it becomes available to the MQTT server. The MQTT server distributes messages according to the requests from the users, i.e.,&#x20;the vehicles. This type of solutions enables filtering messages before the wireless V2N link, from the eNodeB towards the vehicle, according to the use case needs, instead of continuously broadcasting messages even when no relevant information is available. However, LTE solutions based on MQTT are forced to allocate separate channels for every vehicle even when they require the same information, while direct communication solutions can use the same channel for all users. Fortunately, advanced 5G multicast techniques are expected to alleviate this&#x20;issue.</p>
</sec>
<sec id="s2-2">
<title>2.2 Cooperative Adaptive Cruise Control Strategy</title>
<p>The typical CACC strategy, which is employed in the test, is introduced here. In a homogeneous CACC platoon composed of <italic>n</italic> vehicles is considered, where <italic>l</italic>
<sub>
<italic>i</italic>
</sub>, <italic>q</italic>
<sub>
<italic>i</italic>
</sub>, <italic>v</italic>
<sub>
<italic>i</italic>
</sub> and <italic>u</italic>
<sub>
<italic>i</italic>
</sub> are the length, position, velocity, and desired acceleration of vehicle <italic>i</italic>, respectively, as illustrated in <xref ref-type="fig" rid="F4">Figure&#x20;4A</xref>). A simplified vehicle model is often adopted for CACC design, obtained through feedback linearization of a nonlinear vehicle model (<xref ref-type="bibr" rid="B12">Hedrick et&#x20;al., 1994</xref>). In CACC, a lower level controller is normally implemented to accurate the desired acceleration, although the dynamics of two vehicles might be slightly different. The resulting vehicle dynamics reads:<disp-formula id="e1">
<mml:math id="m1">
<mml:mtable class="align" columnalign="left">
<mml:mtr>
<mml:mtd columnalign="right">
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mtable class="matrix">
<mml:mtr>
<mml:mtd columnalign="center">
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>q</mml:mi>
</mml:mrow>
<mml:mo>&#x307;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>v</mml:mi>
</mml:mrow>
<mml:mo>&#x307;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>a</mml:mi>
</mml:mrow>
<mml:mo>&#x307;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mtable class="matrix">
<mml:mtr>
<mml:mtd columnalign="center">
<mml:msub>
<mml:mrow>
<mml:mi>v</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:msub>
<mml:mrow>
<mml:mi>a</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:mo>&#x2212;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
</mml:mfrac>
<mml:msub>
<mml:mrow>
<mml:mi>a</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x2b;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
</mml:mrow>
</mml:mfrac>
<mml:msub>
<mml:mrow>
<mml:mi>u</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3b8;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>a</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:mfenced>
<mml:mo>,</mml:mo>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:math>
<label>(1)</label>
</disp-formula>where <italic>a</italic>
<sub>
<italic>i</italic>
</sub> is the actual acceleration of vehicle <italic>i</italic>, <italic>&#x3b8;</italic>
<sub>a</sub> represents the vehicle actuator delay, and <italic>&#x3c4;</italic> is a time constant representing the longitudinal vehicle dynamics. (<xref ref-type="bibr" rid="B21">Ploeg et&#x20;al., 2011</xref>) showed the validated model is sufficient to analyze CACC performances considering that the deceleration limitation will not be challenged. Consequently, the transfer function <italic>G</italic>(<italic>s</italic>) from the desired acceleration <italic>u</italic>
<sub>
<italic>i</italic>
</sub> to position <italic>q</italic>
<sub>
<italic>i</italic>
</sub> reads:<disp-formula id="e2">
<mml:math id="m2">
<mml:mi>G</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>s</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>q</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>s</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>u</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>s</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfrac>
<mml:mo>&#x3d;</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3b8;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>a</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mi>s</mml:mi>
</mml:mrow>
</mml:msup>
<mml:mfrac>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mi>s</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>&#x3c4;</mml:mi>
<mml:mi>s</mml:mi>
<mml:mo>&#x2b;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfrac>
</mml:math>
<label>(2)</label>
</disp-formula>where <inline-formula id="inf1">
<mml:math id="m3">
<mml:mi>s</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:mi mathvariant="double-struck">C</mml:mi>
</mml:math>
</inline-formula> is the Laplace variable and <italic>u</italic>
<sub>
<italic>i</italic>
</sub>(<italic>s</italic>) and <italic>q</italic>
<sub>
<italic>i</italic>
</sub>(<italic>s</italic>) denote the Laplace transform of <italic>u</italic>
<sub>
<italic>i</italic>
</sub>(<italic>t</italic>) and <italic>q</italic>
<sub>
<italic>i</italic>
</sub>(<italic>t</italic>), respectively. String stability is one key requirement for CACC, since only a string-stable CACC platoon can take the full advantages in view of safety, fuel consumption, and road throughput. Here, string stability is characterized by the amplification in upstream direction of the signal of interest, which is the so-called performance-oriented approach (<xref ref-type="bibr" rid="B21">Ploeg et&#x20;al., 2011</xref>). However, the imperfection of communication will significantly compromise string stability. To deal with the communication latency, the constant time gap spacing policy is commonly utilized. The desired inter-vehicle distance <italic>d</italic>
<sub>r,<italic>i</italic>
</sub> between vehicle <italic>i</italic>&#x20;&#x2212; 1 and <italic>i</italic> involves a standstill distance <italic>r</italic>
<sub>
<italic>i</italic>
</sub> and a velocity-dependent part with <italic>h</italic> as the time gap. The actual inter-vehicle distance <italic>d</italic>
<sub>
<italic>i</italic>
</sub> is:<disp-formula id="e3">
<mml:math id="m4">
<mml:msub>
<mml:mrow>
<mml:mi>d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>q</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>q</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>.</mml:mo>
</mml:math>
<label>(3)</label>
</disp-formula>
</p>
<fig id="F4" position="float">
<label>FIGURE 4</label>
<caption>
<p>Illustration of the one-vehicle look-ahead CACC scheme: <bold>(A)</bold> illustration of vehicle <italic>i</italic> and <italic>i</italic>&#x20;&#x2212; 1 and corresponding parameters, <bold>(B)</bold> block diagram of the CACC system, <bold>(C)</bold> maximum string stable communication time delay <italic>&#x3b8;</italic> with respect to time gap <italic>h</italic> (with <italic>&#x3c4;</italic> &#x3d; 0.1, <italic>&#x3b8;</italic>
<sub>a</sub> &#x3d; 0.2&#xa0;s).</p>
</caption>
<graphic xlink:href="ffutr-03-742731-g004.tif"/>
</fig>
<p>To realize the vehicle-following objective, the inter-vehicle distance error <italic>e</italic>
<sub>
<italic>i</italic>
</sub>, defined as:<disp-formula id="e4">
<mml:math id="m5">
<mml:msub>
<mml:mrow>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>d</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="normal">r</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>,</mml:mo>
</mml:math>
<label>(4)</label>
</disp-formula>should asymptotically converge. To this end, the PD controller in (<xref ref-type="bibr" rid="B21">Ploeg et&#x20;al., 2011</xref>) is adopted. An internal input <italic>&#x3be;</italic>
<sub>
<italic>i</italic>
</sub> is introduced, which is related to the desired acceleration <italic>u</italic>
<sub>
<italic>i</italic>
</sub> as follows:<disp-formula id="e5">
<mml:math id="m6">
<mml:msub>
<mml:mrow>
<mml:mover accent="true">
<mml:mrow>
<mml:mi>u</mml:mi>
</mml:mrow>
<mml:mo>&#x307;</mml:mo>
</mml:mover>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mo>&#x2212;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>h</mml:mi>
</mml:mrow>
</mml:mfrac>
<mml:msub>
<mml:mrow>
<mml:mi>u</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x2b;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>h</mml:mi>
</mml:mrow>
</mml:mfrac>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3be;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>.</mml:mo>
</mml:math>
<label>(5)</label>
</disp-formula>
<italic>u</italic>
<sub>
<italic>i</italic>&#x2212;1,c</sub>(<italic>t</italic>) is the received desired acceleration of the preceding vehicle, which suffers from the wireless communication latency <italic>&#x3b8;</italic>, reading:<disp-formula id="e6">
<mml:math id="m7">
<mml:msub>
<mml:mrow>
<mml:mi>u</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
<mml:mo>,</mml:mo>
<mml:mi mathvariant="normal">c</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>u</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>t</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>&#x3b8;</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>.</mml:mo>
</mml:math>
<label>(6)</label>
</disp-formula>
</p>
<p>Here, the latency <italic>&#x3b8;</italic> due to different communication technologies will be varying, and thus resulting in corresponding vehicle performances.</p>
<p>Hence, the control structure can be depicted as in <xref ref-type="fig" rid="F4">Figure&#x20;4B</xref>), where <italic>H</italic>(<italic>s</italic>) &#x3d; <italic>hs</italic> &#x2b; 1, <italic>K</italic>(<italic>s</italic>) &#x3d; <italic>k</italic>
<sub>p</sub> &#x2b; <italic>k</italic>
<sub>d</sub>
<italic>s</italic> and <italic>D</italic>
<sub>ff</sub>(<italic>s</italic>) &#x3d; <italic>e</italic>
<sup>&#x2212;<italic>&#x3b8;</italic>(<italic>s</italic>)</sup> represent the Laplace transforms.</p>
<p>Therefore, the string stability transfer function <italic>S</italic>(<italic>s</italic>), which describes the relation between a relevant (scalar) signal of vehicle <italic>i</italic> and the corresponding signal of its preceding vehicle, reads:<disp-formula id="e7">
<mml:math id="m8">
<mml:mi>S</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>s</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x3d;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>u</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>s</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>u</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>s</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfrac>
<mml:mo>&#x3d;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>H</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>s</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfrac>
<mml:mo>&#x22c5;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>D</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>ff</mml:mtext>
</mml:mrow>
</mml:msub>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>s</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo>&#x2b;</mml:mo>
<mml:mi>G</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>s</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mi>K</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>s</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>1</mml:mn>
<mml:mo>&#x2b;</mml:mo>
<mml:mi>G</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>s</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mi>K</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>s</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfrac>
<mml:mo>.</mml:mo>
</mml:math>
<label>(7)</label>
</disp-formula>
</p>
<p>Note that the transfer function is the same for the velocity, acceleration, inter-vehicle distance and distance error in a homogeneous CACC string. A CACC system of interconnected vehicles is string stable if:<disp-formula id="e8">
<mml:math id="m9">
<mml:msub>
<mml:mrow>
<mml:mi>sup</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>&#x3c9;</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo stretchy="false">&#x7c;</mml:mo>
<mml:mi>S</mml:mi>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:mi>j</mml:mi>
<mml:mi>&#x3c9;</mml:mi>
</mml:mrow>
</mml:mfenced>
<mml:mo stretchy="false">&#x7c;</mml:mo>
<mml:mo>&#x2264;</mml:mo>
<mml:mn>1</mml:mn>
<mml:mo>.</mml:mo>
</mml:math>
<label>(8)</label>
</disp-formula>
</p>
<p>In the theoretical analysis considering a constant latency, there exists a maximum latency that string stability can be still guaranteed (<xref ref-type="bibr" rid="B27">Xing et&#x20;al., 2019</xref>), which is shown in <xref ref-type="fig" rid="F4">Figure&#x20;4C</xref>). The vehicle parameters have been identified in (<xref ref-type="bibr" rid="B21">Ploeg et&#x20;al., 2011</xref>): <italic>&#x3c4;</italic> &#x3d; 0.1, <italic>&#x3b8;</italic>
<sub>a</sub> &#x3d; 0.2&#xa0;s. This figure also indicates that time gaps of 0.3, 0.6, and 1.0&#xa0;s require maximum delays of 29&#xa0;ms, 111&#xa0;ms, and 300&#xa0;ms, respectively. Note that any packet loss is ignored&#x20;here.</p>
</sec>
</sec>
<sec id="s3">
<title>3 Cooperative Adaptive Cruise Control Evaluation</title>
<p>In this section the execution and evaluation of the CACC use case is reported. CACC which employs V2V communication between vehicles can lead to a safer and smoother platoon than ACC. In addition, the CACC application is suitable to evaluate the effects of different communication technologies on&#x20;ITS.</p>
<p>The use case has been implemented with two Toyota Prius car labs that drive in a two-vehicle platoon, where the following vehicle is in CACC mode, i.e.,&#x20;automatically adjusts the velocity and acceleration profiles to the ones of the leading vehicle. For the evaluation, two CACC solutions are considered for the wireless V2V link: The short range solution based on ITS-G5 or LTE PC5 and the long range solution based on LTE Uu. Note that the CACC controller is identical for all three communication technologies; however, it can be optimized according to the communication performance of the wireless channel. The hardware in the vehicles consists in a PC Engines APU2 board equipped with Sierra Wireless MC7455&#x20;LTE-A modem, which is attached to a 3 dBi MIMO LTE antenna. For the network infrastructure of the LTE Uu solution, bands 20 and 3 are available. Furthermore, at the metro core network in Helmond a mobile edge computing (MEC) node is used as MQTT server for the CACC application (<xref ref-type="bibr" rid="B28">Xing et&#x20;al., 2021</xref>). Field measurements have been conducted in the RDW test centre in Lelystad (NL) shown in <xref ref-type="fig" rid="F5">Figure&#x20;5</xref> (<xref ref-type="bibr" rid="B23">RDW, 2021</xref>). The test centre is a ring track designed for maintaining high velocity profiles even in the curved sections. The main target of the tests in Lelystad was evaluating the vehicle platooning when driving with high speed profiles and no traffic interference (only authorized vehicles can drive on the track). However, in the test centre, the mobile network has only one base station, eNodeB 29,551, which is positioned at a minimum and maximum distance from the track of 900&#x20;1750&#xa0;m respectively. Because of the coverage limitations, only the B20 band was available for the LTE Uu link. The leading vehicle, Prius 2 (P2), is manually driven, and it follows the acceleration profile shown in <xref ref-type="fig" rid="F5">Figure&#x20;5</xref>. The following vehicle, Prius 3 (P3), accelerates or decelerates automatically in CACC mode. For each test four laps are executed, for a total of four acceleration and deceleration sections. The CACC controller is set in gap control mode, which aims to maintain the time gap between the CACC-equipped vehicle and its predecessor. The CACC schematic of the vehicles is reported in <xref ref-type="fig" rid="F5">Figure&#x20;5</xref>: The C-ITS gateway is the platform of the access layers of the three channels, the on-board-unit (OBU) executes the functions of the network and facility layers, the real-time CACC platform runs the CACC controller algorithm, the vehicle gateway MOVE interfaces the controller with the vehicle actuators and the human machine interface (HMI) platform displays information on a dashboard. Furthermore, two measurement points are considered for the data logging: The flow of exchanged CAMs and iCLCMs at the OBU, and the vehicle state and position at the controller are network (CAN) bus. Moreover, the GPS receiver provides the vehicle position to the CACC platform and time synchronization to the OBU by a pulse per second (PPS) signal with sub millisecond resolution.</p>
<fig id="F5" position="float">
<label>FIGURE 5</label>
<caption>
<p>
<bold>(A)</bold> CACC field test at the RDW Testcentrum in Lelystad (NL). <bold>(B)</bold> location of LTE base station eNodeB 2955. <bold>(C)</bold> schematic of the CACC system inside the two vehicles.</p>
</caption>
<graphic xlink:href="ffutr-03-742731-g005.tif"/>
</fig>
<sec id="s3-1">
<title>3.1 Key Performance Indicators Definition for Cooperative Adaptive Cruise Control Use Case</title>
<p>The most critical KPI for CACC applications is latency because it determines how fast the CACC controller can react. Another important KPI is the number of lost messages, which characterizes the quality and stability of the wireless channel. Regarding the platooning application, the function to optimize is the deviation from the target gap, which is typically characterized as KPI by the inter-vehicle distance. Moreover, the stability of platoon is characterized by the acceleration and velocity amplifications. The selected KPIs are defined as follows:<list list-type="simple">
<list-item>
<p>&#x2022; One Trip Time latency (OTTl), which refers to the difference between the transmitted TTx and received TRx timestamps of a packet or message. At the receiver side, the transmission order and the lost messages are not considered.</p>
</list-item>
<list-item>
<p>&#x2022; Packet error rate (PER), which refers to the percentage of lost packets or messages. A packet is considered lost when it appears in the log file of the Tx and not in the Rx&#x20;one.</p>
</list-item>
<list-item>
<p>&#x2022; Velocity amplification, which refers to the deviation of the velocity profiles of the vehicles in a platoon due to the acceleration amplification.</p>
</list-item>
<list-item>
<p>&#x2022; Inter-vehicle distance, which refers to the distance from the leading to the following vehicle.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s3-2">
<title>3.2 Short Range Cooperative Adaptive Cruise Control Solution</title>
<p>In this section experimental results when operating with the direct V2V solution are reported for both ITS-G5 and LTE PC5. <xref ref-type="fig" rid="F6">Figure&#x20;6</xref> shows the empirical curves of the probability density function (PDF) and cumulative distribution function (CDF) of the OTTl from the measurements with the ITS-G5 and LTE PC5 links. The mode of the OTTl of the ITS-G5 link was approximately 4&#xa0;ms with more than 45% of the total messages, while the one of the LTE PC5 link ranges between 22 and 24&#xa0;ms. Moreover, the latency PDF of the LTE PC5 link is spread on the left side of the mode, reaching values up to 80&#xa0;ms. The correspondent CDF curves shows that only 10% of the messages are received with OTTl below the mode and only 60% below 40&#xa0;ms that corresponds to the message frequency of 25&#xa0;Hz.</p>
<fig id="F6" position="float">
<label>FIGURE 6</label>
<caption>
<p>Empirical PDF <bold>(A)</bold> and CDF <bold>(B)</bold> of the OTTl of the CAMs.</p>
</caption>
<graphic xlink:href="ffutr-03-742731-g006.tif"/>
</fig>
<p>
<xref ref-type="table" rid="T1">Table&#x20;1</xref> (top) reports the OTTl statistical properties of both CAMs and iCLCMs in the two directions: P2 to P3 (P3 to P2). As expected from the curves in <xref ref-type="fig" rid="F6">Figure&#x20;6</xref>, the mode of the ITS-G5 link is 4&#xa0;ms, the mean drops between 3.4 and 3.9&#xa0;ms and the standard deviation is between 1 and 1.5&#xa0;ms. Moreover, more than 95% of the messages was received within 5&#xa0;ms. On the other hand, the OTTl of the LTE PC5 link has a mode between 22 and 25&#xa0;ms, a mean is shifted on the left to 38&#xa0;ms and a standard deviation between 13 and 15&#xa0;ms. Lastly the PER of the ITS-G5 link is below 0.1% for iCLCMs and below 0.02% for CAMs, while the PER of the LTE PC5 link ranges between 4.5 and&#x20;5%.</p>
<table-wrap id="T1" position="float">
<label>TABLE 1</label>
<caption>
<p>OTTl specifications derived from the measurements in Lelystad with the ITS-G5 and LTE PC5 links (top) and with the LTE Uu link (middle). Latency comparison of the LTE mobile networks in Lelystad test center and Helmond, where the MEC is physically located (bottom).</p>
</caption>
<table>
<thead valign="top">
<tr>
<th rowspan="2" align="left"/>
<th rowspan="2" align="center">Type</th>
<th rowspan="2" align="center">n. messages</th>
<th colspan="4" align="center">OTTl (ms)</th>
<th rowspan="2" align="center">PER (%)</th>
</tr>
<tr>
<th align="center">Mode</th>
<th align="center">Mean</th>
<th align="center">Std</th>
<th align="center">95th %ile</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td rowspan="2" align="left">ITS-G5</td>
<td align="left">CAM</td>
<td align="center">13,800 (13,801)</td>
<td align="char" char="(">4 (4)</td>
<td align="char" char="(">3.4 (3.4)</td>
<td align="char" char="(">1.0 (1.0)</td>
<td align="center">4 (4)</td>
<td align="char" char=".">0.01 (0.02)</td>
</tr>
<tr>
<td align="left">iCLCM</td>
<td align="center">13,800 (13,800)</td>
<td align="char" char="(">4 (4)</td>
<td align="char" char="(">3.9 (3.9)</td>
<td align="char" char="(">1.7 (1.0)</td>
<td align="center">5 (5)</td>
<td align="char" char=".">0.09 (0.09)</td>
</tr>
<tr>
<td rowspan="2" align="left">LTE PC5</td>
<td align="left">CAM</td>
<td align="center">6,800 (6,800)</td>
<td align="char" char="(">24 (22)</td>
<td align="char" char="(">38.0 (37.3)</td>
<td align="char" char="(">14.2 (14.2)</td>
<td align="center">65 (64)</td>
<td align="char" char=".">4.46 (5.09)</td>
</tr>
<tr>
<td align="left">iCLCM</td>
<td align="center">6,800 (6,800)</td>
<td align="char" char="(">25 (23)</td>
<td align="char" char="(">30.8 (31.0)</td>
<td align="char" char="(">13.5 (13.6)</td>
<td align="center">56 (58)</td>
<td align="char" char=".">4.51 (4.82)</td>
</tr>
</tbody>
</table>
<table>
<tbody valign="top">
<tr>
<td rowspan="2" align="left">
</td>
<td rowspan="2" align="center">
<bold>Type</bold>
</td>
<td rowspan="2" align="center">
<bold>n. messages</bold>
</td>
<td colspan="4" align="center">
<bold>OTTl (ms)</bold>
</td>
<td rowspan="2" align="center">
<bold>PER<xref ref-type="table-fn" rid="Tfn1">
<sup>a</sup>
</xref>
</bold> <bold>(%)</bold>
</td>
</tr>
<tr>
<td align="center">
<bold>Mode</bold>
</td>
<td align="center">
<bold>Mean</bold>
</td>
<td align="center">
<bold>Std</bold>
</td>
<td align="center">
<bold>95th</bold> <bold>%ile</bold>
</td>
</tr>
<tr>
<td rowspan="2" align="left">TLS on</td>
<td align="left">CAM</td>
<td align="center">13,649 (13,619)</td>
<td align="char" char="(">30 (30)</td>
<td align="char" char="(">81.0 (69.5)</td>
<td align="char" char="(">119.4 (88.1)</td>
<td align="char" char=".">292.0 (225.0)</td>
<td align="center">&#x2013; (0.2)</td>
</tr>
<tr>
<td align="left">iCLCM</td>
<td align="center">13,649 (13,620)</td>
<td align="char" char="(">27 (27)</td>
<td align="char" char="(">72.3 (60.1)</td>
<td align="char" char="(">116.3 (84.6)</td>
<td align="char" char=".">273.5 (212.5)</td>
<td align="center">&#x2013; (0.2)</td>
</tr>
<tr>
<td rowspan="2" align="left">TLS off</td>
<td align="left">CAM</td>
<td align="center">13,974 (13,942)</td>
<td align="char" char="(">30 (30)</td>
<td align="char" char="(">56.9 (52.3)</td>
<td align="char" char="(">75.1 (56.8)</td>
<td align="char" char=".">146.0 (133.0)</td>
<td align="center">&#x2013; (2.0)</td>
</tr>
<tr>
<td align="left">iCLCM</td>
<td align="center">13,974 (13,942)</td>
<td align="char" char="(">27 (27)</td>
<td align="char" char="(">49.3 (45.0)</td>
<td align="char" char="(">72.9 (52.5)</td>
<td align="char" char=".">128.5 (106.5)</td>
<td align="center">&#x2013; (2.0)</td>
</tr>
</tbody>
</table>
<table>
<tbody valign="top">
<tr>
<td rowspan="2" align="left">
</td>
<td rowspan="2" align="center">
<bold>n. messages</bold>
</td>
<td colspan="4" align="center">
<bold>OTTl (ms)</bold>
</td>
<td rowspan="2" align="center">
<bold>PER<xref ref-type="table-fn" rid="Tfn1">
<sup>a</sup>
</xref>
</bold> <bold>(%)</bold>
</td>
</tr>
<tr>
<td align="center">
<bold>Mode</bold>
</td>
<td align="center">
<bold>Mean</bold>
</td>
<td align="center">
<bold>Std</bold>
</td>
<td align="center">
<bold>95th</bold> <bold>%ile</bold>
</td>
</tr>
<tr>
<td align="left">Lelystad</td>
<td align="center">13,649 (13,619)</td>
<td align="char" char="(">30 (30)</td>
<td align="char" char="(">81.0 (69.5)</td>
<td align="char" char="(">119.4 (88.1)</td>
<td align="center">292 (225)</td>
<td align="center">&#x2013; (0.2)</td>
</tr>
<tr>
<td align="left">Helmond</td>
<td align="center">47,498 (47,495)</td>
<td align="char" char="(">22 (22)</td>
<td align="char" char="(">26 (28)</td>
<td align="char" char="(">13.3 (14.2)</td>
<td align="center">46 (47)</td>
<td align="center">&#x2013; (&#x2013;)</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn id="Tfn1">
<label>a</label>
<p>&#x201c;&#x2013;&#x201d; indicates no packet error observed.</p>
</fn>
</table-wrap-foot>
</table-wrap>
<p>Experimental results show an outstanding performance in terms of OTTl and PER when operating with the ITS-G5 link. However, it must be taken into consideration the ideal conditions in the Lelystad, where no other vehicles were involved and there was almost no interference from other wireless devices. The performance of the LTE PC5 solution was significantly worse than ITS-G5. The main cause of this penalty is the mismatch between the frequency of the SPS flow defined by the LTE PC5 standard and the message frequency defined by the application layer. The result of this mismatch is the larger OTTl mode and variance shown in both <xref ref-type="fig" rid="F6">Figure&#x20;6</xref> and <xref ref-type="table" rid="T1">Table&#x20;1</xref> (top).</p>
</sec>
<sec id="s3-3">
<title>3.3 Long Range Cooperative Adaptive Cruise Control Solution</title>
<p>Experimental results of the CACC tests executed with the long range solution based on LTE Uu are reported in this section. The first KPI to be analyzed is the OTTl that is reported in <xref ref-type="fig" rid="F7">Figure&#x20;7</xref>. Transport layer security (TLS) is applied and included in the OTTl calculation. From the CDF curves we can observe that there is no significant impact of the TLS for the messages received within 40&#xa0;ms, which are 60%. The TLS becomes relevant when we consider the remaining 40% of the messages that were received with OTTl larger than 40&#xa0;ms. More specifically, the CDF curves show a penalty between 20 and 40&#xa0;ms when the TLS is applied.</p>
<fig id="F7" position="float">
<label>FIGURE 7</label>
<caption>
<p>Empirical PDF <bold>(A)</bold> and CDF <bold>(B)</bold> of the OTTl of the CAMs with TLS on/off. Four laps were executed with TLS on and other four laps with TLS&#x20;off.</p>
</caption>
<graphic xlink:href="ffutr-03-742731-g007.tif"/>
</fig>
<p>A more quantitative description of the OTTl measurements is reported in <xref ref-type="table" rid="T1">Table&#x20;1</xref> (middle). Data is presented for CAMs with TLS on/off. Experimental results confirm that the impact of the TLS does not affect the distribution around the mode, which is between 27 and 31&#xa0;ms. We can notice that the 95th percentile doubles and both mean and standard deviation are shifted by 20&#x2013;30&#xa0;ms when the TLS is on. Another KPI to consider is the reliability described by the PER, which is almost null as long the mobile network coverage is granted. However, occasionally the connection was lost in the straight line section with the lowest signal strength, which is the most distant from the eNodeB, thus raising the&#x20;PER.</p>
<p>Overall, the performance of the long range system was penalized by the weak coverage of the eNodeB and the distance from the MEC located in Helmond (<xref ref-type="bibr" rid="B20">Passchier et&#x20;al., 2015</xref>), which is more than 100&#xa0;km from Lelystad. To characterize this penalty, we also recorded data in Helmond, where the MEC is hosted. For these measurements the two vehicles were in CACC mode and they were communicating through the LTE network. However, CACC vehicle platooning could not be tested. The LTE network in Helmond allowed to use B3; however, we only enabled B20 to be comparable with the results in Lelystad. <xref ref-type="fig" rid="F8">Figure&#x20;8</xref> shows the comparison between the OTTl measured in Lelystad and Helmond. We can see that in Helmond the distribution of the OTTl was shifted down by approximately 8&#xa0;ms compared to the one in Lelystad.</p>
<fig id="F8" position="float">
<label>FIGURE 8</label>
<caption>
<p>OTTl comparison between data collected in Lelystad and Helmond.</p>
</caption>
<graphic xlink:href="ffutr-03-742731-g008.tif"/>
</fig>
<p>Furthermore, <xref ref-type="table" rid="T1">Table&#x20;1</xref> (bottom) reports the statistical characteristics of the OTTl measured in Lelystad and Helmond. We can notice a significant improvement in Helmond; more specifically, the mode is 8&#xa0;ms lower and the 95th percentile is 47&#xa0;ms, which is a fifth of the one in Lelystad.</p>
</sec>
<sec id="s3-4">
<title>3.4 Vehicle Dynamic Analysis of Cooperative Adaptive Cruise Control Solutions</title>
<p>To continue the evaluation, we analyzed the vehicle dynamic KPIs related to latency and PER; more specifically, the analysis focuses on the effect of the OTTl on the performance of the CACC controller. Experimental results of three communication technologies with a time gap of 0.3&#xa0;s are reported. For each communication technology, four laps were carried out. Results with the most similar speed profiles of P2 are chosen, to compare the performances of P3 and the effects due to communication technologies. The distance error contains the constant inter-vehicle distance when the CACC string is standstill, thus the error will converge to the constant inter-vehicle distance when the CACC string is achieved at static conditions, i.e.,&#x20;the velocities are constant. Due to the limited length of the test field, the CACC string may not have been in a static condition when the preceding vehicle started accelerating or decelerating. The acceleration/velocity indicators extracted are based on the time period when velocity variations occurred, while the inter-vehicle distance and distance error indicators are extracted when the velocity variations finished. In <xref ref-type="fig" rid="F9">Figure&#x20;9</xref>, the acceleration phase and deceleration phase are shown for the two short range technologies: ITS G5 and LTE PC5. Furthermore, the key performance indicators based on the experiments are summarized in <xref ref-type="table" rid="T2">Table&#x20;2</xref>. Note that the string stable or unstable performances will be better observed in the case of longer platoon (<xref ref-type="bibr" rid="B21">Ploeg et&#x20;al., 2011</xref>). For the accelerating phase, the acceleration magnitude of the preceding vehicle is around 0.8&#xa0;m/s<sup>2</sup>. For ITS-G5 and LTE PC5 the maximum acceleration of P3 reached the peak value. For the deceleration phase, the magnitude is much larger, thus the acceleration amplification performances will be more obvious if there is overshoot. For ITS-G5, the deceleration of P3 (1.28&#xa0;m/s<sup>2</sup>) is much smaller than that of P2 (1.55&#xa0;m/s<sup>2</sup>). For LTE PC5, the deceleration of P3 (1.60&#xa0;m/s<sup>2</sup>) almost reaches that of P2 (1.65&#xa0;m/s<sup>2</sup>). Clearly, there is no overshoot for ITS-G5 and LTE&#x20;PC5.</p>
<fig id="F9" position="float">
<label>FIGURE 9</label>
<caption>
<p>Vehicle responses of CACC string with ITS-G5 <bold>(A)</bold> and LTE PC5&#x20;<bold>(B)</bold>.</p>
</caption>
<graphic xlink:href="ffutr-03-742731-g009.tif"/>
</fig>
<table-wrap id="T2" position="float">
<label>TABLE 2</label>
<caption>
<p>String stability KPIs for short-range communication technologies, with time gap &#x3d; 0.3&#xa0;s.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th rowspan="4" align="left"/>
<th rowspan="2" colspan="2" align="center">Accel.</th>
<th rowspan="2" colspan="2" align="center">Decel.</th>
<th colspan="2" align="center">Velocity</th>
<th colspan="2" align="center">Distance</th>
<th colspan="2" align="center">Error</th>
</tr>
<tr>
<th align="center">max</th>
<th align="center">min</th>
<th rowspan="2" align="center">max</th>
<th rowspan="2" align="center">min</th>
<th rowspan="2" align="center">max</th>
<th rowspan="2" align="center">min</th>
</tr>
<tr>
<th align="center">P3</th>
<th align="center">P2</th>
<th align="center">P3</th>
<th align="center">P2</th>
<th align="center">P3</th>
<th align="center">P3</th>
</tr>
<tr>
<th colspan="2" align="center">(m/s<sup>2</sup>)</th>
<th colspan="2" align="center">(m/s<sup>2</sup>)</th>
<th align="center">(m/s)</th>
<th align="center">(m/s)</th>
<th align="center">(m)</th>
<th align="center">(m)</th>
<th align="center">(m)</th>
<th align="center">(m)</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="left">ITS-G5</td>
<td align="char" char=".">0.74</td>
<td align="char" char=".">0.79</td>
<td align="char" char=".">1.52</td>
<td align="char" char=".">1.59</td>
<td align="char" char=".">30.6</td>
<td align="char" char=".">24.8</td>
<td align="char" char=".">13.1</td>
<td align="char" char=".">10.4</td>
<td align="char" char=".">4.09</td>
<td align="char" char=".">2.79</td>
</tr>
<tr>
<td align="left">LTE PC5</td>
<td align="char" char=".">0.82</td>
<td align="char" char=".">0.82</td>
<td align="char" char=".">1.60</td>
<td align="char" char=".">1.65</td>
<td align="char" char=".">30.5</td>
<td align="char" char=".">24.9</td>
<td align="char" char=".">13.2</td>
<td align="char" char=".">11.1</td>
<td align="char" char=".">4.33</td>
<td align="char" char=".">3.35</td>
</tr>
<tr>
<td align="left">LTE Uu TLS on</td>
<td align="char" char=".">0.80</td>
<td align="char" char=".">0.79</td>
<td align="char" char=".">1.68</td>
<td align="char" char=".">1.57</td>
<td align="char" char=".">30.6</td>
<td align="char" char=".">24.9</td>
<td align="char" char=".">14.4</td>
<td align="char" char=".">11.4</td>
<td align="char" char=".">5.35</td>
<td align="char" char=".">3.89</td>
</tr>
<tr>
<td align="left">LTE Uu TLS off</td>
<td align="char" char=".">0.82</td>
<td align="char" char=".">0.74</td>
<td align="char" char=".">1.47</td>
<td align="char" char=".">1.57</td>
<td align="char" char=".">30.3</td>
<td align="char" char=".">24.9</td>
<td align="char" char=".">13.5</td>
<td align="char" char=".">11.2</td>
<td align="char" char=".">4.87</td>
<td align="char" char=".">3.66</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>In view of velocity responses, for both communication technologies, the velocity of P3 reaches that of P2 without observable overshoot. For the inter-vehicle distance and error, the LTE PC5 communication experiences a larger maximum error since the following vehicle P3 responses for acceleration with the longer latency. With the different communication environment (e.g., in Helmond), the latency and PER shall be influenced (<xref ref-type="bibr" rid="B15">Lei et&#x20;al., 2011</xref>). Thus, we artificially added latency and packet error to show the CACC-equipped vehicle performances in a more realistic driving environment. When 20% packet error is added, there exists two or three consecutive packet losses for ITS-G5, while three or four consecutive packet losses occur with LTE PC5, as shown in <xref ref-type="fig" rid="F10">Figure&#x20;10</xref>. Furthermore, the following vehicle decelerated with more than 0.5&#xa0;m/s<sup>2</sup>, when the connection is lost. In fact, the CACC will degrade to ACC mode when three packets are lost or the latency of over 100&#xa0;ms due to the safety functionality. Therefore, CACC is sensitive with large PER with the short-range communication technologies.</p>
<fig id="F10" position="float">
<label>FIGURE 10</label>
<caption>
<p>
<bold>(A)</bold> ITS-G5 and <bold>(B)</bold> LTE PC5 solutions acceleration and velocity responses with 20% PER impairment. LTE Uu solution acceleration and velocity responses with TLS on <bold>(C)</bold> and off <bold>(D)</bold>.</p>
</caption>
<graphic xlink:href="ffutr-03-742731-g010.tif"/>
</fig>
<p>
<xref ref-type="fig" rid="F10">Figure&#x20;10</xref> shows the vehicle responses by LTE Uu with TLS on and off. When TLS is on, there is a slightly acceleration overshoot, while the deceleration is amplified along the CACC string (<xref ref-type="table" rid="T2">Table&#x20;2</xref>). When the latency is over 100&#xa0;ms, CACC will degrade to the ACC mode. When TLS is off, the latency is less compared to that with TLS on. However, the CACC connection functionality still degrades. Note that for LTE Uu, the connection on the curves is influenced, such that the CACC string is not at a stationary situation before the acceleration/deceleration slots. This will significantly affect the inter-vehicle distance indicator. Thus, the inter-vehicle distance will not be focused for LTE Uu. When the communication environment is better in Helmond (where more MECs exist and the signal strength is higher), LTE Uu should be able to support the CACC application.</p>
</sec>
</sec>
<sec id="s4">
<title>4 Green Light Optimized Speed Advisory Evaluation</title>
<p>GLOSA is one of the applications of smart intersection systems that involve I2V communications. In this section we report the evaluation of the smart intersection C-ITS, whose infrastructure is located in the Helmond test site shown <xref ref-type="fig" rid="F11">Figure&#x20;11</xref>. The test site covers a section of Europaweg (provincial road N270) of almost 2&#xa0;km (<xref ref-type="bibr" rid="B19">Passchier et&#x20;al., 2011</xref>). For the evaluation we selected three intersections with three intelligent traffic lights HEL804, HEL806 and HEL701. Two solutions are available for I2V communications from the iTLCs to the approaching vehicles: Short range based on ITS-G5 and long range based on LTE Uu. Unfortunately, LTE sidelink was not supported by the iTLCs hardware; thus, a short range solution based on LTE PC5 could not be implemented and tested on the field. The LTE mobile network included two eNodeB units and both B20 and B3 bands were available. Specifications of the messages broadcasted by iTLCs are reported in <xref ref-type="table" rid="T3">Table&#x20;3</xref> (top). The size of CAM is fixed to 26 bytes, while the size of the MAP ones derives from the area considered as the road crossing; therefore, it differs for each iTLC. On the other hand, the size of SPAT messages is variable and ranges between 300 and 1000 bytes. The final length of a message includes the headers and footers, whose size depends on the technology. However, only SPAT messages provide information that requires to be updated, while the information of CAMs and MAP messages provide static information that is used by the vehicle to locate the positions of the traffic light and the geography of the intersection. The update rate of the messages is 100&#xa0;ms; however, iTLCs are configured to publish new messages every second, i.e.,&#x20;at a rate of 1&#xa0;Hz, unless a change has occurred. Therefore, the iTLC is expected to broadcast CAM and MAP messages at a constant rate of 1&#xa0;Hz, because their content is constant over time. SPAT messages instead describe the signal state of the intersection, which mutates over time; therefore, iTLCs are expected to sporadically publish SPAT messages within the 1&#xa0;s window.</p>
<fig id="F11" position="float">
<label>FIGURE 11</label>
<caption>
<p>GLOSA field test site in Helmond with the three intelligent traffic lights: HEL804, HEL806 and HEL701.</p>
</caption>
<graphic xlink:href="ffutr-03-742731-g011.tif"/>
</fig>
<table-wrap id="T3" position="float">
<label>TABLE 3</label>
<caption>
<p>Specifications of the messages broadcasted by the iTLCs in the Helmond test site (top) and messages broadcasted over the two wireless links and the number of users to have same data efficiency (bottom).</p>
</caption>
<table>
<thead valign="top">
<tr>
<th rowspan="2" align="left">Name</th>
<th rowspan="2" align="center">Msg. ID</th>
<th colspan="3" align="center">Msg. size (B)</th>
<th colspan="2" align="center">Header/trailer (B)</th>
</tr>
<tr>
<th align="center">
<italic>HEL804</italic>
</th>
<th align="center">
<italic>HEL806</italic>
</th>
<th align="center">
<italic>HEL701</italic>
</th>
<th align="center">ITS-G5</th>
<th align="center">LTE Uu</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="left">CAM</td>
<td align="center">02</td>
<td align="center">26</td>
<td align="center">26</td>
<td align="center">26</td>
<td align="center">114/4</td>
<td align="center">&#x2014;</td>
</tr>
<tr>
<td align="left">SPAT</td>
<td align="center">04</td>
<td align="center">Not fixed</td>
<td align="center">Not fixed</td>
<td align="center">Not fixed</td>
<td align="center">120/4</td>
<td align="center">66/0</td>
</tr>
<tr>
<td align="left">MAP</td>
<td align="center">05</td>
<td align="center">1,704</td>
<td align="center">1,562</td>
<td align="center">3,704</td>
<td align="center">120/4</td>
<td align="center">66/0</td>
</tr>
</tbody>
</table>
<table>
<tbody valign="top">
<tr>
<td rowspan="2" colspan="2" align="left">
</td>
<td colspan="3" align="center">
<bold>CAM</bold>
</td>
<td colspan="3" align="center">
<bold>SPAM</bold>
</td>
<td colspan="3" align="center">
<bold>MAP</bold>
</td>
</tr>
<tr>
<td align="left">
<italic>
<bold>HEL804</bold>
</italic>
</td>
<td align="left">
<italic>
<bold>HEL806</bold>
</italic>
</td>
<td align="left">
<italic>
<bold>HEL701</bold>
</italic>
</td>
<td align="left">
<italic>
<bold>HEL804</bold>
</italic>
</td>
<td align="left">
<italic>
<bold>HEL806</bold>
</italic>
</td>
<td align="left">
<italic>
<bold>HEL701</bold>
</italic>
</td>
<td align="left">
<italic>
<bold>HEL804</bold>
</italic>
</td>
<td align="left">
<italic>
<bold>HEL806</bold>
</italic>
</td>
<td align="left">
<italic>
<bold>HEL701</bold>
</italic>
</td>
</tr>
<tr>
<td rowspan="2" align="left">ITS-G5</td>
<td align="left">Number</td>
<td align="center">4,551</td>
<td align="center">4,522</td>
<td align="center">4,844</td>
<td align="center">6,838</td>
<td align="center">6,270</td>
<td align="center">7,287</td>
<td align="center">8,373</td>
<td align="center">8,471</td>
<td align="center">18,452</td>
</tr>
<tr>
<td align="left">Bytes</td>
<td align="center">655,344</td>
<td align="center">651,168</td>
<td align="center">697,536</td>
<td align="center">2,762,293</td>
<td align="center">3,630,173</td>
<td align="center">5,578,525</td>
<td align="center">8,321,248</td>
<td align="center">7,596,294</td>
<td align="center">19,400,667</td>
</tr>
<tr>
<td rowspan="1" align="left">LTE Uu</td>
<td align="left">Number</td>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">16,738</td>
<td align="center">18,090</td>
<td align="center">18,744</td>
<td align="center">11</td>
<td align="center">9</td>
<td align="center">17</td>
</tr>
<tr>
<td align="left"/>
<td align="left">Bytes</td>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">0</td>
<td align="center">5,651,552</td>
<td align="center">9,313,359</td>
<td align="center">13,181,824</td>
<td align="center">18,854</td>
<td align="center">14,229</td>
<td align="center">61,455</td>
</tr>
<tr>
<td align="left">Intersection (users)</td>
<td align="left">
</td>
<td align="left">
</td>
<td align="left">
</td>
<td align="left">
</td>
<td align="char" char=".">6.13</td>
<td align="char" char=".">4.16</td>
<td align="char" char=".">5.49</td>
<td align="left">
</td>
<td align="left">
</td>
<td align="left">
</td>
</tr>
</tbody>
</table>
</table-wrap>
<sec id="s4-1">
<title>4.1 Key Performance Indicators Definition for Green Light Optimized Speed Advisory Use Case</title>
<p>Latency is not the most critical KPI of the GLOSA use case because of the typical low transmission rate. In this scenario, other KPIs such as the coverage become more relevant because of the larger number of potential vehicles involved in the use case. Regarding the application performance, the most typical KPIs are travelling time and energy consumption. Following the definition of the selected KPIs:<list list-type="simple">
<list-item>
<p>&#x2022; Data efficiency, which refers to the percentage of data considered relevant for the use case from the total of data transmitted through the wireless channel. This KPI provides a tool to compare efficiency MQTT publish/demand and standard broadcasting approaches.</p>
</list-item>
<list-item>
<p>&#x2022; Coverage, which refers to the distance when the vehicle enters in or leaves the covered area, which is defined as the area around the traffic light where the packet delivery rate (PDR) measured by the vehicle is above a chosen threshold.</p>
</list-item>
<list-item>
<p>&#x2022; Energy consumption with respect to GLOSA requirements of the communication distance. The fuel consumption and battery loss of a vehicle model in Matlab/Simulink are calculated, in which a longitudinal hybrid electric vehicle with parallel hybrid transmission is&#x20;used.</p>
</list-item>
<list-item>
<p>&#x2022; Traveling time crossing the traffic lights. The GLOSA-equipped vehicle targets a highest speed passing the intersection.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s4-2">
<title>4.2 Evaluation Green Light Optimized Speed Advisory Solutions</title>
<p>In this section we report the experimental data and result analysis of the short and long range solutions based on ITS-G5 and LTE Uu respectively. For the evaluation the vehicle was collecting data from the two systems that were running in parallel. Experimental data has been collected over five test sessions at different hours of the day for a total of 225&#xa0;min. <xref ref-type="table" rid="T3">Table&#x20;3</xref> (bottom) reports the number of messages received by the vehicle from the iTLCs overall the test sessions. Moreover, <xref ref-type="fig" rid="F12">Figure&#x20;12</xref> shows the respective percentages of each message type. For this use case we assume that only the SPAT messages are relevant for the application; therefore, the data efficiency of the short range solution has an efficiency of 24% while the long range is above 99%. More specifically, the ITS-G5 channel is penalized by the large size MAP messages, which must be continuously broadcast despite having the same content. Furthermore, the short range system could not block messages from other iTLCs of nearby traffic lights, despite it was not transitioning through their intersections; these messages are referred as others. Measurements show a clear a clear advantage of the long range solution in terms of data efficiency; however, the short range system has the advantage that multiple users can share the same channel. On the other hand, the long-range solution must allocate dedicated channels for each user even if they are requesting the same data. Therefore, the data efficiency of LTE Uu decreases linearly with the number of users while the one of ITS-G5 remain constant. <xref ref-type="table" rid="T3">Table&#x20;3</xref> (bottom) reports the intersection point when the number of users make the data efficiency of the two systems to be the same. For the three intersections in field test, we can derive that the long range solution is more efficient than the short range one if the number of vehicles is lower than four to six, depending on the MAP size and frequency of SPAT updates.</p>
<fig id="F12" position="float">
<label>FIGURE 12</label>
<caption>
<p>Percentages of SPAT, MAP, CAM, and other received messages from the ITS-G5 link <bold>(A)</bold>. Average reach of the three iTLCs when approaching (leaving) the intersections <bold>(B)</bold>.</p>
</caption>
<graphic xlink:href="ffutr-03-742731-g012.tif"/>
</fig>
<p>When analyzing the coverage, measurements showed that there was no loss of connection in the LTE Uu link, i.e.,&#x20;the PDR was always 1 when the vehicle was crossing the intersections. This is due to the optimal coverage of the mobile network in Helmond and the significant message frequency of 1&#xa0;Hz. On the other hand, the ITS-G5 link was bounded to the distance of the vehicle from the traffic light. <xref ref-type="fig" rid="F12">Figure&#x20;12</xref> shows the coverage of the three iTLCs for three PDRs. Measurements show a coverage above 400&#xa0;m when the vehicle was driving in the main road, i.e.,&#x20;west and east directions, while it drops below 300&#xa0;m in the secondary road. This large coverage is mainly due to the gain of the antennas on the vehicle and the ideal conditions of the road. To continue the evaluation, we studied the impact of the communication KPIs on the GLOSA application and objectives. When considering the GLOSA application, we must consider both the individual and multiple vehicle cases. For an individual vehicle, the GLOSA strategy targets the highest speed when crossing the intersection, i.e.,&#x20;the smallest speed deceleration. Therefore, the maneuver of the GLOSA equipped vehicle will have a lower influence on the other traffic participants following the vehicle. Regarding the fuel consumption, simulation results reported in (<xref ref-type="bibr" rid="B17">MathWorks, 2021</xref>) shows that responding to SPAT messages further in advance cannot guarantee the total energy consumption would be lower. On the other hand, if the vehicle can receive SPAT messages earlier, it can also start decelerating earlier, thus reducing the deceleration amplitude and consequently the travelling time. Therefore, it can be suggested that the longer coverage achieved by the LTE Uu system would enable to improve the travelling time KPI in the single vehicle scenario. If we consider the scenario with multiple vehicles crossing the intersection and all of them are GLOSA-equipped, the optimal communication distance around 350&#xa0;m (<xref ref-type="bibr" rid="B14">Katsaros et&#x20;al., 2011</xref>), such that the lowest total energy consumption is achieved. Moreover (<xref ref-type="bibr" rid="B14">Katsaros et&#x20;al., 2011</xref>), reported that an increase of GLOSA-equipped vehicles would enables reductions of energy consumption.</p>
</sec>
</sec>
<sec id="s5">
<title>5 Conclusion</title>
<p>The proposed hybrid ecosystem for C-ITSs has been implemented and tested for two use cases. For the CACC use case we perform a platoon with two vehicles equipped to support the three air interfaces: ITS-G5, LTE Uu and LTE PC5. Experimental results show that the best performance in terms of latency is achieved by the ITS-G5 solution proving the maturity of the technology. The other short range solution, based on LTE sidelink, was penalized by the strict requirement on the synchronization between modem and applications. Despite this penalty, the CACC platoon could guarantee string stability and keep the vehicle following smoothly with both technologies. The performance of the long range solution based on LTE Uu was significantly affected by the low coverage and the distance from the MEC; During the tests latency values above 100&#xa0;ms occurred, which resulted in fluctuations during the CACC platoon. However, a second session of measurements that were taken in another location closer to the MEC and with higher coverage, showed a significant improvement of the OTTl comparable to LTE PC; these results suggest that string stable platoons are achievable also with the long range solution. For the GLOSA use case we recorded the traffic broadcasted by three intelligent traffic lights to compare coverage and data efficiency of the short range and long range solutions based on ITS-G5 and LTE Uu respectively. Measurements show that the long range solution has the potential to improve GLOSA related KPIs and even improve the efficiency of the system when targeting single vehicles; however, the MQTT protocol becomes less efficient when more than four to six vehicles are involved.</p>
</sec>
</body>
<back>
<sec id="s6">
<title>Data Availability Statement</title>
<p>The datasets presented in this article are available from the&#x20;corresponding author on reasonable request. Requests to access the datasets should be directed to <email>b.cimoli@tue.nl</email>.</p>
</sec>
<sec id="s7">
<title>Author Contributions</title>
<p>BC, HX, VH, IP, and GK contributed and participated to the testing activities. BC and HX analyzed the data that was discussed among all authors as were the results. VH and IP developed the systems on the vehicles and GK contributed to set the mobile network connection. BC, HX, SR, HN, and IT wrote the manuscript. All authors read and approved the manuscript.</p>
</sec>
<sec id="s8">
<title>Funding</title>
<p>This work was carried out within the CONCORDA project, an action co-financed by the European Union under the Grant Agreement number INEA/CEF/TRAN/M2016/1364&#x2009;071.</p>
</sec>
<sec sec-type="COI-statement" id="s9">
<title>Conflict of Interest</title>
<p>GK was employed by the company KPN, IP and VH were employed by the company Siemens Industry Software Netherlands.</p>
<p>The remaining authors declare that the research was conducted in the absence of any commercial or financial relationships that could be construed as a potential conflict of interest.</p>
</sec>
<sec sec-type="disclaimer" id="s10">
<title>Publisher&#x2019;s Note</title>
<p>All claims expressed in this article are solely those of the authors and do not necessarily represent those of their affiliated organizations, or those of the publisher, the editors and the reviewers. Any product that may be evaluated in this article, or claim that may be made by its manufacturer, is not guaranteed or endorsed by the publisher.</p>
</sec>
<ack>
<p>The authors like to thank all CONCORDA project partners for their contributions to this&#x20;work.</p>
</ack>
<sec id="s11">
<title>Supplementary Material</title>
<p>The Supplementary Material for this article can be found online at: <ext-link ext-link-type="uri" xlink:href="https://www.frontiersin.org/articles/10.3389/ffutr.2022.742731/full#supplementary-material">https://www.frontiersin.org/articles/10.3389/ffutr.2022.742731/full&#x23;supplementary-material</ext-link>.</p>
<supplementary-material xlink:href="DataSheet1.ZIP" id="SM1" mimetype="application/ZIP" xmlns:xlink="http://www.w3.org/1999/xlink"/>
</sec>
<ref-list>
<title>References</title>
<ref id="B1">
<citation citation-type="journal">
<collab>5 GAA P-190033</collab> (<year>2019</year>). <article-title>V2x Functional and Performance Test Report; Test Procedures and Results</article-title>. <comment>Report</comment>. </citation>
</ref>
<ref id="B2">
<citation citation-type="book">
<collab>5 GAA Working Group1</collab> (<year>2019</year>). <source>C-V2X Use Cases Methodology, Examples and Service Level Requirements</source>. <comment>White paper</comment>. <comment>Available at: <ext-link ext-link-type="uri" xlink:href="https://5gaa.org/news/5gaa-releases-white-paper-on-c-v2x-use-cases-methodology-examples-and-service-level-requirements/">https://5gaa.org/news/5gaa-releases-white-paper-on-c-v2x-use-cases-methodology-examples-and-service-level-requirements/</ext-link>
</comment>. </citation>
</ref>
<ref id="B3">
<citation citation-type="book">
<collab>5 G-PPP</collab> (<year>2021</year>). <source>Service Performance Measurement Methods over 5G Experimental Networks</source>. <comment>White paper &#x2013; ICT-19 performance KPIs</comment>. <pub-id pub-id-type="doi">10.5281/zenodo.4748385</pub-id> </citation>
</ref>
<ref id="B4">
<citation citation-type="book">
<collab>Amsterdam Group</collab> (<year>2015</year>). <source>Signal Phase and Time (SPAT) and Map Data (MAP)</source>. <comment>ver 1.1 SPAT/MAP</comment>. <publisher-loc>Amsterdam, Netherlands</publisher-loc>: <publisher-name>Amsterdam Group Institution</publisher-name>. </citation>
</ref>
<ref id="B5">
<citation citation-type="book">
<collab>C-ITS Platform</collab> (<year>2018</year>). <source>C-ITS Platform Phase II: Certificate Policy for Deployment and Operation of European Cooperative Intelligent Transport Systems (C-ITS)</source>. <comment>Release 1.1</comment>. <publisher-name>European Commission&#x2019;s Communication</publisher-name>. </citation>
</ref>
<ref id="B6">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Dey</surname>
<given-names>K. C.</given-names>
</name>
<name>
<surname>Yan</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Shen</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Chowdhury</surname>
<given-names>M.</given-names>
</name>
<etal/>
</person-group> (<year>2016</year>). <article-title>A Review of Communication, Driver Characteristics, and Controls Aspects of Cooperative Adaptive Cruise Control (CACC)</article-title>. <source>IEEE Trans. Intell. Transport. Syst.</source> <volume>17</volume>, <fpage>491</fpage>&#x2013;<lpage>509</lpage>. <pub-id pub-id-type="doi">10.1109/TITS.2015.2483063</pub-id> </citation>
</ref>
<ref id="B7">
<citation citation-type="book">
<collab>ETSI EN 302&#x20;663</collab> (<year>2012</year>). <source>Intelligent Transport Systems (ITS); Access Layer Specification for Intelligent Transport Systems Operating in the 5 GHz Frequency Band</source>. <comment>V.1.2.0</comment>. <publisher-loc>France</publisher-loc>: <publisher-name>ETSI</publisher-name>. </citation>
</ref>
<ref id="B8">
<citation citation-type="book">
<collab>ETSI EN 302&#x20;665</collab> (<year>2010</year>). <source>Intelligent Transport Systems (ITS); Communications Architecture</source>. <comment>V1.1.1</comment>. <publisher-loc>France</publisher-loc>: <publisher-name>ETSI</publisher-name>. </citation>
</ref>
<ref id="B9">
<citation citation-type="book">
<collab>ETSI TS 303&#x20;613</collab> (<year>2020</year>). <source>Intelligent Transport Systems (Its); Lte-V2x Access Layer Specification for Intelligent Transport Systems Operating in the 5 Ghz Frequency Band</source>. <comment>V1.1.1</comment>. <publisher-loc>France</publisher-loc>: <publisher-name>ETSI</publisher-name>. </citation>
</ref>
<ref id="B10">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Giambene</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Rahman</surname>
<given-names>M. S.</given-names>
</name>
<name>
<surname>Vinel</surname>
<given-names>A.</given-names>
</name>
</person-group> (<year>2020</year>). &#x201c;<article-title>Analysis of V2V Sidelink Communications for Platoon Applications</article-title>,&#x201d; in <conf-name>IEEE International Conference on Communications (ICC)</conf-name>, <conf-loc>Dublin, Ireland</conf-loc>, <conf-date>7-11 June 2020</conf-date> (<publisher-loc>Dublin</publisher-loc>: <publisher-name>IEEE</publisher-name>). <pub-id pub-id-type="doi">10.1109/ICC40277.2020.9148968</pub-id> </citation>
</ref>
<ref id="B11">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Gonzalez</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Villamil</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Franchi</surname>
<given-names>N.</given-names>
</name>
<name>
<surname>Fettweis</surname>
<given-names>G.</given-names>
</name>
</person-group> (<year>2019</year>). &#x201c;<article-title>String Stable CACC under LTE-V2v Mode 3: Scheduling Periods and Transmission Delays</article-title>,&#x201d; in <conf-name>IEEE 5G World Forum (5GWF)</conf-name>, <conf-loc>Dresden, Germany</conf-loc>, <conf-date>30 Sept.-2 Oct. 2019</conf-date> (<publisher-name>IEEE</publisher-name>), <fpage>292</fpage>&#x2013;<lpage>297</lpage>. <pub-id pub-id-type="doi">10.1109/5GWF.2019.8911631</pub-id> </citation>
</ref>
<ref id="B12">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Hedrick</surname>
<given-names>J.&#x20;K.</given-names>
</name>
<name>
<surname>Tomizuka</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Varaiya</surname>
<given-names>P.</given-names>
</name>
</person-group> (<year>1994</year>). <article-title>Control Issues in Automated Highway Systems</article-title>. <source>IEEE Control. Syst.</source> <volume>14</volume>, <fpage>21</fpage>&#x2013;<lpage>32</lpage>. <pub-id pub-id-type="doi">10.1109/37.334412</pub-id> </citation>
</ref>
<ref id="B13">
<citation citation-type="book">
<collab>IEEE 802.11p</collab> (<year>2010</year>). <source>Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications Amendment 6: Wireless Access in Vehicular Environments</source>. <publisher-loc>New York, United States</publisher-loc>: <publisher-name>IEEE</publisher-name>. </citation>
</ref>
<ref id="B14">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Katsaros</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Kernchen</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Dianati</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Rieck</surname>
<given-names>D.</given-names>
</name>
</person-group> (<year>2011</year>). &#x201c;<article-title>Performance Study of a green Light Optimized Speed Advisory (GLOSA) Application Using an Integrated Cooperative ITS Simulation Platform</article-title>,&#x201d; in <conf-name>International Wireless Communications and Mobile Computing Conference (IWCMC)</conf-name>, <conf-loc>Istanbul, Turkey</conf-loc>, <conf-date>4-8 July 2011</conf-date> (<publisher-loc>Istanbul</publisher-loc>: <publisher-name>IEEE</publisher-name>). <pub-id pub-id-type="doi">10.1109/IWCMC.2011.5982524</pub-id> </citation>
</ref>
<ref id="B15">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Lei</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>van Eenennaam</surname>
<given-names>E. M.</given-names>
</name>
<name>
<surname>Wolterink</surname>
<given-names>W. K.</given-names>
</name>
<name>
<surname>Karagiannis</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Heijenk</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Ploeg</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2011</year>). &#x201c;<article-title>Impact of Packet Loss on CACC String Stability Performance</article-title>,&#x201d; in <conf-name>International Conference on ITS Telecommunications (ITST)</conf-name>, <conf-loc>St. Petersburg, Russia</conf-loc>, <conf-date>23-25 Aug. 2011</conf-date> (<publisher-loc>St. Petersburg</publisher-loc>: <publisher-name>IEEE</publisher-name>), <fpage>381</fpage>&#x2013;<lpage>386</lpage>. <pub-id pub-id-type="doi">10.1109/ITST.2011.6060086</pub-id> </citation>
</ref>
<ref id="B16">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Lianghai</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Weinand</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Han</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Schotten</surname>
<given-names>H. D.</given-names>
</name>
</person-group> (<year>2017</year>). &#x201c;<article-title>Feasibility Study of Enabling V2X Communications by LTE-Uu Radio Interface</article-title>,&#x201d; in <conf-name>International Conference on Communications in China (ICCC)</conf-name>, <conf-loc>Qingdao, China</conf-loc>, <conf-date>22-24 Oct. 2017</conf-date> (<publisher-loc>Qingdao</publisher-loc>: <publisher-name>IEEE</publisher-name>). <pub-id pub-id-type="doi">10.1109/iccchina.2017.8330349</pub-id> </citation>
</ref>
<ref id="B17">
<citation citation-type="web">
<collab>MathWorks</collab> (<year>2021</year>). <article-title>Parallel Hybrid Transmission</article-title>. <comment>Available at: <ext-link ext-link-type="uri" xlink:href="https://nl.mathworks.com/help/physmod/sdl/ug/parallel-hybrid-transmission.html">https://nl.mathworks.com/help/physmod/sdl/ug/parallel-hybrid-transmission.html</ext-link> (Accessed December 12, 2020)</comment>. </citation>
</ref>
<ref id="B18">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Nafi</surname>
<given-names>N. S.</given-names>
</name>
<name>
<surname>Khan</surname>
<given-names>R. H.</given-names>
</name>
<name>
<surname>Khan</surname>
<given-names>J.&#x20;Y.</given-names>
</name>
<name>
<surname>Gregory</surname>
<given-names>M.</given-names>
</name>
</person-group> (<year>2014</year>). &#x201c;<article-title>A Predictive Road Traffic Management System Based on Vehicular Ad-Hoc Network</article-title>,&#x201d; in <conf-name>Australasian Telecommunication Networks and Applications Conference (ATNAC)</conf-name>, <conf-loc>Southbank, VIC, Australia</conf-loc>, <conf-date>26-28 Nov. 2014</conf-date> (<publisher-loc>Melbourne</publisher-loc>: <publisher-name>IEEE</publisher-name>), <fpage>135</fpage>&#x2013;<lpage>140</lpage>. <pub-id pub-id-type="doi">10.1109/ATNAC.2014.7020887</pub-id> </citation>
</ref>
<ref id="B19">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Passchier</surname>
<given-names>I.</given-names>
</name>
<name>
<surname>Driessen</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Heijligers</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Netten</surname>
<given-names>B.</given-names>
</name>
</person-group> (<year>2011</year>). &#x201c;<article-title>The Road Side Unit for the A270 Test Site the Road Side Unit for the A270 Test Site</article-title>,&#x201d; in <conf-name>8th ITS European Congress</conf-name>, <conf-loc>Lyon, France</conf-loc> (<publisher-loc>Lyon</publisher-loc>: <publisher-name>TNO</publisher-name>), <fpage>1</fpage>&#x2013;<lpage>5</lpage>. </citation>
</ref>
<ref id="B20">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Passchier</surname>
<given-names>I.</given-names>
</name>
<name>
<surname>Van Vugt</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Tideman</surname>
<given-names>M.</given-names>
</name>
</person-group> (<year>2015</year>). &#x201c;<article-title>An Integral Approach to Autonomous and Cooperative Vehicles Development and Testing</article-title>,&#x201d; in <conf-name>IEEE 18th International Conference on Intelligent Transportation Systems</conf-name>, <conf-loc>Gran Canaria, Spain</conf-loc>, <conf-date>15-18 Sept. 2015</conf-date> (<publisher-loc>Gran Canaria</publisher-loc>: <publisher-name>IEEE</publisher-name>), <fpage>348</fpage>&#x2013;<lpage>352</lpage>. <pub-id pub-id-type="doi">10.1109/ITSC.2015.66</pub-id> </citation>
</ref>
<ref id="B21">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Ploeg</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Scheepers</surname>
<given-names>B. T.</given-names>
</name>
<name>
<surname>Van Nunen</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Van de Wouw</surname>
<given-names>N.</given-names>
</name>
<name>
<surname>Nijmeijer</surname>
<given-names>H.</given-names>
</name>
</person-group> (<year>2011</year>). &#x201c;<article-title>Design and Experimental Evaluation of Cooperative Adaptive Cruise Control</article-title>,&#x201d; in <conf-name>Int. IEEE Conf. Intell. Transp. Syst</conf-name>, <conf-loc>Washington, DC, USA</conf-loc>, <conf-date>5-7 Oct. 2011</conf-date> (<publisher-name>IEEE</publisher-name>), <fpage>260</fpage>&#x2013;<lpage>265</lpage>. <pub-id pub-id-type="doi">10.1109/itsc.2011.6082981</pub-id> </citation>
</ref>
<ref id="B22">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Pyyk&#xf6;nen</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Lumiaho</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Kutila</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Scholliers</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Kakes</surname>
<given-names>G.</given-names>
</name>
</person-group> (<year>2020</year>). &#x201c;<article-title>V2X-supported Automated Driving in Modern 4G Networks</article-title>,&#x201d; in <conf-name>International Conference on Intelligent Computer Communication and Processing (ICCP)</conf-name>, <conf-loc>Cluj-Napoca, Romania</conf-loc>, <conf-date>3-5 Sept. 2020</conf-date> (<publisher-loc>Cluj-Napoca</publisher-loc>: <publisher-name>IEEE</publisher-name>). <pub-id pub-id-type="doi">10.1109/ICCP51029.2020.9266189</pub-id> </citation>
</ref>
<ref id="B23">
<citation citation-type="web">
<collab>RDW</collab> (<year>2021</year>). <article-title>RDW Testcentrum</article-title>. <comment>Available at: <ext-link ext-link-type="uri" xlink:href="https://www.rdw.nl/zakelijk/branches/fabrikanten-en-importeurs/typegoedkeuring-aanvragen/testen/rdw-testcentrum">https://www.rdw.nl/zakelijk/branches/fabrikanten-en-importeurs/typegoedkeuring-aanvragen/testen/rdw-testcentrum</ext-link>
</comment>. </citation>
</ref>
<ref id="B24">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Santa</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Pere&#xf1;&#xed;guez</surname>
<given-names>F.</given-names>
</name>
<name>
<surname>Morag&#xf3;n</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Skarmeta</surname>
<given-names>A. F.</given-names>
</name>
</person-group> (<year>2014</year>). <article-title>Experimental Evaluation of CAM and DENM Messaging Services in Vehicular Communications</article-title>. <source>Transportation Res. C: Emerging Tech.</source> <volume>46</volume>, <fpage>98</fpage>&#x2013;<lpage>120</lpage>. <pub-id pub-id-type="doi">10.1016/j.trc.2014.05.006</pub-id> </citation>
</ref>
<ref id="B25">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>van de Sluis</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Baijer</surname>
<given-names>O.</given-names>
</name>
<name>
<surname>Chen</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Bengtsson</surname>
<given-names>H. H.</given-names>
</name>
<name>
<surname>Garcia-Sol</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Balaguer</surname>
<given-names>P.</given-names>
</name>
</person-group> (<year>2015</year>). <source>I-GAME D3.2: Proposal for Extended Message Set for Supervised Automated Driving</source>. <publisher-name>European Commission</publisher-name>. </citation>
</ref>
<ref id="B26">
<citation citation-type="book">
<collab>World Health Organization</collab> (<year>2018</year>). <source>Global Status Report on Road Safety 2018</source>. <publisher-loc>Geneva, Switzerland</publisher-loc>: <publisher-name>World Health Organization</publisher-name>. </citation>
</ref>
<ref id="B27">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Xing</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Ploeg</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Nijmeijer</surname>
<given-names>H.</given-names>
</name>
</person-group> (<year>2019</year>). <article-title>Compensation of Communication Delays in a Cooperative ACC System</article-title>. <source>IEEE Trans. Veh. Tech.</source> <volume>69</volume>, <fpage>1177</fpage>&#x2013;<lpage>1189</lpage>. <pub-id pub-id-type="doi">10.1109/TVT.2019.2960114</pub-id> </citation>
</ref>
<ref id="B28">
<citation citation-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Xing</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Cimoli</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Passchier</surname>
<given-names>I.</given-names>
</name>
<name>
<surname>Kakes</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Ho</surname>
<given-names>V.</given-names>
</name>
<name>
<surname>Nijmeijer</surname>
<given-names>H.</given-names>
</name>
</person-group> (<year>2021</year>). &#x201c;<article-title>Practical Challenges in CACC Communication: ITS G5, LTE Uu, and LTE Sidelink PC5</article-title>,&#x201d; in <conf-name>European Control Conference (ECC)</conf-name>, <conf-loc>Delft, Netherlands</conf-loc>, <conf-date>29&#x20;June-2 July 2021</conf-date>. <pub-id pub-id-type="doi">10.23919/ecc54610.2021.9655171</pub-id> </citation>
</ref>
</ref-list>
</back>
</article>