Vehicular ad hoc network

Source: Wikipedia, the free encyclopedia.
(Redirected from
Vehicle-to-vehicle
)

Vehicular ad hoc networks (VANETs) are created by applying the principles of

road safety
, navigation, and other roadside services. VANETs are a key part of the
intelligent transportation systems (ITS) framework. Sometimes, VANETs are referred as Intelligent Transportation Networks.[3] They are understood as having evolved into a broader "Internet of vehicles".[4] which itself is expected to ultimately evolve into an "Internet of autonomous vehicles".[5]

While, in the early 2000s, VANETs were seen as a mere one-to-one application of MANET principles, they have since then developed into a field of research in their own right. By 2015,[6]: 3  the term VANET became mostly synonymous with the more generic term inter-vehicle communication (IVC), although the focus remains on the aspect of spontaneous networking, much less on the use of infrastructure like Road Side Units (RSUs) or cellular networks.

VANETs are in development and are not in use by commercially available vehicles.[7]

Applications

VANETs support a wide range of applications – from simple one hop information dissemination of, e.g., cooperative awareness messages (CAMs) to multi-hop dissemination of messages over vast distances. Most of the concerns of interest to

mobile ad hoc networks (MANETs) are of interest in VANETs, but the details differ.[8]
Rather than moving at random, vehicles tend to move in an organized fashion. The interactions with roadside equipment can likewise be characterized fairly accurately. And finally, most vehicles are restricted in their range of motion, for example by being constrained to follow a paved highway.

Example applications of VANETs are:[6]: 56 

  • Electronic brake lights, which allow a driver (or an
    autonomous car
    or truck) to react to vehicles braking even though they might be obscured (e.g., by other vehicles).
  • Platooning, which allows vehicles to closely (down to a few inches) follow a leading vehicle by wirelessly receiving acceleration and steering information, thus forming electronically coupled "road trains".
  • satellite navigation system[9]
  • Road Transportation Emergency Services[10] – where VANET communications, VANET networks, and road safety warning and status information dissemination are used to reduce delays and speed up emergency rescue operations to save the lives of those injured.
  • On-The-Road Services[11] – it is also envisioned that the future transportation highway would be "information-driven" or "wirelessly-enabled". VANETs can help advertise services (shops, gas stations, restaurants, etc.) to the driver, and even send notifications of any sale going on at that moment.
  • Electronic Toll Collection[12] – The tolling application performed with the C-ITS equipment. These latter use the ITS-G5 technology, the Roadside Unit (RSU) and the on-board unit (OBU) with features specified by the standardization Institute ETSI. To perform this service, we highlight two mains requirements: how to have a reliable geolocation of the vehicle when it crosses the tollgate and how to secure the communication during the transaction process.

Technology

VANETs can use any wireless networking technology as their basis. The most prominent are short-range radio technologies are

WLAN and DSRC. In addition, cellular technologies or LTE and 5G
can be used for VANETs.

Simulations

Prior to the implementation of VANETs on the roads, realistic computer simulations of VANETs using a combination of Urban Mobility simulation [13] and Network simulation are necessary. Typically open source simulator like SUMO[14] (which handles road traffic simulation) is combined with a network simulator like TETCOS NetSim,[15] or NS-2 to study the performance of VANETs. Further simulations are also done for communication channel modeling that captures the complexities of wireless network for VANETs.[16]

Standards

Major standardization of VANET protocol stacks is taking place in the U.S., in Europe, and in Japan, corresponding to their dominance in the automotive industry.[6]: 5 

In the U.S., the IEEE 1609 WAVE Wireless Access in Vehicular Environments protocol stack builds on IEEE 802.11p WLAN operating on seven reserved channels in the 5.9 GHz frequency band. The WAVE protocol stack is designed to provide multi-channel operation (even for vehicles equipped with only a single radio), security, and lightweight application layer protocols. Within the

traffic monitoring, intersection management technologies, future telematics applications, and ITS
-based services.

Radio frequencies

In the US, the systems will use a region of the 5.9 GHz band set aside by the United States Congress, the unlicensed frequency also used by Wi-Fi. The US V2V standard, commonly known as WAVE ("Wireless Access for Vehicular Environments"), builds upon the lower-level IEEE 802.11p standard, as early as 2004.

The European Commission Decision 2008/671/EC harmonises the use of the 5 875-5 905 MHz frequency band for transport safety ITS applications.[17] In Europe V2V is standardised as ETSI ITS,[18] a standard also based on IEEE 802.11p. C-ITS, cooperative ITS, is also a term used in EU policy making, closely linked to ITS-G5 and V2V.

