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.

Instructions: 

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.

Categories:
426 Views

The following data set is modelled after the implementers’ test data in 3GPP TS 33.501 “Security architecture and procedures for 5G System” with the same terminology. The data set corresponds to SUCI (Subscription Concealed Identifier) computation in the 5G UE (User Equipment) for IMSI (International Mobile Subscriber Identity) based SUPI (Subscription Permanent Identifier) and ECIES Profile A.

Instructions: 

The following data set is modelled after the implementers’ test data in 3GPP TS 33.501 “Security architecture and procedures for 5G System” with the same terminology. The data set corresponds to SUCI (Subscription Concealed Identifier) computation in the 5G UE (User Equipment) for IMSI (International Mobile Subscriber Identity) based SUPI (Subscription Permanent Identifier) and ECIES Profile A, the IMSI consists of MCC|MNC: '274012'. 

In the 5G system, the globally unique 5G subscription permanent identifier is called SUPI as defined in 3GPP TS 23.501. For privacy reasons, the SUPI from the 5G devices should not be transferred in clear text, and is instead concealed inside the privacy preserving SUCI. Consequently, the SUPI is privacy protected over-the-air of the 5G radio network by using the SUCI. For SUCIs containing IMSI based SUPI, the UE in essence conceals the MSIN (Mobile Subscriber Identification Number) part of the IMSI. On the 5G operator-side, the SIDF (Subscription Identifier De-concealing Function) of the UDM (Unified Data Management) is responsible for de-concealment of the SUCI and resolves the SUPI from the SUCI based on the protection scheme used to generate the SUCI. 

The SUCI protection scheme used in this data set is ECIES Profile A. The size of the scheme-output is a total of 256-bit public key, 64-bit MAC & 40-bit encrypted MSIN. The SUCI scheme-input MSIN is coded as hexadecimal digits using packed BCD coding where the order of digits within an octet is same as the order of MSIN. As the MSINs are odd number of digits, bits 5 to 8 of final octet is coded as ‘1111’.  

# Example Python code to load data into Spark DataFrame

df = spark.read.format("csv").option("inferSchema","true").option("header","true").option("sep",",").load(“5g_suci_using_ecies_profile_a_100k.gz”)

Categories:
2929 Views

Secure cryptographic protocols are indispensable for modern communication systems. It is realized through an encryption process in cryptography. In quantum cryptography, Quantum Key Distribution (QKD) is a widely popular quantum communication scheme that enables two parties to establish a shared secret key that can be used to encrypt and decrypt messages.

Categories:
52 Views

The MGWO and GWO code

Categories:
108 Views

We compared the performances of an LwM2M device management protocol implementation and FIWARE’s Ultralight 2.0. In addition to demonstrating the viability of the proposed approach, the obtained results point to mixed advantages/disadvantages of one protocol over the other.

Categories:
161 Views

Reconsructed images (video sequences) and results for the paper: "Adaptive block compressive sensing for distributed video coding"

Instructions: 

All files in attached zip file.

Categories:
49 Views

The dataset includes 2 parts: private and public traffic.

The private traffic is self-captured network traffic of serveral softwares, such as YouTube, Skype, streaming video, totally 16 categories.

The public traffic is an open VPN dataset, including numorous VPN or nonVPN network services, totally 24 categories.

 

Categories:
436 Views

This dataset contains supplementary data and information for 

C. H. Teh, B. K. Chung and E. H. Lim, "Multilayer Wall Correction Factors for Indoor Ray-Tracing Radio Propagation Modeling," in IEEE Transactions on Antennas and Propagation, vol. 68, no. 1, pp. 604-608, Jan. 2020, doi: 10.1109/TAP.2019.2943397.

 

Instructions: 

Everything is in the zip file. Documentation is given in readme.pdf.

 

Categories:
47 Views

Underground UE statistics measurements captured on u-blox SARAN211 NB-IoT device, frequency band 20. Signal waveform captured by means of Rohde&Schwartz TSMW device. The samples were taken along ca. 1600m of level -2 underground tunnel system under Lyngby Campus of Technical University of Denmark.

Categories:
101 Views

This dataset contains supplementary data and information for 

C. H. Teh, B. K. Chung and E. H. Lim, "An Accurate and Efficient 3-D Shooting-and- Bouncing-Polygon Ray Tracer for Radio Propagation Modeling," in IEEE Transactions on Antennas and Propagation, vol. 66, no. 12, pp. 7244-7254, Dec. 2018, doi: 10.1109/TAP.2018.2874519.

Instructions: 

Everything is in the zip file. Documentation is given in readme.pdf.

Categories:
93 Views

Pages