# Crowdsourcing Framework for QoE-Aware SD-WAN +
## 5 Test Bed Implementation
### Use Case Scenarios
A number of scenario files of 40 s in length with timestamped events were used, where delay and loss were changed during the video streaming session. For each scenario, we streamed the videos with different streaming protocols, recorded all output videos, and ran a comparative analysis. In order to examine the performance of real-time QoE feedback on SD-WAN operation, an SDN-based rerouting experiment was also set up to demonstrate that QoE feedback can be captured and processed in real time during live video streaming session. Feedback can be sent on the spot to the SDN controller to alert the controller of issues in the steaming service. Our intention was to demonstrate how traffic rerouting could be done instantly on the basis of QoE feedback and how the results would compare to the perception of a participant. \begin{table}
\begin{tabular}{c c c c c c} \hline \hline
**Time** & **0 s** & **10 s** & **20 s** & **30 s** & **35 s** \\ \hline \multicolumn{6}{c}{**Scenario 1**} \\ \hline
**Delay** & 10 ms & 10 ms & 50 ms & 0 ms & 25 ms \\
**Loss** & 1\% & 0\% & 0\% & 1\% & 1\% \\ \hline \multicolumn{6}{c}{**Scenario 2**} \\ \hline
**Delay** & 70 ms & 10 ms & 5 ms & 5 ms & 25 ms \\
**Loss** & 0\% & 1\% & 1\% & 0\% & 0\% \\ \hline \multicolumn{6}{c}{**Scenario 3**} \\ \hline
**Delay** & 75 ms & 0 ms & 10 ms & 35 ms & 5 ms \\
**Loss** & 1\% & 0\% & 1\% & 0\% & 1\% \\ \hline \multicolumn{6}{c}{**Scenario 4**} \\ \hline
**Delay** & 35 ms & 80 ms & 5 ms & 25 ms & 5 ms \\
**Loss** & 0\% & 0\% & 1\% & 1\% & 0\% \\ \hline \multicolumn{6}{c}{**Scenario 5**} \\ \hline
**Delay** & 35 ms & 45 ms & 45 ms & 25 ms & 65 ms \\
**Loss** & 1\% & 0\% & 1\% & 0\% & 0\% \\ \hline \hline \end{tabular}
\end{table} 
Table 2: HPC experiment scenarios. For this scenario, a network of three hosts was created: one acting as a streaming server, the second acting as a client, and the third acting as an non-namespace server which can communicate with ONOS SDN controller. The hosts were connected through a network of 10 OVS switch devices with 22 links and 50 flows, where three edge-disjoint paths exist between the client and the server. The choice of this network topology and the number of flows were to allow the network controller to discover alternate paths without having to solve a full optimization problem (which was not part of this study and will be considered in future work). RTP was used as the default streaming protocol. The network topology is shown in Figure 6.  
During video streaming experiences, network degradation scenarios were imposed to affect the quality of the network, in order to indicate if and by how much the participating user would be able to detect such changes during video streaming, and how these changes would affect their QoE. Furthermore, the timing of their QoE feedback was recorded within the time window when QoS parameter change events occurred. Another objective of this experiment was to evaluate how streaming protocols would be able to adapt to these changing events, and if all or some of these changing events would be noticeable to participants or not.