We provide a measurment framework for testbed-driven comparison of Application-Network-Interaction (App-Net) approaches. This repository contains the source coude for Application-Network Interaction building blocks, as discussed in this paper.

All our machines in the testbed run Ubuntu 14.04. For prerequisites concerning the applied Tapas player, please see the according repository.

The provided entities are deployed within our testbed as follows:

To start the tapas instances, message broker, and policy manager, run the startExperiments.sh script. The otption -m indicates the mechanism which shall be applied (spm | qoeff | nade | baseline). The option -b indicates the bandwidth pattern (static | alternating | sawtooth). The possibility to identify an experiment is given by the flag -i. In our deployment, the script is executed on Host1.

$ bash startExperiment.sh -m qoeff -b static -i exp_1

The startExperiment.sh script also starts the message broker on Host2. If, as in our case, the message broker is located on another machine, it must be ensured that it can receive commands from the machine executing startExperiment.sh. In our deployment, we realized this be using netcat. To make the machine hosting the message broker constantly listening, please run the beReady.sh script on the respective machine.

$ bash beReady.sh 

Host 3 acts as a router. On this machines, several tasks are performed.

• We use the tool TraSh for traffic shaping to limit the bandwidth and simulate a bottleneck link
• TraSh is also used for all network control actions, e.g. bandwdith reservation, flow prioritization
• Network monitoring is located on this host
• The Get Request Fetcher (GRF) is used to detect browsing events (only relevant for multi-application scenarios)

To start an experiment, please run the script startExperiments_router.sh. First of all, it limits the bandwidth. The flag -b denotes the bandwidth pattern (static | alternating | sawtooth). The flags -h and -l indicate the bandwidth limits in kbit/s. If static bandwidth should be applied, please use the same values for -h and -l. Furthermore, this script starts the respective network monitoring and network control entities. Please specify the applied mechanism by the -m flag. An experiment ID can be defined with -i. The -g option is used to specify the granularity for throughput probes. For example, if -g 3 is used, the throughput since the last three seconds is queried each third second. Finally, -a specifies the factor for exponentially weighted moving average. If no value is specified, a default value of 0.8 is used.

$ bash startExperiment_router.sh -m qoeff -b alternating -h 3000 -l 1000 -g 2 -a 0.7 -i exp_1

As content server, we use a machine hosting an Apache Server. The server stores several representations of the video Big Buck Bunny.