# A Modular Experimentation Methodology for 5G Deployments: The 5 GENESIS Approach
## 5 Experimental Setup
### ED Definition  
In this section, we show the EDs for three experiments, which have been executed in the UMA 5G deployment while using the methodology presented above. Section 6 analyzes the obtained results. We have defined a first experiment, named Experiment 1, aiming at quantifying throughput and latency KPIs in our deployment under LoS and NLoS scenarios. Listing 3 shows the ED for this experiment. In 5 GENESIS terms, Experiment 1 is a standard experiment, which sequentially executes two standard test cases, i.e., TC_THR_UDP and TC_RTT, in SC_LoS_PS and SC_NLoS_PS scenarios, by using the default available slice and a single 5G NR device, denoted UE_1. Because the applications are already defined in the test cases and no NSs are used, the Application and NSs fields of the ED can be omitted. ```
1<
2 ExperimentType:Standard
3 Automated:Yes
4 TestCases:TC_THR_UDP,TC_RTT
5 UEs:UE_1
6 Slice:Default
7 Scenario:SC_LoS_PS,SC_NLoS_PS
8 ExclusiveExecution:yes
9 Version:2.0
10
11
12
13
14
15 ExperimentType:Standard
16 Automated:Yes
17 TestCases:TC_THR_UDP,TC_RTT
18 UEs:UE_1
19 Slice:Default
20 Scenario:SC_LoS_PS,SC_NLoS_PS
210 ExclusiveExecution:yes
22 Version:2.0
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
390
391
392
393
400
411
420
431
432
433
444
455
456
457
458
4590
460
471
472
473
474
475
476
4778
4790
480
4910
4920
493
4944
5951
5952
59



Finally, we define a third experiment, i.e., Experiment 3, to showcase the flexibility of the proposed methodology. In particular, Experiment 3 highlights how the methodology can be used for benchmarking purposes, and for underlining peculiar behaviors in off-the-shelf devices, requiring further inspection; hence, as reported in Listing 5, we execute the TC_THR_UDP test case in the SC_LoS_PS scenario, while using UE_1 and a second 5G NR device from a different vendor, denoted UE_2. ```
1:
2 ExperimentType:Standard
3 Automated:Yes
4 TestCases:TC_THR_UDP
5 UEs:UE_1,UE_2
6 Slice:Default
7 Scenario:SC_LoS_PS
8 ExclusiveExecution:yes
9 Version:2.0
10}
```

Listing 5: ED for Experiment 3 (evaluation of throughput KPI in two 5G NR devices, UE_1 and UE_2). ## 6 Experimental Results

In this section, we discuss the results that were obtained by executing the experiments defined in Section 5. ### KPI Nalidation across Different Scenarios

We start with Experiment 1, which quantifies throughput and latency KPIs in LoS vs. NLoS scenarios (and PS activated), and it provides an overview of the full usage of the proposed methodology. Tables 4 and 5 report several statistical indicators (and corresponding 95% confidence intervals) for TC_THR_UDP and TC_RTT test cases in both scenarios, respectively. Along with the main KPIs, i.e., UDP throughput for TC_THR_UDP and RTT for TC_RTT, both tables also report an overview of selected complementary measurements, in terms of the average values measured over the entire test case duration. As regards TC_THR_UDP, we observe that the UDP throughput in the LoS scenario is stable at around 180 Mbps, and significantly drops in NLoS, where it achieves an average value of 15 Mbps. Focusing on LoS scenario, we see that such a throughput is rather far from the theoretical maximum calculated in Section 5.3. Because our monitoring probes also allow for the collection of throughput samples at different protocol stack layers and, in particular, at Packet Data Convergence Protocol (PDCP), we investigate this aspect more in detail and report the results in Experiment 3, where we also compare the UE_1 and UE_2 performance (cf. Section 6.3). When considering TC_RTT, we observe an average RTT of about 12 ms in the LoS scenario, which doubles to 26 ms in the NLoS scenario. In the second scenario, we also see larger variance in the KPI samples compared to the first scenario, which instead appears extremely stable.