CRAWDAD gatech/vehicular (v. 2006-03-15)

Citation Author(s):
Richard M.
Fujimoto
Georgia Institute of Technology
Randall
Guensler
Georgia Institute of Technology
Michael P.
Hunter
Georgia Institute of Technology
Hao
Wu
Georgia Institute of Technology
Mahesh
Palekar
Jaesup
Lee
Georgia Institute of Technology
Joonho
Ko
Georgia Institute of Technology
Submitted by:
CRAWDAD Team
Last updated:
Tue, 11/14/2006 - 08:00
DOI:
10.15783/C74S3Z
Data Format:
License:
483 Views
Categories:
Keywords:
0
0 ratings - Please login to submit your rating.

Abstract 

Dataset for short range communications between vehicles and between vehicle and roadside station.

This dataset contains the measurement of the performance of short range communications between vehicles and between vehicle and roadside station.

last modified : 2006-11-14

release date : 2006-03-15

date/time of measurement start : 2005-01-24

date/time of measurement end : 2005-04-23

collection environment : The experiments were conducted in the northwest sector of Atlanta, GA along I-75 between Exit 250 and Exit 255 as shown in the figure in the README files in the traces. This section of I-75 corridor has five regular lanes in addition to one HOV lane in most parts of the study area. Vehicle traffic in the opposite directions is separated by a concrete median barrier. All the experiments were conducted between 2pm and 5pm under non-congested traffic conditions and non-inclement weather conditions.

network configuration : For the experiments, laptop computers running Red Hat Linux 9, an ORINOCO 802.11b gold card with a 2.5dB omni-directional external antenna placed on the roof of the vehicle, and a Garmin 72 GPS receiver (with WAAS correction). The wireless cards configured in IBSS ad-hoc mode with power management turned off and a fixed data rate. The GPS reports latitude, longitude, speed, and heading of the vehicle every 2 seconds. The location information reported by GPS has an accuracy of 5-7 meters. We obtained location information every second through interpolation. All experiments were conducted using broadcast at 2Mbps that allows us to explore basic communication performance because there is no RTS/CTS/ACK and retransmissions.

data collection methodology : IPerf, a network performance measurement tool was used along with the GPS readings to in conjunction with GPS readings to measure network performance. Both sender and receiver log time, location, velocity (from GPS), data packets received / sent, and signal quality.

Traceset

gatech/vehicular/v2r

Measurement of the traffic from vehicle to roadside.

  • files: low_moore.tar.gz, high_moore.tar.gz, low_howell.tar.gz, high_howell.tar.gz
  • description: Performance measurement of a short range communications between vehicle and roadside traffic.
  • measurement purpose: Network Performance Analysis
  • methodology: Sender and Receiver were equipped with the same equipment described above in network description. While the sender was in a vehicle. The sending vehicle traveled in loops Exit 252B and Exit 255 along I-75 for 5 laps. The vehicle was driven in the rightmost lane whenever possible. The sender broadcasted packets of 1470 bytes at an average rate of about 150 packets/s. The receiver was placed on the Peachtree Battle bridge above the median. The receiver was placed in either southern or northern side of the bridge and at different heights. Different locations of the receiver are as follows: a. Low Howell - The receiver was placed on the southern side of the bridge facing Exit 252B on the table of height 0.7m. The traces of this experiment are stored in the low_howell directory. b. High Howell - The receiver was placed on the southern side of the bridge facing Exit 252B on a tripod of height 1.8m. The traces for this experiment are stored in high_howell directory. c. Low Moore - The receiver was placed on the northern side of the bridge facing Exit 254 on the table of height 0.7m. The traces of this experiment are stored in the low_moore directory. d. High Moore - The receiver was placed on the northern side of the bridge facing Exit 254 on a tripod of height 1.8m. The traces for this experiment are stored in high_moore directory.

gatech/vehicular/v2r Traces

  • low_moore: Trace of the traffic between vehicle to roadside where the receiver was placed low on the northern side of the bridge.
    • configuration: Date: 11 Feb 2005 Time: Afternoon Sender: Car: Subaru Imprezza Antenna - External antenna on top of the front passenger seat. Receiver: Location: Peachtree battle bridge. Antenna - External Antenna on the table (0.7m) on the side facing North. Description: Sender travelling in a loop between exit 250 and exit 255. Data collected over 5 laps. Direction: Northbound - Exit 250 to Exit 255. Southbound - Exit 255 to Exit 250.
    • format:

      See note in the parent traceset (gatech/vehicular/v2r)

  • high_moore: Trace of the traffic between vehicle to roadside where the receiver was placed high on the northern side of the bridge.
    • configuration: Date: 24 Jan 2005 and 11 Feb 2005 Sender: Car: Subaru Imprezza Antenna - External antenna on top of the front passenger seat. Receiver: Location: Peachtree battle bridge. Antenna - External Antenna on top of tripod(1.8m) on the side facing North. Description: Sender travelling in a loop between exit 250 and exit 255. Data collected over 5 laps. Direction: Northbound - Exit 250 to Exit 255. Southbound - Exit 255 to Exit 250.
    • format:

      See note in the parent traceset (gatech/vehicular/v2r)

  • low_howell: Trace of the traffic between vehicle to roadside where the receiver was placed low on the southern side of the bridge.
    • configuration: Date: 4 Feb 2005 Time: Afternoon Sender: Car: Subaru Imprezza Antenna - External antenna on top of the front passenger seat. Receiver: Location: Peachtree battle bridge. Antenna - External Antenna on the table (0.7m) on the side facing south. Description: Sender travelling in a loop between exit 250 and exit 255. Data collected over 5 laps. Direction: Northbound - Exit 250 to Exit 255. Southbound - Exit 255 to Exit 250.
    • format:

      See note in the parent traceset (gatech/vehicular/v2r)

  • high_howell: Trace of the traffic between vehicle to roadside where the receiver was placed high on the southern side of the bridge.
    • configuration: Date: 4 Feb 2005 Time: Afternoon Sender: Car: Subaru Imprezza Antenna - External antenna on top of the front passenger seat. Receiver: Location: Peachtree battle bridge. Antenna - External Antenna on top of tripod(1.8m) on the side facing south. Description: Sender travelling in a loop between exit 250 and exit 255. Data collected over 5 laps. Direction: Northbound - Exit 250 to Exit 255. Southbound - Exit 255 to Exit 250.
    • format:

      See note in the parent traceset (gatech/vehicular/v2r)

