CRAWDAD due/packet-delivery

Citation Author(s):
Songwei
Fu
Yan
Zhang
Submitted by:
CRAWDAD Team
Last updated:
Mon, 03/30/2015 - 08:00
DOI:
10.15783/C7NP4Z
Data Format:
License:
576 Views
Citations:
1
Categories:
Keywords:
0
0 ratings - Please login to submit your rating.

Abstract 

The data set includes measurements of the data delivery performance of a WSN link in indoor scenario, where 4 major performance metrics, namely energy, throughput, delay and loss, were measured over 6 months under around 50 thousand parameter configurations of 7 key stack parameters. The meta-data of transmission of nearly 200 million packets are included in the dataset.

last modified :

2015-03-30

nickname :

packet-delivery

institution :

University of Duisburg-Essen and Norwegian University of Science and Technology

release date :

2015-03-30

date/time of measurement start :

2012-11-01

date/time of measurement end :

2013-11-30

collection environment :

The experiments were conducted in a long hallway of 2 meters by 40 meters in a university building. Each mote was fixed on a wooden stand of 0.7-meter high. We maintained line-of-sight between the two motes. The distance between the two nodes varies from 10 meters to 35 meters. During the experiments, university students and employees may walk in the hallway.

network configuration :

The parameter configurations considered in the experiments are:

packet inter-arrival time (ms): 10, 15, 20, 25, 30, 35, 40, 50
packet payload size (bytes): 20, 35, 50, 65, 80, 95, 110
maximum queue size (packets): 1, 30, 60
Max_tries - maximum number of transmissions: 1, 3, 5
retry delay (ms): 30, 60
transmission power level: 3,7,11,15,19,23,27,31
distance between sender and receiver (meter): 10, 15, 20, 25, 30, 35

data collection methodology :

The metadata of each packet is measured at the sender node and receiver node and forwarded to a laptop via USB cables.

sanitization :

The data does not contain any sensitive information that could raise any privacy concerns. Therefore, no sanitization is performed.

Traceset

due/packet-delivery/delay

Per-packet delay of packet transmission under various stack parameter configurations.

  • files: delay_10m_12runs.rar, delay_15m_11runs.rar, delay_20m_10runs.rar, delay_25m_9runs.rar, delay_30m_11runs.rar, delay_35m_9runs.rar
  • description: The traceset includes 6 traces. Each trace consists of the delay measurements of about a dozen of runs under one distance. The delay of each packet is defined as the time between the packet generation at the sender and the packet reception at the receiver.
  • measurement purpose: Network Performance Analysis
  • last modified: 2015-03-30
  • dataname: due/packet-delivery/delay
  • version: 20150401
  • change: the initial version
  • release date: 2015-03-30
  • nickname: delay

