# Evaluating the Feasibility of Intelligent Blind Road Junction V2I Deployments
## 3 Experimental Methodology
### Measurement Plan  
To evaluate the outlined configurations for the IPS, a series of potential measurement runs were identified. Each of the identified measurement runs was chosen to encapsulate data rates that would potentially be generated by an FSN in each of the outlined configurations. For each of the selected data rates, as described in Table 1, 3 measurement runs of 3 min in duration were conducted using iPerf. In the case of the additional mmWave setup for Configuration 2, an additional set of measurements was repeated using the sensor data rates where the Sub-6 Hz setup notably drops in performance. Latency measurements were conducted with the ping utility in the same format, i.e., 3 runs, each 3 min in length, repeated before each of the aforementioned iPerf measurement runs.  
Figure 5: Pseudo–IPS setup with a private 5G NR standalone network used to conduct measurements.  
In Configuration 1, where only object data are transmitted from the FSN(s) to the CIV(s), data rates were chosen to represent the amount of activity in the scene, i.e., a little, some, or a lot of activity. Using the specifications for the CAM message type (300 bytes for each CAM at 10 Hz [8,46,59]) results in a data rate of \(\sim\)25 kbps. For the purposes of this work, this data rate will represent a moderate amount of activity in a scene, thus data rates for a quiet and busy scene can be represented by half (5 Hz-12.5 kbps) and double (20 Hz-50 kbps) the data rate for a moderate scene, respectively.  
In Configuration 2, where sensor data are transmitted from the FSN(s) to the CIV(s), data rates were chosen based on common camera architectures with varying resolutions, frame rates, and compression levels. While it is unlikely that any of these specific camera architectures will satisfy all of the possible FSN scenarios, they will serve as reference points of known video performance for given data rates in Table 1.  
Current generation CCTV Cameras [60] use high resolution (8 MP) sensors with low frame rates (10-20 frame/s) and high compression ratios (H.265), yielding up to 8 Mbps of bandwidth, enabling the storage of large volumes of data. Mobile phones [61] and action cameras [62] most commonly capture 8 MP videos at 30 frames/s with a lower compression ratio (H.265), yielding up to 50 Mbps bandwidth to achieve higher image quality at the expense of storage. Recent trends towards HDR displays have also pushed manufacturers of consumer cameras to implement HDR video captures, that require more storage of colour information (more bits per pixel). Capturing HDR video, with 10 or 12 bits per pixel, causes the bit rate to increase to approximately 150 Mbps. Current production vehicles with advanced ADAS features commonly have HDR cameras (12-bit) [63] to deal with the challenging dynamic range conditions of the outdoors and typically have 2 MP sensors that capture 30 frames/s. These camera systems minimise latency by not compressing the image and therefore have by far the largest bit rate of approximately 800 Mbps, which is set to rise to 3 Gbps for next-generation 4 K video cameras.