gatech/vehicular/v2v

Measurement of the traffic from vehicle to vehicle.

  • files: v2v_follow.tar.gz, v2v_opposite.tar.gz
  • description: Performance measurement of a short range communications between vehicle to vehicle.
  • measurement purpose: Network Performance Analysis
  • methodology: Both the sender and receiver were placed in vehicles. Two different kinds of experiments were conducted. a. Following Scenario: The vehicles traveled in a loop between Exit 250 and Exit 255 with the sender vehicle following the receiving vehicle. Both the vehicles remained in the same lane, second from right. We tried to maintain same distance between two vehicles in a lap. But the distance between two vehicles was varied for different laps. The traces for this experiment are stored in v2v_follow directory. This experiment was done on two days. Hence there are two folders - one for each day in the v2v_follow directory. b. Crossing Scenario: The experiments were conducted on I-75 between Exit 252B and Exit 254. The two vehicles always stayed in the rightmost lane, and were separated by 8 lanes of traffic and a concrete median. The traces for this experiment are stored in v2v_opposite directory.

gatech/vehicular/v2v Traces

  • v2v_follow: Trace of the traffic between two vehicles where the sender vehicle follows the receiving vehicle.
    • configuration: ate: 13 April 2005 and 20 Apr 2005 Time: Afternoon Sender : Car: Subaru Imprezza Antenna - External antenna on top of the front passenger seat. Receiver: Car:Nissan Altima (2000) Antenna - External antenna on top of the front passenger seat. Description: Sender following the receiver broadcasting UDP packets of size 1470 bytes with an average rate of 150 packets/sec. The vehicles traveled in a loop between Exit 250 and Exit 255 with the sender vehicle following the receiving vehicle. Both the vehicles remained in the same lane, second from right. We tried to maintain same distance between two vehicles in a lap. But the distance between two vehicles was varied for different laps.Traces for each day are in seperate folders. Direction: Northbound - Exit 250 to Exit 255. Southbound - Exit 255 to Exit 250.
    • format:

      See note in the parent traceset (gatech/vehicular/v2v)

  • v2v_opposite: Trace of the traffic between two vehicles moving in opposite direction.
    • configuration: Date: 23 Feb 2005 Sender : Car: Subaru Antenna - External antenna on top of the front passenger seat. Receiver: Car: Nissan Altima (2000) Antenna - External antenna on top of the front passenger seat. Description: Sender following the receiver broadcasting UDP packets of size 1470 bytes at a rate of 150 packets/sec. The experiments were conducted on I-75 between Exit 252B and Exit 254. The two vehicles always stayed in the rightmost lane, and were separated by 8 lanes of traffic and a concrete median. Direction: Northbound - Exit 250 to Exit 255. Southbound - Exit 255 to Exit 250.
    • format:

      See note in the parent traceset (gatech/vehicular/v2v)

Instructions: 

The files in this directory are a CRAWDAD dataset hosted by IEEE DataPort. 

About CRAWDAD: the Community Resource for Archiving Wireless Data At Dartmouth is a data resource for the research community interested in wireless networks and mobile computing. 

CRAWDAD was founded at Dartmouth College in 2004, led by Tristan Henderson, David Kotz, and Chris McDonald. CRAWDAD datasets are hosted by IEEE DataPort as of November 2022. 

Note: Please use the Data in an ethical and responsible way with the aim of doing no harm to any person or entity for the benefit of society at large. Please respect the privacy of any human subjects whose wireless-network activity is captured by the Data and comply with all applicable laws, including without limitation such applicable laws pertaining to the protection of personal information, security of data, and data breaches. Please do not apply, adapt or develop algorithms for the extraction of the true identity of users and other information of a personal nature, which might constitute personally identifiable information or protected health information under any such applicable laws. Do not publish or otherwise disclose to any other person or entity any information that constitutes personally identifiable information or protected health information under any such applicable laws derived from the Data through manual or automated techniques. 

Please acknowledge the source of the Data in any publications or presentations reporting use of this Data. 

Citation:

Richard M. Fujimoto, Randall Guensler, Michael P. Hunter, Hao Wu, Mahesh Palekar, Jaesup Lee, Joonho Ko, gatech/vehicular, https://doi.org/10.15783/C74S3Z , Date: 20060315

Dataset Files

LOGIN TO ACCESS DATASET FILES
Open Access dataset files are accessible to all logged in  users. Don't have a login?  Create a free IEEE account.  IEEE Membership is not required.

Documentation

AttachmentSize
File gatech-vehicular-readme.txt1.65 KB

These datasets are part of Community Resource for Archiving Wireless Data (CRAWDAD). CRAWDAD began in 2004 at Dartmouth College as a place to share wireless network data with the research community. Its purpose was to enable access to data from real networks and real mobile users at a time when collecting such data was challenging and expensive. The archive has continued to grow since its inception, and starting in summer 2022 is being housed on IEEE DataPort.

Questions about CRAWDAD? See our CRAWDAD FAQ. Interested in submitting your dataset to the CRAWDAD collection? Get started, by submitting an Open Access Dataset.