<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article  PUBLIC "-//NLM//DTD Journal Publishing DTD v3.0 20080202//EN" "http://dtd.nlm.nih.gov/publishing/3.0/journalpublishing3.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="3.0" xml:lang="en" article-type="research article"><front><journal-meta><journal-id journal-id-type="publisher-id">JTTs</journal-id><journal-title-group><journal-title>Journal of Transportation Technologies</journal-title></journal-title-group><issn pub-type="epub">2160-0473</issn><publisher><publisher-name>Scientific Research Publishing</publisher-name></publisher></journal-meta><article-meta><article-id pub-id-type="doi">10.4236/jtts.2015.52011</article-id><article-id pub-id-type="publisher-id">JTTs-55509</article-id><article-categories><subj-group subj-group-type="heading"><subject>Articles</subject></subj-group><subj-group subj-group-type="Discipline-v2"><subject>Engineering</subject></subj-group></article-categories><title-group><article-title>
 
 
  A Robust Multi-RAT VANET/LTE for Mixed Control &amp; Entertainment Traffic
 
</article-title></title-group><contrib-group><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>oha</surname><given-names>M. Sadek</given-names></name><xref ref-type="aff" rid="aff1"><sup>1</sup></xref><xref ref-type="corresp" rid="cor1"><sup>*</sup></xref></contrib><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Hassan</surname><given-names>H. Halawa</given-names></name><xref ref-type="aff" rid="aff1"><sup>1</sup></xref><xref ref-type="corresp" rid="cor1"><sup>*</sup></xref></contrib><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Ramez</surname><given-names>M. Daoud</given-names></name><xref ref-type="aff" rid="aff1"><sup>1</sup></xref><xref ref-type="corresp" rid="cor1"><sup>*</sup></xref></contrib><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Hassanein</surname><given-names>H. Amer</given-names></name><xref ref-type="aff" rid="aff1"><sup>1</sup></xref><xref ref-type="corresp" rid="cor1"><sup>*</sup></xref></contrib></contrib-group><aff id="aff1"><addr-line>Electronics and Communications Engineering Department, American University in Cairo, Cairo, Egypt</addr-line></aff><author-notes><corresp id="cor1">* E-mail:<email>nohams@yahoo.com(OMS)</email>;<email>hhhalawa@ieee.org(HHH)</email>;<email>rdaoud@ieee.org(RMD)</email>;<email>hamer@aucegypt.edu(HHA)</email>;</corresp></author-notes><pub-date pub-type="epub"><day>18</day><month>03</month><year>2015</year></pub-date><volume>05</volume><issue>02</issue><fpage>113</fpage><lpage>121</lpage><history><date date-type="received"><day>5</day>	<month>March</month>	<year>2015</year></date><date date-type="rev-recd"><day>accepted</day>	<month>8</month>	<year>April</year>	</date><date date-type="accepted"><day>10</day>	<month>April</month>	<year>2015</year></date></history><permissions><copyright-statement>&#169; Copyright  2014 by authors and Scientific Research Publishing Inc. </copyright-statement><copyright-year>2014</copyright-year><license><license-p>This work is licensed under the Creative Commons Attribution International License (CC BY). http://creativecommons.org/licenses/by/4.0/</license-p></license></permissions><abstract><p>
 
 
  Intelligent Transportation Systems (ITS) have been receiving significant interest from various stakeholders worldwide. ITS promise major enhancements to the efficiency, safety, convenience and sustainability of transportation systems. To satisfy the diverse vehicular application requirements, this paper proposes an integration of IEEE 802.11-based VANET and LTE cellular network using mobile vehicular gateways. IEEE 802.11 g is used for V2V communications and LTE for V2I communications. A burst communication technique is applied to prevent packet losses in the critical uplink ITS traffic. A performance simulation-based study is conducted to validate the feasibility of the proposed system in an urban vehicular environment. The system performance is evaluated in terms of data loss, data rate, delay and jitter. The results indicate that the proposed Multi-RAT system offers acceptable performance that meets the requirements of the different vehicular applications.
 
