## 6 CAMINO-Core Logging Features  
The CAMINO-Core implementation supports data logging of all the messages being transmitted and received via the southbound Interface from the different wireless communication modules (ITS-G5, C-V2X PC5 and Cellular modem). The data are logged locally on  
Figure 3: Information presented on the Human-Machine Interface (HMI) when the vehicle is in the Infrastructure to Vehicle Information (IVI) relevance zone.  
the device where the CAMINO-Core is running, in logfiles. Each time the CAMINO-Core application is started, a new log directory is created using the current timestamp as the directory name, <_yyyyMMDDTHHMMss_>, to avoid overwriting any of the locally stored logfiles. The logdata can also be pushed in real-time to a remote database for demo purposes but this is not recommended for evaluation, as logdata can be lost when the remote connection fails.  
The following data can be logged by CAMINO-Core:  
* Transmitted/received messages via the southbound Interface (ITS-G5, C-V2X PC5, 4G/5G) for CA, IVI, DEN services and forwarded messages
* Incoming/outgoing messages via the northbound Interface
* Positioning/speed data retrieved from the GNSS  
All the data that are logged by CAMINO-Core on the southbound, as well as recorded positioning/speed data, follow the InterCor logging format [20]. As an example, in Table 3, a summary is given of the logging format that is used by CAMINO for the transmitted and received C-ITS messages, listing all the data fields that are recorded in local logfiles.  
To analyze the local logfiles, central post-processing evaluation tools are implemented. The data in the logfiles is parsed and centrally recorded in a database. Several scripts are provided to analyze this data in order to calculate well-defined KPIs (e.g., latency, packet delivery rate, range, etc.) and present them in graphs.  
\begin{table}
\begin{tabular}{c c c c c} \hline \hline
**Name** & **Type** & **Range** & **Unit** & **Description** \\ \hline log\_timestamp & long & 0 to \(2^{42}-1\) & msec & \begin{tabular}{c} Timestamp at which the \\ log\_stationid logs the data row, \\ elapsed time since midnight \\ January 1 st 1970 UTC \\ \end{tabular} \\ \hline log\_stationid & long & 0 to \(2^{32}-1\) & n/a & \begin{tabular}{c} Unique id of the host that logs \\ this log data row \\ \end{tabular} \\ \hline log\_applicationid & 0 to \(2^{32}-1\) & long & n/a & \begin{tabular}{c} Unique id of the application, \\ instance or thread, on the \\ log\_stationid host that logs this \\ log data row \\ \end{tabular} \\ \hline log\_action & enum & \begin{tabular}{c} [’SENT’, \\ ’RECEIVED’] \\ \end{tabular} & n/a & \begin{tabular}{c} Action that triggered the logging \\ event \\ \end{tabular} \\ \hline stationid & long & 0 to \(2^{32}-1\) & n/a & \begin{tabular}{c} Unique id of the station that has \\ sent this log data row \\ \end{tabular} \\ \hline log\_communicationprofile & enum & \begin{tabular}{c} [TTS\_G5’, ’LTE\_V2X’, \\ ’CELLULAR’] \\ \end{tabular} & n/a & \begin{tabular}{c} Communication profile, medium \\ or path used to send or receive \\ the message \\ \end{tabular} \\ \hline log\_messagetype & enum & \begin{tabular}{c} [’ETSICAM’, \\ ’ETSLDENM’, \\ ’ISO.IVI’] \\ \end{tabular} & n/a & \begin{tabular}{c} Type of standardised message, \\ used for automated processing \\ in case multiple message types \\ are combined in a single log file \\ \end{tabular} \\ \hline generationtimestamptai & long & 0 to \(2^{42}-1\) & msec & \begin{tabular}{c} International Atomic Time when \\ message was generated \\ \end{tabular} \\ \hline generationtimestamp & long & 0 to \(2^{42}-1\) & msec & \
\begin{tabular}{c} Coordinated Universal Time \\ when message was generated \\ \end{tabular} \\ \hline asn1 data & string & n/a &
\begin{tabular}{c} HEX string of UPER encoded \\ ASN.1 message such as a CAM, \\ DENM, IVI \\ \end{tabular} \\ \hline \hline \end{tabular}
\end{table}
Table 3: Logging format.