# A Modular Experimentation Methodology for 5G Deployments: The 5 GENESIS Approach
## 4 Formalization of the Experimentation Methodology
### Slice  
Network slicing support is part of the new Service-Based Architecture (SBA) specified by 3 GPP in TS 23.501 [46]. A network slice is defined as \"a complete logical network (providing Telecommunication Services and Network Capabilities) including Access Network (AN) and Core Network (CN)\". The management and orchestration of network slices is specified in 3 GPP TR 28.801 [47]. The list of Standard Slice Types (SST) specified in [46] includes three slices: _eMBB slice_, suitable for 5G eMBB services; _URLCC slice_, oriented towards 5G URLLC use cases; and, _Milot slice_, for massive IoT and mMTC applications. However, the standard also contemplates the use of non-standard slices.  
In the 5 GENESIS methodology, the slice specifies the E2E resources specifically allocated in the network in order to fulfill the performance requirements of the solution under test. A full description of the slicing mechanisms supported in 5 GENESIS can be found in [48] and in the corresponding GitHub repository [49]. The template that is used to define the specific slice configuration is based on the Generic Network Slice Template (GST) defined by the Global System for Mobile Communications Association (GSMA) in [50], and Listing 1 shows a GST example. Hence, a testbed defines different instances of the slice template, one per supported slice. Subsequently, the slice is configured, depending on the capabilities of the infrastructure layer, which is, the mapping between the parameters defined in the template and the values configured in each network component depends on the available equipment, which can range from commercial base stations to emulators or software-defined solutions. However, the mapping is transparent to experimenters and vertical use case owners, which just need to choose among the list of slices offered by the testbed. The selection that is made by the experimenter is finally used to fill in the slice ID field in the ED.  
\begin{table}
\begin{tabular}{c c} \hline \hline
**Scenario ID** & **SC\_LoS\_PS** \\ \hline Radio Access Technology & 5G NR \\ Standalone/Non-Standalone & Non-Standalone \\ LTE to NR frame shift & 3 ms \\ Cell Power & 40 dBm \\ Band & n78 \\ Maximum bandwidth per component carrier & 40 MHz \\ Subcarrier spacing & 30 kHz \\ Number of component carriers & 1 \\ Cyclic Prefix & Normal \\ Number of antennas on NodeB & 2 \\ MIMO schemes (codeword and number of layers) & 1 CW, 2 layers \\ DL MIMO mode & 2 \(\times\) 2 Close Loop Spatial Multiplexing \\ Modulation schemes & 256-QAM \\ Duplex Mode & TDD \\ Power per subcarrier & 8.94 dBm/30 kHz \\ TDD uplink/downlink pattern & 2/8 \\ Random access mode & Contention-based \\ Scheduler configuration & Proactive scheduling \\ User location and speed & Close to the base station, direct line of \\  & sight, static \\ Background traffic & No \\ Computational resources available in the virtualized infrastructure & N/A \\ \hline \hline \end{tabular}
\end{table}
Table 3: Scenario template applied to a 5G NR NSA deployment with Line of Sight (LoS) between gNB and UE. The scenario (SC) is denoted SC_LoS_PS, where PS stands for Proactive Scheduling, a vendor-specific configuration available in the gNB (cf. Section 5.3 for more details).  
```
1\"base_slice_descriptor\":{
2\"base_slice_des_id\":\"AthonetEPC\",
3\"coverage\":[\"Campus\"],
4\"delay_tolerance\":true,
5\"network_DL_throughput\":{
6\"guaranteed\":100.000
7},
8},
9\"ue_DL_throughput\":{
10\"guaranteed\":100.000
11},
12\"network_UL_throughput\":{
13\"guaranteed\":10.000
14},
15\"ue_UL_throughput\":{
16\"guaranteed\":10.000
17},
18\"mtu\":1500
19},
```  
Listing 1: Instantiation of the Generic Network Slice Template. Throughput and Maximum Transfer Unit (MTU) values are given in kbps and bytes, respectively.