The runtime infrastructure of Eclipse MOSAIC couples different simulators and can’t be run alone and, therefore, it requires pre-installed simulators. Each simulator coupled with the RTI of MOSAIC usually covers a specific domain (e.g. traffic, communication, application, electricity, or other).
Each of the simulators must implement an interface, the so-called
The ambassador communicates with the actual simulator, which is represented by the
For some cases, if the simulator is directly coupled with the RTI (e.g. Application, or cell), the ambassador also
represents the federate. This architecture allows a simple coupling of own simulators.
The following simulators are coupled already with MOSAIC:
|Application Simulation||MOSAIC Application||Application prototyping and simulation.|
|MOSAIC Mapping||Defining simulation entities, traffic, and mapping of applications.|
|Traffic / Vehicle Simulation||Eclipse SUMO||Microscopic Traffic simulation.|
|PHABMACS *||Sub-microscopic vehicle simulation with 3D visualization.
Documentation will be published soon.
|Network / Communication Simulation||OMNeT++||Event-based network simulator for ITS-G5 and cellular communication.|
|ns-3||Event-based network simulator for ITS-G5 and cellular communication.|
|MOSAIC Simple Network Simulator||Simulator for ITS-G5 ad-hoc communication using simplified models.|
|MOSAIC Cell||Simulator for cellular communication.|
|Environment Simulation||MOSAIC Environment||Environmental event simulation.|
|E-Mobility Simulation||MOSAIC Battery *||Simulator for discharging, charging and recuperation of electric vehicles.|
|MOSAIC Charging *||Simulator for requests towards charging stations.|
*) Only part of the MOSAIC Extended bundle.