# Positioning by Multicell Fingerprinting in Urban NB-IoT Networks +
## 4 Dataset Description and Analysis
### Data Description and Availability  
Each entry in the datasets collected in Rome and Oslo includes an extensive set of data fields, divided into four categories:  
1. Time stamp, including date, time, and coordinated universal time (UTC);
2. GPS data, including estimates of latitude, longitude, altitude, speed and heading, and the number of satellites used for the estimation;
3. Network data, including the E-UTRA absolute radio frequency channel number (EARFCN), the corresponding carrier frequency, the NPCI, the mobile country code (MCC), the mobile network code (MNC), the tracking area code (TAC), the cell identity (CI), the eNodeB-ID, and the cell ID. Figure 1: The setup adopted for the measurement campaign in Rome, Italy: R&S TSMA6 mobile network scanner (**a**), GPS antenna (**b**), Samsung S20 5G mobile phone (**c**), RF antenna (**d**), and tablet used to remotely access the ROMES software running in the embedded PC within the TSMA6 scanner (**e**) (image drawn from [33]). Signal data, including the RSSI, SINR, RSRP, and RSRQ values measured for the reference signals transmitted by the eNodeB on each of the two antenna ports used in NB-IoT (Tx0 and Tx1), as well as the power, RSSI, and carrier-to-interference noise ratio (CINR) values measured on the narrowband secondary synchronization signal (NSSS). Note that the list of fields for each category provided above is not exhaustive; more details can be found in the description of the dataset in [41]. Table 1 lists the data fields, indicating the corresponding measurement units and formats, and provides an example value. Not all available data fields were used in this work; the subset adopted includes the latitude and longitude from GPS data, the MNC, NPCI and the eNodeB-ID from the network data, and the RSSI, SINR, RSRP, and RSRQ values averaged over the two antenna ports Tx0 and Tx1 from the signal data. The combined use of NPCI, eNodeB-ID, and MNC was required since the NPCI is not a unique indicator, neither across operators nor within \begin{table}
\begin{tabular}{c c c c} \hline \hline
**Category** & **Data Field** & **Unit/Format** & **Example** \\ \hline \multirow{4}{*}{Time stamp} & Date & dd.mm.yyyy & 23.07.2019 \\ \cline{2-4}  & Time & hh:mm.s & 08:25.5 \\ \cline{2-4}  & UTC & seconds & 1,566,583,704 \\ \hline \multirow{4}{*}{GPS data} & Latitude & degrees & 59.922214 \\ \cline{2-4}  & Longitude & degrees & 10.733242 \\ \cline{2-4}  & Altitude & meters & 46.98 \\ \cline{2-4}  & Speed & m/s & 8.03 \\ \cline{2-4}  & Heading & degrees & 199.36 \\ \cline{2-4}  & Sat & - & 6 \\ \hline \multirow{4}{*}{Network data} & EARFCN & - & 6352 \\ \cline{2-4}  & Frequency & Hz & 811,192,500 \\ \cline{2-4}  & NPCI & - & 243 \\ \cline{2-4}  & MCC & - & 242 \\ \cline{2-4}  & MNC & - & 1 \\ \cline{2-4}  & TAC & - & 40,601 \\ \cline{2-4}  & CI & - & 19,803,492 \\ \cline{2-4}  & eNodeB-ID & - & 77,357 \\ \cline{2-4}  & cell ID & - & 100 \\ \hline \multirow{4}{*}{Signal data} & RSSI-Tx0 & dBm & \(-\)28.4 \\ \cline{2-4}  & RSSI-Tx1 & dBm & \(-\)28.4 \\ \cline{2-4}  & NSINR-Tx0 & dB & 20.84 \\ \cline{2-4}  & NSINR-Tx1 & dB & 26.25 \\ \cline{2-4}  & NSSRP-Tx0 & dBm & \(-\)40.07 \\ \cline{2-4}  & NSSRP-Tx1 & dBm & \(-\)34 \\ \cline{2-4}  & NSSRQ-Tx0 & dB & \(-\)11.65 \\ \cline{2-4}  & NSSRQ-Tx1 & dB & \(-\)5.59 \\ \cline{2-4}  & NSSS-Power & dBm & \(-\)25.3 \\ \cline{2-4}  & NSSS-RSSI & dBm & \(-\)25.3 \\ \cline{2-4}  & NSSS-CINR & dB & \(-\)25.3 \\ \hline \hline \end{tabular}
\end{table} 
Table 1: Data fields included in a data entry and examples of corresponding values. the network of a single operator, due to spatial reuse. Since both datasets include data from multiple operators and cover extensive areas, each set of the RSSI, SINR, RSRP, and RSRQ values in a location was associated with the corresponding \(<\)NPCI, eNodeB-ID, MNC\(>\) triplet in order to avoid any ambiguity. A triplet of \(<\)NPCI, eNodeB-ID, MNC\(>\) is indicated in the following as _unique_ NPCI or simply NPCI.