# Dynamic QoS Management for a Flexible 5G/6G Network Core: A Step toward a Higher Programability
## 5 Testbed Design
### Methodology Implementation
\begin{table}
\begin{tabular}{l c c c c c c c c c c c c c c} \hline \hline  & \multicolumn{4}{c}{**Scenario 1**} & \multicolumn{4}{c}{**Scenario 2**} & \multicolumn{4}{c}{**Scenario 3**} & \multicolumn{4}{c}{**Scenario 4**} & \multicolumn{4}{c}{**Scenario 5**} \\ \hline Slice & \multicolumn{3}{c}{WEBMM} & SEC & \multicolumn{3}{c}{WEBMM} & SEC & \multicolumn{3}{c}{WEBMM} & SEC & \multicolumn{3}{c}{WEBMM} & SEC & \multicolumn{3}{c}{WEBMM} & SEC & \multicolumn{3}{c}{WEBMM} & SEC \\ \hline Download Mbps & 90 & X & 10 & 50 & 40 & 10 & 3 & 6 & 1 & 4 & 4 & 2 & 8 & X & 2 \\ \hline Upload Mbps & 50 & X & 50 & 30 & 20 & 50 & 1.5 & 1 & 2.5 & **1.2** & 0.3 & 3.5 & 1.5 & X & 3.5 \\ \hline \hline \end{tabular}
\end{table} 
Table 4: Calculation of max-rates in different scenarios. \begin{table}
\begin{tabular}{l c c c c c c c c c c c c c c c c} \hline \hline  & \multicolumn{4}{c}{**Scenario 1**} & \multicolumn{4}{c}{**Scenario 2**} & \multicolumn{4}{c}{**Scenario 3**} & \multicolumn{4}{c}{**Scenario 4**} & \multicolumn{4}{c}{**Scenario 5**} \\ \hline Slice & WEB & MM & SEC & WEB & MM & SEC & WEB & MM & SEC & WEB & MM & SEC & WEB & MM & SEC \\ \hline Service groups running & \(\surd\) & \(\times\) & \(\surd\) & \(\surd\) & \(\surd\) & \(\surd\) & \(\surd\) & \(\surd\) & \(\surd\) & \(\surd\) & \(\surd\) & \(\surd\) & \(\surd\) & \(\times\) & \(\surd\) \\ \hline Download \(\%\) & 90 & X & 10 & 50 & 40 & 10 & 50 & 40 & 10 & 40 & 40 & 20 & 80 & X & 20 \\ \hline Upload \(\%\) & 50 & X & 50 & 30 & 20 & 50 & 30 & 20 & 50 & 20 & 10 & 70 & 30 & X & 70 \\ \hline Download Min (Kbps) & 2000 & X & 500 & 2000 & 6000 & 500 & 2000 & 6000 & 500 & 1000 & 4000 & 200 & 1000 & X & 200 \\ \hline Upload Min (Kbps) & 500 & X & 2000 & 500 & 500 & 2000 & 500 & 500 & 2000 & 1200 & 200 & 2000 & 1200 & X & 2000 \\ \hline Priority & 3 & X & 1 & 3 & 2 & 1 & 3 & 2 & 1 & 1 & 3 & 2 & 1 & X & 2 \\ \hline Link bandwidth cap & \multicolumn{4}{c}{\(100/100\) Mbps} & \multicolumn{4}{c}{\(100/100\) Mbps} & \multicolumn{4}{c}{\(100/5\) Mbps} & \multicolumn{4}{c}{\(10/5\) Mbps} & \multicolumn{4}{c}{\(10/5\) Mbps} \\ \hline \hline \end{tabular}
\end{table} 
Table 3: Scenario parameters. Figure 7 shows the base station queue parameters in Scenario 2. It also shows the max-queue size (max-rate), min queue size (min-rate), burst rate, and statistics for transferred packets, bytes, and errors for each slice. Further, on Figure 8, we show the flow table content, with proactive flows on base station OVS in Scenario 2. During this process, we perform multiple cycles. We have noticed consistent results regarding the measured performance parameters, and the only observed variance is caused by the random size of the WEB service response. In Figure 9, we present test results, which show the bandwidth utilization in different test scenarios. The first scenario represents a baseline setup where all service groups have the required bandwidth. The WEB service takes up to 40 Mbps, so every transaction executes in less than one second. The SEC upload streaming service also demonstrates its behavior under baseline conditions. Figure 8: Base station flow table in Scenario 2. Figure 7: Base station OVS queue parameters in Scenario 2. Figure 9: Bandwidth usage during testing process. In Scenario 2, we introduce a new service group (in our case, MM service) by defining a new SQL record. After Scenario 2 starts, the SDN controller in charge of the observed slice initiates the creation of new queues for that service group. The new MM service does not suffer from performance degradation because there is still enough shared bandwidth for all traffic. Scenario 3 introduces bandwidth reduction on the shared link, which causes congestion in both directions (upload and download). In the download direction, the link has a maximum bandwidth of 10 Mbps, while the WEB and MM services together require around 47 Mbps of bandwidth for uninterrupted operation.