ance characteristics as compared to client systems. This is the same reason as why a conventional base station (gNB) has different performance requirements (and thus a different implementation) as compared to a conventional UE (mobile phone). Scalability challenge. RSU design is in its infancy, with many options for enhancements in performance to improve the performance/capabilities of the RSU with regards to traffic detection/recognition, algorithmic support, coordination, and SO on. For example: Inclusion of additional inputs to the RSU. Consider inclusion of RADAR/LIDAR; camera; wireless sensing (detection of LTE, 5G, Bluetooth, and other pedestrian- associated RF radiation); ultrasonic; and other sensors intended to enhance the scope of the RSU. This creates a scalability challenge where the main CPU of the RSU will end up becoming a bottleneck, both in terms of connectivity associated with all these sensors, as well as compute requirements to process all input data appropriately. Associated with above is an architectural challenge in how to physically implement the RSU: should the RSU still be a single hardware unit that becomes more bulky/heavy as features evolve and is compromised in where it can be placed, or become distributed where each "sensor" can be placed in the physical location for it to perform optimally? 5G Reduced Capabilities (RedCap) The 5G standard is designed with flexibility in mind, both in terms of hardware/software par- titioning options for implementation as well as flexibility in use cases. The first standardized (Release 15) and well-published use cases, however, center around high-end applications including eMBB and URLLC. Both of these use cases are demanding on the hardware and software implementation complexity and therefore tend to be expensive. As 3GPP releases evolve however, more use cases are being added, including V2X com- munication (sidelink communication channels) and, in Release 17, standardization of lower end use cases that allow for reduced hardware complexity implem