due/packet-delivery/delay Traces

    • 10meter: The delay measurements of all packets transimitted at distance 10 meter.
  • format: Each file has total 8064 lines; Each line includes per-packet delay for the packets transmitted in all the runs under the same stack parameter configuration. Each line in the file has the following format: period | packet length | queue_size | max_retries | retry_delay | TxP_level | distance | average_SNR | delay_run1_pkt1 | delay_run1_pkt2 | ... | delay_run1_pkt300 |delay_run2_pkt1 |...| delay_run2_pkt300 |...|delay_runN_pkt1 |...|delay_runN_pkt300 | Note that for packet that are not received or delay measurement has error, the corresponding delay value is 9999 or 1111.
  • description: Each trace contains the delay measurements of about a dozen of runs at the same distance. Each run contains delay of 300 packets.
  • last modified: 2015-03-30
  • dataname: due/packet-delivery/delay/10meter
  • version: 20150401
  • change: the initial version
  • release date: 2015-03-30
  • url: /download/due/packet-delivery/delay_10m_12runs.rar
  • nickname: 10meter
    • 15meter: The delay measurements of all packets transmitted at distance 15 meter.
  • format: Each file has total 8064 lines; Each line includes per-packet delay for the packets transmitted in all the runs under the same stack parameter configuration. Each line in the file has the following format: period | packet length | queue_size | max_retries | retry_delay | TxP_level | distance | average_SNR | delay_run1_pkt1 | delay_run1_pkt2 | ... | delay_run1_pkt300 |delay_run2_pkt1 |...| delay_run2_pkt300 |...|delay_runN_pkt1 |...|delay_runN_pkt300 | Note that for packet that are not received or delay measurement has error, the corresponding delay value is 9999 or 1111.
  • description: Each trace contains the delay measurements of about a dozen of runs at the same distance. Each run contains delay of 300 packets.
  • last modified: 2015-03-30
  • dataname: due/packet-delivery/delay/15meter
  • version: 20150401
  • change: the initial version
  • release date: 2015-03-30
  • url: /download/due/packet-delivery/delay_15m_11runs.rar
  • nickname: 15meter
    • 20meter: The delay measurements of all packets transmitted at distance 20 meter.
  • format: Each file has total 8064 lines; Each line includes per-packet delay for the packets transmitted in all the runs under the same stack parameter configuration. Each line in the file has the following format: period | packet length | queue_size | max_retries | retry_delay | TxP_level | distance | average_SNR | delay_run1_pkt1 | delay_run1_pkt2 | ... | delay_run1_pkt300 |delay_run2_pkt1 |...| delay_run2_pkt300 |...|delay_runN_pkt1 |...|delay_runN_pkt300 | Note that for packet that are not received or delay measurement has error, the corresponding delay value is 9999 or 1111.
  • description: Each trace contains the delay measurements of about a dozen runs at the same distance. Each run contains delay of 300 packets.
  • last modified: 2015-03-30
  • dataname: due/packet-delivery/delay/20meter
  • version: 20150401
  • change: the initial version
  • release date: 2015-03-30
  • url: /download/due/packet-delivery/delay_20m_10runs.rar
  • nickname: 20meter
    • 25meter: The delay measurements of all packets transmitted at distance 25 meter.
  • format: Each file has total 8064 lines; Each line includes per-packet delay for the packets sent in all the runs under the same stack parameter configuration. Each line in the file has the following format: period | packet length | queue_size | max_retries | retry_delay | TxP_level | distance | average_SNR | delay_run1_pkt1 | delay_run1_pkt2 | ... | delay_run1_pkt300 |delay_run2_pkt1 |...| delay_run2_pkt300 |...|delay_runN_pkt1 |...|delay_runN_pkt300 | Note that for packet that are not received or delay measurement has error, the corresponding delay value is 9999 or 1111.
  • description: Each trace contains the delay measurements of about a dozen of runs at the same distance. Each run contains delay of 300 packets.
  • last modified: 2015-03-30
  • dataname: due/packet-delivery/delay/25meter
  • version: 20150401
  • change: the initial version
  • release date: 2015-03-30
  • url: /download/due/packet-delivery/delay_25m_9runs.rar
  • nickname: 25meter
    • 30meter: The delay measurements of all packets transmitted at distance 30 meter.
  • format: Each file has total 8064 lines; Each line includes per-packet delay for the packets sent in all the runs under the same stack parameter configuration. Each line in the file has the following format: period | packet length | queue_size | max_retries | retry_delay | TxP_level | distance | average_SNR | delay_run1_pkt1 | delay_run1_pkt2 | ... | delay_run1_pkt300 |delay_run2_pkt1 |...| delay_run2_pkt300 |...|delay_runN_pkt1 |...|delay_runN_pkt300 | Note that for packet that are not received or delay measurement has error, the corresponding delay value is 9999 or 1111.
  • description: Each trace contains the delay measurements of about a dozen runs at the same distance. Each run contains delay of 300 packets.
  • last modified: 2015-03-30
  • dataname: due/packet-delivery/delay/30meter
  • version: 20150401
  • change: the initial version
  • release date: 2015-03-30
  • url: /download/due/packet-delivery/delay_30m_11runs.rar
  • nickname: 30meter
    • 35meter: The delay measurements of all packets transmitted at distance 35 meter.
  • format: Each file has total 8064 lines; Each line includes per-packet delay for the packets transmitted in all the runs under the same stack parameter configuration. Each line in the file has the following format: period | packet length | queue_size | max_retries | retry_delay | TxP_level | distance | average_SNR | delay_run1_pkt1 | delay_run1_pkt2 | ... | delay_run1_pkt300 |delay_run2_pkt1 |...| delay_run2_pkt300 |...|delay_runN_pkt1 |...|delay_runN_pkt300 | Note that for packet that are not received or delay measurement has error, the corresponding delay value is 9999 or 1111.
  • description: Each trace contains the delay measurements of about a dozen of runs at the same distance. Each run contains delay of 300 packets.
  • last modified: 2015-03-30
  • dataname: due/packet-delivery/delay/35meter
  • version: 20150401
  • change: the initial version
  • release date: 2015-03-30
  • url: /download/due/packet-delivery/delay_35m_9runs.rar
  • nickname: 35meter

