Software as a Product – Road Surface Detection

The automotive software development industry is undergoing a major shift as more and more SAE Level 4 and SAE Level 5 autonomous features are being developed. Many high-tech companies, OEMs, suppliers, IT services, government agencies, contract houses, etc., have invested billions of dollars into software for autonomous features. Automotive software has become much more complex, and OEMs are looking at non-traditional suppliers such as start-ups as sources for these new applications. This has led to the need for improved interaction between electronic control units (ECUs) and the increased use of domain controllers. Developing features such as road surface detection, brake-to-steer, etc. in this new environment presents numerous new challenges and hurdles.

Road Surface Detection software is an example that can provide a safer driving experience for the driver. Knowing the road surface such as icy, gravel, or wet could be used by many systems in a vehicle to improve safety. The road surface detection algorithm is designed to reside in any ECU or domain controller in the vehicle. The feature classification of the algorithm & target ASIL development requires multiple signals from multiple systems. This presents challenges to the authenticity and accuracy of the data, standardization of the interface, and validation of signals. When systems are provided by different suppliers within vehicles, it becomes difficult to exchange information across ownership silos.

This paper will take a deeper dive into the challenges and potential recommendations of providing an algorithm such as road surface detection in the form of software as a product – as well as solving these challenges while understanding the OEMs’ desire to source software functions from diverse suppliers, justify costs and meet safety requirements and launch timing. We will present our solutions in the context of what is currently being considered in the industry – not only focusing on the technical aspects of vehicle implementation, but it does also consider the technical aspects of software delivery concepts such as an automotive software marketplace or consumer enabled to purchase and update.