No abstract

No abstract

To meet the challenges in software testing for automated vehicles, such as increasing system complexity and an infinite number of operating scenarios, new simulation methods must be developed. Closed-loop simulations for automated driving (AD) require highly complex simulation models for multiple controlled vehicles with their perception systems as well as their surrounding context. For the realization of such models, different simulation domains must be coupled with co-simulation. However, widely supported model integration standards such as functional mock-up interface (FMI) lack native support for distributed platforms, which is a key feature for AD due to the computational intensity and platform exclusivity of certain models. The newer FMI companion standard distributed co-simulation protocol (DCP) introduces platform coupling but must still be used in conjunction with AD co-simulations. As part of an assessment framework for AD, this paper presents a DCP compliant implementation of an interoperable interface between a 3D environment and vehicle simulator and a co-simulation platform. A universal Python wrapper is implemented and connected to the simulator to allow its control as a DCP slave. A C-code-based interface enables the co-simulation platform to act as a DCP master and to realize cross-platform data exchange and time synchronization of the environment simulation with other integrated models. A model-in-the-loop use case is performed with the traffic simulator CARLA running on a Linux machine connected to the co-simulation master xMOD on a Windows computer via DCP. Several virtual vehicles are successfully controlled by cooperative adaptive cruise controllers executed outside of CARLA. The standard compliance of the implementation is verified by exemplary connection to prototypic DCP solutions from 3rd party vendors. This exemplary application demonstrates the benefits of DCP compliant tool coupling for AD simulation with increased tool interoperability, reuse potential, and performance.

Numerous systems engineering (SE) methods for the model-based and textual specification of systems focus on managing complexity solely by partitioning the system based on physical structures or by defining different views of the system and therefore reach their limits in agile development. The increasing demand for an agile system development requires an agile systems engineering procedure for the model-based and textual top-down specification of systems. Although function-based development, This is an open access article under the terms of the Creative Commons Attribution License, which permits use, distribution and reproduction in any medium, provided the original work is properly cited.

No abstract