CoRE4INET is an open source extension to the INET-Framework for the event-based simulation of real-time Ethernet in the OMNEST/OMNeT++ simulation system. It provides real-time Ethernet protocols like AS6802 and AVB. It was created by the CoRE (Communication over Realtime Ethernet) research group at the HAW-Hamburg (Hamburg University of Applied Sciences).
CoRE4INET was first introduced as TTE4INET at the 4th International Workshop on OMNeT++ (2011) along with the 4th International ICST Conference on Simulation Tools and Techniques (2011). You can find the publication and slides here.
Since there were changes necessary to support OMNeT++ 4.2 and INET 2.0, it was completely redesigned. When more real-time Ethernet protocols were added the project was renamed from TTE4INET to CoRE4INET to show that it does not only contain time-triggered protocols.
- Updated dependencies to OMNeT++ 6.0.2 and INET 3.8.3
- Best Efford Crosstraffic
- IEEE 802.1Q / IEEE P802.1p VLANs and Priorities
- Time-Sensitive Networking (TSN)
- IEEE 802.1 Audio/Video Bridging (AVB)
- TTEthernet (AS6802)
- IP over Realtime-Ethernet
If you would like to reference this project please use the following publication:
Philipp Meyer, Franz Korf, Till Steinbach, Thomas C. Schmidt, Simulation of Mixed Critical In-vehicular Networks, In: Recent Advances in Network Simulation, (Antonio Virdis, Michael Kirsche Ed.), ser. EAI/Springer Innovations in Communication and Computing, May 2019. https://doi.org/10.1007/978-3-030-12842-5_10
- Download OMNeT++ 6.0.2
- Install OMNeT++
- Get INET framework 3.8.3
- Disable the feature 'visualization' and all dependent features (causes build issues)
- Get CoRE framework
- GitHub: Clone this repository and import it in OMNEST/OMNeT++
- Working with the framework
- See the documentation in doc/
- Start the examples in the framework
The build state of the master branch is monitored:
Please see INSTALL
Please see doc/
Please see WHATSNEW
The CoRE4INET model is under continuous development: new parts are added, bugs are corrected, and so on. We cannot assert that the implementation will work fully according to the specifications. YOU ARE RESPONSIBLE YOURSELF TO MAKE SURE THAT THE MODELS YOU USE IN YOUR SIMULATIONS WORK CORRECTLY, AND YOU'RE GETTING VALID RESULTS.