<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
    <record>
        <controlfield tag="001">48370</controlfield>
        <controlfield tag="005">20200221144341.0</controlfield>
        <datafield tag="024" ind1="7" ind2=" ">
            <subfield code="2">doi</subfield>
            <subfield code="a">10.1155/2016/8320756</subfield>
        </datafield>
        <datafield tag="024" ind1="8" ind2=" ">
            <subfield code="2">sideral</subfield>
            <subfield code="a">94100</subfield>
        </datafield>
        <datafield tag="037" ind1=" " ind2=" ">
            <subfield code="a">ART-2016-94100</subfield>
        </datafield>
        <datafield tag="041" ind1=" " ind2=" ">
            <subfield code="a">eng</subfield>
        </datafield>
        <datafield tag="100" ind1=" " ind2=" ">
            <subfield code="0">(orcid)0000-0001-7657-0075</subfield>
            <subfield code="a">Sanguesa, J.A.</subfield>
        </datafield>
        <datafield tag="245" ind1=" " ind2=" ">
            <subfield code="a">On the Study of Vehicle Density in Intelligent Transportation Systems</subfield>
        </datafield>
        <datafield tag="260" ind1=" " ind2=" ">
            <subfield code="c">2016</subfield>
        </datafield>
        <datafield tag="506" ind1="0" ind2=" ">
            <subfield code="a">Access copy available to the general public</subfield>
            <subfield code="f">Unrestricted</subfield>
        </datafield>
        <datafield tag="520" ind1="3" ind2=" ">
            <subfield code="a">Vehicular ad hoc networks (VANETs) are wireless communication networks which support cooperative driving among vehicles on the road. The specific characteristics of VANETs favor the development of attractive and challenging services and applications which rely on message exchanging among vehicles. These communication capabilities depend directly on the existence of nearby vehicles able to exchange information. Therefore, higher vehicle densities favor the communication among vehicles. However, vehicular communications are also strongly affected by the topology of the map (i.e., wireless signal could be attenuated due to the distance between the sender and receiver, and obstacles usually block signal transmission). In this paper, we study the influence of the roadmap topology and the number of vehicles when accounting for the vehicular communications capabilities, especially in urban scenarios. Additionally, we consider the use of two parameters: the SJ Ratio (SJR) and the Total Distance (TD), as the topology-related factors that better correlate with communications performance. Finally, we propose the use of a new density metric based on the number of vehicles, the complexity of the roadmap, and its maximum capacity. Hence, researchers will be able to accurately characterize the different urban scenarios and better validate their proposals related to cooperative Intelligent Transportation Systems based on vehicular communications.</subfield>
        </datafield>
        <datafield tag="536" ind1=" " ind2=" ">
            <subfield code="9">info:eu-repo/grantAgreement/ES/MINECO/TEC2014-52690-R</subfield>
        </datafield>
        <datafield tag="540" ind1=" " ind2=" ">
            <subfield code="9">info:eu-repo/semantics/openAccess</subfield>
            <subfield code="a">by</subfield>
            <subfield code="u">http://creativecommons.org/licenses/by/3.0/es/</subfield>
        </datafield>
        <datafield tag="590" ind1=" " ind2=" ">
            <subfield code="a">0.849</subfield>
            <subfield code="b">2016</subfield>
        </datafield>
        <datafield tag="591" ind1=" " ind2=" ">
            <subfield code="a">TELECOMMUNICATIONS</subfield>
            <subfield code="b">79 / 89 = 0.888</subfield>
            <subfield code="c">2016</subfield>
            <subfield code="d">Q4</subfield>
            <subfield code="e">T3</subfield>
        </datafield>
        <datafield tag="591" ind1=" " ind2=" ">
            <subfield code="a">COMPUTER SCIENCE, INFORMATION SYSTEMS</subfield>
            <subfield code="b">121 / 146 = 0.829</subfield>
            <subfield code="c">2016</subfield>
            <subfield code="d">Q4</subfield>
            <subfield code="e">T3</subfield>
        </datafield>
        <datafield tag="592" ind1=" " ind2=" ">
            <subfield code="a">0.207</subfield>
            <subfield code="b">2016</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Computer Networks and Communications</subfield>
            <subfield code="c">2016</subfield>
            <subfield code="d">Q3</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Computer Science Applications</subfield>
            <subfield code="c">2016</subfield>
            <subfield code="d">Q4</subfield>
        </datafield>
        <datafield tag="655" ind1=" " ind2="4">
            <subfield code="a">info:eu-repo/semantics/article</subfield>
            <subfield code="v">info:eu-repo/semantics/publishedVersion</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="0">(orcid)0000-0001-5664-6589</subfield>
            <subfield code="a">Naranjo, F.</subfield>
            <subfield code="u">Universidad de Zaragoza</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="a">Torres-Sanz, V.</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="0">(orcid)0000-0003-1044-7335</subfield>
            <subfield code="a">Fogue, M.</subfield>
            <subfield code="u">Universidad de Zaragoza</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="0">(orcid)0000-0002-1750-7225</subfield>
            <subfield code="a">Garrido, P.</subfield>
            <subfield code="u">Universidad de Zaragoza</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="0">(orcid)0000-0001-6945-7330</subfield>
            <subfield code="a">Martinez, F.J.</subfield>
            <subfield code="u">Universidad de Zaragoza</subfield>
        </datafield>
        <datafield tag="710" ind1="2" ind2=" ">
            <subfield code="1">5007</subfield>
            <subfield code="2">035</subfield>
            <subfield code="a">Universidad de Zaragoza</subfield>
            <subfield code="b">Dpto. Informát.Ingenie.Sistms.</subfield>
            <subfield code="c">Área Arquit.Tecnología Comput.</subfield>
        </datafield>
        <datafield tag="710" ind1="2" ind2=" ">
            <subfield code="1">5007</subfield>
            <subfield code="2">570</subfield>
            <subfield code="a">Universidad de Zaragoza</subfield>
            <subfield code="b">Dpto. Informát.Ingenie.Sistms.</subfield>
            <subfield code="c">Área Lenguajes y Sistemas Inf.</subfield>
        </datafield>
        <datafield tag="773" ind1=" " ind2=" ">
            <subfield code="g">2016 (2016), 8320756[13 p]</subfield>
            <subfield code="p">Mobile Information Systems</subfield>
            <subfield code="t">Mobile Information Systems</subfield>
            <subfield code="x">1574-017X</subfield>
        </datafield>
        <datafield tag="856" ind1="4" ind2=" ">
            <subfield code="s">3069012</subfield>
            <subfield code="u">http://zaguan.unizar.es/record/48370/files/texto_completo.pdf</subfield>
            <subfield code="y">Versión publicada</subfield>
        </datafield>
        <datafield tag="856" ind1="4" ind2=" ">
            <subfield code="s">95557</subfield>
            <subfield code="u">http://zaguan.unizar.es/record/48370/files/texto_completo.jpg?subformat=icon</subfield>
            <subfield code="x">icon</subfield>
            <subfield code="y">Versión publicada</subfield>
        </datafield>
        <datafield tag="909" ind1="C" ind2="O">
            <subfield code="o">oai:zaguan.unizar.es:48370</subfield>
            <subfield code="p">articulos</subfield>
            <subfield code="p">driver</subfield>
        </datafield>
        <datafield tag="951" ind1=" " ind2=" ">
            <subfield code="a">2020-02-21-13:50:15</subfield>
        </datafield>
        <datafield tag="980" ind1=" " ind2=" ">
            <subfield code="a">ARTICLE</subfield>
        </datafield>
    </record>

    
</collection>