Scenario 3

License

If you want to use the dataset or scripts on this page, please use the link below to generate the final list of papers that need to be cited.

Paper Citation Matrix

Overview

Scenario 3 emulates a Vehicle-to-Infrastructure (V2I) mmWave communication setup. The adopted testbed comprises of two units. Unit 1 primarily consists of a stationary base station equipped with an RGB camera and a mmWave phased array. The stationary unit adopts a 16-element 60GHz-band phased array and it receives the transmitted signal using an over-sampled codebook of 64 pre-defined beams. The second unit (Unit 2) is a mobile vehicle unit equipped with a mmWave transmitter and GPS receiver. The transmitter consists of a quasi-omni antenna constantly transmitting (omnidirectional) at the 60 GHz band. Please refer to the detailed description of the testbed presented here. 

Rural Road: It is a two-way street with 6 lanes (3 lanes on each side with a passing lane in-between), a width of ~24 meters, and a vehicle speed limit of 45mph (72.42 kph). The wider street and the higher speed limit present an opportunity to incorporate diversity in the dataset. Furthermore, it is one of the busiest streets in Downtown Tempe, making it host of a large variety of vehicles such as buses, trucks, SUVs, and bikes, to name a few. In terms of wireless communication, the presence of big vehicles present the possibility of partial or complete UE blockage. All these make the location diverse from visual and wireless perspectives alike.

Collected Data

Overview

