
π Automotive Β· Sequence
How a carmaker updates vehicle software over the air: campaign targeting, owner consent, download, safe installation and reporting.
Drawing diagramβ¦
Vehicle OTA sequence: the OEM creates an update campaign for a model and VIN range, the OTA backend notifies the vehicle's telematics unit, the car downloads the signed package over 4G in the background, the owner is asked in the app and on the dashboard to install when parked, the vehicle checks battery and parking state, installs to each ECU with signature checks, reboots, verifies and reports success (or rolls back) to the backend.
sequenceDiagram actor OEM as OEM Engineer participant OTA as OTA Backend participant TCU as Vehicle TCU participant ECU as Vehicle ECUs actor Owner OEM->>OTA: Campaign: Model X, VIN range OTA->>TCU: Update available TCU->>OTA: Download signed package (4G) TCU->>Owner: Install now? (app and dashboard) Owner-->>TCU: Install tonight, parked TCU->>TCU: Check battery above 50%, parked TCU->>ECU: Flash each ECU, verify signature ECU-->>TCU: Installed TCU->>TCU: Reboot and self-test TCU->>OTA: Success OTA-->>OEM: Campaign progress
Every state of an electric vehicle charging session at a public charger, from plug-in to payment, including faults and idle fees.
A connected vehicle platform: the telematics unit in the car, the cloud services that collect data and send commands, and the owner's mobile app.
A charge point operator's platform: chargers speaking OCPP, a central management system, driver app, payments and roaming.
Where each part of a fleet management system runs: GPS devices in trucks, cloud services for tracking and analytics, and apps for managers and drivers.
What happens when a rider books a cab: fare estimate, driver matching, pickup, the trip and payment.
A database schema for a car dealership: vehicles in stock, customers, test drives, bookings, sales and service jobs.