IEEE 802.11p

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

IEEE 802.11p is an approved amendment to the IEEE 802.11 standard to add wireless access in vehicular environments (WAVE), a vehicular communication system. It defines enhancements to 802.11 (the basis of products marketed as Wi-Fi) required to support Intelligent Transportation Systems (ITS) applications. This includes data exchange between high-speed vehicles and between the vehicles and the roadside infrastructure in the licensed ITS band of 5.9 GHz (5.85-5.925 GHz). IEEE 1609 is a higher layer standard based on the IEEE 802.11p.[1]

Description

At some point, 802.11p was considered for dedicated short-range communications (DSRC), a U.S. Department of Transportation project based on the Communications, Air-interface, Long and Medium range (CALM) architecture of the International Organization for Standardization for vehicle-based communication networks, particularly for applications such as toll collection, vehicle safety services, and commerce transactions via cars. The ultimate vision was a nationwide network that enables communications between vehicles and roadside access points or other vehicles. This work built on its predecessor ASTM E2213-03 from ASTM International.[2]

In Europe, 802.11p was used as a basis for the ITS-G5 standard, supporting the GeoNetworking protocol for vehicle to vehicle and vehicle to infrastructure communication.[3] ITS G5 and GeoNetworking is being standardised by the European Telecommunications Standards Institute group for Intelligent Transport Systems.[4]

Context

As the communication link between the vehicles and the roadside infrastructure might exist for only a short amount of time, the IEEE 802.11p amendment defines a way to exchange data through that link without the need to establish a basic service set (BSS), and thus, without the need to wait for the association and authentication procedures to complete before exchanging data. For that purpose, IEEE 802.11p enabled stations use the wildcard BSSID (a value of all 1s) in the header of the frames they exchange, and may start sending and receiving data frames as soon as they arrive on the communication channel.

Because such stations are neither associated nor authenticated, the authentication and data confidentiality mechanisms provided by the IEEE 802.11 standard (and its amendments) cannot be used. These kinds of functionality must then be provided by higher network layers.

Timing advertisement

This amendment adds a new management frame for timing advertisement, which allows IEEE 802.11p enabled stations to synchronize themselves with a common time reference. The only time reference defined in the IEEE 802.11p amendment is UTC.

Receiver performances

Some optional enhanced channel rejection requirements (for both adjacent and nonadjacent channels) are specified in this amendment in order to improve the immunity of the communication system to out-of-channel interferences. They only apply to OFDM transmissions in the 5GHz band used by the IEEE 802.11a physical layer.

Frequency band

IEEE 802.11p standard uses channels of 10MHz bandwidth in the 5.9GHz band (5.850-5.925 GHz). This is half the bandwidth, or double the transmission time for a specific data symbol, as used in 802.11a. This allows the receiver to better cope with the characteristics of the radio channel in vehicular communications environments, e.g. the signal echoes reflected from other cars or houses.[5]

History

The 802.11p Task Group was formed in November 2004. Lee Armstrong was chair and Wayne Fisher technical editor. Drafts were developed from 2005 through 2009. By April 2010 draft 11 was approved by 99% affirmative votes and no comments.[6] The approved amendment was published July 15, 2010.[7] Its title was "Amendment 6: Wireless Access in Vehicular Environments".[7]

In August 2008 the European Commission allocated part of the 5.9 GHz band for priority road safety applications and inter-vehicle, infrastructure communications.[8] The intention is that compatibility with the USA will be ensured even if the allocation is not exactly the same; frequencies will be sufficiently close to enable the use of the same antenna and radio transmitter/receiver.

Simulations published in 2010 predict delays of at the most tens of milliseconds for high-priority traffic.[9]

Implementations

In the Portuguese city of Porto it is used as a mesh to provide vehicle data between public vehicles and wifi access for its passengers [10]

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. https://www.b2match.eu/m4g-portugal/participants/768

External links