V2V is also known as VANET (vehicular ad hoc network). It is a variation of MANET (

Mobile ad hoc network), with the emphasis being now the node is the vehicle. In 2001, it was mentioned in a publication[19] that ad hoc networks can be formed by cars and such networks can help overcome blind spots, avoid accidents, etc. The infrastructure also participates in such systems, then referred to as V2X
(vehicle-to-everything). Over the years, there have been considerable research and projects in this area, applying VANETs for a variety of applications, ranging from safety to navigation and law enforcement.

In 1999 the US Federal Communications Commission (FCC) allocated 75 MHz in the spectrum of 5.850-5.925 GHz for intelligent transport systems.

Conflict over spectrum

As of 2016, V2V is under threat from cable television and other tech firms that want to take away a big chunk of the radio spectrum currently reserved for it and use those frequencies for high-speed internet service. V2V's current share of spectrum was set aside by the government in 1999. The auto industry is trying to retain all it can saying that it desperately needs the spectrum for V2V. The Federal Communications Commission has taken the side of the tech companies with the National Traffic Safety Board supporting the position of the auto industry. Internet service providers who want the spectrum claim that self-driving cars will make extensive use of V2V unnecessary. The auto industry said it is willing to share the spectrum if V2V service is not slowed or disrupted; the FCC plans to test several sharing schemes.[20]

Research

Research in VANETs started as early as 2000, in universities and research labs, having evolved from researchers working on wireless ad hoc networks. Many have worked on media access protocols, routing, warning message dissemination, and VANET application scenarios. V2V is currently in active development by

Daimler, Honda, Audi, Volvo and the Car-to-Car communication consortium.[22]

Regulation

Since then, the

Ann Arbor, Michigan. 2800 vehicles covering cars, motorcycles, buses and HGV of different brands took part using equipment by different manufacturers.[23] The US National Highway Traffic Safety Administration (NHTSA) saw this model deployment as proof that road safety could be improved and that WAVE standard technology was interoperable. In August 2014, NHTSA published a report arguing vehicle-to-vehicle technology was technically proven as ready for deployment.[24] In April 2014 it was reported that U.S. regulators were close to approving V2V standards for the U.S. market.[25] On 20 August 2014 the NHTSA published an Advance Notice of Proposed Rulemaking (ANPRM) in the Federal Register,[26] arguing that the safety benefits of V2X communication could only be achieved, if a significant part of the vehicles fleet was equipped. Because of the lacking immediate benefit for early adopters the NHTSA proposed a mandatory introduction. On 25 June 2015, the US House of Representatives held a hearing on the matter, where again the NHTSA, as well as other stakeholders argued the case for V2X.[27]

In the EU the ITS Directive 2010/40/EU[28] was adopted in 2010. It aims to assure that ITS applications are interoperable and can operate across national borders, it defines priority areas for secondary legislation, which cover V2X and requires technologies to be mature. In 2014 the European Commission's industry stakeholder "C-ITS Deployment Platform" started working on a regulatory framework for V2X in the EU.[29] It identified key approaches to an EU-wide V2X security Public Key infrastructure (PKI) and data protection, as well as facilitating a mitigation standard[30] to prevent radio interference between ITS-G5 based V2X and CEN DSRC-based road charging systems. The European Commission recognised ITS-G5 as the initial communication technology in its 5G Action Plan[31] and the accompanying explanatory document,[32] to form a communication environment consisting of ITS-G5 and cellular communication as envisioned by EU Member States.[33] Various pre-deployment projects exist at EU or EU Member State level, such as SCOOP@F, the Testfeld Telematik, the digital testbed Autobahn, the Rotterdam-Vienna ITS Corridor, Nordic Way, COMPASS4D or C-ROADS.[34] Further projects are under preparation.

VANET in urban scenarios

While using VANET in urban scenarios there are some aspects that are important to take in count. The first one is the analysis of the idle time[35] and the choosing of a routing protocol that satisfy the specifications of our network.[36] The other one is to try to minimize the data download time by choosing the right network architecture after analyzing the urban scenario where we want to implement it.[37]

See also