</p></abstract><kwd-group><kwd>Heterogeneous Networks</kwd><kwd> Intelligent Transportation Systems</kwd><kwd> Vehicular Networks</kwd><kwd> VANET</kwd><kwd> LTE</kwd><kwd> Wi-Fi</kwd></kwd-group></article-meta></front><body><sec id="s1"><title>1. Introduction</title><p>Intelligent Transportation Systems (ITS) have been receiving significant interest from various stakeholders worldwide. Automotive companies, governmental entities, standardization organizations and the research community are all focusing on the design and deployment of ITS. ITS promise major enhancements to the efficiency, safety, convenience and sustainability of transportation systems. Specifically, ITS aim at improving road safety, alleviating urban traffic congestion and offering ubiquitous Internet access for passengers [<xref ref-type="bibr" rid="scirp.55509-ref1">1</xref>] .</p><p>Vehicular networks are believed to play a crucial role in future ITS due to the wide variety of services that they can offer. Vehicular network applications can be broadly classified into 3 main categories, namely active road safety, traffic efficiency and management, and infotainment applications [<xref ref-type="bibr" rid="scirp.55509-ref2">2</xref>] . Safety applications are the first type of applications that aim at enhancing passengers’ safety on the roads by notifying vehicles about dangerous incidents in their vicinity. This can be accomplished by exchanging information like vehicle speed, position and distance heading between vehicles and the infrastructure, which is then used to predict and avoid risky situations [<xref ref-type="bibr" rid="scirp.55509-ref3">3</xref>] .</p><p>Besides safety applications, vehicular networks also support traffic efficiency and management applications. The primary objective of applications in this category is to improve traffic flow and enhance traffic coordination and management. Drivers can avoid congestion and find the most efficient route to their destinations with minimum delay. Additionally, vehicular traffic on the streets will be balanced which will lead to efficient use of the capacity of streets and junctions. This will in turn result in energy savings, pollution reduction and a decrease in travel time. The third type of vehicular applications is infotainment applications, also called comfort or entertainment applications. This class of applications provides information that delivers global Internet services and enhances the passengers’ comfort, convenience and entertainment.</p><p>In summary, vehicular applications enable the gathering and dissemination of information among vehicles (V2V), and between transportation infrastructure and vehicles (V2I) with the goal of assisting passengers to travel safely, efficiently and conveniently. Reliability, mobility support and low-latency are thus critical to satisfy the performance requirements of the different vehicular applications. On one side of the spectrum, infotainment applications have high-bandwidth demands and QoS-sensitive requirements [<xref ref-type="bibr" rid="scirp.55509-ref4">4</xref>] . While, on the other side of the spectrum, safety-critical applications are characterized by low latency and high message delivery rate. To support safety application demands, a large amount of data traffic needs to be exchanged between vehicles and Base Stations (BSs). This will consequently add a heavy burden to the BSs, which is not likely to be accepted by network operators. Additionally, these extra traffic connections increase the effect of interference and thus increase data error rate. Moreover, this also causes an increase in packet delays due to resource depletion. Furthermore, the scheduler at the BS may have difficulties scheduling transmissions within the tight delay bounds required for safety-critical applications [<xref ref-type="bibr" rid="scirp.55509-ref5">5</xref>] .</p><p>To cater to the diverse vehicular application requirements, this paper proposes an integration of IEEE 802.11- based VANET and LTE cellular network using mobile vehicular gateways. The proposed heterogeneous vehicular network combines two technologies with long-range and short-range coverage, namely LTE and Wi-Fi (IEEE 802.11) respectively. Each technology has a different objective and their integrated deployment will improve the vehicular system performance. On one hand, Wi-Fi offers a relatively high capacity at a very low cost and it has a high market penetration. However, it has a low coverage range compared to LTE. This makes it suitable for use as an access network inside the vehicle and for V2V communication between nearby vehicles. On the other hand, LTE offers a wide coverage and better Quality of Service (QoS) but, it requires costly licensed spectrum and is lacking behind Wi-Fi in terms of economies of scale [<xref ref-type="bibr" rid="scirp.55509-ref6">6</xref>] . These characteristics fit with the long range communication requirements of the V2I backhaul network. By integrating Wi-Fi with LTE, high capacity is coupled with long-range communication to improve the overall performance of the vehicular system. IEEE 802.11 g (Wi-Fi) has been selected because of its popularity and low cost. It offers users a uniform and mass-standard connectivity as the same standard is widely used in various parts of cities like hot-spots, tourist centers and information points [<xref ref-type="bibr" rid="scirp.55509-ref7">7</xref>] .</p><p>In the proposed heterogeneous network, there are mainly two types of vehicles: Gateway Vehicles (GVs) and Ordinary Vehicles (OVs). GVs are equipped with both LTE and Wi-Fi interfaces while OVs are only Wi-Fi enabled. A GV can be connected to two networks simultaneously: the LTE network using its E-UTRAN interface and to other OVs through its Wi-Fi interface. The GV can thus serve as a mobile gateway (i.e., relay node) for other OVs in its vicinity to access the LTE network. This can be accomplished by receiving data from OVs (using the Wi-Fi interface) and relaying it to the LTE network (via the LTE interface). OPNET Modeler [<xref ref-type="bibr" rid="scirp.55509-ref8">8</xref>] is used for the design, implementation and evaluation of the proposed network model.</p><p>The rest of the paper is organized as follows. Section 2 provides a background about vehicular networking research. Section 3 describes the proposed architecture. Section 4 presents the results and performance evaluation of the proposed architecture. Finally, the paper is concluded in Section 5.</p></sec><sec id="s2"><title>2. Background</title><p>This section presents some studies that evaluated the feasibility of using IEEE 802.11 and cellular networks to support vehicular networking applications.</p><p>In [<xref ref-type="bibr" rid="scirp.55509-ref9">9</xref>] , an attempt was made to solve the traffic control problem in an urban environment using Wi-Fi where a burst communication technique was used to eliminate packet losses. The authors in [<xref ref-type="bibr" rid="scirp.55509-ref10">10</xref>] proposed a heterogeneous LTE/Wi-Fi vehicular system that supports both infotainment and ITS traffic control data. Other studies ( [<xref ref-type="bibr" rid="scirp.55509-ref1">1</xref>] [<xref ref-type="bibr" rid="scirp.55509-ref5">5</xref>] [<xref ref-type="bibr" rid="scirp.55509-ref11">11</xref>] - [<xref ref-type="bibr" rid="scirp.55509-ref14">14</xref>] ) evaluated the performance of heterogeneous LTE-VANET (Vehicle Ad-hoc Networks) networks, where LTE was the backhaul network and VANET was used for inter-vehicle communication. In [<xref ref-type="bibr" rid="scirp.55509-ref5">5</xref>] , LTE was used to exchange Cooperative Awareness Messages (CAMs) between clusters while, Wi-Fi delivered in-cluster information. Reference [<xref ref-type="bibr" rid="scirp.55509-ref11">11</xref>] envisioned a heterogeneous LTE/IEEE 802.11p network that provides multimedia communication services over spatially apart vehicular groups and a cluster head election mechanism was proposed. A cooperative protocol based on coalition game theory was introduced in [<xref ref-type="bibr" rid="scirp.55509-ref12">12</xref>] to disseminate data in LTE/VANET network. Reference [<xref ref-type="bibr" rid="scirp.55509-ref13">13</xref>] investigated the delivery of real-time streaming of scalable video coded (SVC) video over vehicle-to-infrastructure (V2I) links. The inter-vehicles to infrastructure (V2V2I) model considered in [<xref ref-type="bibr" rid="scirp.55509-ref1">1</xref>] again used IEEE 802.11p for V2V communications and LTE for V2I communications. In [<xref ref-type="bibr" rid="scirp.55509-ref14">14</xref>] , the LTE network was used as a cluster management infrastructure for the IEEE 802.11p VANET. The performance was compared with the decentralized VANET architecture for an urban sensing application. Many of the studies in the field of vehicular communications only investigate a single type of application and either cover V2I or V2V communication only. The simultaneous support of safety, traffic and infotainment applications using both V2I and V2V communication has not been addressed in the literature. Accordingly, this perspective will be investigated in this study.</p></sec><sec id="s3"><title>3. Proposed Model</title><sec id="s3_1"><title>3.1. Network Architecture</title><p>The envisioned WiFi-based VANET-LTE heterogeneous network architecture is shown in <xref ref-type="fig" rid="fig1">Figure 1</xref>. Vehicles that are equipped with both LTE and Wi-Fi interfaces are referred to as Gateway Vehicles (GVs) whereas, only Wi-Fi is supported on-board Ordinary Vehicles (OVs). A GV is under the coverage region of at least one LTE eNodeB, and its LTE and Wi-Fi interfaces are both activated. On the other hand, an OV either lacks an LTE interface or is not present in an LTE coverage area. In other words, it is assumed that the LTE interface is either absent or disabled on OVs.</p><fig id="fig1"  position="float"><label><xref ref-type="fig" rid="fig1">Figure 1</xref></label><caption><title> VANET-LTE network architecture</title></caption><graphic mimetype="image"   position="float"  xlink:type="simple"  xlink:href="http://html.scirp.org/file/6-3500233x5.png"/></fig><p>This paper builds on the model introduced in [<xref ref-type="bibr" rid="scirp.55509-ref10">10</xref>] which consists of seven cells arranged in a hexagonal honey-cell layout where each cell is covered by one eNodeB. The vehicles are modeled moving in a radial path between the 7 cells in an urban traffic model where vehicles move at the maximum speed of 60 Km/hr. The proposed architecture divides the vehicular network into Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure (V2I), On-board Vehicle Communication (OVC), and backhaul connection. The V2V network allows communication between GVs and OVs through Wi-Fi. The V2I network between the vehicle and LTE eNodeB provides access to the LTE core network. The OVC network consists of a Wi-Fi Access Point (AP), passengers’ devices and a vehicular OnBoard Unit (OBU) for ITS data. In this scenario, LTE is the backhaul link used to access the Internet and the connectivity is shared to vehicular users using Wi-Fi as the last mile link. The LTE backhaul links are full duplex. Typically, an LTE eNodeB is deployed alongside the road and the vehicles are under the coverage of the different eNodeBs. More details about the system architecture can be found in [<xref ref-type="bibr" rid="scirp.55509-ref10">10</xref>] .</p><p>From the data flow perspective, GVs sample and gather the information from OVs (through Wi-Fi) then, in turn send periodically the relevant data to the infrastructure (via LTE). Data is exchanged between the GVs and LTE eNodeBs in both the downlink and uplink directions. On the downlink, LTE eNodeBs unicast the data to the GVs where both ITS and infotainment traffic are sent over the LTE link yet, they are routed differently inside the vehicle based on the intended destination. ITS data is sent to the vehicle’s OBU via Ethernet for further processing and decision making. On the other hand, infotainment traffic is sent to the passengers’ devices through Wi-Fi. On the uplink, GVs forward the traffic data (collected from OVs) to the LTE infrastructure at a pre-determined transmission rate.</p><p>In order to reduce the amount of traffic exchanged between vehicles and eNodeBs, a clustering strategy is employed. The GV is the cluster head which maintains the status of the cluster. Only the LTE-enabled cluster head is allowed to receive/transmit data from/to eNodeBs through LTE interfaces. Every OV transmits small data packets called Cooperative Awareness Messages (CAMs) to their corresponding cluster head/GV, providing state information such as speed or location. Such CAMs are transmitted every 100 ms [<xref ref-type="bibr" rid="scirp.55509-ref5">5</xref>] . It is considered that the vehicle clusters are already formed and that in each cluster, vehicles are moving together across all seven cells along the trajectory described in [<xref ref-type="bibr" rid="scirp.55509-ref10">10</xref>] . Thus, cluster members can be assumed not to vary throughout the journey. A single cluster of vehicles consists of 1 GV and 5 OVs.</p></sec><sec id="s3_2"><title>3.2. Simulation Parameters</title><p>The network model is simulated using OPNET Modeler [<xref ref-type="bibr" rid="scirp.55509-ref8">8</xref>] network simulator. The various network configuration parameters are shown in <xref ref-type="table" rid="table1">Table 1</xref>. eNodeB, GV LTE and downlink ITS parameters are all obtained from the model explained in [<xref ref-type="bibr" rid="scirp.55509-ref10">10</xref>] . CAMs are transmitted from OVs to GV where CAM size is 40 Bytes and transmission interval is 100 ms [<xref ref-type="bibr" rid="scirp.55509-ref5">5</xref>] . GV then aggregates CAMs’ data (12000 Bytes) and sends it on the LTE uplink channel every 30 seconds. 33 simulation runs were performed with different random seeds in order to ensure statistical accuracy. It is important to note that all results presented in this paper are subjected to a 95% confidence analysis.</p></sec><sec id="s3_3"><title>3.3. Performance Evaluation Metrics</title><p>This section describes the performance evaluation metrics of the proposed model. The network performance is evaluated in terms of data rate, Data Loss Ratio (DLR), delay and jitter parameters, defined as follows:</p><p>・ Data Rate (in Bytes/sec) is defined as the sum of the data bytes received at the destination averaged over time.</p><p>・ Data Loss Ratio (DLR) is defined as the ratio between dropped packets that do not reach the destination and the total number of packets sent from the source to the destination.</p><p>・ Delay (in seconds) specifies the time elapsed between sending the request from the source and the reception of the response at the source. This metric serves as a measure of the average overall delay of the packets for a particular node.</p><p>・ Jitter (in seconds) is defined as the packet delay variation. This metric is calculated as the standard deviation of packet delay for all packets sent over the network for a particular node.</p></sec></sec><sec id="s4"><title>4. Simulation Results</title><p>In this paper, the overall system performance, as specified by the communication requirements imposed by</p><table-wrap id="table1" ><label><xref ref-type="table" rid="table1">Table 1</xref></label><caption><title> Simulation parameters</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >Parameter</th><th align="center" valign="middle" >Value</th></tr></thead><tr><td align="center" valign="middle"  colspan="2"  >eNodeB</td></tr><tr><td align="center" valign="middle" >Transmit Power</td><td align="center" valign="middle" >10 Watts</td></tr><tr><td align="center" valign="middle" >Antenna Gain</td><td align="center" valign="middle" >18 dBi</td></tr><tr><td align="center" valign="middle" >MIMO</td><td align="center" valign="middle" >2 &#215; 2</td></tr><tr><td align="center" valign="middle" >Bandwidth</td><td align="center" valign="middle" >10 MHz</td></tr><tr><td align="center" valign="middle" >Frequency Band</td><td align="center" valign="middle" >1.8 GHz</td></tr><tr><td align="center" valign="middle" >Rx Sensitivity</td><td align="center" valign="middle" >?123 dBi</td></tr><tr><td align="center" valign="middle" >Duplexing Technique</td><td align="center" valign="middle" >FDD</td></tr><tr><td align="center" valign="middle" >Cell Radius</td><td align="center" valign="middle" >1.5 Km</td></tr><tr><td align="center" valign="middle" >ISD</td><td align="center" valign="middle" >2.6 Km</td></tr><tr><td align="center" valign="middle" >Transmit Power</td><td align="center" valign="middle" >10 Watts</td></tr><tr><td align="center" valign="middle"  colspan="2"  >GV</td></tr><tr><td align="center" valign="middle" >Transmit Power</td><td align="center" valign="middle" >0.2 Watts</td></tr><tr><td align="center" valign="middle" >Antenna Gain</td><td align="center" valign="middle" >0 dBi</td></tr><tr><td align="center" valign="middle" >MIMO</td><td align="center" valign="middle" >1 &#215; 2</td></tr><tr><td align="center" valign="middle" >Rx Sensitivity</td><td align="center" valign="middle" >?106 dBi</td></tr><tr><td align="center" valign="middle" >Shadow Fading Standard Deviation</td><td align="center" valign="middle" >4 dB</td></tr><tr><td align="center" valign="middle" >Downlink ITS IPT</td><td align="center" valign="middle" >120 s</td></tr><tr><td align="center" valign="middle" >Downlink ITS Size</td><td align="center" valign="middle" >1024 Bytes</td></tr><tr><td align="center" valign="middle" >Uplink ITS IPT</td><td align="center" valign="middle" >30 s</td></tr><tr><td align="center" valign="middle" >Uplink ITS Size</td><td align="center" valign="middle" >12000 Bytes</td></tr><tr><td align="center" valign="middle"  colspan="2"  >OV</td></tr><tr><td align="center" valign="middle" >CAM Transmission Interval</td><td align="center" valign="middle" >100 ms</td></tr><tr><td align="center" valign="middle" >CAM Size</td><td align="center" valign="middle" >40 Bytes</td></tr></tbody></table></table-wrap><p>different types of vehicular networking applications, is investigated. For this purpose, the foremost emphasis is on evaluating the data loss, data rate, delay and jitter of vehicular V2V and V2I applications in a realistic urban simulation environment. For all presented scenarios, the aforementioned performance evaluation metrics (data rate, DLR, delay and jitter) were analyzed. A 95% confidence analysis was performed for all presented results.</p><sec id="s4_1"><title>4.1. No Burst Model</title><p>In a video streaming service environment, it is important to maintain the DLR threshold below 1% [<xref ref-type="bibr" rid="scirp.55509-ref15">15</xref>] [<xref ref-type="bibr" rid="scirp.55509-ref16">16</xref>] such that the QoS requirement of video streaming service users is satisfied. Additionally, the performance of video streaming depends greatly on delay and jitter. According to [<xref ref-type="bibr" rid="scirp.55509-ref17">17</xref>] , the maximum acceptable video packet delay is set to 150 ms and the maximum allowable jitter is 50 ms. For traffic control data, since most of the applications are time-critical, the end-to-end delay must be between 100 and 500 ms [<xref ref-type="bibr" rid="scirp.55509-ref18">18</xref>] .</p><p><xref ref-type="table" rid="table2">Table 2</xref> shows the results obtained for vehicular video, downlink and uplink ITS traffic. It can be seen that the maximum video streaming traffic delay is 12.94 ms, while the maximum jitter is 5.84 ms. For downlink ITS traffic, a maximum delay of 22.27 ms and jitter of 6.7 ms is observed. As for uplink ITS traffic, the maximum delay is 23.82 ms and the maximum jitter is 9.69 ms. The obtained values are all below the above-mentioned benchmarks for ITS applications. It can be noted that the DLR for uplink traffic is 1.73%.</p><p><xref ref-type="fig" rid="fig2">Figure 2</xref> shows two packet losses in the uplink data traffic; one of them happens when the GV is in LTE cell 1 while the other one is in LTE cell 2. Due to the criticality of the safety-related information communicated in the uplink direction, a zero DLR is desired. So, in the next section, a burst recovery technique will be proposed to mitigate data losses in uplink ITS traffic.</p><p>The Wi-Fi V2V traffic results are presented in <xref ref-type="table" rid="table3">Table 3</xref>. Worst case values are considered where the DLR, delay and jitter values represent the upper bound of the resulting confidence interval. No data drops were reported for any of the OVs. In other words, all V2V data was successfully received by the GV via Wi-Fi. Additionally, the obtained delay values are far below the 100 ms constraint of the CAM V2V communication.</p></sec><sec id="s4_2"><title>4.2. Burst Recovery Mechanism</title><p>Burst is a communication technique used to reduce or prevent data losses in wireless communication systems. This is accomplished by sending successive identical packets within a certain time frame and separated by a pre-defined period of time. In essence, if one of the original packets is lost, the other redundant packets will still carry the same information to the desired destination.</p><p>There are basically 3 parameters that characterize burst communication, namely T<sub>packet</sub>, T<sub>F2L</sub> and T<sub>burst</sub> [<xref ref-type="bibr" rid="scirp.55509-ref9">9</xref>] . T<sub>packet</sub> is the time between two successive packets within the same burst. T<sub>F2L</sub> is the time between the first and the last packet in the same burst. Finally, T<sub>burst</sub> is the time between the first packets of two successive bursts.</p><p>T<sub>packet</sub> depends on the Inter-Packet Transmission Time (IPT) of the uplink traffic and on number of packets used in one burst, as follows:</p><table-wrap id="table2" ><label><xref ref-type="table" rid="table2">Table 2</xref></label><caption><title> Confidence results of video, downlink, and uplink ITS traffic―No burst model</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >Metric</th><th align="center" valign="middle" >Video</th><th align="center" valign="middle" >Downlink ITS</th><th align="center" valign="middle" >Uplink ITS</th></tr></thead><tr><td align="center" valign="middle" >Data Rate (Bytes/sec)</td><td align="center" valign="middle" >[124311.1; 124338.5]</td><td align="center" valign="middle" >[8.46; 8.56]</td><td align="center" valign="middle" >[393.07; 397.69]</td></tr><tr><td align="center" valign="middle" >DLR (%)</td><td align="center" valign="middle" >0.55%</td><td align="center" valign="middle" >0.8%</td><td align="center" valign="middle" >1.73%</td></tr><tr><td align="center" valign="middle" >Delay (ms)</td><td align="center" valign="middle" >[12.91; 12.94]</td><td align="center" valign="middle" >[20.97; 22.27]</td><td align="center" valign="middle" >[22.79; 23.82]</td></tr><tr><td align="center" valign="middle" >Jitter (ms)</td><td align="center" valign="middle" >[5.59; 5.84]</td><td align="center" valign="middle" >[4.48; 6.7]</td><td align="center" valign="middle" >[7.47; 9.69]</td></tr></tbody></table></table-wrap><table-wrap id="table3" ><label><xref ref-type="table" rid="table3">Table 3</xref></label><caption><title> Results of V2V traffic―No burst model</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >Metric</th><th align="center" valign="middle" >V2V OV1</th><th align="center" valign="middle" >V2V OV2</th><th align="center" valign="middle" >V2V OV3</th><th align="center" valign="middle" >V2V OV4</th><th align="center" valign="middle" >V2V OV5</th></tr></thead><tr><td align="center" valign="middle" >Data Rate (Bytes/sec)</td><td align="center" valign="middle" >400</td><td align="center" valign="middle" >400</td><td align="center" valign="middle" >400</td><td align="center" valign="middle" >400</td><td align="center" valign="middle" >400</td></tr><tr><td align="center" valign="middle" >DLR (%)</td><td align="center" valign="middle" >0%</td><td align="center" valign="middle" >0%</td><td align="center" valign="middle" >0%</td><td align="center" valign="middle" >0%</td><td align="center" valign="middle" >0%</td></tr><tr><td align="center" valign="middle" >Delay (ms)</td><td align="center" valign="middle" >0.790889</td><td align="center" valign="middle" >1.11316</td><td align="center" valign="middle" >1.407288</td><td align="center" valign="middle" >1.63815</td><td align="center" valign="middle" >0.4702</td></tr><tr><td align="center" valign="middle" >Jitter (ms)</td><td align="center" valign="middle" >0.443402</td><td align="center" valign="middle" >0.41698</td><td align="center" valign="middle" >0.387431</td><td align="center" valign="middle" >0.35542</td><td align="center" valign="middle" >0.41207</td></tr></tbody></table></table-wrap><fig id="fig2"  position="float"><label><xref ref-type="fig" rid="fig2">Figure 2</xref></label><caption><title> Uplink ITS traffic and LTE associated eNodeB</title></caption><graphic mimetype="image"   position="float"  xlink:type="simple"  xlink:href="http://html.scirp.org/file/6-3500233x6.png"/></fig><disp-formula id="scirp.55509-formula52"><label>(1)</label><graphic position="anchor" xlink:href="http://html.scirp.org/file/6-3500233x7.png"  xlink:type="simple"/></disp-formula><p>where IPT is the Inter-Packet Transmission Time of the uplink traffic and N<sub>burst</sub> is the number of packets per burst. T<sub>F</sub><sub>2L</sub> depends on the number of packets used in one burst and must satisfy the following constraint:</p><disp-formula id="scirp.55509-formula53"><label>(2)</label><graphic position="anchor" xlink:href="http://html.scirp.org/file/6-3500233x8.png"  xlink:type="simple"/></disp-formula><p>T<sub>burst</sub> must be less than or equal the IPT, which corresponds to the time needed for traffic and routing updates.</p><disp-formula id="scirp.55509-formula54"><label>(3)</label><graphic position="anchor" xlink:href="http://html.scirp.org/file/6-3500233x9.png"  xlink:type="simple"/></disp-formula><p>The minimum number of packets that can be used in one burst is two. A two-packet burst is studied to optimize the LTE channel utilization and minimize the network load. From Equation (1) and for a 30-sec uplink IPT, Tpacket must be smaller than or equal to 15 sec. In case of 2 packets per burst, T<sub>F</sub><sub>2L</sub> = T<sub>packet</sub> from Equation (2).</p><p><xref ref-type="fig" rid="fig3">Figure 3</xref> shows a typical burst communication for ITS uplink traffic. It is clear that two packets were lost from the original uplink traffic, however their burst replicas arrived successfully which indicates that no actual uplink ITS data was lost. <xref ref-type="table" rid="table4">Table 4</xref> shows the results obtained for vehicular video, downlink and uplink ITS traffic for the Burst model. <xref ref-type="table" rid="table5">Table 5</xref> shows Wi-Fi V2V traffic results for the Burst model. All received data, delay and jitter are within the acceptable limits of ITS applications.</p><fig id="fig3"  position="float"><label><xref ref-type="fig" rid="fig3">Figure 3</xref></label><caption><title> Uplink ITS traffic with Burst</title></caption><graphic mimetype="image"   position="float"  xlink:type="simple"  xlink:href="http://html.scirp.org/file/6-3500233x10.png"/></fig><table-wrap id="table4" ><label><xref ref-type="table" rid="table4">Table 4</xref></label><caption><title> Confidence results of video, downlink, and uplink ITS traffic―Burst model</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >Metric</th><th align="center" valign="middle" >Video</th><th align="center" valign="middle" >Downlink ITS</th><th align="center" valign="middle" >Uplink ITS</th></tr></thead><tr><td align="center" valign="middle" >Data Rate (Bytes/sec)</td><td align="center" valign="middle" >[124321.4; 124347.2]</td><td align="center" valign="middle" >[8.39; 8.54]</td><td align="center" valign="middle" >[393.08; 397.1]</td></tr><tr><td align="center" valign="middle" >DLR (%)</td><td align="center" valign="middle" >0.5%</td><td align="center" valign="middle" >1.8%</td><td align="center" valign="middle" >0%</td></tr><tr><td align="center" valign="middle" >Delay (ms)</td><td align="center" valign="middle" >[12.9; 12.93]</td><td align="center" valign="middle" >[21.52; 22.53]</td><td align="center" valign="middle" >[23.4; 24.36]</td></tr><tr><td align="center" valign="middle" >Jitter (ms)</td><td align="center" valign="middle" >[5.56; 5.66]</td><td align="center" valign="middle" >[5.32; 7.58]</td><td align="center" valign="middle" >[8.69; 11.13]</td></tr></tbody></table></table-wrap><table-wrap id="table5" ><label><xref ref-type="table" rid="table5">Table 5</xref></label><caption><title> Results of V2V traffic―Burst model</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >Metric</th><th align="center" valign="middle" >V2V OV1</th><th align="center" valign="middle" >V2V OV2</th><th align="center" valign="middle" >V2V OV3</th><th align="center" valign="middle" >V2V OV4</th><th align="center" valign="middle" >V2V OV5</th></tr></thead><tr><td align="center" valign="middle" >Data Rate (Bytes/sec)</td><td align="center" valign="middle" >400</td><td align="center" valign="middle" >400</td><td align="center" valign="middle" >400</td><td align="center" valign="middle" >400</td><td align="center" valign="middle" >400</td></tr><tr><td align="center" valign="middle" >DLR (%)</td><td align="center" valign="middle" >0%</td><td align="center" valign="middle" >0%</td><td align="center" valign="middle" >0%</td><td align="center" valign="middle" >0%</td><td align="center" valign="middle" >0%</td></tr><tr><td align="center" valign="middle" >Delay (ms)</td><td align="center" valign="middle" >0.79</td><td align="center" valign="middle" >1.113</td><td align="center" valign="middle" >1.406</td><td align="center" valign="middle" >1.637</td><td align="center" valign="middle" >0.47</td></tr><tr><td align="center" valign="middle" >Jitter (ms)</td><td align="center" valign="middle" >0.4436</td><td align="center" valign="middle" >0.4178</td><td align="center" valign="middle" >0.3867</td><td align="center" valign="middle" >0.3547</td><td align="center" valign="middle" >0.4119</td></tr></tbody></table></table-wrap><p>To conclude, the delay, jitter and data drops for both uplink and downlink ITS traffic, and video traffic are within the acceptable limits using the burst technique with only two packets per burst. The obtained simulation results thus show that the proposed system simultaneously satisfies vehicular and infotainment application requirements.</p></sec></sec><sec id="s5"><title>5. Conclusions</title><p>It is anticipated that ITS will play a vital future role in improving traffic efficiency, safety, comfort and emissions. Such systems rely on advanced mobile and wireless communication systems to satisfy the different vehicular applications’ requirements and to accommodate the increasing vehicles’ fleet. In this paper, an integrated IEEE802.11g-based VANET and LTE heterogeneous vehicular network was proposed where infotainment traffic was sent in addition to ITS control traffic in an urban vehicular environment. The system performance was evaluated in terms of data loss ratio, data rate, delay and jitter.</p><p>Data losses in uplink ITS data traffic were initially observed so, a Burst technique was proposed to prevent packet losses. A quantitative analysis was performed to determine the number of packets per burst, the inter- packet and inter-burst intervals. It was found that a substantial improvement was achieved using a two-packet Burst, where no packets were lost in the uplink direction. Additionally, for the given simulation scenario and network traffic load, it was shown that the proposed system meets both the video and ITS traffic application requirements. Thus, the feasibility of the proposed VANET-LTE heterogeneous system in urban vehicular environments was verified. Future work will focus on investigating more applications in the area of ITS.</p></sec></body><back><ref-list><title>References</title><ref id="scirp.55509-ref1"><label>1</label><mixed-citation publication-type="other" xlink:type="simple">Imadali, S., Kaiser, A., Decremps, S., Petrescu, A. and V&amp;egrave;que, V. (2013) V2V2I: Extended Inter-Vehicles to Infrastructure Communication Paradigm. IEEE 5th Global Information Infrastructure Symposium, Trento, Italy, October 2013.</mixed-citation></ref><ref id="scirp.55509-ref2"><label>2</label><mixed-citation publication-type="other" xlink:type="simple">Hossain, E., et al. (2010) Vehicular Telematics over Heterogeneous Wireless Networks: A Survey. Computer Communications, 33, 775-793.  
http://dx.doi.org/10.1016/j.comcom.2009.12.010</mixed-citation></ref><ref id="scirp.55509-ref3"><label>3</label><mixed-citation publication-type="other" xlink:type="simple">Karagiannis, G., et al. (2011) Vehicular Networking: A Survey and Tutorial on Requirements, Architectures, Challenges, Standards and Solutions. IEEE Communications Surveys &amp; Tutorials, 13, 584-616. 
http://dx.doi.org/10.1109/SURV.2011.061411.00019</mixed-citation></ref><ref id="scirp.55509-ref4"><label>4</label><mixed-citation publication-type="other" xlink:type="simple">Araniti, G., Campolo, C., Condoluci, M., Iera, A. and Molinaro, A. (2013) LTE for Vehicular Networking: A Survey. IEEE Communications Magazine, 51, 148-157.  
http://dx.doi.org/10.1109/MCOM.2013.6515060</mixed-citation></ref><ref id="scirp.55509-ref5"><label>5</label><mixed-citation publication-type="other" xlink:type="simple">Tung, L., Mena, J., Gerla, M. and Sommer, C. (2013) A Cluster Based Architecture for Intersection Collision Avoidance Using Heterogeneous Networks. 12th IFIP/IEEE Annual Mediterranean Ad Hoc Networking Workshop (Med-Hoc-Net), Cesson-Sevigne, France, June 2013.</mixed-citation></ref><ref id="scirp.55509-ref6"><label>6</label><mixed-citation publication-type="other" xlink:type="simple">Ghaleb, A., et al. (2013) Preservation of QOS across Hybrid LTE-WLAN Router. IET International Conference on Information and Communications Technologies (IETICT), Beijing, April 2013.</mixed-citation></ref><ref id="scirp.55509-ref7"><label>7</label><mixed-citation publication-type="other" xlink:type="simple">Barbu, G. (2010) E-TRAIN-Broadband Communication with Moving Trains, Technical Report—Technology State of the Art. International Union of Railways, Paris.</mixed-citation></ref><ref id="scirp.55509-ref8"><label>8</label><mixed-citation publication-type="other" xlink:type="simple">Official Site of OPNET:  
www.opnet.com</mixed-citation></ref><ref id="scirp.55509-ref9"><label>9</label><mixed-citation publication-type="other" xlink:type="simple">Daoud, R., EI-Dakroury, M., Elsayed, H., Amer, H. and EISoudani, M. (2007) WiFi Architecture for Traffic Control Using MIPv6. IEEE Mediterranean Conference on Control and Automation MED, Athens, 27-29 July 2007, 1-5.  
http://dx.doi.org/10.1109/MED.2007.4433921</mixed-citation></ref><ref id="scirp.55509-ref10"><label>10</label><mixed-citation publication-type="other" xlink:type="simple">Sadek, N., Halawa, H., Daoud, R., Amer, H. and Ali, N. (2015) Heterogeneous LTE/Wi-Fi Architecture for ITS Traffic Control and Infotainment. International Conference on Electrical Systems for Aircraft, Railway, Ship Propulsion and Road Vehicles, Aachen, March 2015.</mixed-citation></ref><ref id="scirp.55509-ref11"><label>11</label><mixed-citation publication-type="other" xlink:type="simple">Sivaraj, R., Gopalakrishna, A., Chandra, M. and Balamuralidhar, P. (2011) QoS-Enabled Group Communication in Integrated VANET-LTE Heterogeneous Wireless Networks. IEEE 7th International Conference on Wireless and Mobile Computing, Networking and Communications (WiMob), October 2011.</mixed-citation></ref><ref id="scirp.55509-ref12"><label>12</label><mixed-citation publication-type="other" xlink:type="simple">Li, Y., Ying, K., Cheng, P., Yu, H. and Luo, H. (2012) Cooperative Data Dissemination in Cellular-VANET Heterogeneous Wireless Networks. 4th International High Speed Intelligent Communication Forum (HSIC), Nanjing, May 2012.</mixed-citation></ref><ref id="scirp.55509-ref13"><label>13</label><mixed-citation publication-type="other" xlink:type="simple">Yaacoub, E., Filali, F. and Abu-Dayya, A. (2013) SVC Video Streaming over Cooperative LTE/802.11p Vehicle-to-Infrastructure Communications. IEEE World Congress on Computer and Information Technology (WCCIT), Tunis, June 2013.</mixed-citation></ref><ref id="scirp.55509-ref14"><label>14</label><mixed-citation publication-type="other" xlink:type="simple">Remy, G., Senouci, S., Jan, F. and Gourhant, Y. (2011) LTE4V2X: LTE for a Centralized VANET Organization. IEEE Global Telecommunications Conference (GLOBECOM), Houston, 5-9 December 2011, 1-6.  
http://dx.doi.org/10.1109/GLOCOM.2011.6133884</mixed-citation></ref><ref id="scirp.55509-ref15"><label>15</label><mixed-citation publication-type="other" xlink:type="simple">Islam, M. and Chowdhury, M. (2013) Study of Inter-Cell Interference and Its Impact on the Quality of Video Conference Traffic in LTE Network. M.Sc. Thesis, Blekinge Institute of Technology, Sweden.</mixed-citation></ref><ref id="scirp.55509-ref16"><label>16</label><mixed-citation publication-type="other" xlink:type="simple">Ramli, H., Basukala, R., Sandrasegaran, K. and Patachaianand, R. (2009) Performance of Well Known Packet Scheduling Algorithms in The Downlink 3GPP LTE system. IEEE 9th Malaysia International Conference on Communications (MICC), Kuala Lumpur, 15-17 December 2009, 815-820. http://dx.doi.org/10.1109/MICC.2009.5431383</mixed-citation></ref><ref id="scirp.55509-ref17"><label>17</label><mixed-citation publication-type="other" xlink:type="simple">International Telecommunication Union (ITU) (2008) Subjective Video Quality Assessment Methods for Multimedia Applications. Recommendation ITU-T P.910, Geneva.</mixed-citation></ref><ref id="scirp.55509-ref18"><label>18</label><mixed-citation publication-type="other" xlink:type="simple">Mir, Z. and Filali, F. (2014) LTE and IEEE 802.11p for Vehicular Networking: A Performance Evaluation. EURASIP Journal on Wireless Communications and Networking, 2014, 89.  
http://dx.doi.org/10.1186/1687-1499-2014-89</mixed-citation></ref></ref-list></back></article>