Vehicle-to-Infrastructure IEEE 802.11ad Wi-Fi dataset

1. Introduction

This dataset contains space and time-indexed data collected in a Vehicle-To-Infrastructure (V2I) communication scenario, where a moving vehicle downloaded data from a stationary Access Point (AP) using IEEE 802.11ad Wi-Fi.

The dataset is comprised of both throughput data and detailed frame information captured with tcpdump. It can be used to study 802.11ad's behavior in vehicular environments, in particular in what pertains to antenna sector selection.

This dataset is associated with the following article, which we recommend consulting for more information: Geolocation-based Sector Selection for Vehicle-to-Infrastructure 802.11ad Communication, Mateus Mattos, António Rodrigues, Rui Meireles, Ana Aguiar, in the Elsevier Journal of Computer Communications, Volume 193, ISSN 0140-3664, 2022, doi:10.1016/j.comcom.2022.07.005.

2. Experimental setup

The AP was placed at the corner of a residential-area intersection while a mobile client vehicle drove around it, downloading data from the AP.

Commercial Off-The-Shelf (COTS) TP-Link Talon AD7200 were used for both the stationary AP and mobile client. A third AD7200 configured in promiscuous mode was placed next to the mobile client, in order to capture the control frames being exchanged.

2.1 Experimental nodes

3. Trace description

The data is divided into traces. Each trace represents an uninterrupted period of data collection. The experiments were ran twice, once in 2020, and again in 2021. Environmental conditions, such as weather and topography, were consistent between the two experiment sets.

3.1 2020 traces

3.2 2021 traces

4. Data description

4.1 File structure

The data from the 2020 and 2021 sets of experiments can be found in subfolders 2020 and 2021, respectively.

Each subfolder constains the following:

• gps.csv: client vehicle mobility trace (individual NMEA sentences);
• gps-merged.csv: client vehicle mobility trace (summarized);
• thrghpt.csv: application throughput data;
• wifi.csv: summarized 802.11ad frame data;
• pcap/: contains raw .pcap files used to generate wifi.csv, separated by trace number;
• configs/: includes JSON file with fields and filters used by tshark for the generation of wifi.csv.

4.2 GPS data: gps.csv and gps-merged.csv

GPS data was captured by a high-accuracy GPS device: Trimble Pro Series 6H [link], and consists of a combination of fields provided by multiple NMEA GP* sentence codes, namely: GPRMC, GPGGA, GPGLL, and GNGSA [link].

Column description

gps.csv is a table with the following columns:

Note: Because each GPS sentence only contains a subset of the listed columns, any missing values are set to -1.0.

gps-merged.csv is a table containing all mobility information aggregated by GPS timestamp, for ease of use. It contains the following columns:

4.3 Application layer throughput : thrghpt.csv

Data was sent from a custom sender application running on the AP, at the maximum possible rate. A custom receiver application on the client vehicle consumes the data. A time-indexed log of the amount of data sent and received was recorded.

Column description

thrghpt.csv is a table with the following columns:

4.4 802.11ad frame data: wifi.csv

The wifi.csv file contains 802.11ad frame data, captured with tcpdump, on a Talon AD7200 router configured in promiscuous mode and colocated with the mobile client device.

Data collection and processing

The following tcpdump command was used to collect raw data frames:

tcpdump -B 100000 -s96 -i <ad-monitor-interface> -y IEEE802_11_RADIO -w <pcap-file> &

In order to create wifi.csv, the raw data frames were processed using tshark in order to filter out unnecessary information. More specifically, we ran the following command:

tshark -r <input-pcap> -2 -T fields <fields> -Y "<filter>" -E header=y -E separator=, -E quote=d -E occurrence=f

The raw input .pcap files for each trace are provided in the pcap/ folder. The parameters <filter> and <fields> represent the filtering conditions and what fields we want to extract from each frame, respectively. The actual values used are provided in the configs/tshark.json file.

Frames were filtered based on a single field: the WLAN frame type and subtype, or wlan.fc.type_subtype. Only the following types of frames were kept:

Column description

wifi.csv is a table with the following columns: