## 4 Evaluation Results and Discussion
### Performance Analysis
#### 4.2.4 Analysis of the Second Scenario of \(Vnr_{2}\)  
Regarding the incoming \(VNR_{2}\), which demands a resource allocation operation suitable for XR activities, Table 13 depicts the path evaluations of all the three examined strategies, using the same color gradient pattern as in Table 10. This scenario also focuses on a mapping with the same starting and ending nodes as the previous one. This choice was made to observe the diverse measurements that the Wii-enabled QUAKE metric can provide under different conditions, in contrast to the other monolithic strategies. In the same manner as the previous scenario, the three competing strategies followed their evaluation guidelines. Specifically, the SP algorithm calculates the hop count of all candidate paths. The shortest ones are evaluated as the most preferred and ranked at the top of the ranking table, regardless of other possible user-defined specifications which could highlight longer paths. Similarly, the delay-based strategy follows the same algorithmic steps as before. It calculates the \(L\) values and focuses on the paths with lowest ones, unable to identify whether the specific circumstances demand a more elaborate approach. Following the evaluation stage, the algorithm classifies the candidate paths based only on favorable delay values. Contrariwise, the QUAKE-oriented framework, after matching the examined VNR with the appropriate application category, specifies the most suitable Wii combination that serves the exact user-centric requirements. Hence, the weights \(w_{1},w_{2},w_{3},w_{4}\) adjust the \(PJ\), \(L\), \(RNR^{norm}\), and \(RCR^{norm}\) influence upon the QUAKE values, according to the VNR's requirements, providing the best-suited evaluations and path rankings. Apart from the first option of \(BAF\), common to all the competing methodologies, the inadequacy of the single-constraint strategies to produce acceptable resource mappings is more severe. Specifically, the SP algorithm fails to suggest a path with ample computational and networking resources. As Table 13 reveals, its top selections \(BEF\), \(BEAF\), and \(BAEF\) would be unfit to serve demanding immersive applications, due to unacceptably low \(RNR^{norm}\) and \(RCR^{norm}\) values. \begin{table}
\begin{tabular}{c c c c c c c} \hline \hline
**Path Ordering** & **PJ** & **L** & \(RNR^{norm}\) & \(RCR^{norm}\) & QUAKE & **Hop Count** \\ \hline
**BAF** & 0.114 & 0.070 & 0.066 & 0.302 & 0.147 & 2 \\
**BCDGF** & 0.159 & 0.175 & 0.139 & 0.360 & 0.217 & 4 \\
**BCDHGF** & 0.102 & 0.175 & 0.074 & 0.419 & 0.235 & 5 \\
**BEF** & 0.034 & 0.132 & 0.213 & 0.535 & 0.258 & 2 \\
**BEAF** & 0.080 & 0.149 & 0.164 & 0.709 & 0.308 & 3 \\
**BCDEF** & 0.125 & 0.158 & 0.172 & 0.709 & 0.321 & 4 \\
**BAEF** & 0.170 & 0.114 & 0.180 & 0.709 & 0.324 & 3 \\
**BEDGF** & 0.261 & 0.237 & 0.246 & 0.709 & 0.354 & 4 \\
**BCDEAF** & 0.170 & 0.175 & 0.123 & 0.884 & 0.371 & 5 \\
**BEDHGF** & 0.205 & 0.237 & 0.180 & 0.767 & 0.373 & 5 \\
**BAEDGF** & 0.239 & 0.219 & 0.213 & 0.884 & 0.421 & 5 \\
**BAEDHGF** & 0.341 & 0.219 & 0.148 & 0.942 & 0.439 & 6 \\ \hline \hline \end{tabular}
\end{table} 
Table 13: Produced path enumeration results for case of \(VNR_{2}\). \begin{table}
\begin{tabular}{c c c c c c} \hline \hline \multirow{2}{*}{**QUAKE Value Groups**} & \multicolumn{4}{c}{_L Value Groups_} & \multirow{2}{*}{**Total**} \\ \cline{2-4} \cline{6-6}  & **0.0263–0.126** & **0.126–0.226** & **0.226–0.326** & **0.326–0.426** \\ \hline
0.041–0.141 & 35 & 4 & 0 & 0 & 39 \\
0.141–0.241 & 29 & 82 & 3 & 0 & 114 \\
0.241–0.341 & 0 & 76 & 88 & 2 & 166 \\
0.341–0.441 & 0 & 0 & 37 & 1 & 38 \\ \hline
**Total** & 64 & 162 & 128 & 3 & 357 \\ \hline \hline \end{tabular}
\end{table} 
Table 12: \(VNR_{1}\) use case—QUAKE classification of all paths against \(L\) value groups. Likewise, the delay-driven methodology also selects unsuitable candidates for XR activities, like \(BAEF\), \(BEF\), and \(BEAF\), despite that these top provided paths have adequate \(L\) and \(PJ\) values.