## 2 Measurement System and Data Collection Methodology
### Data Collection Methodology  
A set of measurement campaigns was performed at the second floor of the Department of Information Engineering, Electronics, and Telecommunications (DIET) of Sapienza University of Rome, Italy. All measurement campaigns were conducted statically in different indoor locations. Figure 2 shows the map of the second floor of the DIET Department, along with the eight specific locations where measurement campaigns were performed. Location 1 and Location 4 are laboratories, Location 8 is a study hall, and all other locations are offices. Green, blue, and red lines represent walls, windows, and doors, respectively. Figure 1: The system adopted for the measurement campaign: R&S TSMA6 toolkit (**a**), GPS antenna (**b**), 5G-capable device (**c**), RF antenna (**d**), and ROMES software (**e**). Note that ROMES runs in the laptop within the TSMA6 toolkit (**a**); the tablet in (**e**) was only used as a remote monitor, connected via Wireless Local Area Network (WLAN) to TSMA6. Figure 2: Measurement locations at DIET Department. Green, blue, and red lines represent walls, windows, and doors, respectively. In total, 18 measurement campaigns were performed at the eight locations. During these measurement campaigns, multiple 5G PCIs from four different operators were detected in Band n78. However, the present dataset focuses on the two 5G operators resulting in the highest number of data samples. We refer to these two operators as Op1 and Op2, operating at carrier frequencies of 3649 MHz and 3725 MHz, respectively. Figure 3 shows the PCIs detected at each location for both operators and included in the dataset. Figure 3: PCIs included in the dataset at each location for Op1 (**a**) and Op2 (**b**). Once the measurement campaigns were executed, the corresponding data were exported using ROMES [38]. It was observed that both operators deploy a 5G NR system with a sub-carrier spacing of 30 kHz. It was also noticed that Op1 adopts a beam-based transmission scheme where each PCI transmits multiple SSBs (up to eight SSBs). On the contrary, each PCI of Op2 transmitted a single SSB. A detailed discussion on beam-based transmission is given in [39]. However, it can be observed that due to different propagation conditions, a different number of SSBs was detected at different locations, with a maximum of eight SSBs detected. Moreover, the received power of each SSB also differs due to the direction of the beams associated to the SSBs. Figure 4 shows an example of the received power measured at Location 1 for all the SSBs of the same PCI of Op1 and the unique PCI/SSB pair of Op2. For Op1, the average and median of the received power of SSB 6 are higher than all the other SSBs of Op1. For this reason, SSB 6 is defined as the _strongest_ SSB of Op1 at Location 1. Following the above definition of strongest SSB, the dataset in this paper provides data on the strongest SSBs for each PCI of Op1 at each location, i.e., those SSBs having the highest average Reference Signal Received Power (RSRP) at each measurement location. For Op2, since each PCI transmits only one SSB, the dataset provides data on a single PCI/SSB pair. Ultimately, the dataset is composed of so-called channel power delay profiles (PDPs). Each PDP represents a channel measurement at a given location and time. Since the PDP is measured over SSB signals, each PDP sample in the dataset corresponds to a detected PCI/SSB pair. Moreover, since the propagation channel is composed by several propagation paths, each PDP includes its paths with their absolute propagation time in microseconds (\(\upmu\)s) and received power (in dBm) values. The total PDP in-band power level is also provided in the dataset (in dBm). From the PDP, various propagation parameters can be calculated, such as the number of paths, inter-arrival times, root mean square delay spread, and mean excess delay. A comprehensive discussion and analysis on such propagation parameters, also including a correlation analysis for them, can be found in [39].