# A Novel Approach to Multi-Provider Network Slice Selector for 5G and Future Communication Systems
## 6 Experimental Evaluation
### Environment Description  
Given the need for a network traffic dataset to explore, validate, and develop ML models, this work followed the standard behavior presented in several articles by building the scenario and producing a dataset based on a simulation. This behavior was understandable due to the wide and diverse characteristics of computer network scenarios and needs.  
The test environment was implemented using the network software emulator Graphical Network Simulator 3 (GNS3) to provide the infrastructure for the virtualized network functions (NFV Infrastructure). The scenario was composed of 05 UEs transmitting at different traffic rates, as specified in Table 2, for the set of collections performed. In addition, implementation in the gNodeB was performed through a software module (CUPS--Control User Plane Split) running on an Ubuntu Linux 16.04 LTS VM (Maintained by Canonical based in London, UK) with Kubernetes, based on the OpenAirInterface (openair-k8s) project [81].  
Regarding the network edge (Edge Computing), a docker container was used with the deployment of the SDN controller OpenDayLight, to implement the UPF, responsible for the separation and identification of data flows. The Network Data Analytics Function (NWDAF) was implemented in an Ubuntu Linux 16.04 LTS VM with the Anaconda Python 3 framework, to implement the analysis functions and the data mining pipeline, using the Jupyter notebook tool and the Numpy, Pandas and Sklearn libraries.  
Although the scenario presented the core of the 5G architecture (5G Core--5 GC), none of the Network Functions (NFs) relevant to the core were implemented, such as Network Exposure Function (NEF), Network Repository Function (NRF), Policy Control Function (PCF), Unified Data Management (UDM), Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF) and Application Function (AF), as shown in Figure 6. These network functions will be implemented through ETSI NFV OSM, which will use the SLA template generated by the NSSF DAF framework.  
However, three vertical slices were considered, as detailed below, delivered at the network edge by three different 5G providers, according to the 3 GPP TS 22.186 V16.2.0 and 3 GPP TS 22.261 V16.14.0 specifications [82; 83]. The composition of each of the slices is given by the junction of Virtual Networks (VNs)' \(N1\) to N6, under the domain of three different Internet Service Providers--ISPs (X, Y, Z) according to Table 3. Regarding the representation of services, an Iperf server was used for different traffic transmission rates of the Constant Bit Rate (CBR) type.  
As a result, for each of the 11 collections performed in the simulation process, a trace file was obtained for each UE containing a dataset of 33 iterations. Iteration data comprises:  
\begin{table}
\begin{tabular}{c c c c c c} \hline \hline
**Collection** & **UE 1 (Mbps)** & **UE 2 (Mbps)** & **UE 3 (Mbps)** & **UE 4 (Mbps)** & **UE 5 (Mbps)** \\ \hline
01 & 20 & 47 & 07 & 09 & 06 \\
02 & 22 & 45 & 06 & 12 & 08 \\
03 & 24 & 49 & 09 & 10 & 06 \\
04 & 32 & 55 & 14 & 18 & 12 \\
05 & 25 & 50 & 10 & 05 & 02 \\
06 & 45 & 70 & 30 & 05 & 03 \\
07 & 12 & 25 & 05 & 20 & 30 \\
08 & 20 & 22 & 24 & 02 & 07 \\
09 & 08 & 28 & 05 & 10 & 03 \\
10 & 32 & 62 & 22 & 15 & 08 \\
11 & 10 & 15 & 05 & 02 & 15 \\ \hline \hline \end{tabular}
\end{table}
Table 2: Specification of injected traffic during 5 min for each collection.  
Figure 6: Illustration of the simulation environment architecture for producing network traffic.  
the amount of transferred bytes, bandwidth used, transport protocol, latency, jitter and packet loss. Each collection was carried out for a period of 5 min. These raw log data are thus the starting point for carrying out the data analysis process.