References

  1. doi:10.1109/VTCSpring.2015.7145650
    .
  2. ISBN 9780132442046
    .
  3. ^ "Research Challenges in Intelligent Transportation Networks, IFIP Keynote, 2008".
  4. doi:10.1016/j.adhoc.2017.03.006
    .
  5. S2CID 206866025
    .
  6. ^
    ISBN 9781107046719
    .
  7. ^ "VANET applications: Past, present, and future". Vehicular Communications. April 2021.
  8. ^ "A Comparative study of MANET and VANET Environment". Journal of Computing. 2 (7). July 2010. Retrieved 28 October 2013.
  9. ^ "Obstacle Management in VANET using Game Theory and Fuzzy Logic Control". ACEEE International Journal on Computing. 4 (1). June 2013. Retrieved 30 August 2013.
  10. S2CID 206470694
    .
  11. S2CID 15369285
    .
  12. S2CID 201140467
    .
  13. doi:10.1109/WCNC.2013.6554832
    .
  14. ^ "Downloads - Simulation of Urban Mobility". SUMO. 2018-08-20. Retrieved 2018-08-20.
  15. ^ Tetcos. "NetSim Academic". NetSim-Network Simulator & Emulator. Retrieved 2018-08-20.
  16. S2CID 10548384
    .
  17. ^ 2008/671/EC: Commission Decision of 5 August 2008 on the harmonised use of radio spectrum in the 5875 - 5905 MHz frequency band for safety-related applications of Intelligent Transport Systems (ITS)
  18. ^ EN 302 663 Intelligent Transport Systems (ITS); Access layer specification for Intelligent Transport Systems operating in the 5 GHz frequency band (http://www.etsi.org/deliver/etsi_en/302600_302699/302663/01.02.00_20/en_302663v010200a.pdf)
  19. ISBN 9780132442046
    .
  20. ^ "Cars are ready to talk to one another — unless we use their airwaves for Wi-Fi". Los Angeles Times. 25 August 2016.
  21. ^ CORPORATION., TOYOTA MOTOR. "Toyota to Bring Vehicle-Infrastructure Cooperative Systems to New Models in 2015 | TOYOTA Global Newsroom". newsroom.toyota.co.jp. Retrieved 2016-06-01.
  22. ^ "Car 2 Car - Communication Consortium: Technical Approach". www.car-to-car.org. Archived from the original on 2013-09-02. Retrieved 2016-06-01.
  23. ^ Safety Pilot Model Deployment Technical Fact Sheet (http://www.safercar.gov/staticfiles/safercar/connected/Technical_Fact_Sheet-Model_Deployment.pdf)
  24. ^ NHTSA: Vehicle-to-Vehicle Communications: Readiness of V2V Technology for Application (http://www.nhtsa.gov/staticfiles/rulemaking/pdf/V2V/Readiness-of-V2V-Technology-for-Application-812014.pdf Archived 2018-11-15 at the Wayback Machine)
  25. ^ "Vehicles May Soon Be Talking to Each Other". VOA. 4 April 2014. Retrieved 2016-06-01.
  26. ^ Federal Motor Vehicle Safety Standards: Vehicle-to-Vehicle (V2V) Communications, Docket No. NHTSA–2014–0022 (http://www.nhtsa.gov/staticfiles/rulemaking/pdf/V2V/V2V-ANPRM_081514.pdf Archived 2017-04-28 at the Wayback Machine)
  27. ^ Hearing in the House of Representatives (Protocol) (https://energycommerce.house.gov/hearings-and-votes/hearings/vehicle-vehicle-communications-and-connected-roadways-future Archived 2017-05-19 at the Wayback Machine)
  28. ^ [1] Directive 2010/40/EU on the framework for the deployment of Intelligent Transport Systems in the field of road transport and for interfaces with other modes of transport
  29. ^ [2] C-ITS Deployment Platform – Final Report, January 2016 (http://ec.europa.eu/transport/themes/its/doc/c-its-platform-final-report-january-2016.pdf)
  30. ^ [3] Intelligent Transport Systems (ITS); Mitigation techniques to avoid interference between European CEN Dedicated Short Range Communication (CEN DSRC) equipment and Intelligent Transport Systems (ITS) operating in the 5 GHz frequency range (http://www.etsi.org/deliver/etsi_ts/102700_102799/102792/01.02.01_60/ts_102792v010201p.pdf)
  31. ^ [4] 5G for Europe: An Action Plan – COM (2016) 588, footnote 29 (http://ec.europa.eu/newsroom/dae/document.cfm?doc_id=17131)
  32. ^ 5G Global Developments – SWD (2016) 306, page 9 (http://ec.europa.eu/newsroom/dae/document.cfm?doc_id=17132)
  33. ^ Amsterdam Declaration – Cooperation in the field of connected and automated driving (https://english.eu2016.nl/binaries/eu2016-en/documents/publications/2016/04/14/declaration-of-amsterdam/2016-04-08-declaration-of-amsterdam-final-format-3.pdf Archived 2017-03-01 at the Wayback Machine)
  34. ^ For C-ROADS see: Connecting Europe Facility – Transport 2015 Call for Proposals – Proposal for the Selection of Projects, pages 119-127 (https://ec.europa.eu/inea/sites/inea/files/20160712_cef_tran_brochure_web.pdf)
  35. S2CID 4932821
    .
  36. S2CID 209460107
    .
  37. S2CID 208527775
    .

Further reading

External links
Retrieved from "https://en.wikipedia.org/w/index.php?title=Vehicular_ad_hoc_network&oldid=1229892389"