DOI: 10.5281/zenodo.15481726
title: Simulated TSCH dataset using different slotframe matrix configurations

description: The current dataset was obtained by using a specifically developed simulator, to analyze the behavior of a time slotted channel hopping (TSCH) wireless sensor network (WSN), under different operating conditions.

The configuration of the simulator, the characteristics of the network, and the generated traffic patterns are reported in [1].Different configurations of the slotframe matrix, which allows slots to be reserved for specific pairs of nodes, are analyzed.

File "network_topology.pdf" reports the topology of the simulated wireless network.

The four analyzed configurations, which are deeply described in [1], are:



Star, whose slotframe matrix configuration is reported in the "Star.conf" file.

Load, whose slotframe matrix configuration is reported in the "Load.conf" file.

Parallel, whose slotframe matrix configuration is reported in the "Parallel.conf" file.

LPR, whose slotframe matrix configuration is reported in the "LPR.conf" file.


A typical ".conf" file has the following format:# Offset src dest0 4 10 6 20 8 30 10 91 1 0where the first column represents the slot offset, i.e., the time slot in the slotframe matrix (which repeats periodically over time), in which a transmission opportunity is scheduled. Since many concurrent transmissions between different couple of nodes and different channels are possible simultaneously, more than one transmission could be scheduled at the same time. In the example, four transmission opportunities are scheduled in slot offset number 0.The second column of each row represents the source node, while the third column represents the destination node. For instance, the schedule "0 10 9" represents the scheduled transmission at slot offset 0 from the source node 10 to the destination node 9.

 

For each configuration, a corresponding file with the extension ".dat" contains the log generated in the simulation. An example is the following: 00083 72204 FLOW: 6 11 -> 0 LOST: 0 TRIES: 3 LATENCY: 54000082 72156 FLOW: 5 10 -> 0 LOST: 0 TRIES: 4 LATENCY: 346000084 78013 FLOW: 0 4 -> 0 LOST: 0 TRIES: 2 LATENCY: 1240where the transmission in a path from the source node (e.g., 11) to a destination node (e.g., the root node 0) is summarized with a single line in the log.

Each line is composed of the following fields:



<packet number>: an integer number (e.g., 00083) that uniquely identifies a packet transmitted in a multi-hop fashion from the source node to the destination node.

<queuing_time>: the queuing time expressed in terms of number of slots. In the simulation, slots have a length of 20 ms.

<flow_index>: the word "FLOW:" followed by an integer number identifying the flow. The simulation contains seven periodic flows with periods 6001, 6003, 6005, 6007, 6011, 6013, and 6017 expressed in terms of number of slots, for flows with index 0, 1, 2, 3, 4, 5, 6, respectively. For instance, "FLOW: 6" has a period of 6017 slots, which corresponds to 120.34 s (i.e., about 2 minutes).

<path>: an integer value representing the source node of the path, followed by the characters "->", followed by another integer value representing the destination node. For instance, "11 -> 0" represents the transmission in the path between node 11 and node 0.

<lost>: is an indication if the packet was lost in the path ("LOST: 1") or the packet arrived correctly at the destination ("LOST: 0"). A packet is lost if on a given link reached the maximum number of retransmissions.

<tries>: is the sum of the transmissions performed in each link. For instance, the link "10 -> 0" is composed of 3 hops. The value "TRIES: 4" means that a retransmission was performed for one of the links in the path.

<latency>: the transmission latency of the packet from when it was queued to when it reached its destination. The latency is expressed in ms.


For each condition, the number of logged packets (i.e., lines) is 36,742,162, corresponding to 20 years of simulation.

 

In addition, the code of the simulator is provided in the file "TSCHmodeler.zip".

To run the simulations reported in [1], you have to execute the command:



For experiment in Section IV.A



python3 -m TSCHmodeler conf/simple.conf

python3 -m TSCHmodeler conf/simple_1week.conf



For experiment in Section IV.B



python3 -m TSCHmodeler conf/star_minimal.conf for the star minimal configuration

python3 -m TSCHmodeler conf/star_load.conf for the load minimal configuration

python3 -m TSCHmodeler conf/star_parallel.conf for the parallel minimal configuration

python3 -m TSCHmodeler conf/star_LPR.conffor the LPR minimal configuration



For experiment in Section IV.C



python3 -m TSCHmodeler conf/large_40_nodes.conf




 

References:[1] Stefano Scanzio, Pietro Chiavassa, Gabriele Formis, Giacomo Paolini, and Gianluca Cena, "A Lightweight Simulation Environment for TSCH-based Wireless Sensor Networks" under review (the paper will be linked and made available open-source once accepted).