Datasets
Open Access
Dataset of One-Way Delay in Local and Global Networks
- Citation Author(s):
-
EvgenySagatov
Samara National Research University, Moskovskoe sh. 34, Samara, 443086, RussiaSamaraMayhoubSamara National Research University, Moskovskoe sh. 34, Samara, 443086, RussiaAndreiSukhovMoscow Institute of Electronics and Mathematics, Higher School of Economics, Tallinskaya, 34, Moscow, 123458, RussiaDmitriiChernyshV.I. Vernadsky Crimean Federal University, Prospekt Vernadskogo 4, Simferopol, 295007, Russia - Submitted by:
- Evgeny Sagatov
- Last updated:
- Sun, 07/05/2020 - 08:10
- DOI:
- 10.21227/0dmg-3r29
- Data Format:
- Links:
- License:
1141 Views- Categories:
- Keywords:
Abstract
One-way delay (OWD) is the transmission time of the network packet from the first to the last bit from the sender node to the receiver node. The data set presented here was obtained as a result of measurements performed for the paper “Improving the Accuracy of One-Way Delay Measurements”.
One-way delay measurements were performed using three different utilities:
* the utility from the OWAMP protocol;
* first version of our utility, owping1; and
* the new version of our utility, owping2.
These measurement utilities differ critically in the way that they set timestamps. The first generation of utilities (OWAMP and owping1) set the time stamp arbitrarily during the assembly of the measurement package and later during its interpretation after being received. Thus, the processing time on the measuring device is added to the delay value.
The new version of the utility for setting timestamps uses the capabilities that were provided for in the Linux kernel, starting with version 2.6.30. In this and later versions of the kernel the SO_TIMESTAMPING socket option was added, which enables the interrogation of information, from the OS kernel, about the times at which packets are sent and received. Timestamps set/obtained in this way are the most accurate, since the OS kernel sets/interrogates them directly at the time of the physical sending or receiving of packets. Thus, the uncertainty associated with the time interval, associated with the assembly and subsequent interpretation of the packet, has been eliminated.
The graph shown in Figure 3 and the values in Table 2 are derived from data from files located in the Fig3andTab2 folder.
The OWAMP_chrony.csv file contains the results of measurements made on the local network: with, the IP packet size being 46 bytes, the measurement utility being OWAMP, and the type of NTP server being chrony. A file with the numerical OWAMP measurement data in microseconds can be seen via Excel.
The OWAMP_ntpd.csv file contains the results of measurements made on the local network: with, the size of the IP packet being 46 bytes, the measurement utility being OWAMP, and the type of NTP server being ntpd.
The owping2_chrony.csv file contains the results of measurements on the local network: with, the packet size being 46 bytes, the measuring utility being owping2, the NTP server type being chrony, and the protocol being UDP.
The owping2_ntpd.csv file contains the results of measurements on the local network: with, the packet IP size being 46 bytes, the measuring utility being owping2, the NTP server type being ntpd, and the protocol being UDP.
The graph displayed in Figure 5 and the values from Table 3 are derived from data from files located in the Fig5andTab3 folder.
All these files contain the results of measurements across a local network without a switch; the IP packet size is 46 bytes. The measurements in the files are presented in microseconds. They can be displayed via Excel.
In the owping1_icmp.csv file, the data is derived from owping1 utility measurements of ICMP packets.
In the owping1_udp.csv file, the data is derived from owping1 utility measurements of UDP packets.
In the owping2_icmp.csv file, the data is derived from owping2 utility measurements of ICMP packets.
In the owping2_udp.csv file, the data is derived from owping2 utility measurements of UDP packets.
The graph displayed in Figure 6 and the values in Table 4 are derived from data from a file located in the Fig6andTab4 folder.
The owamp_smr-crm_udp.csv file contains the OWD measurements across the global network, in the Samara-Crimea direction, using the OWAMP measurement utility.
Column A – represents the measurements made when the server was located in Crimea.
Column B – represents the measurements made when the server was located in Samara.
Table 5 was built using data from files located in the Tab5 folder.
The ping.csv file contains the results of RTT measurements across the global network, in the Samara-Crimea direction, using the RIPE Atlas measuring system.
The file 1 Client in Crimea.csv contains the results of OWD measurements across the Samara-Crimea section: with IP packet size being 46 bytes, and the measurement utility being owping2. The first column represents the measurements relating to the route from Samara to Crimea, the second represents the measurements relating to the route from Crimea to Samara. The values are in milliseconds. The file can be displayed using Excel.
File 2 Client in Crymea.csv contains the results of OWD measurements across the Crimea-Samara section: with, the IP packet size being 46 bytes, and the measurement utility being owping2. The first column represents the measurements relating to the route from Crimea to Samara, the second represents the measurements relating to the route from Samara to Crimea.
The graph displayed in Figure 7 was constructed using data from a file located in the Fig5 folder.
The owping2-owamp.csv file contains the OWD measurements for the Crimea-Samara direction. Column A contains data measured with owping2, Column B contains data measured with OWAMP.
The values shown in Table 6 were obtained using data from files located in the Tab6 folder.
OWAMP.csv contains the results of measurements across a global network in the Crimea-Samara direction (client in Crimea), where the IP packet size is 1500 bytes, and the measurement utility is OWAMP.
Column A - OWD from Crimea to Samara.
Column B - OWD from Samara to Crimea.
owping2.csv contains the results of measurements across a global network in the Crimean-Samara direction (client in Crimea), where the IP packet size is 1500 bytes, the measurement utility is owping2, and the protocol is UDP.
Column A - OWD from Crimea to Samara.
Column B - OWD from Samara to Crimea.
In addition to the data for the present paper, this set includes several additional files located in the Add folder.
The Rostov-Samara.csv file contains the results of OWD measurements from Rostov in the Don to Samara direction. Column A contains data for the Rostov-Samara direction, measured with owping2. Column B contains data for the return direction, Samara-Rostov.
The Rostov-Moscow.csv file contains the results of OWD measurements at Rostov in the Don to Moscow direction. Column A contains data for the Rostov-Moscow direction, measured with owping2. Column B contains data for the return direction, Moscow-Rostov.
The Rostov-Crimea.csv file contains the results of OWD measurements at Rostov in the Don-Crimea direction. Column A contains data for the Rostov-Crimea direction, measured with owping2. Column B contains data for the return direction Crimea-Rostov.
Dataset Files
File with Dataset dataset.zip (31.35 kB)
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.
