📊 Diagram: ECU Update System Case Study

🔗 Link to Original Paper/Article

View Full Main Source

📝 Short Description

This diagram illustrates the second case study in the paper, which briefly describes a system focused on updating the ECUs of a truck. The diagram shows the flow of data between the different components in the system. The paper does not describe the structure of these systems as they belong to private companies. For this reason we took the liberty of adding some components to the very brief description that is given.

🔤 Abbreviations

• SW: Software
• ECU: Electronic Control Unit

📖 Extensive Description (if possible)

Starting from the left side of the diagram there is the Driver which sends its credentials to the Authentication & Authorization Service node, which in turn generates a token to the Mobile App node. Another flow on this side is from the Fleet Technology node, which sends ecu_info to the Inventory Manager node, which forwards it to the Update Orchestrator node. From this node the update_instruction data is sent to the Mobile App which also receives the update software from the SW Storage node. When receiving the token, software and update_instruction the Mobile App node then sends the software to the Wifi Dongle , which forwards it to the ECU node. This node then generates update_info and sends it to the Report Update node.

🏷️ Label description

• 🗂️ Data Labels:

  • Data:

    • Credentials: Credentials data from the operator
    • SW: Update Software
    • App: Application
    • FleetTechnology: Technology from the fleet of trucks
    • UpdateInstruction: Instruction to produce the update
    • Token: Token generated by the Authentication & Autherization Service
    • UpdateReport: Report on the update process

• 🏷️ Node Labels:

  • AuthorizedParty:

    • Driver: User which is a driver and is authorized to do the update on the truck

⚠️ Constraints

• None

🚨 Violations

• None