1. What is RTE
The role of RTE is a bit like an express transfer station or a telephone operator (that is, in the last world, you need to call the operator first, and then transfer the telephone line to the destination through the operator), and its function is to pass a SWC information through RTE is connected to other SWC or BSW. And RTE has the function of managing these information. For example, the receiving SWC is busy (the user you dialed is busy), then RTE is responsible for making the sending SWC wait, or doing other processing; RTE can also trigger SWC, like this When the receiving SWC is sleeping, and the sending SWC sends a message, then the RTE will wake up the receiving SWC. In a word, RTE provides the operating environment of SWC.
2. The role of RTE
- Provides communication management across ECUs/inside ECUs .
- Provide management functions for runnables (triggering, waking up, etc., simply put, runnables need to be mapped to Tasks to run, and this mapping is implemented through RTE)
- Didn't we mention VFB (Virtual Function Bus) before, RTE is the specific implementation of VFB
- In Vector's toolchain, RTE is automatically generated
The following is still the picture of 2.2, and we can refine it to see the relationship clearly. The RTE here is unified management. We don’t need to care about how to connect those specific connections in RTE (because RTE is automatically generated after it is configured in AppL).