due/packet-delivery/packet-metadata

The metadata of each packet included in the trace are: RSSI, LQI, noise floor, actual queue size, overflow, actual retransmission number, deliver success/fail and arrival time

  • files: distance_10m.rar, distance_15m.rar, distance_20m.rar, distance_25m.rar, distance_30m.rar, distance_35m.rar
  • description: The traceset includes 6 traces. Each trace consists of a dozen of files collected at the same distance. One file includes the measurements of one run. Each file has 8064 lines, and each line includes the metadata of 300 packets that were transmitted at the same parameter configuration.
  • measurement purpose: Bit Error Characterization, Network Performance Analysis
  • last modified: 2015-03-30
  • dataname: due/packet-delivery/packet-metadata
  • version: 20150401
  • change: the initial version
  • release date: 2015-03-30
  • nickname: packet-metadata

due/packet-delivery/packet-metadata Traces

    • 10meter: The measurements of all packets that were transmitted at distance 10 meter.
  • format: Each file has 8064 lines; Each line includes data delivery information for 300 packets transmitted under the same stack parameter configuration. Each line has the following format: experiment_number | run_number | period | packet_length | queue_size | Max_tries | retry_delay | TxP_level | distance | pakcet_sequence_number_001 | buffer_overflow | actual_queue_size| ACK| actual_try_number| RSSI | noise_floor | LQI | arrival_time| ... | pakcet_sequence_number_300 | buffer_overflow | actual_queue_size| ACK| actual_retry_number| RSSI | noise_floor | LQI | arrival_time| Note that the RSSI values in the dataset is without offset. The true RSSI values must add an offset of - 45 dBm.
  • description: Each trace consists of a dozen of files collected at the same distance. One file includes the measurements of one run. Each file has 8064 lines, and each line includes the metadata of 300 packets that were transmitted at the same parameter configuration.
  • last modified: 2015-03-30
  • dataname: due/packet-delivery/packet-metadata/10meter
  • version: 20150401
  • change: the initial version
  • release date: 2015-03-30
  • url: /download/due/packet-delivery/distance_10m.rar
  • nickname: 10meter
    • 15meter: The measurements of all packets that were transmitted at distance 15 meter.
  • format: Each file has 8064 lines; Each line includes data delivery information for 300 packets transmitted under the same stack parameter configuration. Each line has the following format: experiment_number | run_number | period | packet_length | queue_size | Max_tries | retry_delay | TxP_level | distance | pakcet_sequence_number_001 | buffer_overflow | actual_queue_size| ACK| actual_try_number| RSSI | noise_floor | LQI | arrival_time| ... | pakcet_sequence_number_300 | buffer_overflow | actual_queue_size| ACK| actual_retry_number| RSSI | noise_floor | LQI | arrival_time| Note that the RSSI values in the dataset is without offset. The true RSSI values must add an offset of - 45 dBm.
  • description: Each trace consists of a dozen of files collected at the same distance. One file includes the measurements of one run. Each file has 8064 lines, and each line includes the metadata of 300 packets that were transmitted at the same parameter configuration.
  • last modified: 2015-03-30
  • dataname: due/packet-delivery/packet-metadata/15meter
  • version: 20150401
  • change: the initial version
  • release date: 2015-03-30
  • url: /download/due/packet-delivery/distance_15m.rar
  • nickname: 15meter
    • 20meter: The measurements of all packets that were transmitted at distance 20 meter.
  • format: Each file has 8064 lines; Each line includes data delivery information for 300 packets transmitted under the same stack parameter configuration. Each line has the following format: experiment_number | run_number | period | packet_length | queue_size | Max_tries | retry_delay | TxP_level | distance | pakcet_sequence_number_001 | buffer_overflow | actual_queue_size| ACK| actual_try_number| RSSI | noise_floor | LQI | arrival_time| ... | pakcet_sequence_number_300 | buffer_overflow | actual_queue_size| ACK| actual_retry_number| RSSI | noise_floor | LQI | arrival_time| Note that the RSSI values in the dataset is without offset. The true RSSI values must add an offset of - 45 dBm.
  • description: Each trace consists of a dozen of files collected at the same distance. One file includes the measurements of one run. Each file has 8064 lines, and each line includes the metadata of 300 packets that were transmitted at the same parameter configuration.
  • last modified: 2015-03-30
  • dataname: due/packet-delivery/packet-metadata/20meter
  • version: 20150401
  • change: the initial version
  • release date: 2015-03-30
  • url: /download/due/packet-delivery/distance_20m.rar
  • nickname: 20meter
    • 25meter: The measurements of all packets that were transmitted at distance 25 meter.
  • format: Each file has 8064 lines; Each line includes data delivery information for 300 packets transmitted under the same stack parameter configuration. Each line has the following format: experiment_number | run_number | period | packet_length | queue_size | Max_tries | retry_delay | TxP_level | distance | pakcet_sequence_number_001 | buffer_overflow | actual_queue_size| ACK| actual_try_number| RSSI | noise_floor | LQI | arrival_time| ... | pakcet_sequence_number_300 | buffer_overflow | actual_queue_size| ACK| actual_retry_number| RSSI | noise_floor | LQI | arrival_time| Note that the RSSI values in the dataset is without offset. The true RSSI values must add an offset of - 45 dBm.
  • description: Each trace consists of a dozen of files collected at the same distance. One file includes the measurements of one run. Each file has 8064 lines, and each line includes the metadata of 300 packets that were transmitted at the same parameter configuration.
  • last modified: 2015-03-30
  • dataname: due/packet-delivery/packet-metadata/25meter
  • version: 20150401
  • change: the initial version
  • release date: 2015-03-30
  • url: /download/due/packet-delivery/distance_25m.rar
  • nickname: 25meter
    • 30meter: The measurements of all packets that were transmitted at distance 30 meter.
  • format: Each file has 8064 lines; Each line includes data delivery information for 300 packets transmitted under the same stack parameter configuration. Each line has the following format: experiment_number | run_number | period | packet_length | queue_size | Max_tries | retry_delay | TxP_level | distance | pakcet_sequence_number_001 | buffer_overflow | actual_queue_size| ACK| actual_try_number| RSSI | noise_floor | LQI | arrival_time| ... | pakcet_sequence_number_300 | buffer_overflow | actual_queue_size| ACK| actual_retry_number| RSSI | noise_floor | LQI | arrival_time| Note that the RSSI values in the dataset is without offset. The true RSSI values must add an offset of - 45 dBm.
  • description: Each trace consists of a dozen of files collected at the same distance. One file includes the measurements of one run. Each file has 8064 lines, and each line includes the metadata of 300 packets that were transmitted at the same parameter configuration.
  • last modified: 2015-03-30
  • dataname: due/packet-delivery/packet-metadata/30meter
  • version: 20150401
  • change: the initial version
  • release date: 2015-03-30
  • url: /download/due/packet-delivery/distance_30m.rar
  • nickname: 30meter
    • 35meter: The measurements of all packets that were transmitted at distance 35 meter.
  • format: Each file has 8064 lines; Each line includes data delivery information for 300 packets transmitted under the same stack parameter configuration. Each line has the following format: experiment_number | run_number | period | packet_length | queue_size | Max_tries | retry_delay | TxP_level | distance | pakcet_sequence_number_001 | buffer_overflow | actual_queue_size| ACK| actual_try_number| RSSI | noise_floor | LQI | arrival_time| ... | pakcet_sequence_number_300 | buffer_overflow | actual_queue_size| ACK| actual_retry_number| RSSI | noise_floor | LQI | arrival_time| Note that the RSSI values in the dataset is without offset. The true RSSI values must add an offset of - 45 dBm.
  • description: Each trace consists of a dozen of files collected at the same distance. One file includes the measurements of one run. Each file has 8064 lines, and each line includes the metadata of 300 packets that were transmitted at the same parameter configuration.
  • last modified: 2015-03-30
  • dataname: due/packet-delivery/packet-metadata/35meter
  • version: 20150401
  • change: the initial version
  • release date: 2015-03-30
  • url: /download/due/packet-delivery/distance_35m.rar
  • nickname: 35meter
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:

Songwei Fu, Yan Zhang, due/packet-delivery, https://doi.org/10.15783/C7NP4Z , Date: 20150401

 

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 due-packet-delivery-readme.txt1.57 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.