# Results and Achievements of the ALLIANCE Project: New Network Solutions for 5G and Beyond
## 7 The RINA Domain
### QoS Support Evaluation  
In this experiment, we compared two cases: in the first one, we have RINA with QoS support in all layers (called **full RINA**); in the second one, the application-specific QoS requests cannot cross layers, meaning the MPN layer is not able to allocate SPN flows with given QoS differentiation (called **TCP/IP-like**). In full RINA, QTA-Mux is thus available at both SPN and MPN DIFs. Four QoS Cubes (A1, A2, B1, B2) have been considered in the MPN DIF, according to the 2 \(\times\) 2 Cherish/Urgency (C/U) matrix depicted in Figure 8 (right). Please note here that the C/U matrix describes the operation of the C/U multiplexer within the QTA-Mux policy, able to enforce a bi-dimensional relative QoS Cube differentiation based on delay and loss requirements. For instance, flows over the MPN DIF assigned to QoS Cube A1 will be prioritised with respect to losses (i.e., they will be more cherished) and delay (i.e., they will be served with higher urgency) requirements. In contrast, flows assigned to QoS Cube B1,  
Figure 7: The RINA experiment network: (**a**) The 10-node infrastructure; (**b**) The configuration of the DIFs  
for example, will still be prioritised with respect to losses, but un-prioritised with respect to delay (i.e., they will experience, and thus should tolerate, higher delays). Moving up to the SPN DIF, one additional QoS Cube has been considered to better differentiate among heterogeneous application flows (i.e., with finer granularity). Specifically, the five QoS Cubes offered here are: Gold, Silver, Bronze, Sensitive Best Effort (BE) and BE, as described in the 3 \(\times\) 2 C/U matrix depicted in Figure 8 (left). It is important to remark here that flows assigned to QoS Cubes in the SPN DIF will have to be transmitted over A1, A2, B1 and B2 flows across the MPN DIF. Therefore, an adequate mapping of SPN DIF to MPN DIF QoS Cubes becomes crucial to provide the expected QoS to end-user applications. In the ERASER scenario, both Gold and Silver flows in the SPN DIF are mapped to A1 flows in the MPN DIF, Sensitive BE flows to A2 ones, Bronze flows to B1 ones and, finally, BE flows to B2 flows in the MPN DIF. For the TCP/IP-like case, QoS class differentiation is available at the SPN layer only. Therefore, five different QoS classes are still offered to the application layer but only one class is available at the MPN layer, i.e., all five QoS classes are mapped to a single class in the MPN layer, which performs a First-In First-Out (FIFO) default scheduling policy. To compare these two scenarios, we injected synthetic application traffic with 5 different specific flow characteristics specified in Table 4. In particular, we injected 5 flows of each type between PE3 and HR2, thus allocating 25 bidirectional flows in total over the SPN DIF. Finally, we set the total amount of these traffic to occupy an average of 70%, 80% or 90% of the capacity of the IR1-IR2 link. Table 5 presents all latency (minimum, maximum, average) and packet loss measurements collected in both cases. Due to the lack of space, only measurements under 90% offered load are shown. First and foremost, full RINA seems to properly enforce \begin{table}
\begin{tabular}{c c c c c} \hline \hline
**Application** & **Traffic** & **Details** & **Requirements** & **QoS Class** \\
**Type** & **Distribution** & & & \\ \hline HD video & CBR & CBR bitrate: 1.5 Mbps & No delay & Gold \\ call & & & No losses & \\ \hline Online & ON-OFF & ON-OFF periods: 4 s-2 s & Avg. delay & Silver \\ gaming & ON-OFF & CBR bitrate during ON: 4 Mbps & No losses & \\ \hline VoIP & ON-OFF & ON-OFF periods: 3 s-3 s & No delay & \\ CBR bitrate during ON: 64 kbps & Tolerant to losses & Sensitive BE \\ \hline File & ON-OFF & ON-OFF periods: 2 s-1 s & Tolerant to delay & Bronze \\ sharing & CBR bitrate during ON: 5 Mbps & Avg. losses & \\ \hline Interactive & Poisson & Avg. bitrate: 2 Mbps & No requirements & BE \\ traffic & & & & \\ \hline \hline \end{tabular}
\end{table}