Number of Data Collection Units: 2 (using DeepSense Testbed #1)

Number of Data Samples:  1486

Data Modalities: RGB images, 64-dimensional received power vector, GPS locations

Average Data Capture Rate: 6.04 FPS

Sensors at Unit 1: (Stationary Receiver)

  • Wireless Sensor [Phased Array]: A 16-element antenna array operating in the 60 GHz frequency band and receives the transmitted signal using an over-sampled codebook of 64 pre-defined beams
  • Visual Sensor [Camera]: The main visual perception element in the testbed is an RGB-D camera. The camera is used to capture RGB images of 960×540 resolution at a base frame rate of 30 frames per second (fps)
  • Position Sensor [GPS Receiver]: A GPS-RTK receiver for capturing accurate real-time locations for the stationary unit
 

Sensors at Unit 2: (Mobile Transmitter)

  • Position Sensor [GPS Receiver]: A GPS-RTK receiver is installed on the top of the mobile unit and is used to capture accurate real-time locations at 10 frames per second (fps). The collected data comprises the Latitude and Longitude information in addition to other important data
Testbed1
Instances1486
Number of Units2
Total Data ModalitiesRGB images, 64-dimensional received power vector, GPS locations
Unit1
TypeStationary
Hardware ElementsRGB camera, mmWave phased array receiver, GPS receiver
Data ModalitiesRGB images, 64-dimensional received power vector, GPS locations
Unit2
TypeMobile
Hardware ElementsmmWave omni-directional transmitter, GPS receiver
Data ModalitiesGPS locations

Data Visualization

Download

Please login to download the DeepSense datasets

If you don't have an account, please click here to register
If you forgot your account password, please click here

How to Access Scenario 3 Data?

Step 1. Download Scenario 3 Data

Step 2. Extract the scenario3.zip file

Scenario 3 folder consists of three sub-folders:

  • unit1: Includes the data captured by unit 1
  • unit2: Includes the data captured by unit 2
  • resources: Includes the scenario-specific annotated dataset, data labels and other additional information. For more details, refer the resources section below. 
Scenario 3 folder also includes the “scenario 1.csv” file with the paths to all the collected data. For each coherent time, we provide the corresponding visual, wireless and GPS data. 

Resources

What are the Additional Resources?

Resources consist of the following information:

  • visual data annotations: For the visual data, we provide the coordinates of the 2D bounding box and attributes for each frame
  • data labels: The labels comprises of the ground-truth beam indices computed from the mmWave received power vectors, the direction of travel (unit2), and the sequence index
  • additional information: Includes the scenario-specific additional data. Details of the information is provided below

Visual Data Annotations

After performing the post-processing steps presented here, we generate the annotations for the visual data. Using state-of-the-art machine learning algorithms and multiple validation steps, we achieve highly accurate annotations. In this particular scenario, we provide the coordinates of the 2D bounding box and attributes for each frame. We, also, provide the ground-truth labels for 2 object classes, “Tx”, and “Distractor”. The “Tx” refers to the transmitting vehicle in the scene and “Distractor” for any other objects, such as human, other vehicles, etc. We follow the YOLO format for the bounding-box information. In the YOLO format, each bounding box is described by the center coordinates of the box and its width and height. Each number is scaled by the dimensions of the image; therefore, they all range between 0 and 1. Instead of category names, we provide the corresponding integer categories. We follow the following assignment: (i) “Tx” as “0” , and (ii) “Distractor” as “1”. 

Data Labels

The labels comprises of the ground-truth beam indices computed from the mmWave received power vectors, the direction of travel (unit2), and the sequence index. 

  • Ground-Truth Beam: The phased array of unit 1 utilizes an over-sampled beamforming codebook of N = 64 vectors, which are designed to cover the field of view. It captures the received power by applying the beamforming codebook elements as a combiner. For each received power vector of dimension [64 x 1], the index with the maximum received power value is selected as the optimal beam index. This data is provided in the column 7  [‘unit1_beam_index’] of the scenario3.csv
  • Sequence Index: During the data collection process, the mobile transmitter (unit2) travelled multiple times in front of the base station (unit1). For each run, the testbed collects multiple data samples. All the data samples with the same sequence index belongs to the same run
  • Direction of Travel: For this scenario, during the data collection process, the mobile unit generally moves either from left-to-right or right-to-left of the base station. Here “0” represents the left-to-right movement of the transmitter and “1” represents the “right-to-left” movement. The movement is measured is from the point of view of the base station. This is provided in the ‘unit2_direction’ column of the csv

Additional Information

We, further, provide additional information for each sample present in the scenario dataset. The details are provided in the columns 8 – 16 of the scenario3.csv. The contents of the additional data is listed below:

  • index: It represents the sample number
  • time_stamp[UTC]:  This represents the time of data capture in “hr-mins-secs-ms” format
  • unit2_num_sat: For each data sample, it is an integer value representing the number of connected satellites at that time instant 
  • unit2_sat_used: At each time instant, these were the satellites that the receiver was connected
  • unit2_fix_type: This shows whether or not there was a 3D fix. A 3D (three dimensional) position fix includes horizontal coordinates plus altitude. It requires a minimum of four visible satellites
  • unit2_DGPS: Binary indicator representing whether or not there was Differential GPS was used
  • unit2_PDOP: PDOP (position dilution of precision) describes the error caused by the relative position of the GPS satellites 
  • unit2_HDOP: HDOP represents the horizontal dilution of precision
An example table comprising of the data labels and the additional information is shown below.
index unit1_beam_index seq_index time_stamp[UTC] unit2_direction unit2_num_sat unit2_sat_used unit2_fix_type unit2_DGPS unit2_PDOP unit2_HDOP
1 2 1 ['01-20-55-332'] 0 18 G2 G5 G6 G12 G19 G24 G25 R6 R7 R12 R13 R22 R23 E2 E13 E15 E27 E30 3D Yes 1.4 0.8
2 2 1 ['01-20-55-498'] 0 18 G2 G5 G6 G12 G19 G24 G25 R6 R7 R12 R13 R22 R23 E2 E13 E15 E27 E30 3D Yes 1.3 0.7
3 2 1 ['01-20-55-664'] 0 18 G2 G5 G6 G12 G19 G24 G25 R6 R7 R12 R13 R22 R23 E2 E13 E15 E27 E30 3D Yes 1.3 0.7
4 2 1 ['01-20-55-830'] 0 13 G2 G5 G6 G12 G19 G24 G25 R6 R7 R12 R13 R22 R23 3D Yes 1.3 0.7
5 2 1 ['01-20-56-0'] 0 14 G2 G5 G6 G12 G19 G24 G25 R6 R7 R12 R13 R21 R22 R23 3D Yes 1.3 0.7
6 3 1 ['01-20-56-125'] 0 14 G2 G5 G6 G12 G19 G24 G25 R6 R7 R12 R13 R21 R22 R23 3D Yes 1.3 0.7
7 4 1 ['01-20-56-250'] 0 19 G2 G5 G6 G12 G19 G24 G25 R6 R7 R12 R13 R21 R22 R23 E2 E13 E15 E27 E30 3D Yes 1.3 0.7
8 6 1 ['01-20-56-375'] 0 14 G2 G5 G6 G12 G19 G24 G25 R6 R7 R12 R13 R21 R22 R23 3D Yes 1.3 0.7
9 8 1 ['01-20-56-500'] 0 19 G2 G5 G6 G12 G19 G24 G25 R6 R7 R12 R13 R21 R22 R23 E2 E13 E15 E27 E30 3D Yes 1.3 0.7
10 11 1 ['01-20-56-625'] 0 14 G2 G5 G6 G12 G19 G24 G25 R6 R7 R12 R13 R21 R22 R23 3D Yes 1.3 0.7
logo2

DeepSense Scenarios

Machine Learning Tasks

About the DeepSense Team

DeepSense Community

The objective of the registration is to have a way to send you updates in the future regarding the new scenarios, the bug fixes, and the machine learning competition opportunities.