# Evaluating the Feasibility of Intelligent Blind Road Junction V2I Deployments
## 4 Results
### Discussion  
With the latency and throughput performance results of both connectivity setups presented, the findings and insights as they relate to the network architecture configurations must be discussed.  
From the results presented, it is clear that Configuration 1, where the computational resources are located at or near the FSN(s) and object data are transmitted to the CIV(s), is entirely feasible from a network performance perspective. In particular, the mean latency (10.60 ms) measured for the Sub-6 GHz connectivity setup is well within the stringent requirements for V2X applications as specified by the 3 GPP [8, 9]. Additionally, even with the \(\sim\)120 Mbps effective maximum mean throughput achieved by the Sub-6 GHz, this bandwidth would allow for either a further increase in CAM reporting frequency beyond the busy scenario (20 Hz) for a single FSN, or for several FSN(s) to report simultaneously in the busy scenario.  
Unlike the findings for Configuration 1, the results reveal that Configuration 2, where the computational resources are located within the CIV(s) and sensor data are transmitted across the network, may not be feasible from a network performance perspective. Similar to Configuration 1, the latency performance results for both connectivity setups are within the requirements for V2X applications [8, 9]. However, the throughput performance results for both connectivity setups demonstrate that the bandwidth requirements for different sensor data rates impose a trade-off for Configuration 2 depending on the image quality needs of the object detection algorithms. If the image quality provided by the CCTV Camera (8 Mbps) and Action Camera (50 Mbps) data rates is sufficient for the application, then Configuration 2 is likely feasible with the Sub-6 GHz connectivity setup. It should be noted that given the effective maximum throughput (\(\sim\)120 Mbps) found for the Sub-6 GHz connectivity setup, there is a limit of \(\sim\)15 CCTV Cameras (8 Mbps) or \(\sim\)2 Action Cameras (50 Mbps) sensors that could be supported simultaneously by the network. However, if the image quality, i.e., resolution, frame rate, and compression codec, provided by these data rates is not sufficient and sensors of a calibre similar to the Consumer Camera (150 Mbps) or Automotive Camera (800 Mbps) data rates are required, then the use of a mmWave connectivity setup will be required. It should be noted that while the mmWave connectivity setup can afford a significantly higher bandwidth, this comes at the cost of radio robustness in terms of effective transmission range and susceptibility to noise and interference. Thus, if a mmWave connectivity setup is to be used, it will likely have to be deployed at the region of interest to mitigate the aforementioned shortcomings.  
These findings highlight the scalability of the IPS system. Within the constraints of the single channel used in this study, Configuration 1 can support a large number of FSNs (\(\sim\)2400) during a busy scene (20 Hz CAMs). Whereas, Configuration 2 can support significantly fewer FSNs during a busy scene due to the bandwidth requirements of the chosen sensor, i.e., \(\sim\)15 CCTV Cameras (8 Mbps) FSNs or \(\sim\)2 Action Cameras (50 Mbps) FSNs. Given that the IPS uses a publish-subscribe model, the number of CIVs using the IPS system does not contribute to the scalability of the system. Thus, only the available bandwidth and sensor performance requirements predicate the scalability of the system. As previously mentioned, future technologies such as an mmWave connectivity setup leveraged via carrier aggregation could provide scalability support for the substantial sensor requirements of Configuration 2. Additionally, considerations towards security and privacy will notably affect the performance and scalability of the IPS system. The introduction of security and privacy measures, i.e., encryption, authentication, and access control, will necessarily increase the latency and bandwidth required to access and use the IPS system.